Related
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?
I am trying to flash the 5.0 official image to my N5 and it is now stuck on "waiting for device". See attached image.
I was able to see my device in adb, i booted to fastboot mode and adb fastboot listed my device. It sent/wrote the bootloader to the phone, but now is just waiting.
Can i safely kill the flash process and start again? I am a little worried that it is just stuck.
reynolds10g said:
I am trying to flash the 5.0 official image to my N5 and it is now stuck on "waiting for device". See attached image.
I was able to see my device in adb, i booted to fastboot mode and adb fastboot listed my device. It sent/wrote the bootloader to the phone, but now is just waiting.
Can i safely kill the flash process and start again? I am a little worried that it is just stuck.
Click to expand...
Click to collapse
im not going to answer, but you should read threads in other n5 xda sections(general. hint hint..)
simms22 said:
im not going to answer, but you should read threads in other n5 xda sections(general. hint hint..)
Click to expand...
Click to collapse
That's right ya'll wanna flash but don't wanna read :silly:
Thanks guys. Much appreciated.
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
Good morning,
I was tryng to flash the hydrogen os and something went wrong with magisk so now the phone reboot just to fastboot mode and i cant do nothing... I already tried to restore it throw the fasboot recovery guide con this forum but the problem is that the comouter doesnt see the phone in fastboot... I already installed the adb and fastboot driver for the oneplus 6 but if i type the command fasboot devices the promp doesnt show the phone as usually... Someone can help me? Thanks
Did you already try with this?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Sent from my ONEPLUS A6000 using Tapatalk
Guys , I am new on Op7 , I had a stuck in fastboot because of unable to use boot command, then using msm tool I went back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
U can only install twrp through booted TWRP
also pie and q version of OOS need proper boot.img TWRP from this thread https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
new_world_2006 said:
Guys , I am new on Op7 , I had a stuck in fastboot because of unable to use boot command, then using msm tool I went back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
Click to expand...
Click to collapse
Upgrade to 10, then Root.
blas4me said:
Upgrade to 10, then Root.
Click to expand...
Click to collapse
So how i can root, if i have damaged fastboot boot command?
new_world_2006 said:
So how i can root, if i have damaged fastboot boot command?
Click to expand...
Click to collapse
First thing is to OTA update to anything other than 9.5.3. Seemed to me I remembered when I first got the device (many months ago) somebody mentioned there was a fastboot issue on 9.5.3. So just take whatever OTA is availabe to you. Probably 9.5.13
If you still can't boot the twrp.img after that then try manually changing the active slot in fastboot;
fastboot getvar current-slot *(take note of the current slot this command returns)*
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
fastboot reboot bootloader
So you should end up with something like this;
fastboot --set-active=a
fastboot reboot bootloader
fastboot boot "C:\Adb\twrp-3.3.1-4-guacamole.img"
new_world_2006 said:
So how i can root, if i have damaged fastboot boot command?
Click to expand...
Click to collapse
Bootloader is not damaged, did you enable usb debugging.
Please read, most of us have been there, and a lot of us are coming from some other OnePlus device. Project treble was discussed a lot on 5T forums. If your bootloader detects custom firmware while locked, it will lock the phone. You can't run fastboot commands because you missed a step somewhere.