Related
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Caid.
444.
EDIT
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Did you try other key combinations such as Home+Power, or Back+Power?
I'm sorry but I think you're misunderstanding it all a little bit...
Caid444 said:
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
Click to expand...
Click to collapse
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Caid444 said:
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
Click to expand...
Click to collapse
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
Caid444 said:
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
Click to expand...
Click to collapse
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Caid444 said:
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
Click to expand...
Click to collapse
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
Caid444 said:
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Click to expand...
Click to collapse
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
Caid444 said:
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Click to expand...
Click to collapse
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
biktor_gj said:
I'm sorry but I think you're misunderstanding it all a little bit...
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Click to expand...
Click to collapse
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Again, a really big thanks. I've sent my phone back and am getting a new one soon. I much appreciate your reply, however, as it's probably the most understanding and considerate reply I've seen on these forums.
Cheers.
Caid.
444
One more quick question out of curiosity, when you press and hold back and press end to turn on the device (it still goes to the htc magic screen) SHOULD it go to a different screen, other than the "htc magic" screen? Or is that a process that runs without some sort of visual notification on the device itself?
The usb was completely unresponsive after this happened, but in the event that bootloader may have been running, (only possible if it runs without any visual notification on the device itself), I'll go pick up the device and see if my usb drivers on my computer just became unresponsive after being accessed too many times. Sometimes windows does that, right? Perhaps a reboot would have allowed fastboot and the drivers to connect again, if the device was trying to talk to the computer, but I just didn't know on account of not having any notification.
So, again, should pressing back and power bring me to a different screen? or would it also look like it was hanging on htc magic screen?
Caid.
444
p.s. Sorry for the confusing wording, I'm tired and trying very hard to be as specific as possible.
back+end/power should lead you to the fastboot screen right after it shows the HTC Magic screen or whatever splash screen you have installed.
Home+end/power should lead you to the recovery screen.
ok, it was bricked. Thanks for the answer.
Caid.
444
Caid444 said:
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
Click to expand...
Click to collapse
No problem, we all should be here to learn, and to help (except for the trolls)
This is the guide I followed for both Vodafone branded Magics: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Maybe not for now, but for the next magic you get it may come handy
Caid444 said:
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Click to expand...
Click to collapse
When the phone is off with the charger connected and you press the power button, the light goes off, as for the others, you really should be able to enter the SPL if it could the magic bootlogo and vibrated upon boot...
Maybe you didn't try enough or maybe your bootloader behaved differently than mine... I should be more clear anyway, to get to the bootloader, the best way to make it go to the bootloader is press and hold back key, then while holding it, hold the power button too. It should take about a second or two before showing the three skater droids.
Caid444 said:
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
Click to expand...
Click to collapse
When you put the battery while USB or charger is connected, the phone boots up, that's the normal behaviour. About the blue led, that's the Radio bootloader. That's quite dangerous to play with, but it gives a lot of other functions. Another sign that your phone wasn't completely dead Even if you wipe the SPL (the three skater droids), you may be able to boot into the Radio bootloader and write or boot another one to fix it. But that's waaaay harder
Caid444 said:
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Click to expand...
Click to collapse
I guess the first advice when you start tricking with a phone is be careful with what you're doing. That's the good thing of fastboot.
When booting on fastboot mode, you can pick, for example a recovery image, and boot it without overwriting the original rom:
Code:
fastboot boot [recovery_image]
Then, when you see it's working, you can flash it:
Code:
fastboot flash recovery [recovery_image]
fastboot flash boot [boot_image]
fastboot flash system [system_image]
fastboot flash data [data_image]
You can't do that with the system.img since it's too big, but you can do it also with a boot.img
About the key combinations on the phone, it goes like this:
Code:
BACK + END KEY -> Fastboot mode (you shouldn't see the boot logo)
VOLDOWN + END KEY -> Hboot mode (you shouldn't see the boot logo)
ACTION (trackball center) + END KEY -> Radio Bootloader (you shouldn't see the boot logo)
HOME + END KEY -> Recovery mode (you should see the boot logo, then get the recovery menu)
SEND + MENU + END -> Reboot the phone (while the phone is on)
Maybe there are more (android has kind of 'safe mode' but I don't know it it goes there automatically if there's a problem or if it has to be called manually)
Anyway, I hope these things will be useful for the next phone, and for anybody who's a bit lost on this
Regards!
Let us know where you live , so maybe one can help you , I live in Sweden and will be glad to help you if you are near ;-)
Hey! Thanks again for all the help, and the offer to come help. Unfortunately, I'm in China. Coming here from Sweden (although it's a single large landmass) would take quite a bit of time
I appreciate all the support, though. Very cool community we're building here for the magic.
Caid.
444
htc semi-brick?
Hi to all. I'm in the same condition described in this tread; after installing SPL i get the htc block in Vodafone brand red screen.
None keys combination bring me to the boot menù. Only Action(trackball) + power have effect, but with a black screen...
Any suggest?
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Newbie need help
ok so i can still go to recovery mode but everytime i reboot my phone the mytouch 3g logo never goes away im new to Android but not htc can somebody plz help me out.
gruppler said:
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Click to expand...
Click to collapse
Instead of flashing something, you boot a recovery image, and then, from there, you flash whatever you need (using adb & flash_image for example)
PS: Be a little patient, if fastboot is letting you boot a recovery image, the recovery needs to boot, and that takes a little while, and while it's booting, you see the bootlogo until the menu appears. Also, you can try running adb shell after boot process started to try to get an error message (or at least to know if the thing is booting in some way)
I couldn't boot any recovery images. I had tried a few different Hero ROMs but decided i wanted to use Cupcake again because i have a 32B board and it just doesn't have enough RAM, though Swapper makes it usable at least. I don't know what exactly i did, but i've learned a lot from my mistakes. Everything i tried failed the signature check because the hboot version didn't match. If i could just flash the 1.33.2005 hboot again, i would have been in business, but no matter which recovery image i tried, it just sat there doing nothing. And believe me, i waited.
Fortunately, T-Mobile gave me a new device after i took it in and played dumb. And I just rooted it =]
Caid444 said:
ok, it was bricked. Thanks for the answer.
Caid.
444
Click to expand...
Click to collapse
Why not flashing it with an RUU from HTC. Not sure that would work but it is worth trying.
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
iivanovic said:
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
Click to expand...
Click to collapse
I have the same problem. I get up hboot and fast boot menus can not get it in recovery. try to add in sappimg but no luck
I'm having the exact same problem...
Any solution yet?
Hello! I can assure you that your phone is not fully bricked! Awhile ago I flashed a new radio only to discover that I hadn't done my research and was a complete and total idiot. I flashed the 1.76.xxxx on a 32B. It didn't like it. I got a quick HTC logo that disappeared then the phone never responded again. When I say never responded it was dead. no combination of buttons would get any response. If you can get into fastboot you have options. All that's necessary is to make sure you have the appropriate sappimg file. Try the Unlockr's gold card method file. He has a .zip file that may work for you. Just make sure that you find an image that is compatible with your board (32A or 32B). Hope this helps!
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 ><
Hello, so i have a problem. I've installed KingRoot on my LG Spirit H-420 and it worked great, then i searched a bit about this and saw some bad reviews and decided to uninstall it. Then i started searching more and saw some tutorial for rooting with kingroot and then using app called super su-me that uninstalls kingroot and installs SuperSU. So i did this and after installing SuperSU and rebooting my device my signal bar was showing nothing and i was unable to enter settings. Basically when i clicked my settings cog it opened and immediatly closed saying "Unfortunatly settings has stopped working" so i was unable to make calls and access my settings (although i was able to access my wifi/bluetooth/location settings by clicking them in my taskbar). So i unrooted with my superSU and did hard reset by turning off the device and holding vol down and power button to do the factory defaults. After it there was android logo saying working (like always i did the factory reset through my settings) but then its stuck on the boot screen for 30mins, before it hardly took 1min to reset to factory. How ****ed is my device and is there a chance to get it back to working ?
If the bootloader is at least showing the animation, then I don't think you need to worry much. Try the following to begin with:
1. Charge your device for a few hours if it is underpowered.
2. After that, go to your OEM recovery (by long pressing UpVolume + Power buttons) and clear the cache (there usually is the option to do it).
This should solve most issues with bootloop, etc. Try this and report back.
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
a7ogpl said:
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
Click to expand...
Click to collapse
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
prahladyeri said:
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
Click to expand...
Click to collapse
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
a7ogpl said:
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
Click to expand...
Click to collapse
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
prahladyeri said:
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
Click to expand...
Click to collapse
The thing i did it and it got into bootloop. If i click yes then there is an android logo with caption "deleting" and then it goes into booting screen [the one with LG Powered by android without animations] and stays like this forever
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
prahladyeri said:
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
Click to expand...
Click to collapse
Its saying lg h420 when i connect it and it is in the booting screen (the phone), so i basically could be able to flash it but i dont have my computer and the one here is not powerful enough so i dont trust it. I decided i will just try to give it with warranty and if they refuse then i will flash it. There is no other way now to rvive it. Thanks for help tho
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
its not the usual reboot loop, it gets not even that far, its stuck to the "this phone is jailbroken,hit power to pause" after that it just reboots,while empty.
i tried to switch it off, to ensure loading, but keeping the powerbutton 10sec pressed,is impossible,there is not enough time.
i tried to switch into the bootloader, and say switch off, well it goes back into the loop 2sec later,since it got a bit power, it tries its nonsense.
i tried differend loading methods, pc usb, usb pure (2.1mAh), and the oneplus speedloader adapter with the red cable.
what happend before, well it got empty, and switched off,the apps and such didnt change for about a year, it worked, and thats it.
the accu cell got changed about a year ago, by my insurance company, the old one balooned. so they changed it,meaning its not even a old cell.
trying fastload in bootloader,didnt help getting it charged,anything else just relooped.
iam open for suggestions.
thanks and regards
Noal
I think ur phone might be soft bricked or idk. But I'm pretty sure the problems didn't caused by the new battery.
Seems the phone didn't recognize the /system/ or something on twrp that says "There's no system installed" coz i've faced that (no system installed) before.
If u can manage boot into bootloader, try to fastboot a twrp.img and flash a stock firmware.
If u can't, or let's just say you really feel ur phone in fked up state, try to reflash everything with MSM Download Tool.
Here's some threads I found :
Soft Bricked?
I apologize as I've been out of flashing ROMs for over 4 years now. I unlocked my OP6 bootloader, added TWRP, the flashed Lineage 11. One of my apps wont play nice with root so I tried to go back to stock. I tried to use TWRP 3.5.2_9-0 to...
forum.xda-developers.com
[OP6][LATEST 10.3.8] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Credits goes to them.
Hope it helped.
NoalFey said:
its not the usual reboot loop, it gets not even that far, its stuck to the "this phone is jailbroken,hit power to pause" after that it just reboots,while empty.
i tried to switch it off, to ensure loading, but keeping the powerbutton 10sec pressed,is impossible,there is not enough time.
i tried to switch into the bootloader, and say switch off, well it goes back into the loop 2sec later,since it got a bit power, it tries its nonsense.
i tried differend loading methods, pc usb, usb pure (2.1mAh), and the oneplus speedloader adapter with the red cable.
what happend before, well it got empty, and switched off,the apps and such didnt change for about a year, it worked, and thats it.
the accu cell got changed about a year ago, by my insurance company, the old one balooned. so they changed it,meaning its not even a old cell.
trying fastload in bootloader,didnt help getting it charged,anything else just relooped.
iam open for suggestions.
thanks and regards
Noal
Click to expand...
Click to collapse
It is much better to state the status of your device briefly. Like are you on OOS or custom ROM, unlocked bootloader, with custom recovery installed, magisk installed, etc. Then tell the story on what you did or what happen before your phone got the issue you stated. Then maybe someone can help you in more specific way.
Like Azhar_Fahry recommended, I also recommend using MSM tool and revert back to original state like you first bought your device.