Database Info

Wiped and Formated, Now Cant Flash?

Usually I just wipe data, cache, and dalvik. Today though I did this plus formated data, cache, and system. I never do this but the JellyWiz rom I was flashing said to do so. Since I did this the rom will not flash.
E: Can't open /external_sd_Root/Incubus26jc_JellyWiz_VZW_9_14_12_RLS3.zip (bad)
Installation aborted.
Click to expand...
Click to collapse
When I tried restoring the old JB version I was updating from it gave me a MD5 mismatch error. When I tried to restore my original stock root which I have restored from several times without issue it just gave me "Error while restoring /system."
Need help! Stuck in recovery with no idea what to do

Try flashing a firmware through odin: 0
sent from my Galaxy s3 GT i9300 using xda premium HD @ jelly bean leaked builds

i9100g user said:
Try flashing a firmware through odin: 0
sent from my Galaxy s3 GT i9300 using xda premium HD @ jelly bean leaked builds
Click to expand...
Click to collapse
Not really sure what this means to be honest. I rooted using odin but what do you mean by flashing a firmware?

josbor11 said:
Not really sure what this means to be honest. I rooted using odin but what do you mean by flashing a firmware?
Click to expand...
Click to collapse
Yes, do that again. Boot into Download mode(Batt pull to turn the phone off) then hold vol down+home+power till the prompt comes up.
Flash the root66 image using Odin from there.

Brian Gove said:
Yes, do that again. Boot into Download mode(Batt pull to turn the phone off) then hold vol down+home+power till the prompt comes up.
Flash the root66 image using Odin from there.
Click to expand...
Click to collapse
I can just flash 66 as is? Don't have to flash a stock unrooted version first like you do when you brick?
Do you have any idea why this could have happened? I did everything it said on the page and even watched an installation video for the ROM following every step by step instruction. What the hell does formatting system, data, and cache do in recovery? Never had done it before and as soon as I did my phone just messed up. Also, if I flash 66 using odin will my old backups work again?

josbor11 said:
I can just flash 66 as is? Don't have to flash a stock unrooted version first like you do when you brick?
Do you have any idea why this could have happened? I did everything it said on the page and even watched an installation video for the ROM following every step by step instruction. What the hell does formatting system, data, and cache do in recovery? Never had done it before and as soon as I did my phone just messed up. Also, if I flash 66 using odin will my old backups work again?
Click to expand...
Click to collapse
I'm guessing there was a bad download and sadly your nandroid might have been corrupted.
Yes if you flash root66 hopefully your backups will work if they aren't corrupted.
Sent from my Galaxy Nexus using xda app-developers app

voodoomanx said:
I'm guessing there was a bad download and sadly your nandroid might have been corrupted.
Yes if you flash root66 hopefully your backups will work if they aren't corrupted.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Cool thanks. Flashing 66 now through odin. My backups have worked fine before (the exact same ones that just failed). Once this is finished and I test out my backups (assuming they work) how should I go about reflashing JellyWiz? Should I format the system, data, cache again or just do the normal wipes? I'm afraid formatting will mess it up again. Is CWM inferior to TWRP? Thinking about using a different recovery after all of this.

josbor11 said:
Cool thanks. Flashing 66 now through odin. My backups have worked fine before (the exact same ones that just failed). Once this is finished and I test out my backups (assuming they work) how should I go about reflashing JellyWiz? Should I format the system, data, cache again or just do the normal wipes? I'm afraid formatting will mess it up again. Is CWM inferior to TWRP? Thinking about using a different recovery after all of this.
Click to expand...
Click to collapse
I personally use cwm and to me it's more a matter of preference. I too have had a error restoring backups once and it was after a system wipe. A word of advice, because this saved me, keep a ROM on your SD card at all times to be able to just flash in an emergency.
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
I personally use cwm and to me it's more a matter of preference. I too have had a error restoring backups once and it was after a system wipe. A word of advice, because this saved me, keep a ROM on your SD card at all times to be able to just flash in an emergency.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
A rom of Root 66?

