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
Related
I have a nexus 5 that keeps bootlooping, I can get into recovery and bootloader but when I run the fastboot command to unlock the bootloader it shows unlocked but as soon as I restart the phone it shows that it's locked.
I've tried unlocking and flashing but flashing things via fastboot doesn't take any effect.
I was wondering if there is any way to get the phone running or if its dead.
Thanks
mafiaboy01 said:
I have a nexus 5 that keeps bootlooping, I can get into recovery and bootloader but when I run the fastboot command to unlock the bootloader it shows unlocked but as soon as I restart the phone it shows that it's locked.
I've tried unlocking and flashing but flashing things via fastboot doesn't take any effect.
I was wondering if there is any way to get the phone running or if its dead.
Thanks
Click to expand...
Click to collapse
Sounds to me like your emmc is fried. You're gonna have to RMA it, unfortunately.
_MetalHead_ said:
Sounds to me like your emmc is fried. You're gonna have to RMA it, unfortunately.
Click to expand...
Click to collapse
That's what I figured, its out of warranty so no sense in sending it in.
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 unlocked, rooted and installed LOS on one of my classmates honor 8 a few months ago. for whatever reason he decided he wanted to go back to stock and asked me help. due to work and school i was unable to help so he came on to xda to find help.
he ended up using a guide and............... well, its all f*cked!! i dont know how but his phone is not only bootloader locked but also FRP locked.
to make things worse, the phone wont boot and it has no recovery. i have tried the vol+ and power, vol+- and power but non work. i am able to get into fastboot. i have thought of maybe sending the phone in to maybe huawei us but the phone came from ebay.
the phone was a damaged ebay win that was repaired by me. it worked great but i dont know if its possible to send to huawei for repair. anyway, i would appreciate any and all help.
You might need to reset with the /sdcard/ dload method. Check out the other forums for instructions.
Telperion said:
You might need to reset with the /sdcard/ dload method. Check out the other forums for instructions.
Click to expand...
Click to collapse
thanks for the help! i cant enter the update menu. as soon as i try it reboots. the blue splash image flashes and then restarts. ill check around but im really starting to feel bad. i already told my classmate that he might be SOT but i hope i can do something.
droidbot1337 said:
thanks for the help! i cant enter the update menu. as soon as i try it reboots. the blue splash image flashes and then restarts. ill check around but im really starting to feel bad. i already told my classmate that he might be SOT but i hope i can do something.
Click to expand...
Click to collapse
It's highly unlikely that you're SOL, if you can get into the bootloader then you can flash the stock recovery. If you can flash the stock recovery, you can flash a rollback package to completely restore everything to stock.
So long as you have a working fastboot, you're fine.
Telperion said:
It's highly unlikely that you're SOL, if you can get into the bootloader then you can flash the stock recovery. If you can flash the stock recovery, you can flash a rollback package to completely restore everything to stock.
So long as you have a working fastboot, you're fine.
Click to expand...
Click to collapse
ah, the thing is..... both the bootloader and FRP are locked. as i mentioned, he wanted to return to stock and followed a guide here. he doesnt remember what exactly he did as it was almost a month ago but it ended relocking the bootloader and FRP. i really feel horrible for not helping him which is why im desperate to get this working. i might just end up giving him mine.
droidbot1337 said:
ah, the thing is..... both the bootloader and FRP are locked. as i mentioned, he wanted to return to stock and followed a guide here. he doesnt remember what exactly he did as it was almost a month ago but it ended relocking the bootloader and FRP. i really feel horrible for not helping him which is why im desperate to get this working. i might just end up giving him mine.
Click to expand...
Click to collapse
Can you unlock the bootloader again?
Telperion said:
Can you unlock the bootloader again?
Click to expand...
Click to collapse
this is where i get trouble, i have tried for the past day and a half. when i try to unlock i get the following error:
Code:
C:\adb>fastboot oem unlock xxxxxxxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
C:\adb>
droidbot1337 said:
this is where i get trouble, i have tried for the past day and a half. when i try to unlock i get the following error:
Code:
C:\adb>fastboot oem unlock xxxxxxxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
C:\adb>
Click to expand...
Click to collapse
Try a rollback and Install b131 via 3 button method
xynewageyx said:
Try a rollback and Install b131 via 3 button method
Click to expand...
Click to collapse
so i tried and nothing, i get to the blue splash screen and the phone just reboots. i keep trying to unlock the bootloader but i get the same error as i posted above. shouldnt i be able to unlock the bootloader? im thinking that i have some kind of driver problem.
my pc is pretty much dead so im using my laptop and im not sure i have it set up correctly. anyway, i know oem unlock is required to unlock bootloader but is there anyway i can unlock straight from fastboot?
Try a 'fastboot oem relock' with the unlock code, then after the reboot, try unlocking again.
Telperion said:
Try a 'fastboot oem relock' with the unlock code, then after the reboot, try unlocking again.
Click to expand...
Click to collapse
did that but when i try to unlock the bootloader i get the error message. it just keeps stating "(remote: Command not allowed)" which is where i am stuck at.
droidbot1337 said:
did that but when i try to unlock the bootloader i get the error message. it just keeps stating "(remote: Command not allowed)" which is where i am stuck at.
Click to expand...
Click to collapse
Before you unlock try a rollback and flash b131
xynewageyx said:
Before you unlock try a rollback and flash b131
Click to expand...
Click to collapse
thanks for the help. im not able to access any of the recovery functions. i have tried the multiple volume and power combos but none work. all i am able to access is fastboot but thats about it. im unable to run commands such as bootloader unlock which is what i really need.
droidbot1337 said:
thanks for the help. im not able to access any of the recovery functions. i have tried the multiple volume and power combos but none work. all i am able to access is fastboot but thats about it. im unable to run commands such as bootloader unlock which is what i really need.
Click to expand...
Click to collapse
Have u tried to reflaah the firmware?
You have trwp and can boot in twrp right??
xynewageyx said:
You have trwp and can boot in twrp right??
Click to expand...
Click to collapse
nope! as the title says, bootloader locked, FRP locked, no recovery....... and it seems im SOT!!
so, i took apart the phone and switched some parts to another honor 8 that was damaged. the damaged one now works and i will be giving it to my classmate on tuesday before class. i guess ill keep this one and home i figure out how to fix it eventually.
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.
Recently rooted my new Zenfone 7. Is it possible to remove Bootloader unlocked Warning message at the start up of the system? Thanks for an answer.
re-lock the bootloader
Boot into fastboot, then send this command from your pc.
fastboot oem asus-lock
how did you get root to work? I followed the instructions listed and it would not work for me.
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Jkm15 said:
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Click to expand...
Click to collapse
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Jkm15 said:
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Click to expand...
Click to collapse
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Joeb2000 said:
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Click to expand...
Click to collapse
Had locked bootloader on device with magisk. Result is fastboot loop =|
Same wish here. that warning screen is ugly....