Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Link: https://mega.nz/#!gqQATbga
Decryption key: !mD2smD4jEq_FOkhE1uy0PQ5uf6XYpxR0wxxkM6msPiE
Special thanks to @mcdull for preparing this file to all of us.
So after downloading the above files from dr_chch's post extract the files. After that we will need to get QPST which has the program called QFIL which we will be using to unbrick the watch.
Download “QPST 2.7 (QFIL)” from HERE and extract it to an empty folder. Install QPST by double clicking setup.exe.
Now you want to plug in your Huawei Watch 2 to the PC using the charging cable that came with the watch.
At first you might get a notification from the PC that the usb device is unknown, if that happens you will need to hold down on your watch's right top button for around 30 seconds. After that you should get a notification from your PC that a new device was plugged in and it will start to install a new driver. Once that's done you should have a "Qualcomm HS-USB QDLoader 9008" device show up in your device manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We won't be needing the storage device to show up so if it doesn't for you that's alright.
Next we will open QFIL from start menu, if it's not in the start menu you can locate it by going to Program Files\Qualcomm\bin\. You should see "Qualcomm HS-USB QDLoader 9008" written on the top, if it's not then click on the "SelectPort" button and then select "Qualcomm HS-USB QDLoader 9008". After that Insert all the necessary file needed by QFIL:
(1)The programmer will be prog_emmc_firehose.mbn;
(2)Use the rawprogram0.xml;
(3)Use the patch0.xml;
(4)Hit “Download” button.
If the process you did with QFIL finished successfully, the watch will boot again. If not then try to restart the program and repeat the same process again until you succeed.
At this point your watch is alive again but without a firmware so you will need to flash the correct ROM through fastboot.
For that you can check out the guide dr_chch made here:
https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-bt-leo-b09-leo-bx9-t3616779
Thanks for the files and the recovery guide. Please make sure you understand the below before your recovery.
1. You will probably lost the original MAC Address of your WIFI and Bluetooth. But at least the device will work with both functions, it will assign another MAC Address for you.
2. The recovery file includes only the boot loader, you still need to boot into fastboot (holding the device power button until you feel it vibrate. Then quickly release and press the power buttons) to flash the latest ROM downloaded from here.
Mod Edit
what you can help?
dr_chch said:
Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Am getting an error accessing the mega link.
Click to expand...
Click to collapse
kenmlax said:
dr_chch said:
Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Am getting an error accessing the mega link.
Click to expand...
Click to collapse
kenmlax said:
Was this solution ever shared cause ive been waiting for it for quite some time now... my huwei watch model is LEO-DLXX
Click to expand...
Click to collapse
You wont need this file as this is for de-bricking the BT version only.
And the mega link works just fine.
Click to expand...
Click to collapse
mcdull said:
kenmlax said:
You wont need this file as this is for de-bricking the BT version only.
And the mega link works just fine.
Click to expand...
Click to collapse
Is there a way to unbrick the 4g version of this watch. specifically the LEO-DLXX
Click to expand...
Click to collapse
kenmlax said:
mcdull said:
Is there a way to unbrick the 4g version of this watch. specifically the LEO-DLXX
Click to expand...
Click to collapse
If you noticed all the quote, reply, pm name... I have answered you MANY times.
Click to expand...
Click to collapse
Code:
Start Download
Program Path:C:\Leo\prog_emmc_firehose.mbn
COM Port number:7
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I'm getting this error. I tried multiple Desktop's and win7/10
Just learned of this thread......
I am wondering if anyone got the LEO-DLXX Watch 2 4G working again? Mine is recognized in QFIL as a qualcomm 9008, but that is as far as I can get. Has anyone been able to get the bootloader working with the files in this thread? I'm not sure what happened to mine, but it got bricked while installing the global ROM Huawei2_NXG46W_Global_4G. It is strange how it worked for so many people, but not mine. Any help or guidance is appreciated.
stephen1981 said:
I am wondering if anyone got the LEO-DLXX Watch 2 4G working again? Mine is recognized in QFIL as a qualcomm 9008, but that is as far as I can get. Has anyone been able to get the bootloader working with the files in this thread? I'm not sure what happened to mine, but it got bricked while installing the global ROM Huawei2_NXG46W_Global_4G. It is strange how it worked for so many people, but not mine. Any help or guidance is appreciated.
Click to expand...
Click to collapse
it worked for me
I tried many times now and still get the error message.
Also i've used all of the program build's
Is there anyone who can assist me in this process?
luciano1961 said:
it worked for me
Click to expand...
Click to collapse
The ROM worked for you or were you able to recover the boot loader? Has the LEO-L09S recovery found here: https://forum.xda-developers.com/watch-2/help/flashed-huawei-watch2-power-t3632341 worked for anyone?
basziee said:
I tried many times now and still get the error message.
Also i've used all of the program build's
Is there anyone who can assist me in this process?
Click to expand...
Click to collapse
Are you getting the sahara protocol error message as well? Are you trying to use QFIL to restore the bootloader on the LEO-DLXX watch?
Two strange things happened when flashing the ROM from this thread: https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-4g-l-09s-global-t3602205
First, it took a very long time for the device to show up with adb devices. There was a device there, but it wasn't listing every time I connected. As soon as I did, I went ahead but probably shouldn't have. Second, the fast boot process seemed to go along as normal (I have flashed a few ROMS, but never on a watch) until it came to the system. The system fast boot process took seconds....not longer than bootloader, boot, etc.... That is something I have not experienced before and thought it may have to do with a smaller system for android wear, but in fact it is not that small. After that, well it is bricked, but at least showing as a qualcomm disk.
I guess I have to wait until the recovery bootloader (firehose, rawprogram etc..) is leaked for the LEO-DLXX device. There is no possibility of returning the device or paying for service since it was bought in China and brought to Canada where it hasn't even been released yet.
stephen1981 said:
Are you getting the sahara protocol error message as well? Are you trying to use QFIL to restore the bootloader on the LEO-DLXX watch?
Click to expand...
Click to collapse
Yes everytime I tried to flash the .mbm file I get the sahara protocol error saying it is 0 bytes.
I also tried draining the battery fully and I switched between many desktop's
And still no luck
And quick question: my friend has the same watch. Can i do something with that to fix my own?
Has anyone successfully flashed the Huawei Watch 2 Pro (LEO-DLXXU)?
I'm keen to get my watch compatible with Play store apps rather than Huawei App Store, but I'd be keen to hear from someone who has been successful.
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Supercairos said:
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Click to expand...
Click to collapse
same here, i just wish someone would help us find the right files for the 4G version.
Same problem with my LEO-DLXX. I noticed that 1 of 3 files needed to flash has wrong name
rawprogram_unsparse.xml , nor rawprogram0.xml
Is there a problem with this?
Supercairos said:
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Click to expand...
Click to collapse
You mean Oreo?
hackintosh5 said:
You mean Oreo?
Click to expand...
Click to collapse
Nope he means P as in this
Related
Hello everybody!
My S7 is hard bricked after me restore it by Odin
I have tried in many ways but not sucess!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm happy when you care my threads.
Did you verified your Usb drivers, or tried a different port oj your computer? Try unistalling drivers completely and try again
atrix_noob said:
Did you verified your Usb drivers, or tried a different port oj your computer? Try unistalling drivers completely and try again
Click to expand...
Click to collapse
I tried, but it not work!
Hiep2409 said:
Hello everybody!
My S7 is hard bricked after me restore it by Odin
I have tried in many ways but not sucess!
I'm happy when you care my threads.
Click to expand...
Click to collapse
What files did you use to restore from odin? What version was you phone on and what versi9n was the firmware you flashed? Also where did you download it from? (Check for the obvious, like deleting drivers and installing the correct ones or just reinstalling them. Or just use a different computer) Let us know as much as you do, so we can help you out
Looks to me like you have A LOT of driver compatibility issues on your computer. I see some that have to do with HTC.. Do you have an HTC phone as well?
Try these steps:
1. In device Manager, double click on one of the devices with the exclamation mark
2. Click on the "Details" tab
3. Under the "Property" drop down, look for "Hardware Ids" and click on it
Highlight the first thing you see under "Value" right click on it and copy it.
Mine says: USB\VID_04E8&PID_6860&REV_0400
And it's for the SAMSUNG Mobile USB Composite Device
4. Try googling that value. You should find compatible drivers for it.
I'm attaching the USB drivers I'm using.
Hope this helps.
my question is why are you flashing your S7 with tools other than Odin? those tools are not meant to flash the S7
micallan_17 said:
my question is why are you flashing your S7 with tools other than Odin? those tools are not meant to flash the S7
Click to expand...
Click to collapse
As i can see you did not read the first post!
"My S7 is hard bricked after me restore it by Odin"
Basically this means: flash memory is not good for booting divice, so it stays in Qualcomm's Snapdragon USB serial bootloader/flash mode.
These are qualcomm tools.
Grow up!
PadsPCB said:
As i can see you did not read the first post!
"My S7 is hard bricked after me restore it by Odin"
Basically this means: flash memory is not good for booting divice, so it stays in Qualcomm's Snapdragon USB serial bootloader/flash mode.
These are qualcomm tools.
Grow up!
Click to expand...
Click to collapse
Without an unlocked bootloader, it's nearly impossible to brick our S7 unless you try super hard to do so. Instead of getting snappy with people here, giving us information would help.
Can you put the phone into download mode? (power off, hold vol down, home, power until a blue screen appears, then press vol up)
What exactly did you flash with Odin?
Was the flash interrupted? can you provide a log?
Whatever you did to your phone, YOU did it. So dont come here, ask for help, and then tell the people trying to help to "Grow up".
I am having the same issue, except I didn't do anything wrong with Odin, I was a just reflashing, and it broke. How can I fix this?
If you can link the xml files, i can try from my end
anyone fix this have the same issue with a s8 +
[email protected] said:
anyone fix this have the same issue with a s8 +
Click to expand...
Click to collapse
My recommendation is to go on the s8/s8+ forums, hopefully someone had the same issue and resolved it there...
unbrick hardbricked
hi,guys i'm new at this but i found this files on the web that works for me like a charm no configuration needed only double click on file recover.bat and buala.
https:// mega.nz/ #!UyQ11ZIA
Can i have the password for the file
PLZ
carlitossatan said:
hi,guys i'm new at this but i found this files on the web that works for me like a charm no configuration needed only double click on file recover.bat and buala.
https:// mega.nz/ #!UyQ11ZIA
Click to expand...
Click to collapse
decryption key PLEASE
I want this file, too
---------- Post added at 03:56 AM ---------- Previous post was at 03:50 AM ----------
My S7 edge has also become brick. Can you send repair methods and tool files to my Google mail? Thank you!([email protected])
Guys, OP posted 6 months ago and has not posted again since, unlikely they will post the file now
Im on it...
*Detection* said:
Guys, OP posted 6 months ago and has not posted again since, unlikely they will post the file now
Click to expand...
Click to collapse
Here File without password work only with old binary Like 4 But New Binary Not work I have G930V Bricked After Flash Downgrade Companion file From 8.0 I hope any one can share or make file with new binary
G930XU5
https://mega.nz/#!6NEz2I7Q!df-ITxjS0w7YZJmn1_dSoqil7KWgzYmuvLNss-qTePg
G935XU5
https://mega.nz/#!GIkh0DQD!mKb2vR6p6ivYKofhFXl9iT7DAkIg04qn-Nk32VuTHqk
g955u bit5
gonnaneedaburnheal said:
If you can link the xml files, i can try from my end
Click to expand...
Click to collapse
if you need g955u bit5 unbrick solution
whatsapp+2348067369016
I've got a Galaxy S5 that I purchased from someone earlier today and it worked well until I did some type of software update, it went well but then restarted and it's been messed up since. Now, whenever I boot up the phone it boots fine all the way too the Sprint Spark screen and it just hangs, and hangs and then restarts again, and goes through the same process. I've tried reflashing the device using Odin but I keep getting an error "SW REV CHECK FAIL" with some other stuff. I've tired to do so much, I tried resetting the device and the cache using the options. Please, can someone offer me some help. It's a 900P and it's a Sprint device. I just got back from a funeral a little bit ago so I'd love to get this thing working finally, I've been working on it all night.
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
tys0n said:
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
Click to expand...
Click to collapse
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
nulledbyme said:
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
Click to expand...
Click to collapse
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
nulledbyme said:
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
Click to expand...
Click to collapse
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
tys0n said:
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
Click to expand...
Click to collapse
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
nulledbyme said:
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
Click to expand...
Click to collapse
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
tys0n said:
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
Click to expand...
Click to collapse
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
nulledbyme said:
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
Click to expand...
Click to collapse
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
tys0n said:
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
Click to expand...
Click to collapse
I'll try that so, with those files I just put them all into Odin?
nulledbyme said:
I'll try that so, with those files I just put them all into Odin?
Click to expand...
Click to collapse
Yes exactly. This is what you'll find once it's unzipped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
tys0n said:
Yes exactly. This is what you'll find once it's unzipped.
View attachment 4098803
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
Click to expand...
Click to collapse
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
nulledbyme said:
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
Click to expand...
Click to collapse
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
tys0n said:
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
Click to expand...
Click to collapse
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
nulledbyme said:
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
Click to expand...
Click to collapse
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
tys0n said:
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
Click to expand...
Click to collapse
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
nulledbyme said:
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
Click to expand...
Click to collapse
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
tys0n said:
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
Click to expand...
Click to collapse
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
nulledbyme said:
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
Click to expand...
Click to collapse
That's awesome! Glad I could help.
I have downloaded the LTE full factory recovery firmware, I will be providing a package that will bring the watch and will not flash system, userdata, nvram (imei) and will require you to flash the global firmware afterward.
Recovery firmware:
Here
sorayahya said:
So after downloading the above files extract the files. After that, we will need to get QPST which has the program called QFIL which we will be used to unbrick the watch.
Download “QPST 2.7 (QFIL)” from HERE and extract it to an empty folder. Install QPST by double-clicking setup.exe.
Now you want to plug in your Huawei Watch 2 to the PC using the charging cable that came with the watch.
At first, you might get a notification from the PC that the USB device is unknown, if that happens you will need to hold down on your watch's right top button for around 30 seconds. After that, you should get a notification from your PC that a new device was plugged in and it will start to install a new driver. Once that's done you should have a "Qualcomm HS-USB QDLoader 9008" device show up in your device manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We won't be needing the storage device to show up so if it doesn't for you that's alright.
Next, we will open QFIL from the start menu, if it's not in the start menu you can locate it by going to Program Files\Qualcomm\bin\. You should see "Qualcomm HS-USB QDLoader 9008" written on the top if it's not then click on the "SelectPort" button and then select "Qualcomm HS-USB QDLoader 9008". After that Insert all the necessary file needed by QFIL:
(1)The programmer will be prog_emmc_firehose.mbn;
(2)Use the rawprogram_unsparse.xml;
(3)Use the patch0.xml;
(4)Hit “Download” button.
If the process you did with QFIL finished successfully, the watch will boot again. If not then try to restart the program and repeat the same process again until you succeed.
Click to expand...
Click to collapse
At this point, your watch is alive again but without a way to boot to android so you will need to flash the stock rom here
Mine just in case
Is the latest version of the firmware?
OWDE.180707.001.E1 ？
Cao Aobo said:
Is the latest version of the firmware?
OWDE.180707.001.E1 ？
Click to expand...
Click to collapse
No this is just 7.1.1 recovery firmware in case your watch is bricked, then from there you can flash whatever newer firmware you want
Today I restored my watch by this manual. Model LEO-DLXX (LTE). It is 100% works. Thanks again)
Now, can you help me find the latest firmware for flashing with adb/fastboot? I have only old version (android wear 2.0.) And I can't flash ROM from TWRP, it shows the file format has problem and fail to install.
My watch has been updated to the latest firmware. But I had a problem that I did not notice before. When I restored the watch, IMEI was erased. Now any SIM does not work. Please help me.
y-type said:
My watch has been updated to the latest firmware. But I had a problem that I did not notice before. When I restored the watch, IMEI was erased. Now any SIM does not work. Please help me.
Click to expand...
Click to collapse
I have revised the flash package so it doesn't flash the nvram partition and the system, cache, userdata partitions so you need to flash the global rom. I am sorry that your imei was lost, unless you have a backup you would need to get it flashed at a repair store.
I have the same watch as in some of these pics (LEO-DLXX), but am getting the same error of sahara protocol fail. The bootloader recovery link above brings me to Leo-B09S _Recovery. Should it be this folder or something like LTE LEO-L09S? When I load the files in QFIL, it looks a bit different. I don't have rawprogram0.xml, but a file called rawprogram_unsparse.xml. Any help is greatly appreciated. It looks like others have successfully recovered their bootloader on the exact same watch that I have.
stephen1981 said:
I have the same watch as in some of these pics (LEO-DLXX), but am getting the same error of sahara protocol fail. The bootloader recovery link above brings me to Leo-B09S _Recovery. Should it be this folder or something like LTE LEO-L09S? When I load the files in QFIL, it looks a bit different. I don't have rawprogram0.xml, but a file called rawprogram_unsparse.xml. Any help is greatly appreciated. It looks like others have successfully recovered their bootloader on the exact same watch that I have.
Click to expand...
Click to collapse
I reuploaded the file with the proper name, they were the right files just with the wrong zip/folder name and updated the instructions to say rawprogram_unsparse.xml
deadman96385 said:
I reuploaded the file with the proper name, they were the right files just with the wrong zip/folder name and updated the instructions to say rawprogram_unsparse.xml
Click to expand...
Click to collapse
Thanks for your help! I still get the same error over and over again, "Download fail: Sahara fail: QSaharaServer failrocess fail". How many attempts does it usually take?
stephen1981 said:
Thanks for your help! I still get the same error over and over again, "Download fail: Sahara fail: QSaharaServer failrocess fail". How many attempts does it usually take?
Click to expand...
Click to collapse
me also have same watch leo-dlxx and have same error please help.
stephen1981 said:
Thanks for your help! I still get the same error over and over again, "Download fail: Sahara fail: QSaharaServer failrocess fail". How many attempts does it usually take?
Click to expand...
Click to collapse
deadman96385 said:
No this is just 7.1.1 recovery firmware in case your watch is bricked, then from there you can flash whatever newer firmware you want
Click to expand...
Click to collapse
Hi @stephen1981 there is one missing file which is tz.mbn I got it from another recovery and it works fine I put the file in attachments just extract it to the main recovery folder and it will work now my watch started and connected to phone and now it is searching for update
abo3bdo said:
Hi @stephen1981 there is one missing file which is tz.mbn I got it from another recovery and it works fine I put the file in attachments just extract it to the main recovery folder and it will work now my watch started and connected to phone and now it is searching for update
Click to expand...
Click to collapse
Thank you so much! Everyone on XDA has been so helpful. I am glad to have the watch working again!
Now can any one please put a working link for a working stock orio rom for the LEO-DLXX model
---------- Post added at 04:30 AM ---------- Previous post was at 04:19 AM ----------
stephen1981 said:
Thank you so much! Everyone on XDA has been so helpful. I am glad to have the watch working again!
Click to expand...
Click to collapse
You are welcome my friend I'm happy for you too that you got your watch working again
Thanks to everyone who contributed to this thread! Finally my watch has been unbricked!
It's being recognized as BX09 instead of DLXX though, and my sim functionality appears to have disappeared. Still, this is better than being completely useless...
EDIT: Flashed the Sawshark ROM. It's back to DLXX now. IMEI is missing though. Still, it's not the end of the world.
I have hw2 chenesee version. I flashed it with eu firmware and its work fine till i make update (after update my wathes dont have sound). I tried to flash it one more time with eu firmware and now they stop on logo.
savteam said:
I have hw2 chenesee version. I flashed it with eu firmware and its work fine till i make update (after update my wathes dont have sound). I tried to flash it one more time with eu firmware and now they stop on logo.
Click to expand...
Click to collapse
Very interesting.
savteam said:
I have hw2 chenesee version. I flashed it with eu firmware and its work fine till i make update (after update my wathes dont have sound). I tried to flash it one more time with eu firmware and now they stop on logo.
Click to expand...
Click to collapse
please use this :
https://forum.xda-developers.com/showpost.php?p=77935791&postcount=646
and flash it to the watch only that 3 files and it will work again
use adb to reboot to fastboot and then flash the files in the zip file which you will download from the link.
---------- Post added at 11:40 PM ---------- Previous post was at 11:36 PM ----------
ilitirit said:
Thanks to everyone who contributed to this thread! Finally my watch has been unbricked!
It's being recognized as BX09 instead of DLXX though, and my sim functionality appears to have disappeared. Still, this is better than being completely useless...
EDIT: Flashed the Sawshark ROM. It's back to DLXX now. IMEI is missing though. Still, it's not the end of the world.
Click to expand...
Click to collapse
I have also same problem IMEI is 0 and also when connect the watch to PC it shows that the LEO-DLXX driver is missing and can not open its internal memory but still can communicate with the watch using adb
A WARNING: new users, don't flash this as it will erase your IMEI.
old users whose imeis have been erased, take the watch to a service center, along with the original box it came in, and ask them nicely to fix it.
There are several instructions for restoring IMEI. But for this we need to enable diag mode. Who knows how to do this? I've got ROOT. But
this instruction does not work https://www.youtube.com/watch?v=AiOcfvyQf-4 It only finds a new device, but not one com port.
Having had a long research after I bricked my lenovo p12 pro 12.6(the CN version) ,I thought I finally figured out what is happening when boot ROW firmware on my tablet and a method to bypass such region check. Here is detail procedure:
First of all ,you DO NOT need to return your bricked tablet back to the seller or manufactures, any of which costs time and patience.
1、Download the super partition image file Mod edit: Links removed ,and extract super.img from it using 7z x ... command.
2、You can choose to use my bash shell script (flash_stock_firmware.sh)or your manual instructions: to flash the stock firmware
Bash:
bash 'flash_stock_firmware.sh' 'PATH/TO/THE/STOCK/FIRMWARE/FOLDER'
,it takes about 5 minutes to end.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After it booted to framework ,the init process will play a bootanimation ,in my case it shows :
This is exactly what we should to remove.And now you could reboot the tablet into fastboot mode
Code:
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
In my case ,my tablet successfully launches the SetupWizard for registering device to google:
Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?
mardon85 said:
Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?
Click to expand...
Click to collapse
Edited
ZTE AXON 7 said:
otloader
2、fastboot boot rec/recovery.img(Here you should wait for about thirty seconds before initialization completed)
3、adb push systemrw_1.32_flashable.zip /sdcard
4、Go to Install->/sdcard/ and choo
Click to expand...
Click to collapse
ZTE AXON 7 said:
Edited
Click to expand...
Click to collapse
Thanks for this. Its the info I think a lot of us have been waiting for.
Did you find the following issues with your global ROM the same as the video below @ 27:14
That is some really good news, great work!
Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?
Thanks!
ZTE AXON 7 said:
h costs time and patience.
1、Download the super partition image file Mod edit: Link removed ,and extract super.img from it using 7z x ... command.
Click to expand...
Click to collapse
famaTV said:
Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?
Click to expand...
Click to collapse
Download link was updated
Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?
ZTE AXON 7 said:
Download link was updated
Click to expand...
Click to collapse
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.
ZTE AXON 7 said:
EXTRAC
Click to expand...
Click to collapse
mardon85 said:
Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?
Click to expand...
Click to collapse
So far so good, all works fine ,120hz refresh rate,precision 3 pencil ,precisicion keyboard,fast charging,etc...
There is a brand new ROM out today. Are you able to flash that now? Have you tried changing the region code via a hex editor?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
famaTV said:
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.
Click to expand...
Click to collapse
I updated to S212017 with this super image ,no problem:
ZTE AXON 7 said:
I updated to S212017 with this super image ,no problem:
View attachment 5506983
Click to expand...
Click to collapse
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.
mardon85 said:
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.
Click to expand...
Click to collapse
OTA,I changed the original ota update logic from aosp.
ZTE AXON 7 said:
OTA,I changed the original ota update logic from aosp.
Click to expand...
Click to collapse
Wow it seems you've cracked it even better than the Ali Express sellers. Most of the reports are that it can't OTA and the issue with the Settings search bar.
If mine ever clears Chinese customs (been stick there for 12days now) I'll get mine back and be able to play.
Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?
mardon85 said:
Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
View attachment 5507019
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
View attachment 5507027
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?
Click to expand...
Click to collapse
UPDATE... Fast boot commands do actually work. Even though it wont list devices commands like reboot work fine.
Did you have to unlock your bootloader for this? Have you kept widevine L1?
@ZTE AXON 7 you seem to be using Linux like me, mostly. I've used QFIL to flash the ROW ROMs but never did it from Linux. Do you have instructions on how to do that?
Oh wait, I reread your post. That script is for flashing the stock ROM, just like you said. Sorry about that.
Thank you for your work
I don't understand this very well. Do you have detailed operation steps?
yo
The problem that I keep running into is that I am unable to flash the india 9 pro because of a "Device not match image"
I am aware of the many threads on this topic and have read hundreds of threads looking for an answer for my problem. I was able to get my oneplus 9 2115 on lineageOS. I noticed that the phone was now recognized as a 2113 model. Without knowing what I was doing I tried flashing back to stock OxygenOS. In this process I managed to soft brick my phone. I continued to try fixing it and managed to loose adb and fastboot access as well. Now my phone is unresponsive apart from the sound my computer makes when i hold down the power and volume buttons.
Here is what Ive tried:
Many different Qualcomm drivers
Disabling windows signatures and booting into Test Mode
Different ports, cords, and computers
Including original cord and 2.0 cords
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every msm tool variant for the One Plus 9 including 9 pro variants (used with lite firehose and without)
Kept getting Device Not Match Image or Waiting for Device
I know these are only screenshots of the Indian Pro model, but results were the same
Ive been trying to unbrick this phone on and off for months now. I know there are many threads out there with this topic, but I have yet to find a fix.
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Follow directions and it will be fixed.
MrSteelX said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Follow directions and it will be fixed.
Click to expand...
Click to collapse
Hello, thank you for your response. Even with the two msm tools listed i am still getting the "Waiting for device" error after 18s. Do you know how to fix that?
ermbhen said:
yo
I am aware of the many threads on this topic and have read hundreds of threads looking for an answer for my problem. I was able to get my oneplus 9 2115 on lineageOS. I noticed that the phone was now recognized as a 2113 model. Without knowing what I was doing I tried flashing back to stock OxygenOS. In this process I managed to soft brick my phone. I continued to try fixing it and managed to loose adb and fastboot access as well. Now my phone is unresponsive apart from the sound my computer makes when i hold down the power and volume buttons.
Here is what Ive tried:
Many different Qualcomm drivers
Disabling windows signatures and booting into Test Mode
Different ports, cords, and computers
View attachment 5673295
Every msm tool variant for the One Plus 9 including 9 pro variants (used with lite firehose and without)
Kept getting Device Not Match Image or Waiting for Device
View attachment 5673297
View attachment 5673299
I know these are only screenshots of the Indian Pro model, but results were the same
Ive been trying to unbrick this phone on and off for months now. I know there are many threads out there with this topic, but I have yet to find a fix.
Click to expand...
Click to collapse
On the OnePlus 9 pro India you need to make sure "Use lite firehose" is checked and "sha256 check" is unchecked then you can use the thread that was given to you to get back to regular OnePlus 9 firmware
I am continuing to get a "Device not match image" with the India Pro Version
stez827 said:
On the OnePlus 9 pro India you need to make sure "Use lite firehose" is checked and "sha256 check" is unchecked then you can use the thread that was given to you to get back to regular OnePlus 9 firmware
Click to expand...
Click to collapse
ermbhen said:
I am continuing to get a "Device not match image" with the India Pro Version
View attachment 5673925
Click to expand...
Click to collapse
Where did you download that from
ermbhen said:
I am continuing to get a "Device not match image" with the India Pro Version
View attachment 5673925
Click to expand...
Click to collapse
Download it from here https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/India_LE15DA/R (11)/
Same result
Ive downloaded and tired most of the msm tools from onepluscommunityserver as well as some others ive found on forms
ermbhen said:
View attachment 5673929
Same result
Ive downloaded and tired most of the msm tools from onepluscommunityserver as well as some others ive found on forms
Click to expand...
Click to collapse
That is so weird I've never had this problem it's always worked for me and everyone else as far as I know
stez827 said:
That is so weird I've never had this problem it's always worked for me and everyone else as far as I know
Click to expand...
Click to collapse
This is the problem that ive spent months trying to figure out cant find anything online about it
Seems you bricked yours to the point the MSM can't tell what device it is. Time to send it to OnePlus.
EtherealRemnant said:
Seems you bricked yours to the point the MSM can't tell what device it is. Time to send it to OnePlus.
Click to expand...
Click to collapse
can this be done without warranty?
ermbhen said:
can this be done without warranty?
Click to expand...
Click to collapse
Yeah but they will likely charge you something for it. I would reach out to them and find out.
EtherealRemnant said:
Yeah but they will likely charge you something for it. I would reach out to them and find out.
Click to expand...
Click to collapse
Okay thank you for the info. Much appreciated
ermbhen said:
Hello, thank you for your response. Even with the two msm tools listed i am still getting the "Waiting for device" error after 18s. Do you know how to fix that?
View attachment 5673901
Click to expand...
Click to collapse
waiting for device means your device is not connected or is not detected by msm
ermbhen said:
Hello, thank you for your response. Even with the two msm tools listed i am still getting the "Waiting for device" error after 18s. Do you know how to fix that?
View attachment 5673901
Click to expand...
Click to collapse
this is actually the MSMtool that raised my OP9 from the dead. many thanks to the poser @EtherealRemnant for this. just use this.
follow the instructions like "uncheck Use Lite Firehose."
jmadiaga said:
waiting for device means your device is not connected or is not detected by msm
Click to expand...
Click to collapse
Considering that the drivers seem to be installed correctly and the fact that I’ve tried multiple different driver links, do you think it’s safe to say that there is nothing I can do?
jmadiaga said:
this is actually the MSMtool that raised my OP9 from the dead. many thanks to the poser @EtherealRemnant for this. just use this.
follow the instructions like "uncheck Use Lite Firehose."
Click to expand...
Click to collapse
Dude do you have any idea of what his actual problem is because for ethereal remnant's msm to work you first have to flash op9 pro India msm he can't even do that did you read the thread
use orignal cable of oneplus your error param has been solved !
stez827 said:
Dude do you have any idea of what his actual problem is because for ethereal remnant's msm to work you first have to flash op9 pro India msm he can't even do that did you read the thread
Click to expand...
Click to collapse
yes dude i know what i am talking about. have you experienced what the poser experienced? i've had the same experience. i said the modded MSMtool actually works. poser should try different options to get his phone connected and detected by the modded MSM tool. many options are given in different unbricking threads throught oneplus 9 forum and other fora such as OP8,OP8+, etc.
some solutions to device not connected or not being detected by MSM are like the one posted before this: use the original OP red cable. Or use a USB 2.0 port in your windows machine. among others. or try skittles first and blow into the USB port. pray to the OP god. or phoenix if we are talking about rising from the dead, or the sandman ****.
however, i think that as long as you can still press Vol + & - (EDL) then plug in the cable to the windows machine, and within 10 secs press start, the modded msm will work. (assuming that you have the correct qualcomm USB drivers installed in your windows machine.)
yeah dude, sometimes it's all about common sense, too.