Database Info

[Q] Xoom 4G unable to root

Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?

Did you boot up the xoom? And do a DB reboot bootloader? Then fastboot OEM unlock?
Sent from my Xoom using xda premium

Yes I did...

Was it unlocked when you sent in? If so it may still be unlocked.
Sent from my Xoom using xda premium

It was unlocked, but they've upgraded the software to 3.2.2 and it's locked again.

It might not be. They don't have to lock it to flash it. And they probly didn't check either.
Sent from my Xoom using xda premium

Ok....pardon the ignorance but how can I tell? I no longer have Superuser. I can't even flash a custom image. Should I downgrade it to 3.0, Root, and then flash it with the Custom 3.2.2 found here on XDA?...

No not that way it screws it up! Use this and only this! Skip the unlock and see if the files work, then you know you were still unlocked.
http://forum.xda-developers.com/showthread.php?t=1242241
Sent from my Xoom using xda premium

Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.

tdetroit said:
Hammer....tried that....no matter what, once the Xoom bootloader reboots, all I get is: Starting Fastboot Protocol Support. Nothing else happens and my adb windows just sits there and says Waiting for Devices.
Click to expand...
Click to collapse
That's because your timing is slightly off, and you're letting the stock recovery overwrite your custom recovery. You have to "catch the boot"
You can follow these steps:4. Install recovery image (CWM)
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/show....php?t=1074979 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery recovery-solarnz-100611-1150.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.

tdetroit said:
Hi. I just received my Xoom back after the 4G upgrade and now I'm unable to root. I've followed all the steps, but when I type fastboot oem unlock, the command prompt just says <Waiting for Device> (I've confirmed that ADB can see the device), and that's it....it just sits there. Can anyone help me?
Click to expand...
Click to collapse
I got mine back yesterday morning then used the Universal Xoom Root instructions and files to root it yesterday afternoon. Perfect!
-ts

I've tried that...won't work. As far as my timing being off....I'm literally watching the Screen the whole time...I never even get anything except the Fastboot Protocol screen...nothing changes. I simply can't go further. I've tried loading the img file (Step 4), but can't even get that far. I've spent an hour on the phone with Motorola yesterday and after being bounced to 5 different techs, they told me to contact the developer.....which I've done, with no success. I'm almost tempted to send this damn thing back and ask them to revert my device and install an older OS onto it.

Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium

hammer4203 said:
Let the device boot all the way and make sure debugging is checked.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
It is. That was the first thing I've checked.

Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium

hammer4203 said:
Then androidsdk may be fubar. Reload your sdk and try again. Make sure to use the newest and download all the files it needs. Redownload the root files too. Then see what happens. My sdk had to be updated when I bought my xoom.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Ah, I will do that. Matter of fact, I'll download it to my other laptop...which never had any sort of anything SDK related on it, give it a fresh start. Thanks....will do this when I get home this evening.

No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.

tdetroit said:
No such luck. Step two: Fastboot oem unlock....window says: < waiting for device > and my xoom just sits there and says: Starting Fastboot Protocol Support.
I've tried this on a totally different laptop, brand new SDK installed, fastboot, and the motorola drivers for the xoom. I'm at my wits end.
Click to expand...
Click to collapse
Nevermind. IT WORKED. I ended up using my work laptop. Something's wonky with both of my personal laptops....either way, it's now unlocked. Thanks for everyone's help and patience.

Ur welcome! Also remember your mouse on a desktop? Took me weeks to figure out the damn thing was causing the bsod errors, and it seemed to work perfectly fine. I would back up your computers you have issues with and do a fresh install on them. I do every 6mo or so.
Sent from my Xoom using xda premium

[Q] ***HELP*** Bricked..Stuck in Boot Loop**

So here is what I did... Last night i successfully unlocked my bootloader on my AT&T HTC Onc X and established root. I was running the AT&T RUU_Evita_UL_Cingular_US-1.82.502. I then tried to update this morning to AT&T RUU_Evita_UL_Cingular_US-1.85.502(desktop installer type) it kept giving me errors and would not complete. Like an idiot i tried to flash CleanROM 2.0 -★| 1.85.502.3 | Tweaked! | Stable! | CWM Install! through CWM and it installed successfully but my WIFI would not work at all. So i decided to reload CleanROM DE 1.0 -★| which had worked fin in the past. At the end of the installer it said to do a factory reset and I did. After the reboot is where i noticed my problem. I am stuck on the boot animation screen. Not able to get into the phone at all now. I am able to get back to the bootloader menu.. boot into CWM but unable to reflash the room on the sdcard. It will not mount USB storage. None of the stock desktop installer will recognize my device is plugged in....... ANY SUGGETIONS...or am I screwed....

Is it in a boot loop or is it frozen on the HTC One screen? That happened to me last night but I was able to run the RUU installer. Did you make sure HTC Sync wasn't running, and that you killed adb by using adb kill-server before trying the RUU installer?
Apologies if you've done these things already, I'm just grasping at straws here.
If you can do adb reboot bootloader, you should be able to run the RUU installer from there, no?

it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?

taterdog2 said:
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
Click to expand...
Click to collapse
If you have adb on your computer (from the Android SDK) and the drivers installed, you should be able to access the device from fastboot (bootloader). RUU will work if you can get your device into fastboot. I'm doing it right now (I wanted to try it before telling you).
Just remember, if you were on an unlocked 1.82 when you borked it, you need to be locked again before you can use RUU. Just use fastboot oem lock from the command prompt.

If you can get to the bootloader screen you are not bricked. Why can't you run the RUU like normal from there? Just re-lock your bootloader first.
Poster above beat me to it while I was taking forever to post.

1. Hold down your Volume Down Button and your power button
2. Wait for the device to turn off and keep holding the combination until you boot into the bootloader (It might take a couple tries, don't give up)
3. Plug your device into your computer via the OEM USB Cable
4. Use the Volume Up/Down keys and the Power button to select the Fastboot Option
5. Wait till the device is recognized (The text on screen where it said Fastboot should become Fastboot USB)
6. Go to the folder where you have fastboot installed and type:
fastboot oem lock
7. Go back to the bootloader and into fastboot when its done with relocking. Make sure the text on the top of the screen says "Relocked" or "Locked" (under the Tampered flag)
8. Run the RUU while in fastboot mode. Use version 1.85.

I sorry for being a NOOB... step 6. Go to the folder where you have fastboot installed and type:
fastboot oem lock...
when you refer to "having fastboot installed" I am taking it that you are not refering to the RUU installer... where do I get this FASTBOOT file from to install?

I think I figured it out... will let yall know in a few minutes

I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?

taterdog2 said:
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
Click to expand...
Click to collapse
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.

jmattp said:
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
Click to expand...
Click to collapse
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV

ted77usa said:
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
Click to expand...
Click to collapse
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.

jmattp said:
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
Click to expand...
Click to collapse
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...

ted77usa said:
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
Click to expand...
Click to collapse
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.

jmattp said:
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
Click to expand...
Click to collapse
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?

ted77usa said:
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
Click to expand...
Click to collapse
Once you unlock your bootloader on 1.85 you will not need root to flash CWM Recovery

Bricked [i9020A], is there an RUU type stock?

Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!

b0vine said:
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
Click to expand...
Click to collapse
Firstly is this still under warranty? Since its the offical ICS update. Just tell him to go to his provider and ask for a replacement since it was not the user's fault.
A few questions. Why is he receiving the ICS update now? If this was ages ago when ICS was first released, Google stopped ICS update for a weeks or so since there was some problems.
And if the warranty doesnt work. Id say root it and flash a Recovery.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/

It's a few months out of warranty, and no, TELUS won't replace it, he's already tried.
I also can't root it as mentioned. I get to this point in the guide
For Windows:
fastboot oem unlock
And get the ERASE:FAILED error once confirming the unloock.

[Q] Correct unroot and bootloader lock procedure?

Hi, my powerbutton on my sns got stuck in the "on" position. So i need to unroot the phone and lock the bootloader in order to send it to warranty repair. I would do it this way
1) reboot to bootloader
2) flash stock images via fastboot
3) issue fastboot oem lock command
4) done?
Im not really sure so im asking first.
Thanks

