First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment nvme.zip: got it from [url]https://t.me/huaweihax[/URL]
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
{
"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"
}
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. Cholera will see your phone, if everything went right. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
tomek5 said:
Hi, I followed your instructions, and unfortunately it did not work. I was able to revive the phone but only with the latest (STF-L09 8.0.0.385 (C432) - STF-L09C432E2R1P5B175 (9.0.1.175)) firmware, everything else is XLOADER error ... My problem now is that I use the IMEI can not fix. Do you know what I can do there? Thank you.
Click to expand...
Click to collapse
Did you tried the last steps with flashing a lower firmware version with fastboot? I think it also could work when you're on B385.
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
tomek5 said:
Item 8, which firmware "update.app recovery_ramdisk" B385 or B366?.
There is no recovery_ramdisk there are both recovery_ramdis.
Click to expand...
Click to collapse
You have to use B385. Recovery_ramdisk is equal to the partition named recovery_ramdis.
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
tomek5 said:
TWRP (stf-twrp-zxz-0.3.img) hangs on startup image.
Item 5. Should I flash everything (kernel, system, vendor and ramdisk) or just kernels?
Click to expand...
Click to collapse
Weird. Yes, you have to flash the four files.
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
tomek5 said:
I did everything that flashed the firmware (STF-L09C432B378 (8.0.0.378)). All without success, always the same, as soon as I flashe the kernel, the system, the manufacturer and the Ramdisk starts the phone to Honor picture and boots again into the Fastboot. TWRP will not work anymore.
fastboot flash kernel KERNEL.img
fastboot flash system SYSTEM.img
fastboot flash ramdisk RAMDISK.img
fastboot flash vendor VENDOR.img
Click to expand...
Click to collapse
Have you tried booting with volume up and power button pressed? If the blue screen comes up, you can stop pressing the power button. Did you already ones succeeded to get into TWRP?
yes, here I come to the erecovery.
tomek5 said:
yes, here I come to the erecovery.
Click to expand...
Click to collapse
You have to unplug your phone. It may not be charging when you try to get into TWRP.
OK, I did it, the IMEI is back. Did it without TWRP. After flashing the kernel, system, vendor and ramdisk I did a Factory Reset. Then HCU.
Thank you for your help!!!
Clarification
waterboy1602 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
View attachment 4766798: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
View attachment 4766797
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
View attachment 4766799
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot:
Code:
fastboot flash kernel kernel.img
It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting.
Code:
fastboot reboot
If it doesn’t boot, go back into fastboot. Flash TWRP:
Code:
fastboot flash recovery_ramdisk twrp.img
.
Go into TWRP by holding volume-up and power. Be sure your phone isn't charging, otherwise it will boot into erecovery. In TWRP you need to flash NVME.zip (you need to flash it 4 times, it's a security precaution). After flashing NVME.zip it should be possible to fastboot flash vendor and reboot correctly.
Check your security patch in settings/about. If it's lower then June, then you've done everything right. Before you use HCU, you need to flash the right recovery_ramdisk (recovery_ramdis) again. Extract it from update.app and flash it with fastboot. Reboot again and let now the magic begin with HCU.
Check in settings/about if you can see your IMEI. If so, then you can use Hisuite to go back to an official firmware.
Click to expand...
Click to collapse
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Trig18 said:
First of all sorry for my poor English. If you see any language errors, you may always tell them.
After a long road trying to fix my Honor after a bricked it with flashing wrong files with fastboot, I finally fixed it. Because it was so hard to find the right manual, I will write my method down.
This will work for any kind of brick. By example: black screen or reboot cycle. It will also work when you were on EMUI 9 or on a version with a security patch later then June.
Requisites
Access to the inside of your phone
DC-Phoenix + HCU license
ChimeraTool License
TWRP Files for your phone. I used this one.
Huawei Update Extractor
: got it from https://t.me/huaweihax
HUAWEI USB COM 1.0 driver installed
You can only install this driver with driver signature enforcement disabled. For this is Google your best friend.
Firmware files
You can find those on androidhost.ru. Be sure you download the right files. You need two files: one with a security patch later then June 2018, but with EMUI 8 and also a firmware that was released just before June. Unzip already the files you downloaded.
I used the versions B378C432 and B366C432 for the Honor 9 (STF-L09).
Fixing your phone
Go into test point mode. See the attached picture. You need to ground this point with some metal plate of the phone. For this you can use a paperclip. You need to press the power button while grounding the test point. You can see in Device Manager if you succeeded when you see HUAWEI USB COM 1.0
Start DC-Phoenix and go into the 'update OEMINFO' tab. There you need to select the right bootloader. For me it was the selected on in the picture. You can try as much if you want. This won't harm your phone. Unlock FRP and Update OEMINFO don't need to be checked. Press update and when you get the message with completed you can go to the next step.
Close DC-Phoenix and open ChimeraTool. If everything went right, shall Chimera see your phone. Now you need to go to the update firmware tab. Select there the update.app and update_xxx_hw_xxxx.app files from the firmware with the security patch later then June. Otherwise there will be errors while flashing the xloader partition. Now flash these.
Normally your phone reboots automatically. Check in the settings/about if you still have your IMEI. If its not 0000000000 your lucky, otherwise go to the next step.
Shutdown your phone and go into fastboot. You have to extract: kernel, system, vendor and ramdisk from update.app from the firmware with a security patch before June. Flash those files with fastboot: It's possible that you get an error while flashing vendor. We fix this later.
Try rebooting. If it doesn’t boot, go back into fastboot. Flash TWRP:
Just for clarification, am sorry if am being a dummy, Step 3: after closing DC phonix, do i use chimera tool for only checking the phone's visibility or I close it again and flash with DC phonix? Please help
Click to expand...
Click to collapse
You should use Chimera to flash the firmware.
Thanks
waterboy1602 said:
You should use Chimera to flash the firmware.
Click to expand...
Click to collapse
Thank you very much , my device is now fully operational on EMUI9 though I used Dc phonix to flash it in upgrade mode.
Thanks again ??
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
daemonserj said:
Hi, waterboy1602!
Are you sure that for HCU works only with security patches LOWER than June 2018 ?
I am trying to find out exactly this dates, and firmware to downgrade.
BTW. On 4pda admins wrotes that it is not possilbe to downgrade to no_gpu_turbo version.
Do you know something about it ?
Click to expand...
Click to collapse
Yes, after a lot of trial and error I found out that it only works with a firmware lower then June 2018. I know that most people say it's impossible to downgrade to no_gpu_turbo. I found this way to work with my phone. I've put a lot of time into it to find this way. I hope it will also work for you.
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
DydoserLolekDrago said:
Hi, such a question, what should I do if I short-circuited the wrong contacts and after flashing the phone is forever detected as a comport and will not turn
Click to expand...
Click to collapse
Honestly I have no idea. If the testpoints don't work anymore, I dont think you have a lot of options.
how exactly do i ground the testpoint?
i connect it with gnd? or just press it with the
paperclip?
can it break the phone?
Related
Hi,
I could really use a hand with this guys. I haven’t rooted anything for years and I'm really struggling with this one. Not sure if I'm being a massive idiot or not with this.
I have a Mediapad X2 702L and I want to get all of the latest Huawei updates.
Am I correct in assuming that if I tricked it into thinking it was a 703L then I would get the updates?
If so, how would I do this?
I have spent the last few hours trying to solve this question. I'm really not the type of person who asks for help in an era of Google and I'm sorry if I come across as a noob.
I have managed to unlock the bootloader but that's as far as I can get.
Every attempt to get TWRP flashed onto my 702 has failed. I've spent all day scouring different guides but they all seem to differ slightly from one-another or omit details that halt my progress.
I would be very grateful if someone could give me an idiot's guide (or point me to one) that I can follow step by step.
Thank you for your help.
phorenzik said:
Hi,
I could really use a hand with this guys. I haven’t rooted anything for years and I'm really struggling with this one. Not sure if I'm being a massive idiot or not with this.
I have a Mediapad X2 702L and I want to get all of the latest Huawei updates.
Am I correct in assuming that if I tricked it into thinking it was a 703L then I would get the updates?
If so, how would I do this?
I have spent the last few hours trying to solve this question. I'm really not the type of person who asks for help in an era of Google and I'm sorry if I come across as a noob.
I have managed to unlock the bootloader but that's as far as I can get.
Every attempt to get TWRP flashed onto my 702 has failed. I've spent all day scouring different guides but they all seem to differ slightly from one-another or omit details that halt my progress.
I would be very grateful if someone could give me an idiot's guide (or point me to one) that I can follow step by step.
Thank you for your help.
Click to expand...
Click to collapse
That's why I made this
http://forum.xda-developers.com/mediapad-x2/general/mediapad-x2-unlock-bootloader-root-guide-t3212325
From the input of several 702L users, If you are on Android 5.0 you have to flash this twrp instead. Then flash the new 5.1.1 recovery after you update to B109.
https://docviewer.yandex.com/?url=ya-disk-public%3A%2F%2FvI5Y3Obeku4qzIrtHfPviJPL3yhTpSABBi9V4fM0UpU%3D%3A%2FRecovery%2FTWRP%2FX2_TWRP_CN_kangvip.rar&name=X2_TWRP_CN_kangvip.rar&c=5654a1e6657e
You need to flash it in fastboot. The instructions for how to flash are all over these threads. Just use the search on the left.
Thanks. Your guide was the one I was using, mostly. I came unstuck during the TWRP bit. I can't find a good enough fastboot step by step guide. All the guides I've seen so far confuse me.
I'll attempt another go. Already managed to change the DPI to 300 so that has hugely improved things.
phorenzik said:
Thanks. Your guide was the one I was using, mostly. I came unstuck during the TWRP bit. I can't find a good enough fastboot step by step guide. All the guides I've seen so far confuse me.
I'll attempt another go. Already managed to change the DPI to 300 so that has hugely improved things.
Click to expand...
Click to collapse
Download this and unzip it on your PC:
https://docviewer.yandex.com/?url=ya-disk-public%3A%2F%2FvI5Y3Obeku4qzIrtHfPviJPL3yhTpSABBi9V4fM0UpU%3D%3A%2Fadb%2Bfastboot%2Fplatform-tools.zip&name=platform-tools.zip&c=5654bd2be042
Download the twrp (second one in my guide) and put the file in the same folder. Then turn off your phone. Plug in the USB cable into the computer. Hold in volume down and power and then you should be in bootloader mode. Then on your PC, right click while holding in shift on the folder with the android tools and twrp in it and. choose open command prompt here. Then type in fastboot flash recovery twrp_cn.img
To fastboot flash something, simply put the img file you want to flash in with the Android platform tools folder and open a command prompt to that folder and type in fastboot flash and whatever the file you want to flash is. So if you wanted to flash a stock system you would type in fastboot flash system system.img. There are only 5 things you can flash with the x2. These are the things and the commands.
fastboot flash system system.img
fastboot flash cust cust.img
fasttboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash cache cache.img
Fastboot flash recovery recovery.img
If you fastboot flashed those you'd be back to a stock ROM (whichever stock one you downloaded)
You only have to fastboot flash recovery recovery twrp_cn.img though. Then flash one of my KangVIP ROMS and you'll be on b109 and pretty much up to date.
Thank you. I really appreciate the time you took to help.
I've tried to flash TWRP but this happens.
{
"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"
}
Any ideas?
EDIT: Oooooooh, might have figured it out, will update soon.
Right then.
Finally rooted.
The problem was with the boot-lock. Despite it stating it was unlocked, it doesn't appear that it was. I re-applied the unlock code and everything has been smooth sailing from there.
Couldn't get the English theme to work on TWRP though. Had to do it in Chinese.
I'll probably post again when I balls up the flash procedure
phorenzik said:
Right then.
Finally rooted.
The problem was with the boot-lock. Despite it stating it was unlocked, it doesn't appear that it was. I re-applied the unlock code and everything has been smooth sailing from there.
Couldn't get the English theme to work on TWRP though. Had to do it in Chinese.
I'll probably post again when I balls up the flash procedure
Click to expand...
Click to collapse
Make a folder on your internal storage called TWRP (if there is already one just leave it)
Make another folder in the TWRP folder called theme (caps matter so make sure the theme is all small letters)
Make sure the TWRP file says ui.zip put the ui.zip in the theme folder (again, caps matter, it should be all small letters)
When you boot TWRP it will be in English
That's exactly what I have done but TWRP is in Chinese. Could it have something to do with Windows messing with the theme when I rename it as a .zip?
I've tried extracting the files and renaming the extracted folder to ui.zip and I've tried renaming the untouched downloaded theme file to ui.zip but neither works.
EDIT: Done it.
I was literally typing ui.zip for the rename but I just renamed it to ui (without the .zip extension) and it worked.
phorenzik said:
That's exactly what I have done but TWRP is in Chinese. Could it have something to do with Windows messing with the theme when I rename it as a .zip?
I've tried extracting the files and renaming the extracted folder to ui.zip and I've tried renaming the untouched downloaded theme file to ui.zip but neither works.
EDIT: Done it.
I was literally typing ui.zip for the rename but I just renamed it to ui (without the .zip extension) and it worked.
Click to expand...
Click to collapse
If you want to enjoy 703's B110 ROM on your 702L you may go to:
http://forum.xda-developers.com/mediapad-x2/development/rom-stock-b106-gapps-t3230585
Thanks. I tried to flash your B109 rom last night but it got stuck in a boot loop.
I got it back to B015_KangVIP
I have a 702L but it is showing as a 703L in the system settings due to it running the KangVIP
Do I need to boot the 702L or 703L B110 rom?
Will the system settings show all the correct info after flashing?
Sorry for all the questions.
phorenzik said:
Thanks. I tried to flash your B109 rom last night but it got stuck in a boot loop.
I got it back to B015_KangVIP
Can I just TWRP your new B110 Rooted Debloated With GAPPS GEM-703L directly onto my phone, or would I need to something before this step?
Sorry for all the questions.
Click to expand...
Click to collapse
You need to be AT LEAST on B106 before you can flash anything higher eg. B109 or B110 because B015 is EMUI 3.0 with Android 5.0.5 whereas B106 onwards is EMUI 3.1 with Android 5.1.1 - major differences
Since you're on B015_KangVIP you're almost there. Follow guide below by "eenap" to reach B106 with TWRP 5.1.1 first
http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915
After you reach B106 with twrp 5.1.1 then you can head to the below URL for custom B109 or B110 and preserve your 702L's Dual SIM selection:
http://forum.xda-developers.com/mediapad-x2/development/rom-stock-b106-gapps-t3230585
kpcheang2 said:
You need to be AT LEAST on B106 before you can flash anything higher eg. B109 or B110 because B015 is EMUI 3.0 with Android 5.0.5 whereas B106 onwards is EMUI 3.1 with Android 5.1.1 - major differences
Since you're on B015_KangVIP you're almost there. Follow guide below by "eenap" to reach B106 with TWRP 5.1.1 first
http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915
Click to expand...
Click to collapse
This is where I come unstuck. I've tried to follow that guide and failed many times. I just don't get it.
Ever since I have been on KangVIP b015 rom, I can't get my PC to see the phone, so any flashing via adb cmd prompt won't work.
The PC just sees the SD card of the device because it thinks it's a memory card. It won't connect in HiSuite either.
phorenzik said:
This is where I come unstuck. I've tried to follow that guide and failed many times. I just don't get it.
Ever since I have been on KangVIP b015 rom, I can't get my PC to see the phone, so any flashing via adb cmd prompt won't work.
The PC just sees the SD card of the device because it thinks it's a memory card. It won't connect in HiSuite either.
Click to expand...
Click to collapse
You don't need ADB to work to flash the IMGs. Just go into bootloader (assuming your X2 is unlocked) then you can individually flash the 4 IMGs from the B106.
From B015 to B106 (after flashing and reboot) you need to reset/erase to get the B106 to properly work after setup
---------- Post added at 05:34 PM ---------- Previous post was at 05:18 PM ----------
I had the same issue before like you but once I managed to get the B106 working my ADB connection started working again
Why the hell can't I get this to work?
What am I missing?
Here's where I'm at:
1. Got the stock 703L ROM
2. Extracted the files this guide told me to via the Huawei extractor tool
3. Booted my device into fastboot
fastboot flash boot BOOT.img (successful)
fastboot flash cust CUST.img (successful)
fastboot flash recovery RECOVERY.img (successful)
fastboot flash system SYSTEM.img (ERROR CANNOT LOAD SYSTEM.IMG)
Needless to say, phone is now boot looping.
I can get into fastboot so what do I need to do to fix this?
Really getting frustrated by this now. I'll happily pay someone for a step by step guide that can fix this and get me running.
Thank you
EDIT. Out of sheer frustration, I kept at it, doing exactly the same thing and after about the 4th attempt, the system.img was flashed. No idea why it wouldn't work the previous times as I did nothing different.
Now it's booting up to the language selection screen and then rebooting in a loop. SIGH!
phorenzik said:
Why the hell can't I get this to work?
What am I missing?
Here's where I'm at:
1. Got the stock 703L ROM
2. Extracted the files this guide told me to via the Huawei extractor tool
3. Booted my device into fastboot
fastboot flash boot BOOT.img (successful)
fastboot flash cust CUST.img (successful)
fastboot flash recovery RECOVERY.img (successful)
fastboot flash system SYSTEM.img (ERROR CANNOT LOAD SYSTEM.IMG)
Needless to say, phone is now boot looping.
I can get into fastboot so what do I need to do to fix this?
Really getting frustrated by this now. I'll happily pay someone for a step by step guide that can fix this and get me running.
Thank you
EDIT. Out of sheer frustration, I kept at it, doing exactly the same thing and after about the 4th attempt, the system.img was flashed. No idea why it wouldn't work the previous times as I did nothing different.
Now it's booting up to the language selection screen and then rebooting in a loop. SIGH!
Click to expand...
Click to collapse
Do ensure you have the same ADB version as stated in the guide. (v1.42)
Rightfully you should be able to flash the system.img with no errors but usually the ADB drivers can cause issues if they were the incorrect ones.
Try this, instead of 4 you flash 6 IMGs extracted from the stock B015. You need to ensure you extracted them properly using the Huawei Extractor Tool. Each time you extract there is a corresponding header file which can be ignored because we only need the .img file.
1) boot.img
2) cache.img
3) cust.img
4) recovery.img
5) userdata.img
6) system.img
Then reboot. You need to get to B015 stock in order to go to B106.
Thanks.
Done that. I'm now on B015.
Currently doing OTA to B106
I've lost root access somehow, will that make a difference to anything?
phorenzik said:
Thanks.
Done that. I'm now on B015.
Currently doing OTA to B106
I've lost root access somehow, will that make a difference to anything?
Click to expand...
Click to collapse
Good you're making progress. Losing root now won't affect.
Once you reached B106 you can flash the B110 with root and Gapps to regain root.
Update to B106 failed.
Pretty much ready to throw the phone against the wall now.
phorenzik said:
Update to B106 failed.
Pretty much ready to throw the phone against the wall now.
Click to expand...
Click to collapse
Actually yes it is expected to fail because yours is a 702L - I had the same failure but this "failed" step is neccesary to do a bridge partial jump to B106.
Now go to bootloader and flash the same 6 IMGs from B106 ROM.
After that reboot and do initial setup.
Then do Settings--->Reset erase and reboot clean B106.
Finally flash twrp_5.1.1 so that you will have custom recovery in order to flash those custom B110 rooted plus Gapps plus Dual Sim.
"warning this will wipe your data"
"warning make sure that the tablet matches the firmware TB_X605F_USR_S200065_1905280020_Q00332_ROW
1. download adb setup https://forum.xda-developers.com/showthread.php?t=2588979
and install it
2. download the TB-X605F firmware http://www.mediafire.com/file/1uo5eu6iuzx39cd/TB_X605F_USR_S200065_1905280020_Q00332_ROW.zip/file
3. on the tablet go to settings and enable developer options
4. enable oem unlock and usb debugging
5. plug the tablet into the computer with usb cable and check the box on the tablet that allows usb debugging
6. reboot into fastboot using "adb reboot bootloader"
7. once fastboot has loaded type "fastboot oem unlock-go" to unlock the bootloader
8. then on computer extract the zip file and look for boot image "boot.img"
"make sure you have usb debugging enabled in developer options"
9. once your tablet is set up, on the android system prompt click "Charging this device via usb"
then click "Media device MTP" to access tablet storage on computer
10. download the magisk.apk file http://www.mediafire.com/file/vinf7xswbir90yi/magisk.apk/file
11. once downloaded drag the "boot.img" in firmware folder to internal storage
12. open command prompt and type adb install "the directory of the magisk apk file"
13. once magisk is installed launch the app and go to install / install / Select and Patch a File and look for the location of the boot.img
14. magisk will patch the boot image and put it in the download directory
15. go into download directory and you will see magisk_patched.img
16. on computer drag the magisk_patched.img on tablet storage to the directory where you want it to be
17. open cmd on computer type adb reboot bootloader
18. type fastboot flash boot "the directory of the magisk_patched.img"
19. once flashed type fastboot reboot
20. once booted go into magisk if it asks to update manager then update it, once the updated magisk manager is installed go to install / install / Direct Install to update root
Hi,
great job!
Do you know if it is possible to flash a recovery?
Thanks
Bootloop when trying magisk root
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
What error did LMSA give you? The vol-up + USB-in combo is really touchy. Maybe give it a few more tries with LMSA.
Someone else had probs like this, but was able to boot into recovery using Pwr+VolUp+VolDown combo. If that works, see if you can factory reset.
justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
Did you try power+vol up+vol down, 10 seconds long? It reinitialize the tab.
Good luck, neighbour
Hello,
thanks a lot for you help, LMSA stuck a 67% with error "fail to rescue".
The good solution was from my french neighbour with "power+vol up+vol down" for more than 10s. I then got acces to recovery and go to fasboot mode to flash original boot.img.
I've been then able to use LMSA to rescue my TAB and it's back to life !
I just wonder why magisk's boot generated was wrong... I'll make some other try in the weekend to root my tab.
Thanks a lot.
Merci du Var !
justalone said:
Thanks a lot.
Merci du Var !
Click to expand...
Click to collapse
De rien / you're welcome.
I had the same issue at 67% with LSMA.
Before I rooted the Tab, I upgraded it to Android 9 in Settings/System. Then everything worked fine.
I hope your house is safe despite this crazy rain.
This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.
KrazyKlutt said:
This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.
Click to expand...
Click to collapse
There's a magisk_patched.img for that build over on this thread.
Yahoo Mike said:
There's a magisk_patched.img for that build over on this thread.
Click to expand...
Click to collapse
Thanks a million Mike! You’re the best ?
XDA can be a jungle sometimes, I though I did research but I missed both the root thread and the TWRP thread for 605F.
That would have saved my lots of time a headache haha , but I didn’t get a heart attack so it’s all good.
Anyway, the patched Magisk worked perfectly, and all is good , finally a working YouTube Vanced since my previous Xperia 2 tablet.
The only weird thing was the link issue from Lenovo’s recovery for the latest firmware, the full one, not the ota updates.
???
twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix, which i was trying to look for an official tree, but i mean we already have one and when you compile it, it produced a faulty recovery image and lenovo hasn't released a kernel source or device tree yet, but i hope i can get a fully working one
turboperson123 said:
twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix...
Click to expand...
Click to collapse
Try this TWRP for X605F. I've been using the "update" function with no problems.
turboperson123 said:
... lenovo hasn't released a kernel source or device tree yet...
Click to expand...
Click to collapse
Have a look at this post.
There are so many hardware variants of the M10 now, it's probably impossible for Lenovo to release reliable kernel source. There's now even an M10 that uses SDM429 (rather than SDM450). ...and the second gen M10 FHD Plus (X606F) will use the MediaTek Helio P22T.
hello i have a problem i do the adb install command but it say "Missing APK file" plz help me
I can not find a way to avoid errors in the flash process, I attach some images.
{
"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"
}
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
AngelLestat said:
I can not find a way to avoid errors in the flash process, I attach some images.
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
Click to expand...
Click to collapse
Flash EMUI8 and immediately wipe system and extract and flash https://github.com/phhusson/treble_...v300.l/system-roar-arm64-aonly-vanilla.img.xz (this is the compressed form extract using 7zip)
so that you flash system-roar-arm64-aonly-vanilla.img. into system partition.
AngelLestat said:
I can not find a way to avoid errors in the flash process, I attach some images.
a bit of context and history of the things I did:
This is an Honor 8 FRD-AL00 from China, in 2017 I unlocked the bootloader, I rebrand the phone into its Europe version FRD-AL09, then I updated to Emu5, then in my first vacation on Europe (I am from Argentina), the phone ask me for an update. As I knew that I used an Europe ROM, full rebrand, I did not saw nothing nothing wrong with that (if I wanted an update on Argentina, I have to forced with the hisuite), so I accept the official update there.
Results: the phone was bricked.
I buy a new phone there, I kinda forget over some years, now I want to fix it, but seem that it is quite hard, I dont think this is a soft brick.
First I had problems installing TWRP, the only way was using the Multi-Tool8 from @teammT flashing the TWRP 3.1.1 as Erecovery.
If i try to update the twrp to 3.4 from the same twrp or using fastboot, I cant.
I tried to flash a ROM from a similar year than my last correct update, fail using commands, fail using the tool, fail using an extra SD on dload, fail using TWRP.
I tried the same thing with the stock firmware for FRD-AL09 (the multi-tool8 always recognize the phone as FRD-AL09, but I have errors when is flasshing.
The only firmware that I can flash without errors, is one from C185 (mid east latin america), which is the most downloaded firmware in huawei, with emui8 and android 8, but I dont have the cust.img in that update, the bootloop continue.
I tried with a different latin versionbut the flash does not work.
I tried with a custom rom (lineage for honor8), the instalation process seem ok, until I receive the same errors at the end (it can not mount vendor, cust, etc).
I tried to format system, cust, or the partitions that I receive errors, changing first to fat or anyone else, then apply again ext4, but nothing happen, the error persist.
I even had a backup made with TWRP when the phone was working fine, I tried to restore that backup with TWRP and I receive error.
I tried to do all these test using a linux with fastboot (in case I was having issues with some drivers), but I receive the same errors.
Still not sure how to choose the right firmaware, I already tried with 10 already.... most fullota firmwares does not have all the files that I need to unbrick.
I already tried with android 6, 7 y 8, from c432, c185, and one more.
I tried by dload (update), by the 3 zips in twrp, by img from twrp or fastboot, or using the multi tool.
Today I will keep trying to update twrp from 3.1.1 to 3.4, (maybe that would help me to install android 8 roms?) Where I can find the extra cust.img?
I really need to repair this phone, I dont care if it is with an official or custom firmaware, I know that all this seem hard to solve, but I would appreciate at least a clue that would help me to save this phone.
Click to expand...
Click to collapse
I think that the error 255 might be a bad download
-------------------------------------------
PLEASE TRY THIS SOLUTION
I think that the solution to fix this device is "Hurupdater" you just have to rename the 3 firmware files and flash the hurupdater in the same folder using twrp. It should flash the firmware file and also it keeps the bootloader unlocks. it works on honor 8. Hurupdater is also a better way to flash updates.
[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery
Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta. HuRUpdater Huawei Recovery Updater Flash official firmware zip files Can...
forum.xda-developers.com
--------------------------------------------
But if hurupdater method does not work (Im sure Hurupdater would actually work though)
1. Restart device
2. When your on the "Your device has been unlocked and can't be trusted" quickly hold volume button (make sure you are doing it fast enough), it should boot into a stock recovery look alike screen.
3. Now click button that says about downloading latest firmware. Pick your wifi. DONE
Beware that this will relock the bootloader and also put your device on android oreo (EMUI 8)
CHECK_123 said:
I think that the error 255 might be a bad download
-------------------------------------------
PLEASE TRY THIS SOLUTION
I think that the solution to fix this device is "Hurupdater" you just have to rename the 3 firmware files and flash the hurupdater in the same folder using twrp. It should flash the firmware file and also it keeps the bootloader unlocks. it works on honor 8. Hurupdater is also a better way to flash updates.
[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery
Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta. HuRUpdater Huawei Recovery Updater Flash official firmware zip files Can...
forum.xda-developers.com
--------------------------------------------
But if hurupdater method does not work (Im sure Hurupdater would actually work though)
1. Restart device
2. When your on the "Your device has been unlocked and can't be trusted" quickly hold volume button (make sure you are doing it fast enough), it should boot into a stock recovery look alike screen.
3. Now click button that says about downloading latest firmware. Pick your wifi. DONE
Beware that this will relock the bootloader and also put your device on android oreo (EMUI 8)
Click to expand...
Click to collapse
Nice but once hurupdater does not work and need to relock bootloader, the bootloader can be difficult to unlock again.
jjgvv said:
Nice but once hurupdater does not work and need to relock bootloader, the bootloader can be difficult to unlock again.
Click to expand...
Click to collapse
I think you can try the "Your device has been unlocked and can't be trusted" trick and from what i posted then clicking download latest firmware. But it would relock bootloader and put it into EMUI 8. Unlocking the bootloader is also easy anyways, once you get the bootloader code, you can write it down or put it in notepad to always have the bootloader unlock code.
The Honor 8 also has 2 recoveries, one from holding vol up from "Your device has been unlocked and can't be trusted" and also the normal recovery partition where you usually put twrp in (vol up + power button)
You can also use hurupdater to go from android 8 to android 7. The hurupdater method should work because it flashes all the partitions including "Cust.img".
If you dont want to use Hurupdater, then I think you should just do "Your device has been unlocked and can't be trusted" method because it downloads stock firmware including "Cust.img".
And also you dont have to flash "Cust.img". If you extract "Cust.img" you can manually the files on to /cust then It should maybe work.
CHECK_123 said:
I think you can try the "Your device has been unlocked and can't be trusted" trick and from what i posted then clicking download latest firmware. But it would relock bootloader and put it into EMUI 8. Unlocking the bootloader is also easy anyways, once you get the bootloader code, you can write it down or put it in notepad to always have the bootloader unlock code.
The Honor 8 also has 2 recoveries, one from holding vol up from "Your device has been unlocked and can't be trusted" and also the normal recovery partition where you usually put twrp in (vol up + power button)
You can also use hurupdater to go from android 8 to android 7. The hurupdater method should work because it flashes all the partitions including "Cust.img".
If you dont want to use Hurupdater, then I think you should just do "Your device has been unlocked and can't be trusted" method because it downloads stock firmware including "Cust.img".
And also you dont have to flash "Cust.img". If you extract "Cust.img" you can manually the files on to /cust then It should maybe work.
Click to expand...
Click to collapse
lol 2 recovery partitions
anyway maybe update.app can be extracted?
jjgvv said:
lol 2 recovery partitions
anyway maybe update.app can be extracted?
Click to expand...
Click to collapse
Yes, there is also a app called "ZArchiver" in Play Store. It can extract "Update.app". But I dont think it can extract .img files. You may need a computer to extract the .img files.
CHECK_123 said:
Yes, there is also a app called "ZArchiver" in Play Store. It can extract "Update.app". But I dont think it can extract .img files. You may need a computer to extract the .img files.
Click to expand...
Click to collapse
.img is easy, if you get system.img then nice, but i cant extract the super.img where system.img is in it.
Dear community,
I have a doogee S96 pro, I'm from Italy, and I installed TWRP from the unofficaltwrp guide.
Now I'm no more able to boot, the phones goes directly to the recovery.
Probably magisk was no able to patch the system and to disable the tm verity (avb). I have a super partition, and from what I saw the fstab is inside the vendor partition inside super.
Doogee does not provide stock roms, so I cannot restore the phone as factory settings, that's why I open this thread.
Is someone available to help me booting into Android or available to give me the stock boot/recovery img? It's a fast and safe procedure, I can give more details on how to do.
Thank you!
Dear @giubenez I had a similar problem. But after I got in touch with doogee support they sent me the firmware. I want to share it with you and with any other person that wants to ROOT THE DOOGEE S96 PRO
The following link is the firmware and upgrade tool. Please open and download.
Please note that if your computer system is French you need to change the name of the downloaded file.
Spoiler: Link
ZN129（S96）
Folder
1drv.ms
When upgrading the firmware, please do not select the 'Format All+Download' option
When flashing the phone, please set up the software first, turn off the phone, and then connect the phone to the computer.
Best wishes
Wow! thank you!!!
You saved... us!
Why doogee does not respond to me? why they not post the firmware on the forum? WTF
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
Google introduced vbmeta which is also a verity check. An option to bypass this check is to flash an empty vbmeta.img before attempting to flash TWRP recovery.
Click to expand...
Click to collapse
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Ankiseth said:
@giubenez Im very happy to contribute something. IDK why doogee doesnt list this firmware in their website. I was very lucky to receive an answer to my emails.
Also I successfully rooted my S96 PRO, but I learned a few things in the process that might be helpful to you or anyone trying to root this model.
1) After flashing the boot.img (using magisk method). The device went into a boot loop. I could not enter into recovery mode either. I discovered vbmeta was responsible for the boot loop.
I solved this by flashing an empty vbmeta file.
Code:
fastboot flash vbmeta vbmeta.img
You can download the vbmeta.img file I used HERE
2) After flashing vbmeta, the device finally booted and the root was done. But the first time, I noticed all the internal storage folders and files were encrypted. (I know this is normal when you browse files through TWRP, but it happened to me while using the phone in the first boot)
I solved that by wiping > Format Data in TWRP
3) Here you can find the files I used to install TWRP and remove the orange state notification on boot: LINK "Credits to www.getdroidtips.com"
Click to expand...
Click to collapse
GOD BLESS YOU, Ankiseth!
YOU SAVE MY PHONE! SPFLASH AND EVERYTHING WORKS!
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
Good day, I would like to ask you to help us. Please use the following link: https://1drv.ms/u/s!AvX9KABcpSV1kTOgCMsUkLyXY-we?e=nMchxl Download the previous version of the S96pro firmware and follow the tutorial to return the phone to OTA The previous version (ver3.02) was upgraded. The tutorial has been included in the firmware compression package. Please test the night vision camera after flashing the camera and let me know if it can be used normally. Thank you very much.
Click to expand...
Click to collapse
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth :
Please note that if your computer system is French you need to change the name of the downloaded file.
Click to expand...
Click to collapse
which file ?
berzerking said:
Hi guys : I need help. Since the last firmware update (settings/about phone/update) DOOGEE-S96Pro-EEA-Android10.0-20210128, my Ir Camera don't work anymore
Video : https://oracle.tuxme.net/s/Xng63Ej3kJoJhOj
When I used the dial mode *#*#8613#*#* SINGLE TEST
* INFRAED LIGHT : i see the IR light
* Night Vision camera : app crash like the camera when i switch to the night vision mode.
Doggee mail me :
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
There Is Hope Brother... I Just Downloaded The Files And Used The SCATTER-LOADING FILE From 3.02 on SP-FlashTools 5.2 Switched It To Download Only And Hit Download .. Plugged In My Phone To USB While OFF And aftyer the loading was complete .. Phone Reboot As If NEW. ( HARD RESET) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!! Now i Just Have To ReLoad All Apps And Accounts .. And Wait For The oukitel WP7 i ordered out of frustration. Will Be Doing A Review Comparison On Both Cameras !!!!! You Can Follow Me Here If Interested https://www.youtube.com/channel/UCYOpd4yooYgKS-0xe63jnCw
Hi all. Thanks for the information. I was in touch with doogee and they say to me that there is an update during this WE (S9S88A7.DGE.DOOGEE.EEA.HB.HJAYYDVFAZ.0128.V3.03820210313-2312.
Nothing change IR camera don't work
I will flash my S96pro during the week with S9S88A7.DGE.DOOGEE.EEA.HB.HJ.AYYDVFAZ.1130.V3.02.zip and I'll post here what happened
HouseOwl said:
) EVERYTHING LOST WARNING.. But IR CAMERA is Working AGAIN!!!!!
Click to expand...
Click to collapse
Yes !!!!! it s alive !!!!
Thank you dude ! my ir works again !!!!!
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
berzerking said:
But the documentation is .... you know ...
Have you a step by step tutorial or tools to do that ?
Beanpod_ActiveTool is a tool to modified serials, Imei ?
Have i to used SP Flash tool ?
Thanks guys !!
by the way @Ankiseth : which file ?
Click to expand...
Click to collapse
Can you write a tutorial? Have you used SP flash tool?
Thank you!
giubenez said:
btw a couple of days after your post, another user posted the same folder on https://4pda.ru/forum/index.php?showtopic=1010578&st=340.
I rooted the phone by using the 4pda method (i.e. flashing super.img, boot.img, vbmeta.img). After that I flashed twrp and it was fine. Everything was working.
After that I downloaded the OTA update and the phone is no more able to boot, simply goes to TWRP. I tried formatting data, dalvik and cache but the situation is always the same: when i try to boot i go to the recovery. Any idea? Thank you
Click to expand...
Click to collapse
I solved in this way:
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(with the empty vbmeta
>fastboot.exe flash recovery recovery.img
(with the stock recovery)
>fastboot reboot
after that the update attempted to start and failed, the phone then boot to android.
The updates always failes after that, so I disabled them.
this is why the update fails..is it because I used the the Russian super img?
{
"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"
}
#edit: it was because I flashed the wrong recovery. With the correct one, i still have issues with the update: md5 chechsum controll is not passed and the update aborts.
I don't care, I prefer a rooted phone without the updates.
your device has not passed the test and may not work properly - Here is a message on the screen . Constantly overloaded is not included in the recovery. The firmware doesn't help.
Could someone repost the S96Pro stock firmware... I can't find it anywhere online, thanks in advance
I'm uploading them.
https://bit.ly/3en9EZY
Thanks giubenez ,u saved me but now I have the watermark from formatting Google Key State : Fail, I don't see a factory mode file to freeze, tried ADB and couldn't find the build prop values, has anyone else ran into this with a fix?
I can't get what problem are you facing. I unlocked and rooted my s96 pro.
If you describe your issue i can help you solving it.
However, i found very risky to root the phone, if you plan to do the ota updates avoid TWRP since it'll make you bootloop at the moment you try to install the update.
The only way to solve it is to flash the stock recovery through adb.
So.. yeah.
I have recently procured this device and want to install twrp, and stock and/or test a gsi and in what capacity the phone works with one of those.
Enabled both developer mode & the usb debug mode and adb devices lists the device.
N.B; the supplied s96pro cable does not seem to carry data, "presumably" because doogee is cheapskates on cables, as well in the support department. I had to use my sony headphone cable. Go figure, its consequential at least, so there's that.
In any case, read this thread and have downloaded all files, including the apparently new stock rom that is listed since yesterday in the evidently wholesome user Ankiseth's link above.
Questions:
In the 4pda link there are some instructions, specifically the adb command with the boot.img, however.. the links seems to be dead. What to do?
A) Can I first do the vbmeta command and then use our lord and savior Ankiseth's twrp recovery file and follow a generic "Case II: Devices with A/B partition scheme" mentioned in this xda twrp guide?
B) Hope that some other wholesome user share the boot.img file?
(Or, can I use the one in the zip file 'S9S88A7.DGE.DOOGEE.HB.HJ.AYYDVFAZ.1203.V3.04' ?)
-
After twrp is accessible can I use twrp/adb and install either the mentioned shared rom and any gsi for that matter?
I use linux and sure there is spflash, but the adb & twrp combo "subjectively feels" as a more stable way of doing things.
Update 2. Got both twrp and magisk going. Now to figure out if I can install a gsi.
Update, got spflashtool working and used the latest stock rom mentioned in my previous post.
However.
I patched the boot.img from said stock rom in magisk and also flashed twrp-recovery with fastboot.
No luck. Magisk seems not to be installed and the usual twrp gui does not show, seems to be the stock recovery. Got a orange state though.
Global/US OnePlus 9 Unbricking Guide
Tested and used on a LE2115 variant device.
YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)
Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
Step 2: Download the MSM tool.
The proper MSM tool can be found here.
I'd recommend using Internet Download Manager to speed it up.
Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
Step 3: Install the right drivers. (If they aren't installed)
The proper drivers can be found here.
Use the readme.txt file in the driver zip, it'll explain how to do everything.
Step 4: Run the "MsmDownloadTool V4.0.exe"
Set the dropdown to "Others" and click next.
{
"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"
}
Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
Click on "Start" once your phone is detected.
Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!
Errors
If an error occurs, don't worry! See here for the potential errors and how to solve them.
Sahara Communication Failed
When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
Install this app.
When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
Go into settings, and enable Advanced Mode (this is req'd)
Go to the main page, and click download update.
When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
Congrats! You fixed it!
If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
akboy7015 said:
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
Click to expand...
Click to collapse
Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
panoramixmeister said:
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
Click to expand...
Click to collapse
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks
winterfoxx said:
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
Click to expand...
Click to collapse
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
So sad , I am in the same situation!
Did you figured it out ??
from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
Congrats! You fixed it!
panoramixmeister said:
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
Click to expand...
Click to collapse
Congrats! I'm glad I was able to help
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
Erm, try factory resetting it in twrp
winterfoxx said:
Erm, try factory resetting it in twrp
Click to expand...
Click to collapse
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me
the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
papad13 said:
So sad , I am in the same situation!
Did you figured it out ??
Click to expand...
Click to collapse
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
allenjthomsen said:
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
Click to expand...
Click to collapse
"a12" you talked aboit open beta? or we have official oxygen android 12? thx
iaio72 said:
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
Click to expand...
Click to collapse
Can you help finding the “param bin file global”
Please ?