Database Develop

*HELP!!* locked bootloader with no OS

So here's my problem...
I've accidentally wiped out entire phone (including OS)...
I still have access to TWRP, but the bootloader is locked, meaning I cannot flash stock rom (or any roms) to my phone...
I've tried to use following command:
fastboot oem unlock​but it gives me this:
<bootloader> Check 'Allow OEM Unlock' in Developer Options.​FAILED <remote failure>​
How can I check 'Allow OEM unlock' if I can't even get to the setting..?
I see others have similar issue like me but there's no solution to be found... Anyone know how to fix this problem??

prestigiousboi said:
So here's my problem...
I've accidentally wiped out entire phone (including OS)...
I still have access to TWRP, but the bootloader is locked, meaning I cannot flash stock rom (or any roms) to my phone...
I've tried to use following command:
fastboot oem unlock​but it gives me this:
<bootloader> Check 'Allow OEM Unlock' in Developer Options.​FAILED <remote failure>​
How can I check 'Allow OEM unlock' if I can't even get to the setting..?
I see others have similar issue like me but there's no solution to be found... Anyone know how to fix this problem??
Click to expand...
Click to collapse
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.

Evolution_Tech said:
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.
Click to expand...
Click to collapse
Thanks for the comment,
I've tried it and it gave me following error:
Skipping MD5 check: no MD5 file found​Error flashing zip 'sdcard/image-shamu-lmy47d.zip'​

Evolution_Tech said:
Boot into TWRP. Connect to PC. Download a ROM to your PC. Drag and drop the ROM into your internal storage. Flash ROM with TWRP. Enable oem unlock via developer options. Boot to bootloader. Fastboot oem unlock.
Click to expand...
Click to collapse
^ this. You'll still be able to flash a rom because you have twrp.

prestigiousboi said:
Thanks for the comment,
I've tried it and it gave me following error:
Skipping MD5 check: no MD5 file found​Error flashing zip 'sdcard/image-shamu-lmy47d.zip'​
Click to expand...
Click to collapse
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595

Evolution_Tech said:
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595
Click to expand...
Click to collapse
why not m? it booted fine for me via twrp, the twrp flashable version at least.

simms22 said:
why not m? it booted fine for me via twrp, the twrp flashable version at least.
Click to expand...
Click to collapse
To get him up and running with a locked bootloader, I chose to keep it simple. M would require the bootloader and radio flash and that's not happening with a locked bootloader.

Evolution_Tech said:
Are you trying to flash a factory image through TWRP? That won't work. Download a ROM (other than M preview) from the Android development section. Any custom ROM other than M.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Something like this:
http://forum.xda-developers.com/showthread.php?t=3061595
Click to expand...
Click to collapse
I love you man. Thank you for helping me (a noob)

prestigiousboi said:
I love you man. Thank you for helping me (a noob)
Click to expand...
Click to collapse
I guess that means you got it working. :victory: :good:

Evolution_Tech said:
To get him up and running with a locked bootloader, I chose to keep it simple. M would require the bootloader and radio flash and that's not happening with a locked bootloader.
Click to expand...
Click to collapse
doesnt require the radio flash, but does require the bootloader flash. I did forget though, you're right. I updated that via twrp as well. but you are very right about keeping it simple

i got excited when i found this thread. then I realized I have no recovery. this phone is seriously screwed it isn't showing any screens or anything

Stock Recovery: Lenovo K4 Note 6.0

Lenovo K4 Note: Rooted
Recovery: TWRP 3.0.2
Android Version: 6.0
Stock Rom
a7010a48_s219_160810_row
I want to encrypt my phone, but when I do it nothing happens. Screen goes black, I waited for 5hrs .. still black screen.
I rebooted normally & saw in settings that device is not encrypted.
I am guessing this is happening because of TWRP.
Can anyone please upload stock recovery for above mentioned Android version?
Thank You.

Trushant said:
Lenovo K4 Note: Rooted
Recovery: TWRP 3.0.2
Android Version: 6.0
Stock Rom
a7010a48_s219_160810_row
I want to encrypt my phone, but when I do it nothing happens. Screen goes black, I waited for 5hrs .. still black screen.
I rebooted normally & saw in settings that device is not encrypted.
I am guessing this is happening because of TWRP.
Can anyone please upload stock recovery for above mentioned Android version?
Thank You.
Click to expand...
Click to collapse
Here you go. hit thanks if helped you.

