Develop Bugs

Unable to revert to stock rom =[

I was messing around with ROM's one day and saw one that said, "Flash to 1.47 without having to reroot" or something along those lines. I tried it and it worked perfectly. Today I tried to undo the root and flash back to stock using the "[How To] [FIXED!!] Unroot and return to stock" post on Android Central forums.
However, halfway through the update, it fails. I want to return back to stock so I can flash the new Froyo update that is out but I don't know what I did so nothing will update.
I even tried to update directly to Froyo. No go.
I did a NAND restore to my 1.32 build. Still gives me an error.
Is there a way to go back to the Stock bootloader and stock recovery? Maybe that might help?
If there is any other information I can give please let me know.

sekigah84 said:
I was messing around with ROM's one day and saw one that said, "Flash to 1.47 without having to reroot" or something along those lines. I tried it and it worked perfectly. Today I tried to undo the root and flash back to stock using the "[How To] [FIXED!!] Unroot and return to stock" post on Android Central forums.
However, halfway through the update, it fails. I want to return back to stock so I can flash the new Froyo update that is out but I don't know what I did so nothing will update.
I even tried to update directly to Froyo. No go.
I did a NAND restore to my 1.32 build. Still gives me an error.
Is there a way to go back to the Stock bootloader and stock recovery? Maybe that might help?
If there is any other information I can give please let me know.
Click to expand...
Click to collapse
this should be q and a!
turn your phone on while holding down on volume.
can you see option for recovery? what happens when you click it?

message for noobs: NEVER try to unroot to upgrade if you want to keep root. always WAIT until someone posts a ROOTED version for your eager beaver.
now why were you trying to unroot?
when in doubt, you can always start over by following instructions here.

Sorry. Didn't know about the Q+A thing. Guess I need a mod to move it.
I hit recovery and it says:
Android system recover
use vol-keys to nvaigate. power-key to select
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Flash zip from sdcard
-Wipe
-Partition sdcard
-Other
-Power off

sekigah84 said:
Sorry. Didn't know about the Q+A thing. Guess I need a mod to move it.
I hit recovery and it says:
Android system recover
use vol-keys to nvaigate. power-key to select
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Flash zip from sdcard
-Wipe
-Partition sdcard
-Other
-Power off
Click to expand...
Click to collapse
Ok, things aren't totally screwed yet.
Go here:
http://forum.xda-developers.com/showthread.php?t=740667
Follow the instructions and install a rooted version of Froyo. Why go back to stock? This is exactly what you'd be installing with stock, but you have root.

tatnai said:
message for noobs: NEVER try to unroot to upgrade if you want to keep root. always WAIT until someone posts a ROOTED version for your eager beaver.
now why were you trying to unroot?
Click to expand...
Click to collapse
I wanted to undo it so I can test the stock HTC non-rooted rom. Which didn't flash over my rooted 1.47 build. So I thought that if I revert to stock it should flash. Thats where I'm stuck at currently ><
I did a data, cache, dalvik wipe. Restored back to a 1.32. Got the OTA update. Downloaded and tried to install and got the following error:
Build: RA-evo-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (56 files)
E: Verification failed
Installation aborted.
I also can't use the RUU to get back to 1.32 or 1.47

Saturn2K said:
Ok, things aren't totally screwed yet.
Follow the instructions and install a rooted version of Froyo. Why go back to stock? This is exactly what you'd be installing with stock, but you have root.
Click to expand...
Click to collapse
Will do. Sorry for the slight lag in replies. 5 minute newbie limit on posts;
I'll try this and see if it works.

sekigah84 said:
I wanted to undo it so I can test the stock HTC non-rooted rom. Which didn't flash over my rooted 1.47 build. So I thought that if I revert to stock it should flash. Thats where I'm stuck at currently ><
I did a data, cache, dalvik wipe. Restored back to a 1.32. Got the OTA update. Downloaded and tried to install and got the following error:
Build: RA-evo-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (56 files)
E: Verification failed
Installation aborted.
I also can't use the RUU to get back to 1.32 or 1.47
Click to expand...
Click to collapse
IF you manage to get back to stock and IF you install the unrooted HTC OTA, you will lose root until/unless the devs come up with a way to root it. Is that what you're actually trying to do?

smw6180 said:
IF you manage to get back to stock and IF you install the unrooted HTC OTA, you will lose root until/unless the devs come up with a way to root it. Is that what you're actually trying to do?
Click to expand...
Click to collapse
Yep. I want full stock.

I just want to know that I will be able to return to stock for repair purposes. Its scaring the crap out of me atm not being able to return to stock lol

[Q] Trouble with updating OTA to JB

I'm currently using the stock rom from Google (4.0.4) after updating it from 4.0.1 which originally shipped with my device (manually, not OTA). Just yesterday I decided to update my phone to JB through the OTA update. It downloads perfectly fine but when it reboots into the installation, I get the error with the android mascot and red exclamation mark.
-- Install /cache ...
Finding update package ...
Opening update package ...
Verifying update package ...
Installing update ...
Verifying current system ...
assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/radio:12583168:8b7209e8c3a6d73254ad92069aabe693beffd6bd:12583168:47b1799049e32ef2c0746ca716f5277a83768b96")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I'm pretty sure it manages to download perfectly fine since the file is still in my cache (filename is f946a4120eb1.signed-yakju-JR003C-from-IMM761.f946a412.zip) Anyone able to help me with this?

spaceinvad3rs said:
I'm currently using the stock rom from Google (4.0.4) after updating it from 4.0.1 which originally shipped with my device (manually, not OTA). Just yesterday I decided to update my phone to JB through the OTA update. It downloads perfectly fine but when it reboots into the installation, I get the error with the android mascot and red exclamation mark.
I'm pretty sure it manages to download perfectly fine since the file is still in my cache (filename is f946a4120eb1.signed-yakju-JR003C-from-IMM761.f946a412.zip) Anyone able to help me with this?
Click to expand...
Click to collapse
You do not have the XXLA2 radio flashed. You need to flash that before applying the update.

Thanks for that. I've also got another question. I currently can't access clockwork mod through the recovery menu, after updating it to 4.0.4 I wasn't able to access it anymore. I've tried the rom manager from the play store but it says something that I don't have permission. I think I forgot to install the super user when I initially installed the update to 4.0.4.

I agree, you have to be careful with each rom's compatibility. 4.0.4 brought with it new radios which I believe most if not all jb roms are based on. You can flash the new radios after rooting and unlocking the device. If you manually root the phone, you'll know if you successfully pushed su to your sd card.
Sent from my Galaxy Nexus using xda app-developers app

spaceinvad3rs said:
Thanks for that. I've also got another question. I currently can't access clockwork mod through the recovery menu, after updating it to 4.0.4 I wasn't able to access it anymore. I've tried the rom manager from the play store but it says something that I don't have permission. I think I forgot to install the super user when I initially installed the update to 4.0.4.
Click to expand...
Click to collapse
1) every ota update disables root access.
2) every ota update places two files on your device that re-flash the stock recovery every time you boot your phone.
3) the android laying on its back with the exclamation point IS the stock recovery.
4) you need to flash cwm, flash the su package, then rename/delete this file: /system/etc/install-recovery.sh and you are all set.
Sent from my Galaxy Nexus using Tapatalk 2

