Hi All -
I finally broke down and rooted my US wifi Xoom, but I've run into a problem. I followed the instructions for installing the custom recovery and that went fine. I then installed the 'update_US-Xoom-WiFi-3.2.1-HTK75D_stachre_v02.zip' per the instructions.
When I rebooted, the Xoom was stuck in the honeycomb boot animation. I manually rebooted using the vol up / power button and, upon reboot, I got the green "enter your password" screen that I'd normally see after encrypting my device (I didn't encrypt it).
Now, I'm stuck there - I tried reflashing the recovery and the ROM, did a factory reset, etc and I get the same thing. I can't format or mount the 'data' folder in recovery - I suspect that's where the problem is.
Anyone have any suggestions? Thanks!
<UPDATE> Disregard - a quick 'fastboot oem unlock' solved the problem.
Related
hi all
i am trying to do a factory reset to my nexus S but i faced some problems, the phone cant be reset to factory settings. my phone is on 2.3.4 and is rooted
i had tried the following steps
1) going to Settings>Privacy>Reset phone
after i confirm to wipe everything, the phone rebooted and it will stuck at the "Google" logo (in words) with the fastboot unlock logo at the bottom. i took off the battery to shutdown the phone (anything i press at this moment does not get any response from the phone) and start it up again. once it is started (it get pass the google word logo if i do it this way) all my application and even my themes are still there
2) shutting down the phone. press volume up + power button. choose recovery
same thing happen as above. it cant get pass the google word logo and once i restart the phone by plugging out the batt, it went back to previous state without wiping anything
i search online guide and also youtube video and all of them shows that the recovery will bring you to a android with a exclamation mark (in the triangle) but i cant get to the screen. i had left my phone there for 30 minutes but it is still stuck at the google logo.
Please help
Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik.
polobunny said:
Reflash latest clockworkmod recovery, boot into recovery and wipe data + cache + dalvik.
Click to expand...
Click to collapse
thanks for the feedback. now i am trying to flash it but i faced "adb device not found" error
ok done
managed to flash it back to an older version and everything works now
thanks a lot for your help! cheers
Make sure to update it eventually because you could run into issues when flashing stuff if your recovery isn't up to date.
No problem!
Hello,
I apologise, this may be a long post, but I do need to explain exactly where I am at otherwise I will get recycled answers that I have already googled and tried and failed.
I recently bought a 'bricked' nexus s from eBay to play with and see what I could do.
It was previously stuck on the Google logo at boot. This is what I did...
1) I was able to boot into the bootloader (volume up + power etc) and unlock the bootloader.
2) I flashed the official bootloader, radio and Jelly bean zip file (from Google) to the phone. It failed at flashing system.img
3) I flashed ICS again failed flashing system.img
4) I flashed Gingerbread, SUCCESS...the phone booted!
5) The phone booted to the lock pattern screen of the previous owner.
6) I contacted the previous owner, and asked for the pattern. He gave me a pattern...it was wrong.
7) Booted into android stock recovery and attempted to factory reset. Booted to lock pattern screen.
8) Flashed clockworkmod recovery and attempted to factory reset. Booted to lock screen.
9) Flashed twrp and attempted to factory reset. Booted to lock screen.
10) In custom recovery, mounted "SD card" to computer, manually deleted former owners stuff, which reappears after un mounting.
11) Copied across various custom roms, all fail to install.
12) Turn to xda...
I just want to clear out the phone and start again.
The model is i9020t. I'm doing everything through fastboot and adb doesn't work because I cant get into the phone to enable debugging.
If anyone has any original ideas, please help.
Sent from my GT-I9300 using xda app-developers app
RufusFlambard said:
Hello,
I apologise, this may be a long post, but I do need to explain exactly where I am at otherwise I will get recycled answers that I have already googled and tried and failed.
I recently bought a 'bricked' nexus s from eBay to play with and see what I could do.
It was previously stuck on the Google logo at boot. This is what I did...
1) I was able to boot into the bootloader (volume up + power etc) and unlock the bootloader.
2) I flashed the official bootloader, radio and Jelly bean zip file (from Google) to the phone. It failed at flashing system.img
3) I flashed ICS again failed flashing system.img
4) I flashed Gingerbread, SUCCESS...the phone booted!
5) The phone booted to the lock pattern screen of the previous owner.
6) I contacted the previous owner, and asked for the pattern. He gave me a pattern...it was wrong.
7) Booted into android stock recovery and attempted to factory reset. Booted to lock pattern screen.
8) Flashed clockworkmod recovery and attempted to factory reset. Booted to lock screen.
9) Flashed twrp and attempted to factory reset. Booted to lock screen.
10) In custom recovery, mounted "SD card" to computer, manually deleted former owners stuff, which reappears after un mounting.
11) Copied across various custom roms, all fail to install.
12) Turn to xda...
I just want to clear out the phone and start again.
The model is i9020t. I'm doing everything through fastboot and adb doesn't work because I cant get into the phone to enable debugging.
If anyone has any original ideas, please help.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hi, did you try to use Nexus Root Tool kit??
RufusFlambard said:
Hello,
I apologise, this may be a long post, but I do need to explain exactly where I am at otherwise I will get recycled answers that I have already googled and tried and failed.
I recently bought a 'bricked' nexus s from eBay to play with and see what I could do.
It was previously stuck on the Google logo at boot. This is what I did...
1) I was able to boot into the bootloader (volume up + power etc) and unlock the bootloader.
2) I flashed the official bootloader, radio and Jelly bean zip file (from Google) to the phone. It failed at flashing system.img
3) I flashed ICS again failed flashing system.img
4) I flashed Gingerbread, SUCCESS...the phone booted!
5) The phone booted to the lock pattern screen of the previous owner.
6) I contacted the previous owner, and asked for the pattern. He gave me a pattern...it was wrong.
7) Booted into android stock recovery and attempted to factory reset. Booted to lock pattern screen.
8) Flashed clockworkmod recovery and attempted to factory reset. Booted to lock screen.
9) Flashed twrp and attempted to factory reset. Booted to lock screen.
10) In custom recovery, mounted "SD card" to computer, manually deleted former owners stuff, which reappears after un mounting.
11) Copied across various custom roms, all fail to install.
12) Turn to xda...
I just want to clear out the phone and start again.
The model is i9020t. I'm doing everything through fastboot and adb doesn't work because I cant get into the phone to enable debugging.
If anyone has any original ideas, please help.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You can try the Nexus Root Toolkit at: http://www.wugfresh.com/nrt/
XDA Thread: http://forum.xda-developers.com/showthread.php?t=1766475
Thanks guys, I tried it but no such luck.
From what I gather the toolkit is basically automating the fastboot and adb commands, as the same problems ensued. Adb couldn't find the phone because there is no way to enable usb debugging, and fastboot did what it did, but userdata is left untouched.
Sent from my GT-I9300 using xda app-developers app
RufusFlambard said:
Thanks guys, I tried it but no such luck.
From what I gather the toolkit is basically automating the fastboot and adb commands, as the same problems ensued. Adb couldn't find the phone because there is no way to enable usb debugging, and fastboot did what it did, but userdata is left untouched.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Use the toolkit.. Boot to bootloader (NOT RECOVERY).. Tell the toolkit what version of android you are on and that you are bricked and want to flash to stock.. Change usb ports if it doesn't immediately recognize that you are connected.. It will not need to be debugged to revert to stock..
follow prompts and you are done!
Remember that you will not be rooted and won't have a custom recovery any more and will need to reflash these.. Some roms are pre-rooted..
i have unlock root, and install cmw with my a701. first i tried CyanogenMod, after that Evil Purgatory ROM...
after that i tried to back to stock rom. after several day struggling in "assert failed: getprop("ro.product.device")", finally i can pass the error...
but after i run the update.zip, they ask me about flash recovery (i answer yes), and rood device (i answer no), after reboot, the device stuck in iconia tab logo, (after acer, animation, then iconia tab logo). after the i tried to run the recovery, but it always stuck in "recovery verified failed..."
i have no idea how to enter fastboot or adb.
there's nothing i can do to the device right now...
any idea how to enter fastboot or adb, or fix my a701?
please help me, i already search all around xda, cannot find the solution, every solution need to enter adb mode or fastboot mode...
I have the exact same problem now. Has anyone found a solution to this?
Many thanks
EDIT: FIXED! For anyone experiencing a similar problem, I managed to recover mine by powering on, holding Volume + (one dot) and repeatedly switching the rotation lock switch. This gave the messaging wiping user data, and wiping cache, and it rebooted as it should! Good luck.
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.
So, I just decided to try and Flash the old TF101 with Katkiss 6.0.1 and Gapps, but I always get stuck on the same problem.
My TF101 is running Android 4.0.3 ICS and USB Debugging is on
I downloaded TWRP app on the transformer, as well as the latest .blob flash file through the app.
Before this, I rooted the tablet using Kingroot.apk, which worked. When I went to flash the tablet with the recovery, the app noted "Recovery Partition not found".
I tried to boot into recovery mode on my own, (Pressing Pwr + Volume down , Then hitting Volume Up), The android screen popped, up and then flashed to a fallen android with a red triangle.... The screen stays on this for a minute and then boots into the normal system. I can't even boot into recovery through ADB, using the
Code:
adb reboot recovery
, The tablet will just reboot normally, not into recovery mode.
The Device does recognize through ADB....
Is my recovery partition just non existent? Even when I just let the system though without pressing volume up, it only gives me the option of (Android) or (Erase Data). when I click erase data, ill stay on the asus loading screen indefinitely and nothing will happen until i turn it off and on.
I just cant seem to boot into TWRP for some reason, and that means I just cant install the downloaded custom ROM.
How Can I fix this and boot into TWRP? I've tried for hours and have been hung up due to the same problem each time, even after rooting.
Did you already solve that problem? I also need a solution.Thanks