Recovery mode - Samsung Galaxy Nexus

Hi GN users -
Rooted my phone this evening and all (I thought) was going well. I've been trying to do a backup via rom manager but when the phone reboots i get the android with a red exclamation point. This happens when trying to get to recovery mode using ROM manager or just using the volume buttons. Can't get a clean back up.
Used the following files:
recovery-clockwork-5.8.3.1-toroplus.img
Superuser-3.0.7.efghi-signed
Should I have used CWM-SuperSU-v0.87?
If i can access the boot loader can I go ahead and flash with CWM?
Thanks
Denver

Apparently telling people where to post is frowned upon in this establishment. Please refer to my other post

ÜBER™ said:
You did it wrong. You need to flash the toroplus big dog.zip please search before posting and do not post questions in android development.
http://forum.xda-developers.com/showthread.php?t=1614922
This has the how to.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Please stop being a douche and just answer the question and notify mods if you think posts are in the wrong section.
Sent from my Galaxy Nexus using XDA

So the problem is that you flashed custom recovery and when you reboot it reverts to stock recovery? If so it's because you're on the stock ROM and it's got a script that restores stock recovery upon reboot. You can either install a custom ROM or do this:
juliano_q said:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse

riggsandroid said:
Please stop being a douche and just answer the question and notify mods if you think posts are in the wrong section.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Apparently somebody is blind because I did answer the question... idiot.
Back to the OP you have to reflash your recovery.img then once in recovery flash the super user.zip located here http://tinyurl.com/77cfowp
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
Apparently somebody is blind because I did answer the question... idiot.
Back to the OP you have to reflash your recovery.img then once in recovery flash the super user.zip located here http://tinyurl.com/77cfowp
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
He flashed the correct zips.

jesusice said:
He flashed the correct zips.
Click to expand...
Click to collapse
He must not have if he is getting the broken android. So no he did not. The one I linked is the correct zip to flash to keep recovery and root without having to delete all that stuff. I know I did the exact same thing when I first attempted to root my phone.
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
He must not have if he is getting the broken android. So no he did not. The one I linked is the correct zip to flash to keep recovery and root without having to delete all that stuff. I know I did the exact same thing when I first attempted to root my phone.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
And I flashed the zips he posted when I rooted. I trust that Bigrushdog does know what he's doing but that zip seems to have a lot of things in there that he may or may not need. Like, why does it contain a boot.img? He only needs the SU binary to obtain root. His problem must be that he's rebooting. He should fastboot flash recovery, then fastboot reboot recovery and then flash the SU zip from there. And if he wants to stay on the stock ROM he should follow the instructions I posted. I'm not saying you're *wrong* but I am saying that I'm more right
EDIT: Rereading his post I'm pretty sure he does have root already, his problem is just that recovery isn't sticking which is a known issue with a known solution as I posted previously. Its the exact same thing on the Nexus S.

If anything we are equally correct and my method is much simpler. And yes the boot.img is required this is the stock kernel image without the recovery.sh that runs on the stock kernel. This will keep him from having to delete it manually. I know this because the same method was needed for my epic. You have to flash a tweaked stock kernel without the recovery.sh then flash the recovery. Then everything will stick. His issue is he didn't flash the tweaked kernel and upon booting the stock kernel deleted his custom recovery.
Sent From My Sprint Galaxy Nexus via XDA Premium

denverdesktop said:
Hi GN users -
Rooted my phone this evening and all (I thought) was going well. I've been trying to do a backup via rom manager but when the phone reboots i get the android with a red exclamation point. This happens when trying to get to recovery mode using ROM manager or just using the volume buttons. Can't get a clean back up.
Used the following files:
recovery-clockwork-5.8.3.1-toroplus.img
Superuser-3.0.7.efghi-signed
Should I have used CWM-SuperSU-v0.87?
If i can access the boot loader can I go ahead and flash with CWM?
Thanks
Denver
Click to expand...
Click to collapse
Ignore all the previous comments and once you follow This You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3

