[Q] Rooting 2.3.3 - Nexus S Q&A, Help & Troubleshooting

Hi All,
I'm trying to root my Nexus S and this is my first time rooting an android phone. I'm following instructions at
http://forum.xda-developers.com/showthread.php?t=895545
But it is failing when i try to do a recovery of superuser zip file. instead i'm displayed an android with exclamatory mark.
I'm on Android 2.3.3, build GRI40.
Please help me in rooting my phone.

Did you try posting in the thread instead of starting a new one?

Yes it said i don't have permission to post on that thread

Google Modaco and Superboot. That's what worked for me. You just need to figure out how to do the "fastboot oem unlock" command.

The android and "!" exclamation sounds like you're still on the stock recovery.
Get back into fastboot mode on the phone (pull battery if needed), then go back to the step that has you "fastboot flash recovery recovery.img" and start over from there.
You have to get Clockwork recovery onto the phone to be able to flash the superuser zip.

distortedloop said:
You have to get Clockwork recovery onto the phone to be able to flash the superuser zip.
Click to expand...
Click to collapse
Are you sure? I got superuser through Superboot, and got Clockwork after rooting.

Thanks...superboot from modaco forum worked me. This is cool just one click and im rooted. On to next step...flashing the rom

willentrekin said:
Are you sure? I got superuser through Superboot, and got Clockwork after rooting.
Click to expand...
Click to collapse
The guy wasn't trying the superboot method, he was trying a different method that requires clockwork to flash the superuser zip file, so yes, in the context of the question he posted, I am not only sure, I am very sure.
If the guy is having trouble getting into clockwork recovery, using superboot isn't going to help him out beyond getting su and superuser.apk installed, since superboot doesn't replace the stock recovery with clockwork. Without clockwork he's not going to be able to use recovery to get much done in terms of flashing custom roms or updates.
kirdroid said:
Thanks...superboot from modaco forum worked me. This is cool just one click and im rooted. On to next step...flashing the rom
Click to expand...
Click to collapse
You still need to master the step in the other method that flashes clockwork onto the phone. If you can't get that done, no custom roms; if you could get that done, no reason to use superboot.
Be aware, superboot replaces your kernel with a modded one; probably not a big deal, but something to consider if you wanted a stock kernel. For example, one version of superboot for 2.3.3 uses the 2.3.2 color tables.

Related

[Q] Issue with CWM v3.0.2.5

Hi all,
I recently unlocked my VZW Xoom using the OEM unlock instructions found here: http://forum.xda-developers.com/showthread.php?t=967065
I then downloaded the most recent CWM (3.025) and followed the instructions found in this thread: http://forum.xda-developers.com/showthread.php?t=1038870
I was able to write CWM to the recovery partition with no errors showing in either ADB or on the device itself. I verified the checksum of recovery.img.
What happens now is that when I reboot to recovery from ADB, the red Moto logo shows up, and at first everything looks good. At the top it says "Reading ODM fuse 1".
Then, a green Android logo with a yellow exclamation mark on it appears over a black screen. It looks like some sort of error message. I have CWM on my phone so I know this isn't what it's supposed to look like
In any case, has anyone else seen this issue (or better yet, know how to fix it)? I should point out that after a few minutes, the Xoom automatically boots into HC and works just fine.
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Jthom203 said:
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Click to expand...
Click to collapse
Hi - thanks for the response.
Yes, I've tried that, rebooted the device, rebooted the PC, tried it again, etc. Still no dice
does it still boot? if so try installing rom manager and using it to flash CWR
Sic123 said:
does it still boot? if so try installing rom manager and using it to flash CWR
Click to expand...
Click to collapse
Yep, it still boots. I've never used ROM manager, but I did happen to just download it. I'll give that a shot.
Two other things I didn't mention in the OP:
- I do not have an SD Card in the slot.
- I also didn't 'root' the phone yet with the SuperUser APK, only unlocked the bootloader. Would either of those cause the issue?
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Jthom203 said:
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Click to expand...
Click to collapse
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
volta said:
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
Click to expand...
Click to collapse
Root was the answer. Duh. I feel dumb now.
Either way, once I get to 10 posts, I can post in the dev forum thread to make it clear that root, not just OEM unlock, is required to flash CWM so that dummies like me can get things working quickly
nice, glad that you got it working.
Be sure to install Tiamat 1.31 so you can use your SD card and get full access to CWM
Rom Manager question
Has anyone found a way to allow Rom Manager to "Manage Backups"? It appears that it isn't pointing to the correct directory/ folder.
Had the same issues after installing CWM from ROM Manager - used the adb method instead and this fixed the issue. (Xoom was already rooted and OEM unlocked)