Is it cwm flashable? I keep synergy as an emergency backup.
Sent from my SCH-I535 using xda app-developers app

josbor11 said:
A rom of Root 66?
Click to expand...
Click to collapse
dont listen to him...flash root66 thru odin as already mentioned and go from there...use my guide if need be.

droidstyle said:
dont listen to him...flash root66 thru odin as already mentioned and go from there...use my guide if need be.
Click to expand...
Click to collapse
I think you missed my point, at this point he needs Odin. However, if you keep a zip on your SD card then if your backups gasp like his situation he can just fish that zip. It was simply some advice for future reference, were not all next to a computer ask the time. For people like me that just get an urge to flash it helps to have backups like this.
Sent from my SCH-I535 using xda app-developers app

No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium

annoyingduck said:
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
in order to flash jellywiz i had to do the following or else i bootlooped:
wipe data/factory reset
wipe dalvik cache
format system
flash rom
booted up flawless.
i also used this methid for paranoid android...i will probably update my guide with this. unfortunately i cant give any info on what formatting system is actually doing. never had to do this before??

annoyingduck said:
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I don't know why they are suggesting it but it doesn't do anything beyond the normal factory reset and then the zip formatting system itself.
Its just the manual way of doing what a clean flash does.

Why are people having issues restoring nandroids after doing this? Apparently bootlooping occurs after format/jb install/restore previous nandroid.
Sent from my SCH-I535 using xda premium

Brian Gove said:
I don't know why they are suggesting it but it doesn't do anything beyond the normal factory reset and then the zip formatting system itself.
Its just the manual way of doing what a clean flash does.
Click to expand...
Click to collapse
if im not mistaken formatting the system deletes the rom/kernel itself...normal factory reset from cwm recovery only deletes rom data/cache.
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
annoyingduck said:
Why are people having issues restoring nandroids after doing this? Apparently bootlooping occurs after format/jb install/restore previous nandroid.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
edit* good question!

droidstyle said:
if im not mistaken formatting the system deletes the rom/kernel itself...normal factory reset from cwm recovery only deletes rom data/cache.
Click to expand...
Click to collapse
Yeah you're right but the zip of the ROM 99% of the time formats system also.

Brian Gove said:
Yeah you're right but the zip of the ROM 99% of the time formats system also.
Click to expand...
Click to collapse
i wonder why i had to format system to get the latest jellywiz rom to not hang on galaxy s splash screen? it makes no sense.

Also, how does a format not erase your nandroids? It should also wipe titanium backups if they are not on your external. Am I wrong on that? Could formatting lose certain bits of info that the nandroid may not have partitioned, and that's why the restores are not working correctly?
Sent from my SCH-I535 using xda premium
---------- Post added at 09:57 PM ---------- Previous post was at 09:55 PM ----------
Add on: good info guys
Sent from my SCH-I535 using xda premium

Trying to install CM10 with TWRP

I have an att htc one x that has 4.01 and 2.20 software. I was able to successfully root the phone and now I'm trying to install CM10 but it's failing when trying to install.
It says it missing a MD5 File and says theres an error in the SD card/download/ the cm 10 file.
What am I doing wrong? Thank you

Make sure the Rom is for our phone and check the md5 sum it might be a bad download

I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru

kswannabe said:
I've tried redownloading the file several times and I'm still getting the same error message.
I'm downloading CM10 from here http://get.cm/?device=endeavoru
Click to expand...
Click to collapse
Wrong version, endeavoru is the international (Tegra3) One X. Our phone is code named evita.
Just stick to the Development forum here, to avoid flashing ROMs for the wrong version of the One X:
http://forum.xda-developers.com/forumdisplay.php?f=1726

Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?