msedek said:
Ignore all the previous comments and once you follow http://forum.xda-developers.com/showthread.php?p=23229558 You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Actually he would be even more lost and confused.
Sent From My Sprint Galaxy Nexus via XDA Premium

Just do this:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak (note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse
Then flash your custom recovery and it'll stick.
No need to make it complicated.
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
msedek said:
Ignore all the previous comments and once you follow This You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
That has nothing to do with the problem.

nodstuff said:
Just do this:
Then flash your custom recovery and it'll stick.
No need to make it complicated.
Click to expand...
Click to collapse
Seriously this again? Why are y'all making it much more complicated than it needs to be? Reflash recovery... in recovery flash the zip I linked to. Done.
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
Seriously this again? Why are y'all making it much more complicated than it needs to be? Reflash recovery... in recovery flash the zip I linked to. Done.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
What's complicated about erasing a script? Flashing a kernel to do the same thing seems much more complicated.

jesusice said:
What's complicated about erasing a script? Flashing a kernel to do the same thing seems much more complicated.
Click to expand...
Click to collapse
It takes longer.. takes more effort.
Its simpler to flash the su.zip and call it a day. Than have to flash recovery flash a subinary.zip delete the script the reflash recovery.
Sent From My Sprint Galaxy Nexus via XDA Premium

nodstuff said:
Just do this:
Then flash your custom recovery and it'll stick.
No need to make it complicated.
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
That has nothing to do with the problem.
Click to expand...
Click to collapse
It always has to do with the problem.. Why to do a Mess with your phone and not doing a fresh start???
Also in the way getting a wise android man while learning how to fastboot /adb?...
Thats all i got to say.. In my case id start all over and not going deep complicating things and messing up the os
Galaxy Nexus AOKP m5 Franco kernel m3

Thanks for the assistance.
Ended up reflashing with bigdog and now all seems well.
The assistance is appreciated.
Denver

denverdesktop said:
Thanks for the assistance.
Ended up reflashing with bigdog and now all seems well.
The assistance is appreciated.
Denver
Click to expand...
Click to collapse
Lol I'm sorry for clouding your thread with a semi-argument. Glad your up and running
Sent From My Sprint Galaxy Nexus via XDA Premium

it happens
No problem. It happens.
I can comfortably flash AOPK with CMW, correct?
Thanks
Denver

Yes but make sure you wipe all
Galaxy Nexus AOKP m5 Franco kernel m3

Related

[Q] Easy GN root

I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
you have a nexus, theres only one way to do it correctly.. fastboot oem unlock, fastboot a custom recovery(cwm or i recommend twrp recovery), flash a custom rom(and kernel if you want) in your recovery, then reboot. thats all you need to do. no need for apps or hacks. thats why we buy nexus devices, for the ease. since youre already unlocked, just fastboot a recovery and flash a rom
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
Follow instructions in Method 1 here.
simms22 said:
you have a nexus, theres only one way to do it correctly.. fastboot oem unlock, fastboot a custom recovery(cwm or i recommend twrp recovery), flash a custom rom(and kernel if you want) in your recovery, then reboot. thats all you need to do. no need for apps or hacks. thats why we buy nexus devices, for the ease. since youre already unlocked, just fastboot a recovery and flash a rom
Click to expand...
Click to collapse
He's asking how to root, not how to flash a rooted custom ROM...
efrant said:
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
in this case its one and the same. ive owned every single nexus and this method does not change. all other methods are just extra baggage. or, if you want to, tell all my nexii(nexus one, nexus s, and galaxy nexus) that they dont have root. all the custom have have the superuser binaries that are needed.
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
efrant said:
Follow instructions in Method 1 here.
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
lol, that easy method that you posted is way more complicated. but im guessing that youre recommending this method because youre the one that wrote it up. no need to get more complicated than needed
simms22 said:
in this case its one and the same. ive owned every single nexus and this method does not change. all other methods are just extra baggage. or, if you want to, tell all my nexii(nexus one, nexus s, and galaxy nexus) that they dont have root. all the custom have have the superuser binaries that are needed.
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
lol, that easy method that you posted is way more complicated. but im guessing that youre recommending this method because youre the one that wrote it up. no need to get more complicated than needed
Click to expand...
Click to collapse
Let me rephrase: I think he was asking how to root a stock ROM.
But thanks for your input: if for you, the way to root a rom is to flash a custom rom, you must be right...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Let me rephrase: I think he was asking how to root a stock ROM.
But thanks for your input: if for you, the way to root a rom is to flash a custom rom, you must be right...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
fine. then flash a custom recovery and a rooted stock rom. same thing. the easiest way.
efrant said:
Follow instructions in Method 1 here.
He's asking how to root, not how to flash a rooted custom ROM...
Click to expand...
Click to collapse
Why do you perpetuate the myth of rooting a Nexus?
You root non dev phones, is there some deeper meaning to this?
simms22 said:
fine. then flash a custom recovery and a rooted stock rom. same thing. the easiest way.
Click to expand...
Click to collapse
Which is exactly what i said to do: flash cwm and flash su.zip. nothing else.
morfic said:
Why do you perpetuate the myth of rooting a Nexus?
You root non dev phones, is there some deeper meaning to this?
Click to expand...
Click to collapse
Not sure I understand what you are saying.
Sent from my Galaxy Nexus using Tapatalk 2
Moved to Q&A
Check my sig buddy.
You'll probably need to start from the beginning.
I assume you mean you're carrier unlocked, and not bootloader unlocked.
i think this method is pretty easy. i had no issues using it.
http://forum.xda-developers.com/showthread.php?t=1392310
Just download cwm and put it with your adb/fastboot files.
download the su.zip and put it onto your "sd card".
Pull up cmd prompt and access adb files
adb reboot bootloader
*make sure bootloader unlocked*
Fastboot flash recovery cwm.img
Fastboot reboot bootloader
Fastboot boot cwm.img
Then flash the su.zip
Done
Sent from my Galaxy Nexus using XDA
thos25 said:
Just download cwm and put it with your adb/fastboot files.
download the su.zip and put it onto your "sd card".
Pull up cmd prompt and access adb files
adb reboot bootloader
*make sure bootloader unlocked*
Fastboot flash recovery cwm.img
Fastboot reboot bootloader
Fastboot boot cwm.img
Then flash the su.zip
Done
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Suggestion:
At this time cwm should no longer be preached as defacto standard.
It would be better to refer to "a recovery" linking to both cwr and twrp2.
CWR is extremely antiquated and the ease of use of twrp2 is MUCH better.
morfic said:
Suggestion:
At this time cwm should no longer be preached as defacto standard.
It would be better to refer to "a recovery" linking to both cwr and twrp2.
CWR is extremely antiquated and the ease of use of twrp2 is MUCH better.
Click to expand...
Click to collapse
I only used CWM as an example. I do see your point though.
Personally, I haven't even bothered rooting my nexus or felt the need to do so. Due to the fact that I have not rooted my nexus, I don't have a preferred recovery. I was under the impression that CWM was the preferred recovery (of the majority of nexus users) based on comments I've read in the nexus forum.
I did have my EVO & Evo 3D rooted and used both CWM and TWRP at different times. I preferred TWRP. I believe it was TWRP 1.1.1 vs CWM 4.0.1.4 iirc. I tried TWRP 2.0 but didn't like the touch interface.
I just figured I would jump in to give an easy root method to the OP. That is one of the only benefits to the HTC unlock method. The fact that it forces you to learn some things that many other people would never bother to learn, ie fastboot/adb commands. once you get those down you are pretty golden.
At any rate, you are right though. TWRP could be a better option for the OP. And based on my EVO 3D experience, I would say it probably will be the better option.
Sent from my Galaxy Nexus using XDA
thos25 said:
I only used CWM as an example. I do see your point though.
Personally, I haven't even bothered rooting my nexus or felt the need to do so. Due to the fact that I have not rooted my nexus, I don't have a preferred recovery. I was under the impression that CWM was the preferred recovery (of the majority of nexus users) based on comments I've read in the nexus forum.
I did have my EVO & Evo 3D rooted and used both CWM and TWRP at different times. I preferred TWRP. I believe it was TWRP 1.1.1 vs CWM 4.0.1.4 iirc. I tried TWRP 2.0 but didn't like the touch interface.
I just figured I would jump in to give an easy root method to the OP. That is one of the only benefits to the HTC unlock method. The fact that it forces you to learn some things that many other people would never bother to learn, ie fastboot/adb commands. once you get those down you are pretty golden.
At any rate, you are right though. TWRP could be a better option for the OP. And based on my EVO 3D experience, I would say it probably will be the better option.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
the newest twrp touch recovery is sweet, cwm doesnt even come close. when you do decide to set your nexus free, give it a try
SoulOfDownfall said:
I have an unlocked bootloader and ICS 4.0.4. what is easiest root? One click root didnt work.
Thanks in advance for putting up with my stupid question
Please explain in detail, the instructions, like youre talking to somebody stupid. thanks
Click to expand...
Click to collapse
Install GNex Toolkit from here http://forum.xda-developers.com/showthread.php?t=1392310. First do option 1 (drivers) and than option 7 (one-click for all). You have root and cwm, works like a charm and is the easiest way to do it.
Jubakuba said:
Check my sig buddy.
You'll probably need to start from the beginning.
I assume you mean you're carrier unlocked, and not bootloader unlocked.
Click to expand...
Click to collapse
Im bootloader unlocked, cwr.
im very computer savvy, and tech savvy, i know what im talking about, so everything i say i am completely positive of, i am experienced with android, i just dont know how to root. I have the su.zip on my sd card btw.
Good Lord,
One question and so many answers, no wonder new users are confused--
Don't pay attention to me--just bored atm and trying to decide btw the GN tmobile or One S to replace my N1--
Nothing like hijacking a thread either--
I prefer to use Galaxy Nexus Root Toolkit. Its very simple and do the job well. Never experiencing any problems with it.
Sent from my Galaxy Nexus using Tapatalk 2

Help backing up stock JB kernel

I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!
mtmjr90 said:
I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!
Click to expand...
Click to collapse
Here's the stock kernel for you
Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Edit: Oh, also is that zip flashable via CWM?
Sent from my Galaxy Nexus using Tapatalk 2
I got it from one of the Jellybean threads, but with the sheer volume of JB threads today, I can't remember which. I think it's the main JB thread in General.
The only thing I did was rename it from StockKernel.zip and added the JB prefix so as not to lose it in my mess of files
Ah, sounds good. Thanks again!
Sent from my Galaxy Nexus using Tapatalk 2
mtmjr90 said:
Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Click to expand...
Click to collapse
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot
efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot
Click to expand...
Click to collapse
Is that via a terminal emulator on the device then?
efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Click to expand...
Click to collapse
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?
mtmjr90 said:
Is that via a terminal emulator on the device then?
Click to expand...
Click to collapse
Either or.
---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------
drewcam888 said:
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?
Click to expand...
Click to collapse
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)
efrant said:
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)
Click to expand...
Click to collapse
I don't see any option to restore only the kernel. Where is this option?
drewcam888 said:
I don't see any option to restore only the kernel. Where is this option?
Click to expand...
Click to collapse
Under "backup and restore" under "advanced restore", select boot image.
Sent from my Galaxy Nexus using Tapatalk 2
Only a little bug for me:
From settings-->storage (memoria in italian) It can't see all the files in the sdcard, also doesn't see a lot of music (but I can see those music files with play music app)...
Any other thing is working fine, good battery life, much faster on homescreen and on the appdrawer, maybe a little laggier on temple run...
Waiting for the official release...
So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.
jenda.69 said:
So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
Click to expand...
Click to collapse
Yes, you are right.
jenda.69 said:
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.
Click to expand...
Click to collapse
If harveydent used dd to dump the image, it will be padded with a bunch of zeros at the end. Both will work fine, although you cannot flash the untrimmed one using fastboot, you need to use recovery or dd.
Sent from my Galaxy Nexus using Tapatalk 2

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