iamironman91 said:
Here you go. hit thanks if helped you.
Click to expand...
Click to collapse
Hi. Thanks for replying.
I got following error in cmd while flashing:
writing 'recovery'...
FAILED <remote: image is not a boot image>
finished.

What's the code you put in adb
fastboot flash recovery recovery.img
Is this you used?

iamironman91 said:
What's the code you put in adb
fastboot flash recovery recovery.img
Is this you used?
Click to expand...
Click to collapse
Yes

Trushant said:
Yes
Click to expand...
Click to collapse
try this

iamironman91 said:
try this
Click to expand...
Click to collapse
Not working... same error.

Enable us debugging. Paste these codes in adb
fastboot erase recovery
fastboot flash recovery recovery.img
Let me know if works
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
Before that backup everything if something goes wrong

iamironman91 said:
Enable us debugging. Paste these codes in adb
fastboot erase recovery
fastboot flash recovery recovery.img
Let me know if works
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
Before that backup everything if something goes wrong
Click to expand...
Click to collapse
Same error.
The problem is with the recovery image.
Thank you for trying to help me.
Any senior member out there? Your assistance will be very much appreciated.

:good:
These imgs are from ota of s219, s208, s147 Lollipop.
Or may be you try downloading stock firmware and flash only recovery img via sp tools.
Ofcourse any senior member will have easiest solution

iamironman91 said:
:good:
These imgs are from ota of s219, s208, s147 Lollipop.
Or may be you try downloading stock firmware and flash only recovery img via sp tools.
Ofcourse any senior member will have easiest solution
Click to expand...
Click to collapse
I tried to flash only recovery via SP Tools but it sent my phone in boot loop, had to flash whole rom to get it working again.

Trushant said:
I tried to flash only recovery via SP Tools but it sent my phone in boot loop, had to flash whole rom to get it working again.
Click to expand...
Click to collapse
Flash is ok? What android_n_setup.zip version you have?after flashing,you can boot to stock?i think note the twrp causing this..

i want stock recovery s232

can i delete TWRP after installed

Telegram link for Lenovo k4 note plzz

@k4note

iamironman91 said:
:good:
These imgs are from ota of s219, s208, s147 Lollipop.
Or may be you try downloading stock firmware and flash only recovery img via sp tools.
Ofcourse any senior member will have easiest solution
Click to expand...
Click to collapse
Bro, just ask him to unzip "recovery.zip" and then use the "recovery.img" for flashing!
Simple thing, yet eazy to miss.

TWRP Backup

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.

HELP! Soft Bricked phone!

So, I installed supersu zip on my twrp recovery and now my phone won’t boot and the screen just starts with N/A and the moto screen flashes and won’t boot up. I can’t find any moto e4 plus (xt1775 owens) firmware anywhere and any help would be appreciated. (7.1.1)

Moto E4 plus xt 1775. Firmware
danieljensen9 said:
So, I installed supersu zip on my twrp recovery and now my phone won’t boot and the screen just starts with N/A and the moto screen flashes and won’t boot up. I can’t find any moto e4 plus (xt1775 owens) firmware anywhere and any help would be appreciated. (7.1.1)
Click to expand...
Click to collapse
I have that phone, actually I soft bricked my first one the same way and managed to get another. If you can explain to me how I can get an image of it , I'd be glad to send it to you. I was just about to unlock the bootloader

autodoc88 said:
I have that phone, actually I soft bricked my first one the same way and managed to get another. If you can explain to me how I can get an image of it , I'd be glad to send it to you. I was just about to unlock the bootloader
Click to expand...
Click to collapse
if you have an unlocked bootloader and rooted device than do this in terminal emulator app
dd=if /dev/block/bootdevice/by-name/system of=/sdcard/system.img
this will backup your device system in image format.

autodoc88 said:
I have that phone, actually I soft bricked my first one the same way and managed to get another. If you can explain to me how I can get an image of it , I'd be glad to send it to you. I was just about to unlock the bootloader
Click to expand...
Click to collapse
That would be amazing. What I need is the boot.img if any of you knows how to extract it. It was corrupted by a systemless root. I believe that you can do a nandroid backup of the boot with twrp. Just to make it clear mine is the US qualcomm model. Not the mediatek. https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160 DO NOT USE fastboot flash USE fastboot boot!

