Hello guys,
Can anyone please clarify to me the source of my problem:
I've tried to root my PRA-LA1 (Huawei GR3 2017 PRA-LA1C185B120) without making a TWRP backup of my partitions :crying: I wiped the data and cache but after that when accessing to system I am not anymore able to:
-access developer options
-setting Pin, Password or enrol a fingerprint
-doing a factory reset from security options
-uninstalling any app even those I've installed
I've already try to flash (boot.img, both recoveries imgs,system.img ) without any success but can't flash vendor.img (Command not allowed)
RAR1991 said:
Youppii
After multiple trying and boot loops, here is what I did to solve my problem
1- I have an UNLOCKED FRP and UNLOCKED bootloader
2- I Downloaded the B182 TWRP Backup from This Post Made By ChinHona used the rooted version from this link
3- I used TWRP to make a Backup of my own partitions just in case , and I made a full Restore Without oeminfo and Version
after that the phone has booted (after some reboots of course )and it's working properly but the version still PRA-LA1C185B120 to fix that I have opened my own version.emmc.win backup in a HexEditor and searched for every occurrence of C185B120 and replaced it with C185B182 reflashed it with TWRP with skipping MD5 Check and that's it.
Click to expand...
Click to collapse
RAR1991 said:
Hello guys,
Can anyone please clarify to me the source of my problem:
I've tried to root my PRA-LA1 (Huawei GR3 2017 PRA-LA1C185B120) without making a TWRP backup of my partitions :crying: I wiped the data and cache but after that when accessing to system I am not anymore able to:
-access developer options
-setting Pin, Password or enrol a fingerprint
-doing a factory reset from security options
-uninstalling any app even those I've installed
I've already try to flash (boot.img, both recoveries imgs,system.img ) without any success but can't flash vendor.img (Command not allowed)
Click to expand...
Click to collapse
Try dload method . google it
Enviado do meu Mi A1 através do Tapatalk
euricoalex said:
Try dload method . google it
Enviado do meu Mi A1 através do Tapatalk
Click to expand...
Click to collapse
can't use dload "Software install failed!" and same thing from TWRP
RAR1991 said:
can't use dload "Software install failed!" and same thing from TWRP
Click to expand...
Click to collapse
Seek in htcmania . have a good tutorial .
Enviado do meu Mi A1 através do Tapatalk
euricoalex said:
Seek in htcmania . have a good tutorial .
Enviado do meu Mi A1 através do Tapatalk
Click to expand...
Click to collapse
Sorry I don't understand what you mean by that
[SOLVED]
Youppii
After multiple trying and boot loops, here is what I did to solve my problem
1- I have an UNLOCKED FRP and UNLOCKED bootloader
2- I Downloaded the B182 TWRP Backup from This Post Made By ChinHona used the rooted version from this link
3- I used TWRP to make a Backup of my own partitions just in case , and I made a full Restore Without oeminfo and version.
after that the phone has booted (after some reboots of course )and it's working properly but the version still PRA-LA1C185B120 to fix that I have opened my own version.emmc.win backup in a HexEditor and searched for every occurrence of C185B120 and replaced it with C185B182 reflashed it with TWRP with skipping MD5 Check and that's it.
RAR1991 said:
Youppii
After multiple trying and boot loops, here is what I did to solve my problem
1- I have an UNLOCKED FRP and UNLOCKED bootloader
2- I Downloaded the B182 TWRP Backup from This Post Made By ChinHona used the rooted version from this link
3- I used TWRP to make a Backup of my own partitions just in case , and I made a full Restore Without oeminfo and Version
after that the phone has booted (after some reboots of course )and it's working properly but the version still PRA-LA1C185B120 to fix that I have opened my own version.emmc.win backup in a HexEditor and searched for every occurrence of C185B120 and replaced it with C185B182 reflashed it with TWRP with skipping MD5 Check and that's it.
Click to expand...
Click to collapse
Glad you've got your phone to work.
Still nothing for me.
NetfariousIntent said:
Glad you've got your phone to work.
Still nothing for me.
Click to expand...
Click to collapse
do you have TWRP Installed on your phone? if yes I think that this method will be useful for you
[/COLOR]
RAR1991 said:
do you have TWRP Installed on your phone? if yes I think that this method will be useful for you
Click to expand...
Click to collapse
I'm doing it right now, but when i try to extract the backup, I get: Data error: recovery.log.. :/
NetfariousIntent said:
[/COLOR]
I'm doing it right now, but when i try to extract the backup, I get: Data error: recovery.log.. :/
Click to expand...
Click to collapse
Yes I know same thing occurred to me just ignore it the MD5 checks of the files are OK
RAR1991 said:
Yes I know same thing occurred to me just ignore it the MD5 checks of the files are OK
Click to expand...
Click to collapse
Getting command not allowed after restoring the backup. lol
NetfariousIntent said:
Getting command not allowed after restoring the backup. lol
Click to expand...
Click to collapse
where are you getting this message fastboot or in twrp?
RAR1991 said:
where are you getting this message fastboot or in twrp?
Click to expand...
Click to collapse
fastboot
NetfariousIntent said:
fastboot
Click to expand...
Click to collapse
but after restoring the backup from twrp you don't have to go infastboot mode just let it boot to the system
RAR1991 said:
but after restoring the backup from twrp you don't have to go infastboot mode just let it boot to the system
Click to expand...
Click to collapse
It says I should flash stock recovery again. alright then.
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
Okay, now it boots itself into eRecovery.
NetfariousIntent said:
It says I should flash stock recovery again. alright then.
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
Okay, now it boots itself into eRecovery.
Click to expand...
Click to collapse
I don't recommend to install the stock recovery.
is your phone booting to the system after the restoration or not?
RAR1991 said:
I don't recommend to install the stock recovery.
is your phone booting to the system after the restoration or not?
Click to expand...
Click to collapse
Nope.
It's booting to eRecovery.
NetfariousIntent said:
Nope.
It's booting to eRecovery.
Click to expand...
Click to collapse
you have restored all partitions ecxept oeminfo and version or not?
try to do a full Data wipe with twrp and reinstall root from the folder in the link with adb sideload on twrp and reboot
RAR1991 said:
you have restored all partitions ecxept oeminfo and version or not?
try to do a full Data wipe with twrp and reinstall root from the folder inth link with adb sideload on twrp and reboot
Click to expand...
Click to collapse
I have restored all partitions lol
full data wipe means wipe data or format data?
NetfariousIntent said:
I have restored all partitions lol
full data wipe means wipe data or format data?
Click to expand...
Click to collapse
I mean format, I think you should put back your original oeminfo at least
Related
admin please delete this thread. Thanks!
delete
Thank you for the great help. I have a question, can you guide me with the steps to flash the files?
Sammy_S said:
Thank you for the great help. I have a question, can you guide me with the steps to flash the files?
Click to expand...
Click to collapse
You have adb drivers? if yes proceed to next step, if no, install them (google it)
Copy system, boot, recovery, cust to adb folder
Open a cmd with shift+ right click
Enter fastboot with volume down+power
Enter the commands from above... that's it i think...(just woke up so maybe forgot something)
Yes I have.
Sammy_S said:
Yes I have.
Click to expand...
Click to collapse
hit me on private if you need more help... if you succeed post in the thread... good luck
snapdesign, thank you again for the help and the support you provided here and through the private messages.
Sammy_S said:
snapdesign, thank you again for the help and the support you provided here and through the private messages.
Click to expand...
Click to collapse
did you succeed?
No I didn't because I don't have any working rom. I extracted the system files from two different roms but it didn't work.
I guess I'll wait for huawei to release the stock rom.
Sammy_S said:
No I didn't because I don't have any working rom. I extracted the system files from two different roms but it didn't work.
I guess I'll wait for huawei to release the stock rom.
Click to expand...
Click to collapse
try with stock recovery and updaye.app in dload folder
I did. I used sd card. but when I enter recovery, only 3 options are there. 'reboot system now', wipe data/factory reset' and 'wipe cache partition'. When I select factory reset, it starts processing for 5-6% then it stop.
Sammy_S said:
I did. I used sd card. but when I enter recovery, only 3 options are there. 'reboot system now', wipe data/factory reset' and 'wipe cache partition'. When I select factory reset, it starts processing for 5-6% then it stop.
Click to expand...
Click to collapse
something is very wrong on your end...
Sammy_S said:
I did. I used sd card. but when I enter recovery, only 3 options are there. 'reboot system now', wipe data/factory reset' and 'wipe cache partition'. When I select factory reset, it starts processing for 5-6% then it stop.
Click to expand...
Click to collapse
Did you create a "dload" folder in your sd? If not, do it and paste in this new folder only the "update.app" file (once extracted the whole rom) and try again, you have to restart the phone pushing both vol+,vol- and power buttons. I forgot doing this and finally it worked!
Enviado desde mi HUAWEI VNS-L31 mediante Tapatalk
---------- Post added at 11:06 PM ---------- Previous post was at 10:45 PM ----------
Here is the link: https://mega.nz/#F!N49UgYSb!yJB-a_O4YABQe2i-_lD58w you have to download the "update.zip" and then extract the file "update.app"
thanks to @Disadamsdsdnts
from htcmania
Enviado desde mi HUAWEI VNS-L31 mediante Tapatalk
Jiji,
Thank you so much. I did the same process but it didn't work. I will try the update.app file which you gave. I hope it will work.
Sammy_S said:
Jiji,
Thank you so much. I did the same process but it didn't work. I will try the update.app file which you gave. I hope it will work.
Click to expand...
Click to collapse
Let me know if it works ?
Enviado desde mi HUAWEI VNS-L31 mediante Tapatalk
Sammy_S said:
Jiji,
Thank you so much. I did the same process but it didn't work. I will try the update.app file which you gave. I hope it will work.
Click to expand...
Click to collapse
that is for L31... you have L21 right?
snapdesign said:
that is for L31... you have L21 right?
Click to expand...
Click to collapse
Yes I have VNS-L21. I have tried both.
Sammy_S said:
Yes I have VNS-L21. I have tried both.
Click to expand...
Click to collapse
that was for L31... what was your last working firmware? try to extract from that update.app with huawei extractor system.img..
snapdesign said:
that was for L31... what was your last working firmware? try to extract from that update.app with huawei extractor system.img..
Click to expand...
Click to collapse
That's the thing. I don't have a last working firmware.
Sammy_S said:
That's the thing. I don't have a last working firmware.
Click to expand...
Click to collapse
try this... so just system don't work?
Another reason for this error is if you have device encryption enabled. In order to restore factory image, you first need to format /data to remove encryption.
I have no idea why this causes the error "cannot load system.img", but it definitely does.
Click to expand...
Click to collapse
also try this:
I faced the same error. Error cannot load system.img. I figured it out after few attempts and a few images. It turns out I had an older version of ADB and I could only install old factory images.
Click to expand...
Click to collapse
If you want to install Android Marshmallow, make sure to install the latest ADB version.
Can Anyone Upload A TWRP Backup For PRA-LA1 OR PRA-LX1 ?!
Cause My Device Is Bricked And I Can't Boot Or Use It Anymore !
So,Can Anyone Upload The TWRP Backup As Fast As Possible !?
I Want These From The Backup:-
Boot
Cache
Cust
OEMinfo (if it's PRA-LA1C185B120)
Data
System
Vendor
Product
Version
@haky86
@ChinHon
Can Anyone Of You Make A TWRP Backup For Me,Please ?!
I Need It A.F.A.P !
Here is a complete TWRP backup of the B100. Then make updates OTA, or with the Firmwarefinder.
ChinHon said:
Here is a complete TWRP backup of the B100. Then make updates OTA, or with the Firmwarefinder.
Click to expand...
Click to collapse
Thanks For The Help.
I'll Try It And Report Back.
:laugh:
ChinHon said:
Here is a complete TWRP backup of the B100. Then make updates OTA, or with the Firmwarefinder.
Click to expand...
Click to collapse
It Locked My Bootloader
And Keeps Booting To eRecovery
So, Tomorrow I'll Try To Unlock The Bootloader
And Make Factory Reset From The Stock Recovery
Then Flash The TWRP RECOVERY
Otherwise Thank You
I Think It'll Work After I Do This
Press and hold vol.+ and vol.- and power to the device restarts. Now an update process begins with 5% breaks off. Now chooses in the menu the Reboot.
---------- Post added at 20:56 ---------- Previous post was at 20:53 ----------
The Bootloader Unlocking automatically makes the Factoryreset.
ChinHon said:
Press and hold vol.+ and vol.- and power to the device restarts. Now an update process begins with 5% breaks off. Now chooses in the menu the Reboot.
---------- Post added at 20:56 ---------- Previous post was at 20:53 ----------
The Bootloader Unlocking automatically makes the Factoryreset.
Click to expand...
Click to collapse
I Tried The Update Thing Didn't Work For Me !
But I'll Try And Unlock The Bootloader !
ChinHon said:
Press and hold vol.+ and vol.- and power to the device restarts. Now an update process begins with 5% breaks off. Now chooses in the menu the Reboot.
---------- Post added at 20:56 ---------- Previous post was at 20:53 ----------
The Bootloader Unlocking automatically makes the Factoryreset.
Click to expand...
Click to collapse
But Can You Give Me Your Bootloader Unlock Code ?!
Cause I Can't Obtain Any Information With The Phone Bootlooping To eRecovery !
The code must fit to the IMEI. Get him by DC Unlocker Client.
ChinHon said:
The code must fit to the IMEI. Get him by DC Unlocker Client.
Click to expand...
Click to collapse
I Unlocked The Bootloader
Then My Device Goes To Error Mode And Says
"Update System Again"
Error!
Error NO : Load Failed
Fastboot Doesn't Do Any Thing At All
And When I Reboot It It Goes To Error Mode Again And Again
Flash now a Recovery.
https://forum.xda-developers.com/p8...-to-root-huawei-p8-lite-2017-android-t3582179
ChinHon said:
Flash now a Recovery.
https://forum.xda-developers.com/p8...-to-root-huawei-p8-lite-2017-android-t3582179
Click to expand...
Click to collapse
I Can't Flash Anything Cause It's In Error Mode!
When I Enter:-
Fastboot Flash Recovery Pargue.img
It Says:-
Waiting For Device
And Doesn't Do Anything At All !
YSFYoussef480 said:
I Can't Flash Anything Cause It's In Error Mode!
When I Enter:-
Fastboot Flash Recovery Pargue.img
It Says:-
Waiting For Device
And Doesn't Do Anything At All !
Click to expand...
Click to collapse
Take another USB cable and/ or another PC USB port. First connect, then restart the Device with key combi in the bootloader.
ChinHon said:
Take another USB cable and/ or another PC USB port. First connect, then restart the Device with key combi in the bootloader.
Click to expand...
Click to collapse
Tried It
Didn't Work
You do not come to the Recovery also any more?
ChinHon said:
You do not come to the Recovery also any more?
Click to expand...
Click to collapse
Yes But I Let The Device To Drain The Battery Then I Flashed The TWRP Recovery And Flashed The Stock Boot Image After I Flash It It Has A Problem It Goes To eRecovery All The Time But When I Flash The Rooted Boot Image It Boots But I Can't Go To DEV Options Or The Security In Settings
Make now the update from the instructions on the B110. Then everything becomes good.
ChinHon said:
Make now the update from the instructions on the B110. Then everything becomes good.
Click to expand...
Click to collapse
Can You Send Me A TWRP Backup Of Your Current Stock Boot Partition ?!
The restore from the TWRP backup seldom succeeds. Better flash by ADB or Rashr Flash tool apk.
https://mega.nz/#!Flk20Tga!-oQ6I630JHr167R9WfUS7n-zkS2T4ZRf4qtSDZMPkpQ
ChinHon said:
The restore from the TWRP backup seldom succeeds. Better flash by ADB or Rashr Flash tool apk.
https://mega.nz/#!Flk20Tga!-oQ6I630JHr167R9WfUS7n-zkS2T4ZRf4qtSDZMPkpQ
Click to expand...
Click to collapse
I Meant A TWRP Backup For Your Current Stock Boot Partition !!
Not An Image Because It Doesn't Work At All !!
So, Please Can You Send Me A TWRP Backup Of Your Current Boot Partition !!
Or If You Gave Me The TWRP Backup Of The Whole B110 It Will Be Much Appreciated !!
Everything what I can offer is in #2. This is a complete backup without datapartition.
Hello!
For quite a while I've been having the PRA-LX1C432B106 with no OS. I have been searching the XDA forums for possible solutions and have tried Sir ChinHon's unbricking tutorial and many others. Unfortunately, my System partition is only 1921MB, which means I cannot restore that partition with the available ones, as I receive Error: 255 (extractTarFork() process ended with ERROR: 255 whenever the restored size gets close to the maximum size of my partition).
If anyone could help me with this, it would be so much appreciated!
UPDATE: Solved by using K-Rom!
theholycutu said:
Hello!
For quite a while I've been having the PRA-LX1C432B106 with no OS. I have been searching the XDA forums for possible solutions and have tried Sir ChinHon's unbricking tutorial and many others. Unfortunately, my System partition is only 1921MB, which means I cannot restore that partition with the available ones, as I receive Error: 255 (extractTarFork() process ended with ERROR: 255 whenever the restored size gets close to the maximum size of my partition).
If anyone could help me with this, it would be so much appreciated!
Click to expand...
Click to collapse
answer this few questions:
is your bootloader unlocked?
is your frp unlocked?
can you access recovery?
did you wipe the vendor and cust partitions?
do you have the update.app for your device?
Sent from my PRA-LA1 using Tapatalk
brother i was faced that error and i solve it check this link https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/error-255-t3654981
hamzio7 said:
answer this few questions:
is your bootloader unlocked?
is your frp unlocked?
can you access recovery?
did you wipe the vendor and cust partitions?
do you have the update.app for your device?
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
My bootloader is unlocked, frp unlocked, I can access recovery, I restored vendor and cust partitions using some twrp restores and I know that with the vendor partition i had an error which was solved by changing the file system to EXT4 and i think it was wiped and no, i can't find the update.app on the firmware finder or for that matter on the internet.
Al-Jalodi said:
brother i was faced that error and i solve it check this link https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/error-255-t3654981
Click to expand...
Click to collapse
I saw and read your thread and tried to do what you said but I am still facing the same error
theholycutu said:
I saw and read your thread and tried to do what you said but I am still facing the same error
Click to expand...
Click to collapse
brother , did you wipe data ? so wipe data then do like i mentioned before
Al-Jalodi said:
brother , did you wipe data ? so wipe data then do like i mentioned before
Click to expand...
Click to collapse
I wiped data, unmounted, mounted, tried to restore backup and I still have that error. And I think it's because I do not have enough space on the System partition, I don't think it has anything to do with the data partition. Thanks a lot for the suggestion, though
theholycutu said:
I wiped data, unmounted, mounted, tried to restore backup and I still have that error. And I think it's because I do not have enough space on the System partition, I don't think it has anything to do with the data partition. Thanks a lot for the suggestion, though
Click to expand...
Click to collapse
so do factory rest then redo the steps because i do factory rest from TWRP (that option ask you to type yes ) so try it bro and tell me
Good luck
Al-Jalodi said:
so do factory rest then redo the steps because i do factory rest from TWRP (that option ask you to type yes ) so try it bro and tell me
Good luck
Click to expand...
Click to collapse
Thank you, but still no progress.. I still get that error 255 when trying to restore
theholycutu said:
Thank you, but still no progress.. I still get that error 255 when trying to restore
Click to expand...
Click to collapse
which backup you trying to restore ? the old backup or b170 backup ?
Al-Jalodi said:
which backup you trying to restore ? the old backup or b170 backup ?
Click to expand...
Click to collapse
I haven't tried the b170 one. It was the b110 to update to b164
theholycutu said:
I haven't tried the b170 one. It was the b110 to update to b164
Click to expand...
Click to collapse
so try the new backup https://mega.nz/#!4hlFUQwL!LoiK5wE4tfxJpAemqb9kQgIy-qUmkFgdfWeV_BJqbVU
and check this thread by ChinHon
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/how-to-root-2017-family-huawei-honor-geraete-der-reihe-pra-prague-android-7-0-emui-5-0.823799.html
Al-Jalodi said:
so try the new backup https://mega.nz/#!4hlFUQwL!LoiK5wE4tfxJpAemqb9kQgIy-qUmkFgdfWeV_BJqbVU
and check this thread by ChinHon
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/how-to-root-2017-family-huawei-honor-geraete-der-reihe-pra-prague-android-7-0-emui-5-0.823799.html
Click to expand...
Click to collapse
I tried that backup..and it's actually so close, but still not working. The system restore has 2083 MB while my system partition has 1921MB..
theholycutu said:
I tried that backup..and it's actually so close, but still not working. The system restore has 2083 MB while my system partition has 1921MB..
Click to expand...
Click to collapse
sorry brother i do not understand what do you mean , so you mean you are confused because system size partition ?
maybe it's have nano Gapps or micro Gapps and few stock app like HiCare , tripadvisor ,....etc
Al-Jalodi said:
sorry brother i do not understand what do you mean , so you mean you are confused because system size partition ?
maybe it's have nano Gapps or micro Gapps and few stock app like HiCare , tripadvisor ,....etc
Click to expand...
Click to collapse
Okay, let me explain better. When I go in TWRP into Wipe and Advanced Options and I check the System Partition, it shows me that i have 1921MB Total. I tried to restore that backup and it gave me the error. Went to restore only the system partition and I saw it had over 2000MB. And that is the cause of the error. I would need a backup with less. I don't know why my System Partition is so small and I can't resize it or something.
theholycutu said:
Okay, let me explain better. When I go in TWRP into Wipe and Advanced Options and I check the System Partition, it shows me that i have 1921MB Total. I tried to restore that backup and it gave me the error. Went to restore only the system partition and I saw it had over 2000MB. And that is the cause of the error. I would need a backup with less. I don't know why my System Partition is so small and I can't resize it or something.
Click to expand...
Click to collapse
First make a factoryreset in the stock recovery. Then in TWRP wipe data and system and restore the rescue rom. Or take the K-Rom V.3.1.
ChinHon said:
First make a factoryreset in the stock recovery. Then in TWRP wipe data and system and restore the rescue rom. Or take the K-Rom V.3.1.
Click to expand...
Click to collapse
Did everything but using the ROM. Waiting for the release of the updated download
ChinHon said:
First make a factoryreset in the stock recovery. Then in TWRP wipe data and system and restore the rescue rom. Or take the K-Rom V.3.1.
Click to expand...
Click to collapse
I got it to work by using the K-Rom v3!!!! Waiting for the 3.1! Thank you so much man, you are a god! <3
The K-Rom V.3.2 is ready and is now extensively tested. If everything goes well it comes Sunday night online. This Rom is however a complete firmware with all partitions, also data.
MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
hw to install
Waleedaligomaa said:
hw to install
Click to expand...
Click to collapse
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Where L09 ..??
Sent from my MHA-L09 using XDA-Developers Legacy app
ante0 said:
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
That was some journey to the dark side. Welcome back.
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload. Then rebrand back to L29C432 using Hwota. It's currently the only free way of rolling back to Nougat.
ante0 said:
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload.
Click to expand...
Click to collapse
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
albertobom said:
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
Click to expand...
Click to collapse
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
ante0 said:
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
Click to expand...
Click to collapse
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
jaimeguate said:
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Nothing special really just want to know if I can go back if I have to. ?
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
Oeminfo in this thread: https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 can be restored as a backup. That's probably the easiest way.
Alternative, copy and flash using dd.
cp /external_sd/MHA-AL00C00. bin /tmp/oeminfo.bin
dd if=/tmp/oeminfo.bin of=/dev/block/sdd5
5[Strogino said:
;74268268]MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
Click to expand...
Click to collapse
Hi bro can you send me oeminfo of chinese version of p8 lite 2017/honor 8 lite????
I want to rebrand my phone
ante0 said:
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
seniga1 said:
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
Click to expand...
Click to collapse
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
flash recovery_ramdisk twrp.img
That did the trick, really appreciated, you'r my new hero :highfive:
Oreo updates
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
You should be able to get updates if you are on the Oreo beta, update checks for stock recovery and won't update if you are on a custom or patched recovery, system update would just see you as updating from beta to release version, beta and release versions are both official ROMs so I don't think you would have any issues with updating as long as the device brand is the same.
plz help sir
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
jaldi said:
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
Click to expand...
Click to collapse
You do have Oreo, right?
TWRP should fail to install if you don't have Oreo (unless you're flashing it to recovery and not recovery_ramdisk).
But it sounds to me like it's not installing at all, since you're ending up in stock recovery.
Make sure you use "fastboot flash" , not "fastboot boot"
I am using the Indian model. I wanted to go back to 103.5 from 11.0.1 so I flashed the 10.3.5 zip but then I got stuck in a recovery loop and all the folders were encrypted. TWRP didn't ask for the pattern. I then flashed fastboot rom with the save user data option but the phone now is stuck rebooting to stock recovery.
Please tell me what to do, I don't want to lose my data. If I can somehow decrypt I can use my twrp backup to restore but if I wipe everything then I will lose that too. What to do
I don't think you have a chance of getting the backup back. But wait for others to tell you of there is a way
Sent from my Redmi K20 Pro using Tapatalk
ishaqtkr said:
I don't think you have a chance of getting the backup back. But wait for others to tell you of there is a way
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
how do I know if the fastboot rom I downloaded is ok, it paused a couple of times during downloading, does it give an error if its not ok. Is it certain that the phone will work if I select clean all? I don't want to do it if there is any other option
gwenmillett said:
how do I know if the fastboot rom I downloaded is ok, it paused a couple of times during downloading, does it give an error if its not ok. Is it certain that the phone will work if I select clean all? I don't want to do it if there is any other option
Click to expand...
Click to collapse
Yes it should bring error if the file is corrupted. Regarding if it will work with fastboot clean all, YES it will, if that's the only solution then get the fastboot ROM and flash it with mitool, as you may know, don't select CLEAN ALL AND LOCK, only CLEAN ALL
Sent from my Redmi K20 Pro using Tapatalk
---------- Post added at 05:42 PM ---------- Previous post was at 05:42 PM ----------
From where did you get the fastboot ROM?
Sent from my Redmi K20 Pro using Tapatalk
ishaqtkr said:
Yes it should bring error if the file is corrupted. Regarding if it will work with fastboot clean all, YES it will, if that's the only solution then get the fastboot ROM and flash it with mitool, as you may know, don't select CLEAN ALL AND LOCK, only CLEAN ALL
Sent from my Redmi K20 Pro using Tapatalk
---------- Post added at 05:42 PM ---------- Previous post was at 05:42 PM ----------
From where did you get the fastboot ROM?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I used http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
Do they do anything different at the service center, will they be able to save my data?
Your data is gone. Even Service Center can't help you.
Use miflash tool to flash official recovery rom.
gwenmillett said:
I am using the Indian model. I wanted to go back to 103.5 from 11.0.1 so I flashed the 10.3.5 zip but then I got stuck in a recovery loop and all the folders were encrypted. TWRP didn't ask for the pattern. I then flashed fastboot rom with the save user data option but the phone now is stuck rebooting to stock recovery.
Please tell me what to do, I don't want to lose my data. If I can somehow decrypt I can use my twrp backup to restore but if I wipe everything then I will lose that too. What to do
Click to expand...
Click to collapse
If you have the same 11.0.1 recovery rom somewhere, then try to remove the compatibility.zip from it and flash it from flash drive after mounting it in TWRP. I think that way, you'll get back to Miui where you can take your data back up.
rajumack07 said:
If you have the same 11.0.1 recovery rom somewhere, then try to remove the compatibility.zip from it and flash it from flash drive after mounting it in TWRP. I think that way, you'll get back to Miui where you can take your data back up.
Click to expand...
Click to collapse
you're a life saver! this worked. but the data is still encrypted, all the files are gibberish
gwenmillett said:
you're a life saver! this worked. but the data is still encrypted, all the files are gibberish
Click to expand...
Click to collapse
Try adding a security pin in miui and then go to twrp, it should ask for the same pin and then after you get in, you should see your files (just guessing) . But to keep your data encrypted, AFAIK, only way to flash another rom is through flash drive.
rajumack07 said:
Try adding a security pin in miui and then go to twrp, it should ask for the same pin and then after you get in, you should see your files (just guessing) . But to keep your data encrypted, AFAIK, only way to flash another rom is through flash drive.
Click to expand...
Click to collapse
Tried that, didn't work. Had to factory data reset in the end
gwenmillett said:
Tried that, didn't work. Had to factory data reset in the end
Click to expand...
Click to collapse
Share all the steps you're doing considering you are in miui and wanted to flash.
rajumack07 said:
Share all the steps you're doing considering you are in miui and wanted to flash.
Click to expand...
Click to collapse
I flashed 10.3.5 over 11. 0.1 but didn't wipe data. That made it bootloop to recovery
gwenmillett said:
I flashed 10.3.5 over 11. 0.1 but didn't wipe data. That made it bootloop to recovery
Click to expand...
Click to collapse
When you want to revert back to an earlier major version of MIUI, it is recommended to flash a fastboot ROM using the Mi Flash Tool and using the 'clean all' flash option.