cahir_cz said:
Hi, my powerbutton on my sns got stuck in the "on" position. So i need to unroot the phone and lock the bootloader in order to send it to warranty repair. I would do it this way
1) reboot to bootloader
2) flash stock images via fastboot
3) issue fastboot oem lock command
4) done?
Im not really sure so im asking first.
Thanks
Click to expand...
Click to collapse
Seems about right

kwibis said:
Seems about right
Click to expand...
Click to collapse
Thanks for confirming. However when i reboot my phone into bootloader my computer cant detect it, thus making fastboot flashing impossible. Any idea what to do?

You need to make sure you have fastboot drivers installed on your computer. Search o the forum, loads of info, I cannot search now as I'm on the phone. Good luck :thumbup:
Sent from my Nexus S

cahir_cz said:
Thanks for confirming. However when i reboot my phone into bootloader my computer cant detect it, thus making fastboot flashing impossible. Any idea what to do?
Click to expand...
Click to collapse
some pics step by sptep to help!!!! (at the 6 step it appear "asus android device" but dont care about that, just search for the words "android devices", nexus devices are universal they work with all drivers)
download drivers (unzip first): http://www.4shared.com/rar/Udv-0weq/usb_driver.html

You're going to have a problem if the power button is not working.
Not going to be able to issue any commands if you can't move the cursor up and down with the volume keys in fastboot. Basically get where it says fastboot USB int...

Retard in need of Help. Weird problem with recovery of my OPO