[Q] MyTouch 4G Slide Root question (hboot 1.45.0013/bootloader unlocked/S-On)

Alright, so I got this phone a week ago. First off, I am loving it. Screw Apple.
Anyway, first thing I wanted to do was root it so I can debloat all of T-Mobile's poop applications they cram inside of it.
I've read places that HBOOT 1.45.0013 isn't rootable. I've read it IS rootable, but only with S-OFF on a previous HBOOT. And I've read that it is rootable, but you can't get S-OFF after root.
I've used HTC's unlock tool, which went successful because I flashed CWM through fastboot. I've tried HTC Supertool, MrRoot, and Revolutionary (which says it isn't compatible)
My question then is, which of the above statements is true? If it is rootable, I don't care about S-OFF too much. But I can't ever find a guide that tells me how to root it with this current HBOOT.
Halp pl0x? <3
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
What's the difference in flashing Superuser, and downloading it from the Market?
Sent from my myTouch_4G_Slide using xda premium
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Blue6IX said:
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Click to expand...
Click to collapse
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Btw I see tht your question has been answered but in Mr Root's next update will include a Rooter/Unrooter for the newest H-Boot (Without S-Off)
MewTech said:
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Click to expand...
Click to collapse
For a while it was so - you couldn't do anything with 1.45.0013, HTC broke the OTA so you couldn't unlock it.
In my quest for s-on to s-off (still ongoing) I found a leaked copy of the OTA as a signed HTC package so now we can actually unlock them, and people can work with them and they are now rootable.
Still stuck with s-on though, which is unfortunate - we're working on it and hopefully can crack it soon. Got some leads we're chasing down, each layer we unravel shows us another that has to be solved below it.
ICS? Dunno - i'm not interested in ICS yet, still trying to learn gingerbread through and through (i'm an android newbie) before moving up to ICS. That's on hold right now because of the s-on issue i'm working on. tbalden has been leading the charge on ICS and I would recommend looking into his works if that is your interest.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
can you explain in detail how to flash it to rom?????
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD card" (I'd look up the exact wording, except that my phone has been running a solid 24 days without reboot and I really wanna see how long it goes). Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
ok this is my huge problem i have the same hboot with s-on
i have the full stock stupid t-mobile mt4gs AOS 2.3.4 software# 1.55.531.3 and i DONT have CWM or any of the extras in only thing i succeeded is getting the bootloader unlocked so what should i do?
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Blue6IX said:
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Click to expand...
Click to collapse
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
We love to title our posts here
crimedave1987 said:
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
Click to expand...
Click to collapse
Well,
What exactly did you do that returned this error (mainly because I don't remember if fastboot or adb returns that)? What tutorial/guide were you following? Were you in adb trying to "dd" the CWM recovery image or were you trying to flash an img file from within fastboot? Either way, what was the exact command you typed?
Your other thread (sorry, didn't realize I had replied to you in two different places) received an answer as well. After looking around to get the info you need for this post, I see now you've posted in quite a few threads to which I'm subscribed (guess I just never noticed the name, sorry).
So I see you have an unlocked bootloader. At this point, yes, flash CWM. Blue6ix gave an excellent post on how to do this. Is this the one you are currently trying to follow in order to install CWM?
tried to use superuser
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestions? I have mytouch4gslide with s on unlocked with HBoot 1.45.0013
wesomatic said:
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestion? I have mytouch4g with s on unlocked with HBoot 1.45.0013
Click to expand...
Click to collapse
From my earlier post:
cj chitwood said:
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD Card”. Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
Click to expand...
Click to collapse
Did this help? Only things I can think of are (1) using ”flash update.zip” instead of ”flash [any] zip file” or, less likely, (2) trying to flash an apk instead of a zip.
--
Sent from my Android ”phone”:
HTC DoubleShot /T-Mobile MyTouch 4G Slide running Bulletproof
Yes, that thread did help me. I used your instructions. I even have a new sd card. I have read some threads about formating it first. I did not do that. Also where can I get a good zip file? I down loaded it from some file sharing program 2share I think... Tried again ROOTED!!!! It was so easy!!! Been doing this for a week!!! Wow!!!!!!!!!!!!!!!!!!!
bricked my phone!!!
Just want to add... Do not use ROM Manager from The Market. Bricked my phone. Just stays in start up. Had it rooted and everything!!!!
NO BRICK
Thank God For CWM!!!!!
I am stuck someplace in betweem
Hi:
I too have a MyTouch Slidwe 4G with the hboot 1.45.0013. All the contrary information I have found lead me to go to the professionals. I purchased the root-android.org software. It seemed to run fine - I got no errors and it said that the phone was rooted. I see the superuser app on the phone. However, when I try to run Titanium Backup, it says that the phone is not rooted. The people at root-android.org are not answering my emails (I did get my money back). Any ideas of where I should go from here?
Thanks!
You should never have to purchase root for any android, if it has been done once then chances are it is plastered how to all over the internet, if the phone has a thread on xda then it will be there. Being you got yourself this far I'll help you out a bit more
http://forum.xda-developers.com/showthread.php?p=29439712
Read and understand is my advice, always read until you understand, then search if you have questions, then finally ask questions here if you are still stumped.
For the most part every question you can ask is already answered by one of the super helpful xda folk here, and chances are it is the right information.
I do advice to gain radio soff with the wire trick, it will make life easier... Read up and happy flashing!
Sent from my Nexus 7 using xda premium

How to root Xoom with Android 4.1.1?

I have looked all over the forums and I can not find it. All the forums show how to root a Xoom with Honeycomb or Ice Cream Sandwich TO Jellybean, but what if i already have JellyBean? I just want to get superuser access onto the stock Jellybean ROM and Kernel.
This Link:
http://forum.xda-developers.com/showthread.php?t=1796335
Has been the most useful so far, but even it only roots Ice Cream Sandwich.
How do I root Android 4.1.1 on my Motorola Xoom with 4.1.1.
This should work! Flash it in recovery
What do I need?
matt4321 said:
This should work! Flash it in recovery
Click to expand...
Click to collapse
Do I need to have clockwork mod installed or anything, i have done NOTHING root to my xoom. I rooted my HTC EVO 4G. But i havent flashed a recovery, installed a ROM, No SU, NOTHING. So what exactly should i do with your zip?
Use instructions and tools in http://forum.xda-developers.com/showthread.php?t=1468298 to get Clockwork installed, and then use the modded zip that matt4321 posted (I think that should work... )
Yeah use the AIO tool to unlock your bootloader, then you want to install CWM recovery, then boot into recovery and flash the zip I uploaded
I used this exact process (ended up just GEDify'ing it after sending it back to stock), but before I did that everything worked fine.
Thank you!
I'm too junior to get a Thanks button, so thank you to matt4321 for the JB universal XOOM root, to airesch for leading me too XxLordxX's link and of course to XxLordxX for the tools and instructions to get my XOOM rooted! Worked perfect on my XOOM WIFI JRO03H with no problems. You guys are the best!:good:
stuck on Starting Fastboot Protocol Support - Xoom Android 4.1
I'm trying to follow the directions to install ClockworkMod Recovery
http://forum.xda-developers.com/showthread.php?t=1074979
I'm using Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
and following the procedure for "Method 2 Without CWM"
I got as far as entering the code: adb reboot bootloader
The Xoom rebooted and the Motorola logo appears with the message "Starting Fastboot Protocol Support"
It's just stuck there.
The volume up/down buttons don't do anything at this point.
Any ideas?
thanks!
themonman said:
I'm trying to follow the directions to install ClockworkMod Recovery
http://forum.xda-developers.com/showthread.php?t=1074979
I'm using Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
and following the procedure for "Method 2 Without CWM"
I got as far as entering the code: adb reboot bootloader
The Xoom rebooted and the Motorola logo appears with the message "Starting Fastboot Protocol Support"
It's just stuck there.
The volume up/down buttons don't do anything at this point.
Any ideas?
thanks!
Click to expand...
Click to collapse
Here, detailed procedure with snapshots.
http://forum.xda-developers.com/showthread.php?p=29733454
N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)
Hi,
thanks for the url.
One problem.
And the most important, download EOS-RECOVERY-V6, the "recovery software" that will allow you to work without the need of the PC:
Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
This link goes to a file not found page.
Any update on where I can get that file?
thanks!
wesamothman said:
Here, detailed procedure with snapshots.
http://forum.xda-developers.com/showthread.php?p=29733454
Click to expand...
Click to collapse
themonman said:
Hi,
thanks for the url.
One problem.
And the most important, download EOS-RECOVERY-V6, the "recovery software" that will allow you to work without the need of the PC:
Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
This link goes to a file not found page.
Any update on where I can get that file?
thanks!
Click to expand...
Click to collapse
You have to use another recovery. Eos-r6 was abandoned and another recovery came in as the perfect one. TWRP recovery
http://forum.xda-developers.com/showthread.php?p=28988754
matt4321 said:
This should work! Flash it in recovery
Click to expand...
Click to collapse
Matt,
Is this file appropriate for the WiFi only Xoom?
I installed TWRPv2.8.0.0-Wingray-Non-BigPart on my Xoom. That process went flawlessly.
I used TWRP to install "vanilla" Xoom-Universal-Root.zip. This also appeared to go flawlessly.
However, various root checker apps tell me I do NOT have root.
Please, any suggestions? I ultimately want to get to BigPart but I'm stuck at this point.
thanks,
Dave
vronp said:
Matt,
Is this file appropriate for the WiFi only Xoom?
I installed TWRPv2.8.0.0-Wingray-Non-BigPart on my Xoom. That process went flawlessly.
I used TWRP to install "vanilla" Xoom-Universal-Root.zip. This also appeared to go flawlessly.
However, various root checker apps tell me I do NOT have root.
Please, any suggestions? I ultimately want to get to BigPart but I'm stuck at this point.
thanks,
Dave
Click to expand...
Click to collapse
Yeah, that zip should be good to root any Xoom on 4.1. I wouldn't bother sorting root if you want to go to bigpart as it wipes everything anyway.
Jump straight to bigpart, read read and read again this thread: https://forum.xda-developers.com/showthread.php?t=2506997
Once that is all sorted and booted, I think you should be good to just flash whatever root tool you want (SuperSU, phh superuser etc)
My memory is rusty on all this though, I haven't messed with my xoom in a long time and you quoted a post over 4 years old lol

[Q] Flashing Recovery on Latest VZW Version

I had my phone bootloader unlocked, CWM loaded, and rooted. I decided I didn't really need root and was messing around so I took the VZW update which, of course, required me to flash the stock recovery.
Well, I wanted to play with the new CM 10.2 so I went to flash CWM back on using mattlgroff's utility and while I don't receive any errors and it reboots the phone, the stock recovery is still there.
Any way to flash a recovery or am I hosed? I thought it was only motochopper I couldn't use on the new VZW firmware.
theoreticaljerk said:
I had my phone bootloader unlocked, CWM loaded, and rooted. I decided I didn't really need root and was messing around so I took the VZW update which, of course, required me to flash the stock recovery.
Well, I wanted to play with the new CM 10.2 so I went to flash CWM back on using mattlgroff's utility and while I don't receive any errors and it reboots the phone, the stock recovery is still there.
Any way to flash a recovery or am I hosed? I thought it was only motochopper I couldn't use on the new VZW firmware.
Click to expand...
Click to collapse
Flash recovery manually.
Turn on USB debugging
Open the folder that has the tool files. Find the one that had adb, fastboot and aapt. Go up one folder. Hold the shift key and right click the folder that has adb etc. There is a option in the right click menu that says something to the effect of 'open in command prompt', select it. in the command prompt type: adb reboot bootloader Hit enter.
Copy the cwm img file into the folder with adb and fastboot. Go back to the command prompt. Then type fastboot flash recovery <name of recovery>.img Hit enter. If it doesnt reboot type: fastboot reboot Hit enter.
Enjoy.
Tip: when typing the name of the cwm image type the first few letters then hit tab to autocomplete the name.
Unfortunately, while the commands went through without error, it still has the stock recovery.
theoreticaljerk said:
Unfortunately, while the commands went through without error, it still has the stock recovery.
Click to expand...
Click to collapse
Bad download maybe? Give TWRP a try.
Unfortunately I did.
theoreticaljerk said:
Unfortunately I did.
Click to expand...
Click to collapse
When you go into the bootloader it does, in fact, say you are unlocked?
Sent from my DROID RAZR HD using Tapatalk 4
I was using mattlgroff's utility and the first time I tried CWM it failed. I didn't have my phone rooted, but I had the bootloaded unlocked. So, I just rooted the phone and reflashed CWM and it was fine. I think that same utility has the old software on it, so if nothing else, just flash the old software, root, and then install your recovery.
mentose457 said:
When you go into the bootloader it does, in fact, say you are unlocked?
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
It does still say UNLOCKED.
al2fast said:
I was using mattlgroff's utility and the first time I tried CWM it failed. I didn't have my phone rooted, but I had the bootloaded unlocked. So, I just rooted the phone and reflashed CWM and it was fine. I think that same utility has the old software on it, so if nothing else, just flash the old software, root, and then install your recovery.
Click to expand...
Click to collapse
I can't root because I'm on the latest VZW version.
theoreticaljerk said:
It does still say UNLOCKED.
I can't root because I'm on the latest VZW version.
Click to expand...
Click to collapse
You can flash back to the last version then root. Then you can try flashing CWM or TWRP.
EDIT: Im pretty sure they found a way to root the latest OTA.
mentose457 said:
You can flash back to the last version then root. Then you can try flashing CWM or TWRP.
EDIT: Im pretty sure they found a way to root the latest OTA.
Click to expand...
Click to collapse
Correct me if I'm wrong though...but I don't believe you need root to flash a recovery.
theoreticaljerk said:
Correct me if I'm wrong though...but I don't believe you need root to flash a recovery.
Click to expand...
Click to collapse
You shouldn't but these phones are a bit wonky when it comes to that sort of stuff. For example you dont need root to unlock the bootloader on any other phone except this one.
What does the stock recovery even look like? Ive never been there. After flashing the recovery how are you getting to recovery? Are you using the terminal or command prompt on your computer or are you holding the up/down/power combo the arrowing down to recovery and then arrowing up?
theoreticaljerk said:
I had my phone bootloader unlocked, CWM loaded, and rooted. I decided I didn't really need root and was messing around so I took the VZW update which, of course, required me to flash the stock recovery.
Well, I wanted to play with the new CM 10.2 so I went to flash CWM back on using mattlgroff's utility and while I don't receive any errors and it reboots the phone, the stock recovery is still there.
Any way to flash a recovery or am I hosed? I thought it was only motochopper I couldn't use on the new VZW firmware.
Click to expand...
Click to collapse
Ive found the solution to this if you still haven't...
You need to have root. How you get that is up to you. I flashed back to the last rootable OTA, rooted, used voodoo root keeper to backup root, then took the OTA and restored root with voodoo. Once I had root again i used Root Explorer to rename the file called recovery-from-boot.p in /system . Then I booted into fastboot mode and flashed the recovery like normal. That was it.

[Q] Corrupt Recovery

Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it

Categories

Resources