I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
stuck on animation loop
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
shadowarez said:
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
Click to expand...
Click to collapse
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
didnt you install clockwork mod first?
slap_shot_12 said:
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
Click to expand...
Click to collapse
the thing i found showed me to installed the clockwork mod first before i did any flashing, i rooted device then i flashed once clockwork mod was installed, i had to root, then install rom manager and goo manager, from within there i installed the clockwork recovery script/mod then i proceeded to flash chromi-X DEODEX.
Did you flash the correct bootloader? I had the same problem, look for my posts in the last few pages of ChromiX.
Here: http://forum.xda-developers.com/showpost.php?p=41658701&postcount=2716
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
buhohitr said:
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
Click to expand...
Click to collapse
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
slap_shot_12 said:
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
Click to expand...
Click to collapse
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
You are truly a god among men.
buhohitr said:
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
Click to expand...
Click to collapse
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Somehow the stock recovery was reinstalled on your tablet, thus letting this method work. It however does not on CWM or TWRP. All you did was manually reinstall a stock rom back onto your tablet. How it got the stock recovery is beyond me unless you flashed a stock ROM from CWM and didnt realize what you were installing.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Since the JB 4.2.1 upgrade, this is the most reliable method to install Asus full stock firmware. Also, since you're unlocked, let root the device by go here http://forum.xda-developers.com/showthread.php?t=2230763 download the tool and root it. Once rooted, I suggest that you should install TWRP custom recovery, by download Goomanager from the market, open the app and tab on the 3 little boxes on the top right hand corner, select "install recovery scripts" , this will shutdown your device and install custom TWRP recovery script, once this installed, you can download "rebooter" from the market and this app has many options, one of them is allowed you easily boot into custom recovery.
Related
Hey everyone,
I got a Nexus S that gets stuck on the Google logo when it starts up. I can get the phone into the bootloader and I can also clear the data from the phone but that hasn't fixed it. If you have any suggestions, please respond to the thread. Thank you!
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
brenix said:
I had this issue once for some reason... I had to take out the battery and put it back in, then boot into recovery and wipe the cache/davlik cache... Have you tried that yet??
Click to expand...
Click to collapse
Yah, i just did it and it didnt solve my problem but thanks for the suggestions
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
lostgoatX7 said:
Sounds to me like you flashed an incompatible kernel. Have you recently flashed anything?
Click to expand...
Click to collapse
No but the person I purchased it from might have. Does anyone know how to load stock android becuase I'm not experienced with rooting.
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
any solution?
hi guys.i have the same issue.does anyone have a solution for this?
i had the same problem.....what i did was cleared everything on recovery and flashed cyanogenmod and now is all good (this was of course after changing my underwear lol )
Smokexz said:
Looks like he bricked it, lucky for you, it's a Nexus. You have to find a stock Gingerbread ROM and flash it with ODIN or maybe through recovery. Look around for a stock ROM.
Sent from my Xoom
Click to expand...
Click to collapse
how can I do it?
I got the same problem.
Nexus S stuck at Google lOgo
I have the same Issue
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....
Similar problem
Ahoy!
I have a similar problem. Bought the phone in the States so I'm not in a position to go into psychological warfare with some poor high school kid working in Best Buy. Plus, all this is totally my fault...
I dropped my phone down the can (if it was a Blackberry I would have flushed) and manged to rescue it through handy desiccant (open shoe box gel packets) and rediscovering religion *cough* until this is sorted *cough*.
When I eventually fired her back up (the battery had flatlined btw) I'm stuck on the Google screen. So battle commenced...
The phone was stock 2.3.4, never rooted, no CW Recovery.
T-Mobile I9020T.
I sorted the Win 7 USB device issue
Can see it with fastboot but not adb.
Can access the bootloader screen so tried the Recovery option but it just goes into Google splash screen each time.
Flashed various versions of CW recovery (herring, mecha) to it but hitting the Recovery menu on the bootloader screen just keeps going to the Google splash screen.
This is where I complicated things because I'm a complete and utter noob to the rooting game.
I'm fairly sure I was careless early on with the appropriate versions of the full stock and singular recovery images I was trying to flash, so this might be useful information.
I downloaded ODIN and tried it briefly but it didn't seem to recognise my phone (I keep reading the ODIN needs to be tricked into recognising the phone). I also keep reading the ODIN is unnecessary if you have fastboot access so let this line of inquiry slide.
I downloaded a full Clockwork Mod Stock Nandroid (Stock-GRH78-Nandroid) and attempted to flash it all. The boot img failed due to a "FAILED exceed blocks" problem, so I tried this (classic noob try anything):
"Got a failure when trying to flash back a 8Mb boot.img?
From example above I started from a boot.img smaller than the full boot partition but if you create a new boot.img or start from an image of the full partition taken manually or with clockworkmod, boot.img will be 8Mb-large (8388608) and fastboot fails with "FAILED exceed blocks 0x00000020 > 0x0000001e".
I'm not really sure about what size the file should be but as it's filled with zeroes till reaching 8Mb, I decided to cut it:
0x00000020 => 0x0000001e means for me 8388608 / 0x20 * 0x1e = 7864320, so I did:
dd if=boot.img of=boot2.img bs=262144 count=30
fastboot flash boot boot2.img"
Click to expand...
Click to collapse
This worked! noob W1NNAR!!!11one111!!
I got the same thing with the recovery and the same "trick" worked. When it got around to the system img it eventually failed with a "Magic number" problem. Checking this problem out made me realise I can't keep messing around and should "get help".
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
hand_of_henry said:
As a further note I'm aware that the recovery can get flashed each time to stock after a reboot so I've been flashing CW Recovery and then trying to boot into Recovery straight away. Still getting stuck on the Google Splash screen.
I haven't found anyone with my problem that couldn't get sorted with CW so I'm either completely boned or missing something ridiculously easy. Been trying things for over a week - I'm getting close to selling her for scrap.
Click to expand...
Click to collapse
Do "fastboot erase recovery" then flash a different ClockworkMod build. Try 3.0.2.4
Sent from my Nexus S using XDA App
Thanks Matt.
Just tried erasing (hadn't before) and flashing 3.0.2.4 - no dice. Tried erasing and 3.0.2.5 and no luck either.
twitch153 said:
Have you turned S-Off?
-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
Click to expand...
Click to collapse
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
hand_of_henry said:
Maybe I'm missing a blindingly obvious step.
My exact steps are:
Starting phone into bootloader screen (Volume + Up)
Erasing the recovery (as of Mike's post above)
Flashing the recovery (ensuring the recovery file is named "recovery.img")
On success of that selecting the Recovery menu item.
Each time I get Google Splash screen.
Click to expand...
Click to collapse
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
asafru said:
Try to use fastboot to go into recovery directly instead of flashing recovery and choosing it from the bootloader menu.
"fastboot boot recovery.img" and see how this goes.
Edit: try this recovery as well
http://forum.xda-developers.com/showthread.php?t=988686
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks asafru,
I tried booting into recovery but again, no luck. I did it with one of the recovery builds you suggested (the cyan recovery but having trawled that thread I'm not sure what the difference is between the colours).
matt2053 said:
How long do you wait on the splash screen? I recall this happening to me once but I thinkbi just let it sit and recovery eventually showed up after a while.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's a fair point - I had expected to see the recovery screen fairly sharpish.
I've waited 15 minutes now on the splash screen for flashings of cw 3.0.2.4, 3.0.2.5 and the mysterious cyan build of 4.0.0.2.
I imagine this is an appropriate amount of time for the recovery to kick in?
I've tried all these recoveries using the Recovery menu item and also using the booting directly recovery method that asafru suggests above.
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Did you wipe before restore?
davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!
DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....
Then NVFlash will fail still...
davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/
Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?
Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision
Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.
Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?
Hello all
just did the ICS w/root flash upgrade to my xoom cause it was wheezing, on it's last leg. funny thing after using the modded cwm factory reset/ wipe this that everything.
then used cwm to install the upgrade. installed root explorer. and to my surprise all my old data/dir's are still on the sd card
WTF this is gonna be a problem? or not?
thanks
Calm down, why is your question so angry? LOL
You are now rooted - so even a factory data reset from CWM will not erase your internal SDcard Data. It is not a problem, you can manually erase your un needed data from Root Explorer if need be. Is all good, no worries.
endless loop
Thanks for your reply. this xooms been giving me fits for a 3 days now.
started having to reinstall a few new games. then TB started messing up
did a factory reset and lost use of the home button.
so i tried to install tiamat, on reboot all i get is a little white revolving kinda circle on the bottom right of screen.
tried installing wingray that worked. til i powered the xoom down. on reboot it gets stuck in the pulsating ics screen. only way to get it to boot is too reflash and then it boots
so everytime i power down it gets stuck in loop.
can anybody help with this? is it hardware?
thank you
WarrantyVoided said:
Thanks for your reply. this xooms been giving me fits for a 3 days now.
started having to reinstall a few new games. then TB started messing up
did a factory reset and lost use of the home button.
so i tried to install tiamat, on reboot all i get is a little white revolving kinda circle on the bottom right of screen.
tried installing wingray that worked. til i powered the xoom down. on reboot it gets stuck in the pulsating ics screen. only way to get it to boot is too reflash and then it boots
so everytime i power down it gets stuck in loop.
can anybody help with this? is it hardware?
thank you
Click to expand...
Click to collapse
Which version of Xoom are you using?
xoom wifi u.s. 32g
WarrantyVoided said:
xoom wifi u.s. 32g
Click to expand...
Click to collapse
Sounds like it might be the software. What system image did you use to root? Did you flash the GAPPs as well, when you flashed the ROM? Unroot, go back to stock. Start from scratch Re-Root then flash the Wingray ROM and the GAPPS from here : This is a pretty solid ROM Let us know.
http://forum.xda-developers.com/showthread.php?t=1484770
Thanks
just found the way to flash back to 3.01,
now it boots everytime i turn it back on. geez that ics was a nightmare, wonder why?
first thing it did was start downloading updates
what version is the easiest to root?
holy crap, it's only updated like 6 times now, its now working on ics
WarrantyVoided said:
holy crap, it's only updated like 6 times now, its now working on ics
Click to expand...
Click to collapse
I really does not matter which version you are on before root, because you are going
to push a dif image on there anyway. Great you are back to stock and have a clean
slate to work with!
1. Downloading the rooting-update zip file.
Download the zip file from here - http://goo.gl/Om9aP
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
2. Flashing recovery
1. Download this Recovery image. http://bit.ly/iLRAIV (place this image in you SDK PlatformTools Folder, or which ever folder that contains your adb.exe)
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
the xoom came along way today, from semi brick to ics with cwm. but the universal root tool did not work root explorer/cwm cannot get su.
dang sure learned alot today
i found the update.zip in that script from xxlordxx and did all that but it did not work
did the same thing with the link you provided here and it work.
thanks for all your help.
what benefits are gained using tiamat
WarrantyVoided said:
what benefits are gained using tiamat
Click to expand...
Click to collapse
It depends on your taste. I sent you the link to that ROM because it is STABLE and you can flash it just to make sure that your system is working correctly. It's best to try a few diff ROMs and see which one best suits your needs!---------- Post added at 12:37 PM ---------- Previous post was at 12:32 PM ----------
WarrantyVoided said:
the xoom came along way today, from semi brick to ics with cwm. but the universal root tool did not work root explorer/cwm cannot get su.
dang sure learned alot today
i found the update.zip in that script from xxlordxx and did all that but it did not work
did the same thing with the link you provided here and it work.
thanks for all your help.
Click to expand...
Click to collapse
Sure, no problem.
I thought it would be cool to see what the fuss is about rooting and loading a custom ROM but I just dont see the point after playing around the last few days.
I followed the rooting instructions online for the HTC One S ville and then made it to the loading Clockwork Recovery onto the phone and performing an Nandroid backup like it suggested. Well thats where I ran into the issue of not being able to boot into anything else afterwards it would just keep booting to Clockwork Recovery screen. I figured out that I have to hold the power button for 10 seconds and then it will boot properly to stock android ROM. So once I figured that out I began using the tutorial to load the Viper ROM. Once I loaded the viper rom I ran into an issue at step #11
After you configured it, reboot to your bootloader in fastboot mode
Click to expand...
Click to collapse
I stopped there because I was still stuck at the issue of being booted to the Clockword Recovery screen and unable to get to the bootloader screen. Even now if I shutdown my phone it just restarts to the Clockwork Recovery screen and I have to do the 10 second power button trick to get around it. (remember I did not complete steps 11-20 from post #5 here on the instructions)
http://forum.xda-developers.com/showthread.php?t=1850917
So I was just wondering what I should do to get back to complete stock android rom and see about unrooting my phone.
jerm said:
I thought it would be cool to see what the fuss is about rooting and loading a custom ROM but I just dont see the point after playing around the last few days.
I followed the rooting instructions online for the HTC One S ville and then made it to the loading Clockwork Recovery onto the phone and performing an Nandroid backup like it suggested. Well thats where I ran into the issue of not being able to boot into anything else afterwards it would just keep booting to Clockwork Recovery screen. I figured out that I have to hold the power button for 10 seconds and then it will boot properly to stock android ROM. So once I figured that out I began using the tutorial to load the Viper ROM. Once I loaded the viper rom I ran into an issue at step #11
I stopped there because I was still stuck at the issue of being booted to the Clockword Recovery screen and unable to get to the bootloader screen. Even now if I shutdown my phone it just restarts to the Clockwork Recovery screen and I have to do the 10 second power button trick to get around it. (remember I did not complete steps 11-20 from post #5 here on the instructions)
http://forum.xda-developers.com/showthread.php?t=1850917
So I was just wondering what I should do to get back to complete stock android rom and see about unrooting my phone.
Click to expand...
Click to collapse
Did you wide data/cache before you flashed your custom rom?
There are several ways to get back to your stock rom... If you made a backup of your stock rom via cwm just restore it.. if you didnt make a backup just find the correct ruu for your device and flash it that way, if you dont have super cid you will need to find the correct ruu or it will not flash. If you need any more infomation please let me know and i will do my best to help you out step by step.
jerm said:
I thought it would be cool to see what the fuss is about rooting and loading a custom ROM but I just dont see the point after playing around the last few days.
I followed the rooting instructions online for the HTC One S ville and then made it to the loading Clockwork Recovery onto the phone and performing an Nandroid backup like it suggested. Well thats where I ran into the issue of not being able to boot into anything else afterwards it would just keep booting to Clockwork Recovery screen. I figured out that I have to hold the power button for 10 seconds and then it will boot properly to stock android ROM. So once I figured that out I began using the tutorial to load the Viper ROM. Once I loaded the viper rom I ran into an issue at step #11
I stopped there because I was still stuck at the issue of being booted to the Clockword Recovery screen and unable to get to the bootloader screen. Even now if I shutdown my phone it just restarts to the Clockwork Recovery screen and I have to do the 10 second power button trick to get around it. (remember I did not complete steps 11-20 from post #5 here on the instructions)
http://forum.xda-developers.com/showthread.php?t=1850917
So I was just wondering what I should do to get back to complete stock android rom and see about unrooting my phone.
Click to expand...
Click to collapse
Keep trying to get into the bootloader with holding the power for 10 seconds then as soon you see stop flashing hold the Vol- and power then use the all-in-one kit to install TWRP recovery then you wont have this problem any more and you will still need to fastboot boot.img for the rom to work.
PEP-C said:
Did you wide data/cache before you flashed your custom rom?
There are several ways to get back to your stock rom... If you made a backup of your stock rom via cwm just restore it.. if you didnt make a backup just find the correct ruu for your device and flash it that way, if you dont have super cid you will need to find the correct ruu or it will not flash. If you need any more infomation please let me know and i will do my best to help you out step by step.
Click to expand...
Click to collapse
No i did not clear the cache or the dalvik cache....im not sure if i wiped data to be honest since it was a few months back. I still have not wiped either caches as of now either.
I'm going to try to download twrp or whatever from the android market right now
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.
Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.
success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!
stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.
jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good: