Related
I had ruined my KFHD ROM so it boots with two options :
1. Reboot your Kindle .
2. Reset to Factory Defaults .
in both cases it was same result reboot with same previous options .
Can i flash new ROM from my computer ?
(adb couldn't find the device)
Please Help :crying:
ShinTeuk said:
I had ruined my KFHD ROM so it boots with two options :
1. Reboot your Kindle .
2. Reset to Factory Defaults .
in both cases it was same result reboot with same previous options .
Can i flash new ROM from my computer ?
(adb couldn't find the device)
Please Help :crying:
Click to expand...
Click to collapse
Download the KFHD SRTool from here:
http://forum.xda-developers.com/showthread.php?t=1951254
Don't worry you shouldn't need a factory cable. There is another way to enable fastboot.
Power off your device and unhook from the computer.
Unzip the tool and run SR Tool
Choose option 1 or 2
It should say [waiting for device], at this point plug in the device. It should automatically start to boot (if not hit the power button) then go to a screen that says Fastboot Kindle Fire and the tool should start sending the image. This is going to reflash the system image. Be patient it can take awhile to finish. More than likely it is what is causing the problem depending on what you did to cause it. If some applications you downloaded are causing problems I would recommend erasing cache and userdata after the script completes.
To get out of fastboot hold down the power button for 10-20 seconds
Let me know if this works as I have not tried to enable fastboot this way on the HD7. Should work though, it does on the HD8.9 and the original.
onemeila said:
It should automatically start to boot (if not hit the power button) then go to a screen that says Fastboot Kindle Fire and the tool should start sending the image. This is going to reflash the system image. Be patient it can take awhile to finish. More than likely it is what is causing the problem depending on what you did to cause it. If some applications you downloaded are causing problems I would recommend erasing cache and userdata after the script completes.
To get out of fastboot hold down the power button for 10-20 seconds
Click to expand...
Click to collapse
Thank you very much . i followed you and yes it's automatically start to boot but it's went to the previous screen not to (Fastboot Kindle Fire) screen
ShinTeuk said:
Thank you very much . i followed you and yes it's automatically start to boot but it's went to the previous screen not to (Fastboot Kindle Fire) screen
Click to expand...
Click to collapse
Did it go straight to that screen or did the Kindle Fire logo appear first? Like it was trying to boot but then went to that screen. Did you try selecting an option? Did the command prompt change? sorry for all the questions just trying to get a feel for what exactly is happening?
onemeila said:
Did it go straight to that screen or did the Kindle Fire logo appear first? Like it was trying to boot but then went to that screen. Did you try selecting an option? Did the command prompt change? sorry for all the questions just trying to get a feel for what exactly is happening?
Click to expand...
Click to collapse
No man really thank you for helping me ask whatever you want
The Kindle logo appears first the device tried to boot then went to the dammin screen .
Yes i tried the options 1 and 2 nothing happened .
The command prompt is just waiting the device couldn't find it .
i think that i need a driver that makes the pc recognize the device on the booting
i saw a way to make a factory cable is it true ?
sorry man but i like to learn every thing
that what happening on my kindle check this : >>youtu.be/Q-tZl5gWwdU
ShinTeuk said:
No man really thank you for helping me ask whatever you want
The Kindle logo appears first the device tried to boot then went to the dammin screen .
Yes i tried the options 1 and 2 nothing happened .
The command prompt is just waiting the device couldn't find it .
i think that i need a driver that makes the pc recognize the device on the booting
i saw a way to make a factory cable is it true ?
sorry man but i like to learn every thing
Click to expand...
Click to collapse
Yeah I just had someone also test that method and it does not work on the 7" hd models, sucks!
To answer your question about factory cable,
Yes it is, and its really easy if you have a soldering iron(don't really need it but helps) and are handy. Basically a usb cable has five leads but only uses four of them. You have to make a jumper with a 1k resistor(thats what is recommended) from that fifth lead to the power(red) lead. Pretty easy.
Here's a link with more details and there is a post by someone in there who sells them, cheap at that:
http://forum.xda-developers.com/showthread.php?t=1392693
Thank you again ill try it and tell you what happened with me
so now i made a factory cable and connect my Kindle to the computer and fast boot start computer can recognize the kindle when i used the Kindle Fire Utility to install fire fire fire it turned off and never start again :S
ShinTeuk said:
so now i made a factory cable and connect my Kindle to the computer and fast boot start computer can recognize the kindle when i used the Kindle Fire Utility to install fire fire fire it turned off and never start again :S
Click to expand...
Click to collapse
First of all not to be an ass but why would you do this? First the kindle fire utility is for the first gen KF. Second how could you not have seen all the news and articles talking about the bootloader on these devices being locked down. It's probably one of the most talked about aspects about this device right now. What has happened is by trying to load fire fire fire, which is a custom bootloader for first gen, you have flashed over the original bootloader and hopefully not but possibly bricked your device permanently. If you can manage to get it back into fastboot I can send you a backup of the bootloader partition you can reflash. PM me and i'll walk you through it.
Here's a longshot as this forum is close to its death, but I was building PA (wanted the old memories) for the Kindle. Fast forward, everything built and it gave me a flashable zip like it should. Upon flashing the zip with TWRP 2.8, I rebooted and now it is just on an infinite loop with the Kindle Fire logo. Not the blue one, but the original one. I am unable to get into anything, not fastboot mode or recovery? Any thoughts or solutions? Thanks!
Edit: I should also mention that the original Kindle Fire logo shows up for a few seconds, then turns off and does it again hence the loop.
When you say you can't get into fastboot or recovery, is that via the device? Have you tried via adb?
Sent from my HTC 10 using XDA Labs
squ89r97 said:
When you say you can't get into fastboot or recovery, is that via the device? Have you tried via adb?
Click to expand...
Click to collapse
ADB is useless at this point - it only works if you're booted into Android or in TWRP and connected to a computer previously authorized for ADB via Android.
OP - did you use a fastboot cable? Also, can you verify the drivers are installed properly? You'll need to disable driver signature enforcement on Windows 8+ before the drivers will successfully install.
Sent from my Amazon Jem using XDA Labs
A hard brick is generally described as a device that won't do anything at all. Since your device is showing the kindle logo on the screen, there may be hope.
Hold the power button until the screen goes blank, than plug in a fastboot cable. If you can boot into fastboot, then you are not bricked. If you can't get it to fully power off, then you may need to disconnect the battery, which I have no clue how to do since I've never taken apart one of these devices.
paulshriner said:
A hard brick is generally described as a device that won't do anything at all. Since your device is showing the kindle logo on the screen, there may be hope.
Hold the power button until the screen goes blank, than plug in a fastboot cable. If you can boot into fastboot, then you are not bricked. If you can't get it to fully power off, then you may need to disconnect the battery, which I have no clue how to do since I've never taken apart one of these devices.
Click to expand...
Click to collapse
If you've got the kindle connected to a computer with working ADB and fastboot, you can also type fastboot -i 0x1949 poweroff to turn it off, if I remember correctly.
Sent from my Amazon Jem using XDA Labs
EDIT: I got to fastboot mode finally, just by trying different USB cable... (am I dumb? yes. really.) I'm sorry for wasting everyone's time that tried to help me!
I tried to install xposed via TWRP, and after that I got stuck in a bootloop, then I tried to install something in panic in twrp in order to fix my phone, and then when I was about to boot, it said "No OS installed are you sure you want to reboot?" I tapped Yes. Now I can't access my recovery mode anymore.
I haven't installed fastboot on my phone or whatever (dont know does it have to be installed to get access to it) but when I try the button combination I'm not accessing the fastboot mode.
I'm stuck in a screen where it says 'Your device has been unlocked and can't be trusted" and in the bottom is says "Your device is booting now..." and does nothing.
Please I really need help, I paid for my phone 300 euros and have had it only like month... also i'm addicted to pokemon go and my p9-lite is the only device I could play it with, and my family isn't the richest one and I can't buy a new one in like a year
)
To access fastboot mode. Make sure the phone is off. Press and hold vol down and insert USB cable. That should bring you to fastboot mode.
n0my said:
To access fastboot mode. Make sure the phone is off. Press and hold vol down and insert USB cable. That should bring you to fastboot mode.
Click to expand...
Click to collapse
not working, just brings me to the same screen where it says "your device has been unlocked and can't be trusted"
what about 3 button combination???
Hold vol- ;vol+ and power button, when huawei logo appers realise power button.
Sugestion. Dont mess with TWRP and zips if u dont know what are u installing.
P.S. DC phoenix can fix your phone, but it cost 15 EUR and u should be able to acced fastboot.
Sent from my EVA-L19 using XDA-Developers mobile app
the 3 button combination doesn't work either.. also DC phoenix won't put me in fastboot right? as I've searched online about it.
And I won't mess with twrp ever again when I get my phone back.
Karibu0 said:
not working, just brings me to the same screen where it says "your device has been unlocked and can't be trusted"
Click to expand...
Click to collapse
connect cable with pc, then connect with phone, only then press volume down and powerbutton about 15 sec, so phone force restart, keep holding vol down. need to be in fastboot mode, if are not ,then its done for you!
Arnys said:
connect cable with pc, then connect with phone, only then press volume down and powerbutton about 15 sec, so phone force restart, keep holding vol down. need to be in fastboot mode, if are not ,then its done for you!
Click to expand...
Click to collapse
well...... I guess my phone is 'done' then
Is there any other ways to install the firmware than fastboot? like some kind of tool on pc so it forces the install and your phone doesn't have to be in fastboot or anything?
Finally got to fastboot mode, just by trying different USB cable... (am I dumb? yes.) I'm sorry for wasting everybody's time!
I'm never gonna do any modding to my phone ever again
Hi, I have a problem with my p9 too. I can't access fastboot or recovery mode. The phone stays on black screen, no led. When i pluged it on usb, he is detected but as "USB SER". How can i do to reflash ?
My P9 have problem who help me......plssss
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.