Database Develop

[Q] HTC one bricked? stuck on HTC logo

Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.

limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)

Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium

Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.

Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.

@rider5512 Sounds right to me. Thanks for clarifying.

Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?

limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.

crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?

limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache

limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.

crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".

limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?

crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.

I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium

hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.

limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.

limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.

Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.

if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq

Have I really bricked a Nexus phone??

Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.

claytonjn said:
Here's the story. Got Google Fi package and Nexus 6 today. Decided I'd load Android M preview on Nexus 6. did all the fastboot stuff to get the developer preview installed, then while still in fastboot mode I installed TWRP, then locked fastboot, then rebooted into TWRP. Pushed ROM zip to /sdcard through adb, tried wiping everything failed. Tried flashing zip, everything failed. Decided to reboot. TWRP asked me if I wanted to install SuperSU, i chose to because I thought I might need it to get TWRP working. After rebooting got message "Your device has failed verification and may not work properly" then it powers off. I can boot into fastboot/recovery, but in recovery the touchscreen doesn't work so I can't do anything. Booting normally gives the failed verification message. Tried fastboot format userdata, which I believe is what caused the touchscreen to cease registering in TWRP.
Is there any way for me to recover this thing? Back when I had a Galaxy Nexus, and even with my S5, there's nothing really that can be done that would completely brick the thing. I'm pretty dumbfounded that a Nexus device would be so easily bricked...it's not like I don't have experience with this stuff, I've been rooting and developing Android apps for years.
I have a feeling I have to return the thing, but Amazon has no more stock, and if I buy directly from Google or Motorola I'll have to pay sales tax.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you lock the bootloader just to be clear?

bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.

gee2012 said:
Did you lock the bootloader just to be clear?
Click to expand...
Click to collapse
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
simms22 said:
bricked? no, you just didnt read up in information properly. you relocked your bootloader. as of android 5.0, you have to enable unlocking the bootloader after you boot up in the developer section. since you relocked your bootloader before you checked if your device will boot, you can not unlick your bootloader again, which means you can not use twrp either. what you can try is using fastboot to wipe your cache and data. if that doesnt work, id try to get an rma.
Click to expand...
Click to collapse
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk

have you tried fastboot oem unlock again ?

uicnren said:
have you tried fastboot oem unlock again ?
Click to expand...
Click to collapse
Yes, it says it needs to be enabled in developer options
Sent from my Developer Edition Galaxy S5 using Tapatalk

when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.

uicnren said:
when you get the failed verification message, what happens after that?
does it ever make it to the M preview?
Also if you wait a little while after that message, you may be able to use adb commands again.
I had the same thing happen with M and TWRP and was able to recover it.
Click to expand...
Click to collapse
It says it will reboot in 5 seconds, but after 5 seconds the screen just goes blank. It appears the device is off, but maybe not.
Do you know what adb commands I would need to use to recover from this state?
Sent from my Developer Edition Galaxy S5 using Tapatalk

claytonjn said:
Yes. I still remembered all of the flashboot commands from my Galaxy Nexus. It didn't even occur to me to look anything up.
If a device is unusable, without any way to recover it, it's essentially a paperweight, or bricked. So if my only option is an RMA, then it is bricked. I don't mean to sound rude or argumentative by the way... I appreciate your help. Just clarifying the semantics.
Debt from my Developer Edition Galaxy S5 using Tapatalk
Click to expand...
Click to collapse
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.

well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.

simms22 said:
technically, its not bricked, not yet anyways. as many people have fixed this issue using fastboot to wipe cache and data.
Click to expand...
Click to collapse
Unfortunately that is not working for me (Not allowed in locked state!)
uicnren said:
well, let it sit for a few minutes after the message, it may just boot normally. That verification message appears with M preview for many users.
you may also see HERE for another possible solution.
if adb is working, chances are pretty good its booting into android, in which case you wont need to do anything else, but let it boot (be patient, it can take several minutes), then retick the selection to allow oem unlock.
Click to expand...
Click to collapse
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.

Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...

