Related
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
lunzi88 said:
Hi All, as the title states, I'm currently stuck in a CWM bootloop after trying to applying the new OTA update on my rooted transformer.
I know it was kinda stupid of it.
I tried following the steps posted here, but i can't seem to get adb to push the file through.
I must admit that I'm not very good with using command prompts and i have no idea if I'm doing it right.
Steps I'm sure i'm doing right so far.
I opened up my cmd and cd C:\android-sdk\platform-tools
When typing adb devices, my transformer is successfully recognized as 0123456789ABCDEF OFFLINE
However, the next part got me slightly confused.
I had typed in C:\android-sdk\platform-tools>adb push C:\cwm_recovery-5027_rogue_rburrow-tf101-r1.zip /sdcard/download.
However, i kept encountering the error that the device is offline.
I had also set up a marco to press the up arrow+enter key with a 10ms pause in between followed by a 1 second pause before repeating.
However, the file was still unable to be pushed to the device despite countless tries.
I'm not sure if it's because the line i had entered was wrong or was it due to some other factor.
Would someone be kind enough to help me take a look and see if i had done something wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
pierrekid said:
Damn man sorry to hear that. Def should have flashed stock recovery before applying the OTA. Im sure one of these guys can help you out though good luck!
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
yeah dude, i realised that after i googled for a fix.
prior to this my experience with OTA updates on rooted+CWM phones had never encounter such problem.
The most that had happened previously was that the update failed to be installed.
I had no idea it could get stuck in a loop i couldnt get out of.
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
thanks for the tip.
I can't try it right now as I left the tablet at home when I left for work today.
I'll update once I get back home to try it.
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
The words are not even popping up for me, it just shows the asus logo and then goes straight into recovery. I go into adb devices and it shows OFFLINE aswell.
:S
baseballfanz said:
when you're doing adb devices, is your tablet in recovery or off?
try this,
push and hold vol down plus power button
when you see words at top left corner, wait a while till you see options to wipe data or cold boot.
Select cold boot to see ifnyou can boot into OS
Click to expand...
Click to collapse
That's what I did when it happened to me. Worked like a charm.
I did the same thing and I'm stuck too.
Sent from my Kindle Fire using xda premium
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
lamaqc said:
Same problem here for the same reason...flash ota update on my root tablet....I'm always on cwm recovery when reboot. I'm able to cold boot it when holding.vol down and power but I do I get around this cwm ecovwry bootloop? Thanks
Envoyé depuis mon HTC Glacier avec Tapatalk
Click to expand...
Click to collapse
Same here. The only way I can boot now is VolDown + Power. Another thread recommended flashing some stock-like ROM, but I'd rather not.
Has someone found out how to boot normally?
I have to cold boot everytime my device reboots or it shuts off, which is quite often.
The cold boot method is becoming really annoying.
Thanks!
Found a way!
Hi guys! This is my first post helping somebody
So I found a way to make it boot normally...
What you need to do is to cold boot your device.
Then download from the store Android Terminal Emulator.
Open it up and type in:
Code:
su
Allow SuperUser if prompted.
If you get # then you are good to go!
Now you need to type in:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Once it's done, reboot your tablet and you should see a progress bar.
Let it load and once it's done, you have your tablet back!
Hope it works!
Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..
i am reading all that i can find and try, but cant seem to get this Transformer Tf101 out of boot loop, cant believe i never heard or saw that clockwork would do this, can someone point me in the direction i need to be in to fix this awesome tablet. Thanks
mikehe said:
i am reading all that i can find and try, but cant seem to get this Transformer Tf101 out of boot loop, cant believe i never heard or saw that clockwork would do this, can someone point me in the direction i need to be in to fix this awesome tablet. Thanks
Click to expand...
Click to collapse
PERI should work (http://forum.xda-developers.com/showthread.php?t=1681155)
JoinTheRealms said:
PERI should work (http://forum.xda-developers.com/showthread.php?t=1681155)
Click to expand...
Click to collapse
tried that but i cant seem to get the drivers for tablet loaded its in clock work recovery 5.8.3.4 screen right now, let me try again
trying to get win 7 (64) see this thing is a ***** cant seem to get it to see drivers and i cant find adb package if there is one
Try the recovery from 1 click root app, working fine think its rogue 1.3
Sent from my HTC One X using xda premium
I have the same problem with my tf101 and this recovery, have tried flashing other recoveries and changing kernels etc but whilst clockwork says its flashing fine it doesnt seem to get it out of the bootloop and just always loops back into the same 5.8.3.4 recovery. adb doesnt seem to be working either as it is coming up just as 'transformer' in other devices in the device manager and cant find any drivers or wont let me install the adb ones for it. Not sure what to do was just swapping recoveries as I needed to flash an update off my sdcard and this recovery didnt seem to have that option.
Any luck fixing it? Peri or one click root dont seem to be working because of the missing drivers I am assuming?
Whoops silly me forgot to do a cold boot into the OS that fixed it....
Sent from my Transformer TF101 using xda app-developers app
ok if i power off tablet hold volume down then when it starts into recovery, if i dont do anything it will show a screen that gives 2 options "wipe data" and "android" if i just wait a few seconds it will boot up into cynagenmod rom and tablets works, but anytime i try to use boot into recovery it throws it back into CWR and then the loop starts again. how do i get this CWR off of tablet.
mikehe said:
ok if i power off tablet hold volume down then when it starts into recovery, if i dont do anything it will show a screen that gives 2 options "wipe data" and "android" if i just wait a few seconds it will boot up into cynagenmod rom and tablets works, but anytime i try to use boot into recovery it throws it back into CWR and then the loop starts again. how do i get this CWR off of tablet.
Click to expand...
Click to collapse
You need to get rid of that "bad" recovery. Go to the dev section, get one of the recovery there, your choice doesn't matter.
boot into recovery and flash the new recovery.
When done don't use reboot option in the recovery.
Use the Vol down plus power button and let it get to the 2 options of wipe data or cold boot linux (just like you did earlier).
Once it boot to your OS use terminal (free in Play Store).
Open terminal and type in the following
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
*press ENTER after each line.
what do u mean dev section and recovery, i loaded the asus recovery install.apk loaded that i get into terminal but i dont know cmd syntax at all so in the second line of ur instruction what does the "|" represent
if i did it right i get message that says cannot open for write: no such file or directory
Dev = Development
Go to the development section and get either Roach's version of CWM, TeamWin recovery or Team Rouge recovery.
That "|" is a verticle bar.
If you're keyboard don't have it, get Hacker's keyboard.
ok i flashed rogue recovery and will try the terminal commands again
ok now i get 5+0 records in
5+0 records out
5 bytes transfered, is that a good sign
Thank You baseballfanz for you help, shes back in action
That's good to gear.
Hey Guys,
I've been on android since the G1. I've troubleshooted all problems I've had since flashing cyanogenmod when he was first on xda. With this Nexus 7, however, I've kept it completely stock.
I've had it for a month and it's been great. Yesterday I downloaded a homeland torrent and watched it. Put it down, came back two hours later and it was on a black screen (it was charged when I left at least to 50% after d/l and watching the video). I pressed the power button and it wouldn't start. I finally held it down for about 30 seconds and then it went to the "Google" screen all in white letters. It stayed there. I tried holding power for 10, 20, 30, 40, 50, 60 seconds and it would just reboot to the google screen. I finally tried to enter fastboot, i was able to, and got excited at being at a functional screen that I went into "recovery" and then the google screen just popped back up. Now I can't even get into fastboot.
I've tried the nexus toolkits but they both need either abd in android or the fastboot screen. I can't get into them. I finally called google play devices support and they said they will email me within two days to replace my nexus 7. However, I'd like to get my stored images, music, videos, etc off of there at the very least (although, I'd much rather fix it and keep it).
Can you guys suggest anything?
tl;dr : Stuck on google screen, can't enter fastboot. Is there anything I can do to make it boot? Option 2: how can I at least take my (emulated /virtual) sd card data out of it?
THANKS!
You are rebooting each time you try fastboot, correct?
Sent from my Nexus 7 using Tapatalk HD
Correct. It goes black for about three seconds then back to Google screen indefinitely
Sent from my HTC VLE_U using xda app-developers app
Bump?
Wow, I see criticism every time someone mentions they're "Bricked." Now that someone finally is bricked--or at least it seems like--no one is saying anything...
What happens if you hold all 3 keys for ~30-40 seconds, it should, at that point, reboot to the bootloader.
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
mihahn said:
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Thanks guys!
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, holding all three, holding power and volume up, holding power and volume down doesn't work. I've tried holding power until it restarts and then doing power and volume down, up, and both. Nada.
I appreciate your input guys. I'll just return the product to google... hopefully they don't fix it without a full wipe and get ahold of my files! Yeek!
AW: [Q] Stuck on Google Screen- Cannot enter fastboot
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
But I guess the best is to replace it
Sent from my SK17i running Android 4.1.2
mihahn said:
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
Click to expand...
Click to collapse
He said he was 100% stock.
The stock recovery doesn't start up the adbd daemon. That's typical for stock recoveries.
Proves the point that even if you stay with stock on the N7, you should unlock the bootloader as soon as you get the device. Then the option of soft-booting a different recovery (fastboot boot recovery.img) would be available for rescue situations - even if the ROM stays completely stock and unrooted.
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
When your device is on and showing Google
Press and hold the Power key till the screen goes black
Once black, press and hold the volume down key
This will take you to fastboot
Press volume key up twice then power key to select
Device should now be in recovery mode
If you wiped the OS, use Wugs Toolkit to recover from soft brick in advanced options
If you want to push files to your device and try to recover, use MSKIP's Toolkit
Hope this helps....good luck
Sent from my Nexus 7 using XDA Premium HD app
dwny said:
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
Click to expand...
Click to collapse
Nope, not unlocked, rooted or have a custom recovery.
Hey guys
I tried the one-click root toolkit for mac from android rootz.
Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help
When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset
My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok.
Sent from my Nexus 10 using Tapatalk HD
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
scooterbaga said:
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
Click to expand...
Click to collapse
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
bg1906 said:
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
Click to expand...
Click to collapse
Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time.
With a now bootable device, I'm off to replace the recovery... Thanks again.
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Hyflex said:
Hey,
I need some help with my Nexus 10, it's stuck at the moment.
I ran fastboot oem unlock via the Samsung Google Nexus 10 ToolKit 1.3.0 (updated for 4.2.2) and as soon as it was done it rebooted and was stuck...
Booting normally it gets to the bootlogo and just sits there forever, going round and round and round.
If I try to boot into fastboot it shows that it's unlocked but I can't change change to recovery using the volume rocker it's just a solid static screen, only choice is to start which boots back into the normal boot logo.
I have no way to use adb or fastboot... it's just stuck :/ How do I recover/unbrick this?
Any help would be much appreciated.
Click to expand...
Click to collapse
Reboot holding Power and both volume buttons and you should be able to get to recovery
brees75 said:
Reboot holding Power and both volume buttons and you should be able to get to recovery
Click to expand...
Click to collapse
I'm on the xda-devs irc at the moment and we've got so far... but still its messed up.
- Recovery is dead (can't get into it atm, orange triangle guy every time)
- Flashed stock via fastboot and unrooted, but on reboot I get the triangle guy.
- I can boot into unsecure roms (temporary)
- I can boot into temporary recoverys, clearing cache works but davlik cache and factory reset doesn't work both say "failed"
I'm currently awaiting the guy whos been helping me get back from the shops.
From what I remember you need to either install something or run a command after "oem unlock" for security reasons. Android wont let you boot back into the OS until you have wiped all the data after the unlock.
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
altimax98 said:
The orange guy means it's working. There's a button combo to hit at that screen to get the recovery to boot. Once there do a factory reset and your done.
That's why toolkits sick, they teach you nothing and when they break your stuck
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
The pressing 3 buttons at once; cycling to recovery... method wasnt working because there was no recovery accessable what so ever and temporary recoveries weren't working.
That's what a few guys in IRC said too about the toolkits haha
Thankfully some guy by the name of YellowGTO spent some time helping me out and we finally got there in the end, he's awesome and extremely patient
jlvlawrence said:
Can you flash a factory image to it via fastboot?
Rock Chalk Jayhawk!
Click to expand...
Click to collapse
Okay, updates for everyone just incase someone else gets the problem.
- Factory Images via fastboot flashed fine but never stuck, just kept returning me to triangle dude.
- Fix permissions, did nothing
- Restoring stock recovery did nothing, I still couldn't get to a recovery.
- Temporary recoveries only had limited functionality.
I decided to unlock an already unlocked phone again
I flashed stock, Ran file permissions
Used the temporary recovery to clear the cache/davlik (previously didn't work)
I re-rooted, Installed TWRP 2.4.4.0, this finally stuck.
I double checked that it had stuck by booting the system, rebooting into recovery, powering device of and powering it on to Android. It was all working perfectly.
I then made my backup and put a custom rom and kernel on, it's working lovely now.
It seems that somewhere during the oem unlock it messed up some partitions or something resulting in recoveries and flashing not to work/stick.
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Good to hear it's working for you. The issue is that the stock N10 bootloader does not wipe the data partitions correctly as it should. So after an unlock you need to go into the stock recovery and wipe it. Boot once, then go and flash all your flasheys
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That's the thing, the recovery wasn't available in any way shape or form and temporary recoveries wouldn't wipe the cache... the oem unlock went wrong somehow even though it had full power, wasn't interrupted or anything.
I'm glad it's all working now, I thought the device was completely dead at one stage.
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
anazei said:
I think you had the problem almost everyone runs into:
As you can see in the video, you just have to try for a bit to actually get the recovery menu to open - My heart dropped a little before I knew that as well
Click to expand...
Click to collapse
I think you are right and that was his problem..... The toolkit actually told him how to handle this ... but who reads all the that text anyway