• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] Get ready for OTA's!

I did a clean install from the onset...
Wipe all
Partition Updater
Rom
after boot disables adaptive brightness and I only have the ripple in recovery.

Mightysween at XDA seems to have the same thought that its a GPU issue, so idk. Doesn't affect functionality its just a cosmetic eye sore lol
 
SuperR said:
I wonder if I make a new flashable that updates everything except the bootloader if it would fix all the glitching. It's possible the new bootloader is causing the glitch in recovery and that the other partitions fix the glitch everywhere else.
Click to expand...
Sounds like a good idea. When its done upload and I'll give her a whirl.
 
SuperR said:
I wonder if I make a new flashable that updates everything except the bootloader if it would fix all the glitching. It's possible the new bootloader is causing the glitch in recovery and that the other partitions fix the glitch everywhere else.
Click to expand...
Just a quick point. This recovery flicker is only present in custom recoveries. I didn't have it with the stock recovery on 5.0.2...
 
starkraving said:
I did a clean install from the onset...
Wipe all
Partition Updater
Rom
after boot disables adaptive brightness and I only have the ripple in recovery.

Mightysween at XDA seems to have the same thought that its a GPU issue, so idk. Doesn't affect functionality its just a cosmetic eye sore lol
Click to expand...

starkraving said:
Just a quick point. This recovery flicker is only present in custom recoveries. I didn't have it with the stock recovery on 5.0.2...
Click to expand...
The thing is, if it were a driver issue only, I would have it too. I did not update the partitions and my cwm-swipe is glitch free.
 
Just fastbooted stock recovery from the first zip ROM and no flicker...fastbooted CWM and flicker is back. Maybe its something with partitions but whatever it is doesn't effect the stock recovery.
 
starkraving said:
You think it's boot loader related? Maybe just omit the boot loader from the package and update the modem only?
Click to expand...
That's what i am thinking. However, there are several other partitions that are updated. I was thinking to update all but the bootloader. Not sure what the best route would be
 
Has anyone tried downgrading their bootloader to 4.4.4? This might answer the question the eastiest. I can make a flashable downgrade package if someone is willing to try it.
 
Actually, it looks like the bootloader was not updated when we got 4.4.4, so it is the bootloader from 4.4.2 we would downgrade to.
 
Actually,I'm wrong. When I installed that Brazilian ROM, I was on KitKat boot loader still and I don't think I had the flickering in recovery, only on boot and after it booted until I turned the screen on and off.
 
amarc78 said:
Well, it's not bricked.☺ But the boot loader is still 41.19.
Click to expand...
Well isn't that strange. I am 100% certain I used the correct file. I wonder if it has something to do with having 2 bootloader partitions.
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11

I could make it flash both but I don't have any clue what may happen lol
 
SuperR said:
Well isn't that strange. I am 100% certain I used the correct file. I wonder if it has something to do with having 2 bootloader partitions.
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11

I could make it flash both but I don't have any clue what may happen lol
Click to expand...
Let's play a little game of android roulette. LOL.
 
Just in case you are feeling brave, this one flashes both aboot and abootBackup

edit: removed attachment for safety reasons
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom