I was trying to fixed my honor 20 pro after atempting the root process, beacuse I thought the warning message (your device is unlocked and can't be trusted) on the boot screen was the cause of why I could't find some apps on the play store such as Netflix. (and I don't need the root anymore)
After I read some guides and tried to restore the system from eRecovery (without success) I tried the bootloader cmd method with the phone connected via usb in fastboot mode.
Unfortunatly i probably deleted some img files by prompting fastboot flash bootloader (but i'm not sure) and i bricked the system which is now stucked in a boot loop.
I'd like to restore the whole system with a factory firmware but I can't find the official one.
I only found one on androidhost.ru but it seems to do not contain any KERNEL.img or SYSTEM.img
Should I asked to the technical support the firmware or does anyone can provide a proper one? or any other solutions?
I'd just like to restore my honor as a new phone without root.
Related
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
I'm stuck with this problem too. The exact problem. Have you found a way to fix it?
I have exactly the same problem with my Huawei Tablet.
If I boot with the original ROM and look in the "/log" - directory with adb shell, there is a cust.log. The contents say, that the specific ROM is not original or factory.
I think even the bootloader is unlocked, there is a kind of signature checking.
EDIT: @Asdforcer: Have you tried to boot the original boot.rom with "fastboot boot" - command?
How to remove FRP on Huawei Y6 TIT U02
Hi,
Since I try to update firmware from HUAWEI website, my phone comes non stop booting (bootloop). Any one can help me how to fix my phone?
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
Try to unlock your bootloader
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
My system crashed when I was typing in Whatsapp and since then the phone is trying to reboot but is stuck eternally in the boot screen with the Mi and Android logo. I only had 100 MB free space, so maybe the system cannot boot because of that?
- The newest version of Mi PC Suite cannot connect and an older MiPhoneAssistant version is only able to flash the ROM.
- I tried to clear caches with fastboot but it says "device is locked. Cannot erase". Also flashing TWRP is not possible.
- When trying to start adb shell in bootloader mode it only says "error: closed".
- It is possible to start adb shell when the phone is stuck in the boot screen, but without root permission I cannot access the data folder
So I really tried a lot, but as this whole topic is new to me, maybe someone has another idea? I once already successfully recovered encrypted files from an old Windows partition and I didn't imagine that this would be so difficult on a phone. I only need my notes from the MIUI Notes app, (almost) all the other stuff was backuped.
Is your phone bootloader is locked?
Jaga1234 said:
Is your phone bootloader is locked?
Click to expand...
Click to collapse
Yes, otherwise I would have flashed another one
So finally I had to use the testpoint method (https://www.youtube.com/watch?v=AE4JhUbZ_LQ) to flash a new ROM, but all data ist lost .
sector001 said:
So finally I had to use the testpoint method (
) to flash a new ROM, but all data ist lost .
Click to expand...
Click to collapse
I tried with qfil tool it was successful but still stuck at milogo , when i am trying with miflash there is some error always
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?
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.