Can go to BL and "fastboot set_active a" then reboot to go from b to a. No problems switching a to b in TWRP or BL by set_active command. The real problem is that if I try to update and forget to go to BL I get bricked and have to run blankflash.bat.
Which takes me to a locked BL where I can't boot TWRP via fastboot...
I thought I got out the first time but I have not been able to recover without flashing stock which wipes or makes data partition unrecoverable.
Anyway... WTF did I do to BL to make it detect that it is locked when I have unlocked, and never relocked BL.
Any insight would be greatly appreciated, thanks.
What are you updating to? There was a run of 15.1 ROMs that would result in bricks. It's fixed now- so if you are trying to flash a really old rom, try flashing the latest.
Related
hi i have done sum thing terrible to my phone and now i can only asses the boot loader cant get in to OS or recovery,
unable to flash new recovery and after trying to flash stock RUU i am stuck with boot loader relocked have tried to re unlock it but no luck.
s-on with os 7.19.401.2 any ideas on what to do?
Necrolog_92 said:
hi i have done sum thing terrible to my phone and now i can only asses the boot loader cant get in to OS or recovery,
unable to flash new recovery and after trying to flash stock RUU i am stuck with boot loader relocked have tried to re unlock it but no luck.
s-on with os 7.19.401.2 any ideas on what to do?
Click to expand...
Click to collapse
What steps did you take that led you to this point? Are you stock recovery at minute or are you custom recovery? Is your phone detected by fastboot (type fastboot devices)
Also I assume to tried HTC.com/dev to unlock using a different unlock token?
stovie_steve said:
What steps did you take that led you to this point? Are you stock recovery at minute or are you custom recovery? Is your phone detected by fastboot (type fastboot devices)
Also I assume to tried HTC.com/dev to unlock using a different unlock token?
Click to expand...
Click to collapse
just for future reference, he needs to flash the stock firmware, same one he already has, my suspicions say he has re-locked his bootloader with a custom recovery on there, thats why he cant unlock his bootloader, it requires stock recovery, the only way to get stock recovery on an s-on and re-locked device is to flash stock firmware. :good:
Seanie280672 said:
just for future reference, he needs to flash the stock firmware, same one he already has, my suspicions say he has re-locked his bootloader with a custom recovery on there, thats why he cant unlock his bootloader, it requires stock recovery, the only way to get stock recovery on an s-on and re-locked device is to flash stock firmware. :good:
Click to expand...
Click to collapse
Yeah I figured he'd done that, which is why I wondered was he custom recovery
thanks for the reply’s, i have now tried to use a new unlock token but i get the same problem as before, before i relocked the boot loader i flashed what i think was the stock recovery but now i can’t get in to recovery i can use fastboot and it does show up under fastboot devices and when i try to put the unlock token on i get the screen to confirm but when i confirm it boot into recovery and just stays there till the battery drains on i reboot it any more idea’s or advice ?
I installed the CM11 for this phone, I know not perfected yet, but it started having issues so I figured I would just go back to non-sense and be done with my CM11 trial.
At first I was just having trouble mounting DATA, then after a few reboots into TWRP 2.8.7.0 -- I lost my CACHE partition as well.
I tried using the RUU, but failed for SECURITY. I can't flash any ROMS (no DATA / CACHE) -- So I am stuck. FASTBOOT works, and I have access via TWRP, but thats it.
Carrier is Virgin Mobile.
Phone is U.S. 32-bit
Been rooted and working since we got root.
Any advice on how to proceed? Can I rebuild partitions from inside TWRP (command line?) can I find something that can be FASTBOOT or installed some other way?
Going back to stock is fine for now, what I am shooting for since it got all buggered up. And no I can't install BACKUPS either. Need partition access first..
Sorry, I think ADB is working, just can't do anything again because of the inability to mount the DATA & CACHE partitions.
The RUU failed by security because you have bootloader unlocked. Try to re-lock bootloader and re-install the RUU. That should work fine.
Been a while since I messed with this model, how do I re-lock bootloader?
****derp.
To re-Lock your bootloader Load phone into FASTBOOT and issue fastboot oem lock from command prompt. Phone will reboot and show RELOCKED.
Reboot phone in fastboot.
In adb, check with "fastboot devices" that your device is connected.
Then, in adb, type:
Code:
fastboot oem lock
And now you will have bootloader relocked.
PS: The phone only will reboot in Bootloader. That's because you don't have any OS installed.
To install the RUU, only plug the phone in fastboot and open the RUU program.
Thanks for help. seems all better now.
I was flashing system partition via dd .. Yeah stupid I know.. Some how boot loader locked itself previously.. My system is incomplete.. Won't boot.. Stock recovery and locked boot loader.. If I try to unlock boot loader via fastboot I get error about Dev options which I can not get to... Please help!
Will rsd lite still flash? Why did my boot loader lock itself ? Something new? New boot loader or new android do this?!
urhaxable said:
I was flashing system partition via dd .. Yeah stupid I know.. Some how boot loader locked itself previously.. My system is incomplete.. Won't boot.. Stock recovery and locked boot loader.. If I try to unlock boot loader via fastboot I get error about Dev options which I can not get to... Please help!
Click to expand...
Click to collapse
Sounds like RMA to me.
i dont get how bootloaders magically lock themselves, unless a script was run that issued the relock command..
one of the ota updates locked boot loader I believe, as I always leave my bootloaders unlocked for rescue, always testing different rooms, etc.. as well as it locking my bootloader it also required you to boot phone and go to developer settings and enable oem unlock there before you can fastboot oem unlock...
or maybe some other chaos locked my bootloader, idk..
fortunately I was under warranty, and phone was wiped good enough for them to not see phone was rooted or just didn't care and Motorola sent me a new phone...
I had a stock Nexus 6 onto which I loaded the MarshMallow previews.
I then decided to go back to 5.1.1 on the basis of the final release using the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Once I had entered the final fastboot command I also stupidly entered the command to lock the bootloader prior to rebooting
Some thing went wrong and now the phone sits on the google (while letters on black background) screen on bootup.
What are my options? I can access the bootloader, but its not showing up as a device on the on "adb devices"
Any assistance would be appreciated.
Sorry to say, but you've got a paperweight.
If by some chance you switched out the stock recovery.img with TWRP you're good, but otherwise, nope.
And in bootloader you use fastboot, as in "fastboot devices", not adb.
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
petermuell said:
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
Click to expand...
Click to collapse
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Didgeridoohan said:
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Click to expand...
Click to collapse
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
danarama said:
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
Click to expand...
Click to collapse
Hmm... This got interesting. It should survive a factory flash then.
@mittu1 Did you have OEM unlock allowed prior to locking your bootloader? If so, please, please, please run the command fastboot oem unlock and return with the result.
Yes, if you have stock recovery and can't unlock bootloader (probably because "allow OEM unlock" was not checked, or whatever reason), then you're pretty much stuck. Maybe then try this: http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I think it was intended for people who had downgraded their bootloader accidentally.
There is a zip file for flashing that toggles the "allow OEM unlock" flag (http://forum.xda-developers.com/showpost.php?p=61258590&postcount=352). If you can boot to twrp and flash a zip from the computer, flash that file, then boot to bootloader and unlock BL via fastboot.
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
If you have a custom recovery (TWRP) you can, after running those commands, flash a rom through TWRP and then proceed to boot up, tick "OEM Unlocking", unlock and do whatever you then intended to do.
Edit: Or use the above mentioned zip to toggle the "OEM Unlock"-thingy...
As i understood the OP the recovery is stock also. But somebody wrote the above, and as last resort it could be tried. And if it's false info, then let's have it clarified.
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
They should, but if not, a foctory reset can be done from stock recovery. Select recovery mode, then at the Android press power and then volume up. Then select the factory reset from the menu. See if it boots after that
BUT try fastboot oem unlock first, if you wipe without that and then try to unlock I think it'll fail to unlock
Didgeridoohan said:
Hmm... This got interesting. It should survive a factory flash then.
Click to expand...
Click to collapse
No, it is just my assumption. I am not aware if something in first boot process unchecks that option.
Also, FYI, many of us have noticed that when we bought Nexus 6 and unboxed it, booted straight to bootloader, it would unlock, but after first boot on 5.0, had to enable OEM unlock in settings... so maybe first boot process after a "wipe" resets?
Will try and revert
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.
You need to flash stock through EDL
Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.