Related
Hi there guys!
My Xiaomi Hongmi S1 couldn't pass the boot phase after me trying to install Xposed. Then, the software Mi Phone Manager tried to recover the system files with the phone in fastboot (in this phase I still could enter fastboot and recovery) - somewhere along this process I had to leave and, when I came back, I had an error message in the software and the phone was turned off. After this I could not turn the phone on anymore, not even into fastboot or recovery.
MiFlash detects the phone even like this, but is unable to flash things into it.
PLEASE, HELP ME!
Someone?
Go in fastboot to pc
(you probably see anything on your phone)
On PC you can see if you are in fastboot by
Klicking on Refresh button on MiFlash you will see that you are connected
And Flash stock rom
See On thread (1)
(Also See MiFlash Picture from Thread)
Link: forum.xda-developers.com/showthread.php?p=53594673#post53594673
If that fails, your phone is probably broken.
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.
So by now most of you have seen the DFU MultiDL tool by @raystef66 only you had to switch from Multi tool to Miflash or Edl Tool.
I have worked out how to get Edl working in this tool.
First of all this tool was designed to run on Windows 7 so in Windows 10 it didn't seem to function properly.
So I set it to Windows 7 compatibility first off to see if it would work.
I had better results with phone detecting and saying connected instead of disconnect.
Next the phone needed to be booted into FTM mode if you are just flashing an Edl package, if your phone is in DFU it skips this step as per the instructions below.
Next I found it was better to place the Edl package within the MultiDL tool folders.
C:\program files > DFU MultiDL tool > DA > SMT > firehose and overwrite the exsiting firehose file.
Pics posted below show instruction (tranlated from Chinese to English) and MultiDL tool in flashing progress (sorry they are not very clear)
I hope this helps
I am trying to relock my bootloader to send my phone in for a warranty replacement, but EDL mode is disabled because I'm on B35. Can I use this tool to achieve that? I'd appreciate any help...
parmar.saab said:
I am trying to relock my bootloader to send my phone in for a warranty replacement, but EDL mode is disabled because I'm on B35. Can I use this tool to achieve that? I'd appreciate any help...
Click to expand...
Click to collapse
Boot your phone into FTM mode to start the process, it should switch to Edl mode.
This tool won't lock the bootloader, however some Edl packages will have a locked boot image.
If your Edl is still locked try the Edl tool by Djkuz.
Start Edl tool as admin, boot into FTM to start, follow the on screen instructions then unlock then choose Edl fix.
You may be able to lock the bootloader with Edl Tool or use the Axon 7 tool kit to relock.
I hope this helps
Syberclone said:
Boot your phone into FTM mode to start the process, it should switch to Edl mode.
If your Edl is still locked try the Edl tool by Djkuz.
Start Edl tool as admin, boot into FTM to start, follow the on screen instructions then unlock then choose Edl fix.
I hope this helps
Click to expand...
Click to collapse
This is the error I get in the EDL tool:
parmar.saab said:
This is the error I get in the EDL tool:
Click to expand...
Click to collapse
I can't get the pic to show properly, what is the error?
Make sure you have the Edl tool in the root directory of the drive.
Eg: C:\ or D:\ for it to operate properly.
Can you boot to FTM?
parmar.saab said:
This is the error I get in the EDL tool:
Click to expand...
Click to collapse
What happens if you use the key combination? Hold Vol+, Vol- and power. If there's a constant red LED then you're on DFU. Right after just use this tool and you'll get to EDL
But I don't get it? If you want to relock the bootloader, you'll have to roll back to B19. If you'll do so just flash the stock recovery and use a B19 package from ZTE US
Choose an username... said:
What happens if you use the key combination? Hold Vol+, Vol- and power. If there's a constant red LED then you're on DFU. Right after just use this tool and you'll get to EDL
But I don't get it? If you want to relock the bootloader, you'll have to roll back to B19. If you'll do so just flash the stock recovery and use a B19 package from ZTE US
Click to expand...
Click to collapse
Here's my situation:
I have an A2017U, that was initially running 15.1 and developed an issue that requires me to send it in for a warranty exchange. I found a thread to return it to stock, which left me on B35 stock with TWRP still intact. However, my bootloader if still unlocked, and I need to relock it before sending the phone in. I am somewhat of a noob when it comes to this, but what exactly would I need to do in order to relock the bootloader? I'd greatly appreciate it if you could point me in the right direction.
parmar.saab said:
Here's my situation:
I have an A2017U, that was initially running 15.1 and developed an issue that requires me to send it in for a warranty exchange. I found a thread to return it to stock, which left me on B35 stock with TWRP still intact. However, my bootloader if still unlocked, and I need to relock it before sending the phone in. I am somewhat of a noob when it comes to this, but what exactly would I need to do in order to relock the bootloader? I'd greatly appreciate it if you could point me in the right direction.
Click to expand...
Click to collapse
well, as a first you could respond to my question ?
If you can get into EDL by the key combination, then you're done. Just use a B19 EDL package to go back and you'll have fastboot there. After that, run the command to relock
Choose an username... said:
well, as a first you could respond to my question
If you can get into EDL by the key combination, then you're done. Just use a B19 EDL package to go back and you'll have fastboot there. After that, run the command to relock
Click to expand...
Click to collapse
That's the problem, the key combination doesn't work to get the phone into EDL mode (I'm guessing it's because it is disabled on B35). In essence, I don't have fastboot access. I tried relocking in FTM but get the error as shown in the picture.
parmar.saab said:
That's the problem, the key combination doesn't work to get the phone into EDL mode (I'm guessing it's because it is disabled on B35). In essence, I don't have fastboot access. I tried relocking in FTM but get the error as shown in the picture.
Click to expand...
Click to collapse
still you don't really respond. What HAPPENS when you use the key combination? Does it reboot? Does it stay black and show a red LED? Black with no LED?
Anyways, you can enter EDL simply by enabling adb and issuing "adb reboot edl" from the system. (or from FTM). it just seems weird that it would reboot, because usually the phone just goes into DFU when you use the combination
When I use the button combination, the phone shows a blank/black screen with a solid red notification light. However, I get no response on any commands from the Axon 7 Toolkit.
@Syberclone: Thanks for the recommendation to run the tool in Win7 compatibility mode, I have Windows 10 and the tool always shows as disconnected. I can use the tool to switch from DFU to EDL, no problem, but could never figure out how to use it to flash an EDL.
I'd like to point out that FTM isnt accessible if you're not running a stock-based ROM. In all my tests I was never able to boot into FTM on custom ROMs like LineageOS, AOSP Extended, etc.
However, if you can boot directly into EDL with the buttons, or can use this tool to switch from DFU to EDL, then access to FTM doesn't matter.
@parmar.saab: A black screen with a solid red light is DFU mode, you need to use the DFU MultiDL Tool to switch from DFU to EDL. EDL is a black screen too, but has a red light that will turn off if you use the button combo. In other words, it will blink rather than staying solid. Then you can use the Axon 7 Toolkit or Axon 7 EDL Tool to flash an EDL. Or you might be able to flash with the DFU tool, if you can get it to work.
@AnonVendetta No problem
It took me a while to work it out, a bit over 2 hours of testing and retesting using my Axon.
I didn't want to put it in to DFU to do a full test, however it worked a treat once I got it sorted.
FTM was as per the Chinese instructions not actually mine, apparently if the phone is in DFU the app will work accordingly.
Hello
I tried to flash a custom rom on my Nord N10 --> [ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie] <--
At 47%, the flash stopped. I tried it a several times but always with the same result.
I did a factory reset in twrp, since then all was gone from internal storage.
And now I'm unable to flash ANY rom on the device.
I tried a lot of ways: flashing stock rom with stock recovery, flashing different custom roms in twrp and other recoveries, Msmtool, extracting payload.bin and flash all the images in fastboot (I followed the commands at the bottom of this page), ... but I haven't got the result I wanted.
I even got into "Qualcom crash dump mode". That's when I tried to use the MsmDownloadTool but it wouldn't recognize any COM port.
I can transfer .zip files to the internal storage when using twrp, but flashing always fails (see attached file).
Sideloading in PE or Lineage recovery works, but flashing fails (2nd attached file).
Overview:
Positives:
bootloader is unlocked
fastboot is accessible
fastboot commands are working so I'm able to flash by fastboot command
recovery is accessible and different versions can be flashed
internal storage is accessible and copying files is possible (though, folders like Android, DCIM, downloads, etc... are all gone)
Negatives
Msmtool doesn't recognize the COM ports
some images (like vendor.img) can't be flashed in fastboot when extracted from the rom by using Payload Dumper
error shown in twrp (file attached)
neither can a rom be flashed in PE recovery or Lineage recovery
Anyone able and wanting to help or provide a link to a tutorial? I don't care which rom is installed, I just want to get the phone working again and at this point I fail to see what I'm doing wrong.
Kind regards
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
I'll look into it and give it a try. Thanks!
SomeRandomGuy said:
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
Click to expand...
Click to collapse
Couldn't get into EDL mode (I tried EVERYTHING). I updated/repaired the Qualcomm drivers, re-flashed another version of twrp and was able to flash this rom in twrp after I copied the rom to the sd card. It worked, the N10 is back alive again.
Hi everyone, I bought this phone working from second hand but the seller told me he tried to unlock the bootloader without success and the phone still loose the fingerprint sensor, so I decided to unlock the bootloader successfully following THIS thread and made a downgrade to Android 9 according to THIS other tutorial hopping to get it work again but I wasn't able to do it, so I decided to just use LGUP to install the same Android 12 that I had but the problem started at this point because once the KDZ was installed successfully, the deviced got a bootloop but I still was able to get into EDL, Fastboot and Download Mode, so I tried the steps from THIS other thread to unbrick it but it got even worse at this point, I flashed all the abl, xbl, etc. partitions and the "rawprograme files" via QFIL and then the phone won't even gave any life signals. I contacted someone that some months ago had the same problem and he told me that I could get into EDL by short pining the test point on the motherboard, which actually worked, so I extracted the KDZ Android 9 rom that I flashed in the first place to get the original abl, xbl, etc. partitions that I crossflashed from a v50 (Which I downloaded from the corresponding thread for unbrick), in other words I flashed the same partitions with the correct v50s files instead other model ones. So now this is where I'm right now, the phone don't turns on at all but when I connect it to the PC it gets recognized as LGE Android Platform USB Serial Port (COM11) and the buttons combinations don't work at all, so still can't get into Download mode by any method or even turn off the device, but I still can disconnect the battery and short pin the Qualcomm 9008 mode to use QFIL.
Would someone please be so kind of telling me how could I recover the Download Mode to use the COM4 and COM5 ports to flash the phone via LGUP?. According to THIS other thread, I could get the correct XML "rawprograme files" for my device (which I crossflashed with the v50) from a KDZ using some tools and Python, but I have to be honest: I DON'T KNOW HOW, even with the step by step tutorial.
At this point I think this would be the right step, to flash all the original files for my model and get the Download Mode back to be able to flash the KDZ rom via LGUP and update via OTA to Android 12 again to avoid the bootloop problem.
try to reflash(QFIL method) modified abl should get the download mode back
darrelama said:
try to reflash(QFIL method) modified abl should get the download mode back
Click to expand...
Click to collapse
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
iMarzateD said:
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
Click to expand...
Click to collapse
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
darrelama said:
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
Click to expand...
Click to collapse
Hello again, already tried flashing the engineering abl but I still can't get into download mode. The phone keeps off the whole time and by plugging in the USB cable, no matter what button combination, the PC always recognizes it as the same LGE Android Patform USB Serial Port (COM11), the only other state of the device is the Qualcomm 9008 by pinning the motherboard. This specific COM11 state never was able to flash anything by PC, I don't know what actual mode is, but when I was able to set the devide in Download Mode the PC always showed 2 devices in the Device Manager, the COM5 and the COM4, that way I knew I was able to use the LGUP to flash. I'm thinking that I'm not setting the phone on the correct state to flash by any method, but since the buttons seems not to work, I don't know how could I do it.
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
ardian1899 said:
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
Click to expand...
Click to collapse
Thanks, I'll try that for sure to see if I can get into the Download Mode or something. I would appreciate so much if you could share your backup, since I think I could restore the whole firmware with it, but I don't have any experience on the "LUNs" tho. I'm any case, I don't have too much time every week to give it a try, so I hope tomorrow I could test the combo you say.