Alright have read the first 30 pages of comments on http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 and I starting to feel like I'm dumber then a brick.
Okay here is my problem: Just bought a used OPO with the classic boot logo loop error. I have tried to just simply Factory reset it (both Full and wipe cache) and it gives me E: failed to mount /cache (invalid argument) error. Then I googled it and most of the results said that I need to simply reinstall the software with adb. Okay got adb up and running and installed my phones drivers and booted into fastboot.
Then when I try to install it gave me "device not unlocked" error... Fine googled it tried "fastboot oem unlock" and it was still not unlocked.
Googled that and read the posts about tampered bits and after running the "fastboot oem device-info" It gives me "Device tampering: true" "Device unlocked: false" so damn.
Then I read the posts and tried to sideload OnePlusOne-BootUnlocker.zip (used the "apply update" in cyanogen recovery to get the ADB sideload) but it comes up with E: failed to mount /cache (invalid argument) and fails all the other things.
Have tried "fastboot boot recovery recovery.img" but that have the have a unlocked bootloader.
I'm abit lost ATM because I discovered that wile I can get fastboot and Sideload (from update) to show my device the normal adb can't see it when just being in the menu.
So if one of you could point me in the right way or if you got time guide me then I would be greatfull.
Regards Magnus/Mjallo
PS. Please don't burn me for asking

Can post pictures of the screen if it is needed

@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.

h11wiscan said:
@Mjallo google "Bacon Toolkit."
Does literally all the things you are trying to do in a matter of a few clicks. Walks you through everything step by step.
Click to expand...
Click to collapse
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.

might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone

Mjallo said:
Okay have played around with the program abit more and all it does is that same as me doing it in CMD.
I still have the problem with Device tampering and device unlock state. Where is the tools for fixing that?
Have tried to fix the cache but it still make the invalid argument.
Click to expand...
Click to collapse
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.

kenboyles72 said:
might could fastboot flash official images to get the phone back to normal. you dont have to have bootloader unlocked to flash official boot images. you can go here https://cyngn.com/support and download the cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee.zip (scroll down to opo section) and/or go to http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and get the download and follow directions in that post to flash phone
Click to expand...
Click to collapse
Have tried with both Normal Cyanogen and CyanogenMOD (that is what the bootlogo says on this phone) and both of them give the Device not unlocked error both on screen and in CMD

h11wiscan said:
Yeah idk then. Need more screenshots or info to help. Could be a million things.
-Are you using OEM USB cable?
-Did you install ALL drivers properly?
-Have you rebooted since installing ALL drivers?
-Have you tried using bacon toolkit on another computer? Sometimes simply switching computers can help.
-Did you try resetting phone to factory state using ABD/Bacon Toolkit?
-In Bacon Toolkit did you select the proper firmware and software version before attempting to use the program?
A few questions to ask yourself before we go further.
Click to expand...
Click to collapse
Okay I'm using the OEM cable (have tried both the one I got with this phone and the one I got with my Orginal OPO)
Have gone through the steps checking my drivers and they should be working and A OKAY, reboot and all.
Don't have access to another pc ATM but will look after the option.
Have tried all the option in Bacon toolkit to reset the phone to factory setting and non is working, tried to then use the recovery option to maybe get it to work that way but no dice. Have also tried sideloading both with Toolkit and with CMD and no luck their either. Took a picture of the screen when the sideload tries to work.
http://imgur.com/6L74N6J
The Firmware question is up in the air because I have never got it booted so I have no clue what firmware it has only hint that the boot screen is Cyanogen MOD READY and not just Cyanogen like on my other OPO
Hope it helps finding the problem

I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

kenboyles72 said:
I super hard bricked my phone a while back, even lost a partition. I was finally able to get it back by flashing colorOS. took a few tries to get the program to recognize my phone, but finally got it flashed. The phone never booted all the way up with colorOs, but it fixed what needed fixed and I was then able to fastboot flash CM13, unlock bootloader and go from there. don't have that thread bookmarked, but it's here in the forums.
Edit: found thread http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on

Mjallo said:
It sadly did not fix the problem it gives this problem and just stops working (need to close it in taskmanger) http://imgur.com/w1zOQFU.
Well the quest goes on
Click to expand...
Click to collapse
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.

kenboyles72 said:
when you run the program, one of the columns should have a few random characters and "com" in it. if you dont see com in any of the columns, then the program is not seeing you phone. if you do see com, the click on that row and press start and it will show files being written in green showing progress. if phone is not being seen, follow that guide to the letter, specially if this is on a win7/8 machine. i will get my lappy out in a bit and give a few screenies on what it should look like, i wont actually flash my phone though.
Click to expand...
Click to collapse
It sees it (you can see it in COM5 in the picture) and when the progress bar shows it just make a little green tip then just stops showing

are you running the program as administrator? right click on exe and select run as administrator? other than that, don't see why it's not flashing and I'm out of ideas, sorry.