Related
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
janos666 said:
Hello all
A friend of mine has a Huawei Honor 6 H60-L12.
He tried to do a firmware update and he bricked the phone.
I bought it and I am desperately trying to recover it.
Here is what I know about the phone:
It had Android 5.1.1
It had Emui 3.1 and was trying to upgrade to 4.0
(Probably was rooted)
It is H60-L12
No matter what I do, I cannot enter recovery mode with the 3 button trick.
I can anytime enter Fastboot mode.
I tried to unbrick it with HONOR Multi-Tool, everything seems to work alright, but flashing boot.img fails. After unbrick I should enter recovery mode but it does not work, phone remains stuck with the Honor logo.
Computer connects to phone in Fastboot mode, Multi-tool and fastboot command works, I also have the drivers installed.
I know that after bricking the rooted phone, I should restore it and remove root before upgrade but I cannot get there.
Please advise
Best regards,
Janos
Click to expand...
Click to collapse
Instead of using the honor multi tool, why don't you use the Android SDK platform tools and connect to your phone through adb. You can solve any problem using that. You have to do everything manually but it works and never disappoints as long as you can enter fastboot mode.
Download android SDK and install it. Run the program and only choose platform tools to download. You don't need anything else
Download the latest firmware for your phone and unzip it to get dload folder which will have an update.app in it.
Download Huawei update extractor and open update.app in it.
Extract recovery, boot, Cust and system images from update.app and save them to the platform tools folder.
Flash them using adb and then do a forced update.
Will work wonders. If you need any help or need more info, please let me know.
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
janos666 said:
Hello muradulislam
First of all, thank you for trying to help me.
I tried something similar to your suggestion but I still have problems.
Let me explain.
My phone is H60-L12
Latest stable firmware which I found is this one:
H60-L02-L12_EMUI3.1_Android5.1_C00B535.zip
I extracted the boot, cust, recovery and system images with Huawei update extractor.
My device is detected in fastboot mode, fastboot devices gives me this result:
c:\adb>fastboot devices
F6CDU15117010953 fastboot
When I try to flash the boot.img, it gives me this error:
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10274 KB)...
OKAY [ 1.092s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.135s
I tried to continue with the rest but I think this is useless.
Please tell me what to do.
Best regards,
Janos
Click to expand...
Click to collapse
My expertise are quite limited but may be, just may be (wishful thinking), you can to flash the twrp recovery specific for your phone. Boot into that and flash a custom ROM from there.
It may not work as I guess, boot.img is needed before entering recovery but give it a try. It never hurts.
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
Click to expand...
Click to collapse
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
janos666 said:
Come on, guys!
There must be somebody who can help me.
Guillermo, panamera2011 and muradulislam tried to help me and I want to thank you for their patience.
Problem is, that I am still missing something.
There are 2 weeks now, each day after work I try to revive this phone.
These are the facts I know:
Tried the programs on 4 different machines, Windows 7, Windows 8.1, Windows 10, 32 bit and 64 bit versions.
Tried different sets of drivers (the one from Android SDK, the Universal ADB drivers, the ones installed by multi-tool)
Result is always the same.
I can flash anytime, any version of cust.img recovery.img and system.img but I can flash only the boot.img which is resulting from an EMUI2.3 or EMUI3.0 package.
If I try to flash boot.img from EMUI3.1 or EMUI4.0, I get the following error:
sending 'boot' (10274 KB)...
OKAY [ 1.103s]
writing 'boot'...
FAILED (remote: flash write failure)
I tried flashing different stock or CWM or TWRP recoveries. They all are written correctly, but I cannot enter any recovery mode.
Someone advised me to try to flash fastboot.img. It is not working, gives error.
I have already many hours and maybe hundreds of firmware writes, I downloaded around 100 GB of firmwares....
There must be an idea how to save this phone.
I am open to any decent advice.
Best regards,
Janos
Click to expand...
Click to collapse
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
janos666 said:
Yes, I can flash cust, recovery and system from the same EMUI2.3 or 3.0 package, but I am still unable to boot recovery.
Unfortunately, Huawei customer service will not help me because phone is H60-L12 (Chinese version) and they don't provide support only for L04
Click to expand...
Click to collapse
Well, I have mentioned DigiGoon in the previous reply. May be he can help a bit.
@janos666
You can always put your desired boot.img in a flashable zip, and flash it via TWRP recovery.
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
janos666 said:
Hi DigiGoon!
No, I cannot, because I was never able to access any kind of recovery
Click to expand...
Click to collapse
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
muradulislam said:
@DigiGoon
You can flash boot.img from emui 2.3 or 3.0? If its written correctly then may be you can try to boot into that emui version by flashing Cust, system and recovery from the same firmware?
Your last hope is Huawei customer service.
Click to expand...
Click to collapse
zinko_pt said:
You can't mix LP and MM ROMs and IMG files. If you want to downgrade, for example, from MM to LP you must use B800 transitional package.
So you must use IMG files from last installed working ROM.
Click to expand...
Click to collapse
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
Sure. I would go from there as I sometimes mixed boot.img from LP or MM and always got bootloop. I would stick to IMG files from last installed ROM.
janos666 said:
Hi zinko_pt
Thank you for your reply.
So this means that I should find out what version he flashed? He told me that flashing firmware went OK, but after reboot, phone wasn't starting anymore.
Click to expand...
Click to collapse
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Hi DigiGoon !
Sorry, which one is the flash transition package?
Which parts to flash from it?
Which is notification LED? I can see only one red LED blinking sometimes, but only when battery is low.
DigiGoon said:
If it was Marshmallow, you have to flash transition package as zinko_pt said, otherwise you have to flash all the IMG files of Lollipop.
And after executing this command from fastboot mode
Code:
fastboot reboot
do you see notification LED light up?
Click to expand...
Click to collapse
Isn't there an option to flash all img files from fastboot?
P.S. I just got new info from the guy who flashed it first time. He says he tried to write version:
H60-L02-L12_emui3.1_android5.1_c00B535
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Click to expand...
Click to collapse
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
janos666 said:
Is there such thing as "not correctly unlocked" or "partially unlocked" bootloader?
When i try to write some parts of the firmware, i get the following error:
FAILED (remote: Command not allowed)
Normally this would mean that the bootloader is NOT unlocked, but anyway i test it, it says unlocked.
If i type fastboot oem get-bootinfo, i get the following result:
c:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.005s
Also the fastboot screen displays in red "PHONE UNLOCKED"
I can write some parts of the firmware, but not the fastboot.img, and boot.img only from EMUI2.3 or EMUI3.0
Please help me
Click to expand...
Click to collapse
Some threads mention of locking and unlocking your device again. Give that a try. May help...
muradulislam said:
Some threads mention of locking and unlocking your device again. Give that a try. May help...
Click to expand...
Click to collapse
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
janos666 said:
I don't have the unlock code that's why I cannot try to relock it... And in this state I cannot get the necessary info to obtain the unlock code.
Anyway, when I tried to unlock with a bogus unlock code (1234567812345678), it gave me an error something like this:
Command failed, bootloader already unlocked.
Click to expand...
Click to collapse
The info you are missing is device id, another user got his device id using Huawei hacker toolkit v 1.4, his model was h60-L02. May be you can give it a try.
You have to lock it before trying to unlock again.
Fastboot OEM lock xxxxxxxxxxxxxxxx...
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
Hello XDA,
i had a fully working device, rooted unlocked bootloader MHA-L29C432. After i clicked in superSU to deinstall it, everything went bad. My smartphone was totally fu*
I got this message Error Mode Attention! Func 10 Bootimg and 2 Load failed i followed this https://forum.xda-developers.com/mate-9/help/bricked-mate-9-please-help-t3722133 post and got rid of the message but know when i boot my phone its restarts after the huawei logo into e recovery permanent.
I dont know what to do know its frustating like my english i guess... lol
I got a unlocked bl and have my twrp back.
calby17 said:
Hello XDA,
i had a fully working device, rooted unlocked bootloader MHA-L29C432. After i clicked in superSU to deinstall it, everything went bad. My smartphone was totally fu*
I got this message Error Mode Attention! Func 10 Bootimg and 2 Load failed i followed this https://forum.xda-developers.com/mate-9/help/bricked-mate-9-please-help-t3722133 post and got rid of the message but know when i boot my phone its restarts after the huawei logo into e recovery permanent.
I dont know what to do know its frustating like my english i guess... lol
I got a unlocked bl and have my twrp back.
Click to expand...
Click to collapse
Follow the instructions here
Shadowprince94 said:
Follow the instructions here
Click to expand...
Click to collapse
I get this error
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.442s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.454s
and i can disconnect now...
calby17 said:
I get this error
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.442s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.454s
and i can disconnect now...
Click to expand...
Click to collapse
Did you use the files in that link? If so, you flashed Oreo.
Whatbwas your firmware before SuperSU? Lx9C432Bxxx
ante0 said:
Did you use the files in that link? If so, you flashed Oreo.
Whatbwas your firmware before SuperSU? Lx9C432Bxxx
Click to expand...
Click to collapse
I did... also i already have twrp why does this weird tool try to install it aigen?
I'm a bit confused and really want to get my phone back to normal
My firmware was EU C432 oreo 8.0.0... something else. I dont remember it so good
calby17 said:
I get this error
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.442s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.454s
and i can disconnect now...
Click to expand...
Click to collapse
dude help me please
calby17 said:
I did... also i already have twrp why does this weird tool try to install it aigen?
I'm a bit confused and really want to get my phone back to normal
My firmware was EU C432 oreo 8.0.0... something else. I dont remember it so good
Click to expand...
Click to collapse
Well, that tool is for Nougat so it's no good for Oreo.
Flash this: https://mega.nz/#!YaIUhZhQ!ewDfrlQC5-fQ1oHfEj2YOo-2rDyi6b-dUoM4qx13e9A
fastboot flash recovery_ramdisk TWRP-3.0.3-for_Oreo.img
Then download this:
https://mega.nz/#!YaJX3LzL!H71Fl2OSHInk7OH7KWbWj7KFrR0lJi9oN9QB2hpMaTM
Flash ramdisk using fastboot flash ramdisk b361_ramdisk.img
B361 is the released oreo in EU. If you had a beta I'll have to find some other ramdisk. I have B329 too if that one doesn't work.
Sorry it took a while, I was sleeping.
ante0 said:
Well, that tool is for Nougat so it's no good for Oreo.
Flash this: https://mega.nz/#!YaIUhZhQ!ewDfrlQC5-fQ1oHfEj2YOo-2rDyi6b-dUoM4qx13e9A
fastboot flash recovery_ramdisk TWRP-3.0.3-for_Oreo.img
Then download this:
https://mega.nz/#!YaJX3LzL!H71Fl2OSHInk7OH7KWbWj7KFrR0lJi9oN9QB2hpMaTM
Flash ramdisk using fastboot flash ramdisk b361_ramdisk.img
B361 is the released oreo in EU. If you had a beta I'll have to find some other ramdisk. I have B329 too if that one doesn't work.
Sorry it took a while, I was sleeping.
Click to expand...
Click to collapse
Thanks.
During flash no problems, but my phone keeps rebooting into eRecovery after your Device has been unlocked and cant be trusted.
calby17 said:
Thanks.
During flash no problems, but my phone keeps rebooting into eRecovery after your Device has been unlocked and cant be trusted.
Click to expand...
Click to collapse
Was it long ago you installed Oreo?
ante0 said:
Was it long ago you installed Oreo?
Click to expand...
Click to collapse
i didnt use the beta. I upgreaded from hicare/ normal systemupdate to oreo when its was out. A few days ago.
calby17 said:
i didnt use the beta. I upgreaded from hicare/ normal systemupdate to oreo when its was out. A few days ago.
Click to expand...
Click to collapse
Ah, good.
I'll extract it when I get home.
Its the boot I sent then. I extracted it from my phone and I'm rooted. That's probably why it doesn't work.
ante0 said:
Ah, good.
I'll extract it when I get home.
Its the boot I sent then. I extracted it from my phone and I'm rooted. That's probably why it doesn't work.
Click to expand...
Click to collapse
Okay Btw yesterday when i was in twrp it showed me NO OS do you really want to shut down? Is this true?
calby17 said:
Okay Btw yesterday when i was in twrp it showed me NO OS do you really want to shut down? Is this true?
Click to expand...
Click to collapse
If a fresh boot image doesn't work you can always use HWOTA8 and reinstall Oreo.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
ante0 said:
If a fresh boot image doesn't work you can always use HWOTA8 and reinstall Oreo.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
Click to expand...
Click to collapse
D. Create "HWOTA8" directory in MTP sdcard.
E. Put hwota8_update.zip, MHA_RECOVERY8_NoCheck.img, and three huawei update package (update.zip, update_data_public.zip, and update_all_hw.zip) files into "HWOTA8" directory.
F. TWRP install sdcard hwota8_update.zip, it will reboot and install update automatically.
I dont understand these steps right i think...
Okay iam stupid. I did not know i can transfer data with my PC in twrp. Now i need these update.zp public and the other one. I need to go in a few minutes, if you can send me a link please where i can find these ante0
Where can i get update.zip data_public und all hw?
calby17 said:
D. Create "HWOTA8" directory in MTP sdcard.
E. Put hwota8_update.zip, MHA_RECOVERY8_NoCheck.img, and three huawei update package (update.zip, update_data_public.zip, and update_all_hw.zip) files into "HWOTA8" directory.
F. TWRP install sdcard hwota8_update.zip, it will reboot and install update automatically.
I dont understand these steps right i think...
Okay iam stupid. I did not know i can transfer data with my PC in twrp. Now i need these update.zp public and the other one. I need to go in a few minutes, if you can send me a link please where i can find these ante0
Where can i get update.zip data_public und all hw?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v107979/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/MHA-L29_hw_eu/update_full_MHA-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...79/f1/full/public/update_data_full_public.zip
Rename update_data_full_public.zip to update_data_public.zip, rename update_full_MHA-L29_hw_eu.zip to update_all_hw.zip
Make a folder on external SD named HWOTA8, put files in there.
ante0 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2307/g1699/v107979/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/MHA-L29_hw_eu/update_full_MHA-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...79/f1/full/public/update_data_full_public.zip
Rename update_data_full_public.zip to update_data_public.zip, rename update_full_MHA-L29_hw_eu.zip to update_all_hw.zip
Make a folder on external SD named HWOTA8, put files in there.
Click to expand...
Click to collapse
yeey ^^ my phone works aigen like charm.
Thank you ante0 great guy good to see that somebody helps here
I am stuck in fastboot. The bootloader is unlocked and I do not have twrp. Everytime I try to install twrp I get this message "FAILED (remote: Failed to load/authenticate boot image: Load Error)" I think it is because my boot image is not there.
When I try to install factory boot image (fastboot flash boot.img) I get this message:
PS C:\platform-tools> fastboot flash C:\Users\Admin\Downloads\boot_stock.img
unknown partition 'C:\Users\Admin\Downloads\boot_stock.img'
error: cannot determine image filename for 'C:\Users\Admin\Downloads\boot_stock.img'
HELP PLEASE
fastboot flash boot boot.img
u missed the boot partition
Bradl79 said:
fastboot flash boot boot.img
u missed the boot partition
Click to expand...
Click to collapse
Just tried and it looks to have flashed, but I am still stuck in bootloader/fastboot menu
here is the output:
PS C:\platform-tools> fastboot devices
efba8ca6 fastboot
PS C:\platform-tools> fastboot flash boot C:\Users\Admin\Downloads\boot_stock.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.118s]
writing 'boot'...
OKAY [ 0.393s]
finished. total time: 2.520s
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Bradl79 said:
did you flash the correct boot.img for the correct phone model and os version?
you may just want to flash the fastboot rom
Click to expand...
Click to collapse
Thank you! That fixed my problem. I flashed 10.0.1-GM21BA-OnePlus7ProOxygen_21.E.21_OTA_021_all_1910071445_8d6a-FASTBOOT
Now I'm back to stock and not rooted. Good thing I backed up my software before flashing.
What's the easiest way to gain root access again? Which specific files do I need?
My phone is GM1917 on Android 10 Oxygen OS 10.01.GM21BA
champstar said:
Now I'm back to stock and not rooted.
Click to expand...
Click to collapse
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
champstar said:
Now I'm back to stock and not rooted.
What's the easiest way to gain root access again? Which specific files do I need?
Click to expand...
Click to collapse
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
redpoint73 said:
That is what flashing a stock boot.img does. What were you trying to accomplish by flashing stock boot.img?
Fastboot boot TWRP, then flash Magisk zip.
Use TWRP unofficial version -70 if you are on Android Q.
Click to expand...
Click to collapse
Thank you! I am now rooted again. There's so much information available online, it is hard to nail down exactly what to do once something messes up.
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
champstar said:
Now my wifi is not working. I flashed the stock boot image so my kernel should be back to stock right?
I am on TWRP 3.3.1-70 and Magisk is up to date.
Click to expand...
Click to collapse
Broken wifi probably means you flashed the wrong stock boot.img.
redpoint73 said:
Broken wifi probably means you flashed the wrong stock boot.img.
Click to expand...
Click to collapse
That did the trick, I flashed modded magisk for OS 10 and now wifi is working.
So, I upgraded from MIUI 13 Stable to MIUI 14 Weekly today (clean flash via fastboot). What I hadn't realized is that my TWRP was still on A12, so TWRP couldn't read internal storage.
But when I tried to flash the A13 TWRP via Fastboot, I get this error:
Code:
Warning: skip copying recovery image avb footer (recovery partition size: 104857600, recovery image size: 201326592).
Sending 'recovery' (196608 KB) OKAY [ 6.370s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
So, somehow, my recovery partition is way too small (or it is just full? But I already erased the old TWRP, so currently I have no recovery)
And the only way I can boot into TWRP is to use the fastboot boot command to temporarily boot into it.
Is there a way to deal with this without doing a wipe?
EDIT: My dumbass was trying to flash the Boot version of TWRP instead of the Rec version
TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
NOSS8 said:
TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Click to expand...
Click to collapse
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
Which img?
NOSS8 said:
Which img?
Click to expand...
Click to collapse
skkk's A13 TWRP image
wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Btw the error message I get after trying to 'flash current TWRP' is this:
Code:
cd /tmp/abrec/ && /system//bin/magiskboot repack -n /dev/block/bootdevice/by-name/recovey_a /tmp/abrec/rec_a.img process ended with ERROR: 1
Error repacking image.
wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
And if I try to flash it via 'Install', I get:
Code:
size of image larger than target device
wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?
NOSS8 said:
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?
Click to expand...
Click to collapse
I am such a moron lmao. I was trying to flash the Boot version of TWRP instead of the Rec version... Just flashed the Rec version and it works now. You made me check back on the TWRP thread, so thanks I guess ahah