Hi !
I had rooted my Honor 9 flashing ramdisk file through fastboot so I unlocked the bootloader and FRP and everything was fine. I was on Oreo. Now I wanted to go back to a stock unrooted Oreo phone. I used "fastboot oem relock
Code:
" but now my phone doesn't boot anymore.I didn't flash any unroot file. When I turn it on I have a Google logo and then Huawei eRecovery but it doesn't work. The phone now says in fastboot "Phone Relocked" and "FRP Lock". I'm used to flash samsung phones but I'm a bit confused with Honor/Huawei.
Any help please ?
nobody ?
closed. the phone is now dead...RIP
Related
Hi all, yesterday I updated the bootloader of my OnePlus X and today I accidentally rebooted it into fastboot mode, when I tried to reboot the device it started a bootloop. Now I can't even boot into recovery but only in fastboot. I also tried to flash TWRP with command prompt but it says that the device isn't unlocked (strange i'm sure it was till yesterday) so I tried to unlock it with "fastboot oem unlock" but it says that oem unlock is disabled. Please help me
To unbrick your phone use this
You can then update to 3.1.3 Stock with the default bootloader.
You need to enable OEM-unlock in the developer-settings else patching the new bootloader may lock it again had the same problem.
Nordii said:
To unbrick your phone use this
You can then update to 3.1.3 Stock with the default bootloader.
You need to enable OEM-unlock in the developer-settings else patching the new bootloader may lock it again had the same problem.
Click to expand...
Click to collapse
Thank you! It worked
Hi, I want to install a stock official google release of android 7.0 onto the Doopro P2 Pro. If I cant do that I want to at least root the phone, the reason being that this phone is pretty well built, but the software is just bloatware, it barely qualifies as android, it also has ads. I successfully got into bootloader/fastboot, and I checked that it is unlocked via windows cmd "fastboot oem device-info". I also successfully flashed some kind of twrp into it with "fastboot flash recovery "C:\Users\...\twrp.img"".
The only problem is that this phone only has options if I boot it into recovery mode, but only a logo if I am in fastboot mode. I tried using "fastboot boot "C:\Users...\twrp.img"", which returns a remote: dtb not found error.
Now when I try to boot into recovery mode (adb reboot recovery), it just loads the bootloader which only has a logo as I mentioned earlier. The OS still boots up fine. The only problem I can think of is that I am trying to boot a TWRP that is not compatible with the device / android (6.0.1). Please somebody help me!
gabor6505 said:
Hi, I want to install a stock official google release of android 7.0 onto the Doopro P2 Pro. If I cant do that I want to at least root the phone, the reason being that this phone is pretty well built, but the software is just bloatware, it barely qualifies as android, it also has ads. I successfully got into bootloader/fastboot, and I checked that it is unlocked via windows cmd "fastboot oem device-info". I also successfully flashed some kind of twrp into it with "fastboot flash recovery "C:\Users\...\twrp.img"".
The only problem is that this phone only has options if I boot it into recovery mode, but only a logo if I am in fastboot mode. I tried using "fastboot boot "C:\Users...\twrp.img"", which returns a remote: dtb not found error.
Now when I try to boot into recovery mode (adb reboot recovery), it just loads the bootloader which only has a logo as I mentioned earlier. The OS still boots up fine. The only problem I can think of is that I am trying to boot a TWRP that is not compatible with the device / android (6.0.1). Please somebody help me!
Click to expand...
Click to collapse
hi, same for me, any news, did you found any way to root it or any stock firmware rom source maybe?
Hello all,
I have a Mate 10 Pro that I was having trouble updating, I assumed due to having TWRP installed. So, I tried to restore the stock recovery via fastboot flash.
However, the flash would always fail with "remote: Command Not Allowed" error. Googling showed this to be result of locked bootloader, but my phone was indeed unlocked. Indicated on the screen when in Download mode.
Some threads suggested relocking and then unlocking the bootloader again. So I ran fastboot oem relock, which restarted and factory reset the phone. Then I ran fastboot oem unlock and I am now getting the "remote: Command Not Allowed" error, and my phone remains locked and now it will not boot at all but only to the eRecovery screen which wants to connect to wifi and download a package but getting package info always fails. Oh, and since I didn't think to remove my account, the phone is also FRP locked.
I had found a thread before this incident saying to change the DNS in order to get the eRecovery download to work, and at the time it did. Now the only thread I find with that suggestion (81.177.139.39, not sure it's the same one) it still fails to get package info.
So as it stands I have a FRP locked, bootloader locked Mate 10 Pro that will only boot to eRecovery.
Anyone have any suggestions?
Hello
I want to share with my problem. Yesterday i did (again) stock rom instalation by hurupdater in twrp and my Honor 9 went bootloop. Now i dont have twrp, phone shows red statement "your device has failed verification and may not work properly" and its going erecovery after boot. Erecovery cant find solution and shows "data package info failed" which is weird to me because last time everything went okay...
I was able to go white fastboot screen with usb plug, but i dont have any backups on hisuite and i have no idea how to fix it. I will be grateful for your help.
boot in bootloader, with fastboot :flash twrp on recovery_ramdisk and use again HuRUpdater with a corrrcect firmware.
oslo83 said:
boot in bootloader, with fastboot :flash twrp on recovery_ramdisk and use again HuRUpdater with a corrrcect firmware.
Click to expand...
Click to collapse
cant be done. Fastboot&rescue mode shows Phone Unlocked FRP unlocked but when i type anything in cmd nothing is happening. Comand adb devices is not showing my phone.
in bootloader mode you have to use fastboot and not adb...
Hello!
My Nokia 7.1 is stucked in "Download Mode" after i installed Security Update i already tryed Reset to Factory Mode but still the same.
I'm able to access the Phone via Fastboot cmd, i tryed to unlock OEM so that i can do a "fastboot erase userdata" so that i can send the phone to a service center but it dont work cause its locked.
I cant install the apk from Nokia so i'm not able to receive the .key File to unlock my Bootloader, is there a other way to unlock my Bootloader?
Thanks you very much!
-pumpk1n-
Resolved: I asked techmesto.com he flashed my a ROM on my Phone now it workes again, thanks for the help !!