Hello all,
I have a friends sprint hero cdma that was rooted with z4root. He was flashing a mod that changed the text from green to orange and the phone froze. He waited quite a while then decided to hard reset. When he put the battery back in and rebooted the phone and the phone would not boot past white HTC bootlogo. The phone will not boot into recovery and the PC will recognize the phone, but the system will not mount so the ruu will not detect the phone either. HTC sync does not detect the phone being connected either. I am using a program called USBDeview and it shows the driver is there and says it is connected but none of the programs detect its connection. Any ideas?
Thanks in advance. Again this is not my phone and I am not familiar with rooting procedures with this phone, but I see a great learning experience in front of me and love these challenges.
this should be in QnA.
Hold power + vol down. will get you into HBOOT. if you flashed the eng-spl that unlocks fastboot you can erase and flash new. Tutorials are somewhere in this forum.
Sorry for the wrong forum. The phone will not hboot or boot into recovery
If it gets that far, you should be able to run the RUU. It'll restore everything to stock ;-)
Sent from my Epic using XDA App
The phone does not connect all the way for some reason. The RUU does not see device and neither does ADB. In device manger, when the device is connected it is assigned a drive letter and I can right click and go to properties and details and the description says android phone. I am out of ideas. Even when the device is connected and assigned a drive letter I can open file explorer and click on the device and the directory is blank. The SD card does not even show up, but if I take sd and put it in an adapter the sd card is still in tact with everything on it.
Sounds like a driver went haywire try searching the dev section for my thread on how to install adb. I know you have it already but try the diffrent drivers. I would post a link but I'm mobile. Hope it helps
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
Power off
hold vol up and power on
should be in fast boot mode
plug in your USB cable
should now be in fast boot usb mode
run RUU from the computer
RUU should recognise the phone and start installing
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
nordy420 said:
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
Click to expand...
Click to collapse
Yes this is basically true. But if you get the HTC screen, chances are that it is not bricked. I have to ask, did you flash anything like a radio for GSM? If not, then you might need to just let it sit there for an exstended period of time and see if it boots. When I do certain things to my phone, it might take up to 15 minutes to get by the HTC logo screen.
nordy420 said:
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
Click to expand...
Click to collapse
I wish I could take a screen shot and show you but the phone is not recognised at that point except by the RUU when it is waiting for bootloader. Bootloader is another name for fastboot.
It would be a white screen with green letters and it will say fastboot near the top under the green letters. At the bottom of the screen there will be 3 android characters on skate boards.
This is what you should see. Try again
Important: Make sure the USB is not conected at this time
Power off
Hold volume up, then press the red key (power on)
Fastboot screen comes up
At this point plug in the USB. It will change from Fastboot to Fastboot USB
Run RUU .5 or .6 from the computer
It will get to a point where the install says waiting for bootloader
from there it should start installing
If you can't get to the bootloader screen (fastboot) then I am not sure how to help you
Let me know if it works for you.
Edit: If you are not using ENG SPL or have S-Off read this post. You will need a working knowledge of how to use ADB.
http://forum.xda-developers.com/showthread.php?t=958968
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Thank you for the help by the way. I am not the owner of the phone, I am just more patient than the owner and have nothing to lose if it is screwed lol. http://androidforums.com/sprint-hero-all-things-root/259735-bricked.html. Here is his desperate cry for help after it happened. I own a Droid x and have no idea what he was actually trying to do, but maybe after you read what he did then maybe we can come up with a fix. I agree with you supporters that the phone is not bricked but it is sure being stubborn. Please let me know what ya think. Thanks.
unCoRrUpTeD said:
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Click to expand...
Click to collapse
I will try this when I get home. I did do a battery pull but I did not leave it out very long, but the screen never changed for me, just stayed white with HTC logo in the middle.
Be very sure to disconnect the USB. That was the step I was missing and I could not get it to boot to recovery when it was stuck at the logo. Once the USB was disconnected, took the battery out, put it back in, and held down the home button while pushing the power. That worked! Woot!
Lynne
No luck. The phone will not boot into anything to where a PC will recognize it.
nordy420 said:
No luck. The phone will not boot into anything to where a PC will recognize it.
Click to expand...
Click to collapse
Have you downloaded android commander and gave that a shot? androidcommander.com
android commander recognises the phone when it is at the logo screen. it will see all but the sdcard.
within android commander menu, there is a reboot to bootloader command
Ill try it, and report back
So I messed with android commander a little and could not get it to detect the device. I really think that it is a driver issue. I cannot get the HTC driver to install for the phone. A different driver has been installed for the device and windows will not let me manually install one. I can use the install legacy and the HTC driver is there but it will not correlate with the phone when connected.
Related
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
Hi i will put everything out so it can be answered without going back and forth : I was installing Trickdroid 10.3 and was about 95% done then it crashed I erased the wrong thing and now am stuck on hboot/fastboot screen everything I seleect either shuts down phone and restarts it back in same place or does nothing helpful. Usb can't be seen and recovery will do same flash off the right back to same screen s-on was s-off but is now back to on hboot is 1.44 radio 4a 14.3250.13 phone was rooted and bootloader was unlocked my device is TAMPERD and says UNLOCKED HAHAHA had to say T&U was funny when i got it saying it still is, but says ss-on... I have been looking and readin for a week and now it came down to taken suggestistions and hopefully we can get it fixed cause i dont want to end up with an electric bath toy for the babys!!!:crying:
DrzNikki said:
Hi i will put everything out so it can be answered without going back and forth : I was installing Trickdroid 10.3 and was about 95% done then it crashed I erased the wrong thing and now am stuck on hboot/fastboot screen everything I seleect either shuts down phone and restarts it back in same place or does nothing helpful. Usb can't be seen and recovery will do same flash off the right back to same screen s-on was s-off but is now back to on hboot is 1.44 radio 4a 14.3250.13 phone was rooted and bootloader was unlocked my device is TAMPERD and says UNLOCKED HAHAHA had to say T&U was funny when i got it saying it still is, but says ss-on... I have been looking and readin for a week and now it came down to taken suggestistions and hopefully we can get it fixed cause i dont want to end up with an electric bath toy for the babys!!!:crying:
Click to expand...
Click to collapse
Can you see the device in ADB mode?
dgtiii said:
Can you see the device in ADB mode?
Click to expand...
Click to collapse
No I can't......I also forgot I am running windows 8, when I use the adb device nothing, any adb codes, or serial numbers don't show up. No matter what is done recovery is not working. I have an s4, it too was in the same state, I was able to download ROM to external SD card, rebooted into recovery mode, and re-flash ROM. That is almost fixed...
If I get a female to female USB and mount the USB somehow will it give it the same effect? If so any suggestions? Or any other suggestions to help me get through this?
DrzNikki said:
No I can't......I also forgot I am running windows 8, when I use the adb device nothing, any adb codes, or serial numbers don't show up. No matter what is done recovery is not working. I have an s4, it too was in the same state, I was able to download ROM to external SD card, rebooted into recovery mode, and re-flash ROM. That is almost fixed...
If I get a female to female USB and mount the USB somehow will it give it the same effect? If so any suggestions? Or any other suggestions to help me get through this?
Click to expand...
Click to collapse
Yes, that would be my advice. Go to a site like Amazon, and search for a "micro USB OTG cable". They are inexpensive, and will allow you to use a flash drive with the phone in recovery. Then download a rom onto a flash drive, and install from there.
dgtiii said:
Yes, that would be my advice. Go to a site like Amazon, and search for a "micro USB OTG cable". They are inexpensive, and will allow you to use a flash drive with the phone in recovery. Then download a rom onto a flash drive, and install from there.
Click to expand...
Click to collapse
Thank you for replying!!! How would I get into recovery with no access to the phone? Is there a manual script to get into it? Also I can upload a picture of the only part of the phone I can see if that would help?
DrzNikki said:
Thank you for replying!!! How would I get into recovery with no access to the phone? Is there a manual script to get into it? Also I can upload a picture of the only part of the phone I can see if that would help?
Click to expand...
Click to collapse
Hold down the power button while holding down the volume down button at the same time until the phone reboots. If it does not, use the same procedure while holding the proximity sensor under a bright light (sounds weird but it works!). Phone will boot into bootloader mode, select recovery, and you will be good to go. I'll take a look if you upload a pic, sure
I had something similar, but managed to get in through ABD (windows 7), but also remembering that I was stuck in a boot loop, i wiped cache , re tried and rom loaded and booted. Have a read up on ABD in windows 8, see if there's anthing your missing or specific modded files needed for windows 8 and ADB running, just my opinion
Hello everyone,
I've just tried installing twrp-3.0.2-3-thea.img (md5sum: 35c37561f0c22bfe23cd01b5c388e8b5) and BETA-SuperSU-v2.62-3-20151211162651.zip (md5sum: 7fcb30bcbcd18b5f0b0f5848a096d4ed) on a Moto G LTE 2014 "Thea".
Unfortunately something didn't work. The device first was stuck in the boot animation, then started booting correctly a few times, but now it's completely bricked:
I've been unable to turn the phone on using either pressing power+button down for 10 secs or just pressing the power button for 2 mins while being connected to an usb charger. Obviously it won't connect to adb/fastboot/etc.
I'm really puzzled. Is it even possible to brick a device like this just by trying to root it? Any suggestions?
Alright, found the issue - it seems that for some reason or another flashing TWRP or SuperSu caused fastboot to stop working, hence the hard brick. Now It shows up as "qhsusb_bulk" - unfrotunately there's no way to fix this by myself given that the only fastboot images ( "MBM-CI") available are for Android 4.4.4.
If your bootloader is unlocked you shouldn't have any problems reflashing. You do however have to make sure you are flashing the correct recovery IMG for your phone there are a very large number of ROMS and each is device specific. Try leaving LTE out of your search criteria when searching for images to flash with, rather just Moto G 2nd gen 2014 and you will be on your way to finding the correct IMG. I found a Titan IMG that works with my XT1072 and believe you me that was after the 5th/6th time of reflashing! Another handy tip is that in order to enter into fast boot or recovery mode there's are a few things to consider, namely
The version of fastboot adb you have installed on your PC, some versions behave strangely? Don't ask me I know nothing!
Secondly and very importantly you need to have latest drivers for your make and model of phone installed on your PC.
Thirdly before you connect your phone via its USB cable to PC you must first start up fastboot if you are just using fastboot. I have mine sitting as shortcut on desktop right next to adb shortcut for convenience.
Fourth: hold power button plus vol down for about 3-5 seconds, continue to hold vol- button but let go of power button (this is an important detail that many people on the forum forget to mention) with Motorola specifically!!!! Trust me do it this way and you will almost certainly always boot into recovery/fastboot mode
5th connect your phone to your PC ( not to teach your grama how to suck eggs but don't forget to select USB debugging under dev options on your phone) hopefully you did this??? Otherwise I don't know what the work around is for that, other than factory reset and start over?!
Anyway after connect to PC in the shell terminal run the adb devices command if you are in adb or
run the fastboot devices if you are in fastboot to see if your computer can detect your device? This is a clear indication of whether or not your bootloader is unlocked and/or whether USB Debugging is selected, shouldn't be hard to work out which device is yours as only one device should then show up. There are threads on XDA about how to unlock BL. Aquire root and flash recovery images, obviously, but I couldn't begin to tell you how to do that as each scenario is so different from the next, best of luck!:good:
None of those solutions would obviously work, considering the bootloader/fastboot partition has been altered to the point the device won't boot at all, forget about Drivers or USB Debugging.
By the way, I've just got my device from motorola, after roughly two months since they took it to the repair centre. Their official response has been "We won't fix devices who had been tampered with".
Oh well. When I got it back the clerk could only congratulate me for my really nice new paperweight.
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Now It shows up as "qhsusb_bulk"
Click to expand...
Click to collapse
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
LuuchoRocha said:
The phone isn't starting at all? It shows something on the screen or acts just like powered off?
Click to expand...
Click to collapse
Completely blank screen. No response whatsoever.
You mean the PC isn't recognizing the phone at all and just shows an USB device with that identifier?
Click to expand...
Click to collapse
That's right. It's the same error which occurs on some MSM89xx SoCs when the bootloader/blankflash gets steamrolled. But contrary to what happens to some devices like the Galaxy SIII, there are no available bootloader image files available anywhere, and it looks like the SoC used on mot g devices does not provide any failsafe boot mode from sd.
In other words, it's a really nice paper weight until a disgruntled Lenovo employee leaks the required files somewhere. Actually, according to the Motorola tech guy I've spoken to, there's the chance that clearing the bootloader triggers an efuse making it impossible to recover from altogether, but I really hope this is not the case.
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan
TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm
TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.