Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Shebee said:
Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Click to expand...
Click to collapse
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
dominoeflux said:
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
Click to expand...
Click to collapse
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Shebee said:
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Click to expand...
Click to collapse
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well that sucks :/
Guess I'll just wait for my next phone.
Related
recently i flashed twrp recovery on my phone successfully but on opening recovery mode from bootloader screen it again takes me back to bootloader screen, after that i have ony few options like normal boot ,power of, restart bootloader. i appreciate some help , plz tell me what should i do , how to open twrp recovery or get back to stock recovery??
btw phone is rooted and twrp flashed through adb following this link - http://www.xda-developers.com/how-to-install-twrp/
thanks
Are you sure you unlocked your bootloader before you flashed TWRP?
Sent from my ASUS_Z00A using Tapatalk
GroveStreetHomie said:
Are you sure you unlocked your bootloader before you flashed TWRP?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
No I thought it would be good to backup the current stock Rom before unlocking the boot loader. I was gonna do that after backup but this problem showed up. Boot loader is locked for now
amanbansal009 said:
No I thought it would be good to backup the current stock Rom before unlocking the boot loader. I was gonna do that after backup but this problem showed up. Boot loader is locked for now
Click to expand...
Click to collapse
Yeah, always unlock your bootloader first before flashing any kind of recovery.
Follow this thread to fix your problem.
http://forum.xda-developers.com/zenfone2/help/enter-recovery-551ml-z00a-t3345633
Sent from my ASUS_Z00A using Tapatalk
GroveStreetHomie said:
Yeah, always unlock your bootloader first before flashing any kind of recovery.
Follow this thread to fix your problem.
http://forum.xda-developers.com/zenfone2/help/enter-recovery-551ml-z00a-t3345633
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
thank you very much sir... i appreciate it. now i will unlockbootloader first and then flash twrp
Hi there, I have a similar problem i think. I have unlocked bootloader.
My problem is PC won't regonize my device. I installed the driver for intel asus adb but it would says "error: device not found" for fastboot cmd.
so now i m stuck in fastboot and can't do anything ...
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Can you boot into bootloader mode what so ever?
Yes only into bootloader. Can't unlock again though. Won't let me.
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
Only can get into bootloader but cannot unlock again. Everything else is gone.
jdubya45 said:
Yes only into bootloader. Can't unlock again though. Won't let me.
Click to expand...
Click to collapse
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
stevew84 said:
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
Click to expand...
Click to collapse
Yes. Fails. Remote fail and not allowed.
jdubya45 said:
Yes. Fails. Remote fail and not allowed.
Click to expand...
Click to collapse
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
stevew84 said:
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
Click to expand...
Click to collapse
I am not sure. I think I need Unlocked bootloader.
Actually i think you just need to reunlock using depixel8. That should unlock your bootloader and allow you to flash new firmware
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Marghost said:
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
You have to be booted in Android for dePixel8 to work.
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
MArtyChubbs said:
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
He said that he tried to unlock the bootloader again and it won't let him. With a locked bootloader, you can't flash the system images.
Sent from my Pixel XL using XDA-Developers mobile app
Moderator warning,
I have cleaned this thread. XDA does not allow users to discuss fraud on this site.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
My mind is blown on how you accomplished this. Did you ERASE the partitions and then plan on flashing stock ones yourself? Why not just run the script (flash-all.bat) that would have automatically done the ENTIRE process for you, except re-locking the bootloader?
If all you did was re-lock the bootloader, it should have done a factory reset on the next boot and used the existing system partition. If you erased the system partition and then re-locked the bootloader, you are almost certainly screwed and had better hope Google has some mercy to let you RMA the phone.
Couple options you could try off the top of my head. The pixel has A/B patitions try adb sideloading an update zip to get it to switch to the backup partition that might still be there.
You could also try downloading the Factory images and extracting the system and go into fastboot and type
Code:
fastboot boot system system.img
and see if that works. Then if it boots on the temp image run deadpixel8 or whatever its called and reflash the stock image with the flash-all.bat.
have the same problem on my pixel after accidentally relocking after root before flashing back to stock.
Does anyone have the stock pixel xl recovery.img? I thinking if I boot into recovery "fast boot boot recovery.img" then I can add side load etc the ota from google.
jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Insert BRICK emoji here
Atlantian said:
Insert BRICK emoji here
Click to expand...
Click to collapse
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer? ?
thank you!
Blooddrunked said:
Hello!
i have got a Problem...
my usb c port is broken. the only thing that is working is loading the battery.
i can factory reset the smartphone for return to google, but my problem is the bootloader. any ideas, how i can relock the bootloader withput using my computer?
thank you!
Click to expand...
Click to collapse
if you're returning it to Google they don't really care if it's locked or not. I've sent them back for an RMA both ways never had any problems
Agree, relocking shouldn't be needed for a RMA...
Just make sure your device is completely stock at the very least.
Personally, I'd flash the factory images to both slots and lock the bootloader. However, if others have suggested they don't have any issues sending it back with the bootloader unlocked, then just flash the factory images.
Although, it is just one command to lock it (just be absolutely sure you're completely stock before locking, if you go that route).
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ?
Click to expand...
Click to collapse
You can't, and don't worry about it.
Blooddrunked said:
thank you All! but i need to get the stock recovery... how can i install the Stock recovery without an pc and without twrp? because i have the twrp edition with the encryption problem on Android pie... ??
Click to expand...
Click to collapse
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Badger50 said:
You could download the OTA zip and move it to your data folder with a root explorer type app, then flash it with twrp. Will twrp not decrypt without screen lock security?
Click to expand...
Click to collapse
Thank you! it worked!
Blooddrunked said:
Thank you! it worked!
Click to expand...
Click to collapse
Well there ya go! Your welcome. :good::good:
how long does it take to get the replacement from google??
That's exactly why I never unlock the bootloader, root, install custom ROMs, etc. I don't want to be in the situation where I can't use my warranty or insurance.
kismetmookz said:
how long does it take to get the replacement from google??
Click to expand...
Click to collapse
My bootloader was unlocked and it was not an issue. I sent my phone back and got a new phone in 6 days. I guess it would also depend on where you live. I live on the east coast and sent my phone to Texas and they sent me a new one from Illinois.
please help me
i got bootloop when clean flash and lock bootloader
but when unlock bootloader again it boot normally
royalcrown01 said:
please help me
i got bootloop when clean flash and lock bootloader
but when unlock bootloader again it boot normally
Click to expand...
Click to collapse
If you can unlock the bootloader again, I'd guess the flash didn't manage to erase everything.
Normally you'd have to boot and enable OEM unlocking before being able to unlock bootloader.
royalcrown01 said:
please help me
i got bootloop when clean flash and lock bootloader
but when unlock bootloader again it boot normally
Click to expand...
Click to collapse
Did gsi android 10 flash recently?
if the answer is yes
with the bootloader unlocked you must boot twrp and flash stock-repartition.zip
You can now block the bootloader in stock without bootloop
royalcrown01 said:
please help me
i got bootloop when clean flash and lock bootloader
but when unlock bootloader again it boot normally
Click to expand...
Click to collapse
There is another way too. Put your phone in EDL mode (fastboot oem edl) and flash the stock rom again. Even with clear_all_lock option enabled ,your phone won't lock your bootloader. When the phone boots up after flash,and you see the boot screen wait until you see erasing circle,after the second reboot,hold VOL - and power button until you go in fastboot mode. Then on your PC type: fastboot oem lock. The phone will boot up,then it will erase user data ,and you are ready with locked bootloader. I didn't have the stock repartition script ,so that's what i did.
Sent from my Xiaomi Mi A2 Lite using XDA Labs
Alijosekt said:
Did gsi android 10 flash recently?
if the answer is yes
with the bootloader unlocked you must boot twrp and flash stock-repartition.zip
You can now block the bootloader in stock without bootloop
Click to expand...
Click to collapse
Yes gsi android 10 is recently flashed
Can you give me link to stock-repartition ?
a1291762 said:
If you can unlock the bootloader again, I'd guess the flash didn't manage to erase everything.
Normally you'd have to boot and enable OEM unlocking before being able to unlock bootloader.
Click to expand...
Click to collapse
I tried but not helped
royalcrown01 said:
I tried but not helped
Click to expand...
Click to collapse
Well I told you the 100% working method so...
nikoman1987 said:
Well I told you the 100% working method so...
Click to expand...
Click to collapse
Problem solved with flashing stock_repartiting.zip
royalcrown01 said:
Problem solved with flashing stock_repartiting.zip
Click to expand...
Click to collapse
Nice to hear that! Sometimes flashing custom ROMs can be very frustrating
royalcrown01 said:
Problem solved with flashing stock_repartiting.zip
Click to expand...
Click to collapse
link for stock repartition zip?
melekbarca said:
link for stock repartition zip?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2-lite/development/10-0-android-q-daisy-t3967734
melekbarca said:
link for stock repartition zip?
Click to expand...
Click to collapse
http://4pda.ru/forum/dl/post/17164801/stock_repartition.zip
nikoman1987 said:
There is another way too. Put your phone in EDL mode (fastboot oem edl) and flash the stock rom again. Even with clear_all_lock option enabled ,your phone won't lock your bootloader. When the phone boots up after flash,and you see the boot screen wait until you see erasing circle,after the second reboot,hold VOL - and power button until you go in fastboot mode. Then on your PC type: fastboot oem lock. The phone will boot up,then it will erase user data ,and you are ready with locked bootloader. I didn't have the stock repartition script ,so that's what i did.
Sent from my Xiaomi Mi A2 Lite using XDA Labs
Click to expand...
Click to collapse
Worked for me, thanks man.
,
Cremig said:
Worked for me, thanks man.
,
Click to expand...
Click to collapse
no problem
royalcrown01 said:
please help me
i got bootloop when clean flash and lock bootloader
but when unlock bootloader again it boot normally
Click to expand...
Click to collapse
I have same problem ..
robin_vilensky_ said:
I have same problem ..
Click to expand...
Click to collapse
If it works unlocked but not locked, something is modified. Leave it unlocked or flash a complete stock rom.
a1291762 said:
If it works unlocked but not locked, something is modified. Leave it unlocked or flash a complete stock rom.
Click to expand...
Click to collapse
1 I downloaded original firmware from xiaomi web site very 10.0.13
2 I moved all files to adb tools folder
3 I run the cmd file flash_all_lock.bat
4 phone rebooted and got boot loop only entered to recovery mode.
5 and yes he booting only with unlocked BL
Alijosekt said:
Did gsi android 10 flash recently?
if the answer is yes
with the bootloader unlocked you must boot twrp and flash stock-repartition.zip
You can now block the bootloader in stock without bootloop
Click to expand...
Click to collapse
Can you give me the stock-partition.zip?
robin_vilensky_ said:
1 I downloaded original firmware from xiaomi web site very 10.0.13
2 I moved all files to adb tools folder
3 I run the cmd file flash_all_lock.bat
4 phone rebooted and got boot loop only entered to recovery mode.
5 and yes he booting only with unlocked BL
Click to expand...
Click to collapse
Probably something failed to flash. I don't know how much error checking the script has. Try again? Take note of the output, looking for warnings and errors.