danieljensen9 said:
That would be amazing. What I need is the boot.img if any of you knows how to extract it. It was corrupted by a systemless root. I believe that you can do a nandroid backup of the boot with twrp. Just to make it clear mine is the US qualcomm model. Not the mediatek. https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160 DO NOT USE fastboot flash USE fastboot boot!
Click to expand...
Click to collapse
OH WOW....thats where the problem is damn wrong partition command , i did that yesterday, feel like a idiot now... so do we have a correct boot.img? xt1775 owens.
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
neilc300 said:
OH WOW....thats where the problem is damn wrong partition command , i did that yesterday, feel like a idiot now... so do we have a correct boot.img? xt1775 owens.
Click to expand...
Click to collapse
in my own defense i was following instructions to the T ....Lol

Unlocked bootloader yes, no root.
Francesco Franz said:
if you have an unlocked bootloader and rooted device than do this in terminal emulator app
dd=if /dev/block/bootdevice/by-name/system of=/sdcard/system.img
this will backup your device system in image format.
Click to expand...
Click to collapse
I do have that device, xt 1775, I haven't been able to get a twrp image to flash ,so I can root it . If anyone has it or knows elwhere I can find it ? I'd be happy to send you the boot image

autodoc88 said:
I do have that device, xt 1775, I haven't been able to get a twrp image to flash ,so I can root it . If anyone has it or knows elwhere I can find it ? I'd be happy to send you the boot image
Click to expand...
Click to collapse
i have both boot.img and recovery.img of xt1775 but your device recovery partition is smaller.

autodoc88 said:
I do have that device, xt 1775, I haven't been able to get a twrp image to flash ,so I can root it . If anyone has it or knows elwhere I can find it ? I'd be happy to send you the boot image[/QUOTE
i can flash twrp[ but i can't boot to anything except fastboot which is way better than nothing, i flashed some boot.img using flash command instead of boot command i guess it wiped the boot partition error says failure to load kernel. so you have the device and you need the working twrp?
---------- Post added at 10:20 PM ---------- Previous post was at 10:16 PM ----------
Francesco Franz said:
i have both boot.img and recovery.img of xt1775 but your device recovery partition is smaller.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-e4-plus/development/recovery-twrp-3-1-1-moto-e4-plus-t3682180
this is the one i used and it worked i did not see the boot link there till just now im gonna try ir now. you know how to flash thru fastboot right?
Click to expand...
Click to collapse

Yes I know how to flash ,but how do I boot to recovery that's not flashed
I need more knowledge then I have at present and it blows

danieljensen9 said:
So, I installed supersu zip on my twrp recovery and now my phone won’t boot and the screen just starts with N/A and the moto screen flashes and won’t boot up. I can’t find any moto e4 plus (xt1775 owens) firmware anywhere and any help would be appreciated. (7.1.1)
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/showthread.php?t=2239421
Download the unsu script zip and flash it with twrp and then you should be able to flash Magisk v14.2 or phh's superuser. Supersu will not work with the E4 or E4 plus at the present time. Especially not the system install versions.
---------- Post added at 08:23 AM ---------- Previous post was at 08:12 AM ----------
autodoc88 said:
I need more knowledge then I have at present and it blows
Click to expand...
Click to collapse
Open a terminal in whatever folder you have the recovery on your pc and you can boot the recovery with
Code:
fastboot boot recovery twrp.img (or what ever the recovery is named)
this will boot your device to the recovery instead of flashing the recovery to the device. You can use the recovery just the same as if it were installed.

bricked
My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help

danieljensen9 said:
So, I installed supersu zip on my twrp recovery and now my phone won’t boot and the screen just starts with N/A and the moto screen flashes and won’t boot up. I can’t find any moto e4 plus (xt1775 owens) firmware anywhere and any help would be appreciated. (7.1.1)
Click to expand...
Click to collapse
You probably need to flash a no-verity-opt-enctypt.zip and retry booting.
Here's the original Back to stock thread;
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441

[ROM] Service ROMs

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"