Database Develop

Required Help with connecting phone to PC in order to root

I am trying to root my device, to the final goal of installing a Nougat build on it. Been browsing through lots of guides, including this one which looks rather friendly:
https://www.idroidspace.com/how-to-root-htc-one-m7/
The problem is that the software did not recognize my phone.
I have enabled USB debugging. the PC detects the phone, I also have HTC Driver installed (downloaded HTC Sync Manager).
I also unlocked the boot-loader in the past, with success to the best of my knowledge (anyway I can confirm?).
Another problem I got that may come from the same source is that when opening command prompt and putting ADB Devices it wouldn't detect anything.
I have already old version of TWRP installed but I cannot flash the nougat from it, and in order to update the TWRP I wanted to root the device.
Am pretty much a beginner but can follow orders.

Droriley said:
I am trying to root my device, to the final goal of installing a Nougat build on it.
Click to expand...
Click to collapse
It's a waste of time to root if you're planning to flash a Nougat rom. It's a well spread misconception when ppl say "I want to root my phone" cause you're not rooting the phone, you're rooting the operating system on it (the rom). Most custom roms are pre-rooted so when flashing it on your phone you'll already have root. If you flash a non-rooted rom over your already rooted rom, you'll loose root hence why it's a waste of time to do it now. The only thing needed to flash a custom rom is a unlocked bootloader and a custom recovery.
Been browsing through lots of guides, including this one which looks rather friendly:
https://www.idroidspace.com/how-to-root-htc-one-m7/
The problem is that the software did not recognize my phone.
Click to expand...
Click to collapse
Outdated guide and tools
I also unlocked the boot-loader in the past, with success to the best of my knowledge (anyway I can confirm?).
Click to expand...
Click to collapse
Reboot in bootloader mode and check the first line of text it will either be ***LOCKED*** ***UNLOCKED*** or ***RELOCKED***
Another problem I got that may come from the same source is that when opening command prompt and putting ADB Devices it wouldn't detect anything.
Click to expand...
Click to collapse
Make sure you have the latest drivers version. ADB commands are only usable when booted in the OS with usb debugging turned on and you also need to unlock your screen once after connecting the phone to your PC. ADB commands will also work when booted in TWRP recovery. WIll not work in bootloader mode where you have to use FASTBOOT commands.
I have already old version of TWRP installed but I cannot flash the nougat from it
Click to expand...
Click to collapse
What is your twrp version and what rom do you want to flash? What is your "fastboot getvar all" ?
and in order to update the TWRP I wanted to root the device.
Click to expand...
Click to collapse
You don't need root to update TWRP, just flash the latest version using fastboot in bootloader mode:
Code:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader

Alray, thanks for your thorough reply. I'd appreciate further help.
Reboot in bootloader mode and check the first line of text it will either be ***LOCKED*** ***UNLOCKED*** or ***RELOCKED***
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/s/iyxepbaiu4x1uva/2017-06-12 00.23.29.jpg?dl=0
I believe the Bootloader is indeed unlocked.
Make sure you have the latest drivers version. ADB commands are only usable when booted in the OS with usb debugging turned on and you also need to unlock your screen once after connecting the phone to your PC. ADB commands will also work when booted in TWRP recovery. WIll not work in bootloader mode where you have to use FASTBOOT commands.
Click to expand...
Click to collapse
I don't know where from do I get the latest ADB drivers. As said, I downloaded HTC Sync Manager.
USB Debugging is turned on.
I tried in TWRP Recovery - still with no success.
What is your twrp version and what rom do you want to flash? What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
https://www.dropbox.com/s/n8gojoe3jgv8wzm/2017-06-12 00.24.19.jpg?dl=0
You don't need root to update TWRP, just flash the latest version using fastboot in bootloader mode:
Click to expand...
Click to collapse
Much like trying to flash the below rom - I was not able to flash the newer TWRP.
https://www.dropbox.com/s/l2wvgrhjgifjlcp/2017-06-12 00.24.51.jpg?dl=0
https://www.dropbox.com/sh/jhmyj852saithxa/AABalcp37aOSFrI2FTarRTUoa?dl=0
Code:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Need assistance with the step before.

