So im running 3.1 rooted with the 1.4.4 Tiamat Kernel. I had this weird force closing issue where gapps would force close whenever i tried to connect to wifi. I powered down, turned on, and am now stuck in a boot animation loop. I can hold down the Vol Down button and it says "Starting Fastboot Protocol Support." but nothing changes. Is there anything I can do it fix it/turn it off until i get home to my computer with the SDK? On another note I did install the wpa supplicant (sp?) files to allow it to connect to an adhoc wifi source (eris tether). Please and thank you
EDIT: I have booted into recovery, but I am unable to mount any of the drive locations or wipe them. I did a factory data reset (as much as it could I guess?), but im still at the boot loop.
Hook it up to computer while its in fastboot and open a command prompt from the folder you have fastboot. Type "fastboot reboot-bootloader" and you should get adb to recognize, then push stock images or root images and recovery.
What recovery were you using? Did you flash the one from ROM manager?
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
razor532 said:
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
Click to expand...
Click to collapse
You will need to flash a good recovery, I suggest you you use the .img file in this thread through adb when you get to your laptop:
http://forum.xda-developers.com/showthread.php?t=1074979
The recovery version you updated to won't look at your external sdcard, so you can't flash from it until you re-install a good recovery.
Can't we get a pinned warning about this issue?
Thanks everyone, sorry for the delay. I ended up fixing it with a fastboot oem unlock command. However after countless flashes unable to get it to boot again i realized i was flashing the tiamat rom and then a different tiamat kernel boot.img, most likely the culprit in my boot loop. The minute i did a factory reset, updated cwr and only flashed the rom, everything works fine. Thanks for everyones help
Sent from my Eris using XDA App
So glad you were able to fix it!
Related
Hi Guys,
replaced my wpa_supplicant file in a failed attempt to get adhoc connectivity. Now I have the dreaded boot loop.
If I try recovery mode, I get an exclamation mark so thats a no go. The phone shows up in device manager on XP as "Android ADB Interface", but ADB device list is empty.
Any help much appreciated,
Regards
ross
Every time you boot the phone the NS rewrites the recovery back to stock. You MUST flash a custom recovery EVERY TIME (unless you rename the stock recovery img, search for how to do it on xda) That's why you can't get into recovery.
Sent from my NS running NSCollab cuz I lost my tin cans and string....
rossc007 said:
Hi Guys,
replaced my wpa_supplicant file in a failed attempt to get adhoc connectivity. Now I have the dreaded boot loop.
If I try recovery mode, I get an exclamation mark so thats a no go. The phone shows up in device manager on XP as "Android ADB Interface", but ADB device list is empty.
Any help much appreciated,
Regards
ross
Click to expand...
Click to collapse
Babydoll25 said:
Every time you boot the phone the NS rewrites the recovery back to stock. You MUST flash a custom recovery EVERY TIME (unless you rename the stock recovery img, search for how to do it on xda) That's why you can't get into recovery.
Sent from my NS running NSCollab cuz I lost my tin cans and string....
Click to expand...
Click to collapse
thats not true, you dont have to flash the custom recovery every time. i bet cw recovery was flashed through rom manager, thats why its not there right now. what you want to do is flash the recovery through fastboot, then it will stick.
Thanks for the replies guys, I've made progress but I'm still have issues.
I'm relatively new to this so forgive me if my understanding of the process isnt what it should be. I've flashed a recovery mod (recovery-clockwork-3.0.2.4-crespo.img) using fastboot via the SDK. The file was uploaded successfully. I reboot the phone and I still get the boot loop problem after about 20 secs.
I assume that the recovery mod doesnt replace the wpa_supplicant file that I've put on the phone. Is there a way for me to access the file system and restore the backup I made? ADB wont detect the phone, but fastboot does :S
Again, help much appreciated!
if you can get into clockwork recovery, you can restore your backup from there , if you made a backup. Myself, i always have at least 3 different roms on phone in case of boot loop, has happen to me before.After you have reflashed clockwork recovery, make sure you reflash root file as well
Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.
Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again
Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?
^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.
but, how can I overwrite it? it seems like they are read only...
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:
No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
Ive looked around the internet, and here, and cant really figure something out. Do I have to install CM10 from fastboot or can I just install the zip using TWRP?
I ask because I tried installing the stable version of CM10 using TWRP and when I reboot I just get the spinning Cyanogenmod logo for a long time. Nothing ever happens.
Am I doing something wrong?
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I will do that right now. Appreciate the help.
Is flashimagegui an android app? Thats the only reference to it I can find.
Yes it is. There is a donation version on play store. Or there's an xda free version if you search the forums
Sent from my HTC One XL using xda app-developers app
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
JohnnyDanger said:
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
Click to expand...
Click to collapse
what version of hboot is on your device? if it is one of the later ones (1.12+) then you'll need to flash the boot img seperately. If this is the case, (and it sounds like it , as the same thing happened to me and the symptoms where the same).
Extract it from the ROM that you are flashing (open the zip file and drag out the boot.img). Then while TWRP is running, connect the USB cable to your comp and fire up a terminal (you'll need ADB/fastboot set up and working - search google or XDA for how to do it in your operating system).
Once you have adb/fastboot working and TWRP running -> at a terminal (or command prompt on windows) use adb to push the rom onto the sdcard, and then reboot to bootloader and select fastboot.
run "fastboot flash boot boot.img" without the quotes. This should write the kernel image to the boot partition, and then you should be able to load TWRP to (wipe cache/dalvik and then) reflash cyanogen mod.
Good luck
If you can still boot into recovery, you're fine. Manually flash the CM10 boot.img with fastboot, do a full wipe in TWRP and then reinstall the CM10 zip + gapps. Should be good after that.
Thanks for the info, from both of you. Im going to try that right now.
Im trying to flash the boot.img file, but I keep getting an error. Any ideas?
Heres what I get
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (5248 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
codeprimate said:
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
Click to expand...
Click to collapse
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
JohnnyDanger said:
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
Click to expand...
Click to collapse
can you get into TWRP? if you can, go to the mount menu and see if you can unmount and then remount the sdcard. If you can do this, then you have no need to do the team-nocturnal sdcard fix.
I was able to unmount and then remount the sdcard. Actually, when I went into Mount menu in TWRP to begin with it gave me the option to Mount, then unmount. Is that the same thing? Does that mean my sdcard is not mounted and should I mount it in TWRP?
I was finally able to flash the boot.img. I then went into TWRP to install CM10. It installed and now is back into the spinning logo. Im ready to give up on this. Any more suggestions?
Just a thought, should I be removing the boot.img from the CM10 zip Im trying to install?
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
area51avenger said:
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
JohnnyDanger said:
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
Click to expand...
Click to collapse
No worries man, good luck with your One X, I hope the worst is behind you now.
If you are feeling confident, there is a method to downgrade your hboot so you don't need to stuff around flashing the boot image separately. This however does involve bricking and then de-bricking your device, and you'll need a linux computer to pull it off, so this isn't for everyone.
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!