kswannabe said:
Thanks for the information.
Was able to successfully flash to CM10 but I'm stuck at the CM10 boot screen. Circle going counter clock wise around. What should I do?
Click to expand...
Click to collapse
If you flashed an international rom, there's a good possibility you messed something up. Factory reset, wipe /system, and try flashing the correct CM10 rom again.

Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?

kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
A guy I was working with had the boot screen splash. If you've flashed the correct one, then wipe your caches. if that doesn't work reflash.

kswannabe said:
Ok. I'm trying to do a factory reset from bootloader but whenever I do, it goes to the CM10 boot screen where I was earlier. How can I do a factory reset?
Click to expand...
Click to collapse
Don't do it from bootloader, it can corrupt your sdcard. Do it from recovery.
Go into recovery, wipe cache, dalvik cache, factory reset and system. Then install the CORRECT rom.
Sent from my One X using xda premium

How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
And there goes my stock rom... Factory reset is not working on TWRP and tried system reset thinking it would get rid of CM10 but instead erased my stock rom.
Please help, need a working phone soon..

kswannabe said:
How can I reflash?
Thanks
-edit-
I was able to get back into TWRP. There I tried to do a factory reset but it tells me it failed. And after installing CM10, do I have to go back into bootloader and flash boot.img from the CM10 nightly zip file?
Click to expand...
Click to collapse
There are stickies and tuts around here for this.. but, the reason why it's not working for you is you didn't flash the boot.img first. before you installed the .zip. Also, you'll need the latest gapps for that ROM as well.

Not familiar with the forums around here, so if you could link me some of these stickies or tutorial it would be great.

Have a look here
Sent from my One X using xda premium

timmaaa said:
Have a look here
Sent from my One X using xda premium
Click to expand...
Click to collapse
or here http://forum.xda-developers.com/showthread.php?t=1952076

I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.

mfc1288 said:
I have this problem. i went to the thread you posted, loaded TWRP, I've factory reset and what not, but now I'm stuck in TWRP without any real viable options. When I try to reboot to system, it brings me back to TWRP menu.
Click to expand...
Click to collapse
Do you have a rom flashed? If so, wipe both caches and reboot. If that doesn't work, reflash and do a system wipe from TWRP.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Rooted SGH-T989D trying to flash CM10
kswannabe said:
How can I reflash?
Thanks
Click to expand...
Click to collapse
hi. i have fallowed all the steps to root my phone from this site. when i go down to how to flash a rom i have some issues.
i am trying to flash CM10. when i go to install on (step 8) i get an errer. my screen says
Updating partition details...
Running boot script...
Finished running boot script.
E:Unable to open zip file.
Error flashing zip /external_sd/cm-10.1-hercu
Updating partition derails...
then it shows the home butten. failed in red than wipe cach/dalvik and reboot system buttons
anyone have any idea what im doing wrong?

Exactly which phone do you have? It looks like it says Hercules in the cm file name you wrote, which I think is a Samsung.
Sent from my Evita

Corrupted userdata partition

Basically, my userdata partition keeps getting corrupted every couple of flashes. I have to factory flash to get everything working again. It just started happening recently(A few hours ago). What is going on? Thanks!

While flashing the stock images make sure you have also Erased cache partition and formatted it using stock recovery.. I was exactly in the same spot as you were few weeks ago and a cache partition format solved it completely!

Koopa777 said:
Basically, my userdata partition keeps getting corrupted every couple of flashes. I have to factory flash to get everything working again. It just started happening recently(A few hours ago). What is going on? Thanks!
Click to expand...
Click to collapse
I had the same problem as you. I used this guide and now it works great. Just follow the steps. Good luck.

prabs99 said:
I had the same problem as you. I used this guide and now it works great. Just follow the steps. Good luck.
Click to expand...
Click to collapse
I can actually confirm that it is an issue with ParanoidAndroid. It always corrupts the data partition following boot. I repeated it with continued success.
Sent from my Nexus 5 using Tapatalk

