Hello guys, I unlocked and then locked the bootloader after an attempt to bring back the 1+2 to stock.
I have used TOOL ALL IN ONE by MAURONOFRIO to do all this stuff.
Now I want to unlock the bootloader to try the CM13 , but when I write
fastboot oem device-info
It tells me that
Device tampered: false
Device unlocked: false
It seems like I can't unlock the bootloader, no matter how I try. Also I do not have the root so I can't follow this other guide.
Do you have any tip to help me out?
Ok I just wiped data.
Now it says:
tampered: false
unlocked: true.
Now it seems like I can't flash the recovery.
I have used the same tool from before, it didn't work.
So I just used:
fastboot flash recovery *filename.img*
and it still goes back to stock recovery.
Any ideas?
Make sure you boot into recovery before letting the OS boot. If its stock OS it will replace the recovery if you let it boot. This may also be a big help http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568/page1 Go to first post and then how to install custom recovery.
Thank you, I solved the issue Now I have the latest CM13 and it works really good. Thanks!!
Related
This is freaking bizarre. I have been banging away on this phone for hours, but have not been able to unlock the bootloader since it's a VZ device (No OEM unlock in developer options, and therefore Killswitch prevents me from getting the HTC code). But... I successfully flashed TWRP on a lark, installed SU, and am now rooted with NO bootloader unlock and NO DATA WIPE from installing TWRC. My fastboot/download mode screen still says LOCKED.
Someone, please verify this because it's too freaking weird. I used the XTC2 clip for S-OFF, but since it was direct mode I'm wondering if I can't just slurp the comms and make a simple tool for S-OFFING. A topic for another day.
Here's what I did.
TO SOFF
Reboot into download mode (PWR+DN) with XTC2 in M9's microSD slot. (XTC2 is registered, activated, and updated).
Use XTC2 tool to Read phone info just to test connection.
Use XTC2 Tool "Direct Mode Commands" tab to Write security to 0. Takes about a second, and ends up with OKAY when done.
Key down on the phone to select "Reboot to download mode"
After reboot, it will say S-OFF. However, bootloader is still locked and will say *** LOCKED *** at the top.
Next, I tried several different things that didn't work.
1) XTC2's bootloader unlock - blocked by Killswitch
2) Manual bootloader unlock with adb and htcdev - blocked by Killswitch.
3) Run TWRC without flashing (fastboot boot twrc.img) but just got rejected by "Under Flash".
Then finally out of desperation, I rebooted to download mode and tried to flash TWRC... Which worked. On a locked bootloader??? I used the XTC console to send it, but I think that it is the same as fastboot.
flash recovery twrp-2.8.7.0-hima.img
------------------------------------------------------------------
sending 'recovery' (36288 KB)... OKAY
writing 'recovery'... (bootloader) HOSD CL#xxxxxx
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
Execution time is 5461(ms)
OKAY
------------------------------------------------------------------
The damn thing said the flash was successful! So I rebooted to bootloader, then to recovery - and got the TWRP menu! Installed su and rebooted to the system. The phone is rooted, but no data has been lost since it was never unlocked.
This is a very curious case, so if anyone would be kind enough to try to reproduce it I'll be happy to assist with any info I can give.
Big Bada Bump!
Isn't this forum for M9+, not the regular M9?
Dont know much about forum mechanics. Any way this thread could be moved to its proper place? I think we should keep this one alive... My m9 longs for its freedom!
I dont know excatñy why this happened but you are a lucky guy! =d specially since it is a verizon phone and you didnt kill it no matter how hard you tried!!!! Awesome pal!
truly weird...
i went a very similar route - i got twrp installed with the bootloader still locked, but s-off and super-cid via xtc2 direct commands.
i was able to use twrp to install SuperSU, but my phone hung on reboot.
the only way to recover was to flash a stock verizon RUU...
i was able to get xtc2clip to unlock my bootloader though - long story, check my latest thread.
anyway - kudos to you, and good luck!
I think you don't need to unlock BL if you're s-off (correct me if i'm wrong) to be able to flash imgs. I have s-offed 2 M9s and 2 M8 (not VZ though) using XTC2Clip, did not unlocked BL but still flashes imgs
Hello.
Long story short:
I have a OnePlus2, I can boot in Fastboot mode and my PC does recignize the fastboot device.
fastboot oem device-info says that Bootloader is locked and when I try to unlock (fastboot oem unlock) it states "okay" but cannot boot into system because there is none installed. -> Bootloop
I cannot boot into recovery nor install a recovery due to the locked bootloader.
My Question:
Is there a way to unlock the bootloader in fastboot and/or install a boot.img?
I am happy for any help that I get.
Have a good day/night
SoulSnatcher
No, but why you don't have system?
You have stock recovery download official signed full zip and flash it. Recovery.
Also unbrick guide using the one you need Qualcomm drivers
Sent from my ONE A2005 using Tapatalk
I'm trying to take my phone back to as stock as possible. Using the requested official firmware pack from Motorola when trying to flash motoboot.img through fastboot it fails everytime saying (bootloader) has-slo:motoboot: not found... error: cannot load "motoboot.img" . Also, when trying to relock my bootloader after typing fastboot oem lock begin it says (bootloader) Please fully flash the signed build before locking phone!
I'm assuming that since motoboot.img isn't flashing that's why it says please fully flash the signed build, because everything else is flashed properly. The phone boots fine and all I'd just like to get rid of the bootloader unlocked screen and have it stock.
Because there is no "motoboot.img" in the zip, only "boot.img" and "bootloader.img".
Ah true, but the command to lock the bootloader still says "Please fully flash the signed build before locking phone!" Any ideas?
"OEM lock begin" says that. You just proceed. The phone is locked at the end with "OEM lock" command.
Lol... OK. so I started over with the fastboot commands using "fastboot oem lock begin" before flashing the rest of the items from the Moto firmware zip. When I get to the system.img I get (bootloader) Invalid signed image and (bootloader) Preflash validation failed.
This phone is ridiculous, back to the nexus 5x... this thing can sit in a drawer and rot
When this happened to me, I just restored via TWRP the stock image backup and flashed stock recovery via fastboot. After that you can flash the same rom via fastboot and lock it but where's the point to lock it anyway? Motorola knows that you unlocked it. And no, the phone is not ridiculous and imho much better than N5x. [emoji4]
Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new
I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.
I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"
AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.
And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.
no I have no phones now with similar problems, but at different stages of the same issue.
My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)
and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.
ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
Have you tried the fastboot oem unlock command?
DR_HAX34 said:
Have you tried the fastboot oem unlock command?
Click to expand...
Click to collapse
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"
I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
I'm currently on lollipop stock firmware with phone rooted and bootloader unlocked. I have also flashed latest Twrp recovey.
But here is the problem, i downloaded Resurrection remix latest version and tried to flash it, but error 7 came up. I bypassed this error by editing the updater script ( i followed a tutorial ). Now when i flashed the rom it says its sucessful but when I select boot to system it goes to fastboot mode. Im a noob so please dont be harsh to me.
PLEASE HELP ME FAST
THANKS
You still need to upgrade to stock MM before flashing RR M.
24imelqui said:
You still need to upgrade to stock MM before flashing RR M.
Click to expand...
Click to collapse
WIll I have to unlock my bootloader again when i go to stock MM.
abhishek_los said:
WIll I have to unlock my bootloader again when i go to stock MM.
Click to expand...
Click to collapse
No, but to be sure go to fastboot the type:
fastboot oem device-info
if you see this -->> (bootloader)Device unlocked: true
then you are still unlocked.
24imelqui said:
No, but to be sure go to fastboot the type:
fastboot oem device-info
if you see this -->> (bootloader)Device unlocked: true
then you are still unlocked.
Click to expand...
Click to collapse
Thanks man it worked and i am able to flash Resurection remix.
Thanks a lot again
Glad I was able to help. Warning, flashing can be addictive! And make sure to have a nandroid back-up.
WRT the original post, I tried the same procedure but after having errors i flashed the twrp with adb through cmd:fastboot flash boot boot.img . And now it is showing no OS available and shows that it is not rooted in the twrp recovery. Now it is still not flashing the rom and showing error and now i have no idea what to do. So, please give me instructions on how to repair my asus zenfone 2 laser ze550kl. I did all this on MM.
If you have TWRP 3025 then you can flash any custom ROM. Try to redownload the ROM, maybe it's just a bad download. What error did you see?