The most peculiar thing happened after I applied today's JWR66Y update.
Prior to the update my GNex was running stock 4.3, rooted with SuperSU, and TWRP recovery was installed. So I flashed back to stock recovery and used the SuperSU app option for "Full unroot" in preparation to apply the OTA update.
Instead of letting the system do it, I copied the downloaded zip file from cache to my PC and used ADB sideload. Then I used fastboot to flash TWRP. From TWRP I flashed UPDATE-SuperSU-v1.51.zip
Here's the peculiar part. When I rebooted I didn't have root. The SuperSU app appeared as installed under Apps, but there was no icon in the app drawer. So I went to Google Play and installed SuperSU from there. After that everything was back to normal.
I never saw this happen before. Out of curiosity does anyone know why? I'm thankful it was so simple to fix but I'm scratching my head.
Sent from my Nexus 7 using xda app-developers app
Mine did something strange as well, but different than yours. I'm also running stock 4.3, rooted with SuperSU, and TWRP. For me it downloaded and installed the update then booted into TWRP recovery. After that finished doing something automatically it asked if I wanted to fix root, which I did. The phone booted back up and it's back on JWR66V and when I check for updates it says there aren't any. Still have root though.
Raugturi said:
Mine did something strange as well, but different than yours. I'm also running stock 4.3, rooted with SuperSU, and TWRP. For me it downloaded and installed the update then booted into TWRP recovery. After that finished doing something automatically it asked if I wanted to fix root, which I did. The phone booted back up and it's back on JWR66V and when I check for updates it says there aren't any. Still have root though.
Click to expand...
Click to collapse
Put stock recovery and the update should work. Then you can put TWRP back.
unsought spendsP
sordna said:
Put stock recovery and the update should work. Then you can put TWRP back.
Click to expand...
Click to collapse
Thanks. I'll try that once I can find somewhere to download the update (or whenever it decides to show up again.
Raugturi said:
Thanks. I'll try that once I can find somewhere to download the update (or whenever it decides to show up again.
Click to expand...
Click to collapse
Don't answer "Yes" to that question. Then flash latest compatible supersu. Do you have root then?
a manta sent this.
Raugturi said:
Thanks. I'll try that once I can find somewhere to download the update (or whenever it decides to show up again.
Click to expand...
Click to collapse
You can download the update zip file from here:
http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
I just did it for my Nexus 7, followed the same steps described for my GNex, and the same thing happened haha. Oh well, easy enough to fix but I'm still wondering why flashing the UPDATE-SuperSU-v1.51.zip didn't install the app.
Sent from my Nexus 7 using xda app-developers app
sordna said:
Put stock recovery and the update should work. Then you can put TWRP back.
Click to expand...
Click to collapse
That was always enough for me with prior updates, too (before 4.3) but this update couldn't be applied without unrooting. It threw a Status 7 error and "Installation aborted". The moment I unrooted, the update installed without issue.
Sent from my Nexus 7 using xda app-developers app
beekay201 said:
Don't answer "Yes" to that question. Then flash latest compatible supersu. Do you have root then?
a manta sent this.
Click to expand...
Click to collapse
Did you mean to quote someone else?
Please if i may ask...is twrp better than cwm? What r d pros n cons
Sent from my Galaxy Nexus using Tapatalk 4
Another question, i don't have the stock recovery. img file from jwr66v now google images only show jwr66y..will extracting recovery.img from this to flash before update work? Since I'm still on jwr66v? Or csn u pls upload the recovery. img for gsm yakju. Thanks
Sent from my Galaxy Nexus using Tapatalk 4
David said:
Another question, i don't have the stock recovery. img file from jwr66v now google images only show jwr66y..will extracting recovery.img from this to flash before update work? Since I'm still on jwr66v? Or csn u pls upload the recovery. img for gsm yakju. Thanks
Click to expand...
Click to collapse
Instead of accepting the OTA, install the zip file efrant posted here:
http://forum.xda-developers.com/showpost.php?p=44886292&postcount=102
it has the recovery dependency removed, so you can keep your custom recovery. Copy the zip to your sdcard, rename to update.zip and install via either CWM or TWRP.
Thanks.. Will do that and give a report. :thumbup::thumbup:
Sent from my Galaxy Nexus using Tapatalk 4
I downloaded the file..from the link above, renamed to update.zip, got into cwm. Hit apply...didn't work..gave a systsm 7 error..somethijg about build.prop and a directory/file not found in d package
Update:
Then copied my ota from cacbe n flashed thru cwm, toggled file verification off. It worked a bit then system 7 again but this time rebioted like someone mentioned above as though it was fully updated.. Ie upgrading apps etc..but after all it was stil jwr66v. So now i need d stock recovery.img file i guess.. Can someone please upload
Update 2:
As many have already stated...i went into supersu app..full unroot, rebooted into cwm using the original ota from cache( which i had copied into clockwork folder) flashed it successfully, then flashed supersu 1.51 which i also put in d above folder. Rebooted and now I'm rooted on jrw66y..last thing was to install the supersu app from playstore. Hope it helps
Sent from my Galaxy Nexus using Tapatalk 4
Raugturi said:
Mine did something strange as well, but different than yours. I'm also running stock 4.3, rooted with SuperSU, and TWRP. For me it downloaded and installed the update then booted into TWRP recovery. After that finished doing something automatically it asked if I wanted to fix root, which I did. The phone booted back up and it's back on JWR66V and when I check for updates it says there aren't any. Still have root though.
Click to expand...
Click to collapse
Raugturi said:
Did you mean to quote someone else?
Click to expand...
Click to collapse
Nop, quoted the "wrong" post.
a maguro sent this.
David said:
...then flashed supersu 1.51 which i also put in d above folder. Rebooted and now I'm rooted on jrw66y..last thing was to install the supersu app from playstore.
Click to expand...
Click to collapse
Which brings me back to my original question. Why does the SuperSU app have to be installed from Google Play if UPDATE-SuperSU-v1.51.zip is installed from recovery? All of the system su files are there, just not the app. Isn't this a bit peculiar?
Sent from my Nexus 7 using xda app-developers app
Yeah
Sent from my Galaxy Nexus using Tapatalk 4
I got the OTA. I did "full unroot" in SuperSU. Isntalled the OTA, TWPM automatically installed the update.zip.
But now my device in unrooted and when i want to reboot into recovery in order to flash SuperSU i get the android logo with the exclamation mark! What to do?
plaktoets said:
I got the OTA. I did "full unroot" in SuperSU. Isntalled the OTA, TWPM automatically installed the update.zip.
But now my device in unrooted and when i want to reboot into recovery in order to flash SuperSU i get the android logo with the exclamation mark! What to do?
Click to expand...
Click to collapse
reflash twrp in fastboot.
i bet you used a toolkit to root didnt you?
Zepius said:
reflash twrp in fastboot.
i bet you used a toolkit to root didnt you?
Click to expand...
Click to collapse
No, initially I rooted by flashing supersu.
Flashing TWRP did the trick, thanks.
Nexus 4 did the same
CatThief said:
The most peculiar thing happened after I applied today's JWR66Y update.
Prior to the update my GNex was running stock 4.3, rooted with SuperSU, and TWRP recovery was installed. So I flashed back to stock recovery and used the SuperSU app option for "Full unroot" in preparation to apply the OTA update.
Instead of letting the system do it, I copied the downloaded zip file from cache to my PC and used ADB sideload. Then I used fastboot to flash TWRP. From TWRP I flashed UPDATE-SuperSU-v1.51.zip
Here's the peculiar part. When I rebooted I didn't have root. The SuperSU app appeared as installed under Apps, but there was no icon in the app drawer. So I went to Google Play and installed SuperSU from there. After that everything was back to normal.
I never saw this happen before. Out of curiosity does anyone know why? I'm thankful it was so simple to fix but I'm scratching my head.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have a Nexus 4 and my device did exactly the same after updating from 4.2.2 to 4.3(jwr66v).. Do not know the reason.. But after downloading the app from Play Store, things are working fine.. I suspect the Full Unroot option in SuperSu to be the culprit..
Related
If you have any questions, concerns or problems, please post in the CDMA post because I will no longer be checking here.
theboo7 said:
This is a guide on how to get ClockWorkMod onto your LTE Galaxy Nexus through Rom Manager
Go to market, search "Clockworkmod"
Install Rom Manager*
Open up Rom Manager and select "Flash ClockworkMod Recovery"
A pop-up will come up called "Confirm Phone Model," of course choose "Google Galaxy Nexus CDMA"
Now let it install etc, then with a File Manager** with SU access, Go to system, click "Mount R/W"(if using Root Explorer) and then scroll down until you see "recovery-from-boot.p" and rename it to "recovery-from-boot.p.bak"
Close out off your File Manager and go to Rom Manager and select "Reboot into Recovery"
There you go
You should be able to boot into CWM
* Free version works
**I used Root Explorer
Click to expand...
Click to collapse
For starters that file doesnt exist under the directory "system"
jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
By "that file" I'm assuming you are referring to "recovery-from-boot.p" ?
jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.
staticx57 said:
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.
Click to expand...
Click to collapse
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw
theboo7 said:
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw
Click to expand...
Click to collapse
I had to do this same thing on stock to keep the stock recovery from restoring.
jermaine151 said:
I had to do this same thing on stock to keep the stock recovery from restoring.
Click to expand...
Click to collapse
Yeah it's a known bug, that's hopefully getting worked on.
Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk
dc iz 2 legit said:
Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Then you would follow the steps in the OP
What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?
Xirix12 said:
What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?
Click to expand...
Click to collapse
Flashing through ROM Manager is just a simpler way to get CWM. And I'm not sure why you would have gotten the red triangle, unless you didn't rename/delete the file in system. And I haven't heard anyone say the couldn't do anything in recovery, so I'm not sure what the problem is there.
When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App
civicsisedan said:
When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM
theboo7 said:
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM
Click to expand...
Click to collapse
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App
civicsisedan said:
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Okay, so glad that you got it sorted out
Sent from my Galaxy Nexus using XDA App
this step by step process was incredibly easy. thank you!!!
reflekt2099 said:
this step by step process was incredibly easy. thank you!!!
Click to expand...
Click to collapse
Your welcome
Sent from my Galaxy Nexus using XDA App
Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk
Xirix12 said:
Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yeah, that file can cause problems with CWM on LTE, although it's a quick fix, I'm sure it's being worked on for future editions. And since you've been able to flash things, when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.
theboo7 said:
when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.
Click to expand...
Click to collapse
Same here. You gotta go slow. I selected the wrong option many times.
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Your phone is rooted? If yes you can't install OTA updates
I'm rooted yes. So what do I do? Unroot?
Sent from my Galaxy Nexus using xda app-developers app
htc_woe_is_me said:
I started doing the Google framework force stop and clear cache today while on wifi and was prompted after 5 or 6 tries. It downloaded, verified download, rebooted and TRIED to install. About 15% through, it said untrusted zip and cwm screen popped up top and asked 'install untrusted zip?' Of course I hit yes.. why isn't it trusted? Its straight from the carrier. Anyway it immediately said installation aborted. I repeated this process again and got the same results. Please someone help. Now that JB is finally here my phone won't take it???
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
polimeno said:
Your phone is rooted? If yes you can't install OTA updates
Click to expand...
Click to collapse
Not true. Root makes no difference.
efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
So either way I will lose all my settings, home screens and what not?
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
efrant said:
If you have CWM flashed, you have to manually flash the update -- it won't install over-the-air. If you want to install it over-the-air, flash back the stock recovery then accept the update.
Not true. Root makes no difference.
Click to expand...
Click to collapse
It's exact. But root can only be done if you have bootloader unlocked, and with unlocked bootloader can not install OTA updates
htc_woe_is_me said:
So either way I will lose all my settings, home screens and what not?
Click to expand...
Click to collapse
No, updating using an OTA update file will NOT make you lose anything.
htc_woe_is_me said:
I used Galaxy Nexus Toolkit to do all of my rooting, installing CWM and all-- is there a way to accomplish what I need to on there?
Click to expand...
Click to collapse
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
efrant said:
No, updating using an OTA update file will NOT make you lose anything.
I can't help you out with the toolkit, but have a look at my signature for some useful links on doing things without a toolkit.
Click to expand...
Click to collapse
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
htc_woe_is_me said:
OK, so the best thing would be to flash the stock recovery? Sorry for all the questions, and I really appreciate all your help. I swear I used to know how to do this crap on my Dinc, but it's been years since I did all that.
Click to expand...
Click to collapse
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
efrant said:
Go to the Google page with all the images and download the mysid IMM76K image, extract the recovery.img from within, and flash it using fastboot: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
htc_woe_is_me said:
OK, I'm trying this now... I downloaded the images from Google.. extracted its contents... found the recovery image file. Do I need to put that file into a zip file?
Click to expand...
Click to collapse
Gnex Toolkit wasn't working because of some missing file... re-installed it and flashed the stock recovery via Gnex Toolkit (I think). Is there a way to check which recovery is running? Anyway, if it is indeed stock, I just got prompted again for the OTA JB update.. it's installing now.... fingers crossed!!!
..OK so now it rebooted... started installing, got about halfway through.. paused, then it went to the stock recovery screen and stayed with a red triangle around an exclamation point! What is happening here?!
I have now re-locked the bootloader and received the prompt for OTA again....
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
htc_woe_is_me said:
Still won't work for me. I've tried even flashing the stock image and it won't install at all. Actually nothing is installing.
I've never done anything to the phone besides unlocking the BL and rooting and switching to CWM. It seems to have something to do with the SD mount.. nut then again I have no idea.
Where's all the Android gurus at?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Follow the instructions in the "update" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Guys i am having this EXACT problem, except on a S4 (I337M to be exact)
Here is my thread with the details
http://forums.androidcentral.com/as...t-update-ota-failure-using-triangle-away.html
But basically, im just wondering how i can get stock recovery back and get this ota to work!!!
Thanks!
Can not for the life of me get this too boot into CWM.
I have used CF auto root and confirmed I have root access, I have deleted the recovery file in system/etc and no matter what I do, CWM just won't boot, it just keeps booting into android recovery. I even tried taking the battery out as soon as CWM is finished to prevent a boot into the os and then trying to boot into it, still nada.
Is there something I am missing?
Are you already rooted or are you trying to install CWM first and then root?
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
Sorry just re-read lol. Why don't you use TWRP? Personally I like that recovery better. Since you're already rooted just install goomanager and install it through there. Or you could also install CWM through rom manager.
Sent from my SGH-M919 using xda app-developers app
marcoxx626 said:
Are you already rooted or are you trying to install CWM first and then root?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Already rooted, I read a guide that says delete install.recovery.sh, which I thought I did but it is not actually deleting, says it is but just does not disappear? wtf
EDIT: just seen your edit, I used clockwork before on my DHD, that is why i chose this. Will try it via ROM manager, if all fails I shall try your recovery choice, TY.
Ok this is weird, root checker confirms I have root, I can grant things root access (rom manager, goomanager) but they always fail when setting the permissions, also can't delete that file in system/etc...so my device is like half rooted or something? Any ideas?
Gibbo3771 said:
Ok this is weird, root checker confirms I have root, I can grant things root access (rom manager, goomanager) but they always fail when setting the permissions, also can't delete that file in system/etc...so my device is like half rooted or something? Any ideas?
Click to expand...
Click to collapse
Why are you deleting system files? I've never had to delete anything when rooting or flashing a recovery.
Sent from my SGH-M919 using xda app-developers app
marcoxx626 said:
Why are you deleting system files? I've never had to delete anything when rooting or flashing a recovery.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
install.recovery.sh installed reflashes the recovery system to the android default, I am trying to flash to clockwordmod but it just keeps booting into android recovery no matter what i do, root checker confirms i am rooted.
I am just stumped on what to do....i can't get any custom recovery on this.
Goomanager says it can not find one for my phone and rom manager says the s4 is not even supported, all apps are up to date. what gives?
Gibbo3771 said:
install.recovery.sh installed reflashes the recovery system to the android default, I am trying to flash to clockwordmod but it just keeps booting into android recovery no matter what i do, root checker confirms i am rooted.
I am just stumped on what to do....i can't get any custom recovery on this.
Goomanager says it can not find one for my phone and rom manager says the s4 is not even supported, all apps are up to date. what gives?
Click to expand...
Click to collapse
try TWRP through goomanager. its better imo, and installed in seconds with no problem. didnt have to delete anything either.
oh and btw, if this is a gt-i9505 related problem, youre in the wrong forums... might help more over in the gt-i9505 forums
The Illest 619 said:
try TWRP through goomanager. its better imo, and installed in seconds with no problem. didnt have to delete anything either.
oh and btw, if this is a gt-i9505 related problem, youre in the wrong forums... might help more over in the gt-i9505 forums
Click to expand...
Click to collapse
nah goomanager/rom manager was not installing either CWM or TWRP, however i done a factory reset of the phone, redone the rooting process and installed TWRP manually, fixed now.
Where is this mhystical forum section?
Gibbo3771 said:
nah goomanager/rom manager was not installing either CWM or TWRP, however i done a factory reset of the phone, redone the rooting process and installed TWRP manually, fixed now.
Where is this mhystical forum section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2162
thats for the correct version of your phone
The Illest 619 said:
http://forum.xda-developers.com/forumdisplay.php?f=2162
thats for the correct version of your phone
Click to expand...
Click to collapse
Probably a stupid question but I guess the roms in this section will not work with my phone? the choice here compared to there is ehm....limited hehe.
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
roulyz said:
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Click to expand...
Click to collapse
You will have to abd sideload the update. Do a search and you will find how to do it.
nrage23 said:
You will have to abd sideload the update. Do a search and you will find how to do it.
Click to expand...
Click to collapse
Thanks a ton - I thought I was going to have to do something a hell of a lot more time-consuming than a sideload.
And for some reason, TWRP isn't letting me sideload. ADB won't detect the tablet to allow it.
EDIT: Nevermind - evidently it was something very recent that got messed up - I returned to the backup I made after getting 4.4.1 loaded, and it flashed without issue. Yay.
destruya1 said:
Thanks a ton - I thought I was going to have to do something a hell of a lot more time-consuming than a sideload.
And for some reason, TWRP isn't letting me sideload. ADB won't detect the tablet to allow it.
EDIT: Nevermind - evidently it was something very recent that got messed up - I returned to the backup I made after getting 4.4.1 loaded, and it flashed without issue. Yay.
Click to expand...
Click to collapse
Glad it worked out.
nrage23 said:
You will have to abd sideload the update. Do a search and you will find how to do it.
Click to expand...
Click to collapse
I have already adb sideload the update but it's fail again
Search on xda for debuggerd nexus 7 4.4
Somewhere there is a zip with the stock one
Sent from my HTCSensation using xda app-developers app
---------- Post added at 02:01 PM ---------- Previous post was at 01:57 PM ----------
http://forum.xda-developers.com/showthread.php?p=47640397
Sent from my HTCSensation using xda app-developers app
roulyz said:
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Click to expand...
Click to collapse
You need to take the device back completely to stock for the update to work.
Wugs Toolkit is an incredible tool to do so.
http://www.wugfresh.com/nrt/
No, that will mean loss of time. If you use wug toolkit you can extract system.img from stock image and then flash it on your device, so that you won't have to erase anything. Anyway if debuggerd zip worked there's no need to do anything else
Sent from my Nexus 7 using xda app-developers app
I was able to update my rooted Nexus 7 with custom recovery. I just had to revert my adblocking hosts file in adaway. It overwrote my recovery and lost root, so I just flashed recovery again and rerooted.
Sent from my SGH-I747M using xda app-developers app
I flashed my Nexus 7 2013 4.4 with Stock Rooted ROM - Official 4.4.2 Google OTA, and it work. All my data have been there.:victory:
http://forum.xda-developers.com/showthread.php?t=2563017
roulyz said:
I flashed my Nexus 7 2013 4.4 with Stock Rooted ROM - Official 4.4.2 Google OTA, and it work. All my data have been there.:victory:
http://forum.xda-developers.com/showthread.php?t=2563017
Click to expand...
Click to collapse
I did the same, and it went OK. For my data I restored it from the backup.
BullSpit said:
You need to take the device back completely to stock for the update to work.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
No you don't, flashing system.img and boot.img before applying the OTA patch would do the trick, without losing your data.
eBug said:
No you don't, flashing system.img and boot.img before applying the OTA patch would do the trick, without losing your data.
Click to expand...
Click to collapse
Cool, good to know. Many thanks! I stand corrected.
I'm currently running the stock Rom with build E98020h. I have successfully achieved root access and have verified it through several apps, and also have supersu installed and seemingly operating fine. I have tried using the 'g pro kitkat recovery' app to flash the recovery, and also freegee but freegee at the opening screen says my device is unsupported. When i go into rom manager v5.5.3.7 and try install a custom rom or even just tap boot to recovery i get an error at the loading screen with the LG logo and it sits there. Am i doing something wrong or is the 20h update keeping me from being to successfully reach recovery? Any insight is greatly appreciated.
Sent from my LG-E980 using XDA Free mobile app
Same method worked on my 20g....not sure about 20h
Sent from my LG-E980 using XDA Free mobile app
aidenthefirst said:
I'm currently running the stock Rom with build E98020h. I have successfully achieved root access and have verified it through several apps, and also have supersu installed and seemingly operating fine. I have tried using the 'g pro kitkat recovery' app to flash the recovery, and also freegee but freegee at the opening screen says my device is unsupported. When i go into rom manager v5.5.3.7 and try install a custom rom or even just tap boot to recovery i get an error at the loading screen with the LG logo and it sits there. Am i doing something wrong or is the 20h update keeping me from being to successfully reach recovery? Any insight is greatly appreciated.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
20h may be blocking you off...
You could try using LG Flash Tool to go back to stock 4.1.2 (E98010k) and then using FreeGee to bypass and go from there. But idk if that'll work.
aidenthefirst said:
I'm currently running the stock Rom with build E98020h. I have successfully achieved root access and have verified it through several apps, and also have supersu installed and seemingly operating fine. I have tried using the 'g pro kitkat recovery' app to flash the recovery, and also freegee but freegee at the opening screen says my device is unsupported. When i go into rom manager v5.5.3.7 and try install a custom rom or even just tap boot to recovery i get an error at the loading screen with the LG logo and it sits there. Am i doing something wrong or is the 20h update keeping me from being to successfully reach recovery? Any insight is greatly appreciated.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
aidenthefirst, or anyone else....
You ever figure out how to load recovery on the 20h update? Id also like to install CWM or TWRP without having to roll back to 20g.
Thanks.
Jasbo said:
aidenthefirst, or anyone else....
You ever figure out how to load recovery on the 20h update? Id also like to install CWM or TWRP without having to roll back to 20g.
Thanks.
Click to expand...
Click to collapse
I don't think that's possible. You're going to have to flash back to an older version using lg flash tools. If you need to back up anything like texts and contacts, use G Cloud. If you need game data/other data related to specific apps backed up, use Helium. If you're attached to stock try flashing a stock ROM, it will be very similar to your experience now. That'll ensure you get the latest KitKat and still get stock experience... you can always go AOSP too.
thanks... I was hoping to just not have to Flashtools my phone again =P and since its been a while since I checked the forums I wasnt sure if 20h was sorted out yet or not.
Jasbo said:
aidenthefirst, or anyone else....
You ever figure out how to load recovery on the 20h update? Id also like to install CWM or TWRP without having to roll back to 20g.
Thanks.
Click to expand...
Click to collapse
I found the way to do it without having to roll your system back to anything older than 20h. Let me type it all up And make sure I have the proper links and app names and will post in a bit
Sent from my LG-E980 using XDA Free mobile app
OK so after you achieve root access on your phone download the apk in the link below. Install it open it and run it. You should now be able to have full recovery access...
Sent from my LG-E980 using XDA Free mobile app
So apparently I haven't posted enough in threads to attach a link from outside this site. PM me for the link.
Sent from my LG-E980 using XDA Free mobile app
This is the link i found to download the app I used on my e98020h to unlock recovery. I hope it works as well for you all as it did for me.
https://drive.google.com/file/d/0B4vSbKccbcIOV1NjMDlqWUdmVm8/preview?pli=1
Sent from my LG-E980 using XDA Free mobile app
So I'm running into another problem and after a lot of 'googling' I can't find an answer. But running purely stock unrooted and my SD card reads and writes fine. Now that I have rooted and fully obtained recovery access my phone will not recognize much less use it. Any suggestions?
Sent from my LG-E980 using XDA Free mobile app
aidenthefirst said:
This is the link i found to download the app I used on my e98020h to unlock recovery. I hope it works as well for you all as it did for me.
https://drive.google.com/file/d/0B4vSbKccbcIOV1NjMDlqWUdmVm8/preview?pli=1
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I found this elsewhere trying to unlock my e980 that was on 20h when I got it.
OK so I found that G Pro KK recovery elsewhere and installed it but wasn't sure what to do from there.. Which option did you choose when running it? Flash recovery, reboot, or reboot recovery? I tried to reboot to recovery and I got into a CWM recovery, but at that point wasn't sure if I was really there or if I needed to flash the recovery from there or from the app.
I'm dying to get rid of the stock ROM on this thing but there are more steps involved than my previous devices.
Thanks!
volkey said:
I found this elsewhere trying to unlock my e980 that was on 20h when I got it.
OK so I found that G Pro KK recovery elsewhere and installed it but wasn't sure what to do from there.. Which option did you choose when running it? Flash recovery, reboot, or reboot recovery? I tried to reboot to recovery and I got into a CWM recovery, but at that point wasn't sure if I was really there or if I needed to flash the recovery from there or from the app.
I'm dying to get rid of the stock ROM on this thing but there are more steps involved than my previous devices.
Thanks!
Click to expand...
Click to collapse
All the APK does as I have found out is 'unlocks' the recovery access. After I ran that app I installed Freegee from the app store and installed the CMW recovery from there just to make sure it all was installed and correctly accessible. at that point you just need to download the ROM that you are intending to install and download it. put the zip somewhere in your directory. boot to recovery wipe the necessary mediums and then install from the app and CWM will take care of the rest. Most of the forum threads that have the links to the ROMs will have full instructions on how to install that certain ROM. I can supply links to some if need be. NOT MY THREADS but ones I found helpful.
aidenthefirst said:
All the APK does as I have found out is 'unlocks' the recovery access. After I ran that app I installed Freegee from the app store and installed the CMW recovery from there just to make sure it all was installed and correctly accessible. at that point you just need to download the ROM that you are intending to install and download it. put the zip somewhere in your directory. boot to recovery wipe the necessary mediums and then install from the app and CWM will take care of the rest. Most of the forum threads that have the links to the ROMs will have full instructions on how to install that certain ROM. I can supply links to some if need be. NOT MY THREADS but ones I found helpful.
Click to expand...
Click to collapse
installing the ROM isn't an issue for me, it's getting the recovery installed.
What process did you do after starting up the G Pro Recovery app? install recovery, reboot, then run freegee?
volkey said:
installing the ROM isn't an issue for me, it's getting the recovery installed.
What process did you do after starting up the G Pro Recovery app? install recovery, reboot, then run freegee?
Click to expand...
Click to collapse
Yes. Open and run the G Pro Recovery app, once that is done you need to reboot. Install Freegee and open it. I installed CWM. You can use whatever you want. Then I reboot again, once the phone comes back up I used clockwork mods recovery manager to get in and out of recovery. Also, I pulled my SD card out of the phone prior to rooting as I would lose access to it after I did the process. So just to be safe you might want to do that.
Sent from my LG-E988 using XDA Free mobile app
aidenthefirst said:
Yes. Open and run the G Pro Recovery app, once that is done you need to reboot. Install Freegee and open it. I installed CWM. You can use whatever you want. Then I reboot again, once the phone comes back up I used clockwork mods recovery manager to get in and out of recovery. Also, I pulled my SD card out of the phone prior to rooting as I would lose access to it after I did the process. So just to be safe you might want to do that.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
OK, thanks.
Which root?
aidenthefirst said:
[OP]
Click to expand...
Click to collapse
Which root did you use?
Once you take the update then root your device again you have to do a factory reset on your phone in order to flash a recovery. Currently running E98020I, been there, done that! G Pro KitKat then FreeGee. Mic check 1 2, 1 2
LowVolume said:
Which root did you use?
Click to expand...
Click to collapse
Roottool is an easy way to go Amigo
volkey said:
I found this elsewhere trying to unlock my e980 that was on 20h when I got it.
OK so I found that G Pro KK recovery elsewhere and installed it but wasn't sure what to do from there.. Which option did you choose when running it? Flash recovery, reboot, or reboot recovery? I tried to reboot to recovery and I got into a CWM recovery, but at that point wasn't sure if I was really there or if I needed to flash the recovery from there or from the app.
I'm dying to get rid of the stock ROM on this thing but there are more steps involved than my previous devices.
Thanks!
Click to expand...
Click to collapse
If you just want to install the recovery, get an app call flashify from the play store. Install the app, then download and then flash the twrp .IMG file that you've gotten from this thread: http://forum.xda-developers.com/showthread.php?t=3144369