Database Info

stock recovery corrupted

apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed

Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
same here. did you managed to work it out?

Solved
eelc said:
same here. did you managed to work it out?
Click to expand...
Click to collapse
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.

Mass1veDynam1c said:
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.
Click to expand...
Click to collapse
can u make the total tutorial video of this whole process ???

I would ask if you could post a link to the update you used and a list of the commands you used..im in the US ..so it is honor 6x for the US

bricked honor 6x
You need three softwares
1. huawei multi tool by mt,,,,, in english version bro
2. Huawei update extractor
3. Firmware file update .zip
First extract the zip file , there you will get update.app file . Extract BOOT.IMG RECOVERY.IMG SYSTEM.IMG USER DATA.IMG using Huawei extractor software .
NOW open huawei multitool app (internet connection required)
Put all these files you extracted in unbrick folder of huawei multi tool
Follow steps to unbrick your device
Thank you..

can you send the links please....thank you!

Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
Try to flash twrp first , later flash stock recovery from twrp by clicking on flash image . Be sure u are installing a working recovery but not a corrupted one

Help. Phone Relocked. FRP Lock. No OS. No Custom Recovery.

Hello guys,
I had some problems with my Honor 6x L21 so I tried to flash new custom ROM that I didn't like in the end. I tried to revert back and found update.app method. I somehow relocked my bootloader and now tried to install update.app which fails at 5 % and says it is not compatible.
Now, I have erecovery with me that can get nothing after connecting to wifi. No update from SD Card option available.
When I try to unlock bootloader again, it fails.
Also, when I run command 'fastboot oem get-bootinfo' the following lines do come in result:
<bootloader> unlocked
OKAY [0.009s]
Finished.
However, my phone shows Phone Relocked and FRP lock.
Any help guys?

@amannan: I have a US BLN-L24, I was able to use the dload method to roll back to Marshmallow from Nougat. I'm not sure why it sometimes fails at 5%, I think Huawei recently implemented something to cause the update to fail if you haven't passed an online verification check. So basically, no upgrading offline for some of the newer firmwares, someone correct me if I'm wrong. I think it has something to do with Nougat too.
In your case, all hope isnt lost as long as you can access eRecovery and fastboot. What you need to do is find the stock MM packages for your device. This will most likely consist of a small rollback file and a much larger firmware file. Go search Huawei's downloads section on their website until you find what you need, use your model as a reference point. There should also be a PDF file with instructions in it, read it.
For each of the 2 files you get, extract the zips, make a folder called dload on your MicroSD (not internal phone storage). In my case I had to first place the update.app file from the rollback zip into the dload folder, boot to eRecovery (hold volume up and volume down, then hold Power, let let of Power when logo appears but continue to hold the other keys). From there the file will automatically flash. Then I had to extract update.app from the large firmware zip and put in dload, repeat same process again. You should be back on MM.
If either file wont flash then go download Huawei Firmware Extractor. Use it to extract boot.img and recovery.img from the rollback zip's update.app, then boot to fastboot mode while phone is powered off. Plug in a MicroUSB charger into phone then plug other end into PC.
Then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Make sure to install drivers for the phone first, just install HiSuite on Windows is easiest way. For ADB and fastboot, install '15 seconds adb fastboot" (Google it). If the terminal on your PC says something like "file not found", then either use the cd command (change directory) to move working directory to boot.img/recovery.img location, or move the files to C:\adb.
Once you're back up and booting you can then proceed to bootloader unlock, root, ROM flashing, etc.
Hope this helped!

AnonVendetta said:
@amannan: I have a US BLN-L24, I was able to use the dload method to roll back to Marshmallow from Nougat. I'm not sure why it sometimes fails at 5%, I think Huawei recently implemented something to cause the update to fail if you haven't passed an online verification check. So basically, no upgrading offline for some of the newer firmwares, someone correct me if I'm wrong. I think it has something to do with Nougat too.
In your case, all hope isnt lost as long as you can access eRecovery and fastboot. What you need to do is find the stock MM packages for your device. This will most likely consist of a small rollback file and a much larger firmware file. Go search Huawei's downloads section on their website until you find what you need, use your model as a reference point. There should also be a PDF file with instructions in it, read it.
For each of the 2 files you get, extract the zips, make a folder called dload on your MicroSD (not internal phone storage). In my case I had to first place the update.app file from the rollback zip into the dload folder, boot to eRecovery (hold volume up and volume down, then hold Power, let let of Power when logo appears but continue to hold the other keys). From there the file will automatically flash. Then I had to extract update.app from the large firmware zip and put in dload, repeat same process again. You should be back on MM.
If either file wont flash then go download Huawei Firmware Extractor. Use it to extract boot.img and recovery.img from the rollback zip's update.app, then boot to fastboot mode while phone is powered off. Plug in a MicroUSB charger into phone then plug other end into PC.
Then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Make sure to install drivers for the phone first, just install HiSuite on Windows is easiest way. For ADB and fastboot, install '15 seconds adb fastboot" (Google it). If the terminal on your PC says something like "file not found", then either use the cd command (change directory) to move working directory to boot.img/recovery.img location, or move the files to C:\adb.
Once you're back up and booting you can then proceed to bootloader unlock, root, ROM flashing, etc.
Hope this helped!
Click to expand...
Click to collapse
Dear AnonVendetta, Thank you so much for the help. I was able to use the dload method. I read somewhere that the last firmware version needs to be updated using dload method. I had B361 before it got all messed up so tried that update and it started working.
Also, the fastboot won't flash any img file since the FRP was locked somehow.
Thank you for the help