OTA 4.1 update from preview build

Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.

Sgtpanda said:
Basically I have the preview build of Jelly Bean (JRN84D) but it keeps alerting me to install the OTA version which fails, I know there are lots of threads about this but I can't seem to find the answer in them, I tried flashing the stock recovery but when I try to boot into it I get the Red exclamation mark and can't do anything with the volume or power keys, this is the same exclamation mark I get when trying to install the update.
I think the recovery file may be corrupt, is this the key to getting OTA update? Also my radio is XXLF1 if that helps. Thanks for any help offered, I watched the video and everybody hates noobs but I tried the solutions in other posts and it seems to have got worse.
EDIT: I can access recovery now, but the update still fails.
Click to expand...
Click to collapse
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.

dnlsmy said:
Flash the Stock Recovery/Radio/Bootloader for Takju from the hosted Google Factory Images through Fastboot. It won't erase your data/apps. For the Recovery, you will need to extract it manually from the image while the bootloader and radio should be standalone.
Click to expand...
Click to collapse
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.

Sgtpanda said:
When you say the Takju Google Factory Image do you mean the 4.0.4 takju image? as that's the only one I can find on their site.
Thanks.
Click to expand...
Click to collapse
Yes.
Sent from my Galaxy Nexus using xda app-developers app

wilsonlam97 said:
Yes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.

Sgtpanda said:
Flashed the radio, bootloader and recovery from it and it still doesn't work, if I press up and power button after it fails it gives me a status 7 error, might just flash stock and unroot if there's no other way.
Click to expand...
Click to collapse
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
What is the error?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.

Any ideas or am I screwed and should go ahead and try flash stock rom and unroot? Will that even help?

Sgtpanda said:
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.

efrant said:
What's the FULL error.
Also, are you using a recovery that is different from CWM 5.5.0.2 or 5.5.0.4? If so, get rid of it, and use one of those.
Click to expand...
Click to collapse
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.

Sgtpanda said:
I'm using stock recovery because everything I've read says to use stock if you want to accept OTA updates, the full error is:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349","512784ba869d55f3cf2d291baaa5f6a0aa90b960")
E: Error in /cache/edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...

efrant said:
Where did you get the preview build? Based on that error, it would seem to me like you flashed a non-stock version of JB 4.1 like bigxie's ROM. If that is the case, you need to flash a stock ROM before any update can be applied...
Click to expand...
Click to collapse
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?

