I rooted my oneplus 2 some time ago to install the Screencast.app that there was on the oneplus one. I then after a while noticed that it started to perform worse than before i rooted it, so i decided to try to unroot it to fix the performance. But when i rebooted to fastboot and tried to flash the stock recovery, it said that the bootloader was locked. I then tried doing the unlock command (fastboot oem unlock), and it seemed to work (although - it didnt - in cmd it said finish but when i booted into bootloader again it was still locked) but when my phone tried to reboot, there was i quick flash of the oneplus logo and then the screen went blank. When i tried turning it off, i just rebooted and did the same thing. I could not boot into recovery either. The only thing i could do was booting into fastboot and from there i managed to use the command fastboot continue and restart my phone properly. So now i cant use my recovery to factory reset, i cant install a new recovery because the bootloader is locked, and now every time my phones powers off, i have to do the same thing with booting into fastboot and do the fastboot continue command to start it.
Can anyone tell me what the issues is here and how i can solve it?
I have the same problem, but once I got the phone to boot, I did a factory reset. Now I'm unable to even boot, literally the only thing that works is fastboot.
Related
Hello everyone!
Okay, so I'll try to keep it as short as possible but with the most information I can give ofc.
So here's what I did with my Oneplus 2:
- unlocked bootloader
- flashed custom recovery (twrp)
- flashed superSU.zip
- flashed xposed.zip
- used it for about half a year if not even longer
everything on Lollipop 5.1 stock rom so xposed would work.
Everything was fine but some day when I wanted to enter twrp recovery it didn't work. (I swear, this is the most illogical thing ever but I DID NOT CHANGE A THING!)
I tried to enter recovery via fastboot but that didn't work either.
So I reflashed latest TWRP recovery.img for OP2 via fastboot.
When I pressed power + vol. down to see if it'd work nothing happened.
When I tried to enter recovery when my system was booted via power button->restart->recovery my phone got stuck in a bootloop.
I had to go in fastboot mode to enter "fastboot continue" in order to get my phone booting normal again.
Then, one night when my phone was in my pocket it vibrated and got stuck in the bootloop again, even though it was booted into system and locked last time I used it (minutes before that).
I had no access to a computer at that moment so I had to wait for a few days.
Now when I boot my phone in fastboot mode and try to enter "fastboot continue" on my cmd nothing happens with my phone and cmd says "(command write failed (Unknown error))" even though "fastboot devices" shows that my device is connected properly.
I also tried:
- the FirstAidKit, copied the Win Files in my fastboot directory and started the firstaid.bat but it stops on "fastboot flash boot boot.img" (I waited for like two hours).
- a different USB port (USB 3 and USB 2)
I am kinda depending on my phone so yeah..
If someone knows how to fix this I would be very grateful.
Have a good day/night
SoulSnatcher
Do you have a backup??
If yes, download the latest official OS from Oneplus and the stock recovery. Flash the stock recovery. Try rebooting into stock recovery. If it succeeds, wipe everything and flash OS via adb sideload.
Honestly, I can't guess what went wrong with your device. Maybe it could've been some app which crashed the entire system.
AJay27 said:
Flash the stock recovery.
Click to expand...
Click to collapse
Same problem as with the FirstAidKit:
"fastboot devices" does display the device but "fastboot flash recovery recovery.img" doesn't do anything (I waited for 1h just to make sure).
I'll try this Mega Unbrick Guide for A Hard Bricked OnePlus 2 next, even though I can get into fastboot but since it doesn't do s**t I'll have to give it a try. I mean, what's the worst thing that could happen? That my phone gets bricked?!
Haha.... hmm.
I'll keep the person(s) updated who care to know what's happening.
Cheers
fml
So my Nexus6p randomly restarted once (I had been on 7.0 since release date with no issues) and since then is stuck in bootloop on the Google Logo.
Holding the Power+Volume Down boots into bootloader. From there I can't get to recovery or even tried the factory reset from there and it always gets stuck on the Google Logo.
I have downloaded the SDK and while fastboot works, adb doesn't.
I can't flash anything through fastboot because boot loader is locked. I can't unlock the booatloader because remote oem unlock is disabled. I have never had the need to root or unlock bootloader, so never had USB debugging or allowing unlock checked under debugging tools.
Can't sideload OTAs since adb doesn't work.
Do I have any options to recover the device and make it work again?
kumarshah said:
So my Nexus6p randomly restarted once (I had been on 7.0 since release date with no issues) and since then is stuck in bootloop on the Google Logo.
Holding the Power+Volume Down boots into bootloader. From there I can't get to recovery or even tried the factory reset from there and it always gets stuck on the Google Logo.
I have downloaded the SDK and while fastboot works, adb doesn't.
I can't flash anything through fastboot because boot loader is locked. I can't unlock the booatloader because remote oem unlock is disabled. I have never had the need to root or unlock bootloader, so never had USB debugging or allowing unlock checked under debugging tools.
Can't sideload OTAs since adb doesn't work.
Do I have any options to recover the device and make it work again?
Click to expand...
Click to collapse
Do you just have stock recovery? If so, can you boot directly into it with power + vol up. If so, maybe try hitting stock recovery menu to side load ADB or factory reset? Otherwise, sounds pretty borked unfortunately.
Sent from my Nexus 6P using Tapatalk
Hi guys, I tried flashing stock rom and re-locking the bootloader so that I could have the phone completely stock. However, after re-locking the bootloader, I seem to have bricked the phone. I've scoured the forum for fixes, tried tenfar's tool, and nothing has worked yet. Hopefully someone has come across this situation before and can advise me on how to get my phone working again.
So how I got to this point.
-Originally the phone was on stock rom, rooted, with official TWRP recovery.
-Booted into TWRP, wiped cache, dalvik, data.
-Flashed ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip.
-Flashed ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip.
-Rebooted phone, went through initial setup, then turned on Allow OEM Unlocking in Dev Options.
-Rebooted back into TWRP, used Minimal ADB to fastboot oem lock.
So the phone rebooted twice from there, and seemed like it was going to boot properly, but the first screen that appeared was a lock screen asking for the password. I didn't set any passwords, and couldn't find any default factory passwords even looking through the zteusa forums on posts for similar situations. Then I tried rebooting into the bootloader to factory reset the phone, but trying to boot into the bootloader only leads to a black screen after the ZTE boot logo. That's where I'm currently stuck. No matter what I try, be it tenfar's tool, I can't get into anything but the black screen or the password-locked screen.
Using tenfar's tool, after I issue the axon7root.exe -p 3 command, it shows the next two lines, up to Version 1.10, then does nothing else. I'm not sure if this is because I flashed B29, and the tool only goes up to B27.
Any advice would be greatly appreciated!
Tennear's tool for flashing a boot and recovery image seems the most promising I think, but I don't quite understand how to use it.
-Rebooted back into TWRP, used Minimal ADB to fastboot oem lock.
Click to expand...
Click to collapse
First, you shouldn't (can't?) relock the bootloader while you're using a custom recovery. Additionally, I don't think you can issue fastboot commands to recovery.
Boot into TWRP and do a factory reset from there.
If not, flash the ZTE B29 image either via stock recovery (flashed via TWRP/tenfar's tool), or edit the install script to make it flashable via TWRP.
Hi guys...
So my OnePlus 2 was having some issues yesterday, and I flashed the stock ROM. This was completely fine and dandy, but I also wanted to put the stock recovery on it. I made sure OEM unlocking was on, went into fastboot, and typed in "fastboot oem unlock" like normal. It finished in like a tenth of a second which I thought was a little strange. The phone rebooted and I put it back into fastboot. I tried to flash the recovery and it said (remote device is locked. Cannot flash images). So at this point I was frustrated. I went into TWRP and installed the SuperSU binary. Then, I went to the Play Store, downloaded Flashify, and flashed the recovery onto my phone. I restarted my phone.... and bam. Recovery wouldn't work anymore. And then when I tried to boot into normal Android it still wouldn't work, just stuck on the OnePlus and Android screen, as if there was no /system/ partition. I can still get it into Fastboot, and I put it in EDL mode and installed the Qualcomm 9008 driver, and flashed OxygenOS 3.0.2 through the MSM downloader from https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ and the MSM downloader just gave me an error that, in garbage text, said something about Sahara and Firehouse or something like that. I did get it to go successfully by downloading a different recovery package (I believe it was Color OS 2.0) but I have a ONE A2005 and I belive that was meant for ONE A2001 and it caused my phone to constantly flash rapidly at the Oneplus and Android screen (it would start to boot then immediately shut off). Fastboot still works but it still says the bootloader is locked so I can't really do anything. Any help would be much appreciated!
Jack
Update: I finally got Recovery to work. However, it still gets stuck on the OnePlus & Android screen, even after sideloading a stock ROM and installing it via the stock recovery. I fear my boot.img is corrupted. Does anyone happen to know where I can find a stock ROM that comes with recovery.img, boot.img, system.img, et cetera?
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
superblox02 said:
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
Click to expand...
Click to collapse
You should be able to unlock it in fastboot or adb
OEM unlock or something like that
Check this thread https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
I recently got an LG G6 US997 with a stock ROM. I flashed it with TWRP and Lineage just fine, however the fingerprint reader wouldn't work. I flashed it back to a stock ROM using LGUP. Everything appeared to go just fine, however after it reboots it boots into fastboot mode and is stuck in a loop now. I've tried flashing it again, however the result is always the same, it gets stuck in a fastboot loop.
Does anyone have any suggestions?
Have you tried doing 'fastboot reboot' from cmd on a computer with the lg device drivers?
Mnky313 said:
Have you tried doing 'fastboot reboot' from cmd on a computer with the lg device drivers?
Click to expand...
Click to collapse
Thanks for your reply. Yes, it just boots back into fastboot mode.
Interesting, have you tried flashing twrp for the is you have and doing 'fastboot reboot-recovery' or try holding power and vol down, release power for a split second when you see the g6 logo and hold it again, go through the prompts for factory reset, it should open twrp, try wiping system and flashing a stock zip.
cortjehster said:
I recently got an LG G6 US997 with a stock ROM. I flashed it with TWRP and Lineage just fine, however the fingerprint reader wouldn't work. I flashed it back to a stock ROM using LGUP. Everything appeared to go just fine, however after it reboots it boots into fastboot mode and is stuck in a loop now. I've tried flashing it again, however the result is always the same, it gets stuck in a fastboot loop.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Do the button combo and try a factory reset.
Sent from my Nexus 6P
Mnky313 said:
Interesting, have you tried flashing twrp for the is you have and doing 'fastboot reboot-recovery' or try holding power and vol down, release power for a split second when you see the g6 logo and hold it again, go through the prompts for factory reset, it should open twrp, try wiping system and flashing a stock zip.
Click to expand...
Click to collapse
Looks like my first attempt to reply didn't post...
I can't flash TWRP because the bootloader is locked again (I assume because I flashed a stock ROM). Since the OS won't boot, I can't get into the developer options to enable OEM unlocking again.
I did try doing a factory reset, several times. Each time the colored circle would come up for a few seconds and then it would go back into a fastboot loop.
Have you tried attempting to unlock the bootloader anyway using the fastboot command?
Mnky313 said:
Have you tried attempting to unlock the bootloader anyway using the fastboot command?
Click to expand...
Click to collapse
Thanks for your reply.
I've tried "fastboot flashing unlock" and "fastboot flashing unlock_critical". Both returned with "FAILED (remote: unknown command)".
I also tried "fastboot flashing get_unlock_ability" which returned "(bootloader) get_unlock_ability: 1". I'm not sure if that 1 means true that it can be unlocked or something else.
If I do a "fastboot getvar unlocked" it returns "unlocked: no" which is how I know it's locked again (after the flash back to stock).
i have the same problem..anyone can get it fix?
cortjehster said:
I recently got an LG G6 US997 with a stock ROM. I flashed it with TWRP and Lineage just fine, however the fingerprint reader wouldn't work. I flashed it back to a stock ROM using LGUP. Everything appeared to go just fine, however after it reboots it boots into fastboot mode and is stuck in a loop now. I've tried flashing it again, however the result is always the same, it gets stuck in a fastboot loop.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Have you tried this command
fastboot oem fb_mode_clear