claytonjn said:
Unfortunately that is not working for me (Not allowed in locked state!)
ADB works when I boot to TWRP, but when I try to boot normally, after the device will boot in 5 seconds message, the screen goes blank and adb does not work. I let it sit like that for more than 30 minutes. Curiously, when the screen goes blank my PC does chime indicating hardware has been attached.
Click to expand...
Click to collapse
If you have TWRP, boot to bootloader and use the following fastboot commands:
fastboot format userdata
fastboot format cache
Then boot to TWRP, connect to PC. Download a ROM to your PC and drag and drop in the root of internal storage. Then flash the ROM from TWRP, boot up, enable OEM unlock. Then boot back to bootloader and:
fastboot oem unlock
You should be good after that.

holeindalip said:
Can you still get into twrp? If so just move a ROM over to it and flash that, enable OEM unlock restart and unlock boot loader...
Click to expand...
Click to collapse
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.

claytonjn said:
I can boot into TWRP. At first it was "working" but it couldn't mount /data so I couldn't really do anything (that was the first thing I tried.) Now however when I boot to TWRP it doesn't respond to touch at all... I can get into a shell with adb, but I haven't figured out anything to do from there.
Click to expand...
Click to collapse
Follow my instructions listed above.

Evolution_Tech said:
Follow my instructions listed above.
Click to expand...
Click to collapse
II'm attempting that now.but fastboot format userdata and fastboot format cache fail. after booting into twrp the Nexus shows up in My Computer, but internal storage does not. I can push a ROM zip to the device with adb, but haven't figured out how to flash it yet because touch doesn't work...

SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!

claytonjn said:
SUCCESS! I was able to flash the ROM .zip using ADB in TRWP using
Code:
ADB push ROM.zip /sdcard/.
ADB shell
twrp install /sdcard/ROM.zip
THANK YOU EVERYONE!
Click to expand...
Click to collapse
glad you got it back, persistence pays off.

Lesson learned today? QUIT RE-LOCKING YOUR BOOTLOADER!

You can lock boot loader, you just have to make sure your phone boots first before locking it

Nexus 6 - Can't boot TWRP recovery

I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.

simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.

briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention

So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?

simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.

No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.

ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.

nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.

50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.

ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.

Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.

ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.

So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.

ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?

Moto E5 play only boots to TWRP.

Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.

foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.

MotoJunkie01 said:
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
Click to expand...
Click to collapse
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3

foxcell said:
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
Click to expand...
Click to collapse
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2

MotoJunkie01 said:
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
Click to expand...
Click to collapse
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!

foxcell said:
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
Click to expand...
Click to collapse
Good luck. And just follow the instructions to the letter and it'll go smoothly.

Well I got some bad news... phone is stuck in a boot loop now, and no longer loads TWRP. I followed your directions and Oreo installed with no errors or warnings. Since going to Reboot -> System, it boots, says "N/A", then reboots.
I can get out of the boot loop by pressing volume down + power key, and from there I can access Android recovery (says 'bad key' when booting, instead of 'N/A') which gives me various options. It can still read SD cards and even says the proper OS.
I think it can still be saved since I can access Android recovery. I haven't tried the format system or cache options from Android recovery, because that might permanently screw it up.
Anyways... I'm here if you have any advice on what I can do. Maybe I should of bought an E4, lol.

Would you suggest I follow this?
https://forum.xda-developers.com/moto-e5/how-to/firmware-restoring-moto-e5-play-to-t3820053
I have no data on the phone so everything can be wiped no problem.

MotoJunkie01 said:
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Click to expand...
Click to collapse
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.

foxcell said:
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
Click to expand...
Click to collapse
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.

MotoJunkie01 said:
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
Click to expand...
Click to collapse
I did as followed, and phone is restored!!! Now when starting up it says "bad key" so I assume that means bootloader is still unlocked?
I still want to root and such, but I think I'll wait because rooting instructions I found were vague and trying to follow them got me into the situation I was in, lol.
Thanks for your help!!

foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77283595&postcount=196

Xiao Mi A2 "Can't load Android system"

Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.

I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?

blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video

Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?

My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:

epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again

blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again