Related
As title says, but we need a working backup. Mine is broken, can someone upload a working one, plz?
This is the howto:
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Thanks for this solution. But I have a problem because after installing the rom file .tot have a locked bootloader, and at this moment I can not do flash twrp.
In order to unlock the bootloader command "fastboot oem unlock" I get the answer that it is not possible. NTR it can not unlock it.
Goes some way to upload twrp with a locked bootloader or a way to unlock?
Danielf85 said:
Thanks for this solution. But I have a problem because after installing the rom file .tot have a locked bootloader, and at this moment I can not do flash twrp.
In order to unlock the bootloader command "fastboot oem unlock" I get the answer that it is not possible. NTR it can not unlock it.
Goes some way to upload twrp with a locked bootloader or a way to unlock?
Click to expand...
Click to collapse
My bootloader is locked, too. The only way to write to the phone seems to be via download mode, but flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot doesn't work...
To install twrp we need to unlock the bootloader.
However, when the command "fastboot oem unlock" system gives the answer
FAILED (remote: oem unlock is not allowed)
Then how to unlock?
Danielf85 said:
To install twrp we need to unlock the bootloader.
However, when the command "fastboot oem unlock" system gives the answer
FAILED (remote: oem unlock is not allowed)
Then how to unlock?
Click to expand...
Click to collapse
There's really nothing you can do to force an unlock. If you can adb sideload a full OTA zip (say for 7.0) from Google and get that to boot up, that's pretty much your best bet.
Sent from my Nexus 5X using Tapatalk
I mean, the new unlock command is:
fastboot flashing unlock
oc2 said:
I mean, the new unlock command is:
fastboot flashing unlock
Click to expand...
Click to collapse
On Nexus 5X both commands can be used (oem unlock and flashing unlock)
I followed all the steps except I can't boot to recovery...when I try (manually via ADB or automatically using Wug's tool) it just goes back into the bootloop. I can't even boot temporarily to recovery (without flashing). I'm getting close to throwing in the towel...
Did not work for me, sadly
Edit: Here's how I managed to fix the problem
1. Moved Nandroid backup to PC.
2. Download factory image MTC20F from https://developers.google.com/android/nexus/images.
3. Install factory image (This will erase all data on your phone so move your files to your PC).
4. Install TWRP 3.0.2-0 from https://dl.twrp.me/bullhead/twrp-3.0...lhead.img.html via fastboot.
5. Go in TWRP>Wipe>Advanced Wipe and repair all partitions that can be repaired (System, Data, Cache).
6. Restore Nandroid backup.
7. Success.
Hope it works for other people too, cheers
Anyone in Portland Oregon and want to take a crack at unbricking my 5x? LG gave me an RMA, but given it's not a hardware issue, I'm thinking it will be a waste of time to send it in -- I'm worried they'll just say "all your hardware is fine". Happy to buy drinks or pay a bit if someone can get me up and running.
Hello all,
I have Zenfone 2 on which I intended to use a custom ROM.
So the first thing was to unlock the bootloader.
On previous occasion, on my Nexus, I had used the - fastboot oem unlock - command and it had worked. So with that in mind, I booted into the bootloader and tried the command, but it failed - saying oem command unrecognized.
Then I searched online and apparently, to unlock the bootloader, Asus has launched an app! But to be able to install the app, I need to get a normal boot happening, which is not happening now.
In between all this, I tried the commands - fastboot flash recovery <recovery.img>, fastboot flash boot <boot.img> too. But none of these were successful, and each of them returned a 'Permission denied' message, probably coz the bootloader was locked.
Now the situation is that -
- Bootloader is locked.
- Phone is stuck in bootloader
- There is no recovery installed. In fact, from the bootloader, when I try to boot into 'Recovery Mode', it goes there for a second and returns back to the bootloader. Doesn't show the normal android image with a 'X' on top.
- There is no root access.
Now I think the first step is to get root access, and for this I want to try the method with installing CWM recovery and SuperSu.
But for this, I need to be able to push the SuperSu.zip to the phone, which I am not able to.
Can somebody please help!
r the drivers for fastboot & adb update to date?
Android version?
If the phone is stuck in bootloader, you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Raw files: https://yadi.sk/d/FijRoAVJtvRiG
AFT: https://yadi.sk/d/NQCiY--IsQjBr (I use AsusFlashToolInstaller1.0.0.14.exe).
you can use Asus Flash Tool to flash .raw files and unbrick the phone.
Click to expand...
Click to collapse
Have to choose wipe the data or not?
hafiz019 said:
Have to choose wipe the data or not?
Click to expand...
Click to collapse
stay away from aft. if will f**k up yor device completely. AFT is too unstable. lot of times it bricks the device to unrecoverable state. tell me the bootloader version, ifwi version shown on screen while in bootloader mode.
I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?
ghtcp said:
I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Did the PC shut down or the phone?
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
If unlocked you can fastboot the firmware as you normally would
Dobsgw said:
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
Click to expand...
Click to collapse
You can flash images with Mi Flash on locked bootloader no problem.
marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
They can try but if recovery isn't accessible then fastboot is the only option and without unlocked bootloader you cannot use it.
Test point is then the only way.
Obviously its best to try flashing without opening the phone first.
marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
Wtf! You can't use mi flash tool unless your bootloader is unlocked
The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END
ghtcp said:
The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END
Click to expand...
Click to collapse
The bootloader gods have smiled upon you this time
Hello! I have locked bootloader with "fastboot oem lock". I was in panic, but randomly I press "Volume -" + "power-on" and my Mi A1 have loading in Fastboot mode, where I was able to unlock bootloader again.
Hope, this can help you.
HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone
same issue in redmi note 4
indersethi said:
HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone
Click to expand...
Click to collapse
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....
Basilp275 said:
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....
Click to expand...
Click to collapse
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.
ccelik97 said:
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.
Click to expand...
Click to collapse
Yes,it's worked
Basilp275 said:
Yes,it's worked
Click to expand...
Click to collapse
Cool then ?
I had the same problem today. my phone was distroed when I tried to install Gcam.
my phone was not unlocked so that the flash of the new stock of the ROM was not possible. The solution is to connect the phone to a PC in fastboot mode and from the platform tools in cmd to type fastboot oem unlock. After that, I did not have to have a flash phone. Everything worked as if I only had to backup the data.
now I have a new phone.
People, with Mi A1, cling to two things - slot A or slot B and lock or unlock. The easiest way to do this is a cardinal error.
Greetings.
Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?
jesus4android said:
Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?
Click to expand...
Click to collapse
With locked bootloader I got no chance to flash anything. Neither fastboot nor MiFlash - any solutions? Also would be helpful to enabke USB Debugging via fastboot. Anyone knows?
If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!
I want to sell my Google Play app developer license.
Please email me or call me if you are interested.
phone - +917007797787
Email- [email protected]
I got a bricked Mi 6 from a friend. He was trying to flash firmware, and somehow messed up. Trying to boot normally or into recovery showed "The system has been destroyed". `fastboot continue` did not work. Bootloader was locked ( = no possibility to do fastboot oem unlock). On top of that, the phone only accepted fastboot commands right after the usb cable was connected ( => I had to run a fastboot command, like `fastboot getvar all`, fastboot would output `< waiting for any device >`, then I connected cable, and it would work). Running fastboot commands later resulted only in fastboot hanging / getting stuck, with no output, can not be terminated with ctrl+c unless cable was disconnected.
I got myself a windows computer (I use linux), tried to do bootloader unlock. Failed on "add your mi account in Settings -> Developer -> blablabla" - no way to do that with a bricked phone. Then I found out about EDL (Emergency download) mode. This is what worked.
The only way to get into the EDL mode in this state was the hardware way (shortcutting the pins / "PCB test points"). Search online for "mi 6 edl mode testpoints". Basically, you have to:
1. remove the rear cover
2. remove the screws on the plastic part above the battery, remove the plastic piece
3. disconnect the battery (shorter connector on the left side)
4. shortcut the pins using a tweezer (the pins are just above the battery connector)
5. while the pins are connected, connect the USB cable
6. check in device manager that you have "HS-USB QDloader 9008" in the COM devices
7. use mi flash tool to flash the fastboot firmware
The pins (from https://www.mobilerdx.com/2019/02/xiaomi-mi-6-test-points-xiaomi-mi-6-edl-mode-pinout.html):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And after you succeed, maybe unlock your bootloader, so that you don't have to do this again
Hi,
I'm new to Z2 play ROM/TWRP things and here's my issue on a XT 1710-01 (on retca channel):
After unlocking my bootloader, I've installed TWRP 64 bits and did a backup before doing anything else, but for whatever reason, restoring it didn't work. I just thought then that I could re-flash the retail stock ROM available at https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ , which worked fine (phone boots fine, works fine and is still on retca channel, etc.), except that now, I'm unable to re-lock the bootloader, as I get a message like "signed boot.img required" (or something alike) on "fastboot oem lock" command.
I also get the "bad key" message on the unlock warning at boot time (see attached).
Here are the commands I used to reflash the stock ROM:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Now, I'm just wondering if I missed something or is it just that the stock ROM I reflashed is not the good one (or just unsigned) . Any help would be appreciate.
Thanks.
Need official signed by Moto image. Not available from any official source unfortunately. I have a same request to lock a bootloader.
it's very important to ask how your parachute Works before you jump off the plane
@KirMit Thanks for the follow-up.
Do you know if it would be an option for me to try to find a complete ROM/backup made by someone with the exact same model (so presumably, with the signed boot.img), flash/restore this backup on my unit and then try to relock the bootloader?
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Paulinga said:
I have the same problem. Cannot find a signed boot.img
If anyone can think of a solution I would be totally interested in hearing about it.
I can live with this phone with the bootloader unlocked, but I may need to sell it, so I need to get rid of that warning screen.
Click to expand...
Click to collapse
You can get rid of the warning screen, but you can't get rid of the N/A-Bad Key sign, so you must make your own boot logo (meant to cover those nasty letters with a white background) and ADB flash it as logo.bin... that's if you don't have TWRP recovery; in such case you can use a flashable zip for that matter.
Sent from my Moto Z2 Play using XDA Labs
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
xdaVTU said:
Please look at this video:
It's in portuguese, but you will understand by just following his steps.
If you want, look at the other videos, all of them will help you(not all are about relocking bl)
If you're on october patch, there is the firmware: https://androidfilehost.com/?fid=11410932744536987421
Thanks to junior passos
Click to expand...
Click to collapse
Doesn't work on my Z2p. My oem unlock is always greyed out even after trying the instructions in this video with 3 different firmwares.
For anyone who doesn't understand what's going on in the video.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system and reboot
4) go to developer options and, enable oem unlocking
5) return to bootloader and run the lock bootloader bat file.
6)done your locked.
Or if like in my case, it does not work, oem unlocking is still greyed out.
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Cupcake 1.5 said:
I managed to ungrey oem unlocking but, only by flashing magisk. Somehow magisk ungreys oem unlock? Unfortunately, we cannot lock bootloader with magisk installed. Once magisk is uninstalled, oem unlocking is greyed out again?
I think I know how to get around this, adb pull boot.img that magisk has modified. Full unroot magisk, preferably with magisk uninstall zip. Then fastboot flash the patched boot image and run bootloader lock with the OEM unlock switch set.
---------- Post added at 10:32 PM ---------- Previous post was at 09:49 PM ----------
And I am locked, it worked. I now know how to lock my bootloader even when the video guide above fails to remove the greyed out oem switch.
1)flash the firmware.
2)flash twrp, backup boot & system.
3) restore boot and system
4)flash magisk and reboot
6) back up boot.img to pc
7) flash magisk uninstall zip
8)fastboot flash stock recovery
9) fastboot flash magisk modified boot
10)boot device and enable oem unlocking
11) reboot to bootloader and run bootloader lock bat file
11) oem locked!
By the way, easiest way to back up boot is use the app "partition backup & restore". Be sure to change the setting to save as img and not archive.
Click to expand...
Click to collapse
TravellingGuy said:
Yes! This!
I've never been able to go back to stock and relocking the bootloader because the OEM Unlock was always greyed out. Using the patched boot.img, as @Cupcake 1.5 explains allowed me to lock my bootloader again.
Thank you!
Click to expand...
Click to collapse
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
smbld said:
Hi all, ok i'm late unfortunately can you help me ? i have the boot magisk signed and key is ok. But when i'm reflashing recovery stock, there is also a bad key.
So there is still the warning at startup, i think this is due to this issue
Click to expand...
Click to collapse
Ha, it's been too long since I used this phone. I can't help, unfortunately.
Hello all
I desperately try to relock my bootloader but failed many times and I am shortly before giving up. I was once on a locked bootloader on LOS but camera didn't work. (Couldn't reproduce)
Maybe you see something I missed out / didn't understand.
The main reason is, that some apps like ebanking check the state of the bootloader. And they also don't go through Securenet because of huawei.
So what I tried with this setup:
sign both boot.img and twrp.img with BootSignature.jar using own private key
Twrp Using: twrp-3.5.2_9-0-oneplus3
boot img from:
lineage-17.1-20210330-microG-oneplus3
lineage-18.1-20210403-microG-oneplus3
With firmware: oxygenos-9.0.6-firmware-3 from https://github.com/nvertigo/firmware-3t/tree/master/archive/op3
Mostly I got the ideas from https://forum.xda-developers.com/t/device-forum-rules-please-read-before-posting.3333345/
And what I do is this:
Using fastboot flash signed recovery
boot into recovery
whipe everything (is this needed every time?), data, factory reset, all partitions except internal & usb
reboot into recovery
sideload lineageos with signed boot.img inside
fastboot oem unlock => directly restarts after 'yes'
boot into LOS
fastboot oem unlock => directly restarts after 'yes' again
Do you see something I do wrong? Should I use other versions/files?
Hope to find a way
Edit: Also I can go back to stock where it gets locked again using the latest OnePlus3_16_A.86_191104_repack.