OP3T - Black (broken) screen. How to recovery data (debug not enabled) - OnePlus 3T Questions & Answers

Hi all,
I have a particularly tricky case here. A OnePlus 3T with a broken screen (its black, can't tell if its registering taps) which I need to recovery data (photos) from. Normally I'd just use ADB but of course usb-debugging isn't enabled. I've tried rebooting into recovery... hold the power button and vol-down until the phone vibrates, keep holding for a few seconds. Then wait. Then vol down twice and power again to hopefully select English but the when I try
Code:
adb devices
nothing comes up on the list.
I'm wondering if anyone has any ideas how I can recover data/photos from this device.
One again the facts are:
-OnePlus 3T
-screen is broken, black, doesn't display anything
-usb-debugging is NOT enabled
-i can see the device in fastboot mode (boot w/ vol-up+power)
Thanks!

willjeffery said:
Hi all,
I have a particularly tricky case here. A OnePlus 3T with a broken screen (its black, can't tell if its registering taps) which I need to recovery data (photos) from. Normally I'd just use ADB but of course usb-debugging isn't enabled. I've tried rebooting into recovery... hold the power button and vol-down until the phone vibrates, keep holding for a few seconds. Then wait. Then vol down twice and power again to hopefully select English but the when I try
Code:
adb devices
nothing comes up on the list.
I'm wondering if anyone has any ideas how I can recover data/photos from this device.
One again the facts are:
-OnePlus 3T
-screen is broken, black, doesn't display anything
-usb-debugging is NOT enabled
-i can see the device in fastboot mode (boot w/ vol-up+power)
Thanks!
Click to expand...
Click to collapse
Replace the screen and recover your data?
Anyways,this ain't OP3T forums,this is OPO forums.

Anyways,this ain't OP3T forums,this is OPO forums.
Click to expand...
Click to collapse
Oh whoops. Been a while since I posted on here. I'll post on there an have a mod delete this thread.
Also yes, that's an option but the repair place can't guarantee that the device won't be formatted during the repair... how that would happen is beyond me.

willjeffery said:
Oh whoops. Been a while since I posted on here. I'll post on there an have a mod delete this thread.
Also yes, that's an option but the repair place can't guarantee that the device won't be formatted during the repair... how that would happen is beyond me.
Click to expand...
Click to collapse
I don't see any need to format device after replacing broken screen? Is your device still on warranty?

Mr.Ak said:
I don't see any need to format device after replacing broken screen? Is your device still on warranty?
Click to expand...
Click to collapse
My thoughts exactly. My only guess is that the repair place would just swap out the device for a refurb. Also, its not my device, belongs to a friend who asked for advice. I believe its out of warranty. The phone was dropped away so likely wouldn't be covered, anyway.

willjeffery said:
My thoughts exactly. My only guess is that the repair place would just swap out the device for a refurb. Also, its not my device, belongs to a friend who asked for advice. I believe its out of warranty. The phone was dropped away so likely wouldn't be covered, anyway.
Click to expand...
Click to collapse
Why not replace it yourself? It is much easy and cheap way.

YouTube is your best friend for DIY replacements!
Sizzled with Bacon ?

I'm having a similar problem. Did you fixed your phone? I'm unemployed and i don't have money to buy a replacement screen.

Boot fastboot
Install TWRP via fastboot command with "fastboot flash recovery recovery.img" -make sure to designate file location of recovery image in terminal
boot into recovery from fastboot with "fastboot reboot recovery"
MTP should be enabled by default
If the device is encrypted, you will not be able to access the files without entering encryption key in TWRP.
In that case, a repair of the screen will be necessary to obtain access to the files
If the phone is not bootloader unlock, it would require a FULL DATA WIPE in order to do so, which would not be beneficial in your case.

Related

Nexus 6 7.0 broken screen not rooted - need to backup data!

Hi, so my phone's LCD and glass are broken and there is no display nor is touch working but the phone is on. I don't want to spend any money on it for replacing the LCD. It's on Android 7.0 stock, not rooted and everything stock and Wifi and USB debugging is NOT enabled although there is no lock code on the phone. I need to transfer my data to my pc (and no internal SD files are backed up in my Google account) but when I connect my phone to my PC, it doesn't show any files as i need touch to enable file transfer mode even though it recognized the nexus 6. Now i have 2 questions.
1. How to backup/transfer all my data? (preferably an alternative to the OTG mouse and HDMI solution since i can't find it easily in my country and can't order from amazon/ebay etc to my country).
2. How to reset the phone completely if i want to sell it to someone?
Any help would be highly appreciated on this matter...
yasirrfc said:
Hi, so my phone's LCD and glass are broken and there is no display nor is touch working but the phone is on. I don't want to spend any money on it for replacing the LCD. It's on Android 7.0 stock, not rooted and everything stock and Wifi and USB debugging is NOT enabled although there is no lock code on the phone. I need to transfer my data to my pc (and no internal SD files are backed up in my Google account) but when I connect my phone to my PC, it doesn't show any files as i need touch to enable file transfer mode even though it recognized the nexus 6. Now i have 2 questions.
1. How to backup/transfer all my data? (preferably an alternative to the OTG mouse and HDMI solution since i can't find it easily in my country and can't order from amazon/ebay etc to my country).
2. How to reset the phone completely if i want to sell it to someone?
Any help would be highly appreciated on this matter...
Click to expand...
Click to collapse
Adb pull files from recovery
holeindalip said:
Adb pull files from recovery
Click to expand...
Click to collapse
Hi, thanks for your reply. Can you please explain/guide me a bit on adb pull?
yasirrfc said:
Hi, thanks for your reply. Can you please explain/guide me a bit on adb pull?
Click to expand...
Click to collapse
What files are you needing to get off?
holeindalip said:
What files are you needing to get off?
Click to expand...
Click to collapse
I only need my images and the whatsapp folder. btw i dont have usb debugging enabled and not rooted.
yasirrfc said:
I only need my images and the whatsapp folder. btw i dont have usb debugging enabled and not rooted.
Click to expand...
Click to collapse
Do you have e a custom recovery installed? Bootloader unlocked? Can you see anything onscreen?
holeindalip said:
Do you have e a custom recovery installed? Bootloader unlocked? Can you see anything onscreen?
Click to expand...
Click to collapse
Nope no custom recovery installed. i didn't unlock the bootloader so im guessing its locked. and can't see anything on the screen nor can it recognize touch input as LCD and glass is damaged. is there any way?
yasirrfc said:
Nope no custom recovery installed. i didn't unlock the bootloader so im guessing its locked. and can't see anything on the screen nor can it recognize touch input as LCD and glass is damaged. is there any way?
Click to expand...
Click to collapse
I haven't used adb enough to know whether or not if stock recovery can be used, maybe somebody else can chime in
I hate to say it but your getting them by replacing the screen. Without root or adb debugging you won't even have access to the directory or be able to issue the device any commands.
zelendel said:
I hate to say it but your getting them by replacing the screen. Without root or adb debugging you won't even have access to the directory or be able to issue the device any commands.
Click to expand...
Click to collapse
Can i reset my phone in this condition? If i end up selling it, i want to wipe all the data in it so is that possible in this condition?
yasirrfc said:
Can i reset my phone in this condition? If i end up selling it, i want to wipe all the data in it so is that possible in this condition?
Click to expand...
Click to collapse
Maybe if you have it connected to the device the Android device manager. I disable it myself so can't say for sure. Other then that. No you are not gonna be able to. I really would just replace the screen. Not only will you learn something but you will be able to get all your stuff as well as the sale value will be higher.
bump
zelendel said:
Maybe if you have it connected to the device the Android device manager. I disable it myself so can't say for sure. Other then that. No you are not gonna be able to. I really would just replace the screen. Not only will you learn something but you will be able to get all your stuff as well as the sale value will be higher.
Click to expand...
Click to collapse
is wiping through fastboot an option? like if i enter download mode and wipe through a fastboot command.. don't know the exact steps though..
yasirrfc said:
is wiping through fastboot an option? like if i enter download mode and wipe through a fastboot command.. don't know the exact steps though..
Click to expand...
Click to collapse
If you are wanting to just wipe and sell then yes it is an option
holeindalip said:
If you are wanting to just wipe and sell then yes it is an option
Click to expand...
Click to collapse
ok so i've downloaded a fastboot compilation and i need to use fastbook device to check if nexus 6 is in fastboot mode and fastboot -w to wipe. I tried turning my phone off but i think it doesnt turn off until you press the power off button on the screen, even if you hold the power button longer. so ill let my phone fully discharge so it turns off and then charge it a bit while its off and then try to turn it on in fastboot mode by pressing volume down and power and then enter the commands. seems right?
yasirrfc said:
ok so i've downloaded a fastboot compilation and i need to use fastbook device to check if nexus 6 is in fastboot mode and fastboot -w to wipe. I tried turning my phone off but i think it doesnt turn off until you press the power off button on the screen, even if you hold the power button longer. so ill let my phone fully discharge so it turns off and then charge it a bit while its off and then try to turn it on in fastboot mode by pressing volume down and power and then enter the commands. seems right?
Click to expand...
Click to collapse
Yup, if you plug the phone into PC before booting into fastboot, hold vol- then hit power button,while in your fastboot directory on PC, hold shift and right click mouse button, then click open command prompt from here. Then type: fastboot devices this will then tell you on PC if phone is connected and ready to receive commands. If it returns your phones serial number then proceed with the commands
If you hold power button to reboot phone, as soon as phone vibrates hold the vol- key and it should put you into fastboot mode
holeindalip said:
Yup, if you plug the phone into PC before booting into fastboot, hold vol- then hit power button,while in your fastboot directory on PC, hold shift and right click mouse button, then click open command prompt from here. Then type: fastboot devices this will then tell you on PC if phone is connected and ready to receive commands. If it returns your phones serial number then proceed with the commands
If you hold power button to reboot phone, as soon as phone vibrates hold the vol- key and it should put you into fastboot mode
Click to expand...
Click to collapse
can't seem to boot in fastboot mode. My PC recognizes nexus 6 when its connected in normal mode so i know when its normally on. So i tried holding the power down button for 10 seconds or so and then tried holding the volume down button for several seconds and then connected it to PC but fastboot didn't recognize it neither my PC in general but after a while nexus 6 showed up on my PC which probably meant it rebooted normally without going into fastboot mode. any tips?
yasirrfc said:
can't seem to boot in fastboot mode. My PC recognizes nexus 6 when its connected in normal mode so i know when its normally on. So i tried holding the power down button for 10 seconds or so and then tried holding the volume down button for several seconds and then connected it to PC but fastboot didn't recognize it neither my PC in general but after a while nexus 6 showed up on my PC which probably meant it rebooted normally without going into fastboot mode. any tips?
Click to expand...
Click to collapse
Probably need to install drivers
holeindalip said:
Probably need to install drivers
Click to expand...
Click to collapse
tried installing the drivers twice. no luck...
holeindalip said:
Probably need to install drivers
Click to expand...
Click to collapse
it finally worked but after wiping it said erase successful, but not automatically formatting. cant determine partition type and then it said failed twice. dont know if it wiped it or not so ill leave my phone in fastboot mode for a while. any clues? should i flash a stock image on it or something?

My 3T went crazy and shut down by itself. Will only start up to the bootloader now.

This happened last night and my phone is currently running Paranoid Android with the latest TWRP and Magisk.
So I was holding my phone in my hand and when I checked my phone it was as if 5 pairs of hands were touching the screen. I was not touching the screen myself but the phone was opening all sorts of apps and locking itself and opening the app drawer in such a quick way that I could not even shut the phone down since when I tried to hold the power button to shut down the phone, I did not even have the time to press the power off option before the phone started going crazy again.
Once it reached about 5%, the phone shut off by itself. I've been trying to open it however it will only reach the bootloader screen. Once I try to open the phone to recovery or standard mode, the oneplus logo will appear but it will quickly shut down again after a few seconds. I tried flashing TWRP already but the phone still won't boot to recovery. The oneplus logo would appear but it just turns off around the time TWRP should be appearing.
Does this mean I bricked my phone? Is there any way to recover my photos and data currently on my phone?
Have you tried to leave the phone to charge overnight and then boot?
Check if TWRP boots with
Code:
fastboot boot twrp.img
Symbiotec said:
Does this mean I bricked my phone? Is there any way to recover my photos and data currently on my phone?
Click to expand...
Click to collapse
Unless you can at least boot TWRP (and then just mount storage or adb pull) I don't think you can retrieve much of anything.
It always surprises me that folks wait for a disaster (and then ask for recovery solutions), instead of regularly backing up the data that is important to you.
Honestly this sounds like hardware damage more than a software brick, can't be certain until the unbrick guide is done though. I have seen the same thing happen to other water damaged phones where it starts to randomly open applications then dies.
przemcio510 said:
Have you tried to leave the phone to charge overnight and then boot?
Check if TWRP boots with
Code:
fastboot boot twrp.img
Click to expand...
Click to collapse
I tried this however it said it could not find the file in the directory?
redpoint73 said:
Unless you can at least boot TWRP (and then just mount storage or adb pull) I don't think you can retrieve much of anything.
It always surprises me that folks wait for a disaster (and then ask for recovery solutions), instead of regularly backing up the data that is important to you.
Click to expand...
Click to collapse
I backup my files monthly, it just so happened that my phone went haywire a few days before I was gonna backup January's files.
ZVNexus said:
Honestly this sounds like hardware damage more than a software brick, can't be certain until the unbrick guide is done though. I have seen the same thing happen to other water damaged phones where it starts to randomly open applications then dies.
Click to expand...
Click to collapse
That's what I initially thought too. However, if it was hardware damage wouldn't that mean I couldn't open the bootloader?
Symbiotec said:
I tried this however it said it could not find the file in the directory?
Click to expand...
Click to collapse
Obviously you have to type twrp's .img file name or rename the file to twrp.img. Don't forget to download it first from https://twrp.me
Man i see kind of threads a lot lately. I feel there isn't any hardware damage, just people that don't know what they are doing or doing things wrong.
Download the twrp image and boot it through adb, if the oneplus logo appears than it HAS to at least boot the recovery. Also, before you do anything with your phone, considering it isn't the cheapest thing in the world(at least for me) do some reading first, it always helps.
Symbiotec said:
I tried this however it said it could not find the file in the directory?
Click to expand...
Click to collapse
That means you did it wrong.
As mentioned, the syntax has to be correct. If you use the command verbatim: fastboot boot twrp.img
Then the file has to be exactly named twrp.img and it needs to be located in the same folder where fastboot.exe is located (which is the same directory you need to be running the command from).
Also, if in Windows, and you renamed the file; make sure you have the Windows option disabled to hide known file extensions. It is usually enabled by default, so turn that option off! Otherwise, you may have unwittingly named the file "twrp.img.img" and not know it (the screen will show "twrp.img").
These are all common mistakes. But if your top post when you said "I tried flashing TWRP already but the phone still won't boot to recovery" it would have been more useful to tell us that if failed to flash.
przemcio510 said:
Obviously you have to type twrp's .img file name or rename the file to twrp.img. Don't forget to download it first from https://twrp.me
Click to expand...
Click to collapse
I tried running it in ADB and according to ADB, TWRP finished booting on the phone. The oneplus logo appeared with the text "fastboot mode" below it however the phone shuts down a few seconds after this screen appears. Is it still a problem in how I tried to boot the TWRP?
redpoint73 said:
That means you did it wrong.
As mentioned, the syntax has to be correct. If you use the command verbatim: fastboot boot twrp.img
Then the file has to be exactly named twrp.img and it needs to be located in the same folder where fastboot.exe is located (which is the same directory you need to be running the command from).
Also, if in Windows, and you renamed the file; make sure you have the Windows option disabled to hide known file extensions. It is usually enabled by default, so turn that option off! Otherwise, you may have unwittingly named the file "twrp.img.img" and not know it (the screen will show "twrp.img").
These are all common mistakes. But if your top post when you said "I tried flashing TWRP already but the phone still won't boot to recovery" it would have been more useful to tell us that if failed to flash.
Click to expand...
Click to collapse
My apologies. According to ADB the TWRP flash was successful however the phone still refuses to open in recovery.
Symbiotec said:
I tried running it in ADB and according to ADB, TWRP finished booting on the phone. The oneplus logo appeared with the text "fastboot mode" below it however the phone shuts down a few seconds after this screen appears. Is it still a problem in how I tried to boot the TWRP?
Click to expand...
Click to collapse
You were supposed to use fastboot command, is this what you meant?
przemcio510 said:
You were supposed to use fastboot command, is this what you meant?
Click to expand...
Click to collapse
I already performed the command in fastboot. Once the command was finished the oneplus logo appeared with the text "fastboot mode" below
I have "the same problem", but my OP I can turn on again.
I was using it with Ressurection Remix 7.1.2, so I tried to update to Z-Unleashed 8.0 and my problems start on this moment... So, I tried to reinstall the Ressurection, but it continue restarting .... I'm thining that's an hardware problem....
rodrigoo said:
I have "the same problem", but my OP I can turn on again.
I was using it with Ressurection Remix 7.1.2, so I tried to update to Z-Unleashed 8.0 and my problems start on this moment... So, I tried to reinstall the Ressurection, but it continue restarting .... I'm thining that's an hardware problem....
Click to expand...
Click to collapse
How did you fix the problem?
Symbiotec said:
How did you fix the problem?
Click to expand...
Click to collapse
I don't know. I think that it have emotions. Actually is working normally with Z-unleashed.
I entered in bootloader mode and:
"fastboot format -w system" (you'll lose all your data) and installed all again...
Default kernel...

Any help, i may have bricked my fire

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.

Bootloop

Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
I dont think there is way to get the pictures but you can fix the phone tho
_matze__ said:
Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
Click to expand...
Click to collapse
the photos has not synchronized with the google account?
maybe you can try with some tool like this
https://www.wondershare.net/ad/dr-fone/dr-fone-android.html
(it is difficult but you can try)
to reset the device in stock etc you can try with test points & edl mode ...If you have guarantee, send it to service but the photos will be lost of course...
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
_matze__ said:
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
Click to expand...
Click to collapse
Really IDK....Can work may or may not.Not all devices in the list,the list is updated but many users do not add their devices
there are other such applications.hit on google search for example : "recovery data from android phone"
and you will see and others like that
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
_matze__ said:
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
Click to expand...
Click to collapse
Reboot on edl mode & flash stock rom via miflash tool
if your device can boot on fastboot
"fastboot reboot edl" (need unlocked BT)
https://forum.xda-developers.com/showpost.php?p=78963902&postcount=6
from test points > edl > miflash tool (not needs unlocked BT)
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
(the better solution? If you have a warranty send it to service...All this needs some experience)

ADB Works, Fastboot still "waiting for any device"

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.

Categories

Resources