Database Info

[Q] failbooted recovery from CWM ROM Manager stuck

Dear people of awesomeness,
The story: I was following the exciting thread about the new CWM support for SGS4G by krylon360 and team, followed the directions (overwriting the recovery file WITH R/W enabled, placing update.zip into the root of my SD card...), and got stuck. Didn't know what to do exactly after that, other than try to use ROM Manager to backup my phone. Saw the "Reboot into recovery" option in the ROM manager menu and thought hey, let's see what this does. Most careless, stupidest thing I've done this year. fail.
The question: What is/are the way/s to boot into stock recovery mode? I can't seem to find a definitive method for booting into "stock recovery mode", though I've found plenty of ways to boot into download mode (a whole thread of them lol). I managed to find ONE method after reading through hundreds (honest) of posts in dozens of threads here and elsewhere: Hold vol+ Vol- and Power simultaneously from a powered off state.
The secondary fail: Obviously this didn't work for me, and although I'm near certain I'm going to have to do the "Odin" thing, I just wanted to ask if anyone could clearly explain the method to boot into stock recovery?
The shameless 2nd question: This question may have been asked elsewhere, shame on me, but... the .tar I'm downloading ([ROM-ODIN]T959VUVKB5 Stock + Root -- (hxxp://forum.xda-developers.com/showthread.php?t=978836)) will it wipe my phone?

akira6968 said:
Dear people of awesomeness,
The story: I was following the exciting thread about the new CWM support for SGS4G by krylon360 and team, followed the directions (overwriting the recovery file WITH R/W enabled, placing update.zip into the root of my SD card...), and got stuck. Didn't know what to do exactly after that, other than try to use ROM Manager to backup my phone. Saw the "Reboot into recovery" option in the ROM manager menu and thought hey, let's see what this does. Most careless, stupidest thing I've done this year. fail.
The question: What is/are the way/s to boot into stock recovery mode? I can't seem to find a definitive method for booting into "stock recovery mode", though I've found plenty of ways to boot into download mode (a whole thread of them lol). I managed to find ONE method after reading through hundreds (honest) of posts in dozens of threads here and elsewhere: Hold vol+ Vol- and Power simultaneously from a powered off state.
The secondary fail: Obviously this didn't work for me, and although I'm near certain I'm going to have to do the "Odin" thing, I just wanted to ask if anyone could clearly explain the method to boot into stock recovery?
The shameless 2nd question: This question may have been asked elsewhere, shame on me, but... the .tar I'm downloading ([ROM-ODIN]T959VUVKB5 Stock + Root -- (hxxp://forum.xda-developers.com/showthread.php?t=978836)) will it wipe my phone?
Click to expand...
Click to collapse
does your phone still boot up normally?

also when you get to the recovery menu it should be blue. scroll down to reinstall packages, and that will get you to CWM recovery

Ok first, Rom Manager should not be used until Koush incorporates our device in it.
Your findings are correct, the vol+,vol-, + the power button should get you into recovery, besides that the only other way is to use an app/power menu mod but that requires the phone to be on.
It sounds like the next thing for you is Odin. From your phones current state you can, hold vol+, vol- and then plug USB Cable into phone (Brings you into download mode), ive read some users pull battery and put it back in, but the first way i explained it should get you into download mode. From there, choose Roms KB5, KC1, or KD1, and yes your device will be factory reset. Your documents should be on your SD. I dont know if you have Titanium Backup to restore your apps, if not, you will have to manually install them after your odin session.
hope this helps

E:signature verification failed
chris.... said:
also when you get to the recovery menu it should be blue. scroll down to reinstall packages, and that will get you to CWM recovery
Click to expand...
Click to collapse
When I boot into recovery mode and select reinstall packages it starts out:
install from SD card
Finding update package
Opening update package
verifying update package...
E:signature verification failed
installation aborted
I have downloaded krylon360's cwm final update.zip and put it in my root directory.
The only posibility I can think of was a friend rooted my phone with an older update.zip file and i am trying to put the new one on. I deleted the old update.zip and copied over the new one.
i then downloaded odin and followed the instructions on a post to flash my rom with the t959+root from krylon360 as well. I believe that worked, because a lot of the apps that came with the phone are back now.
i tried reinstalling packages after this and still the verification error.
i have been doing a lot of browsing, searching and reading tons of posts on here... cant seem to figure this one out. any ideas?
Thanks

