powered up with PWR and (-) key and wont come out of it
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.
skip this, finally woke it up...on to next problem thanks all
When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev
ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...
my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.
I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim
blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.
roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.
nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in APX mode...
I have no idea how this happened, but basically my XOOM has spontaneously broken itself. I was using it like normal, just watching some videos over TVersity and I noticed it started running a little slow. So I restarted it and it never got past the boot animation and hasn't since.
I figured I would try a factory reset under Recovery, but it won't work because it can't even find the internal sdcard. I can't mount the sdcard, I can't wipe it, I can't do anything with it.
I'm hoping someone here might know what to do? Or if not, how can I remove all traces of ClockworkMod Recovery so I can exchange it without them claiming I somehow broke it?
Could reflashing the boot and recovery with the stock images possibly fix this problem, or are they also kept on the internal sdcard and therefore untouchable while the XOOM is in this state?
If your pc can recognise your xoom and connect, you can flash the official images from Moto and recover your xoom with adb, unlike me.
http://forum.xda-developers.com/showthread.php?t=1108505
This thread has all the info you need to reflash to your stock Xoom.
But then again, you may not need to go this far. Perhaps just hang around until someone with much more knowledge can help you.
flombs said:
If your pc can recognise your xoom and connect, you can flash the official images from Moto and recover your xoom with adb, unlike me.
http://forum.xda-developers.com/showthread.php?t=1108505
This thread has all the info you need to reflash to your stock Xoom.
But then again, you may not need to go this far. Perhaps just hang around until someone with much more knowledge can help you.
Click to expand...
Click to collapse
Thanks for that, I'll hold out for an easier solution but I appreciate your advice as a fall-back plan
I wish I could have that as a fallback plan. Can't even connect my Xoom to my PC. oh...wait...
I would like to start off by introducing myself (and apologize if this is in the wrong section). I'm Zach Anyways, I have a 1st gen Kindle Fire and I think I bricked it. I got the replacement one from Amazon and promptly rooted with KFU and installed CWM instead of TWRP. I later decided I didn't like CWM and wanted to go to back to TWRP. From inside of CWM, I deleted and cleared my caches, factory reset, wiped the SD card, and then put the update.zip from Amazon onto the root of my SD card while mounted from within CWM. I flashed it, rebooted, and it is now stuck at the "Kindle Fire" splash screen. Kindle Fire Utility tells me my ADB is online, however the boot status is unknown. I have basically tried every option in KFU and nothing is working. Also, the Unbrick Utility is a piece of s**t and never works, even with ADB. Am I screwed here? I really need my Kindle because there are apps on there that I absolutely require. I really don't want to order/make a factory cable either. Someone please help.
http://forum.xda-developers.com/forumdisplay.php?f=1561
Might be just in the wrong boot mode, the good people in the kindle fire q&a forum will help you.
I fixed it by doing the USB boot mode trick (taking the back off and shorting a metal contact point) everything is working fine now!
Sent from my Amazon Kindle Fire using xda app-developers app
Any help appreciated. I was trying to install second bootloader to my kfhd7 and HAD twrp working and when trying to complete the process upon reboot when the red triangle recovery screen showed up(i thought nothing of it) and it asked to restore device or something else, i believe i chose the restore option. ever since i have been stuck at the splash screen with orange kindle fire replaying over and over. I made a flimsy fastboot cable(which is now broke, I ordered a skorpn one) and was able to get into fastboot but i absolutely cannot get the device recognized in fastboot or adb. Mind you i had the drivers/adb working previously. I fear that without FB recognition on my pc I will be SOL... running windows 8 and FB cable should be here tomorrow or next day. wanna be prepared when they arrive. In advance thank anyone who helps for your help.
psver the last week im pretty sure i've read almost every kfhd7 post out there and haven't found one exactly like this. do not seem to find anyone else having some much trouble getting ADB/Fastboot to see device as me when in this situation(used to be the easiest part for me).
Sorry if this is in the wrong section but i'm at a loss. Ok so here is my dilemma. I rooted my friends f60 using kingo root. I was going to install a de-bloated rom to give her more space but it was late and I never got around to finding a suitable rom so I just left her with the rooted phone. Well she ended up having someone else flash cyanogenmod and I guess there were bugs. Her camera didn't work and and kinda laggy. Well she the same guy come back and "fix it" and I have no clue as to what he did. the phone doesn't power on and I can't get it into download mode or fastboot. When I plug it into the comp it vibrates and the windows chime dings notifying something has been connected to it. When I go to view the drive the only thing in it is an image folder nothing else? Luckily I saved a badckup of her phone when I did the initial root. Can I just flash that back? If so how do I even get the phone to be detected?
http://forum.xda-developers.com/showthread.php?t=863209
Thread closed