Develop Bugs

[ROM] 1 Dec ITL41F [GSM] - Stock ROM image for ClockworkMod

Here is the completely stock ROM image for the GSM Galaxy Nexus, version ITL41F. It is not rooted, if you wish to root after installing use my Superboot. System and boot images are included, recovery and baseband are not. The baseband version for ITL41F is the same (XXKK1) as ITL41D, which is posted in this topic if required.
I know this will be useful to anyone wishing to revert their phone to get a future OTA, to chefs wanting to base a ROM on it etc. etc., so here it is.
To install, flash this update zip via ClockworkMod.
Enjoy!
DOWNLOAD - MD5: da1a2c364d316f734f5bd75e7a2f7e32
P

hi paul,
i presume this is not the official ITL41F from google, but the one you have cooked yourseld?

qwerp_ said:
hi paul,
i presume this is not the official ITL41F from google, but the one you have cooked yourseld?
Click to expand...
Click to collapse
It's official Samsung firmware.

Thanks for the ROM - this will be useful for many I'm sure
Can I just ask - is there a reason the recovery image isn't included? It seems from recent threads that this is often requested in order to flash completely back to stock, but no-one seems to have one available. I was just wondering if it there was a specific reason why people haven't been posting it?
Cheers

Think I'll have a play about with this in my kitchen - get some practice in for when I get my GN

Shodney said:
Thanks for the ROM - this will be useful for many I'm sure
Can I just ask - is there a reason the recovery image isn't included? It seems from recent threads that this is often requested in order to flash completely back to stock, but no-one seems to have one available. I was just wondering if it there was a specific reason why people haven't been posting it?
Cheers
Click to expand...
Click to collapse
You can't flash the recovery image as your using CWM to flash it
You'll need fastboot to flash the recovery

Evostance said:
You can't flash the recovery image as your using CWM to flash it
You'll need fastboot to flash the recovery
Click to expand...
Click to collapse
Oooh. I can see how that would be a problem

Bit of an issue, the dsixda kitchen won't deodex the ROM. Any suggestions?
EDIT: Ignore me, should've actually checked to see if dsixda had returned to update his kitchen - which he has!

Is this the one with the permanent volume bugfix?

Annie the Eagle said:
Is this the one with the permanent volume bugfix?
Click to expand...
Click to collapse
Yes it is....

solved my own problem

Shodney said:
Thanks for the ROM - this will be useful for many I'm sure
Can I just ask - is there a reason the recovery image isn't included? It seems from recent threads that this is often requested in order to flash completely back to stock, but no-one seems to have one available. I was just wondering if it there was a specific reason why people haven't been posting it?
Cheers
Click to expand...
Click to collapse
install the rom then lock bootloader then recovery should revert back to stock,it worked on the nexus s so i think it should work the same on this i hope lol

http://groups.google.com/group/android-building/browse_thread/thread/2dde45a058a737b9#
Google Official build.
EDIT
Sorry that build is only 4.0.1 (ITL41D)
Sent from my Galaxy Nexus using XDA App

siedkins said:
http://groups.google.com/group/android-building/browse_thread/thread/2dde45a058a737b9#
Google Official build.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
its a tar file how to use it

siedkins said:
http://groups.google.com/group/android-building/browse_thread/thread/2dde45a058a737b9#
Google Official build.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
It's also not the volume fix build, which is a shame
Sent from my HTC Sensation Z710e using xda premium

EddyOS said:
It's also not the volume fix build, which is a shame
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Yes apologies - I reedited my post when I saw that also.
Sorry for cross posting on this thread. Hopefully they will release the new updated version soon.
Although it probably worth a look as it has an autoscript to restore your phone to stock by flashing multiple files.

If your phone is rooted and have CWM, Superuser and Adfree installed and you flash this what exactly happens?
Does it uninstall CWM? if not how do you access it?
Stret

Stretlow said:
If your phone is rooted and have CWM, Superuser and Adfree installed and you flash this what exactly happens?
Does it uninstall CWM? if not how do you access it?
Stret
Click to expand...
Click to collapse
I need an answer as well.

