Hi, yesterday i unlocked my bootloader and flashed TWRP on my Honor 8 (FRD-L09.) And for some weird reason, my phone was soft bricked. When i tried to boot it, i had to go into fastboot mode, and then reboot it. Because of this, i relocked my bootloader and when i did that, i got an error message saying my system is damaged and should be formatted. So i tried formatting it with eRecovery, and it couldn't download the package info. But when i rebooted my device, everything was factory reset, and everything is as normal except for that the stock themes app is completely gone. Does anyone have a fix for this?
Edit: other EMUI apps are also gone, like the clock and calculator.
How did you go about relocking your bootloader?
Sent from my Honor 8 using XDA Labs
ayush rao said:
How did you go about relocking your bootloader?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
I used ADB on my computer and typed "fastboot oem relock (unlocking code)" (without quotes.) I got no error messages, and not even when i flashed TWRP, so it's so weird that this happened.
See, you didn't state this in your other thread. Sorry but what you need to do is flash the OS again. Your device won't function correctly because it was not formatted properly. A format WILL NOT erase OEM apps.
Evzonix said:
I used ADB on my computer and typed "fastboot oem relock (unlocking code)" (without quotes.) I got no error messages, and not even when i flashed TWRP, so it's so weird that this happened.
Click to expand...
Click to collapse
Are you currently running TWRP?
Sent from my Honor 8 using XDA Labs
Related
My google pixel is now bricked or atleast i think it is. This is what i did.
I already had PA 7.1.2 installed on my phone along with GAPPS. Everything was just fine untill i thought to get rid of the "unlocked bootloader warning screen". Stupid me!
I wanted a rooted phone with custom recovery but without the annoying warning message when i restart my phone everytime. Something like "google cant check the corruption of my phone".
I got into the bootloader mode and locked my bootloader with "fastboot flashing lock". The huge mistake i did was that i never turned on the OEM unlock option in my developer settings nor the USB debugging mode. Now my phone would not start into system and recovery. It bootloops for ever if i did those.
I am in India and not sure how i will get it replaced by google. Can this be solved. The solution i can think of is unlocking OEM from fastboot mode. Now if i try "fastboot flashing unlock", it tells me "Failed (remote: oem unlock is not allowed).
Someone please help meeeee. I have no other phone. Pleaseeeeeeeeeee.....
Prem's Pixel said:
My google pixel is now bricked or atleast i think it is. This is what i did.
I already had PA 7.1.2 installed on my phone along with GAPPS. Everything was just fine untill i thought to get rid of the "unlocked bootloader warning screen". Stupid me!
I wanted a rooted phone with custom recovery but without the annoying warning message when i restart my phone everytime. Something like "google cant check the corruption of my phone".
I got into the bootloader mode and locked my bootloader with "fastboot flashing lock". The huge mistake i did was that i never turned on the OEM unlock option in my developer settings nor the USB debugging mode. Now my phone would not start into system and recovery. It bootloops for ever if i did those.
I am in India and not sure how i will get it replaced by google. Can this be solved. The solution i can think of is unlocking OEM from fastboot mode. Now if i try "fastboot flashing unlock", it tells me "Failed (remote: oem unlock is not allowed).
Someone please help meeeee. I have no other phone. Pleaseeeeeeeeeee.....
Click to expand...
Click to collapse
You can get into fastboot mode. Have you tried reinstalling your firmware? Can you fastboot boot into TWRP?
Try this utility to see if it can help.
https://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
Tulsadiver said:
You can get into fastboot mode. Have you tried reinstalling your firmware? Can you fastboot boot into TWRP?
Click to expand...
Click to collapse
Yes i tried reinstalling. When the installation begins it tells me that it cant continue cuz the OEM is not unlocked. When i boot into recovery, it bootloops non-stop.
Not sure what to do.
I am in the process of installing the skipsoft tool. Lets see. Thanks for your response. Much appretiated. I hope this works.
I tried skipsoft. No luck. It is asking to unlock the OEM from developer settings in order to unlock the bootloader, which is technically impossible.
Because my phone cant boot into its OS. Any other idea. Please. I spent a lot of money for this phone and now this. There should be some way to unlock OEM without enabling it in developer option.
God help me !!!!
Prem's Pixel said:
I tried skipsoft. No luck. It is asking to unlock the OEM from developer settings in order to unlock the bootloader, which is technically impossible.
Because my phone cant boot into its OS. Any other idea. Please. I spent a lot of money for this phone and now this. There should be some way to unlock OEM without enabling it in developer option.
God help me !!!!
Click to expand...
Click to collapse
Have you tried fastboot boot twrp, install twrp, wipe everything and reinstall PA?
Sent from my Google Pixel using XDA Labs
It is not allowing me to fastboot boot twrp because it tells me that i have to unlock the bootloader first. So when i try to unlock bootloader..it is asking me to unlock OEM from developer settings. Its kind of a paradox now...
I am stuck in between. My only stupidness is the main reason i got into this trouble.. why god why...!
I appretiate your help man... just help me plss.
Prem's Pixel said:
It is not allowing me to fastboot boot twrp because it tells me that i have to unlock the bootloader first. So when i try to unlock bootloader..it is asking me to unlock OEM from developer settings. Its kind of a paradox now...
I am stuck in between. My only stupidness is the main reason i got into this trouble.. why god why...!
I appretiate your help man... just help me plss.
Click to expand...
Click to collapse
Also not booting to stock recovery from bootloader?
You got yourself into a hell of a situation m8.
Sent from my Google Pixel using XDA Labs
Prem's Pixel said:
It is not allowing me to fastboot boot twrp because it tells me that i have to unlock the bootloader first. So when i try to unlock bootloader..it is asking me to unlock OEM from developer settings. Its kind of a paradox now...
I am stuck in between. My only stupidness is the main reason i got into this trouble.. why god why...!
I appretiate your help man... just help me plss.
Click to expand...
Click to collapse
Try this:
Boot into bootloader
Run fastboot command:
Fastboot continue
Sgace said:
Also not booting to stock recovery from bootloader?
You got yourself into a hell of a situation m8.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
I know
Tulsadiver said:
Try this:
Boot into bootloader
Run fastboot command:
Fastboot continue
Click to expand...
Click to collapse
When i run "fastboot continue" it still bootloops...
Prem's Pixel said:
I know
Click to expand...
Click to collapse
From fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Everything should now be wiped clean so you need to flash factory image
Sent from my Google Pixel using XDA Labs
Sgace said:
From fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Everything should now be wiped clean so you need to flash factory image
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
This is what i get when i do those.
Fastboot erase system - please unlock device to enable this command. (Remote failure)
Fastboot erase data - same as above
Fastboot erase cache - same as above.
Thanks though. Still waiting for a miracle to happen.
Prem's Pixel said:
This is what i get when i do those.
Fastboot erase system - please unlock device to enable this command. (Remote failure)
Fastboot erase data - same as above
Fastboot erase cache - same as above.
Thanks though. Still waiting for a miracle to happen.
Click to expand...
Click to collapse
Damn bro, thats crap. Sorry I'm out of ideas for now.
If I come up with something will let you know.
Good luck m8.
Sent from my Google Pixel using XDA Labs
Prem's Pixel said:
This is what i get when i do those.
Fastboot erase system - please unlock device to enable this command. (Remote failure)
Fastboot erase data - same as above
Fastboot erase cache - same as above.
Thanks though. Still waiting for a miracle to happen.
Click to expand...
Click to collapse
Try this to get to stock recovery
https://www.google.com/amp/s/www.androidexplained.com/pixel-recovery-mode/amp/
Do you have a nandroid backup?
Sent from my Google Pixel using XDA Labs
Tulsadiver said:
Try this to get to stock recovery
https://www.google.com/amp/s/www.androidexplained.com/pixel-recovery-mode/amp/
Click to expand...
Click to collapse
I tried the steps mentioned in the link you provided, when i select recovery mode. It starts bootlooping. It bootloops everywhere except the fastboot screen. And, the fastboot screen shows that bootloader is locked loke i mentioned before. Back to where i started.
Sgace said:
Do you have a nandroid backup?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Nope, i dont have a nandroid backup.
Sgace said:
Damn bro, thats crap. Sorry I'm out of ideas for now.
If I come up with something will let you know.
Good luck m8.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your patience.
Try to push the full OTA thru recovery..
Found here: https://developers.google.com/android/ota?hl=vi
Although I'm a nood, but maybe there's a solution found here
So I probably screwed this up pretty bad. I unlocked the bootloader then installed twrp then installed RROS on my honor 8. Then I decided to be stupid and wanted to put the honor 8 back to stock. So I flash the stock recovery and then flash emui 5. Now if I go to the dev options the bootloader is grayed out but not selected. I've tried adb and fastboot to try and re-unlock the bootloader but it gives me a failure response. Anyone got any ideas?
Thank you in advance
Korvain said:
So I probably screwed this up pretty bad. I unlocked the bootloader then installed twrp then installed RROS on my honor 8. Then I decided to be stupid and wanted to put the honor 8 back to stock. So I flash the stock recovery and then flash emui 5. Now if I go to the dev options the bootloader is grayed out but not selected. I've tried adb and fastboot to try and re-unlock the bootloader but it gives me a failure response. Anyone got any ideas?
Thank you in advance
Click to expand...
Click to collapse
I figured it out i was typing the command incorrectly, the correct command is:
fastboot oem relock 'passcode'
Hi, I'm trying to root my Honor 8 device and install TWRP. However when I try to flash the TWRP file in ADB, I get this error message:
FAILED(remote not allowed). I have tried different versions of TWRP, the latest one and the one thats for Honor 8 on their site. I have unlocked bootloader. I don't understand what's happening. Can someone please explain this?
It's my first time rooting a device manually, so i dont know much. If you are able to, please refer to things in an easy manner.
Thanks in advance.
ver1x said:
Hi, I'm trying to root my Honor 8 device and install TWRP. However when I try to flash the TWRP file in ADB, I get this error message:
FAILED(remote not allowed). I have tried different versions of TWRP, the latest one and the one thats for Honor 8 on their site. I have unlocked bootloader. I don't understand what's happening. Can someone please explain this?
It's my first time rooting a device manually, so i dont know much. If you are able to, please refer to things in an easy manner.
Thanks in advance.
Click to expand...
Click to collapse
Is Your Bootloader Unlocked???
And Also This TWRP:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/page1
Can Only Work For The Honor 8 Android 7
On TWRP Website, The TWRP There Only Works For The Honor In Android 6.
Also When Flashing a recovery Do "fastboot flash recovery [Filename]"
RealFireBlaze20 said:
Is Your Bootloader Unlocked???
And Also This TWRP:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/page1
Can Only Work For The Honor 8 Android 7
On TWRP Website, The TWRP There Only Works For The Honor In Android 6.
Also When Flashing a recovery Do "fastboot flash recovery [Filename]"
Click to expand...
Click to collapse
Yes i have unlocked the bootloader. I'm pretty sure i've already tried that version of TWRP, but i will try again tomorrow.
I always flash recovery using "fastboot flash recovery (file name)" so that's not the problem.
ver1x said:
Yes i have unlocked the bootloader. I'm pretty sure i've already tried that version of TWRP, but i will try again tomorrow.
I always flash recovery using "fastboot flash recovery (file name)" so that's not the problem.
Click to expand...
Click to collapse
Hmmmm... Okay
RealFireBlaze20 said:
Hmmmm... Okay
Click to expand...
Click to collapse
I think i might have found the problem.
When i go into bootloader it says FRP lock, i've looked around a bit, and i cant seem to figure out what it is and how i can unlock it.
If you know, how?
ver1x said:
I think i might have found the problem.
When i go into bootloader it says FRP lock, i've looked around a bit, and i cant seem to figure out what it is and how i can unlock it.
If you know, how?
Click to expand...
Click to collapse
I had same problem. I successfully unlocked bootloader but after that I accidentally restored default settings in developer settings and oem unlock was ticked off and greyd out. Then I noticed the same FRP lock.
I had to relock and unlock the bootloader. Only after that I was able to flash twrp on my phone.
To relock you type "fastboot oem relock (unlock code)"
After that you can turn on "oem unlock" and "usb debugging"
And yes, It will wipe your data when relocking and again after unlocking so it takes some time. Hope this helps :fingers-crossed:
Juhkimo said:
I had same problem. I successfully unlocked bootloader but after that I accidentally restored default settings in developer settings and oem unlock was ticked off and greyd out. Then I noticed the same FRP lock.
I had to relock and unlock the bootloader. Only after that I was able to flash twrp on my phone.
To relock you type "fastboot oem relock (unlock code)"
After that you can turn on "oem unlock" and "usb debugging"
And yes, It will wipe your data when relocking and again after unlocking so it takes some time. Hope this helps :fingers-crossed:
Click to expand...
Click to collapse
Thanks, i will definetely try this!
Edit: it worked! Thank you so much.
ver1x said:
Thanks, i will definetely try this!
Edit: it worked! Thank you so much.
Click to expand...
Click to collapse
Good to hear that
I can't do it
How am I supposed to get the bootloader code now that Huawei disabled it on their site?
VFR99 said:
How am I supposed to get the bootloader code now that Huawei disabled it on their site?
Click to expand...
Click to collapse
Dc unlocker Progam for pc
Hello guys, I dont know whats happening with my Nexus 5 right now. Its stuck on Google logo which appears during restarting of the phone.
I have tried everything. I try to go into recovery it dosent work. I tried changing it to CWM from TWRP still it stays TWRP i get errors while flashing .bat files like (error: failure to write). Please help been stuck on this since past 72hours. Any help to resolve this issue is appreciated. Thanks :crying::crying::crying:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
OEM can be locked and unlocked. But the only problem now is i cannot override the previous partitions as there is an error "failed to write" i dont understand why is this happening this is also the reason i cannot get into my recovery as when i enter recovery it gets stuck for some reason.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also what does flash 4.4 mean? Sorry new to this!
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also i tried to erase partitions manually but i always got an error as (remote: failed to erase partition)
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
It goes back to unlocked
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
Do you have discord or teamspeak or any other apps to chat directly?
NeXussssssssss said:
It goes back to unlocked
Click to expand...
Click to collapse
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
audit13 said:
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
Click to expand...
Click to collapse
I tried the 1st step by overwriting twrp with cwm dint work. Also ADB isnt connected. I tried to but just fastboot works.
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
audit13 said:
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried flashing new roms it says failure to write to cache,boot,recovery everything fails!
There is no way to erase partitions as it fails!
I would say the internal memory is damaged and will require a motherboard change.
I kept my phone on charge for a few mins and when I came back to unplug, it was stuck on google screen. tried turning off the device or restarting it but nothing works. The phone was extremely hot. My phone is completely factory stock. the bootloader is locked too. how to recover it now ? please help.
i tried entering recovery mode but as soon as i select recovery it gets back to google logo screen again.
right now i have kept the phone in freezer now.
my bootloader is locked .. can i still unlock it and flash factory image ?
help ?
not a single reply ? bump...
Are you able to communicate with the device using fastboot?
Try flashing the stock images via fastboot
You won't need an unlocked bootloader for this
post-mortem said:
Are you able to communicate with the device using fastboot?
Click to expand...
Click to collapse
yes im able to communicate with the device through fastboot. but my bootloader is locked.
wahur1 said:
yes im able to communicate with the device through fastboot. but my bootloader is locked.
Click to expand...
Click to collapse
Try the instructions at the top of the page here https://developers.google.com/android/images
It may work without unlocking the bootloader.
post-mortem said:
Try the instructions at the top of the page here https://developers.google.com/android/images
It may work without unlocking the bootloader.
Click to expand...
Click to collapse
whatever command i use it says OEM unlock is not allowed.
Just throwing out ideas that you may have already tried. If I understand right you cannot get into recovery which eliminates trying to sideload the stock image. Your bootloader is locked and it will not let you unlock so booting into TWRP is out of the question. Are you just wanting your phone operational again? Have you tried wiping/factory resetting with fastboot commands? i.e. fastboot erase userdata or fastboot format userdata.
wahur1 said:
whatever command i use it says OEM unlock is not allowed.
Click to expand...
Click to collapse
Have you tried flashing without unlocking the bootloader?
post-mortem said:
Have you tried flashing without unlocking the bootloader?
Click to expand...
Click to collapse
yes i have tried flashing by giving the fastboot command "flash-all.bat" it starts flashing and it stops in the initial stage by giving error " restarting bootloader" then I get 2nd error " bootloader locked" and process repeats again
toasterboy1 said:
Just throwing out ideas that you may have already tried. If I understand right you cannot get into recovery which eliminates trying to sideload the stock image. Your bootloader is locked and it will not let you unlock so booting into TWRP is out of the question. Are you just wanting your phone operational again? Have you tried wiping/factory resetting with fastboot commands? i.e. fastboot erase userdata or fastboot format userdata.
Click to expand...
Click to collapse
both command not working .. same bootloader locked message.
error message " Please unlock the device to activate this command"
anyone else can help ?
I would contact Google customer support. Even though my phone was out of warranty and I was not the original buyer (bought in eBay), they were willing to make a one-time exception for an RMA. I didn't use it because my phone is rooted and I was afraid of being charged for any repairs. As long as your phone is stock and unrooted, you have a chance. Just say that you think you have a hardware failure and while you understand that they are in no obligation to help, you would appreciate anything they can do.
Sent from my Pixel XL using Tapatalk