Koopa777 said:
I can actually confirm that it is an issue with ParanoidAndroid. It always corrupts the data partition following boot. I repeated it with continued success.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You're the only one saying such things. If there was a problem with the ROM we would have heard it from others and the team would see the same issues.
The ROM ships with stock Google kernel. The ROM doesn't do anything in itself that could corrupt your userdata
Sent from my Nexus 5

Pirateghost said:
You're the only one saying such things. If there was a problem with the ROM we would have heard it from others and the team would see the same issues.
The ROM ships with stock Google kernel. The ROM doesn't do anything in itself that could corrupt your userdata
Sent from my Nexus 5
Click to expand...
Click to collapse
I've come to the conclusion, after 4(!) factory images, that the ROM DEFINITELY corrupts the recovery. I have a 100% success(failure?) rate when flashing PA. Clean md5, after first boot the ROM functions properly, but recovery fails to mount the userdata partition, every time. Flash a new recovery, or adb shell and attempt to repair don't work. I understand that it doesn't make sense, but it's obviously something that's happening with the ROM. After 4 factory images, the only other factors are the recovery(PhilZ, TWRP, AND CWM all fail) being borked from the start, or the ROM. It's obviously not the recovery(all 3 have clean md5s, are transferred with adb push, and function perfectly otherwise).....
Again, in the ROM I can r/w to the /data, so the partition is fine, but the ROM borks the recovery.

But there is nothing in the ROM that would cause that. Are you restoring anything from previous versions? Are you installing an app that does this?
Sent from my Nexus 5

Pirateghost said:
But there is nothing in the ROM that would cause that. Are you restoring anything from previous versions? Are you installing an app that does this?
Sent from my Nexus 5
Click to expand...
Click to collapse
No and no. I don't even install Gapps. The ROM alone still triggers it. I just boot into system then boot to recovery.
Sent from my Nexus 5 using Tapatalk

Koopa777 said:
No and no. I don't even install Gapps. The ROM alone still triggers it. I just boot into system then boot to recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This sounds like you have a hardware issue. Did it do this on stock image with custom recovery?
Sent from my Nexus 5

Pirateghost said:
This sounds like you have a hardware issue. Did it do this on stock image with custom recovery?
Sent from my Nexus 5
Click to expand...
Click to collapse
No. I can flash different ROMs, kernels, etc. Just not PA. The only thing of note was that my stock backup bootlooped when restoring with TWRP, but other than that no.
Sent from my Nexus 5 using Tapatalk

Nevermind, I just flashed liquidsmooth+Elementalx with PhilZ and it happened again. So what exactly is going on?

Are you not able to repair the corrupted partition as explained in the linked thread?
Sent from my Nexus 5

Pirateghost said:
Are you not able to repair the corrupted partition as explained in the linked thread?
Sent from my Nexus 5
Click to expand...
Click to collapse
Nope. Adb shell in Philz says repair failed. I found this
http://forum.xda-developers.com/google-nexus-5/help/unable-to-mount-data-issue-t2723993
http://forum.xda-developers.com/google-nexus-5/help/recovery-mount-data-t2639945
But neither helps. Recovery still can not mount /data.

I would RMA it.
Sent from my Nexus 5

I would try LG Flashtool it worked for me.

maxal said:
I would try LG Flashtool it worked for me.
Click to expand...
Click to collapse
Seriously? I have the LGFT installed(G2 owner) too. Hm......So basically get the tot and dll, and flash? COM41 and all that jazz?

Koopa777 said:
Seriously? I have the LGFT installed(G2 owner) too. Hm......So basically get the tot and dll, and flash? COM41 and all that jazz?
Click to expand...
Click to collapse
Yup, here is the link http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

I just called Google. RMA is inbound. It just kind of sucks, this phone was solid. No light bleed, no dead pixels, etc. Except for a loose power button.
Anyway I think it is definately a hardware issue, as my phone has been getting crazy hot lately. I know it's supposed to get hot, but this phone was scorching...Might have fried something.

Help updated 4.4.2

