I was using the latest TWRP 2.1 and CM9 nightly. When I clicked reboot to recovery, now my TP just keeps blinking TWRP's logo page, like in a loop. Now if I press power and home buttons to restart, it will go to recovery directly and then enter the infinite loop again... Anyone knows how I can fix that
p.s. while it's in the loop, using webOS doctor doesn't seem to be able to detect the device.
webOS doctor will only recognize it when it's in dev mode (the mode with the big usb sign on it). It wont detect anything if you're bootlooping.
You want to go into webos recovery, not cwm
^^ +1
You have to reboot holding the UP button (which you should know if you installed Android). From there either doctor or ACMEUninstall and then reinstall... though I don't think doctoring will be needed if you can do ACMEUninstall.
If you are looking to doctor, make your device restart and then immediately hold the volume up button. This will display a usb symbol and put you in recovery mode. Start the webOS doctor and plug your device in when it asks you to.
Thanks for the help guys!! My TP revived! I forgot about the holding volume_up key feature because flashing android was like years ago
Related
Hi everyone. First time poster here. I'm having problems with my Samsung Apollo (i5801). I was at first going to root my phone, but before even getting to there, I was trying to access recovery mode so that I could fix a USB error (USB would not be detected when plugging into PC, only charged). I don't know what ended up happening, but now I am stuck in a rut.
Trying to hold Volume Up + Down, Home, and Powering on leads to the exclamation mark triangle android screen. Pushing the home button after that just leads to a reboot.
Holding Volume Down + Home and powering on leads to a blue "DOWNLOADING DO NOT TURN OFF" screen which I get stuck on.
Holding Volume Up + Home leads to a "Forced upload by key pressing" screen.
My phone still cannot access any boot menu and still cannot connect by USB to my PC.
I have not rooted anything and the firmware was on 2.1 Eclair before this whole thing happened.
Any ideas or suggestions would be grateful. Thank you!
Well seems like you can access Download mode just fine, so how about flashing it?
2 things here
you cant actualy access a boot menu on a stock apollo, you need to flash a firmware to it first
and the reason your pc cant connect to the handset is you most likely dont have the samsung drivers installed
http://forum.xda-developers.com/showthread.php?t=778880
this thread should help plenty same handset, just called something else
hope this helps
I installed CWM initially, but it never rebooted automatically after installing. I rebooted it manually and all hell broke loose. The only way that I can start g tab now is if I use nvflash. Once I got the system working, I tried shutting down and then getting into CWM again, but a no go. It doesn't even start regularly, with just the power button being pressed. Any advice?
It turns out that I am stuck in the APX mode all the time. If I press just the power button, the APX mode comes on. How can I get out of it?
another topic (SOUNDS LIKE SAME PROBLEM)
aboy7 said:
It turns out that I am stuck in the APX mode all the time. If I press just the power button, the APX mode comes on. How can I get out of it?
Click to expand...
Click to collapse
Try this thread I think they have the same issue..
http://forum.xda-developers.com/showthread.php?t=903684
Other wise of course there is always NVFLash
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
Help!
My Tablet S keeps going to the boot animation when trying to connect to the wifi. It appears that once it can connect to my home router it jumps into the boot animation, which stops the wifi, then the tablet will try to connect again. Upon connection it'll loop back into the boot animation. This just loops over and over again.
Tried turning it off and then back on, no luck. Factory reset works, but it this problem comes back.
Any ideas?
what can be is you have to install something wrong or ideally where you bought it back and give you another of the insurance so that error may be the device
Thats what I thought 2 at first...but a factory reset would've removed any faulty apps. U could try a factory reset from recovery mode tho.
For this, shut down tablet and start it by holding both power and Volume up key. Once in recovery mode navigate with ur Vol. down key to factory reset and select it with the power key.
Hope this helps.
I was trying the get into usb mode to fast boot but ended up clicking wipe system, now android and everything is gone including clockwork mod recovery. Not even the bootloader will work, I have tried clicking the power button and the volume up/down and it still doesn't pop up on the screen. Is there a way to install android again threw usb without doing anything on the tablet because I can't do anything on the tablet. Though when I hold the power and the volume down key at the same time when its connected to the computer a driver window poped up saying abx or something?
Hey everyone,
I have a family members Nexus S here, it was painfully slow on Cyanogenmod11 (4.4.4), so I tied to revert it to CM9 (for 4.0/ICS).
I cleared the cache and dalvik cache, but I think forgetting to clear data is why it's in a boot loop now.
But anyways, the problem is in the title, this power button doesn't work, and without being in either recovery or booted into the OS I can't get ADB to connect to it to just reinstall the ROM from my PC.
I can get it to the bootloader screen by pressing volume up while putting the battery back in, but weirdly after that it won't let me use volume up or down to move around the menu, nor the capacitive buttons, while it normally did allow me to do that when I used to get in there through clockworkmod.
Any ideas?
The sparknotes, again, are no power button, won't boot, can't connect to PC. I did search similar problems, but only came up with fixes surrounding either the power button or getting it to connect to PC.
I got fastboot installed on my Mac, just not sure exactly what to do. I tried putting fastboot reboot-recovery into terminal, it says command fastboot not found, even though fastboot installed fine.
Anyone? Halp?
Final desperate bump