Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "xda"
What a beautiful morning.
Heard my phone going crazy because of notifs.
Turned on DND.
Made myself a coffee.
Drunk the coffee.
Looked at phone.
Email from paypal.
Hello you have received donation.
Looking at how much (expecting like 5$ or less) 20$ ?????????
Wtf the guy did go crazy ??????
Looking at XDA.
Hi, i have sent you a donation. I hope you can get that money to good use. Thank you for your hard work on our old device.
Really good morning.9
The moment i started Android Porting.
The tons of messages i got on XDA from random people.
Oh fucking hell
But one message was like WTF ?
Not exactly the message but it has the same point.
Hey Bro, I installer your room and it work but when i turned my phone of it didnt turn back on. The small buttn on side doesnt work to turn it on.
Then he posted the same message to thread since i dont respond to PMs.
Some user helped him and what was the issue ?
HIS FUCKING PHONE BATTERY WAS DEAD
He just had to charge it. FFS6
Yep, you need to know c++, php, HTML, CMS, and </> to become an Android developer.
That's not important.
I love sponsored content. Always accurate.10
*wondered for 4 years how a bootloop looks like*
Nexus: yOU wAnE kNoW wHaT a BoOtLoOp LoOkS LiKe?!
*bootloops itself to shit*
Well I guess that I know what I'll be doing tonight then. Flash that new StatixOS build because the phone shat itself.
*tries to reflash the recovery*
*tries to flash the stock OS*
*still fucking bootloops*
*finds a post on XDA saying something about fucked big cores that need to be disabled*
Fucking piece of junk. So not only the battery is shit, but also the CPU is shit, huh. Certified pieces of shit.
*flashes the patched boot.img that disables the big cores*
*phone loads Google logo.. good*
*BOOTLOOPS FUCKING AGAIN*
MJHUIETHNIUBESZPTUIBG ESVGU d
FUCK!!! Fuck you Google, fuck you Nexus, fuck you Huawei, HOW DIFFICULT CAN IT BE TO DESIGN A FUCKING PHONE?!!!
So yeah. Looking for suggestions for a new phone. Anything of which the kernel source is released and of which the battery is halfway decent (unlike this fucking piece of shit) should do.7
Decided to upgrade my hardware a day after wk119 ends. Oof. I'll post an update once the first part (monitors) arrives, but here's a before pic in the meantime.
Monitors: 3 different brands at 3 different sizes/resolutions. Left to right: 1920x1080, 1680x1050, 1440x900.
Mic: Neewer NW-800 with a U-PHORIA UMC22 interface.
Keyboard: A DIY Nyquist kit from keeb.io with Canvas XDA keycaps.
Rubber duck: I prefer a fuzzy kitten.3
Oh fucking Huawei.
- Honor 6x (BLN-L22C675)
- Has EMUI4.1 Marshmallow
- Cousin brother 'A' (has bricking XP!)
- Uncle 'K'
- Has Mac with Windows VM
- Stock as LineageOS / AOSP
Procedure (fucking seriously):
- Find XDA link to root H6X
- Go to Huawei page and fill out form
- Receive and use bootloader code
- Find latest TWRP
- Flash latest TWRP
- TWRP not working? Bootloops
- XDA search "H6X boot to recovery"
- Find and try modded TWRP
- TWRP fails, no bootloop
- Find & flash TWRP 3.1.0
- Yay! TWRP works
- Find and download LineageOS and SuperSU
- Flash via TWRP
- Yay! Success.
- Attempt boot
- Boot fails. No idea why
- Go back to TWRP
- TWRP gives shitload of errors
"cannot mount /data, storage etc."
- Feel fucked up
- Notice that userdata partition exists,
but FSTAB doesn't take
- Remembers SuperSU modded boot
image and FSTABS!
- Fuck SuperSU
- Attempt to mod boot image
- Doesn't work (modded successfully
but no change)
- Discover Huawei DLOAD
Installer for "UPDATE.APP" OTAs
Note: Each full OTA is 2+ GB zipped
- Find, download, fail on 4+ OTAs
- Discover "UPDATE.APP Extractor"
Runs on Windows
Note: UPDATE.APP custom format
Different per H6X model
- Uses 'K''s VM to test
- My H6X model does not have
a predefined format
- Process to get format requires
TWRP, which is not working
- FAIL HERE
- Discover "Firmware Finder"
Windows app to find Huawei
- Tries 'K''s VM
- Fails with 1 OTA
- Downloads another firmware ZIP
- Unzips and tries to use OTA
- Boots successfully?!
- Seems to have EMUI 5.0 Nougat
- Downloads, flashes TWRP
- TWRP not working AGAIN?
- Go back to XDA page
- Find that TWRP on EMUI 5 - NO
- Find rollbacks for EMUI5 -> EMUI4
- Test, fail 2-4 times (Massive OTAs)
- DLOAD accepts this one?!!!
- I HAVE ORIG AGAIN!!!
- Re-unlock and reflash TWRP
- Realise that ROMs aren't working on
EMUI 4.1; Find TWRPs for EMUI5
- Find and fail with 2-3 OTAs
Note: Had removed old OTAs for
space on Chromebook (32GB)
- In anger, flash one with TWRP
instead of DLOAD (which checks
- Works! Same wasn't working with
- Find and flash a custom TWRP
as old one still exists (not wiped in
- Try flashing LineageOS
- LineageOS stuck in boot
- Try flashing AOSP
- Try flashing Resurruction Remix
- Realise that need stock EMUI5
- Realise that the firmware I installed
wasn't for my device so not working
- FUCK NO MORE LARGE DLs
- Try another custom TWRP
- Begin getting '/cust mounting' errs
- Try reflashing EMUI5 with TWRP
- Doesn't work
- Try DLOADing EMUI5
- Like before, incompatability
- DLOAD EMUI4
- Reunlock and reflash TWRP
- WRITE THIS AS A BREAK
Typical interaction in any XDA development thread:
User: How do I put these ROMs on my phone? Plz halp!
Me: ROOT -> flash RECOVERY -> enter recovery -> flash ROM -> flash Gapps -> profit.
User: How to get the roots? Can halp me?
Me: You're in a Nexus forum. There are directions on how to root everywhere.
User: I can't find. Plz halp.
Me: Fastboot oem unlock, fastboot flash recovery.img, flash SuperSU, flash ROM...
User: Where I can get fastboot?
Me: *link to Google developer's page*
User: Can you just tell me?
Me: No, you need to figure it out, so you know what you're doing.
*2 hours later*
User: HALP! I use toolkit for to get roots, and now phone won't come on! How to fix?! Halp, halp, halp!
*5 minutes later*
Ok thats enaugh.
Some people are still so fucking stupid to ask the same question on XDA and on my thread 15 fucking times.
When you will release it ??
2 days later.
When will you release it ??
And so on.
Until i got to this point.
I fucking swear if i see some stupid question on my fucking thread that has been answered and the user just cant search then he will get very rude response.
This needs to be done since my thread isnt the only one with those idiotic questions: when will it be done, how to root it (Literally in the main post is the answer).
Lot of devs on XDA agree.
I understand that they are new to it but for ffs search !!!!!!15
Porting 8.1 to old device is really pain but thats nothing compared to whats to come.
Google annouced Project Treble and it does that vendor shit is on partition and init files are edited to make them load. Then you can run GSI (Generic System Image). When it was released all developers said that its impossible to bring support for it unofficialy. Then some guys on XDA ported it to Xiaomi phone. Great they proved almost entire XDA wrong. Great. Then few phones did the same. Amazing. Now almost any phone with good dev can be trebelized. Great. Well the device needs 400MB+ partition that is unused so that we can add vendor files there. Well its issue on my phone since i dont have that big unused partition. FUCK. Well i have 11.1GB Virtual SDcard partition. Hmmmm maybe i can resize that partition and create new partition of size 500MB to make it as vendor. OK great. Once thats solved then just copy them and done. WRONGGGGGGGGGGGGG. Its not that easy. First you need to make a script that places all device releated shit into vendor. OK thats easy. Then comes the hard part. Those vendor files have no fucking clue they are in not in system folder. So they start loading shit and ofcourse they will fail if they are not in system. Well most users think we are done thats its over. Its not. HEX editing comes to the rescue. You edit every single blob to make it compatible with vendor partition. OK after that hell pain you are almost done. Just edit init files and try GSI. It will probably fail to boot. Now you search logs for missing crap and slowly add that until it boots.
So this is ahead of me since i dont have 8.1 support yet. But once its done then im coming for you treble. Ohhhhhh how cool would it be to run android P on Xperia P ?
Sure you can skip treble porting but its better if you do it since it makes porting new android version soooooooo much easier.11
Bad thing: I spilled booze on my fabrics yet again. I probably shouldn't drink from the couch or the bed anymore.
Good thing: I found out how to disassemble my tablet and removed its cameras.
Bad thing: front cam couldn't be removed without damaging some traces for a coax connection.
Bad thing: during disassembly I noticed significant amounts of corporate "fuck you" and certified enganeering. Like allowing the rubber back plates of the tablet to come off, but not get back on without percussive maintenance!!! FUCKING CERTIFIED PIECES OF SHIT!!!
Good thing: even after a lot of Tappy-tap-tap, the tablet still works without a problem. Hopefully I can now save some others from the shitstains by posting about it on the XDA thread 🤔
Overall verdict: FUCK!!!12
I would like to know some of you guys most used/preferred apps that you have been using it for long time or you will install them immediately after purchasing new phone/ formating/ installing custom ROM.
List them down if you feel like it, maybe some of them can be helpful to us. Here's mine list.
P.S. Apart from devRant
- ES file Explorer
- NoRoot firewall
- xda labs
- Nova launcher8
Its possible that this or the next build of Lineage15.1 will finally boot on my Nypon.
If it doesnt then at least most of the shit is fixed and what comes next will be pretty quick i hope.
If it does then im gonna have looooot of fun on XDA and Telegram with people. Because they have no clue im almost done with 8.1 Ohhhhh yes im terrible person for not telling them but i dont want to get their hopes high if i fail somehow.
Im gonna be like */Takes picture of the tasty oreo coockie/* They are gonna tell me thats nice and wont beleive me. Then im just gonna post a link and tell them to test it without telling them what it is and renaming it to 13.0 just for fun. Then they boot it and find out that its oreo. MUHAHAHHAHHAHAHAHHAHAHHAHA. Its kind of nice.2
Muhahahahahahah i came up with a way to post my testing ROMs on xda without fucking noobs downloading it and spamming the thread with wifi doesnt work and ETC bullshit. (Ahhhhh i hate them sooooooooo fucking much).
Easy just create a C code that has the URL encrypted and the code decrypts it. Well noob woudlnt be able to decode it on his own. (At least i hope so).
Still less people get access to it and less spam.4
My new HTC smartphone hates me.
First it started to shut down all of the sudden yesterday night, when I was solving quadratic equations on my laptop.
I thought that it might be due to low battery. So I have restarted it. After putting itself into a bootloop for 4 start sequences, it was able to fully start to the page where it told me to enter the security pin to decrypt my files. I also had 30 attempts left. Like a ransomware.
I was like "tf I didn't set anything up".
So I decided to use my first attempt as I had 30 attempts left.
I entered the pin (I can swear that it's correct) and it told me that it has to wipe the /data partition.
I did that. I pressed that button. After waiting for 30 minutes I gave up and rebooted into the bootloader.
Bootloader -> Download Mode -> wipe /data (stock rom + stock recovery btw.)
Some error with "e: mount /cache failed[...]e: mount /data failed"
So, I tried using the adb sideload - no success.
Fastbooted into RUU Mode - HTC keeps rebooting itself into the RUU Mode - no success
Tried to flash the firmware and twrp recovery from Download mode - no success
Then I tried to flash all these things from the sd card - no success
Searched for revolutionary (I know this from my old HTC sensation device).
It wasn't big of any help.
Then someone on xda recommended htcDev (htc's <b>developer-friendly</b> lol site)
I followed every step. Everything seemed to be okay.
I got to the last step.
I needed to get my encrypted token by entering "fastboot oem get_identifier_token" to be able to submit it to HTC, and after they would send me an e-Mail with an .bin file that would let me unlock the bootloader to be able to flash my way through all this headache giving fucking piece of dog shit!
But since I can't back to the phone settings to select the bootloader activation box that would let me get my token... but nah.
Sent by using the devRant web app (:\)8
Getting a new phone next month and its development is so far non existent on XDA.
So as you could have guessed yes im downloading sources and getting to work for AOSP build.
Oh and its SONY so its not gonna be that hard.4
I will write a bot for XDA PMs that when it receives new PM and reads please, alpha, build then it will make a angry fucking response that is really long and will just sign at the end
-Haxk20 fucking angry PM bot.
(Dev)Life in the past 12 hours
Oh boy have the last 12 hours been a roller coaster ride for me. Noob me decided to "compile" AoSP for my device to get a taste of how custom ROMs are built from source. Overall it was fun but the errors were a very good excercise for googling, SO. Couple stuff I learnt ( possibly useful for anyone who comes here )
* The shebang line ( #!/usr/bin/env python ) on my system translated to Python 3.7 environment instead of the expected Python 2.7. Best solution I think to avoid confusion is to create a python 2.7 environment and source it.
* Get your trees right. A jar file called WfdCommon.jar ( apparently known as wifi-display common ) was the cause of several hours of hunting the fault. My vendor tree somehow didn't have this file so dex2oat was borking out like mad. I'm still amazed how I figured this one out almost by myself. ( Basically I had to check every file included in the boot class path, and find the odd one )
* I wasted a lot of time in finding the right files to change version numbers and all. Maybe I didn't search XDA properly for a guide ?
Overall it was a fun experience. Also if anyone's experienced in this area could you share resources to learn more about custom ROM development? Specifically on the tweaking part where you mix features from different ROMs to make a great ROM ( like AoSP extended or Pixel Experience ). All I could find were on the zips and not on sources.10
When you know they are going to curse you like "rom is unstable... you broke my phone" so you deal them like this 😂1
Building RR for my device from 2013 with excellent support still. (Xperia SP).
Damn I think I never saw easier build.
No errors on first try.
Just edited devote tree to work with RR and boom working ROM.
But that is only because of one of the best devs at XDA since he is supporting this device in LineageOS.6
BEST DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
To all those idiots at xda who always ask for ETA and when x will be fixed.
Fuck you !!!!!!!!!!!
You have access literary to all my fucking sources.
Why dont you fix the fucking RIL if you cant wait.
I would all of them give 1 week to fix some easy bug without internet and let the suffer like that. Then they might realize it isnt easy to fix android hw bugs.
You have brain too.
But i can just use it much much better.10
My older brother introduced me to linux and android custom roms when I was like 11. So I flashed my old sony Ericson phone with custom roms from xda and tried Ubuntu live CDs on my mother's old 40gb hdd laptop.
But my introduction to programming was when I saw some videos about the raspberry pi on YouTube.
I was like 14 and programmed basic scripts for my raspberry pi in nano over putty or notepad++.
At first I didn't even knew to intendent but in the process of my first project (Python sunrise alarm clock with tts) I learned many valuable things about Python and Linux/Debian.
The years after that I learned more with my now multiple RaspberryPIs, Arduinos and other hardware.
So in conclusion RaspberryPIs, the diy/open source community and especially my brother introduced me to programming.
Latest promoted thread on XDA to make the list:
"how to disable forced encryption".
This is from a place that tries to be innovative. I'm half expecting a thread get promoted with the title "how to give everyone your passwords/identity/credit cards".
Ohhh update on the LineageOS16. Everything works. So this weekend im doing full port of LineageOS17. Sure its a dirty port since im just basically taking SODP (Sony Open-Source Device Project) sources and using them in LineageOS sources so it has to work kind of but its still a port of custom ROM thats usable. And well since LineageOS17 is getting to the stage that more and more roms are getting out on XDA then well i will do the same.3
postmarketOS port day uhmmmmmmmmmmmm 3.
Surprisingly to get a port of it you just need kernel which is hella awesome. What isnt awesome is the boot image of the 2012,2013 sony devices.
This is gonna get technical. If you dont care about it just skip it.
So sony decided that using ELF format for boot image is good idea. And TBH they were kinda right. ARM processor after all can execute ELF natively and work efficiently. Whats the issue then you might ask. Well kinda simple. Normal AOSP boot images are not ELF format. (They kinda are but arent at the same time. Lets just say they contain ELF image at some point). This is of course the google way. Overenginner everything you can.
So why is the ELF image format the issue ? Well to produce this elf image you need special script provided by sony that can make ELF format boot image that you have to compress properly afterwards. OK this sounds OK so whats the issue ? AOSP or well android sources do not support this out of the box. What we need to do is to create a custom way of creating that boot image. Which isnt hard but is just extra unneeded work.
Now when you flash the image it all works as expected.
But what happens if the format isnt right ?
Device will just show blank screen and reboot and so on forever (Or well until battery dies).
Why it cant boot other images is kinda self explanatory. Its different format. OK so it wont boot anything other then custom boot image OK.
Now what does postmarketOS (PMOS from now on) do ?
Well it creates basic AOSP bootimage with custom ramdisk. Which is all fine on most devices. Except here of course.
So that wont boot.
You may just say why dont you just convert it ? Well it isnt that easy. Each elf file has its own header. Which is for that kernel and etc. If it doesnt match eyyyy no boot. So we cant just convert it that easily.
Why not just use the script ? One could do that of course. ( i have not yet done that as its almost midnight and i have test tomorrow). Issue here could be that it still doesnt boot which would mean that something else is wrong. It will most likely work tho. (hopefully)
What i would need now is UART. (Yes phones have UART if you didnt know)
What is that ? Way to communicate and debug the kernel when something is wrong to the point where nothing works. Issue is my UART to USB converter is who knows where and the new one isnt going to be here that soon.
Thats all for now i guess. Long one i know. But well that is the behind the scenes of those kind of things. It isnt as simple as one may think sadly.
It woudlnt be my first and sadly not even last time i would get PM saying to hurry the development or some other shit like that. (Yes people are like that). And when you get issue it isnt as easy as opening duckduckgo and searching it as most likely it will return something which is far from what you are doing.
So if you are that kind of person that sends PMs to devs on XDA to hurry the development or asking when its gonna be done. STOP. Please just stop. We have real life too (I know its hard to believe but well its there) and doing this isnt the only thing we do. Its gonna be done when its gonna be done. And i hope this is gonna at least put some perspective for those people to not send those kinds of messages to us. (We read them. We just dont reply to shit)
TL;DR Sony decided to use different format of bootimage on 2012/3 devices which is pain to generate properly.2
I first started off with a pentium 3 machine in 2004, started gaming on warcraft 3 and maplestory and eventually got addicted to it because nothing else was interesting in my life. Okay extending this story, i eventually got banned, dad smashed 1000 bucks of his money by kicking and throwing it. Years later (i think it was 2011), i got hold of my first Android device. This time round, things were different and I spent 6 months with it problem free and then it started lagging. Google search led me to XDA, started modding the device, eventually startedgetting interested about how people do it and voila, C prog, write some management drivers for malloc and etc. Eventually i dropped kernel development 3 years later and now im in .NET Core.5
Guys, i've searched long and hard for a custom Kindle fire 1st Gen ROM... Digging through the internet to find this shit is hard. The dropbox links on XDA for OtterKat aren't working.
I managed to flash Cyanogen to my other kindle (Fire HD 7) - which my dad wants back, even though he dosent use it. I'm left with this first gen, and i've been at it all day2
Is it possible to install a Linux distro on a android phone?
I have already unlocked bootloader so it should work right? Android is linux too.
I'm sorry if this is more of a xda-developers or stackoverflow question. Tell me if i should move the question somewhere else.2
!Rant, I have finally found a custom Android ROM that works on my phone. Thank you Rohan Purohit, You are a legend.
Here's the link for any curious people:
Flashed the amazon-official firmware for the KF1. great. backed up. fantastic.
now to find a rom.
nothing on XDA is actually there; all of the download links for kindle fire 1st gen lead to 404 pages. I'm actually getting very stressed over this. if i'm being stupid and missing a working link to a compatible ROM for KF1, PLEASE tell me
- Your pal Park