Droriley said:
Alray, thanks for your thorough reply. I'd appreciate further help.
https://www.dropbox.com/s/iyxepbaiu4x1uva/2017-06-12 00.23.29.jpg?dl=0
I believe the Bootloader is indeed unlocked.
I don't know where from do I get the latest ADB drivers. As said, I downloaded HTC Sync Manager.
USB Debugging is turned on.
I tried in TWRP Recovery - still with no success.
https://www.dropbox.com/s/n8gojoe3jgv8wzm/2017-06-12 00.24.19.jpg?dl=0
Much like trying to flash the below rom - I was not able to flash the newer TWRP.
https://www.dropbox.com/s/l2wvgrhjgifjlcp/2017-06-12 00.24.51.jpg?dl=0
https://www.dropbox.com/sh/jhmyj852saithxa/AABalcp37aOSFrI2FTarRTUoa?dl=0
Need assistance with the step before.
Click to expand...
Click to collapse
TWRP 2.6.3.0 is really outdated. This version does not have the required kernel to support the fstab file system used by recent roms. You need at least twrp 2.7.1.1, or the latest version: 3.1.N0.0
Are you using the original usb cable that came with the phone? If no you might want to double check if your usb cable is capable of data transfer (there are usb cables that only have the +5v and ground connections for charging but not the data+ and data- connections). Try another usb ports/cable.

alray said:
TWRP 2.6.3.0 is really outdated. This version does not have the required kernel to support the fstab file system used by recent roms. You need at least twrp 2.7.1.1, or the latest version: 3.1.N0.0
Are you using the original usb cable that came with the phone? If no you might want to double check if your usb cable is capable of data transfer (there are usb cables that only have the +5v and ground connections for charging but not the data+ and data- connections). Try another usb ports/cable.
Click to expand...
Click to collapse
This one ain't good? https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
any other way I can sort it out? I cannot manage to connect to my phone via command promp - I tried both in Fast boot and in Recovery.
PC feels the phone though - when on normal landing page I can see the phone content on explorer + it generates HTC Sync Manager.
Any way I can flash the updated TWRP from phone itself?

Droriley said:
PC feels the phone though - when on normal landing page I can see the phone content on explorer + it generates HTC Sync Manager.
Click to expand...
Click to collapse
You need to uninstall HTC sync manager, otherwise it will not work.
Or eaven better way is to install just naked drivers instead of sync manager.

Tarx100 said:
You need to uninstall HTC sync manager, otherwise it will not work.
Or eaven better way is to install just naked drivers instead of sync manager.
Click to expand...
Click to collapse
Where from?
Sent from my SM-G920F using Tapatalk

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

Help! Stuck on "Charging screen" after uninstalling magisk.

I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.

Try power button + Volume down for up to 10 seconds.....should shutdown and reboot after a few seconds of shutdown
(Meaning, it will shutdown and appear to just be off.....but it will actually start to reboot after a few seconds of nothing.....so be prepared/ready to do the button mash to boot to recovery......it will vibrate once as it begins to boot again....
*****edit.....
Sorry I'm in the wrong thread (different phone), but its possible you need to press and hold power plus volume up/or volume down.
Best of luck
Sent from my [device_name] using XDA-Developers Legacy app

Thank you for the suggestion, but sadly for me it doesn't work. My phone doesn't shutdown at all and is just in this perpetual charging state even after holding the power button for 30 seconds.

Hanzor said:
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Click to expand...
Click to collapse
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again

reg66 said:
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
Click to expand...
Click to collapse
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.

Hanzor said:
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Click to expand...
Click to collapse
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo

reg66 said:
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
Click to expand...
Click to collapse
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.

Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?

reg66 said:
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
Click to expand...
Click to collapse
I'm not very familiar with how it works, if it's okay I would be glad to be guided.

Hanzor said:
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Click to expand...
Click to collapse
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude

reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
That's alright, I'm fine with later or tommorow as well. Rest well, and thanks!

reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?

Hanzor said:
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Click to expand...
Click to collapse
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck

reg66 said:
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
Click to expand...
Click to collapse
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!

Hanzor said:
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Click to expand...
Click to collapse
Excellent. Glad it's all good again :good:

Phone stuck at black Mi logo

Hello, I never experienced this before so here I am trying to find some explanation, hopefully it's the right place... I have a Xiaomi Mi 5 Pro, few years old, sometimes slow but otherwise perfect, I changed the battery couple times.
Today I noticed it was at around 20% charge, I plug it to the wall, and leave it on the bed (turned on). After a few hours I go back to check on it and found the 100% indicator, but the phone was turned off.
I obviously try to turn it back on, but it gets stuck at the Mi logo (black screen with "unlocked" text below). I have installed a MIUI.eu rom ver. 11, twrp 3.2.3-0 recovery, and everything has been fine for years. I tried several times, still Mi logo (it's not bootloop, it's just stuck).
Suprised, I try to boot into recovery, and there I noticed that all the partitions are marked empty 0 bytes. I tried several things like backup, switching file format, restoring file system, etc., but it just won't work. It's like it has all been wiped and can't be mounted again.
I connected it to my desktop, MTP enabled from twrp, device recognized, storage completely empty. I remember I could see files there just the other day...
I tried all possible wipes, they won't work, either can't mount the partitions or other errors.
I already asked for suggestions elsewhere, which pointed me to fastboot flash using the adb/fastboot tools on Windows.
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Also if I boot in recovery, I can see it detected in the adb/fastboot tools screen, the scary part is that there it says "Bootloader: locked" (but it has been unlocked for years, and it even says unlocked in the black Mi screen!)
I'm lost, I never had anything like this, any suggestions to save the device? I would be really grateful

ZexDC said:
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Click to expand...
Click to collapse
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.

Indie Zex said:
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.
Click to expand...
Click to collapse
Thanks it was the driver stopping the fastboot.
Now I still cannot flash anything though, I get the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried different roms, different MiFlash, from terminal, but same error.
From recovery I still see empty not mounted partitions.
Any other suggestions?

Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.

Indie Zex said:
Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.
Click to expand...
Click to collapse
Yes that was the first thing I tried unfortunately that's where I found out something was off... I can't wipe any partition, I can't mount any partition, I tried to switch filesystem but no luck.
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...

ZexDC said:
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...
Click to expand...
Click to collapse
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...

Indie Zex said:
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...
Click to expand...
Click to collapse
It's very weird, I've been flashing lots of stuff in the past but I've never been locked out like this.
And the joke is that the black Mi logo screen still says "unlocked" as it should be... no idea, maybe it is programmed to just give up after some years.

Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.

Indie Zex said:
Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.
Click to expand...
Click to collapse
I tried that, it gives the following error:
I noticed that even from MiFlash the device id sometimes disappears, not sure if that's the no link error

I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)

