So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Yes, it does.
What I would do if I was stuck in a bootloop (well thats what I did when I soft bricked my phone "NO OS INSTALLED" now it works again )
is go here https://cyngn.com/products/oneplusone/ download the cm-11.0-XNPH38R-bacon-signed-fastboot.zip extract it in your fastboot folder (make sure you have the latest sdk tools from google or else with an older version it will say that system.img is too large when you flash the zip), open a cmd (run as administrator). check if your bootloader is still unlocked (mine got locked so I was facing a similar situation) type fastboot oem device-info ....it should say unlock true.... then
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
hope it works
hermunn123 said:
So I'm in the precarious bootloop nightmare... and I'm pretty noobish at Android on the "developer" side, I'll say. I also didn't have USB Debugging enabled when my phone randomly decided to freak out on me.
I tried the fix found here:
Edit: I can't post links yet. The fix is found at Android Police. Story is titled: Here's An Easy Fix For A OnePlus One Sudden Death Bug That Results In Neverending Boot Loops.
I got to the point where I had to input the "adb shell" command then crashed and burned. My computer never recognized the device on the "adb devices" command... and I'm assuming it's because I don't have USB Debugging enabled. There might be another reason why, but I couldn't tell you. The "fastboot devices" command gave me a valid response when I was in fastboot mode.
I'm kinda all over the place, sorry. Just not really sure what to do from here. Can a noob solve this relatively easy with USB Debugging not enabled (if that's the case)? I've submitted an RMA already, but I have a feeling it's going to take OPO forever to get back to me.
TIA!
Click to expand...
Click to collapse
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
And voila you are good to go.:good:
vamshi88 said:
Hey I had the same problem today, went into bootloop and unware of what the problem was i just flashed stock 38R but still had the bootloop. now as you can guess my usb debugging was not enabled but i got out of it here is how.
Go to TWRP>advanced>Terminal command.
now you should see the platform folder here
Just hit select button on the bottom right.
Now just type
And voila you are good to go.:good:
Click to expand...
Click to collapse
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
hermunn123 said:
This seems like the easiest fix... but I don't have TWRP installed. Is it possible to install that in the state my phone is in?
Click to expand...
Click to collapse
What is your phones status now?
vamshi88 said:
What is your phones status now?
Click to expand...
Click to collapse
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
hermunn123 said:
Completely stock phone that is stuck in the constant on,off bootloop. Can boot into fastboot and CyanogenMod Recovery screens.
Click to expand...
Click to collapse
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Fastboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
vamshi88 said:
I do not use CWM and so i dont know how to help you on that, but flashing TWRP is not hard through Flashboot just follow this guide http://forum.xda-developers.com/showthread.php?t=2788632.
let me know if you need further help.
Click to expand...
Click to collapse
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
timmaaa said:
He can't flash TWRP because he said he's completely stock, which means the bootloader is locked. Btw, it's fastboot, not flashboot.
Transmitted via Bacon
Click to expand...
Click to collapse
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
vamshi88 said:
haha while typing i guess i mixed up flashing and fastboot hence flashboot. Also he can unlock the bootloader now cant he? what happens if he flashes TWRP without unchecking "Update recovery with system updates" (after bootloader unlock)? because after i got into the reboot problem i flashed the factory image, by now my bootloader was already unlocked but i was not able to uncheck the "Update recovery with system updates" or enable the usb debugging. still i flashed TWRP via fastboot and i was good to go.
Click to expand...
Click to collapse
He could try unlocking the bootloader, but my guess is that it will fail with his phone in the current state. Failing to uncheck the 'update cm recovery' option in Developer Options shouldn't pose a problem until an update is taken.
Transmitted via Bacon
Stuck in bootloop
th3xeroeagle said:
When you connect your phone to your pc while in fastboot in device manager does it say Android Adb Device?
Click to expand...
Click to collapse
Hey there,
My OPO is stuck in bootloop and believe me, i just took it out of the box (though it was 4 months without charge).
I cannot put it in to fast boot and I tried power cycling too by discharging it for 12 hours & charging for 6+1 hour. Its just the same.
Can you help?
Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
then go back into volume up + power (fastboot mode)..... fastboot flash recovery <recovery-name>.img while the recovery file is in the fastboot.exe folder. then boot into recovery.
zephiK said:
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
Click to expand...
Click to collapse
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
lemonspeakers said:
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
Click to expand...
Click to collapse
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
zephiK said:
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
Click to expand...
Click to collapse
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
tkdsl said:
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
Click to expand...
Click to collapse
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
teh roxxorz said:
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
Click to expand...
Click to collapse
I've already tried this on 3 different computers.
I don't see how having dev mode would affect bootloader if I never boot into the OS.
Someone had the same issue and had found a fix. I will give this tampering fix a try:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-totally-locked-t2817735
lemonspeakers said:
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Click to expand...
Click to collapse
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Dr.Linde said:
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Click to expand...
Click to collapse
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
lemonspeakers said:
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
Click to expand...
Click to collapse
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Dr.Linde said:
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Click to expand...
Click to collapse
That is sooo SCHWEET! I can't wait to try it on my phone when I get home! Woot!
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
@nickizm, when you boot to fastboot and enter the command "fastboot devices", can you see your device listed on the screen?
Thanks for the reply.. The fastboot work fines apart from when I try to unlock the devices and it reboots into recovery, it crashes and doesn't unlock.. the rest of the phone works fine apart from the recovery... my bootloader is also locked and I can't unlock it due to crashing
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screem enabled: false
I can't be certain but I'm pretty sure I read a similar issue to this a few days ago that was caused by not having the latest fastboot software, the user resolved it by downloading the latest android sdk and trying again.
Worth a shot.
Hope it helps.
Powered by Bacon
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
nickizm said:
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
Click to expand...
Click to collapse
Did you try with the latest android sdk?
Powered by Bacon
I'm sure I did.. It wasn't that old.. I can try again, but the problem is I won't be able to unlock my phone??
is this the right link? http://developer.android.com/sdk/installing/index.html?pkg=studio
New drivers, exactly the same
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Rkr87 said:
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Click to expand...
Click to collapse
Yea i have also tried the tool kit V2
My problem is that the recovery is damaged in some way and my device is locked. i can't "fastboot oem unlock" as it just crashes when it goes to reboot.. is there a way to unlock my device with another method or can the recovery be repaired some how? i'm such noob
patstar5 said:
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
Click to expand...
Click to collapse
Ye i tried that as well.. can't unlock the device as it just crashes when it goes to reboot into recovery
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Rkr87 said:
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Click to expand...
Click to collapse
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
nickizm said:
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
Click to expand...
Click to collapse
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Rkr87 said:
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Click to expand...
Click to collapse
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
nickizm said:
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
Click to expand...
Click to collapse
No worries! Let me know how it goes good luck!
Rkr87 said:
No worries! Let me know how it goes good luck!
Click to expand...
Click to collapse
Definitely! cheers again
nickizm said:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
Click to expand...
Click to collapse
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
adb reboot recovery
Click to expand...
Click to collapse
there you can got into recovery.
Gh05tShie1d said:
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
there you can got into recovery.
Click to expand...
Click to collapse
That doesn't work as my device crashes when it goes into recovery..
eg: "fastboot oem unlock", factory reset, or a boot recovery all crash as my recovery isn't working. When my device goes to reboot in recovery the 1+ logo comes up, fades out to like a blueish from the white 1+ logo and crashes.. so basically it's looked and I can't get into recovery.. thanks for trying
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.