Related
Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
There is no need to relock your bootloader.
The reason the OTA-Update fails, is that one of the /boot, /system, /logo or /recovery partitions are changed.
For example the /recovery if you flashed it permanently or the /boot partition for rooting. Also the /system partition when you remove same build-in apps or install xposed and do not reverse the changes.
To restore the partitions you have to flash the stock ROM Images of the partitions.
That's all you have to do!
Most of you have the problem that they can't find the right stock ROM with the correct build-no. (or don't have access to the FileFactory folder).
In desperation you just download any stock ROM that contain "XT16xx" and flash it, without any idea what you are doing.
And that is the reason your phones lost the IMEI no.
There is also another problem with changing /system or /boot after the OTA-Update, because usually Motorola don't release a stock ROM image which include the OTA-Update when the next OTA-Update should be a major update to the next Android Version (6.0.1 -> 7.0). So when you make some changes to /system or /boot (rooting) after the OTA-Update you have no stock ROM image files of the current build-no and you have to flash the hole stock ROM image and erase all your data and take then two OTA-Updates (6.0 -> 6.0.1 -> 7.0) to get Android 7.0.
This is the reason you should make a TWRP backup of /system and /boot to restore it and then take the next OTA-Update, maybe to Android 7.0.
[GUIDE]
ONLY FOLLOW THIS GUIDE IF YOU HAVE THE CORRECT STOCK ROM IMAGE !!!
STOCK ROM IMAGE FILE NAME MUST CONTAIN YOUR CURRENT BUILD-NO AND SKU (e.g. XT162) OF THE PHONE !!!
I am not responsible for any damage or failure on your smartphone.
Requirements:
Correct Stock ROM Image for your phone -> FileFactory Moto G
Minimal ADB & Fastboot
Motorola Drivers
TWRP - Custom Recovery
1a. If you get the OTA-Update notification
If you are rooted and the OTA-Update notification pops up, download the update and hit the "later" button. Go with your fav. Filebrowser to:
Code:
/data/data/com.motorola.ccc.ota/app_download
and copy the OTA-Update "Blur_Version.2....." file to your SD-Card.
Go to 2. ↓
1b. If you don't get the OTA-Update notification because you already try to install it and get "error 7"
First option is to wait and drink some cups of tea till the notification popup again and try 1a. ↑
Second option is to go to 2. ↓, but then you have no root access till the notification popup up again.
2. Restore the stock ROM images
Extract only the boot.img, logo.bin, recovery.img, system.img_sparsechunk.0 to .7 files to the MADB&FB folder.
Connect your phone to your PC and open MADB&FB, check the connection with:
Code:
adb devices
return should include your "serial-no" and "device".
Reboot into bootloader with:
Code:
adb reboot-bootloader
and check again with:
Code:
fastboot devices
return should be "serial-no" and "fastboot".
Flash the partitions with:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
After every command should be a return with "OKAY".
Reboot your Phone with:
Code:
fastboot reboot
After reboot all your data is still there and you can sideload the OTA-Update, if the OTA-Update notification has not already appeared.
3. Sideload from SD-Card
Reboot into recovery:
Code:
adb reboot recovery
After few seconds the dead "Android" should appear with "No command."
HOLD "Power" and then HOLD "VOLUME UP" for 2-1 seconds and release. Now you are in "Android Recovery".
Select "Apply update from SD card" and choose your "Blur_Version.2..." file.
After 20-30 min you get "success" message and select "Reboot system now".
4. Make a backup of /system, /boot, /recovery and /logo
Before you can make some further changes on your /system, /boot, /recovery and /logo, you should backup these partitions for the next OTA-Update.
Follow all steps in the Guide to root systemless -> [ROOT][GUIDE] Systemless Rooting with SuperSU 2.78 , which include the TWRP backup (/system and /boot).
Then come back here and install on your rooted phone -> Partitions Backup & Restore.
Select "LOGO" and "RECOVERY" and change Settings to "Raw partitions image (img)" and save it on your SD-Card.
Now you have all partitions as a backup for the next OTA-Update. So when the next update is coming, you have to flash /logo and /recovery and then restore your TWRP backup and you are able to install the update without issues.
Have Fun and don't pay attention to my writing errors
Bender1987 said:
Many of you have trouble to install the last OTA-Update (SP 1.July) on their rooted devices.
Here is a quick guide to successfully install the OTA-Update without losing any of your data, only all changes you made to the system are restored to stock.
You can root your phone again with this GUIDE after the update -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
There is no need to relock your bootloader.
Click to expand...
Click to collapse
I used this procedure a couple of days ago and it worked flawlessly. When I rebooted after flashing all of the stock files, my OTA update notification was there waiting for me to select "Install". I did and it installed without issues.
What is surprising to me is how many people try it with the wrong firmware and then are surprised when they screw up their phones.
I was so close!!! lol, didn't realize they checked /logo for modifications. Was about to completely wipe everything to get the update to apply. Glad I checked xda before doing so as all I was missing was flashing stock logo.img (restoring system, recovery and boot I had already tried). Thanks Bender1987 for the easy guide.
I have the 64GIG 4G plus (XT-1644)
Hi @Bender1987,
Thank you for your guides, they are very helpful. I've already unlocked, rooted without flashing twrp, uninstalled some system apps and flashed xposed using Flashfire on my xt1642, and eveything is running fine so far. So, when an OTA update is available (hopefully nougat!) will I receive the notification? Or does the rooting stop even OTA notifications? Thanks!
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Bender1987 said:
@pblasi
You already received the OTA-Update with SP 1.July? If yes, i think the next OTA-Update should be Android 7.0.
Click to expand...
Click to collapse
I just got my xt1642 a week ago. It already came with build number: MPJ24.139-48 which I think is the latest, so I haven't received any OTA update yet.
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Bender1987 said:
@pblasi
the current build-no is MPJ24.139-63 with Security Patch 1.July.
I add "TWRP backup" which is very important for the next OTA-Update, maybe Android 7.0.
Click to expand...
Click to collapse
Well, I spent 2 days without touching the phone before unlocking/rooting and didn't receive this ota-update. Maybe it is not available for my version (32gb, 3gb ram, xt1642)...
If I didn't flash twrp, I guess I won't need to restore it, right? Anyway, I made the full backup following your instructions. In which partition is stock twrp included? Boot? Thanks.
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Bender1987 said:
Backup with TWRP only cover system, boot, cache and data partition, that means I have to add some steps to get a backup from logo and recovery -_-
Maybe tomorrow.
Click to expand...
Click to collapse
Let me know if I understood it right. I made a TWRP backup of untouched boot, system and data, rooted and installed xposed without flashing TWRP and without changing logo.bin. Then I should be able to install next OTA update if I previously restore my copies of boot and system in TWRP. Right? No need to flash stock images in this case? Thanks!
@pblasi jep you are right
Xt1644 not play nice with adb nor does it go into recovery it just reboots when I hold the buttons...or it stays on no command
All devices have stock recovery on it. I tried it again, when you see the dead Android -> HOLD POWER and then HOLD VOLUME UP for 2-3 sec. -> release VOLUME UP and still HOLD POWER
https://www.youtube.com/watch?v=SuOrl7Q4JY8
at 1:58.
When I flash the files, for the boot and recovery I get a warning that the "image not signed or corrupt". Eventually it is written... but is that normal?
mfastboot flash recovery recovery.img
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
Image not signed or corrupt
OKAY [ 0.153s]
finished. total time: 0.684s
Click to expand...
Click to collapse
@SoNic67
Maybe it is not the correct stock rom?
Hmm, it was DL from the usual place, but true, I am not 100% sure about it. However, it "works" but I don't get the OTA.
I am DL now the newer full FW.
LE: That latest full FW worked. I had to reinstall all my apps from backup but...
Weird thing is that before my imei disappeared I was getting the ota updates
Sent from my 6045X using Tapatalk
@Bender1987 I have a TWRP backup of unmodified Stock ROM XT1643, so now to install OTA do I just have to flash the nandroid backup & then flash stock recovery to get ota updates? If so then how can I go about flashing stock recovery. Thanks in advance mate
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Bender1987 said:
@Amit_timA
TWRP only backup /system and /boot, to restore recovery you must flash it from a stock rom image. If all partitions are stock after restoring you can get the OTA-Update.
Click to expand...
Click to collapse
Will try
Hey Guys, i have a big problem. I had the cdroid-rom on my Honor 8. Today something crashed and i can only boot into twrp. It say's no OS installed and i can only switch between fastboot-mode & twrp. In Fastboot i cannot flash anything. When i try to flash twrp again it says
"target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.541s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s"
i also tried to store back to stock with the dload mehtod but it does't work. I tried several options to bring the phone back to life but nothing works.. can someone give me an explanation how i can bring the phone back to stock software?
Thanks!
Looks like your bootloader is locked which is why you can't flash recovery.
Not sure if you can get around that. If you can still boot into TWRP you can recover.
Try this
1 DL stock Rom b360
2 DL twrp 3.1.1-1
3 extract the recovery files
4 Boot in twrp and connect with PC
5 copy the dload folder with the update.app to your sdcard
6 copy the stock recovery to your device Zoo
7 flash the stock recovery with twrp
8 after flash.....make three button method
Sry for the bad english...........i had a similar problem......i flashed twrp 3.1.1-1 and lineage OS..... All was fine
xynewageyx said:
Try this
1 DL stock Rom b360
2 DL twrp 3.1.1-1
3 extract the recovery files
4 Boot in twrp and connect with PC
5 copy the dload folder with the update.app to your sdcard
6 copy the stock recovery to your device Zoo
7 flash the stock recovery with twrp
8 after flash.....make three button method
Sry for the bad english...........i had a similar problem......i flashed twrp 3.1.1-1 and lineage OS..... All was fine
Click to expand...
Click to collapse
Can you give me a link to the files i need? Also, how do i get the original recovery.img?
Thanks for your answer!
EDIT: I have no Windows PC, how can i extract from mac?
nckwtzl said:
Can you give me a link to the files i need? Also, how do i get the original recovery.img?
Thanks for your answer!
EDIT: I have no Windows PC, how can i extract from mac?
Click to expand...
Click to collapse
Not sure if the Huawei extractor will work on MAC. What was your exact model and build number.
You can also try flashing the Rollback Package to EMUI 4, then the EMUI 4 software itself via dload from sd card. This was the method that was always able to revive my phone when nothing else worked.
try this first.......install twrp 3.1.1-1 and try to flash openkirins lineageos.....
And huawei update extractor is not for mac......you will need a virtual maschine
For everyone who has the same problem. I used this Tutorial to solve the problem. I think this solution is the problemsolver in general. https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
Hi my friends
I update my mate 9 to Oreo beta. its cool.
now I want install TWRP Recovery, but in installation through fastboot, I faced with this error:
failed (remote: partition length get error)
please help me. I cannot install recovery.
thanks
where did you get the Oreo beta?
I believe the beta can be downloaded through their web site as a limited tester. My understanding of flashing recovery onto the new Android build is that you'll need a newest version of twrp to work for oreo. Most the time the new updates will mess around with the internal storage space.
ystokar said:
where did you get the Oreo beta?
Click to expand...
Click to collapse
You can get it via FH.
vang2k said:
I believe the beta can be downloaded through their web site as a limited tester.
Click to expand...
Click to collapse
The 250 users quota has long been filled unfortunately.
Sent from my MHA-L29 using XDA Labs
martin2007 said:
Hi my friends
I update my mate 9 to Oreo beta. its cool.
now I want install TWRP Recovery, but in installation through fastboot, I faced with this error:
failed (remote: partition length get error)
please help me. I cannot install recovery.
thanks
Click to expand...
Click to collapse
The recovery partitions are different in Android O. There is no working TWRP yet.
If you want to downgrade, however, there will be a solution soon.
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
It worked, I have TWRP, but my PC does not connect to ADB. I tried reinstalling all the drivers but it does not even make any sound when I connect it to USB
fairyland4ever said:
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
great, that worked well. now - with the changed partition table, would you recommend rooting the phone with either of these methods: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986 ?
Dear friend, i have same issue, kindly tell me how to change partition table?
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
UPDATE:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
tobyffm said:
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
Click to expand...
Click to collapse
You need to flash to recovery_ramdisk. Fastboot flash recovery_ramdisk twrpo.img
Hi there , so if we want to flash Oreo through fastboot , what could be the commands lines please ?
as ie : fastboot flash boot boot.img or boot_ramdisk / boot_kernel boot.img ? and so on ..
the complete list of commands, would any 1 pass it over here please ? thanks a bunch
FuM8 said:
Hi there , so if we want to flash Oreo through fastboot , what could be the commands lines please ?
as ie : fastboot flash boot boot.img or boot_ramdisk / boot_kernel boot.img ? and so on ..
the complete list of commands, would any 1 pass it over here please ? thanks a bunch
Click to expand...
Click to collapse
Well. You can flash most partitions. If you extract imgs from an oreo update.app you get the complete list (though some can't be flashed, like erecovery_*.img).
If you extract ramdisk (boot ramdisk) from update.app you flash it as fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img
To extract in Huawei Update Extractor you need to go to settings and disable checksum, it won't extract because something is up with erecovery_ramdis.img (it's misspelled too).
thank you for your reply @ ante0
Something else please .. as I tried and failed to update from MHA-L09-c432198 to Oreo I now get a bootloop error 14 iom3 , I saw on another thread some solutions, which dont work for me as I just cannot boot into twrp because of my battery not charging, even in download / recovery mode... battery three months old... and always working good
What I need to know is how can I either get my twrp saved system back through fastboot or else how can I flash - again only by fastboot mean - the stock firmware of my c432b198 or ...? as i need to flash boot, recovery, cust & system , how can I do so while there is no CUST img in extracted data (seems to be inside the data img itself).
Or else how can do A COMPLETE FORMAT of my internal storage ? the command , any1 i do, give either "not allowed" or partition lengh etc"
any way I can use fastboot to get out of this bootloop iom3 error 14 which don't let my battery charge a little ?
I'm a little much confused and do apology for that. Any help is desesperated needed .
So what is the boot image or the boot partition now called in OREO? I am trying to unbrick my Honor 9 and had Oreo L09-B321 on it before. The only thing I am missing is to successfully flash boot since I am also getting the "partition length error" when I use fastboot boot BOOT.img.
overflyer said:
So what is the boot image or the boot partition now called in OREO? I am trying to unbrick my Honor 9 and had Oreo L09-B321 on it before. The only thing I am missing is to successfully flash boot since I am also getting the "partition length error" when I use fastboot boot BOOT.img.
Click to expand...
Click to collapse
I think ramdisk is the boot partition in oreo, so you have to use fastboot flash ramdisk RAMDISK.img.
YASS
tobyffm said:
Hi, I also have Mate 9 L09 and have exact same error message:
fastboot flash recovery twrpo.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.579s]
writing 'recovery'...
FAILED (remote: partition length get error)
UPDATE:
OK, I managed it by myself, haha.
For anyone else with same issue.
Since Oreo: Partition names have changed.
Use this command: fastboot flash recovery_ramdisk RECOVERY.img
"recovery" changed to "recovery_ramdisk" now.
finished. total time: 0.600s
I downloaded that special TWRP recovery image, but still get the same message. Does not work for me, any new solution available?
Click to expand...
Click to collapse
Worked like a charm. Thanks.
****ty ADB
i have adb drivers installed but if i enter: fastboot flash recovery_ramdisk RECOVERY.img it says cannot load RECOVERY.img
still stuck
tothl74 said:
I think ramdisk is the boot partition in oreo, so you have to use fastboot flash ramdisk RAMDISK.img.
Click to expand...
Click to collapse
i still get folowing error
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (34634 KB)...
OKAY [ 1.214s]
writing 'recovery_ramdisk'...
FAILED (remote: partition error)
finished. total time: 1.235s
i have tried all three commands
fastboot flash recovery twrp_Honor_7x.img
fastboot flash recovery_ramdisk twrp_Honor_7x.img
fastboot flash ramdisk twrp_Honor_7x.img
i cant flash!! same error!!!
failed remote partition lenght get error
Hi,
Yesterday I've tried to rebrand my phone FRD-L09C432 to FRD-L09C10 version. It succeeded and I was in EMUI 4.1.
Then i tried to use hackslash's method to flash android O. While flashing the rom with HuRupdater I've go an error.
Now my phone is bricked in
ERROR MODE
Func NO : 8 (hifi image)
Error NO : 1 (security verify failed)
I've been able to go to fastboot once, and i unlocked bootloader again, but now I can't go back to bootloader anymore.
I've tried every button combination and i left my battery drain to 0% but still no success.
If anyone of you got an idea, I'd be grateful
Did you tried to update your device to Oreo directly from EMUI 4.1. My guide clearly said that you need to flash Nougat package and not Marshmallow one before flashing Oreo.
Regardless, your device is screwed unfortunately and you can't boot your device to fastboot is problematic. I guess you also can't reboot your device to recovery since after you performed the unlock the device has to perform a factory reset and since it's unable to perform it, it has locked you out of fastboot. When I was stuck in this situation, I discharged the battery completely and connected it to PC while holding the volume down button to force it into fastboot. I had to do it several times until it finally worked. After that flash TWRP to your device immediately. Reboot your device to recovery by connecting it to PC and holding the Volume Up button instead. TWRP will allow you to flash a PV package and restore your device.
If you're still unfortunately unable to get your device up and running you have to use DC Phoenix to restore the firmware (it's a paid solution, costs 15 Euros).
hackslash said:
Did you tried to update your device to Oreo directly from EMUI 4.1. My guide clearly said that you need to flash Nougat package and not Marshmallow one before flashing Oreo.
Regardless, your device is screwed unfortunately and you can't boot your device to fastboot is problematic. I guess you also can't reboot your device to recovery since after you performed the unlock the device has to perform a factory reset and since it's unable to perform it, it has locked you out of fastboot. When I was stuck in this situation, I discharged the battery completely and connected it to PC while holding the volume down button to force it into fastboot. I had to do it several times until it finally worked. After that flash TWRP to your device immediately. Reboot your device to recovery by connecting it to PC and holding the Volume Up button instead. TWRP will allow you to flash a PV package and restore your device.
If you're still unfortunately unable to get your device up and running you have to use DC Phoenix to restore the firmware (it's a paid solution, costs 15 Euros).
Click to expand...
Click to collapse
Thank you for the answer.
Btw, can DC Phoenix helps me even when I don't have access to the bootloader? Or do I need first to find a way to go into bootloader
Elyth_ said:
Thank you for the answer.
Btw, can DC Phoenix helps me even when I don't have access to the bootloader? Or do I need first to find a way to go into bootloader
Click to expand...
Click to collapse
DC Phoenix can help you even if the bootloader is not accessible. For that you have to disassemble your device and follow the DC Phoenix Method 3 aka Test point method to flash board software package and then the complete OS.
hackslash said:
After that flash TWRP to your device immediately.
Click to expand...
Click to collapse
HI again, I'm actually in bootloader mode, but flashing TWRP gives me the error FAILED (remote: partition length get error). Do you have any idea on what's causing it ?
EDIT : fastboot flash recovery_ramdisk <your file as usual> worked
EDIT 2 : can't get to reboot in recovery after flashing with that command
EDIT 3 : When I try to reboot to recovery, I get the screen saying "Your device has been unlocked and can't be trusted..." but then I have the error Func NO : 11 (recovery img) Error NO : 2 (load failed!)
Elyth_ said:
HI again, I'm actually in bootloader mode, but flashing TWRP gives me the error FAILED (remote: partition length get error). Do you have any idea on what's causing it ?
EDIT : fastboot flash recovery_ramdisk <your file as usual> worked
EDIT 2 : can't get to reboot in recovery after flashing with that command
EDIT 3 : When I try to reboot to recovery, I get the screen saying "Your device has been unlocked and can't be trusted..." but then I have the error Func NO : 11 (recovery img) Error NO : 2 (load failed!)
Click to expand...
Click to collapse
What TWRP are you trying to flash? I recommend flashing Honor View 10 one from twrp.me. After you install it and you're able to boot to recovery, ping me back.
hackslash said:
What TWRP are you trying to flash? I recommend flashing Honor View 10 one from twrp.me. After you install it and you're able to boot to recovery, ping me back.
Click to expand...
Click to collapse
Unfortunately I tried to use DC Phoenix to flash L09C10 EMUI 4.1 ROM, and this is what I got
Code:
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 73QDU16B03003820
7/15/2018 8:57:52 PM Starting extracting partitions from file UPDATE.APP
Current version: FRDC432B001
Cannot create extract directory: D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\tmp\20180715_205752_UPDATE\
Extract files to directory: D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
7/15/2018 8:58:16 PM Extracting partitions finished OK
7/15/2018 8:58:17 PM Starting to write device in FASTBOOT mode...
Device found: 73QDU16B03003820
IMEI: 861349039027486
Build number: :FRD-L09C10B130
Product model: FRD-L09
Writing XLOADER partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\BOOT.img
BOOT partition UPDATE ...FAILED
Writing RECOVERY partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\RECOVERY.img
RECOVERY partition UPDATE ...FAILED
Writing RECOVERY2 partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\RECOVERY2.img
RECOVERY2 partition UPDATE ...FAILED
Writing DTS partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\DTS.img
DTS partition UPDATE ...FAILED
Writing MODEM partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\SYSTEM.img
SYSTEM partition UPDATE ...FAILED
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\CUST.img
CUST partition UPDATE ...FAILED
Writing MODEM_DTB partition with file D:\Users\Le Kerneau\Apps\DC_Phoenix_v57\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
7/15/2018 8:59:35 PM Writing device finished - INCOMPLETE
Waiting for fastboot device...
Device found: 73QDU16B03003820
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
Process was cancelled by user
Then my phone shutdowned and doesn't turn off anymore
Elyth_ said:
Unfortunately I tried to use DC Phoenix to flash L09C10 EMUI 4.1 ROM, and this is what I got
Then my phone shutdowned and doesn't turn off anymore
Click to expand...
Click to collapse
Well I won't lie, you're in the exact same situation I was in. However even if your phone doesn't turns on, it's still in fastboot mode. Connect it to PC and check fastboot if it is connected. If not hold down the power button to force a restart and then hold volume down button and reconnect the phone to PC. As soon as fastboot detects your device, use DC Phoenix to again flash the EMUI 401 firmware. This time it will flash successfully.
nothing
hackslash said:
Connect it to PC and check fastboot if it is connected. If not hold down the power button to force a restart and then hold volume down button and reconnect the phone to PC. As soon as fastboot detects your device, use DC Phoenix to again flash the EMUI 401 firmware. This time it will flash successfully.
Click to expand...
Click to collapse
Idk, I try every button combination but the screen stays black and fastboot isn't connected
Screen didn't turned on for me too. But I guess I was lucky enough that the device was in fastboot mode and I was able to flash the firmware.
Your only choice is the Method 3 now, the Testpoint method.
hackslash said:
Screen didn't turned on for me too. But I guess I was lucky enough that the device was in fastboot mode and I was able to flash the firmware.
Your only choice is the Method 3 now, the Testpoint method.
Click to expand...
Click to collapse
I simply don't know how to thank you enough. Changed the USB port and my phone is now connected in fastboot mode.
I flashed again with DC Pheonix, it failed again, but my phone restarted and screen turned on. Bootloader was again locked, I unlocked it again and then flashed TWRP from the TWRP Honor 8 Guide.
Now I'm finally back in TWRP, which firmware should I flash ? I'll follow exactly your instructions ahah :laugh:
Elyth_ said:
I simply don't know how to thank you enough. Changed the USB port and my phone is now connected in fastboot mode.
I flashed again with DC Pheonix, it failed again, but my phone restarted and screen turned on. Bootloader was again locked, I unlocked it again and then flashed TWRP from the TWRP Honor 8 Guide.
Now I'm finally back in TWRP, which firmware should I flash ? I'll follow exactly your instructions ahah :laugh:
Click to expand...
Click to collapse
That's excellent. Before I tell you which firmware to flash, what was your device region before all of this happened.
hackslash said:
That's excellent. Before I tell you which firmware to flash, what was your device region before all of this happened.
Click to expand...
Click to collapse
L09C432, European/French
Elyth_ said:
L09C432, European/French
Click to expand...
Click to collapse
Okay, what you should do is, flash L09C432 oeminfo.img from TWRP (you can check Huawei MultiTool for the image). After that perform a complete factory from TWRP. Don't reboot your device yet.
Then, flash B394 firmware (FullOTA-MF-PV one) and ensure you flash all the files available for that firmware (two files). Once the flash is complete reboot your device and you're on EMUI 5. You can then use Firmware Finder to update your device to latest package authorised for your device.
hackslash said:
Okay, what you should do is, flash L09C432 oeminfo.img from TWRP (you can check Huawei MultiTool for the image). After that perform a complete factory from TWRP. Don't reboot your device yet.
Then, flash B394 firmware (FullOTA-MF-PV one) and ensure you flash all the files available for that firmware (two files). Once the flash is complete reboot your device and you're on EMUI 5. You can then use Firmware Finder to update your device to latest package authorised for your device.
Click to expand...
Click to collapse
Thanks i'll sure try this out ! Just in case, "complete factory," means factory reset not format data right ?
Elyth_ said:
Thanks i'll sure try this out ! Just in case, "complete factory," means factory reset not format data right ?
Click to expand...
Click to collapse
Yep!
hackslash said:
Okay, what you should do is, flash L09C432 oeminfo.img from TWRP (you can check Huawei MultiTool for the image).
Click to expand...
Click to collapse
Another question, Huawei Multitool is mainly in russian and i don't understand a single word of it so I'm kind of lost. How should I get the image with that software ?
Elyth_ said:
Another question, Huawei Multitool is mainly in russian and i don't understand a single word of it so I'm kind of lost. How should I get the image with that software ?
Click to expand...
Click to collapse
Try this version http://pro-teammt.ru/projects/hwmt/release/Multi-Tool 8.msi
It's GUI and should prompt you to select language or atleast changing language would be easy.
hackslash said:
Try this version http://pro-teammt.ru/projects/hwmt/release/Multi-Tool 8.msi
It's GUI and should prompt you to select language or atleast changing language would be easy.
Click to expand...
Click to collapse
It seems to be the one I had, anyway i'll do some research bc the GUI is still almost only in Russian even when I select English.
When i click Launch Huawei MultiTool the CMD is in Russian even tho English is selected
EDIT : Nevermind, I found a tutorial I did it.
So i goofed up and wiped everything under advanced when I was switching Roms. I was able to get the original recovery image installed (nv-recovery-st-wx-na-wf-5.2.0.zip) but if i reinstall TWRP and attempt to install any rom, the device name is still "" instead of "ShieldTablet". Is there anyway to restore the device name? I have been digging around on the forums (Including other device forums) but installing recovery is all I have been able to find. (Note: There was some guides advising removal of the device name check from the script within the image file, then re-zipping it. But this seems to always fail with a bad image error.)
Recovery was installed manually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Recovery image pulled from https://developer.nvidia.com/shield-open-source
More info to issue.
Boot into bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
Boot into OS. (everything works.)
EnableUSB debug
adb shell settings get global device_name (Gives back "SHIELD Tablet")
Reboot into bootloader
fastboot flash recovery twrp-3.5.1_9-0-shieldtablet.img
Reboot into twrp
Copy on Rom and attempt to install.
Error text:
E3004: This package is for device: shieldtablet; this device is .
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Lineage-14.1-20210312-unofficial-shieldtablet.zip'
Note: above error text occurs when trying to install any ROM.
I am trying to figure out where "E3004: This package is for device: shieldtablet; this device is ." is pulling the device name. That is the part that I need to fix somehow.
Hi did you try to use a older version of twrp ? I also had my issues with the 9.5.1 version as it doesnt recognize my sdcard so i reflashed the version 9.5.0
You beautiful person! Downgrading from twrp-3.5.1_9-0-shieldtablet.img to twrp-3.5.0_9-0-shieldtablet.img allowed the img to install!
Checking in with the same problem. Thank you for the solution listed of downgrading to 3.5.0_9-0.
Currently flashing!