Indie Zex said:
I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)
Click to expand...
Click to collapse
Thanks for trying I really appreciate. I did follow the tutorial, same error.
It's like the internal storage got fried or something? I have no clue

How To Guide [GUIDE] Converting OnePlus Ace(ColorOS) to OnePlus 10R(OxygenOS)

Few things to keep in mind before starting the process:
If you are on ColorOS12 make sure you are flashing OxygenOS12 and NOT OxygenOS 13; similarly if you are ColorOS13 you will have to use OxygenOS13 zip.
You must ALWAYS use OxygenOS newer than the ColorOS you have currently installed.
[English] Written Instructions:
(Note this is for 10pro, steps are the same but DON'T use any firmwares mentioned there)
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
[Chinese] Written Instructions:
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
Video Tutorial:
Downloads Links:
80W_C.15_OOS_Android13
150W_C.15_OOS_Android13
You can also follow the same instructions if you wish to convert to ColorOS. Just make sure you use ColorOS zip in that case.
Download link for ColorOS:
150W_ColorOS_C.17_Android13

I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-cow partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 3.
If you completed step 3, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.

I
6cdh said:
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-com partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 2.
If you completed step 2, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
Click to expand...
Click to collapse
In the Step #7, it should be *-cow partitions, No?

yashaswee1708 said:
I
In the Step #7, it should be *-cow partitions, No?
Click to expand...
Click to collapse
Ah, yes, it's a typo. edited.

I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sSjBlueVN197 said:
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.View attachment 5876919
Click to expand...
Click to collapse
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip

yashaswee1708 said:
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
Click to expand...
Click to collapse
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....

sSjBlueVN197 said:
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
Click to expand...
Click to collapse
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)

yashaswee1708 said:
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
Click to expand...
Click to collapse
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly

Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings

sSjBlueVN197 said:
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
Click to expand...
Click to collapse
Try factory reset from recovery?

sSjBlueVN197 said:
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Click to expand...
Click to collapse
If you can boot in fastboot do the process again. I'll share the zip once again

oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!

after flashed OOS, can I re-lock bootloader?

sSjBlueVN197 said:
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
Click to expand...
Click to collapse
Let me know if the issues are fixed

sSjBlueVN197 said:
after flashed OOS, can I re-lock bootloader?
Click to expand...
Click to collapse
You can but the process is a bit complicated, on recent updates some time the phone is bricking when we run the query fastboot flashing lock.
So I won't recommend it. Until we can find a easier way.

yashaswee1708 said:
Let me know if the issues are fixed
Click to expand...
Click to collapse
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^

sSjBlueVN197 said:
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
Click to expand...
Click to collapse
So currently everything is okay?

yashaswee1708 said:
So currently everything is okay?
Click to expand...
Click to collapse
yup, everything is OK

80W_C.15_OOS_Android13 it's for Ace racing bro?