Sgtpanda said:
Now that you've mentioned that name, yes that's the ROM I got, I'm gonna go ahead and guess there's no way to return to stock without wiping data is there?
Click to expand...
Click to collapse
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.

efrant said:
Maybe. You can try this without wiping and see if it works. Then apply the JRO03C-from-JRN84D update form here.
Click to expand...
Click to collapse
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?

Sgtpanda said:
And if I do that then will I be able to accept any future OTA updates through android and have it update automatically without having to flash the updates myself?
Click to expand...
Click to collapse
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.

efrant said:
If you follow method 2, then yes, you will be able to automatically accept OTA updates and have it install automatically. BUT, you MAY need to do the first one (i.e., to JRO03C) manually (if you don't get it shortly after you flash JRN84D). After that, you will be all set for the next update.
Click to expand...
Click to collapse
I'll try it, thanks for the help.
EDIT: It worked! Did it without wiping and it accepted the OTA without needing to do it manually, once again thanks so much for helping!

[Q] failed to update rooted nexus 7 2013 from 4.4.3 to 4.4.4

Hi everyone,
I posted this thread in General Discussion Q&A and then found this forum, so I posted once again in hoping to get some solution.
I have updated my rooted Nexus 7 2013-LTE using the method described here from 4.4.2 to 4.4.3 succesfully:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html
I used SuperSU and Xposed framework was temporarily uninstalled. However, when I tried the same procedure to update from 4.4.3 to 4.4.4, following errors are appearing:
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/0c3dd9bfb71f2b8437be322e6cab5832ce2b4d35.signed-razorg-KTU84P-from-KTU84L.0c3dd9bf.zip
(Status 7)
Installation aborted.
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all

hood2ts said:
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all
Click to expand...
Click to collapse
Did you try uninstalling stick mount first? That should put the original debuggerd back.

Did you flash back to the stock recovery before accepting the OTA?

meekrawb said:
Did you try uninstalling stick mount first? That should put the original debuggerd back.
Click to expand...
Click to collapse
I tried uninstalling stickmount, but the debuggerd file is still unchanged. The OTA update is still failed. Anyway, thank u for suggesting an idea.

nhizzat said:
Did you flash back to the stock recovery before accepting the OTA?
Click to expand...
Click to collapse
Nice thing to update using method described in:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html,
is that you move forward with what you have. Will try flashing back to the stock revovery if that simpler method not working .

Not sure why anybody would make a guide on how to update without losing root. Worried about losing data and settings? Sure. Worried about losing root? Never.
If you want simple, you can either use adb sideload with the stock recovery or flash the OTA in a custom recovery like you would any other zip file. If you find you don't have root, flash SuperSU.zip again.

Finally, I used NRT to flash to 4.4.4 using system image with option not to wipe data. Many thanks to nhizzat and meekrawb.

Error sideloading OTA

I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
Verifying update package...
Installing update...
M60QCT.02.003.021
Verifying current system...
Package expects build fingerprint of htc/pmewl_00617/htcpmewl:6.0.1/MMB29M/761759.1:user/release-keys or htc/pmewl_00617/htc_pmewl:6.0.1/MMB29M/787791.1:user/release-keys; this device has htc/pmewl_00617/htcpmewl:6.0.1/MMB29M/748430.5:user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???

nullo said:
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
Click to expand...
Click to collapse
Alrighty seems like I fixed it! I ended up flashing the EraseDevInfo zip in http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Not sure how I did the first update without flashing it that file last time?

nullo said:
Alrighty seems like I fixed it! I ended up flashing the EraseDevInfo zip in http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
Not sure how I did the first update without flashing it that file last time?
Click to expand...
Click to collapse
Glad that worked for you. You don't always trip the verity mode check when you modify system. It seems to only occur when you modify system AND use a 100% stock kernel. So it makes sense that ota will work sometimes and not others.

Edit: wrong thread

nullo said:
I'm trying to update to 1.91.617.1 from 1.80.617.1 and getting an error. I'm s-on, removed SuperSU, downloaded the stock 1.80 TWRP system image, mounted system in TWRP (checked read only box), applied the stock 1.80 TWRP image and then flashed the stock 1.53.617.5 image.
When I go to sideload the 1.91.617.1 OTA I get the following
What do I need to do to get MMB29M/748430.5 to MMB29M/761759.1 ???
Click to expand...
Click to collapse
Do you mind me asking how I can manually flash 1.82.605.6 to my device? I'm s-off/rooted, bootloader locked, flashed stock recovery (thinking I could get OTA, I was wrong). Ideally I'd like to not lose data, but all I'm really worried about is not losing s-off or bricking my phone. It seems like this must be common knowledge, because any time firmware is posted or linked with a ROM there are no instructions on how to actually install it. I would really appreciate some help, I'm stuck on 1.19.605.22!