I'm on stock rooted 4.4.2 running Franco kernel. Question is how do I update with out bringing phone to factory settings
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK

you make a backup in recovery, then dirty flash, dont wipe a single thing, 444 over it. if alls well after, then perfect. if you have issues, you have that backup in recovery to restore

simms22 said:
you make a backup in recovery, then dirty flash, dont wipe a single thing, 444 over it. if alls well after, then perfect. if you have issues, you have that backup in recovery to restore
Click to expand...
Click to collapse
I downloaded then tried to flash the zip file in twrp .. It says it failed not sure what to do next and is 4.4.4 the latest firmware?
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK

ROADKING17 said:
I downloaded then tried to flash the zip file in twrp .. It says it failed not sure what to do next and is 4.4.4 the latest firmware?
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
Unfortunately my clairvoyant skills aren't working today
perhaps you could elaborate on the following 2 things
1) what zip are you flashing?
2) what error are you getting?
Sent from my Nexus 5 using Tapatalk

The pop up I get every 3 days for me to update my device to 4.4.3 I believe.. It's located in twrp under cache... When I try flashing it says error in red lettering ... Also I tried Uninstalling Xposed but seems not to change anything
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK

ROADKING17 said:
The pop up I get every 3 days for me to update my device to 4.4.3 I believe.. It's located in twrp under cache... When I try flashing it says error in red lettering ... Also I tried Uninstalling Xposed but seems not to change anything
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
Don't use OTA updates. Just manually flash a rooted stock ROM via TWRP.
Click the link in my signature and go to the "resources" section. You'll find a full rooted, PURE STOCK 4.4.4 rom there.
Copy it to your /sdcard, take a FULL nandroid backup then flash the ROM.

rootSU said:
Don't use OTA updates. Just manually flash a rooted stock ROM via TWRP.
Click the link in my signature and go to the "resources" section. You'll find a full rooted, PURE STOCK 4.4.4 rom there.
Copy it to your /sdcard, take a FULL nandroid backup then flash the ROM.
Click to expand...
Click to collapse
Will I lose anything on my device and will I be able to dirty flash
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK

ROADKING17 said:
Will I lose anything on my device and will I be able to dirty flash
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
did you read any of the threads? the answer is in there.

ROADKING17 said:
Will I lose anything on my device and will I be able to dirty flash
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
Click to expand...
Click to collapse
if the dirty flash is successful, you wont lose a thing, except time. if you have to go back and wipe, you will lose your data. so, make a backup in recovery first, before the dirty flash.

I think I still have MultiRom boot.img

So I have used MultiRom for a while. It was cool to mess with, but in practice it wasn't something I used often. I used the uninstall option to delete it from my device.
But I have noticed, that my battery charging icon is different from the default. I think this is still the MultiRom boot.IMG.
Also sometimes the led splashes green, also a feature of MultiRom to know when it is listening for a keystroke.
Can I somehow see what boot IMG this is, and should I change it to the original OPO one?
Thanks,
-JustRamon
Sent from my A0001 using Tapatalk

JustRamon said:
So I have used MultiRom for a while. It was cool to mess with, but in practice it wasn't something I used often. I used the uninstall option to delete it from my device.
But I have noticed, that my battery charging icon is different from the default. I think this is still the MultiRom boot.IMG.
Also sometimes the led splashes green, also a feature of MultiRom to know when it is listening for a keystroke.
Can I somehow see what boot IMG this is, and should I change it to the original OPO one?
Thanks,
-JustRamon
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your battery icon has nothing to do with the kernel, so that isn't it. You probably didn't wipe properly (system, data, cache, dalvik cache) when you flashed last or there are some remnants of Multirom left over. Your best option is to first use TWRP to wipe your data partition, and then to flash the stock images with fastboot. Once you've done this just flash whatever ROM you want (wipe properly first).

