Related
Hey there Guys, first of all thanks for takeing the time and reading through this post.
I have used the search function on this board and on google to an unhealthy extend the last 5 Days because no matter what i try there is always something in the way of every method i have tried to the extend that i almost accept the fact that my phone might be Hardbricked in terms of internal memory.
So lets get on with some data.
Im using the Honor 8 FRD-L09 with currently no OS whatsoever.
The Device is:
-Rooted
-Fully Unlocked (Bootloader, OEM, FRP, Debugging Mode (Enabled before Brick)
I Bricked my Honor 8 when i tried to use the Backup function of TWRP to later change the OS from EMUI 5 to AICP
The first try to change to AICP failed, saying for whatever reason that i cannot install this Update on a EVA-L09 Device, (which is strange since the Phone clearly says FRD-L09 on the back aswell as responding good to all past upgrades that i did , which were all for FRD-L09), so i chose to rollback to the Backup, however the Backup was corrupted in the process somehow and so the phone is currently without any OS as i couldnt reinstall the original Backup.
Ok so now for stuff i have tried and the errors i recieve while doing that.
ERecovery
After ERecovery is connected to any WIFI it spits out the error that no Packages can be found.
Fastboot Flashing
I have tried to install the Stock EMUI 4 Boot.img and then use the Huawei Update Extractor to extract the files from the UPPDATE.APP after i made sure that i have the correct firmware downloaded (The oldest possible, FRD-L09C432B101).
I can flash the boot and recovery images just fine, but the System and Cust images throw me the following errors:
System.img Error
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (427769 KB)...
OKAY [ 9.631s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 9.666s
Cust.img Error
flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (416830 KB)...
OKAY [ 8.920s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 11.151s
I have furthermore tested all other FRD-L09 Firmwares up to 130 and even the new B320 for EMUI 5 (for which i installed the EMUI 5 Boot.img) aswell as trying to use:
ZIP Flashing
I have tried to use the following command:
fastboot flash zip UPDATE.APP , which spits out the following error:
fastboot flash zip UPDATE.APP
target reported max download size of 471859200 bytes
sending 'zip' (81444 KB)...
OKAY [ 1.746s]
writing 'zip'...
FAILED (remote: Command not allowed)
finished. total time: 1.761s
I have then tried to lock and unlock the OEM to fix the Command not allowed issue which however did not work out.
MicroSD Updating
I have tried the method of using a MicroSD to install the above Update.APP's in a dload folder in the Root of the card with the stock recovery, however no matter what firmware or what Boot.img or what Stock Recovery.img i use, i always get the Software Incompatibility error.
TWRP Direct Recovery and ADB Sideloading
I have tried the method of directly installing or Sideloading the files through ADB with the help of TWRP, but i get the errors that either /data or /system or /internalstorage cannot be mounted.
I have tried the solution suggested on a few promising youtube videos to simply try a combination of formating to a different type and then back aswell as repairing and then trying again, which worked for /system and /internalstorage, but /data is still not able to mount.
So as you can see i have pretty much tried every trick in the book to get my Phone unbricked, however non of those methods work and im getting desperate.
If any of you have more ideas as to what i could try, please post them here.
Go onto MoDaco honor 8
Google it.
There is a guy called Paul O'Brien on there he will help you sort it out
@ newsupast
have you found a solution?
I have same problem with my FRD-AL10.
Also have checked MoDaCo, but help is very rare.
I've written to Huawei-Support to ask for a rollback-package, but they told me to ask my local support.
The have not replied my question.
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
if you have the boot backup then restore it.
venugopalu007 said:
if you have the boot backup then restore it.
Click to expand...
Click to collapse
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
if you cannot find the boot.img
just do a rollback bro
here is the link
first dload this
http://download-c.huawei.com/download/downloadCenter?downloadId=94070&version=376169&siteCode=de-h
and this now
if your device is BLN-L21C432B151 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v84712/f1/full/update.zip
or BLN-L21C185B131 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v75593/f1/full/update.zip
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Stinks said:
I think that I flashed the wrong files in "boot" and "recovery". Please tell me which files I should flash there.
I used the commands:
.\fastboot flash boot twrp.img
.\fastboot flash recovery twrp.img
Click to expand...
Click to collapse
The guide from "cyberkey.in/how-to-root-honor-6x-100-working/" is simply wrong when it comes to flashing the twrp recovery. If you really followed this guide completely then you flashed the recovery to the boot partition.
Use "fastboot flash recovery twrp.img" to flash the recovery.
You will still have to flash the boot image to your boot partition then (fastboot flash boot boot.img).
Stinks said:
I don't have any backup. Is there a way to just reset everything? Also I don't know how to connect to the phone anymore since adb won't find the device.
Click to expand...
Click to collapse
Use fastboot flash recovery twrpname.img to flash the recovery
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
V
Stinks said:
Ok so basically I need to flash the boot image. However I don't know where to find the stock boot image. I downloaded the so-called "full version" of the stock firmware that I found here: boycracked.com/2017/07/20/official-huawei-honor-6x-bln-l21-berlin-l21-stock-rom-firmware/
However there was no boot.img file inside.
If you could direct me to the proper stock boot.img or send me one, that would greatly help. I had EMUI 5.0 with Nougat 7.0 I believe, phone version BLN-L21.
Click to expand...
Click to collapse
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
venugopalu007 said:
V
Bro there is update.app open it with huawei update extractor then you will see the the boot image.but remember the emui 4.1 boot wont help you in emui 5 .the boot.img must be emui 5 once.
Click to expand...
Click to collapse
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
Bro y this ,just do a rollback .
Stinks said:
Thanks. I successfully updated boot.img and and recovery.img, but system won't load, so I might have imported from the wrong STOCK version.
I tried to reinstall a stock ROM using:
fastboot flash system system.img
But I got this error message:
target reported max download size of 471859200 bytes
sending sparse 'system' (444686 KB)...
OKAY [ 12.901s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 12.929s
Then I tried to erase the system file with "erase system" and got this error:
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
I guess that the only option now is to install the files on an external SD card?
Click to expand...
Click to collapse
I recommend you to download firmware files only from the official honor website or by using the huawei firmware finder(https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146)
In this case try to use huawei firmware finder to get the right stock version for your phone. Download these two files: e.g. update.zip & update_full_BLN-L21_hw_eu.zip.
Export the following image files: recovery, system, boot and cust.
The try to flash them:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
If flashing a partition via fastboot fails then it is usually because it's the wrong image or just not made for your phone.
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Stinks said:
Thank you guys, you saved my phone! I eventually managed to flash the files from Nougat update for European Honor 6X BLN-L21C432B360 that I found there: stechguide.com/honor-6x-b360-nougat-update/
Now the phone is working fine.
Click to expand...
Click to collapse
Glad you revived your phone
question
Stinks said:
Hello! I tried to root my Honor 6x (BLN-L21, EMUI 5.0) following the instructions there:
cyberkey.in/how-to-root-honor-6x-100-working/
The bootloader was successfully unlocked.
But when I tried to flash TWRP the process failed and now my phone is stuck on boot :
"Your device has been unlocked and can't be trusted [...] Your device is booting now."
I can get access to recovery and fastboot. I wiped the cache and tried a factory reset but nothing changed, my system won't start and I don't know what to do.
Please help!
Click to expand...
Click to collapse
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
[email protected] said:
question
my phone is stuck at your device is booting now i cant get to any of other functions such as fastboot or recovry i can only acces it after full charge is gone and after charging.how did you get to acces fastboot or recover.
Click to expand...
Click to collapse
did you solve your issue.....I have same problem now
nokiasatyam said:
did you solve your issue.....I have same problem now
Click to expand...
Click to collapse
Hello, could you be more specific about your problem? I'll be able to help you.
Brief Explanation:
From the screen on which you're stuck, press and hold power button for about 10 seconds to forcibly restart your device. when you see the same screen again, immediately press and hold volume up button(for about 3 seconds) to boot to eRecovery.
> Choose shut down option on eRecovery. press and hold vol down button and insert the charging cable to boot to fastboot.
> Press and hold power and volume up button to boot to recovery. (You could do this even from fastboot screen and the screen you're stuck at).
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
Well guys, I think I did it. I think I really did brick my Honor 8.
Phone details: New Honor 8, Model is FRD-AL10.
It came with the Chinese ROM, locked. What I did was to unlock it with DC unlocker, flash TWRP as custom recovery and root it.
Later, I had some problems with installing Open Gapps so I decided that I will flash a custom ROM unto it. What I chose was this RROS. I followed all of the instructions, made sure my EMUI was up to date, deleted all of my fingerprints (although I did not disable the PIN lock). I performed a factory reset using TWRP, flashed RROS and started facing errors.
Trying to power up the phone I found out it was going into bootloop, not able to start up. Only recovery available was not TWRP, but the default Huawei eRecovery, that lets you restore the phone using the Wi-Fi to download the needed files. Panicking for my new phone, I tried to restore my phone this way, only when it completed the download it failed restoring.
I have tried to unbrick my phone using the Honor 8 Multi-Tool: flashing BOOT.img, CUST.img, Recovery, USERDATA.img and SYSTEM.img. The firmware I downloaded and extracted UPDATE.app from is this: FRD-AL10_C00B135_Firmware_China_Nonspecific_Android 6.0_EMUI 4.1_05013LBP.zip.
The Multi-Tool's log is this:
Code:
12:51:55: All images are found, everything is ready for the unbricking process.
12:52:01: Unbricking started. Your computer may freezes during the process.
12:52:01: flash boot "C:\Users\Mark\Desktop\Honor 8\Unbrick\boot.img"
12:52:03: The Boot image is flashing successfully
12:52:03: flash system "C:\Users\Mark\Desktop\Honor 8\Unbrick\system.img"
12:55:09: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (413881 KB)...
OKAY [ 30.117s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 30.164s
12:55:09: Error#1
12:55:09: flash cust "C:\Users\Mark\Desktop\Honor 8\Unbrick\cust.img"
12:55:28: Error! You are trying to flash the wrong image!
12:55:28: flash recovery "C:\Users\Mark\Desktop\Honor 8\Unbrick\recovery.img"
12:55:31: The Recovery image is flashing successfully
12:55:31: flash userdata "C:\Users\Mark\Desktop\Honor 8\Unbrick\userdata.img"
12:55:38: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 4.183s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.275s]
finished. total time: 5.458s
12:55:38: Error#1
12:55:38: Completed
12:55:38: Something went wrong (((
As you see, SYSTEM.img cannot be written for some reason, and CUST.img is for some reason the wrong file.
I also tried to flash UPDATE.app using a microSD card and the Volume up+Volume down+Power combination, but it fails after 5%, Saying:
Code:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
So either my phone is completely dead, or I am missing something here.
Can anyone help me restore my phone to normal function?
you need to find the rollback package, you had android 7 but you're trying to flash android 6
I traded my phone for this p20 and its rooted, unlocked and has TWRP and I would like to remove all of that and have it back to factory. I've searched but could not find a tutorial. Any help would be appreciated.
Do you have TWRP installed?
Yes. TWRP is installed
I have an OTA update showing on my phone. If I click install will it install stock recovery or will it brick my phone?
ottawadad34 said:
I have an OTA update showing on my phone. If I click install will it install stock recovery or will it brick my phone?
Click to expand...
Click to collapse
I dont think it will brick the phone, but I believe it just wont work. I did basically the same, but I cant remember how I got rid of twrp. I followed a guide (not on xda) very closely to not brick the phone (flashing something to get rid of it, then factory reset).
If you wanna relock your phone, I found the all-in-one-tool very helpful. Just doing oem relock like on the Nexuses doesn‘t work. The tool worked great for me, you still need the unlock code though.
it shouldn't that hard.
1. download full update zip file for your phone.
2. extract the zip, and extract the .APP file using HuaweiUpdateExtractor app.
3. get this file from extracted .APP file : ramdisk.img and recovery_ramdisk.img
4. boot into fastboot and do this :
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
Thanks. When I get home today I will try that
heindrix said:
it shouldn't that hard.
1. download full update zip file for your phone.
2. extract the zip, and extract the .APP file using HuaweiUpdateExtractor app.
3. get this file from extracted .APP file : ramdisk.img and recovery_ramdisk.img
4. boot into fastboot and do this :
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
I get this when I extract update.app
ok i figured out the error but wondering what firmware to download. my phone says eml-l09 8.1.0.102(c792)
do i download this? EML-L09C792B102b (8.1.0.102b)
EML-L09C792B102 (8.1.0.102) FullOTA-MF
ottawadad34 said:
ok i figured out the error but wondering what firmware to download. my phone says eml-l09 8.1.0.102(c792)
do i download this? EML-L09C792B102b (8.1.0.102b)
EML-L09C792B102 (8.1.0.102) FullOTA-MF
Click to expand...
Click to collapse
okay, first things first.
for HuaweiUpdateExtractor, go to settings, and disable every 'verify' settings, those you'll not receive that error message anymore.
next, for download link, here you are : http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2639/g1604/v134418/f1/full/update.zip
heindrix said:
okay, first things first.
for HuaweiUpdateExtractor, go to settings, and disable every 'verify' settings, those you'll not receive that error message anymore.
next, for download link, here you are : http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2639/g1604/v134418/f1/full/update.zip
Click to expand...
Click to collapse
ok got that/ I dont see a recovery_ramdisk.img. I see recovery_ramdis.img and this is what i get when I flash the 2 files
PS C:\adb> fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.448s]
writing 'ramdisk'...
OKAY [ 0.082s]
finished. total time: 0.534s
PS C:\adb> fastboot flash recovery_ramdis recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdis' (32768 KB)...
OKAY [ 0.887s]
writing 'recovery_ramdis'...
FAILED (remote: partition length get error)
finished. total time: 0.899s
ottawadad34 said:
ok got that/ I dont see a recovery_ramdisk.img. I see recovery_ramdis.img and this is what i get when I flash the 2 files
PS C:\adb> fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.448s]
writing 'ramdisk'...
OKAY [ 0.082s]
finished. total time: 0.534s
PS C:\adb> fastboot flash recovery_ramdis recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdis' (32768 KB)...
OKAY [ 0.887s]
writing 'recovery_ramdis'...
FAILED (remote: partition length get error)
finished. total time: 0.899s
Click to expand...
Click to collapse
the last command is wrong, mate.
it should be :
fastboot flash recovery_ramdisk recovery_ramdis.img
heindrix said:
the last command is wrong, mate.
it should be :
fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
thank you so much. You are a lifesaver, it worked Update through the phone failed but updating through HiSuite worked. Now to relock the bootloader do i Use the multi tool or adb?
ottawadad34 said:
thank you so much. You are a lifesaver, it worked Update through the phone failed but updating through HiSuite worked. Now to relock the bootloader do i Use the multi tool or adb?
Click to expand...
Click to collapse
i never relock the bootloader, but i think through adb is okay.
i think the command is :
fastboot oem relock yourcodehere
i must remind you that there's a risk of data lost, you make sure to backup first.
and please save bootloader code somewhere, because Huawei will close the service for releasing bootloader code, for the case maybe you want to sell the device and the buyer needs the code.
Ok thanks. I guess I will be keeping it unlocked. The guy I traded for this phone did not give me the unlock code
Worked for me on my EML-L09. Thanks.