If you successfully flashed your phone and have root access, double check the update.zip is in the root and make sure its the latest one. Another thing is to make sure you copied over the Recovery file and pushed (Copied) it over to System/bin folder. Once you have those two in place you can reboot into stock recovery then "re-install packages" to get to CWM Recovery.

Hooray!
I did the ODIN thing, according to the post mentioned in my OP, and it fixed everything My custom shutdown vid, startup/shutdown sounds were gone, but my apps were still there, even paid apps. No titanium backup.... guess I got lucky lol. Scared the crap outta me when it wouldn't load past the T-Mobile startup image.
I knew not to use CWM yet, was following the thread about imminent implementation of sgs4g support for CWM, but just didn't really think that booting into recovery mode from CWM would get me stuck like that. Didn't even try to install recovery for CWM, knowing that "Epic 4G" and "Vibrant", etc were not the right choice despite the seeming similarities.
I had been keeping up with moving all apps i could to SD, so maybe that saved me, I dunno.
Followed pixelbrains post to use odin and worked perfect. Thank you all!!

glad you got your phone back. \m/

fknfocused said:
If you successfully flashed your phone and have root access, double check the update.zip is in the root and make sure its the latest one. Another thing is to make sure you copied over the Recovery file and pushed (Copied) it over to System/bin folder. Once you have those two in place you can reboot into stock recovery then "re-install packages" to get to CWM Recovery.
Click to expand...
Click to collapse
Thank you for that info.... I actually finally figured it out, but it took me forever. the key kind of is what i thought, that i did not have the recovery file in the right spot. I finally found a free file manager, super manager (recommonded on one of theses posts, i read so many cant remember which one ) after fiddiling with that for like 30-40 mins i finally figured the correct procedure to allow me to paste that recovery file and once i did that, bam, cwm recovery worked fine.
so, the fact that i am able to get to that screen and the latest update.zip file is in my external sd cards root dir. i am all goo there right?
i also used odin to flash "PDA_KD1.tar.md5" my phone after i got that recovery file in the correct place, and then when that was done i booted into the cwm recovery after i downloaded "Bali_SGS4G_v1.4UV.zip" and then i hit install zip from SD card, and i selected choose zip file and selected that bali one, and then i had to scroll down like 7 spots to hit yes to install and it went for a few seconds and then acted like it was done, so i just hit back and then reboot. how do i know if that worked? cuz i dont see anything saying bali at all on my phone...
does it sound like i did that right?
thanks again

edge228 said:
Thank you for that info.... I actually finally figured it out, but it took me forever. the key kind of is what i thought, that i did not have the recovery file in the right spot. I finally found a free file manager, super manager (recommonded on one of theses posts, i read so many cant remember which one ) after fiddiling with that for like 30-40 mins i finally figured the correct procedure to allow me to paste that recovery file and once i did that, bam, cwm recovery worked fine.
so, the fact that i am able to get to that screen and the latest update.zip file is in my external sd cards root dir. i am all goo there right?
i also used odin to flash "PDA_KD1.tar.md5" my phone after i got that recovery file in the correct place, and then when that was done i booted into the cwm recovery after i downloaded "Bali_SGS4G_v1.4UV.zip" and then i hit install zip from SD card, and i selected choose zip file and selected that bali one, and then i had to scroll down like 7 spots to hit yes to install and it went for a few seconds and then acted like it was done, so i just hit back and then reboot. how do i know if that worked? cuz i dont see anything saying bali at all on my phone...
does it sound like i did that right?
thanks again
Click to expand...
Click to collapse
settings menu then go to about phone and check the kernel
Sent from my SGH-T959V using XDA Premium App

thank you, it shows the bali as kernel... so glad to see i did it correctly

