Hello, I need help with my OPX.
I cannot enter Android or recovery, only Fastboot. Also, Fastboot on my PC can detect my device, but ADB cannot.
I had CM 13 and TWRP 3.0.2.0 installed on it, and now I was going to install LineageOS 14.1. I was first going to update TWRP to 3.0.3.0 because I thougt why not. I installed the new version with TWRPs image flashing and then it rebooted itself to Android. Then I was going to enter recovery again to install Lineage, the problem was that I couldn't even start the recovery. So now I tried to install TWRP with Fastboot, but it told me that the bootloader was locked which I thought was strange since I had unlocked it before.
So I tried to unlock the bootloader with Fastboot using "fastboot oem unlock" which it reported that it did and now I couldn't even enter Android.
But when I use "fastboot oem device-info", it says false to both unlocked and tampered and I still couldn't flash or boot into a recovery with Fastboot.
So now I can only boot into Fastboot Mode.
EDIT 2: Never mind, I fixed it with https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Can I remove this thread somehow?
You needed to flash OOS3 ROM or system partion before flashing 3.0.3 and Lineage
Yepp, I noticed. Found out later that it was because of the older bootloader. I had no idea about that before.
Hi all,
Currently running Oreo (via OldDroid manual update) then LOS 15.1 (Berkley unofficial) on top, which is great but would like NFC, buttons, flashlight.
What is the best method to reinstate this functionality? I have tried the rollback for OldDroid rollback to no avail. I believe this method assumes you are rooted, which i am not.
Happy to be on EMUI 5 if necessary as i believe i can now update to Oreo OTA.
Cheers
Can i provide further pertinent information or ask elsewhere to get replies?
What did you do in the fist place to go from stock oreo to LOS 15.0 ; any links ?
Thank you.
I flashed the system image using "fastboot flash system system.img" via article https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/
Cheers
I think, once unrooted, you'll have to flash back stock system.
oslo83 said:
I think, once unrooted, you'll have to flash back stock system.
Click to expand...
Click to collapse
Great, thank you. I am not rooted so I extracted the system.img from STF-L09SC432B360a (from http://pro-teammt.ru/firmware-database/?firmware_model=STF-L09&firmware_page=0) using this guide https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
Then using that stock emui 8 system image:
"fastboot flash system system.img"
I receive the following error:
error: cannot load 'SYSTEM.img'
Any ideas?
Cheers
Another attempt at system.img extract using my windows box and the windows software referred to in https://forum.xda-developers.com/mat...files-t3756733.
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
I performed this reset and device booted to TWRP some commands took place but too quick (saw selinux buts thats it). Device rebooted twice then loaded Huawei eRecovery where the only option is :
Download latest version and recovery
Restore system with wifi
Entered wifi details
Getting package info from server
Getting package info failed.
Booting into TWRP the 'Factory Reset' option performs the same process that i saw when Huawei eRecovery recommended the factory data reset. Some i'm confident in what happened at that point now. Unsure as to what to try at this point. The phone does not boot into EMUI and will only boot to Huawei eRecovery.
The bootloader is unlocked, as per the process to install LineageOS 15.1 in the link in the OP. I've not checked if its still unlocked, but guess that could be causing a problem?
Just checked and bootloader is unlocked.
Interestingly the process to re lock it from the Huawei site (https://emui.huawei.com/en/unlock_step) shows that you have to use the same command to lock the bootloader as to lock it again:
Note: to re-lock the bootloader after unlocking it, restore the device’s software to the Huawei official version using a microSD card then switch the device to fastboot mode and enter “fastboot oem unlock ****************” in the computer’s command prompt, where * refers to the 16-digit unlock password. The device will then restart, and the bootloader lock status will change to “Bootloader Lock State: RELOCKED”.
If i follow those instructions i get the below error:
Code:
fastboot oem unlock **************** <-my 16 digit code
...
FAILED (remote: already fastboot unlocked)
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Thanks. So I can leave the boot loader unlocked at this point and run stock emui? I'll flash stock recovery. Perhaps that will suggest factory reset and then I'll be able to boot.
Thanks again.
oslo83 said:
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Click to expand...
Click to collapse
In order to revert to the stock recovery is it necessary to flash all three recovery images from the update.app file? :
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Looking at flashing the recovery_ramdisk image with the stock version i have extracted using the below:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Noticed the stock recovery_ramdisk i extracted has a filename of 'RECOVERY_RAMDIS.img', not ending in 'K' for 'RAMDISK. Presumably i can simply rename my recovery_ramdisk to "RECOVERY_RAMDISK.img" unless a 15 character filename is a limitation, or adjust my fastboot command to :
Code:
fastboot flash recovery_ramdisk RECOVERY_[B]RAMDIS[/B].img
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
mightyjcb said:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
Click to expand...
Click to collapse
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
oslo83 said:
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
Click to expand...
Click to collapse
Many thanks @oslo83 followed that and just as you said hardware functioning correctly once again!
One further question for future reference, am i now in a position to apply OTA updates when released?
Cheers
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
mightyjcb said:
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
Click to expand...
Click to collapse
You need to flash stock recovery and do a factory reset in stock recovery.
oslo83 said:
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
Click to expand...
Click to collapse
Great, i should be able to meet this criteria quite easily then :
+ I've never rooted the device
+ I have reverted to stock recovery
+ I flashed the stock kernel over the top of the button fix kernel mentioned earlier in this thread.
Thanks again for your help, much appreciated.
zxz0O0 said:
You need to flash stock recovery and do a factory reset in stock recovery.
Click to expand...
Click to collapse
That seemed to do the trick! Ta.
Hi guys!
I was relocking my bootloader on my Huawei P20 Lite and now it isn't booting at all. It goes to the eRecovery screen and that's it.
I tried reverting what I've done, but now the FRP lock is preventing me from executing any fastboot commands from my PC.
Does anyone know what to do?
Why you decided to do that? To avoid initial screen, your device has been unlocked and can't be trusted...
Did you do any kind of modification in the partitions before relock bootloader?
I had done something similar and could not do anything anymore by the frp lock,
I have downloaded the ROM from this link, (make sure this rom is for ure model of phone)
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
then I used this
https://www.dc-unlocker.com/file-list/DC-unlocker_softwares/DC_Phoenix/DC_Phoenix_v52.rar.html
and I paid 15€ ( to use the dc app ) to flash update.app even though there is frplock they can get around this.
it costs money but that's how my p20 works
I have not found a free way yet
why did you paid for that?
I did it myself, factory reset then I simply flashed the stock system. IMG and did a fastboot relock...
Who did you paid?
mchtt said:
why did you paid for that?
I did it myself, factory reset then I simply flashed the stock system. IMG and did a fastboot relock...
Who did you paid?
Click to expand...
Click to collapse
@mchtt can you post the instruction on how to flash from the China version to the international version.
I downloaded the system.img file you uploaded but have no idea how to use it - create update.app and drag the system.img file in there?
Thanks ahead of time.
You should not continue of you don't know how to use files, flashing phone is not as easy we think.
First, you be to provide informations, what's your phone ID, your rom version, and what did you do exactly to your phone ?
My system.img was extracted from the stock update.app version P20 Lite ANE-LX1-C432.
U can simply flash it:
Fastboot flash system system.img
But before or after is mandatory to do a factory reset or full wipe.
It will reset your phone to stock and you will be able to re-lock the bootloader with fastboot if it's not done already.
mchtt said:
why did you paid for that?
I did it myself, factory reset then I simply flashed the stock system. IMG and did a fastboot relock...
Who did you paid?
Click to expand...
Click to collapse
My phone was in a bootloop and there was no recovery and there was no way to factory reset..
To flash img file u need frp unlock and mine was locked
Update on the situation: I sent the device to the atores warranty and they swapped it straight away. Got lucky this time
Salutations!
I accidentally flashed a new recovery.img into my ramdisk partition and now my custom recovery won't boot.
Any suggestions?
Running MorFuZ by Catuva21, EMUI 8.0.0 and it has the OEM unlocking greyed out so can't flash another using Fastboot as it results in a CMD error.
I have extensively searched this forum and couldn't find to answers to the following!
Looking for experts to guide..
Query #1: TWRP Backup of Stock ROM causes bootloop!
I had unlocked Bootloader of Redmi Note 4 and used temporary TWRP (fastboot boot twrp.img) to take a backup of stock ROM and found that the device cannot boot back into Stock ROM.
I had tried to restore 'boot.img' using the TWRP stock ROM backup (and also from downloaded stock ROM) but that didnt help.
Same problem seen in Redmi 4 as well.
When booted to TWRP using fastboot boot (without flashing), in which partition TWRP is stored (boot or cache)?
After I had booted into TWRP (without flashing), is the backup of boot partition that I took still a stock version one?
Query #2: Relocking and unlocking Bootloader
I had unlocked bootloader using the MiFlash unlock tool (miflash_unlock-en-3.5.1108.44).
If I relock the bootloader using the MiFlash tool, would I need MiFlash unlock tool again to unlock or would 'fastboot flashing unlock' work?
Thank you!
n.dnivra said:
I have extensively searched this forum and couldn't find to answers to the following!
Looking for experts to guide..
Query #1: TWRP Backup of Stock ROM causes bootloop!
I had unlocked Bootloader of Redmi Note 4 and used temporary TWRP (fastboot boot twrp.img) to take a backup of stock ROM and found that the device cannot boot back into Stock ROM.
I had tried to restore 'boot.img' using the TWRP stock ROM backup (and also from downloaded stock ROM) but that didnt help.
Same problem seen in Redmi 4 as well.
When booted to TWRP using fastboot boot (without flashing), in which partition TWRP is stored (boot or cache)?
After I had booted into TWRP (without flashing), is the backup of boot partition that I took still a stock version one?
Query #2: Relocking and unlocking Bootloader
I had unlocked bootloader using the MiFlash unlock tool (miflash_unlock-en-3.5.1108.44).
If I relock the bootloader using the MiFlash tool, would I need MiFlash unlock tool again to unlock or would 'fastboot flashing unlock' work?
Thank you!
Click to expand...
Click to collapse
1. That bootloop *probably* happened because you swiped the "allow modification option" in twrp.
(One more advice : in twrp backup you should backup the "system image" and "vendor image" not the "system" and "vendor", If you don't want bootloop after restoring. (Or If you got a bootloop already flash that verity removal zip)
2. You will need mi unlock again.