Related
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 an lg g2 vs980 and i rooted it but have not yet installed a recovery like twrp it is only the very basic root with super user. it decided to install some ota update and now it will not boot past lg screen, white letters flash really fast all i could make out was secure boot error or something. i cannot get it into any kind of download or reset mode, iv tried absolutely everything anyone on this forum has recommended or suggested and nothing works, also when i connect it to my pc running windows 8 it is seen as QSUSB_BULK i have installed the correct updated drivers for my phone and iv manually installed them, nothing i have done will allow my pc to see my phone correctly. when i plug it in it under computer there are local drives f-u that pop up and say i have to format them in order to use them, but they are write protected so i cannot view whats in them, format them or anything. does anyone out there have any kind of suggestion to fix this or am i just completely stupid and missing some big major step? i am also very new to android this is my first android phone lol im a converted apple user haha so the more indept detailed instructions would be greatly appreciated
Same issue here
haeli said:
i have an lg g2 vs980 and i rooted it but have not yet installed a recovery like twrp it is only the very basic root with super user. it decided to install some ota update and now it will not boot past lg screen, white letters flash really fast all i could make out was secure boot error or something. i cannot get it into any kind of download or reset mode, iv tried absolutely everything anyone on this forum has recommended or suggested and nothing works, also when i connect it to my pc running windows 8 it is seen as QSUSB_BULK i have installed the correct updated drivers for my phone and iv manually installed them, nothing i have done will allow my pc to see my phone correctly. when i plug it in it under computer there are local drives f-u that pop up and say i have to format them in order to use them, but they are write protected so i cannot view whats in them, format them or anything. does anyone out there have any kind of suggestion to fix this or am i just completely stupid and missing some big major step? i am also very new to android this is my first android phone lol im a converted apple user haha so the more indept detailed instructions would be greatly appreciated
Click to expand...
Click to collapse
Has anyone come up with a solution to this? I am very new to Android, I have Rooted my G2 so I could install Custom Rom's. Yesterday I receive a OTA update, I refused it and then later when it came up again was going to refuse it, but my shaky finger touched the screen and started the update! next thing I know I have a $600.00 brick. if you hold the power button down It will flash the LG logo and then NADA, screen is lit but nothing happens. Hold the power button and after a few it will Flash the logo again but NADA again. If you hold the down and power button it will go to the reset screen, but again this will not reset the device. PLEASE HELP!
Thank you.
Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
roninb30 said:
Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Click to expand...
Click to collapse
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Russbad said:
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
Click to expand...
Click to collapse
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Click to expand...
Click to collapse
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Is it possible that I need a pit file for the device since no version of Odin will get past initialization? ....if so where can I get one for the this model?
roninb30 said:
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Click to expand...
Click to collapse
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
rkirmeier said:
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
Click to expand...
Click to collapse
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Huge 3rd.
Device should just plain WORK out of the box. There shouldn't have been a need to flash stock to begin with.
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Android.Ninja said:
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica....then again for it to come back. Just wanted to do everything I could before I had to send it. Thanks for the input though. I guess I learned quite a bit researching processes and terminology which will be helpful in the future. ^-^
Russbad said:
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Click to expand...
Click to collapse
Tried many times. The device pretty much gives me the finger by going blank and repeatedly showing the boot up logo when I hold the buttons down.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root.
Click to expand...
Click to collapse
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
roninb30 said:
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica
Click to expand...
Click to collapse
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
ExtremeRyno said:
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
Click to expand...
Click to collapse
After doing research, I think that even if I get a new one, I want to root it. With the problems I've read about for kitkat 4.4.2 I need to know how to fix problems, and start with a fresh install of roms and know how to use custom recovery. I haven't done anything yet, but I was wondering...
Since I'm stuck in a boot loop with no stock recovery, can I flash a custom recovery to fix my issues, flash the stock rom that is on sammobile.com and then root after that? From what I understand this is a soft brick since I can still sometimes access the device. I worked out why I couldn't access the device with adb and now it shows the device as listed. It stays on long enough to where I could flash a recovery before it restarts itself. I'm not trying to do anything stupid, just getting information before I pay the shipping for it back to the states. I've checked the knox counter in download mode, and it is still set to 0, so I haven't voided the warranty yet.
Any input would be greatly appreciated.
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Russbad said:
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Click to expand...
Click to collapse
I understand the skepticism. Yeah, I tried the button combination, usb in, usb out. I can power off the device completely only when it is plugged into power. When I hold the recovery combo from power on, the screen goes black with no flashing of the boot logo, looks as if it wants to go to recovery, and then then the boot logo comes up again, but just continues to the boot animation and continues the boot loop, even if i'm still holding down volume up and home buttons. It will sometimes boot up, then freeze after a couple of seconds, and return to boot loop. On rare occasions it will boot up, but turns me to setup like it's a brand new device. I can access everything for about 10 minutes, and then it will randomly restart and continue to boot loop again after that. I tried update/initialization in kies, but it would restart before the downloading and decompressing of binary could finish. It finished one time and then switch to a downloading screen (although it didn't say odin since you have to manually go there) but the update would freeze at 0 percent no matter how long I left the device there. It's all pretty lame ><
Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.
cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?
I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.
Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.
Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.
Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
U are in edl mode u need to search for blank flash it should get u back up and running
Zacigator said:
So, I followed all the basic instructions of getting ADB, downloading and flashing twrp, and my goal was solely to root my phone so I went ahead and got SuperSU as well and installed it through twrp. Everything went fine until I went to reboot my phone and it wouldn't work, it would only boot into twrp no matter what I did. In a moment of foolishness, I decided to go to the reset section of twerp, and switched to partition A (it was on partition B, where everything had been installed). Now my phone only has a black screen, and no amount of trying to soft reset or anything is turning it on. The only indication I have that my phone is doing anything, is that when I plug it in to my pc I can hear the connection sound. I can't access any files on the phone, and ADB doesn't recognize that the phone is plugged in. It's a Moto g7 power phone, and I used the latest versions of the programs. Also, I did do something of a ****ty backup before I started the process, but since my phone wasn't rooted I don't know how much that'll help me. All the stuff I find online says to just install a stock rom or whatever; but I can't even access my phone to do that. Is there ANYTHING I can do or am I ****ed?
Thanks so much for any and all help
Click to expand...
Click to collapse
Did you get it running