[Q] OTA 2.3.7 update lost SU permissions

Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis

sobamaflyer said:
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
Click to expand...
Click to collapse
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?

krohnjw said:
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
Click to expand...
Click to collapse
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.

sobamaflyer said:
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
Click to expand...
Click to collapse
Yeah, you have the stock recovery. You can't apply a new recovery through rom manager because the su binary doesn't have the appropriate permissions since the update.
Boot into the boot loader (Vol up and pwr). Don't go into recovery. Use fastboot from the boot loader to load CWM. Boot into CWM after flashed and flash the SU binary (mount /system first). After this boot up and delete/rename /etc/install-recovery.sh so that it won't overwrite CWM on each reboot. Install CWM again from Rom Manager or via fastboot (as it was overwritten on boot). Done.

Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"

sobamaflyer said:
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
Click to expand...
Click to collapse
Fastboot is merely a command line tool used for various operations on the device. Mainly though you'll use it to flash an image to a specific partition.
You'll need to boot the device into the boot loader (hold Vol up and power on).
Plug the device in via USB.
Open a command windows in the tools or platform-tools folder of the SDK (depending on your version of the SDK, where the fastboot.exe can be found) and issue the fasboot devices commmand. This should display the serial of any connected devices. If this comes back blank there is an issue with the installed driver. Reinstall the USB driver for the device using the supplied driver from an updated SDK.
Assuming fastboot devices shows one device you now can flash a recovery to the device. Download the appropriate recovery for your device (i9020(a), i9203 or NS 4G) http://mirror.sea.tdrevolution.net/cm/recoveries/. Place this file in the same directory for simplicity.
At this point you can flash your recovery.
fastboot flash recovery file.name.you.downloaded.img
If it is not in the same directory you can alternatively pass the full path to the image.
You now have a custom recovery installed. Select Recovery from the bootloader menu to now boot into this recovery.
Assuming you've already downloaded the su binary and it is on your SD card, mount /system from within CWM and then chose to install zip and select this from the SD card. You now have root access.

Now that a panic attack is settling...
I think I'm getting somewhere but not yet where I want to be. I go to Bootloader, I connect my USB and don't get anything different than above from my sdk tools menu (unusable cmd screen, fail showing on my phone). What does [eventually] work is going back to my "nexus S one click root" folder and clicking run.bat (as fastboot.exe and adb.exe in that folder also do the nothing).
This run.bat reads some sort of fail and boots my phone telling me that debugging is not checked (which it is) and takes me directly to there, then the cmd screen tells me to press enter when I've turned on the [already checked] usb debugging toggle.....what the hell I press enter. Now it goes into the old beautiful CWMR (3.0.xxxx) screen where I'm able to apply .zips, backup etc.
(luckily I think ahead and do a backup right this min.)
Then I go from that screen and decide to apply my new CM7.zip that started all this, I apply that and get a bootloop on the CM7 boot screen.......crap......I go clear my davlik and cache and install CM7 again. Same thing.....crap......
I try restoring my original backup from 9/5/11 I made right after first unlocking my phone.......CM7 bootloop screen.....dammmmiiiiit
I try restoring backup from 9/12 I made after getting everything just like I wanted it.......CM7 bootloop screen.......uh oh, panic beginning.
I restore the backup from a few lines ago, my phone comes back (thank god)
So:
-I have to have the right USB driver in my laptop because something from sdk ultimately talked to my phone?!
-Clockworkmod recovery 5.xxxx has never worked quite right for me, apparently 3.xxxx is still my magic answer?!
-Now that I've gotten this far should I try the same process to get back to my CWMR 3.xxxx screen and put some different files in my root to use than what I've done to this point?
....again, I apologize if I'm being myopic or asking dumb questions. I often say I only know just enough to be dangerous.