Heisenberg said:
Your battery icon has nothing to do with the kernel, so that isn't it. You probably didn't wipe properly (system, data, cache, dalvik cache) when you flashed last or there are some remnants of Multirom left over. Your best option is to first use TWRP to wipe your data partition, and then to flash the stock images with fastboot. Once you've done this just flash whatever ROM you want (wipe properly first).
Click to expand...
Click to collapse
I meant the charging animation outside the rom. Normally its a big battery with red/green filling, but for me its just a small white battery now.
But for the rest I could test out to flash the factory images. But, first I have to get my adb/fastboot drivers working again *sigh*
Sent from my A0001 using Tapatalk

JustRamon said:
I meant the charging animation outside the rom. Normally its a big battery with red/green filling, but for me its just a small white battery now.
But for the rest I could test out to flash the factory images. But, first I have to get my adb/fastboot drivers working again *sigh*
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok, probably should have specified that in the OP. Flashing the stock images is your best bet, so get those drivers sorted out (or use a Linux machine, no drivers required) and you should be able to fix it.

Heisenberg said:
Ok, probably should have specified that in the OP. Flashing the stock images is your best bet, so get those drivers sorted out (or use a Linux machine, no drivers required) and you should be able to fix it.
Click to expand...
Click to collapse
That's a good idea. My Elementary dualboot can help me
I knew it was handy to have that...
Sent from my A0001 using Tapatalk

Heisenberg said:
Ok, probably should have specified that in the OP. Flashing the stock images is your best bet, so get those drivers sorted out (or use a Linux machine, no drivers required) and you should be able to fix it.
Click to expand...
Click to collapse
Can I just search for a OnePlus One boot.img and flash it? I thought it changed during upgrade to lollipop, and I would like to keep my rom if possible
If not so, did someone provide a oneplus one lollipop boot.img, and will it just work with my (allready flashed ofcourse) CyanogenMod nightlies?

JustRamon said:
Can I just search for a OnePlus One boot.img and flash it? I thought it changed during upgrade to lollipop, and I would like to keep my rom if possible
If not so, did someone provide a oneplus one lollipop boot.img, and will it just work with my (allready flashed ofcourse) CyanogenMod nightlies?
Click to expand...
Click to collapse
You need to flash tire appropriate boot.img, you can just extract it from the ROM zip.

Heisenberg said:
You need to flash tire appropriate boot.img, you can just extract it from the ROM zip.
Click to expand...
Click to collapse
Which ROM zip? The Cyanogen 12S one? And can I use flashify to make things easier?
Sent from my A0001 using Tapatalk

JustRamon said:
Which ROM zip? The Cyanogen 12S one? And can I use flashify to make things easier?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Aren't you on a nightly? You need to flash the appropriate boot.img for the ROM you're currently on.

Heisenberg said:
Aren't you on a nightly? You need to flash the appropriate boot.img for the ROM you're currently on.
Click to expand...
Click to collapse
Is it included in those zips? Why is it in there and isn't it automatically flashed when installing it?
Sent from my A0001 using Tapatalk

JustRamon said:
Is it included in those zips? Why is it in there and isn't it automatically flashed when installing it?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yes, it is included in those zips, and it is flashed automatically when you flash the ROM. The boot.img is the kernel, without flashing the kernel the phone wouldn't even boot. This is why I've been telling you that I don't think it's the boot.img that's causing your problem, and why I suggested you flash the stock images with fastboot. I say these things for a reason.

Heisenberg said:
Yes, it is included in those zips, and it is flashed automatically when you flash the ROM. The boot.img is the kernel, without flashing the kernel the phone wouldn't even boot. This is why I've been telling you that I don't think it's the boot.img that's causing your problem, and why I suggested you flash the stock images with fastboot. I say these things for a reason.
Click to expand...
Click to collapse
What controls the outside-rom charging animation then? Or did TWRP or the Nightlies change it?
Edit: After some searching I found out it's part of the bootloader. Something I've never messed with!
Sent from my A0001 using Tapatalk