Unlock/Root

Hello everyone, I just got my hands on my new nexus and I LOVE IT!!. I'm on verizon.
I just have a few questions. I got it yesterday but I see there are new radios/bootloader?
I'm still on stock 4.04 ICS
I want to root/unlock and load up MIUI/AKOP
Can someone give me a small tutorial on how to do this? I see there's a toolkit but i'm confused on what to do because of JB dropping.
As always i'm late to the party
http://forum.xda-developers.com/showthread.php?t=1529058
David522d said:
Hello everyone, I just got my hands on my new nexus and I LOVE IT!!. I'm on verizon.
I just have a few questions. I got it yesterday but I see there are new radios/bootloader?
I'm still on stock 4.04 ICS
I want to root/unlock and load up MIUI/AKOP
Can someone give me a small tutorial on how to do this? I see there's a toolkit but i'm confused on what to do because of JB dropping.
As always i'm late to the party
Click to expand...
Click to collapse
efrant has all the info you need:
http://forum.xda-developers.com/showthread.php?t=1814266
Can I just use the root toolkit? (Does it work well?)
David522d said:
Can I just use the root toolkit? (Does it work well?)
Click to expand...
Click to collapse
it works... but when it fails, it fails hard. and then you dont know where it failed or what it even did.
i personally will not help if you use the toolkit and things go wrong... others will still help.
It's actually very easy on this device. Since you know you are wanting to install a new ROM you don't even need to root. The hardest part is installing the ADB usb drivers and making sure they work correctly. There are basically 3 things you need to do.
1.) Install ADB and the ADB usb drivers
2.) Unlock the bootloader and install a custom recovery (ClockworkMod is the most popular)
3.) Flash a new ROM
You can do steps 1-2 by following this guide up to the recovery install step. Then for step 3 download the ROM of your choice into the internal sd and boot into CWM recovery and flash.
Stupid question, can i do all of this if the phone isnt activated? My sim card should be here in the mail tomorrow
David522d said:
Stupid question, can i do all of this if the phone isnt activated? My sim card should be here in the mail tomorrow
Click to expand...
Click to collapse
yes you can.
Zepius said:
it works... but when it fails, it fails hard. and then you dont know where it failed or what it even did.
i personally will not help if you use the toolkit and things go wrong... others will still help.
Click to expand...
Click to collapse
jeez you had no faith in tookit guy
very easy to do.
now my question to you again
im unlocked rooted and have clockwork touch
should i flash these new radios/bootloader and flash them thru clockwork?
thanks
David522d said:
jeez you had no faith in tookit guy
very easy to do.
now my question to you again
im unlocked rooted and have clockwork touch
should i flash these new radios/bootloader and flash them thru clockwork?
thanks
Click to expand...
Click to collapse
considering i read these forums and see the posts that get created, yeah i dont trust the toolkit. there are so many threads created with the title of "HELP I BRICKED MY PHONE" followed by "i used such and such toolkit"
as far as your other question, you can flash the radios and bootloaders via CWM.
David522d said:
Stupid question, can i do all of this if the phone isnt activated? My sim card should be here in the mail tomorrow
Click to expand...
Click to collapse
Since when did Verizon start using sim cards
Sent from my Galaxy Nexus using xda premium
Zepius said:
considering i read these forums and see the posts that get created, yeah i dont trust the toolkit. there are so many threads created with the title of "HELP I BRICKED MY PHONE" followed by "i used such and such toolkit"
as far as your other question, you can flash the radios and bootloaders via CWM.
Click to expand...
Click to collapse
haha yah no I do believe you.. and thanks!
last question
Until I flash a new rom over stock, will i have to re flash clockwork every time if i want to use recovery
dschreiber69 said:
Since when did Verizon start using sim cards
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Since they got lte
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
David522d said:
haha yah no I do believe you.. and thanks!
last question
Until I flash a new rom over stock, will i have to re flash clockwork every time if i want to use recovery
Click to expand...
Click to collapse
Delete recovery-from-boot.p from /system
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
Since they got lte
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
Delete recovery-from-boot.p from /system
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What i did was install jellybean and now everytime it boots into recovery when i want it to =)
Was android restoring the default recovery because i was on stock ROM?