@amannan: Glad it worked out, you must have already made progress before I posted, your response was too quick.
I do believe you cant flash anything via fastboot if the bootloader is still locked.
I've only owned my Honor 6X for about 2 weeks, I've had to do an emergency recovery several times due to various issues. This is my first Huawei but I've owned many Android devices before, and rooted/custom ROMmed most of them, so I'm just a newbie to Huawei but not Android in general. I'm getting the hang of things.
Good luck!

amannan said:
Dear AnonVendetta, Thank you so much for the help. I was able to use the dload method. I read somewhere that the last firmware version needs to be updated using dload method. I had B361 before it got all messed up so tried that update and it started working.
Also, the fastboot won't flash any img file since the FRP was locked somehow.
Thank you for the help
Click to expand...
Click to collapse
Yes, dload method is the only way to restore the device in such scenario. If frp is locked then condition is worse as you can not flash anything but only dload will help you. Correct package should be flashed and will succeed.

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?

Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone

up

You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition

shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.

cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware

ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.

cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.

ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.

Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse

AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.

Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?

Bootloop and eRecovery fails, dload fails - no way to recover

Hi people,
I need some help here and I hope anybody got an idea to get my FRD-L09 (C432 - on B521 base with OpenKirin's RROS Oreo) to work again somehow.
Situation is: After a failed attempt to upgrade the firmware base to B562 my device is now bootlooping, and goes into eRecovery, after one or two tries to boot, which is then offering to "Download and recovery". That fails at getting package info ("Getting package info failed").
Next I tried to install full OTA-PV package (extracted UPDATE.APP) via dload folder on my SD - that fails at 5 % ("Software install failed!"). For this I took the service ROM from this thread (see post #24 for Oreo version) and version B521 for FRD-L09C432 from firmware finder.
I also tried to get into TWRP 3.2.0 from Huawei Multi-Tool by TeamMT but this suddenly reboots after a few seconds everytime - so this is also useless (I tried several TWRP versions I found - maybe 'bootcomplete=false'?). I hoped to flash the extracted .img files with it.
Flashing the extracted .img files (specially the vendor image, because I think I destroyed it somehow) via fastboot also fails with error "command not allowed". Replacing the eRecovery with TWRP is also not possible (not allowed).
Flashing to system, recovery_ramdisk, kernel etc. via fastboot is possible without any problems - which shows that bootloader and frp are both unlocked.
Info btw: in this few seconds in TWRP I could see that vendor partition cannot be mounted - which shows that it's likely an error on this partition.
Is there any way to flash any "other" (vendor) partition via fastboot? Or do you guys have any ideas to this what I can try - except for bringing this thing to service center for repair :silly:? And please ask, if something is not clear or I forgot to give any info.
Any help is very appreciated.

cypher187 said:
Any help is very appreciated.
Click to expand...
Click to collapse
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.

cypher187 said:
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
Click to expand...
Click to collapse
In my case eRecovery save my a*s 2 times

ScardracS said:
In my case eRecovery save my a*s 2 times
Click to expand...
Click to collapse
Usually dload did the job well for me. I don't know why it didn't in that case.
But I'm still looking for an easy way to upgrade the firmware base for future use (in case we get some) :laugh:

Next time just use HiSuite windows version with Firmware Finder's DNS trick to flash any stock ROM version what you need, only works with version 5.0.2.300. I've got the same issue and recoered by this method ease.
You can download it here.

GUIDE: eRecovery / HiSuite failing to restore - RESCUE on PIE: L29 L09 432 -- v190

WARNING
By doing this you may lose your data, this is intended for when you have nowhere else to turn to.
Back Story
Hi All,
Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
After the installation, I tried to install a bunch of ROM's, I messed up a bit.
Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.
So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.
Ton of files in there, the files i just mentioned which are all .img files and some others.
In the end i needed several to get a perfect restore which has worked every single time without fail.
As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way Yaay, also what to do and where to obtain the firmwares from my experiences.
Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.
Good luck, any questions let me know. :good:
START HERE
*NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
They require an account to be made but besides that they were faster and had more choice.
Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...
Anyway, moving on........
FILES
At the foot of this guide is a link, inside it is everything you should require in order to complete this guide
ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)
IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
Move all of them after downloading to the ADB folder in C:\ADB
CACHE.img
CUST.img
ERECOVERY_RAMDI.img
KERNEL.img
RECOVERY_RAMDIS.img
USERDATA.img
VENDOR.img
SYSTEM.img
EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.
Pre-requisites
- A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
- A device variant of either L-09 or L-29 (others may work but i have not tested)
- A device variant of c432 (the 782 may work but i have not tested)
- Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
- Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
- I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
- A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can
GUIDE
On your computer / laptop
STEP 1 Download all the files from the mega link provided.
STEP 2 Copy the ADB Folder to the root of C: so it looks like this
C:\ADB
STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.
STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear
STEP 5 In the black window type the following:
cd c:\adb then press Enter
STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows
On your Phone
STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.
On your computer / laptop
Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img
*NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
You could then press the tab key and scroll through the files in the folder.
eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img
PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash userdata USERDATA.img
fastboot flash kernel KERNEL.img
fastboot flash vendor VENDOR.img
fastboot flash system SYSTEM.img
STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.
fastboot reboot
If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190
You can then root and use your device as you see fit.
Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN )
NOTE: they actually now have, sorry
https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg
Any questions, please ask away and i'll do what i can to help

