Related
hi all i have a T-mobile G2X and im trying to root this phone so... i try to flash CWM using NVFLASH and everything goes according to plan but once i try to boot into recovery by pressing both volume up and down buttons nothing happens. Once i flash stock recovery phone boots and everything is back to normal but once i flash either version same thing happens again. I tried searching but couldn't find a solution. So if anyone can help me or point me to the right direction i will appreciate it.
You boot into CWM recovery by holding power + volume down (do not touch volume up). Hold the keys a good 10 seconds and wait for the fancy LG logo. Once you see the fancy LG logo (not plain white) you can let the keys go. You will then boot into CWM. You are just pressing the wrong keys. Don't boot that way into stock recovery as it will do a factory reset on your phone.
I seem to be having the same problem, except that my phone only shows the s/w update screen and wont revert back to the stock recovery when i try. nvflash just leaves my phone on the update screen for hours. it will boot up normal if i pull the battery and put it back in, but it only shows the s/w update screen when i try to boot into recovery. any thoughts?
To boot into Clock Work Mod Recovery, you press and hold the "volume down key" and the "power/sleep" button at the same time.
Hold the buttons all the way through the Lg boot logo. After a short moment, you will see a distinct "purplish" bluish glow to the logo. At that time, release both buttons.
You will boot into Clock Work Mod Recover and ready for flashing
or use the Terminal:
$su
#reboot recovery
prettyboy85712 said:
or use the Terminal:
$su
#reboot recovery
Click to expand...
Click to collapse
This command does not work on the P999. Recovery is not on the standard partition and this command will only reboot the phone. To reboot into recovery (if you have CWM installed on the physical recovery partition and not installed by ROM Manager) you need either Weapon Rom installed, which has this built in or there is an app on the Android Market written specifically for LG 2X/G2X devices that knows where the recovery is installed and can reboot into it. On some G2X (P999) models it says not compatible because of the way LG wrote the build.prop but instead of saying "Ok" which closes the program you simply use the back key to get to the main program screen and it works like a charm.
This app is also preinstalled as a system app on my roms.
Market link: https://market.android.com/details?...SwxLDUwMCwiY29tLm1heGlzbWEubGdvMnhyZWJvb3QiXQ..
Thank You everyone for ur help. Ive figure everything out and im now running MIUI ROM.
Hello,
After installing and running OTA Rootkeeper on my TF101 B80 with a rooted ICS ROM (http://forum.xda-developers.com/showthread.php?t=1514658), the tablet keeps booting to ClockworkMod Recovery (v3.1.0.1). I searched XDA Developers and tried different solutions (including flashing the stock ROM from ASUS) to no avail. Apparently, I'm not the first one having this problem, but I can't for the life of me find a solution. I'd be grateful for any help and pointers. Thanks!
Try this in recovery.
Advanced -- Wipe Dalvik Cache
Wipe -- Wipe Cache
Wipe -- Factory Reset/Clear Data
Install zip from SD card (Pick any rooted ICS rom, make sure to follow installation carefully)
Then after that hit rebootin cwm recovery
See if that works.
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Hi guys,
Thank you for your replies. I tried to wipe data/cache/Dalvik cache several times and flash different ROMs. Still no dice.
Cold booting didn't work either. The system gets stuck at the "Cold-booting Linux" message.
What else should I try? Thanks!
Full wipe is needed prior flashing a full rom.
In your case, check out wolf's thread in general section about flashing and recovery even without root.. it might be useful there..
Sent from my awesome rooted Defy: 2.3.6
baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
thanks , this worked for me!
for the last week I was stuck manually cold booting every time I wanted to turn it on.
markp1989 said:
thanks , this worked for me!
for the last week I was stuck manually cold booting every time I wanted to turn it on.
Click to expand...
Click to collapse
Thanks so much for this info - I was stuck in a loop of rebooting only to Clockmod recovery and could not get out of it! This worked for me.
fsxpilot said:
Thanks so much for this info - I was stuck in a loop of rebooting only to Clockmod recovery and could not get out of it! This worked for me.
Click to expand...
Click to collapse
I had this issue with CWM 5.5.0.4 a while back, (incidentally also with the most current version of CWM) and the script worked, however.. when i flashed anything in recovery it would revert back to the recovery loop. Let me know if you experience that same issue. I'm having trouble installing a lot of the newer ROMS (JB)
baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
THIS!!!
Worked for me as well!!
THANKS
baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
If i'm not mistaken, this will fix the bootloop issue. but i noticed that it wouldn't boot into recovery with power options or reboot apps. The only way i could get into recovery was using power and vol down then press vol +. I fixed this by flashing a new recovery, cold boot, enter echo boot in cmd, then reboot which installed the recovery. after that it worked normally.
kernel null said:
I had this issue with CWM 5.5.0.4 a while back, (incidentally also with the most current version of CWM) and the script worked, however.. when i flashed anything in recovery it would revert back to the recovery loop. Let me know if you experience that same issue. I'm having trouble installing a lot of the newer ROMS (JB)
Click to expand...
Click to collapse
Install a new recovery... I suggest twrp
Sent from my Transformer TF101 using xda app-developers app
Worked like a charm. Had me going crazy for a while. Thanks
baseballfanz said:
Try this.
Hold Vol down + Power button till you get the options of cold boot or wipe data,
choose cold boot.
Once you've booted your rom , run terminal emulator.
(Terminal Emulator, free in Play Store if you don't already have it)
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : reboot
Click to expand...
Click to collapse
the cold boot option worked for me thanks !!!!
Ok, so here is a problem I have never had with an android device....
I cannot get my tablet to boot into recovery..I have done it in the past as I installed revolver a long time ago (HTK75.revolver-3.11_epad-8.6.5.21-20111216)
Now I cannot get into the recovery to install a new rom....
I have rooted the phone, Good to Go.
I have downloaded and ran the recovery installer app....
I have tried using the reboot to recovery app (reboot to recovery) which just reboots and keeps my transformer at the ASUS boot screen.
I have tried the power + volume down option and this is what I get:
Android US_epad-user bootloader <e> released by "US_epad-8.6.5.21-20111216
checking for android ota recovery
skiping android ota checking
checking for RCK.. press key <VOL_UP> in 5 sec to enter RCK (So I press it)
Booting recovery kernel image
Thats is...it jsut sits there until I reboot it back to normal again....
Any advice!? I have tried so many different options I have read about on the boards...(plus google)
Try using PERI rooted option to reflash recovery, or run in term emulator with blob on device,
su
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot
I have tried so many different apps and this one finally worked!!!!!
Your awesome, thanks man!
Thanks given
Glad it worked well :]
reset in a circle while trying to flash
Sorry for my english
Can I ask you to describe step by step how you recovered your tablet
updating its firmware tf300t 4.0.3 to 4.1 encountered a similar problem:
The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120604" A03
Checking for android ota recovery
Booting recovery kernel image
When rebooted around and only the volume up button can turn it off.
How do you advise to try to recover it, if you can explain step by step
Alternatively see the use of this program [TOOL]PERI-0.4
http://forum.xda-developers.com/showthread.php?t=1681155
p.s. missed one point in which the boot program and should be used as a stop / pause
this cycle if it is necessary to use the program as confused with one thing:
(EG don't let any commands run at the splash screen or in recovery.)
I recently flashed revolver 4.1.1 and a new kernel but for some reason my tablet always boots to the CWM recovery unless i do the power+vol down then itll go to the wipe or cold boot screenand boot into the OS. This started when the revolver arts downloaded the 4.1.1 patch and booted to recovery and i couldnt find the 4.1.1 patch and rebooted, downloaded it with my browser and installed it.
Any way i can set it back to boot directly to the OS?
Sent from my Transformer TF101 using Tapatalk 2
If you booted from os into recovery then that is the trouble maker. For some reason our transformer 's can't handle it that well.
One of the first topics here goes about this problem.
http://forum.xda-developers.com/showthread.php?t=1671598
The solution is too flash another recovery. And that can be done in the recovery itself with another version you can find here. They made an whole topic over the problem.
http://forum.xda-developers.com/showthread.php?t=1213723
If you experience problems like it won't flash the recovery over the other one.
You have too revert back too clockworkmod 3.2.0.1 of 3.1.0.1 by flashing.
so if your done flashing 3.2.0.2 you can upgrade it again with 5.5.0.4 or even touch recovery 5.8.1.8
So remember "don't boot from os into recovery anymore after doing the above" otherwise you have the same problems. Eventually you can use reboot into recovery apk from the market safe if i recall
deerhurst said:
I recently flashed revolver 4.1.1 and a new kernel but for some reason my tablet always boots to the CWM recovery unless i do the power+vol down then itll go to the wipe or cold boot screenand boot into the OS. This started when the revolver arts downloaded the 4.1.1 patch and booted to recovery and i couldnt find the 4.1.1 patch and rebooted, downloaded it with my browser and installed it.
Any way i can set it back to boot directly to the OS?
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
What recovery version are you using?
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
batjuh said:
If you booted from os into recovery then that is the trouble maker. For some reason our transformer 's can't handle it that well.
One of the first topics here goes about this problem.
http://forum.xda-developers.com/showthread.php?t=1671598
The solution is too flash another recovery. And that can be done in the recovery itself with another version you can find here. They made an whole topic over the problem.
http://forum.xda-developers.com/showthread.php?t=1213723
If you experience problems like it won't flash the recovery over the other one.
You have too revert back too clockworkmod 3.2.0.1 of 3.1.0.1 by flashing.
so if your done flashing 3.2.0.2 you can upgrade it again with 5.5.0.4 or even touch recovery 5.8.1.8
So remember "don't boot from os into recovery anymore after doing the above" otherwise you have the same problems. Eventually you can use reboot into recovery apk from the market safe if i recall
Click to expand...
Click to collapse
Revolver used to have the option to reboot to recovery which I used multiple times and never had any issue. I'm currently using Gummy which reboots you to recovery whether you choose normal reboot or reboot to recovery and still no issues otherwise. I just choose reboot in the recovery and it reboots fine from there.
sidneyk said:
What recovery version are you using?
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
Revolver used to have the option to reboot to recovery which I used multiple times and never had any issue. I'm currently using Gummy which reboots you to recovery whether you choose normal reboot or reboot to recovery and still no issues otherwise. I just choose reboot in the recovery and it reboots fine from there.
Click to expand...
Click to collapse
Im on cwm 5.8.3.4. I used the reboot to recovery in revolver parts. Its just annoying but doesnt prevent using the device.
Sent from my Transformer TF101 using Tapatalk 2
deerhurst said:
Im on cwm 5.8.3.4. I used the reboot to recovery in revolver parts. Its just annoying but doesnt prevent using the device.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
That looks like a version that came from ROM Manager and may be your trouble. What happens when you choose normal reboot from the Revolver power menu?
Like hold power button and choose from the menu? Same thing. Next cold boot goes to recovery.
Yup, rom manager updated.
Haven't tried rebooting from revolver parts yet, didn't even think of it.
deerhurst said:
Like hold power button and choose from the menu? Same thing. Next cold boot goes to recovery.
Yup, rom manager updated.
Haven't tried rebooting from revolver parts yet, didn't even think of it.
Click to expand...
Click to collapse
You might try Team Rogue XM Touch Recovery. It will read both internal and external cards and works well. You may need to apply the fix mentioned in Roach's recovery thread first if it still boots to recovery after.
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
batjuh said:
If you booted from os into recovery then that is the trouble maker. For some reason our transformer 's can't handle it that well.
One of the first topics here goes about this problem.
http://forum.xda-developers.com/showthread.php?t=1671598
The solution is too flash another recovery. And that can be done in the recovery itself with another version you can find here. They made an whole topic over the problem.
http://forum.xda-developers.com/showthread.php?t=1213723
If you experience problems like it won't flash the recovery over the other one.
You have too revert back too clockworkmod 3.2.0.1 of 3.1.0.1 by flashing.
so if your done flashing 3.2.0.2 you can upgrade it again with 5.5.0.4 or even touch recovery 5.8.1.8
So remember "don't boot from os into recovery anymore after doing the above" otherwise you have the same problems. Eventually you can use reboot into recovery apk from the market safe if i recall
Click to expand...
Click to collapse
Finally got a chance to mess with this issue. It wont flash over the current recovery with 3.2.0.1 or .3.1.0.1 or the 5.8.1.8 touch. Getting into recovery by rebooting and letting the messed up recovery thing boot into its self and then selecting the zip to flash.
Sent from my Transformer TF101 using Tapatalk 2
SOLVED
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
[...]
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
I only needed this to stop booting directly into recovery. Thanks!
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
I have been trying to fix this annoying recovery loop for the last 3 days and this fixed it. Kudos to you good sir :good:
Thanks man!
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
Thanks so much man! Your method really works. It saved me from losing faith entirely in the android community! :good:
karenlightning said:
Thanks so much man! Your method really works. It saved me from losing faith entirely in the android community! :good:
Click to expand...
Click to collapse
it's nice to see you all happy :laugh::laugh::laugh::laugh:
I have the same error but in cwm recovery i have "E:can't mount /sdcard/" issue and then i can't flash new recovery..
thanks
So here's my issue... I'm stuck in CWM 5.8.3.4, can't boot into android, stuck in recovery... wanted to flash different recovery, but unless I'm blind I can't get 5.8.3.4 to see the SD Card (external) to flash a file... any ideas on what my options are...
Can't get to Android either, CM10 splash screen keeps spinning..
Update:Resolved my issue by using EasyFlasher
badbullet said:
seems that you have recovery loop problem so try this: Download clockworkmod recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
in recovery, select flash zip from sdcard and select the recovery zip you downloaded
once it has flashed the zip file, don't reboot but hold power button to shot down
power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Click to expand...
Click to collapse
thank you so much buddy!
Phone is not powering up, i think it is dead.
Badbullet said:
Seems that you have recovery loop problem so try this: Download ClockworkMod Recovery v5.5.0.4 roach-tf101-r2 from here :
http://forum.xda-developers.com/attachment.php?attachmentid=934821&d=1331070176
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, don't reboot but hold power button to shot down
Power on your device and boot in android. Download terminal emulator from market and type this:
Code:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Reboot
Click to expand...
Click to collapse
I did same but when i tried to power up the at the end, it wont power up neither charge....
Has anyone else had issues with getting the various JellyBean ROMs for the Transformer TF101 to boot the first time?
I have tried 3 ROMs now, Cyanogen 10, EOS and rayman33's AOSP build. They all install successfully but none of them boot to the OS, they all just sit at their respective animated boot screen.
I've left each one of them sitting for an hour or more and they never finish booting, so it's not a case of me being impatient.
Has anyone else had this? Were you able to solve it, if so, how?
Thanks
aussiedude said:
Has anyone else had issues with getting the various JellyBean ROMs for the Transformer TF101 to boot the first time?
I have tried 3 ROMs now, Cyanogen 10, EOS and rayman33's AOSP build. They all install successfully but none of them boot to the OS, they all just sit at their respective animated boot screen.
I've left each one of them sitting for an hour or more and they never finish booting, so it's not a case of me being impatient.
Has anyone else had this? Were you able to solve it, if so, how?
Thanks
Click to expand...
Click to collapse
I'm having the same issue. What Recovery are you using? By any chance, did you install CWM 5.5.0.4 and get stuck in that recovery loop before?
kernel null said:
I'm having the same issue. What Recovery are you using? By any chance, did you install CWM 5.5.0.4 and get stuck in that recovery loop before?
Click to expand...
Click to collapse
You might be onto something there. I did install CWM 5.5.0.4, I never resolved the recovery loop because I rebooted the device so infrequently it was never a problem, until now it seems.
aussiedude said:
You might be onto something there. I did install CWM 5.5.0.4, I never resolved the recovery loop because I rebooted the device so infrequently it was never a problem, until now it seems.
Click to expand...
Click to collapse
I flashed a newer CWM recovery, then ran the script using SU (either in ADB shell or terminal emulator)
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 and it started booting up fine. However, every time I flash anything in recovery, it goes back to the recovery boot. This is why you and I are having to go through the Cold Boot Linux option... thats where mine freezes with one JB ROM and I go into an infinity logo loop with EOS JB ROM...
kernel null said:
I flashed a newer CWM recovery, then ran the script using SU (either in ADB shell or terminal emulator)
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 and it started booting up fine. However, every time I flash anything in recovery, it goes back to the recovery boot. This is why you and I are having to go through the Cold Boot Linux option... thats where mine freezes with one JB ROM and I go into an infinity logo loop with EOS JB ROM...
Click to expand...
Click to collapse
Try flashing a new recovery. I did this and eliminated the bootloop, mine was caused by updating to .27 while having cwm. I have yet to try a jelly bean rom. I had this issue, flashed teamwin 2.2 touch recovery then cold booted, entered the echo boot cmd in terminal emulator. then restarted tablet which then installed the new recovery and then a reboot performed as expected. Hope this helps.
itj1228 said:
Try flashing a new recovery. I did this and eliminated the bootloop, mine was caused by updating to .27 while having cwm. I have yet to try a jelly bean rom. I had this issue, flashed teamwin 2.2 touch recovery then cold booted, entered the echo boot cmd in terminal emulator. then restarted tablet which then installed the new recovery and then a reboot performed as expected. Hope this helps.
Click to expand...
Click to collapse
I did this just now. Perfect... however, I am not able to access my Internal SD Card. Am I doing something wrong?
*Scratch that, i see all of my files
Update: I did this, and I was able to flash JB. No problems. It takes some getting used to, its not familiar to me yet... i accidentally flashed the ROM, then wiped dalvik cache, and forgot to erase/factory default... luckily it booted fine and actually kept all my old settings upgrading from EOS ICS
I still haven't resolved my boot loop problem aaarrrggghhh!!!
I'm sure once I do all will be well.
Thanks guys
Sent from my Nexus 7 using Tapatalk 2
aussiedude said:
I still haven't resolved my boot loop problem aaarrrggghhh!!!
I'm sure once I do all will be well.
Thanks guys
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Have you tried this? (http://forum.xda-developers.com/showthread.php?t=1681155) if not it should work
Did you try the steps above? Using the cmd echo boot....
Sent from my Transformer TF101 using xda app-developers app
JoinTheRealms said:
Have you tried this? (http://forum.xda-developers.com/showthread.php?t=1681155) if not it should work
Click to expand...
Click to collapse
That did the trick, thanks!!
And I have CM10 booted. Thanks to all who helped get this resolved!! :good:
aussiedude said:
And I have CM10 booted. Thanks to all who helped get this resolved!! :good:
Click to expand...
Click to collapse
When you guys are stuck on the boot logo, how do you reboot the tablet? I'm stuck on boot animation for 10 minutes now, and have no idea how to shut it off, or reboot or go back to recovery. Tried holding power button for 5/10/30 seconds, tried holding power button in combination with Vol- and Vol+ respectivly, nothing. The only thing I can see is just waiting for the battery to die :/
Tried plugging in usb cable, no response out of adb.
ME TOO! I just got the ASUS TF101-X1 from Groupon. Not sure what the model number is. My S/N starts C3OKA and there's RTF101 on here too.
I loaded the TEAM EOS JellyBean ROM and got stuck at the animation logo just after the TEAM EOS appeared. Freaked me out. I, finally, managed to get the Revolver ICS flashed and I'm back up and running,
dulcedosa said:
ME TOO! I just got the ASUS TF101-X1 from Groupon. Not sure what the model number is. My S/N starts C3OKA and there's RTF101 on here too.
I loaded the TEAM EOS JellyBean ROM and got stuck at the animation logo just after the TEAM EOS appeared. Freaked me out. I, finally, managed to get the Revolver ICS flashed and I'm back up and running,
Click to expand...
Click to collapse
I take it that when you were stuck on the animation logo, you just pressed and held the power button and it shut off? This is the problem I have right now is that it won't turn off for me. So, its just staying at that animation until presumably it will shut off once the battery drains.
Luckily, I had just flashed Team Rogue recovery just before I flashed the 8/1/12 TEAM EOS JellyBean ROM.
To get to recovery, press and hold Power + Volume Down, then press Volume Up when prompted <- You have to be fast.
I would try flashing [ROM] Revolver 4 by Gnufabio | 4.1.1 Stable - IC411 | Jun 23 | FaceUnlock | APM
dulcedosa said:
Luckily, I had just flashed Team Rogue recovery just before I flashed the 8/1/12 TEAM EOS JellyBean ROM.
To be to recovery, press and hold Power + Volume Up, then press Volume Up when prompted. You have to be fast.
I would try flashing [ROM] Revolver 4 by Gnufabio | 4.1.1 Stable - IC411 | Jun 23 | FaceUnlock | APM
Click to expand...
Click to collapse
That's the problem I have right now tho, is that my TF101 is stuck on the boot animation logo, and I can't get it to go anywhere. It will not turn off with pressing and holding the power button (tried for 10 seconds, 30 seconds, 1 minute, etc). I have CWM on there, so, I guess once my battery dies, and shuts the tablet off, I'll be able to power it back up again. I really wish there was some sort of physical switch that cuts the power to the tablet, because obviously the 'power' button doesn't do it.
I found this over at Transformerforums: "--Hold down the Power button and the Volume Up buttom, at the same time, for 10 seconds. The TF101 will shut itself off, screen will be black. After a minute, hold down the Power button and the Volume Down button, at the same time, for 10 seconds. The screen will come on about 30 sec after you release the buttons.
"
http://www.transformerforums.com/fo...-reset-hard-reset-factory-reset-no-avail.html
cquilliam said:
That's the problem I have right now tho, is that my TF101 is stuck on the boot animation logo, and I can't get it to go anywhere. It will not turn off with pressing and holding the power button (tried for 10 seconds, 30 seconds, 1 minute, etc). I have CWM on there, so, I guess once my battery dies, and shuts the tablet off, I'll be able to power it back up again. I really wish there was some sort of physical switch that cuts the power to the tablet, because obviously the 'power' button doesn't do it.
Click to expand...
Click to collapse
dulcedosa said:
I found this over at Transformerforums: "--Hold down the Power button and the Volume Up buttom, at the same time, for 10 seconds. The TF101 will shut itself off, screen will be black."
Click to expand...
Click to collapse
This puts your tablet in APX mode. It does not shut it down.
I say the simplest way to fix the boot loop is
1. boot into recovery MANUALLY (dont EVER use "boot to recovery" power-menu, ROM manager boot to recovery etc. This is what is causing your bootloops). Manually means holding power+volume DOWN until it says "push volume up", then you push volume up.
2. while in recovery, using adb, run the echo boot commands as listed earlier in this thread.
And to be able to turn off tablet even with bootloops...
3. from recovery, if not running team win recovery, flash team win recovery. You can use adb to transfer files to the tablet while in recovery.
Code:
adb push teamwinrecoverything.zip /sdcard/
4. from team win recovery, chose power off.
The key to unlocking (almost) any Android problem on any Android device is knowing adb and knowing when to use it
Do not flash while docked
I was FINALLY able to get TEAM EOS JB loaded!
A lesson for all n00bs like me.
DO NOT FLASH WHILE DOCKED! I repeat DO NOT FLASH WHILE DOCKED!
Quite by accident, I figured out that flashing while docked caused the JB ROM to stay stuck at the boot animation. As soon as I undocked, after a few seconds, the boot process proceeded and voila! JELLYBEAN!
josteink said:
This puts your tablet in APX mode. It does not shut it down.
I say the simplest way to fix the boot loop is
1. boot into recovery MANUALLY (dont EVER use "boot to recovery" power-menu, ROM manager boot to recovery etc. This is what is causing your bootloops). Manually means holding power+volume DOWN until it says "push volume up", then you push volume up.
2. while in recovery, using adb, run the echo boot commands as listed earlier in this thread.
And to be able to turn off tablet even with bootloops...
3. from recovery, if not running team win recovery, flash team win recovery. You can use adb to transfer files to the tablet while in recovery.
Code:
adb push teamwinrecoverything.zip /sdcard/
4. from team win recovery, chose power off.
The key to unlocking (almost) any Android problem on any Android device is knowing adb and knowing when to use it
Click to expand...
Click to collapse
I posted this else where, so hopefully it isn't looked at as spamming, but when I was trying different ROMs I could not get wifi to work. It was like my Prime didn't see the wireless radio. After two days of u successful ROMs, I ran across "fix permissions" in CWM. This seemed to clear up the issue. I hope this helps somebody, I couldn't find anything referencing this issue.
Sent from my Transformer Prime TF201 using xda app-developers app