Root method that works please...

I have searched XDA thread's, I have combed through android central. Ever root method I follow including heisenbergs leads to boot loop. Let me just state I am not new to rooting and this is frustrating beyond words. I want to throw this damn thing against a wall but I know it's not the phones fault.
[Before anyone says it, I have searched XDA, Androicentral, several other forum boards high and low , believe me, it only ads to my frustration] So, regarding th title of the post: Should be as simple as flashing supersu in recovery right? Just after flashing the modified boot image? Can't get it to take. I've tried every step variant I can think of like flashing the vendor file which is new to me. Flashing a rom and allowing that supersu included do the rooting, in all different step orders too, so on and so forth - but all of these iterations I have tried leads to bootloop. I get stuck with no choice but to manually flash each partition back to stock just so that I have a phone to use.
After restoring my phone back to stock i am here: I have the most recent TWRP installed for a recovery (thus obviously my bootloader is unlocked too), I have not flashed the modified boot image yet but am aware I will need to before flashing supersu (and wiping cache) in recovery - last time I did it this way it did not work for me...
Can anyone point me to a simple tutorial of how to obtain root or maybe point out what I've done wrong above, please? I am at my wits end over something supposedly so simple. (Go ahead, laugh, call me names, whatever - I deserve it)
What boot image are you flashing? It's probably not compatible with the security patch you are on. Really you don't need to flash a new boot image as the SuperSU zip now patches it. So just flash SuperSU and enjoy root.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Oh yeah I forgot to lol and call you a noob. Noob.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
What boot image are you flashing? It's probably not compatible with the security patch you are on. Really you don't need to flash a new boot image as the SuperSU zip now patches it. So just flash SuperSU and enjoy root.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Oh yeah I forgot to lol and call you a noob. Noob.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks! So it comes in a .zip. Do I extract it or something? I have always just used TWRP to "install", then choose the zip file and "flash". Always worked. Should I have unzipped the package or something?
kerryh420 said:
Thanks! So it comes in a .zip. Do I extract it or something? I have always just used TWRP to "install", then choose the zip file and "flash". Always worked. Should I have unzipped the package or something?
Click to expand...
Click to collapse
No. Just flash the latest SuperSU zip. The installer patches the boot image.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
No. Just flash the latest SuperSU zip. The installer patches the boot image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks Man! you rock!
Now to install a Rom it's the same as always right. DL the ROM of choice and follow Dev's instructions? Wheredoes this vendor.img come into play? flashed through fastboot before the ROM is i assume?
PiousInquisitor said:
No. Just flash the latest SuperSU zip. The installer patches the boot image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks Man! you rock!
Now to install a Rom it's the same as always right. DL the ROM of choice and follow Dev's instructions? Where does this vendor.img come into play? flashed through fastboot before the ROM is i assume?
kerryh420 said:
Thanks Man! you rock!
Now to install a Rom it's the same as always right. DL the ROM of choice and follow Dev's instructions? Where does this vendor.img come into play? flashed through fastboot before the ROM is i assume?
Click to expand...
Click to collapse
Just follow the instructions in the OP of the ROM you wish to flash.
For details on what the vendor partition is and which one to flash, look in the FAQ of the Pure Nexus ROM. I'm to lazy to to explain it myself or even link to it. Sorry, it's late here and locating it's kind of a pain on the mobile.
And for future reference it's an utter waste of time to root then flash a ROM. I'll explain tomorrow if you don't understand why.
Sent from my Nexus 5X using Tapatalk
kerryh420 said:
Now to install a Rom it's the same as always right. DL the ROM of choice and follow Dev's instructions? Where does this vendor.img come into play? flashed through fastboot before the ROM is i assume?
Click to expand...
Click to collapse
The drivers and firmware got extracted into a separate vendor partition. Google doesn't provide source for vendor.img, just binaries. You need to flash a vendor.img that matches the ROM. If they don't match it might still work with some complaints, but it is best to have them matched. Look at your ROM to see which vendor.img they require.

Categories

Resources