Hi everyone,
I seriously need some advices since I can't manage to solve my problem.
BEFORE YOU READ:
A month has passed, and I couldn't manage to recover my phone. I decided to buy a brand new phone for my brother.
The thread is going to stay there, since I hope it could be useful for people luckier than myself
The Problem:
My brother found his phone (the Redmi Note 6 Pro) turned off.
He wasn't able to turn it on.
I could manage to wake it up by pressing volume-up + power
very strangely, it directly turned into the OS (and not into the TWRP)
"but ok, at least it turned on" I thought
After only a few minutes, the phone suddenly turned off and from there my journey started to became a p**p
I'm not able to enter into recovery, and I'm not able to enter into fastboot neither.
I realized that the phone is fu--- ehmm I mean bricked. The funny thing is that we haven't done anything strange.
Some useful informations:
latest TWRP was installed
I was on the latest Pixel Experience Extended ROM (Android 11)
No custom kernel (I kept the kernel included in the PEE ROM)
No Root
What I tried:
Since it was impossible to do anything, I followed some guides (found here and on Youtube as well) and I opened my phone (if I'm lucky, I haven't destroyed anything ---- YET ).
I managed to enter in EDL mode
my Windows PC is able to recognize it on the COM / LPT ports as Qualcomm HS-USB QDLoader 9008
I downloaded the Mi Flash Tool
I downloaded the Boot Firmware and the two special files (prog_emmc_firehose_Sdm660_ddr.elf and prog_emmc_firehose_Sdm660_lite.elf) following this video link (please don't blame me, but I haven't found anything here)
I put the files inside the image folder
I tried to flash the firmware via Mi Flash but I got a funny error: "cannot receive hello packet"
Thinking that I was doing something wrong, I downloaded the latest Mi Flash Tool but nothing
I downloaded the latest tulip global image but nothing
I authenticated with the mi account into the tool (technically it shouldn't be needed) and... guess what? nothing.
I'm totally out of ideas. Of course I tried to reconnect the phone multiple times (shortening the two pins every time). I also tried to disconnect the battery and going USB-power-only.
Every time I get the "cannot receive hello packet" error, and suddenly the procedure fails saying "Riferimento ad un oggetto non impostato su un'istanza di un oggetto" (italian, that means "Object reference not set to an instance of an object").
EDIT: this error is also listed as "Null Reference Exception" (since it seems to be caused by the following exception: "System.NullReferenceException" - as you can read in the log I included)
Any ideas? What else can I try? Have I done anything wrong?
This never happened me before in almost 10 years of flashing. And, you know what? I just learned how to destr--- ehm open a phone! (...I used the little metal tab inside a Monster Energy can as tool *coff coff* -- C Y B E R P U N K)
Thanks to everyone that will try to help me. Every suggestion is appreciated*
*but please don't suggest me a trash can
Mi Flash Log:
Spoiler: Mi Flash Log
[15:18:15 COM6]:MiFlash 2020.3.14.0
[15:18:15 COM6]:vboytest index:6
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:sw in images
[15:18:15 COM6]:flash in thread name:COM6,id:15
[15:18:15 COM6]:vboytest do open :
[15:18:15 COM6]: serial port COM6 opend successfully
[15:18:15 COM6]:[COM6]:start flash.
[15:18:16 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:try to reset status.
[15:18:17 COM6]:Switch mode back
[15:18:17 COM6]:cannot receive hello packet,MiFlash is trying to reset status!
[15:18:17 COM6]:System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
in XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[15:18:17 COM6]:no provision exit:COM6
[15:18:17 COM6]:flashSuccess False
[15:18:17 COM6]:isFactory False CheckCPUID False
[15:18:18 COM6]:before:flashSuccess is False set IsUpdate:True set IsDone True
[15:18:18 COM6]:after:flashSuccess is False set IsUpdate:false set IsDone true
Little Update:
tried to disable windows' driver signature: same issue
tried to disconnect the phone display (seems weird, but why not giving it a chance): same issue.
I also downloaded Mi Flash Pro, which should work even without an authorized Mi account. But I get the same damn error.
Disperate up. You guys are my last hope.
Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!
fawziX said:
Hello @Gh_Racer I got the exact same problem. Found my phone turned off 2 days ago, when I tried to turn it on the miui logo appeared. turned off and that was it. Not been able to turn it on after that. Did u by any chance fix the problem? Thanks!
Click to expand...
Click to collapse
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.
Gh_Racer said:
Damn, really? That's pretty disappointing. These cases are becoming suspicious... maybe that could be some kind of programmed obsolescence(?)
Just for curiosity: were you on stock MIUI or did you have any kind of modifications?
Unfortunately, I couldn't manage to do anything so far.
I loaned my old OnePlus 5T to my brother for now and I think that we'll buy a Redmi Note 10 as soon it will became available in our country. Of course I'm still here for any kind of suggestion until then.
Click to expand...
Click to collapse
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)
fawziX said:
I was on the official MIUI, I didn't do any kind of modifications to the phone. I found it also weird that we have the same problem around the same time. Maybe it's related to an automatic update? mine was like that when I woke up in the morning the day before it was in perfect condition. Let me know if u manage to somehow fix it and I'll let u know if i get it working. (btw I also ordered a new XIAOMI phone red note 9 pro lol)
Click to expand...
Click to collapse
I was on a custom ROM, as I said in my original post, so I won't point my finger to an automatic update. Maybe, maybe, some google-thing update? But I'm really sceptical that it would even be possible to hard brick a device in this way.
That's really weird, anyway.
Ps. Have you tried to open the phone and flash the fastboot + ROM in EDL mode?
I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.
fawziX said:
I have not tried it yet. Do u have some links or tutorials on how to do this? I just received the kit to open the phone. I thought at first it might be a battery problem since the phone doesn't seem to charge at all when I plug it in electricity.
Click to expand...
Click to collapse
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.
Gh_Racer said:
Here are some videos I followed. Do it at your own risk.
Phone Open + EDL Test Points *
Mi Flash Procedure in EDL Mode**
if the phone is not recognized as Qualcomm HS-USB QDLoader 9008, you need to install the drivers
This should work for both locked and unlocked bootloader devices, if I'm not wrong.
Here's another useful and complete guide.
This guide is not for the Redmi Note 6 Pro, so don't use the provided ROM and fastboot. Just follow the procedure, that it's the same for every Xiaomi phone.
* I don't know what kind of nails that guy has lol Keep in mind that you have to heat the phone up with an hair dryer in order to be able to work with the tools (the body is pretty tight).
In the video is not clear, but the phone has two slots: the first one is made for replacing the screen, and the second is made for taking apart the back cover. Pay attention to this (I didn't know this detail, and I took apart my screen during the first attempt).
** During the flash procedure, I get the error I mentioned in my original post. I'm not sure if it's related to having an un-authorized Mi account or whatsoever, I haven't found any clear confirmation about that.
Click to expand...
Click to collapse
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.
fawziX said:
Thank you for the infos! I'll try to do this when I have some free time in the coming days and I'll let you know if I have any success.
Click to expand...
Click to collapse
I hope you'll be able to do something. Please update me in that case! Good luck.
Gh_Racer said:
I hope you'll be able to do something. Please update me in that case! Good luck.
Click to expand...
Click to collapse
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)
fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
I need to search for them, since I downloaded things from a lot of different sources (I also deleted the one I downloade, since I did lost my hopes). I’ll update you in case I’ll be able to find them.
fawziX said:
Btw I also had the hello packet problem. But if u remove the usb cable from PC and then attach it again and refresh it dissapears but then after some time I have the weird xml error (resdump: <?xmlversion="1.0".........)
Click to expand...
Click to collapse
So, exactly, what did you do? You unplugged the cable and attached it again shortening the two test pins? Or you simply attached it without doing anything special?
I wasn’t able to solve the hello packet error.
I don’t know what the xml error is related to, since I couldn’t manage to communicate with the phone. I have no suggestions for this, I’m sorry.
Hi everyone...
Two days ago my Note 6 Pro woke up the same and after doing everything described above and even being able to successfully flash via EDL,
it remains the same and without changes.
I explain...
It turns on and stays in the MI logo, when trying to enter the recovery it stays in the TWRP home screen and only allows to enter the FASTBOOT that is unlocked but when trying to flash from MiFlash it gives an error as when I try directly from. bat file so I decided to try for EDL and it threw the xml error (resdump: <? xmlversion = "1.0" .........), I did some research and it turns out due to "prog_emmc_firehose_Sdm660_ddr.elf" and "prog_emmc_firehose_Sdm660_lite.elf" in "images folder" to firmware uncompress files, and I replaced them with others that allowed the flash to continue and finish successfully, but to my surprise, when restarting the device, everything continued without any change...
Until this moment I do not find any information that can help with this unfortunately.
I just hope that some of the "Great GURUS" in the forum can help and provide some solution... If it exists.
fawziX said:
Hello here I'm again. Maybe you can help me with one more thing. I'm trying to flash it but i get a weird xml error when trying.
Can u link to me the .elf files you used? The link in the video is broken. Thanks again!
Click to expand...
Click to collapse
Tenho o redmi note 6 pro bloqueado no modo edl gostaria de saber se alguém tem como ajudar
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I have the redmi note 6 pro locked in edl mode I wonder if anyone has how to help
Hi everyone, I’m sorry for having not replied yet.
As I wrote in my main post, I haven’t managed to recover my phone so far, so we decided to buy a brand new phone.
I hope you’ll be luckier than me.
Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck
Teddy Lo said:
Hi all, in order to flash your phone you will need authorized account normally, but if you try to flash stock firmware with Mi Flash tool and QFill you will face errors and errors.
What I recommend you is to re-flash full fastboot firmware the same version what you had on your phone or the latest stable fastboot firmware which you can get here:
Oreo Android 8 OEKMIXM
Pie Android 9 PEKMIXM
Latest version:
https://bigota.d.miui.com/V12.0.1.0.PEKMIXM/tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global_ac26982758.tgz
All versions:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Once you download firmware open it with 7-Zip archive tool, and again open firmware inside 7-Zip until you see normal folder with the name of firmware for example "tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global" and extract to desktop.
Once is Finish dowload this bypass auth files.
File with out Login
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now copy those two files:
prog_emmc_firehose_Sdm660_ddr.elf
prog_emmc_firehose_Sdm660_lite.elf
and replace those two files inside firmware that you extracted before on Desktop for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images"
Next step is to use correct MiFlash tool which you can download here:
Working Mi Flash Tool:
MiFlash20160401.zip | by firmwarefile.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Now, load firmware inside Mi Flash tool:
for example:
"C:\Users\YOUR_PC_USER_NAME\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global"
Next is to remove battery cover carefully because you can damage fingerprint flat cable!or use special edl cable if you don't wanna to open your device.
- Disconect battery
- short those test point pins
https://1.bp.blogspot.com/-C8bU7S6nAaI/Xqrd_PdvLXI/AAAAAAAAaLA/PK_E4oI_qPcJhBnSwlbQ0sr5J_9Ti2ycQCNcBGAsYHQ/s1600/21-14-47-images.jpg
-Plug the usb cable while you are holding those pins, once you got your device detected in Qdowloader 9008 mode relese short from test points.
Now click on Reflash on MiFlash tool and you will see your device is detected, now click on Flash and wait (it can take some time to finish). If you got error just unpplug the phone from PC and try again.
FOR FLASH OPTION:
You can check FLASH All or Flash all except storage
Once you successfully flashed your device, unplug device from your pc, plug battery back and power up your device to see if it's working or not.
The pay part if that doesn't work is reprograming or replacing emmc chip with ufi tool or something like that...
Good luck
Click to expand...
Click to collapse
I followed all the steps without any issues, since they were the same as I tried the last time, but a wanted to give a try to the files you linked me.
But... Unfortunately, I always get the same error. Probably, as you correctly pointed, that's an hw fault and there's nothing we can do.
I hope that someone will be luckier than me! I lost my hopes. RIP Redmi Note 6 Pro.
Related
Finally The wait is over
For all of you outside waiting for Global Firmware ROM... here it is:
I have tried it in a LEO-BX9 working flawless... last version received with chinese firmware by OTA was NXH19R
As previously done text is copied from giangishanghai as most are applicable. Thanks @giangishanghai for all the help and the patience :angel
- Make sure you have ADB activated on watch and all files needed on your pc (there are plenty of guides on xda so please search and read it if needed).
- Download 7z file from here : https://mega.nz/#!ozB12QrD
Decription Key
!U6_ZwGwPNUNj3P0PCfpsDtVoGpPG_x1csvR8I1ECOqU
-Edit: You will find 6 .img files:
bootloader, boot, cache, recovery, system, userdata.
-EDIT: In this link you will find whole Recovery software and images if needed:
https://mega.nz/#!YiZkjKyR
Decription Key
!vlUDAZz3mEJsSOpKYgbX5YaITUN59uL3YaVRSOtpVcU
-Edit: Before going to Bootloader, make sure ADB is working and your watch is recognized properly:
Run
Code:
adb devices
Result should be your Watch ID and the word "device" (unathorized or anything else will not work, when unathorized appears make sure to check your Watch for a prompt to authorize something, as it is in Chinese, choose the option with more characters - third one as I remember-)
-Boot the watch into bootloader mode
shut down the watch, press the power button and quickly press twice when the first vibration finished.
-Use the following commands one by one:
(DO NOT flash the bootloader.img)
IMPORTANT!!!: Make sure to run ALL commands below, from the ADB folder, where you have to previously copied all 6 *.IMG files, otherwise you will receive a lot of errors.
For Example if your ADB folder is in C:\adb, the command prompt should be in "C:\adb" so you make a DOS dir command and you see all 6 *.img files plus some ADB files
Then start with following commands one by one in exact order....
fastboot oem unlock (no needed if you already unlock your watch)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
DONE!!
EDIT: ****PLEASE READ IF YOU EXPERIENCE ANY TOUCH ISSUES******Thanks @mcdull
I were able to flash the rom without any issues. HOWEVER...
Originally I suggested NOT to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But I experienced inaccurate touch screen after applying the ROM. And then I finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will NOT change the model number. So the device model is determined by its hardware. And I can check the FCC of Leo-bx9 in official website, so there must be somewhere in the world selling this BX9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that Huawei can be told that you have tempered the bootloader if they dig deep. But I am prepared to give up the warranty for a Global Rom.
Click to expand...
Click to collapse
*****END OF EDIT******
After all this steps your watch reboot and the first thing you will see is a message in English, then you can choose the language you want.
Please don't forget to say thanks and also to @giangishanghai who was really really helpful on remote assistance and also @mcdull who was always promptly replying to help the community
Thank @dr_chch for your great contribution.
I were able to flash the rom without any issues. HOWEVER...
Originally I suggested NOT to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But I experienced inaccurate touch screen after applying the ROM. And then I finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will NOT change the model number. So the device model is determined by its hardware. And I can check the FCC of Leo-bx9 in official website, so there must be somewhere in the world selling this BX9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that Huawei can be told that you have tempered the bootloader if they dig deep. But I am prepared to give up the warranty for a Global Rom.
@dr_chch, grateful if you could include this in your tutorial. Thanks a lot for your contribution that making all these possible.
thank you. It was a pleasure for me to help.
sorry but I am trying to hit thanks button since two days ago with no result.... dunno why...
regards
mcdull said:
thank @dr_chch for your great contribution.
I were able to flash the rom without any issues. However...
Originally i suggested not to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But i experienced inaccurate touch screen after applying the rom. And then i finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will not change the model number. So the device model is determined by its hardware. And i can check the fcc of leo-bx9 in official website, so there must be somewhere in the world selling this bx9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that huawei can be told that you have tempered the bootloader if they dig deep. But i am prepared to give up the warranty for a global rom.
@dr_chch, grateful if you could include this in your tutorial. Thanks a lot for your contribution that making all these possible.
Click to expand...
Click to collapse
done updated thanks!!
Thx all you guys
Will try this out today
I have a LEO-BX9 currently running the Chinese ROM version. I've downloaded the new files. I will try this out later today and post my results as well.
A real huge thanks for getting the ROM and posting the steps. I've been following the forum for a month and it's impressive to see how you guys kept at it until you reached the finish line! Keep up the good work bro's! @giangishanghai and @dr_chch - You guys rock!
Edit: Works flawlessly! Just follow the instructions to the letter. Shiny new English ROM purring like a kitten!
Big thanks, I have the chinese LEO-BX9, works perfectly. the installation only takes less than 2-3 mins.
Will flashing bootloader and re-locking get Android Pay working?
mrgnarchr said:
Will flashing bootloader and re-locking get Android Pay working?
Click to expand...
Click to collapse
hello,
yes it should work.
regards
Hi guys
I flashed the below ROM on my BT version
Leo-L09S 2.1.7_Firmware_general_05014AHH from (Guide: How to flash english firmware to chinese huawei watch 2 sim card variant) on my BT version by mistake....
The watch does not boot at all.. No response when I press the power button cant go into fastboot or anything... its completely dead... Please let me know what can be done...
dr_chch said:
Finally The wait is over
For all of you outside waiting for Global Firmware ROM... here it is:
I have tried it in a LEO-BX9 working flawless... last version received with chinese firmware by OTA was NXH19……
Click to expand...
Click to collapse
Thx for all you do .May I know would you like 2 share a Chinese firmware?
Regards
Done updated,google fit is awesome.Thx dr_chch.
I'm trying to do this, but my Huawei Watch 2 is being recognized as a MTP device and wont appear under the device list when I type "abd devices". How do I fix this? Thanks.
---------- Post added at 02:44 PM ---------- Previous post was at 02:21 PM ----------
So, somehow I made it work. But I didn't do the commands properly and now the watch seems to be bricked. Is there any way I can bring it back into fastboot mode so I can flash the image correctly?
---------- Post added at 02:53 PM ---------- Previous post was at 02:44 PM ----------
Managed to get into fastboot and it seems to work fine. Thank you
What is the difference between this and stock?
devilsden said:
Hi guys
I flashed the below ROM on my BT version
Leo-L09S 2.1.7_Firmware_general_05014AHH from (Guide: How to flash english firmware to chinese huawei watch 2 sim card variant) on my BT version by mistake....
The watch does not boot at all.. No response when I press the power button cant go into fastboot or anything... its completely dead... Please let me know what can be done...
Click to expand...
Click to collapse
I have the same problem :crying: , anyone can help ?? thank so much
Black screen after flash bootloader
Hi Friends,
I tried the installed the first 6 file but it stuck at fastboot page, I restart several times but still not help.
After bootup it goes to fastboot mode.
then I tried to flash the bootloader to see whether it could help, but it turns to black screen.
totally no response , only a black screen, no vibrate holding the power button.
please help !!
thank you for any advice!
[Rom][NWD1.170711.002] Huawei Watch 2 BT LEO-B09 Chinese Fastboot [Factory Images]
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Yonghao Liu said:
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Click to expand...
Click to collapse
Hi, I flash your images, everything works normally expect notify. When notify appears on phone, there is no vibrate and no sound on wear, just notify card shown silently.
My wear had global version system, but Google Map gave a wrong location, so I try China version.
I use light flow to test notify. When I open option "silence phone while wearing watch", phone doesn't sound too but still vibrate. If I close this option, phone sound and vibrate. But watch always doesn't action.
Yonghao Liu said:
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Click to expand...
Click to collapse
Hi friend!I'm a Chinese Huawei Watch 2 User,do you have the LTE version Chinese Factory Image?I spend a lot of time to find it.But I falied.By the way,Are the LEO-B09S and the LEO-DLXX the same model?My device is LEO-DLXX,if I got a LEO-B09S Chinese Factory Image,can I flash it?
Thanks a lot!
CallMeEggLeader said:
Hi friend!I'm a Chinese Huawei Watch 2 User,do you have the LTE version Chinese Factory Image?I spend a lot of time to find it.But I falied.By the way,Are the LEO-B09S and the LEO-DLXX the same model?My device is LEO-DLXX,if I got a LEO-B09S Chinese Factory Image,can I flash it?
Thanks a lot!
Click to expand...
Click to collapse
I tried the international image on a LEO-DLXX, works fine, but without the SIM capabilities (4G, calls and etc), and during the boot there is a message about being using a different operating system. I suppose you'd get the same with the Chinese version.
Hi everybody,
Yesterday I was using my beloved(!) Vivo Nex S (Chinese 256GB version, no root, removed some bloatware some months ago, Nova launcher, rest original) in a normal way, put it away and wanted to use it again about 1 minute later again. When I tried to access the fingerprint reader, I recognized, that the fingerprint reader didn't get green when approaching my finger. After about 2 seconds of trying, my Nex made a reset.
I could only turn it on by pressing the power button for more than 10 seconds begining from there. Until then, I just see the Nex Logo, then the stars flying, then the Nex Logo again. It changes colors, again and again, and after about 2 minutes it shuts down and vibrates twice.
Starting the phone while pressing down the volume up button at the same time, brings me to the chinese Fastboot mode menu. I've the desicion between reboot (no other effect than described above) and Recovery. Chosing recovery, it shows the Vivo Logo again and after about 2 seconds "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH". After 30 seconds it shuts down. No access to the recovery menu!
I contacted the (Indian) chat from Vivo support. The Vivo support doesn't want to be responsible, because I bought my phone in China. Sending it back would probably mean, that I definitely lose my data and that it will take a long time until it's back.
So I tried to get access over USB. I can see "Qualcomm HS-USB Diagnostics 900E" [SIC, it's NOT 9008!] on COM7. I then tried to get access using ADB, where I'm really unfamiliar with. Didn't get any connection. So I tried QFIL, where I could see my phone in the top line of the program, but didn't get any access. (Neither I'm a pro there...)
So, now my biggest hope at the moment: Is there a possibility to get access to my phone using ASTool? I read about it, that it should be a great helper in such problems, and that there could be some hope, that I could even save my data by just flashing some "sectors" of the original system. But there's another problem: This software seems to be not freeware, and all the hacks around have trojans inside.
What do you think about it? Does anybody of you pros have a clue, how to get into the phone, flash a new boot there and how to save my data (about 220GB, desoldering of the memory is not (yet) an option)?
Thanks A LOT in advance to everyone!
Edimahler said:
Hi everybody,
Yesterday I was using my beloved(!) Vivo Nex S (Chinese 256GB version, no root, removed some bloatware some months ago, Nova launcher, rest original) in a normal way, put it away and wanted to use it again about 1 minute later again. When I tried to access the fingerprint reader, I recognized, that the fingerprint reader didn't get green when approaching my finger. After about 2 seconds of trying, my Nex made a reset.
I could only turn it on by pressing the power button for more than 10 seconds begining from there. Until then, I just see the Nex Logo, then the stars flying, then the Nex Logo again. It changes colors, again and again, and after about 2 minutes it shuts down and vibrates twice.
Starting the phone while pressing down the volume up button at the same time, brings me to the chinese Fastboot mode menu. I've the desicion between reboot (no other effect than described above) and Recovery. Chosing recovery, it shows the Vivo Logo again and after about 2 seconds "Your device is corrupt. It can't be trusted and will not boot. Visit this link on another device: g.co/ABH". After 30 seconds it shuts down. No access to the recovery menu!
I contacted the (Indian) chat from Vivo support. The Vivo support doesn't want to be responsible, because I bought my phone in China. Sending it back would probably mean, that I definitely lose my data and that it will take a long time until it's back.
So I tried to get access over USB. I can see "Qualcomm HS-USB Diagnostics 900E" [SIC, it's NOT 9008!] on COM7. I then tried to get access using ADB, where I'm really unfamiliar with. Didn't get any connection. So I tried QFIL, where I could see my phone in the top line of the program, but didn't get any access. (Neither I'm a pro there...)
So, now my biggest hope at the moment: Is there a possibility to get access to my phone using ASTool? I read about it, that it should be a great helper in such problems, and that there could be some hope, that I could even save my data by just flashing some "sectors" of the original system. But there's another problem: This software seems to be not freeware, and all the hacks around have trojans inside.
What do you think about it? Does anybody of you pros have a clue, how to get into the phone, flash a new boot there and how to save my data (about 220GB, desoldering of the memory is not (yet) an option)?
Thanks A LOT in advance to everyone!
Click to expand...
Click to collapse
That sucks. I don't have a solution but I'm curious as to what is taking up 220GB on your phone?
I suggest rescuing the phone first and forgetting about the data.
Twotems said:
That sucks. I don't have a solution but I'm curious as to what is taking up 220GB on your phone?
I suggest rescuing the phone first and forgetting about the data.
Click to expand...
Click to collapse
Well... As long as there is some free flash space, it will be used, right? There are especially 4K movies from our trip to Australia and from my construction works at home (I'm building a pretty special smart home), because the picture quality of the phone was much better than the one of the Lumix TZ81. Some of them luckily have been backuped already.
Well, I could also try to wipe the whole memory first, but I thought I could try to just flash the boot area and get back my data as well and then afterwards make a proper installation again.
But how to enter the phone now again? Any ideas? And should I try the global ROM then (would be my favourite) or just the Chinese again?
Thanks for any comments...
Edimahler said:
Well... As long as there is some free flash space, it will be used, right? There are especially 4K movies from our trip to Australia and from my construction works at home (I'm building a pretty special smart home), because the picture quality of the phone was much better than the one of the Lumix TZ81. Some of them luckily have been backuped already.
Well, I could also try to wipe the whole memory first, but I thought I could try to just flash the boot area and get back my data as well and then afterwards make a proper installation again.
But how to enter the phone now again? Any ideas? And should I try the global ROM then (would be my favourite) or just the Chinese again?
Thanks for any comments...
Click to expand...
Click to collapse
I can't help you unfortunately. But I know you can't flash the global rom to the Chinese version and vice versa.
The only alternative solution is find experience third-party service in your country.
Otherwise you must send it to China and local Vivo service point.
And always take backup your staff on phone to pc or external drive now you wouldn't have worry if you had taken backup.
No 1 rule owning any kind electronic devices is to have backup because you never know with electronics device they're always a chance for hardware failure.
You don't leave this thing to luck.
Sent from my iPad using Tapatalk
Yes, I read a lot about the global ROM on Chinese Vivo Nex in the according thread in the meantime. I'm even thinking in opening my phone and bridge the contacts to get into the 9008 mode forballvofbyou (and for me of course ) instead of sending it back to China. But I'm afraid that I wouldn't even recognize, if I was successful there...
And yes, of course I learned that a (recent) backup would have been nice...
Now, for the moment I plan to flash the chinese ROM first again, in order to maybe being able to savevsome of my data first. Is AFT the right way? There's some kind of a "hack" needed in order to use it, and this one seems to have a Trojan inside! Isvthere a "trojanfree" solution somewhere?
Best regards and thanks a lot for your replies!
Disable Windows defender and run the tool.
That's what I did myself when tried last summer flash global rom to Chinese version.
There's instructions and video tutorial here at Vivo Nex thread a member who upload about how to flash using AFTool
https://forum.xda-developers.com/nex/how-to/rom-vivo-nex-global-rom-1-7-18-service-t3831866/page2
Post 15.
But in order to flash Chinese rom you need having the full zip file and I don't know if there's a indipended source of downloaded.
Easy firmware site has only global rom but not Chinese one last time check.
And doubt Vivo support will provide you that file you'll need in order re flashing you existing Chinese rom version.
Sent from my iPad using Tapatalk
paatha13 said:
Disable Windows defender and run the tool.
Click to expand...
Click to collapse
Well, there's a Trojan in the authorisation tool in the version I got. Did you have to activate yours using this activation tool under your link, or is it usable without this activation as well?
paatha13 said:
But in order to flash Chinese rom you need having the full zip file and I don't know if there's a indipended source of downloaded.
Easy firmware site has only global rom but not Chinese one last time check.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I think, I would even need the Flashfile itself, as I'm not able to transfer the files from a ZIP-file into the internal memory anymore. And yes, you're right. Have been searching the Chinese ROM now for hours, but didn't find it anywhere... :crying:
Found the Chinese (official!) download of the ROM, just for those, who are interested:
http://sysupwrdl.vivo.com.cn/upgrad...es/PD1805_A_1.21.3-update-full_1541422501.zip
It's not even needed to have a stupid Baidu account (which is just registerable using a chinese phone number, which again is just possible to use a Russian phone number creater, which again is not so easy because most of the numbers are already bloked, which...). No, it's just a normal, direct download link!
And hey guys: This evening my Vivo Nex just started to be able to enter the Fastboot menu again!!! Why ever, but that's partial good news (for me at least).
And again for all of them, who want to have an English translation of the menu structure; Here it is !
- Reboot System
- Wipe Data
---- Clear Cache
---- Restore all settings
---- Clear all data
---- Return
- Install Update
---- Mobile phone storage
---- SD card
---- Return
- System repair mode
---- Enter system repair mode
--------- Restart
--------- Download latest version and installation (using WLAN)
--------- Shutdown
---- Cancel
- Power down
- Advanced options
---- Upgrade via USB
---- Upgrade Systems & 3rd party applications
--------- Mobile phone storage
--------- SD card
--------- Return
---- Verify system file integrity
---- Open ADB restart
---- View the upgrade log
---- Return
Some words, what I've seen on my soft bricked phone this evening:
- Wipe data -- Clear Cache: Tried this, but without any changes in behaviour
- Install Update -- Mobile phone storage: Didn't find any backup from Vivo in all the folders and subfolders on my phone. Even though, I could see the whole folder structure from my phone, so theoretically all the data are still there!
- Install Update -- SD card: Just trying this, as soon as the download of the Chinese ROM finished. Maybe with a dirty Flash I would be able to reboot?
BTW: IS THERE A WAY TO JUST FLASH SOME SINGLE FILES INSTEAD OF THE WHOLE ZIP FILE?
- System repair mode -- Download latest version and installation: A message pops up, that nearby WLANs are being searched. But after about 10 seconds it turns back to the previous menu, whithout any success.
- Advanced options -- Verify system file integrity: I get a pass here!!! Unbelievable... Don't know what's still hindering my phone to boot up just in a normal way...
- Advanced options -- Open ADB restart: Could this maybe help to enter the 9008 mode, which many of you out there are trying to reach? Don't understand this in detail, so please don't be mad about me, if this is a silly question...
Thanks for your patience with me, and hope, that some of the information could maybe also help someone of you out there...?
Edimahler said:
Well, there's a Trojan in the authorisation tool in the version I got. Did you have to activate yours using this activation tool under your link, or is it usable without this activation as well?
Click to expand...
Click to collapse
Use this and check for Trojan without extracking the zip file.
virustotal.com
Windows defender its not that trustable and it's full of **** many times when detect something that's not harmful actually.
Yes you need to activate via username and password given on instructions.
Sent from my iPad using Tapatalk
paatha13 said:
Yes you need to activate via username and password given on instructions.
Click to expand...
Click to collapse
Seems as I found an already patched version now, which also seems to be free of malware (at least on my PC, using the Windows defender):
https://mega.nz/#!zrohlSBL!5geOCXwSFHMPCACKjOqLNVF_V8t1jFvZc6FrZj63xOM
Next problem: Can I use AFTool (which is up now) to flash the Chinese ROM to my Vivo Nex again, without having the 9008 mode? And how to do it? Most videos showing solutions in the internet are about cracking the software and not how to use it afterwards...
Well, I tried to find the "fastboot_flash_all" file in my downloaded version of the firmware. But can't find it there (see below).
Because of this I tried using QFIL, but can't find the MBN file again... Boah, it's a really hard puzzle this time...
Unfortunately I can't help you further as my knowledge and only experience was when tried last summer to flash global to Chinese version but it failed and dropped any further examination and leave it as it is.
I haven't tried re flashing existing rom wearing Chinese version device using AFTOOL.
Vivo tools really sucks on those aspect and they're not helping either but just saying to anyone has problem visit Vivo official service.
All the info you can get here xda is the specific topic only provide you above.
Maybe you can try sent pm to member who gave all the information and idea of how using AFTOOL.
Sent from my iPad using Tapatalk
paatha13 said:
Unfortunately I can't help you further as my knowledge and only experience was when tried last summer to flash global to Chinese version but it failed and dropped any further examination and leave it as it is.
Click to expand...
Click to collapse
Dear paatha13, Thanks anyway for your support and your ideas! In the meantime I maybe "accidentially" unlocked the boatloader. Being desperate, I tried everything. Hope it didn't really happen or at least, that it won't have an influence on the warranty of the device... Yes, maybe it's just better to give up there and send it back for "Mainboard exchange", as they call it.
If you're still interested in trying to change to the global version (for me it's really in the background at the moment), maybe this "Unlocking-tool" could help you somehow. I posted the link in the according thread here:
https://forum.xda-developers.com/nex/how-to/guide-vivo-nex-s-apps-safe-to-uninstall-t3813308/page17#post79131637
(in Message #165)
paatha13 said:
Vivo tools really sucks on those aspect and they're not helping either but just saying to anyone has problem visit Vivo official service.
Click to expand...
Click to collapse
Completely agree, it really sucks, that they aren't interested in helping in an easy way by blocking everything.
Well, thanks again, hope I'll be able to help also once. Even if it's only in a "mental supporting" way.
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers. Rebooted and opened msm tool and Is connecting and now showing 2 ports. Hope this works for anyone having trouble ; as earlier I had no Qualcomm driver's installed and no ports showing on msm tool after many attempts to install drivers. I'm now ready when something comes along to flash. After rebooting PC use cmd window adb reboot edl. Will then show up on msm tool as connected. When installing Qualcomm driver's choose first option Wwan is not used to get Ip address. If this works for you hit the like button "it's free". I've seen many people complaining they can't connect to msm tool. This fixed my issues. Tested on windows 10 pro
Driver's. https://drive.google.com/file/d/1AOeuMj6D5f6H4yhAC1QKGN437qV9YmJs/view?usp=drivesdk
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
XNine said:
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
Click to expand...
Click to collapse
No additional driver's need to make Qualcomm devices/one plus phones to connect to msm tool.
illusiveairforce said:
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Click to expand...
Click to collapse
You don't use the factory one use the one above or below. It's a tool that relocks bootloader and flashes device to original firmware that it was shipped with. It's an anti-brick tool so to speak.
I still cant get it to work. the driver looks to be working and MSM identifying it
but no matter what i do it wont progress. i cant adb reboot because adnb nor fastboot are responsive. the phone just disconnectes and reconnects USB over and over and thats it. no button combo of volume keys and power being held for along time seems to work either.
I finally got it functional and now at "Image does not match" tried on 3 other machines with 3 seperate MSm installs.
9 5G LE2115 is my phone I bought directly form OnePlus. Idk what to do from here.
Usually kicks up that warning if your trying to use the wrong msm tool.?
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
applyscience said:
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
Click to expand...
Click to collapse
What about that global fastboot rom I linked you to?
mattie_49 said:
What about that global fastboot rom I linked you to?
Click to expand...
Click to collapse
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
applyscience said:
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
Click to expand...
Click to collapse
You were able to get back from aospa though right? Via msm
mattie_49 said:
You were able to get back from aospa though right? Via msm
Click to expand...
Click to collapse
i always had fastboot access during that, i just was too stupid to extract my own img files form the paylod dumps (theres so many guides online, i just suck with it) anyhow, after you hooked me up with download i just ran the the imgs in a flash-all bat file to clean up both slots of the phone and it was wonderful. as soon as i went to the unofficial lineage my phone just gave up. 2 reboots later.
im not sure what im going to do. its been a long day and not too pleased with myself so im trying to just procrastinate it till tmw or sunday.
[17784][07-04 07:23:08.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[17784][07-04 07:23:11.061]<4> [3] [SP][195] Check cmd done status failed. 1
this is the 2 lines in the log that have ruined my weekend.
I'm investigating possible solutions to common MSM errors that prevent flashing.
See the following thread and feel free to try the steps outlined if you're brave enough.
Please report back your findings.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
Can you re-up these? I'm getting a 404 on the google drive link.
Ethanadams642 said:
Can you re-up these? I'm getting a 404 on the google drive link.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
Hello i've flashed a custom ROM for my Redmi 9 this morning but it failed.
Now my phone doing a big f* bootloop, the recovery (TWRP) is dead and the fastboot too.
I've found a tool named SP Tool to repair the phone but the problem is when i plug my phone to my computer the phone is charging (logic) and instead showing the animation of the battery it bootloop until it runs out of battery.
So someone can help me please
Thanks
Edit: Oh i forgot, now i've realised than when i flashed the rom i've wiped the entire phone (internal storage too)
My bad...
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Hi, my phone has the codename Lancelot with a MTK Helio G80.
I will try, thanks
XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
Both SIM slots have no IMEI? I assume you wiped all and didn't backup?
You'll need Modem Meta and ENG ROM to fix that, you can get the ROM and the specific way to fix it from here.
If you're lost you'll find all the answers in the thread, but don't be afraid to ask there just don't ask an already asked question.
Here is a brief guide made by the same person to provide the ROM.
Goodluck.
LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
hey can i contract to you? i have a same problem too need some help
thank.
LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
can i contract to you? i have a same problem too need help
XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
I followed the guide in the video. But failing in the LibUSB Step. Mediathek device is not showing up. My Redmi 9 is hard bricked, just seeing a "redmi logo" bootloop. No matter if I try to boot normally, recovery or fastboot. Any Idea?
Kisle said:
I followed the guide in the video. But failing in the LibUSB Step. Mediathek device is not showing up. My Redmi 9 is hard bricked, just seeing a "redmi logo" bootloop. No matter if I try to boot normally, recovery or fastboot. Any Idea?
Click to expand...
Click to collapse
This tool installs the driver required to unbrick your device, if you can find your device specific driver to install on your PC then you can skip using this tool and install the driver manually.
If you can't find the driver, then try using a different cable when connecting the phone to the PC. Or a different port in the PC (Like the legacy 2.0 USB port in the motherboard).
The tool should first detect any device connected to install the driver it doesn't work the other way. If it still doesn't work then your only option is to find the driver manually. Or maybe you can find an updated version of the same tool or a similar tool.
XDHx86 said:
This tool installs the driver required to unbrick your device, if you can find your device specific driver to install on your PC then you can skip using this tool and install the driver manually.
If you can't find the driver, then try using a different cable when connecting the phone to the PC. Or a different port in the PC (Like the legacy 2.0 USB port in the motherboard).
The tool should first detect any device connected to install the driver it doesn't work the other way. If it still doesn't work then your only option is to find the driver manually. Or maybe you can find an updated version of the same tool or a similar tool.
Click to expand...
Click to collapse
Thanks for your help. Actually I got it working with a lot of try and error... not even sure which drivers worked at the end. Also I had to switch to a win 7 computer. On win 11 drivers just didnt work. But with MTK Bypass tool + SP flash Tool, I was able to flash the stock image and recover my briked phone!
Kisle said:
Thanks for your help. Actually I got it working with a lot of try and error... not even sure which drivers worked at the end. Also I had to switch to a win 7 computer. On win 11 drivers just didnt work. But with MTK Bypass tool + SP flash Tool, I was able to flash the stock image and recover my briked phone!
Click to expand...
Click to collapse
Glad it worked out in the end mate.
Might be a random guess but it could be because signature protection was enabled on the win 11 PC.
Don't brick your phone again!
LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
Hi can I contact you I also have the same problem and it's my only mobile thank you
DISC0DEVIL said:
Hi can I contact you I also have the same problem and it's my only mobile thank you
Click to expand...
Click to collapse
Hey, i can help you by sending videos that helped me to fix my problem but i've lost them.
Do you have a bootloader locked or unlocked? (here to know how)
If it's the 1st option, relax, you can modify easily
If it's the 2nd a little bit less
NB: i don't use really use this phone, just for developpment and some things than it can break the OS because it had some problems with apps and updates.
Have a great day and i hope than you have found a solution before my answer.
XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
I just made an account to tell all of you amazing people in this forum how much i truly appreciate your support:
YOU ALL ARE AWESOME!!!! I was legit going to loose my job if i didn't unbrick this darn Redmi 9 coz it's my boss's daughter's device
e putting the blame on me being the spoiled lil brat she is :/ so it was either this phone gets working or i get thrown onto the streets.
I soared through so many websites and articles that i had almost given up XD... until i landed here.
I love ya'll! keep up the good work!
LeCaptain said:
Hello i've flashed a custom ROM for my Redmi 9 this morning but it failed.
Now my phone doing a big f* bootloop, the recovery (TWRP) is dead and the fastboot too.
I've found a tool named SP Tool to repair the phone but the problem is when i plug my phone to my computer the phone is charging (logic) and instead showing the animation of the battery it bootloop until it runs out of battery.
So someone can help me please
Thanks
Edit: Oh i forgot, now i've realised than when i flashed the rom i've wiped the entire phone (internal storage too)
My bad...
Click to expand...
Click to collapse
please tell me you didnt reflash preloader
XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
Bro in my device when i Connect my mobile.. libusb not recognized my phone.. What should i do
optsiam said:
Bro in my device when i Connect my mobile.. libusb not recognized my phone.. What should i do
Click to expand...
Click to collapse
Is it in EDL mode?
No but I am gonna try it Tomorrow
Someone help me please? Two days ago i bricked my redmi 9 eea after update via ota. He just died, no infinite loop or charge. After a tutorial from here was able to revive him with sp flash, phyton and other stuffs. Everyting went OK and my phone is alive again. Whatever now I've getting issues that weren't there before hard brick. My redmi doesnt recognize my Sim card. I enter my pin security and then don't get any sim card signal. Also can't log on play store with my Google account, i get this message "there was a problem communicating with Google servers, try again later." Tried to wipe Google play services data, also from play store, formated redmi from recovery but the problems remains. Maybe i need to reinstall rom again, im pretty sure it was the right rom i flashed because i download it from miui official website. Unfortunately after reviving my redmi with sp flash, my bootloader got locked again. Sense i cant log with Google account because phone doesn't recognize my chip to activate data sim card, i cant either unlock with mi unlock. Is there any solution for this? Thanks.
Perhaps flashing phone with another rom the problem gets fixed. I can still flash my phone with sp flash even with bootloader blocked right? My redmi comes with a European rom. To revive him i used rom last update, maybe should try a previous version?
LeCaptain said:
It worked! Thanks
Click to expand...
Click to collapse
Are all the steps performed with the phone turned off and connected to the computer?
long story short i have a SM-a125u that i hard bricked in the process of trying to root , i think i flashed the wrong preloader or something but anyway i can get into brom mode and even as far as loading the firmware into sp flash tool and clicking start to flash but nothing happens when it starts , ive tried the auth bypass , ive trried every tool known to man, i have every file you could need for the phone , pit , scatter, preloader, entire firmware dump , everything if anyone knows what im doing wrong please let me know , id be happy with just getting download mode back to fix it
I think i might be having similar issues with my infinix mtk phone
the problem is similar, samsung a12, does not enter the modes, does not respond to charging, the computer sees it as an MTK port, but the program Odin does not see it, I don’t know what to do ..
By the way, the mtk_bypass_rev3 program understands it, when you press the start button, it does something, some green lines, but again, Odin does not see it ... is it possible to somehow install the stock firmware?
fackstrot said:
By the way, the mtk_bypass_rev3 program understands it, when you press the start button, it does something, some green lines, but again, Odin does not see it ... is it possible to somehow install the stock firmware?
Click to expand...
Click to collapse
I'll upload the files to fix it in a second but it will change your device to sm-a125w or at least it did to mine anyway which is a good thing because it allows OEM unlock if you want to root. It's just the Canadian version but it works fine on American networks ...will upload shortly
PrivyetCyka said:
I'll upload the files to fix it in a second but it will change your device to sm-a125w or at least it did to mine anyway which is a good thing because it allows OEM unlock if you want to root. It's just the Canadian version but it works fine on American networks ...will upload shortly
Click to expand...
Click to collapse
The main thing is to start the system, except for the files, can you please give instructions?)
fackstrot said:
The main thing is to start the system, except for the files, can you please give instructions
Click to expand...
Click to collapse
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com