c:\ADB>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (176429 KB)...
OKAY [ 4.121s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.130s
OEM is LOCKED

@mdda7
You must have an unlocked bootloader.

titi66200 said:
@mdda7
You must have an unlocked bootloader.
Click to expand...
Click to collapse
bootloader is unlocked
but
OEM is locked

mdda7 said:
bootloader is unlocked
but
OEM is locked
Click to expand...
Click to collapse
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.

dladz said:
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
Click to expand...
Click to collapse
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108

mdda7 said:
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
Click to expand...
Click to collapse
OEM unlocking needs to be off mate, 108 shouldn't matter but i believe that it's the version that has the OEM greyed out.
There is a way around it but i'm not sure.

any way?

mdda7 said:
any way?
Click to expand...
Click to collapse
Certainly not with this method as you don't meet the pre-requisites.
That being said I suppose some kind of low level flash tool may work, like i said before a paid for service maybe?
Lets find out everything there is to know.
So your bootloader is unlocked.
Have do you have TWRP installed?
Did any of the images i've listed actually flash successfully?
Have you tried to use eRecovery? or Hi Suite (neither of these worked for me hence this guide)
Beyond that i suppose the only way would be a paid service but their pre-requisites may be the same as mine. In that case I would say you're out of luck, afaik this guide is essentially the lowest you can go. I don't believe anything will work without OEM unlocking turned on.
How do you get onto the firmware you're currently on ? 108 and what state is the phone in right now?
What works? Whats accessible?

@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.

~clumsy~ said:
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
Click to expand...
Click to collapse
Haha no worries fella.

dladz said:
Haha no worries fella.
Click to expand...
Click to collapse
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.

chrissyyyw said:
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
Click to expand...
Click to collapse
Weird. Not sure pal. This is what I did when I was stuck. Did you read everything and follow to the letter? A higher or same firmware?
On fastboot reboot the pc saying it's disconnected is correct. Should have come on.
Does anything ever come on screen?

Thank you, life saver!!

:good:
Johnny Eng said:
Thank you, life saver!!
Click to expand...
Click to collapse
You're very welcome Use the thanks button buddy :good:

dladz said:
:good:
You're very welcome Use the thanks button buddy :good:
Click to expand...
Click to collapse
Done buddy ?
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks

Johnny Eng said:
Done buddy
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Click to expand...
Click to collapse
Which FW version did you flash? I’ve got the same on .282

chrissyyyw said:
Which FW version did you flash? I’ve got the same on .282
Click to expand...
Click to collapse
As i'm still on 190 I wouldn't know this, but would it be possible that userdata isn't actually a part of the update app no more?
Seeing as it still works I would assume that is the case.

There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?

chrissyyyw said:
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
Click to expand...
Click to collapse
No because you're going to be picking them via fastboot anyway, I don't believe the name matters.
The ones in the update I used were not named like that IIRC.