Hi all!
Occasionaly flashed blue spark twrp v41 (for OOS 3.x) while on Sultans ROM with locked bootloader.
No root access, didn't flash supersu. Kingroot and other 'on one click' methods somehow don't work.
Now, when I try to use fastboot to flash recovery it denies as bootloader is locked. When I try to unlock bootloader using 'oem unlock' it tries to boot recovery which doesn't boot (stucks on logo).
Any chance to solve without hardbricked solution?
I'm on OOS 2.2.2 and have done the same thing (flashed blu spark v41)... same result as you though, a phone I can only boot into fastboot mode
This was the advice I was given (from OnePlus forums)...
https://forums.oneplus.net/threads/...lus-logo-help-me-please.462406/#post-15248530
Here are the steps to get TWRP without messing up your recovery partition
>> Grab Bootloader file (emmc_appsboot.mbn) from OxygenOS Lollypop stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
>> Now Type
fastboot reboot-bootloader
>> Now temporarily boot TWRP official recovery for OPX with fastboot
fastboot boot "yourTWRPfileNAME.img"
You should be able to boot to TWRP recovery now
After Flashing and stuff reboot to fastboot and
>> Grab Bootloader file (emmc_appsboot.mbn) from Oxygen OS Marshmallow stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
Reboot and enjoy
Click to expand...
Click to collapse
Edit: Maybe you'll need to flash the emmc_appsboot.mbn file from the Sultans ROM though???
The above didn't work for me. I had to UnBrick
You cannot install a recovery on locked bootloader,your phone is not going into stock recovery because of some boot failure, just turn off your phone remove battery if its removable then try again to go into recovery
Sent from my HUAWEI TIT-AL00 using XDA Forums
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.
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.
Hi,
So long story short, I tried to get good phone for someone for a good price, I ordered a Xiaomi Mi 10 from China - But it came with a bunch of Chinese bloatware so I wanted to flash the Global ROM and have Google on there
I added it to my Xiaomi account, unlocked the bootloader (waited 168 hours), then followed instructions from a youtube video (
)
It worked well - I used adb to flash TWRP, and was able to install the Global ROM from xiaomi.eu using TWRP (version 12-11) (filename: xiaomi.eu_multi_MI10_V12.2.9.0.RJBCNXM_v12-11)
This worked well and everything went smooth, and I thought I was done, then I wanted to remove the device from my Xiaomi account, so I did remove the device from my account via Mi Cloud, and then I went to factory reset the phone, and then it just keeps booting into Fastboot.
I tried to hold buttons to boot into TWRP (volume UP and Power) but just goes into Fastboot, I tried to flash TWRP again via adb using "fastboot flash recovery twrp.img" but am getting this error when I run "fastboot boot twrp.img" - FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Please let me know if there is anything I can do - even to get back to the chinese stock ROM
Thanks in advance
Hi all - I solved the problem by using the Global Fastboot ROM and MiFlash tool - I got a CRC error "update sparse crc list failed" but followed some advice to edit the "Flash.all" script and remove the 2 lines that contain "CRC"
Then the Flash process worked and the phone did boot into Global ROM
The xiaomieu stable version has a problem with custom recovery, so you grabbed fastboot.
if you want to use recovery, you need to boot recovery via ADB with the command fastboot boot recovery ....
Do not use on a stable version of xiaomieu recovery via the restart button to recovery
Actually, one can boot to recovery via restart button, but only after flashing the twrp 3.4.0 little turtle.
However, this recovery isn't able to decrypt the partitions, and could be used for flashing ROMs only from OTG drive.
The one that does decrypt and could be used in "normal" way is twrp 3.4.2.1206, but this one can only be booted as you said with fastboot boot recovery.img