is it just me but does cw recovery prevent you from installing ota updates?
I keep getting the alert from Google to update but get the sad hospitalised Droid when trying to install.
If I flash the stock rom but still have cw recovery and root the phone, will the ota updates work?
Ez
Sent from my Galaxy Nexus using Tapatalk

Stretlow said:
If your phone is rooted and have CWM, Superuser and Adfree installed and you flash this what exactly happens?
Does it uninstall CWM? if not how do you access it?
Stret
Click to expand...
Click to collapse
As far as i know this not touching your recovery.You must lock the bootloader in order to have stock recovery.You must root it again and install rom manager to access it through UI enviroment.I dont know for sure how you can access it with button combination (i think middle volume and power button)
طوني تبولة said:
I need an answer as well.
Click to expand...
Click to collapse
Check my answer
djcr33p said:
is it just me but does cw recovery prevent you from installing ota updates?
I keep getting the alert from Google to update but get the sad hospitalised Droid when trying to install.
If I flash the stock rom but still have cw recovery and root the phone, will the ota updates work?
Ez
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I think your problem is cwm recovery and not the root.You must lock the bootloader in order to have stock recovery.After that the update can installed succesfully
ps: not an expert.From what i read and tried

[HOW-TO] CMW on LTE Version through Rom Manager

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.

ota update issue

Hi guys I'm trying to get my nexus updated to JB. I am on 4.0.4 rooted using the toolkit. I have flashed stock recovery back to the phone using toolkit. I'm getting the attached error. Any ideas anyone?
Thanks

step 1) STOP USING A TOOLKIT!
step 2) http://forum.xda-developers.com/showthread.php?t=1626895

corkie1 said:
Hi guys I'm trying to get my nexus updated to JB. I am on 4.0.4 rooted using the toolkit. I have flashed stock recovery back to the phone using toolkit. I'm getting the attached error. Any ideas anyone?
Thanks
Click to expand...
Click to collapse
Well first of all, I definitely don't recommend you using toolkit. Using it has higher chance of bricking your phone.
It seems like you might have to boot into the clockworkmod recovery and from there, flash the zip. It's faster than the way and also doesn't give you those kind of headache
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Hi guys when I say toolkit its the specific gnex toolkit. I thought this was a well received method for rooting - no?

Are you sure you flashed the right stock recovery for your phone?

Ya definitely flashed right stock recovery. It's very easy using the toolkit.

corkie1 said:
Ya definitely flashed right stock recovery. It's very easy using the toolkit.
Click to expand...
Click to collapse
so is fastboot
fastboot flash recovery nameofrecovery.img

I've used the toolkits and fastboot on 3 different gnex's and not had problems either way. If you fastboot incorrectly as well it's possible to brick your phone right?

wisniphi said:
I've used the toolkits and fastboot on 3 different gnex's and not had problems either way. If you fastboot incorrectly as well it's possible to brick your phone right?
Click to expand...
Click to collapse
well yeah if you fastboot the wrong recovery, but if you typo the command, it errors and wont flash it.

The OTA failed not because of your recovery but because of /system/usr/keylayout/generic.kl not being stock or missing.
You can either find that file and push it back and then run the OTA hoping that's the only file you modified.
Or flash the stock JB image following the link Zepius posted in the 2nd post.

I used this thread to help me update to JB when the OTA wasn't showing up for me (I was impatient).

wisniphi said:
[snip]
If you fastboot incorrectly as well it's possible to brick your phone right?
Click to expand...
Click to collapse
Nope. Odin yes. Fastboot no.
OP: And as El Daddy said you (or one of your root apps) prob changed something related to your keyboard, so you need to replace that file with the stock one.
Sent from my Galaxy Nexus using Tapatalk 2

I can't agree more! This is literally the third straight post I've read with an issue that started with 'I'm rooted using X toolkit...'
Sent from my Galaxy Nexus using xda app-developers app

El Daddy said:
The OTA failed not because of your recovery but because of /system/usr/keylayout/generic.kl not being stock or missing.
You can either find that file and push it back and then run the OTA hoping that's the only file you modified.
Or flash the stock JB image following the link Zepius posted in the 2nd post.
Click to expand...
Click to collapse
Hiya - thanks - I browsed to the location and found a generic.kl.bac file - renamed this rebooted and the OTA went through no problems

