Hi,
I have big problem with my OPO. One night the phone is turned off and fell into a boot loop.
Unfortunately the OEM is not unlocked and now i can't unlocked my phone by the command line.
lukole said:
Hi,
I have big problem with my OPO. One night the phone is turned off and fell into a boot loop.
Unfortunately the OEM is not unlocked and now i can't unlocked my phone by the command line.
Click to expand...
Click to collapse
Screen with my problem
You have to go into bootloader mode (volume down + power) and type fastboot oem unlock. Not flash because your bootloader is locked.
Sent from my Nexus 6 using Tapatalk
lukole said:
Hi,
I have big problem with my OPO. One night the phone is turned off and fell into a boot loop.
Unfortunately the OEM is not unlocked and now i can't unlocked my phone by the command line.
Click to expand...
Click to collapse
zephiK said:
You have to go into bootloader mode (volume down + power) and type fastboot oem unlock. Not flash because your bootloader is locked.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried do this ( power + vol up)
Ok, show me that bootloader is unlocked, then turn on cyanogen recovery, but bootloader isn't unlocked :/
lukole said:
I tried do this ( power + vol up)
Ok, show me that bootloader is unlocked, then turn on cyanogen recovery, but bootloader isn't unlocked :/
Click to expand...
Click to collapse
I said power + volume down. Not volume up, that doesn't get you into bootloader mode.
I told you to unlock the bootloader by typing fastboot oem unlock while being in bootloader mode.
Please read carefully.
Sent from my Nexus 6 using Tapatalk
zephiK said:
I said power + volume down. Not volume up, that doesn't get you into bootloader mode.
I told you to unlock the bootloader by typing fastboot oem unlock while being in bootloader mode.
Please read carefully.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried, but phone is blocked.
zephiK said:
I said power + volume down. Not volume up, that doesn't get you into bootloader mode.
I told you to unlock the bootloader by typing fastboot oem unlock while being in bootloader mode.
Please read carefully.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hang on, power + volume up is the correct combination to get into bootloader, power + volume down gets you to recovery.
Transmitted via Bacon
timmaaa said:
Hang on, power + volume up is the correct combination to get into bootloader, power + volume down gets you to recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
Oh right, I got the two devices mixed up ... wish all the Android OEMs just stick with the same combinations.
OP what did you mean by its locked? What happens when you input fastboot oem unlock?
zephiK said:
Oh right, I got the two devices mixed up ... wish all the Android OEMs just stick with the same combinations.
OP what did you mean by its locked? What happens when you input fastboot oem unlock?
Click to expand...
Click to collapse
It'd make things easier wouldn't it.
Transmitted via Bacon
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
lukole said:
I tried, but phone is blocked.
Click to expand...
Click to collapse
Issue this command:
Code:
fastboot oem device-info
Please post a screenshot of the result.
Transmitted via Bacon
SS:
lukole said:
SS:
Click to expand...
Click to collapse
Ok, and try:
Code:
fastboot oem unlock
Post the result.
Transmitted via Bacon
timmaaa said:
Ok, and try:
Code:
fastboot oem unlock
Post the result.
Transmitted via Bacon
Click to expand...
Click to collapse
OK,
I made everything (SS) then phone turn on to cyanogen recovery, but phone is not unlock...
lukole said:
OK,
I made everything (SS) then phone turn on to cyanogen recovery, but phone is not unlock...
Click to expand...
Click to collapse
So when issuing the fastboot oem device-info command again, it still says false for bootloader unlocked?
Transmitted via Bacon
timmaaa said:
So when issuing the fastboot oem device-info command again, it still says false for bootloader unlocked?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, it says false for bootloader unlocked (SS)
lukole said:
Yes, it says false for bootloader unlocked (SS)
Click to expand...
Click to collapse
Refer to the thread, http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that will fix your issue to unlock your bootloader.
zephiK said:
Refer to the thread, http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that will fix your issue to unlock your bootloader.
Click to expand...
Click to collapse
I tried this method previously, I can't use because don't have custom recovery.
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.
https://forum.xda-developers.com/xperia-z5/help/bootloader-unlock-allowed-able-to-boot-t3715524
So, in the end, I decided to flash the customized E6653 NOBA ROM for my Z5
Later, I was thinking... if I can go to the Flashmode & Fastboot mode, can I continue to unlock the bootloader, even though it says No?
Because to my knowledge, with Bootloader Unlock Allowed No, means that I can't access both Flashmode & Fastboot mode
Thanks lads, again
Aircatcher said:
https://forum.xda-developers.com/xperia-z5/help/bootloader-unlock-allowed-able-to-boot-t3715524
So, in the end, I decided to flash the customized E6653 NOBA ROM for my Z5
Later, I was thinking... if I can go to the Flashmode & Fastboot mode, can I continue to unlock the bootloader, even though it says No?
Because to my knowledge, with Bootloader Unlock Allowed No, means that I can't access both Flashmode & Fastboot mode
Thanks lads, again
Click to expand...
Click to collapse
As i said earlier - no you cant, no possible way.
EugenStanis said:
As i said earlier - no you cant, no possible way.
Click to expand...
Click to collapse
What a bummer... I may likely to RMA or sell this phone and go for XZ, the global version ofc
I did root my phone with fastboot commands when my bootloader was still locked.
That means I could still go to fastboot stuff.
Try the fastboot commands. It might works.
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 was playing with bootloader/flashing kernels etc. than I decided to lock bootloader, I entered the command in CMD, relocked the bootloader and instead of booting, I pressed "recovery mode" accidentally. Phone hasn't entered recovery, and Now the phone is not starting at all, just 0.1 seconds long flashing of google white screen and that's all. Can't enter recovery mode from fastboot menu, and cant boot either. Any suggestions will be helpful. Thanks in advance.
Have you tried reflashing a factory image?
Flipz77 said:
Have you tried reflashing a factory image?
Click to expand...
Click to collapse
how? Can I use CMD in fastboot mode? and the bootloader is locked also
nvm, I have unlocked bootloader and the phone booted normally. Thanks anyway
I wouldn't lock that bootloader again, you got lucky, do a search here on why it's not a good idea
Sent from my Pixel using XDA-Developers Legacy app
Hi Levan_i,
can you tell me how you have done the unlocking?
It seems to me that we have/had the same problem https://forum.xda-developers.com/pixel/help/bootloop-installing-factory-image-t3866332/post78149546#post78149546
ArchArch said:
Hi Levan_i,
can you tell me how you have done the unlocking?
It seems to me that we have/had the same problem https://forum.xda-developers.com/pixel/help/bootloop-installing-factory-image-t3866332/post78149546#post78149546
Click to expand...
Click to collapse
I have just entered "fastboot oem unlock" in CMD
Cant do that
Levan_i said:
I have just entered "fastboot oem unlock" in CMD
Click to expand...
Click to collapse
Says for me remote oem unlock isnt allowed
FalseFriendsGaming said:
Says for me remote oem unlock isnt allowed
Click to expand...
Click to collapse
You need to go to Settings -> System -> Advanced -> Developer options -> set OEM unlocking as enabled. Also, make sure you're using the latest platform-tools package.
Cant do that
post-mortem said:
You need to go to Settings -> System -> Advanced -> Developer options -> set OEM unlocking as enabled. Also, make sure you're using the latest platform-tools package.
Click to expand...
Click to collapse
I can't since I relocked my bootloader after rooting its crashing on startup and cant get to the lock screen
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