I (seemingly) successfully unlocked my Realme's bootloader yesterday, I even managed to get into the bootloader through the DeepTest app, flash TWRP and get into it, but after resetting the phone, the recovery got overwritten by the stock one and now I cannot get into fastboot by any means.
adb reboot bootloader only displays a message for a split second and then reboots into OS again. Which happened before as well.
However, the DeepTest app doesn't show the Check query button (through which I could get into the fastboot) anymore and the only other button there is Apply to exit in-depth test which only displays You can apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode, but tapping on Ok doesn't do anything.
The phone still seems to be working (even fp sensor), I just cannot get into fastboot.
I've also tried flashing the EU (A.54) build to the B.63 build, nothing changed.
How do I resolve this?
/EDIT: I should also mention that after the first wipe (right after confirming bootloader unlock) the DeepTest app was still working as intended, however after the custom recovery was overwritten by the stock one, it started misbehaving as written above. Wiping the internal storage again (through recovery) didn't fix anything as well.
Related
Hi! I just bought a Honor 9 STF-AL00, build: STF-AL00C00B201.
As it is the chinese version, I wanted to rebrand it, so I follow the instructions on https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719.
Unlocking bootloader was successful and as chinese firmware, it did not had a FRP lock.
The first time, rebranding stopped just before the menu.
The second time, I could access the menu and did the install.
But it looks like it did not go as expected because when the phone booted, it did not load TWRP but eRecovery.
So I booted in fastboot, it says phone locked & FRP locked.
I booted once again in eRecovery to download package from server and recovery but it says getting package info failed.
I tried to install stockrom from sd but it didnot work out.
I still have the bootloader code, but now i cant even install TWRP.
Can anyone please help me?
It is a brand new phone, I even havent use it yet and it's already bricked :'(
I install an service full repair stock via dload
http://androidhost.ru/v5
it is working right now.
oblivion2222 said:
Hi! I just bought a Honor 9 STF-AL00, build: STF-AL00C00B201.
As it is the chinese version, I wanted to rebrand it, so I follow the instructions on https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719.
Unlocking bootloader was successful and as chinese firmware, it did not had a FRP lock.
The first time, rebranding stopped just before the menu.
The second time, I could access the menu and did the install.
But it looks like it did not go as expected because when the phone booted, it did not load TWRP but eRecovery.
So I booted in fastboot, it says phone locked & FRP locked.
I booted once again in eRecovery to download package from server and recovery but it says getting package info failed.
I tried to install stockrom from sd but it didnot work out.
I still have the bootloader code, but now i cant even install TWRP.
Can anyone please help me?
It is a brand new phone, I even havent use it yet and it's already bricked :'(
Click to expand...
Click to collapse
You can always re-unlock your phones bootloader again, the key is always same, then flash or boot twrp with fastboot.
Some developers says the command for oreo is: fastboot flash recovery_ramdisk [file name] but I used this: fastboot flash recovery_ramdisk_a [file name]
You even can try to just boot twrp without flashing it to your recovery by simple typing: fastboot boot [file name]
If fastboot can flash twrp, turn your phone off then hold volume up/+ and power button same time and hold them until the state of unlocked warning appears.
You can use dload method or you can use HuRupdater method to flash firmware. You'll find introduction for how to do it.
Just search on xda
(RESOLVED)
How to fix:
Use fastboot to flash recovery.
1. Download Android Development Tools
2. Download TWRP
3. Put all files in a folder on your C drive named "Test"
4. Open cmd, type 'cd C:\Test\
5. Connect your phone to your computer
6. In the cmd prompt, type 'fastboot devices'
7. You should see a device listed.
8. Type 'fastboot flash recovery C:\Test\[Name of the TWRP file].img
9. Rebbot your phone into recovery mode.
10. Wipe your device
11. Install the ROM of your choice.
10. Issue resolved.
Hello all,
I had flashed my Nexus 5X with Lineage 15.1 and then rooted it with SuperSU and it worked perfectly; Until I flashed GAPPs (Apparently you are supposed to install GAPPs before rooting). My phone was freaking out after I flashed GAPPs (Apps that worked before just wouldn't open anymore, the camera couldn't take pictures or video, I couldn't use Google Services Framework, calls would disconnect after a minute, YouTube videos would stop after 8 minutes 16 seconds, etc. General mayhem). I tried all the tricks I knew to fix my issues (Rebooting, Uninstalling and reinstalling Apps, clearing cache via Custom Recovery, Updating, anything I could find to do). I eventually decided that I would just flash stock android. [NOTE: I had a 5x5 pattern lock. I didn't think this would be an issue, as I thought the encryption would be removed when I wiped the drive] So I booted into my custom recovery of choice (TWRP 3.2.3) and wiped my device, then sideloaded the stock Nexus 5X image. I boot into android and I am presented a 3x3 pattern. I thought that this must be some cached code, so I boot into the bootloader to see if I can clear dalvik/cache. But apparently, the custom recovery had been wiped (When I choose Custom Recovery in the bootloader, I just see an android figure on its back, its stomach open. It has the text 'No Command'.) I have tried to get ADB to work, but my device isn't recognized in any state (In the bootloader, in recovery mode, booted with the unencryption screen present).
General Information:
VARIANT - bullhead LGH790 32GB
HW VERSION - rev_1.0
BOOTLOADER VERSION - BHZ32c
SECURE BOOT - Enabled
DEVICE STATE - unlocked
TLDR: My phone is encrypted with a 5x5 pattern, but I can only enter a 3x3 pattern. I have no custom recovery, and no (Apparent) way to use ADB. Is there some other method of wiping everything from my phone that I haven't found during my hours of research, or is it perma-borked?
All in all, I messed up big time. I should have done more research before flashing GAPPs, and I should have removed the encryption just to be safe. I understand, if there is no way to wipe my phone. This is my last attempt before having to switch to a flip phone.
Thank you for your time and consideration. It is much appreciated.
Regards,
Draed3
Sorry to make my first post a request for help. Here's what happened.
I have a model KIW-L24 Honor 5X, with code-name kiwi with TWRP and Lineage OS 15.1 installed. Last night (today?) at around 2 AM PST or so (not sure of the exact time, I would have looked on my phone) my phone suddenly rebooted into recovery. I waited for the menu to pop up or something, but instead it eventually rebooted again. After that, every boot consists of "Boot/Recovery image verify failed!" "Please update to the authorized images." and then brings up the fastboot screen, which proudly displays "PHONE Locked" in green and "FRP unlock" in red. From what I understand, this means that the bootloader is locked (again).
Now, in theory, I can re-unlock the phone (once I find the relevant code again), flash lineage os again, and continue on my merry way. However, I have a password manager on my phone (Keypass2Android) that has not been backed up recently, so it would be preferable if I could recover that, at the very least. I've already tried booting both a custom recovery image and a stock recovery image via
Code:
fastboot boot <image>
but it only came back with
Code:
FAILED (remote: Command not allowed)
so I can only conclude that I cannot boot arbitrary images while the boot-loader is locked.
So, here's my options as I see it:
Unlock the bootloader again, wiping the device.
Flash stock, hope that that doesn't wipe my data. (EDIT: if it doesn't, hope that it doesn't bootloop or something requiring me to wipe)
Find some other method of recovering data from the device.
So, my questions are: how might the bootloader have gotten locked in the first place? Is there anything I can do to recover data, especially my password manager data? Please let me know if there's any other information you need.
Thanks in advance, regardless of the answer.
First of all, thanks for the great guides published here and all the work that went into them. They help resolve a lot of issues.
Unfortunately I encountered an issue today on my KIW-L21 that I can't find a solution for in the published guides. Today a stock update (installed via TWRP) got stuck on first boot and somehow managed to break the DLOAD recovery option (accessed by pressing Vol Up+Down when powering up the phone). Whenever I try to enter the DLOAD recovery mode now, the phone is not flashing the UPDATE.APP from the dload folder on the SD card anymore, but is showing an update screen (looks like a usb plug in a circle). This process stays on 5% for a while and then just reboots the phone into the regular system. So no option to recover from the UPDATE.APP anymore. Otherwise the phone still seems to be working fine.
Here's what I did to run into the problem:
- Successfully flash 5.1_EMUI 3.1_C432B140 firmware found in the Honor 5X repository on XDA via DLOAD recovery
- Flash TWRP (twrp-3.3.1-0-kiwi) via fastboot
- Download update to 6.0.1_EMUI 4.0_C432B350CUSTC432D003 via the regular update option
- After download the phone automatically booted into TWRP to install the update
- Reboot after TWRP flashed the update got stuck on boot and the DLOAD recovery got replaced by that update feature
Since then I booted into TWRP recovery again and installed AOSiP 9.0 + Magisk after wiping data/system/cache. This worked fine and AOSiP is booting and working correctly. The only issue now is that the DLOAD recovery did not get restored that way. That behavior stayed the same.
I tried eRecovery (reports an error after connecting to the wifi network, but this did not work before either) and stock recovery (extracted from B140 firmware and flashed via fastboot) without success. Both stock recovery options failed with an error message but did not provide any details regarding the issue.
Is the lost DLOAD recovery a known issue? Not sure if a partial update is stuck somewhere and needs to be deleted or if the DLOAD recovery function can be flashed via fastboot to fix this.
*** UPDATE 1
Here's some additional things I tried to fix the issue and that I noticed during those attempts:
- Recovery via HiSuite unfortunately does not seem to work. When booted into the bootloader HiSuite does not recognize the device. When booted into AOSiP, the phone is recognized, but the HiSuite app installed on the phone fails to work due to missing location authorizations. It doesn't ask for them though, just displays an error pop-up that leads to settings where I don't have the option to enable location access for the app. When manually checking the location permission for apps HiSuite is not among those that I can enable/disable this for.
- TWRP recovery can't be accessed from the phone despite flashing it via "fastboot flash recovery twrp.img". When launching recovery on the phone I end up in EMUI stock recovery. I can access and use TWRP via "fastboot boot twrp.img" though.
- I tried using the DLOAD update with the dload folder copied to the internal storage (local SD card). This did not change the phone getting stuck at a 5% update instead of the EMUI firmware flash.
- The local dload folder however seemed to have an impact on the stock recovery. While the stock recovery failed with an error before, it now gets the stuck at 99% done and a reboot just restarts the stock factory reset. I did find a way to exit this loop without waiting for the battery to drain (reboot with both volume buttons pressed into the update mode I don't want, reboot regularly once it stops on 5%) that got me back into a running/reset AOSiP.
- I can't boot into EDL mode via ADB (adb reboot edl). I was hoping HiSuite might help in that mode, but the command just rebooted the phone into AOSiP.
- The 5% update issue does not get resolved by disconnecting the phone from a cable during the operation. I read on XDA that this solved the issue for other HUAWEI devices, did unfortunately not work for mine.
- I noticed the bootloader does not show the FRP info anymore on the screen of the phone. It just shows "PHONE Unlocked". Not sure if that is important or just changed to this after unlocking the bootloader a few days ago.
The fact the flashing the recovery partition with TWRP does not seem to work properly suggests a partitioning issue to me. Is there a way to repartition the device and manually flash the relevant partitions via fastboot or some other tool?
If anyone knows how to fix the issue, a pointer in the right direction would be appreciated.
[SOLVED]
I finally managed to fix the issue by reverting to stock in several steps.
Tools required:
- Stock Firmware (I used the C432B140 I downloaded from the XDA Honor 5X repository)
- ADB/Fastboot toolset
- Huawei Update Extractor
- Stock firmware UPDATE.APP in dload folder on SD card installed in phone
1. I extracted BOOT.IMG, RECOVERY.IMG and SYSTEM.IMG from the full stock firmware
2. I rebooted the phone into bootloader (using command "adb reboot bootloader")
3. I flashed the stock recovery image (using command "fastboot flash recovery RECOVERY.IMG)
4. I flashed the stock system image (using command "fastboot flash system SYSTEM.IMG)
5. I flashed the stock boot image (using command "fastboot flash boot BOOT.IMG")
6. I rebooted the phone (using command "fastboot reboot"), this rebooted the phone in a stock B140 / B350 hybrid stock EMUI
7. I entered the ProjectMenu by entering *#*#2846579#*#* on in the phone app and chose "4. Software Upgrade" > "1. SDCard Upgrade" and confirmed that I want to perform the update.
8. The phone finally rebooted into the regular EMUI dload updater and reflashed stock firmware C432B140 to my phone
Afterwards the recovery from dload could also be started via Vol Up+Down when powering up the phone.
Hope this helps someone else fix the issue in case anyone encounters this.
I am facing a very similar issue on a KIW-L21 (running a custom ROM though).
Can anyone guide me to whether the steps presented can be modified to work coming from a custom ROM?
Hello, i want to share my experience because it may me useful for others. I have also a question for you at the end of the story.
I rooted my MI A3 with magisk but without twrp back in 2019 following the guide posted on this forum. The phone had android 9 and I never did software updates. Once in a while a messagge appeared on the screen saying that my software was obsolete and that I needed to update but I always managed to dodge it.
Some days ago my phone started behaving strangly (eg: I turned the volume down to zero but it turned up by itself) so I decided to reboot it. Something went wrong and the phone rebooted in fastboot mode. I tried many things but the phone was only able to boot in fastboot mode.
I thought that maybe the problem was related to the software update that sometimes was popping on the screen. So, i connected the phone to my pc and executed some fastboot commands:
fastboot getvar current-slot (to know which partition was in use. It was B)
fastboot set_active A (to switch to the other partition)
fastboot reboot
The phone rebooted correctly but it was on android 10 (before the problem it was on android 9) and without root. Everything seemed working fine and all the data was safe (only one thing changed, the boot process require much more time now). So, I realized that the phone applied the system update by itself (without my consent).
Now my question. The phone works well for the moment but how can i check the status of the partition B? I suspect that it may be damaged.
Furthermore I would like to flash the stock firmware, clear all the data and unroot the phone. Can I proceed? Should I flash both partitions?
Thanks
Any suggestions?