Returning to stock using a Mac.

Can someone please let me know how to do this. i have search everywhere and no one says anything. they only provide a link but it does not provide step by step nor links to do this. my Gnex is unlocked but not rooted. I would like to go back to stock so that i can update to JB. Thank you in advance.

colomob said:
Can someone please let me know how to do this. i have search everywhere and no one says anything. they only provide a link but it does not provide step by step nor links to do this. my Gnex is unlocked but not rooted. I would like to go back to stock so that i can update to JB. Thank you in advance.
Click to expand...
Click to collapse
Well if you're only unlocked, and not rooted, have custom recovery/ROM or anything, you are completely stock. Just unlocked bootloader... OTA has nothing to do with unlocking bootloader. Also root doesn't stop OTAs. Just FYI... Only flashing custom ROM, custom kernel or custom recovery or a change to a system partition stops the OTA.

kyokeun1234 said:
Well if you're only unlocked, and not rooted, have custom recovery/ROM or anything, you are completely stock. Just unlocked bootloader... OTA has nothing to do with unlocking bootloader. Also root doesn't stop OTAs. Just FYI... Only flashing custom ROM, custom kernel or custom recovery or a change to a system partition stops the OTA.
Click to expand...
Click to collapse
and thats where my problem comes. i cant find a stock rom. im on a custom rom.

colomob said:
and thats where my problem comes. i cant find a stock rom. im on a custom rom.
Click to expand...
Click to collapse
Ohhh ok... But you're not rooted? Strange...
Anyways, here is the link. Whenever efrant tells you to either "fastboot" or "adb", just put ./ in front of it. That's the command for Mac and Linus

kyokeun1234 said:
Ohhh ok... But you're not rooted? Strange...
Anyways, here is the link. Whenever efrant tells you to either "fastboot" or "adb", just put ./ in front of it. That's the command for Mac and Linus
Click to expand...
Click to collapse
i found that way but im an idiot i guess. i read it and re read it and i dont understand it.. :/
any way someone can simplify that and post it here?

colomob said:
i found that way but im an idiot i guess. i read it and re read it and i dont understand it.. :/
any way someone can simplify that and post it here?
Click to expand...
Click to collapse
what are the parts you dont understand?
that will guide you through flashing an official google factory image. you on gsm? yakju or takju, your choice. cdma? only vzw gnex is supported.
Sent from my i9250

bk201doesntexist said:
what are the parts you dont understand?
that will guide you through flashing an official google factory image. you on gsm? yakju or takju, your choice. cdma? only vzw gnex is supported.
Sent from my i9250
Click to expand...
Click to collapse
Im on sprint..

anyways i believe i have everything that the guide asks to have, including the ADB and fastboot for mac. i downloaded the update that he asks to get. i have boot.img, bootloader.img,radio-cdma.img, radio-lte.img, recovery.img and system.img....
or anyone have the stock Rom i can flash and ether flash the update or get it OTA???

colomob said:
anyways i believe i have everything that the guide asks to have, including the ADB and fastboot for mac. i downloaded the update that he asks to get. i have boot.img, bootloader.img,radio-cdma.img, radio-lte.img, recovery.img and system.img....
or anyone have the stock Rom i can flash and ether flash the update or get it OTA???
Click to expand...
Click to collapse
Yes you can use that guide for toroplus (i.e., Sprint) devices as well if you have the images. But since you don't have the userdata image (and therefore you skip that step), you may need to boot CWM and wipe /data and /cache, but only if you experience a bootloop.

So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app

colomob said:
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You cannot flash image files on any recoveries. You need to do those in fastboot mode using command prompt.

colomob said:
So in recovery I have to flash each image? That's the part I don't get.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's not at all what I said.
Follow the guide. But for the userdata image (which you don't have), boot into recovery and wipe data.

I finally did it!! If anyone needs help let me know. PM me.
Sent from my Nexus 7 using xda app-developers app

JWR66Y update and re-rooting peculiarity

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..