[SOLVED] - maybe/sort of
Between reading (and re-reading) the help above and continued research on my own I [think] I solved my problem.
I found the following 2 links:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
And basically started over from scratch, I deleted what I'd put in my pc and re-loaded using those instructions (in the right place, the right way). Doing this I was able to pull up a cmd window and this time it properly accessed my phone. I got it to fastboot recovery - load CWM 5.0... and from there got into my recovery menus on my phone this time.
One curious thing....I tried the part VI in "how to root the samsung" ...""stop the phone uninstalling the custom recovery image"...... I've tried several things there but still get an error that it is read only.
....I went on to install CM7, and it consequently updated right after to the latest CM7, At this moment I have full permissions, superuser access, was able to make a backup of yesterday, the CM7 this morning and then CM7.1.0.1 that loaded.
Will I ultimately have the same issue as before? But be able to overcome it in the same manner when I want to?
Thanks for the help

This is why one click methods are bad. When a problem arises you have no clue what to do because a software did it for you the first time. Glad you got it figured out.
Sent from my Nexus S 4G using xda premium

[Q] How to revert back to stock everything without root on GT-i9020T?

How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.

wierd165 said:
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
Click to expand...
Click to collapse
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip

Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?

mahanddeem said:
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
Click to expand...
Click to collapse
I have reverted back from 4.0.3 yesterday by reflashing the full 2.3.6 rom without any issues. I'm not sure I understand what you mean by losing IMEI.
My phone works just fine after doing this (more than once!).

pcbroch said:
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Click to expand...
Click to collapse
Ok here's my problem i did the ics update earlier before you told me this and still having issues, now when I go to recovery I get a android with his chest open with a red caution sign on it...how could I just format everything, essentially make it the way it was out of box so I could start over...because of all the issues I'm currently having.

When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.

OK thanks...Just please let's summarize this
1.You were on I9020T bone stock , unrooted
2.You had GB 2.3.6
3.You updated manually (or OTA) to 4.0.3
4.You decided to revert to GB 2.3.6
5.You used exactly the same method of manual update (stock recovery after copying the .zip file and in this case the full ROM of 2.3.6 to SD)
6.You followed the stock recovery steps and chose the .zip 2.3.6..
7.After everything was setup , you booted into GB 2.3.6 without any problems
Is that right ? or better if you make the exact detailed steps you did to revert to GB 2.3.6 would be apreciated
Thanks

furiannn said:
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
Click to expand...
Click to collapse
Tried, but then I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Any help?

I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App

Raver27 said:
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
how would I go about flashing the custom recovery? I tried to flash another full rom package with the recovery in it and like i said i got that error...

Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android

furiannn said:
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
Click to expand...
Click to collapse
I don't believe I have a folder as such, being a person who is not familiar with the lingo, etc of all this i rooted it with one-click mod, and just flash things through this, are you saying I can flash things externally? sorry to sound like a bum, but i'm trying to understand thanks.

No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom

furiannn said:
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
Click to expand...
Click to collapse
I'm using clockwork right now, but it seems to be corrupted, im running 4.0.3 right now on a full rom package, so your saying I should still do this? I think i may have done all that before, as the phone is rooted, but I used the one-click method instead.

Just download that file and then you'll have what you need on your pc to do what i mentioned above. Plug the phone in and reflash the new recovery which will not harm it, and then you'll be able to stick gingerbread or ICS back on. You gotta try things out otherwise you'll not understand what is going on. I dont know of any one click thing that will let you go back to default as it was before. After it flashes the new recovery, scroll down to "recovery" on the screen and press the power button, dont restart the system.
In hindsight, while the one click methods are easy to use, theyre getting used by people that dont do the necessary research to learn about the rooting and flashing process. This means you end up skipping so much that you learn about the whole rooting and flashing proocess when doing it manually, which in turn means you have more trouble getting out of it if you want it back to the way it was! No offence intended here, but you just need to man up and do it! All will be well

[Q]

First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?

Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.

airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!

Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium

Thanks a million, I am going to try it fresh on my pc at work. Thanks!

That did the trick THANKS A BUNCH!!!!!

[Q] Trying to Root.

I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!

Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?

arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.

sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?

arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?

sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.

arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.

I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.

sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).

arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.

sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.

Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS

unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance

1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.

Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.

Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx

D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.

arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?

D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.

arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me