I really have no clue how I got here but i had everything going well and then there was an oxygen os update. I installed and lost root functionality so I did the whole twrp install thing all over again which was a mistake. I got stuck in a twrp boot loop and now im stuck in a fastboot loop. I have tried to sideload a stock image but it says phone is not in adb mode.... Help!
david.baquerizo said:
I really have no clue how I got here but i had everything going well and then there was an oxygen os update. I installed and lost root functionality so I did the whole twrp install thing all over again which was a mistake. I got stuck in a twrp boot loop and now im stuck in a fastboot loop. I have tried to sideload a stock image but it says phone is not in adb mode.... Help!
Click to expand...
Click to collapse
Try fastboot install Rom from here. Match the version you last had installed. Give it few minutes to get going once you start the process.
chazey2 said:
Try fastboot install Rom from here. Match the version you last had installed. Give it few minutes to get going once you start the process.
Click to expand...
Click to collapse
Thanks!
I'm in the exact same situation as OP, only my phone is a OP6T @david.baquerizo did you manage to install the fastboot Rom without problems? I'm wondering how it will be able to install if you can't see your phone in fastboot. My plan is to try different computers and go into windows testmode in order to get fastboot access to the phone. If I'm able to do that, it should be possible to flash a twrp.img and get back into action (fingers crossed)
Related
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...
It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.
Okay so I received my opo today and wanted to unlock and root etc.. I managed to install drivers and download a toolkit which managed to unlock my bootloader but wouldn't flash the recovery so I attempted it manually via fastboot and after flashing it would reboot to a back screen then vibrate and reboot to system.. Been doing that all night? Any ideas? many thanks in advance new to this phone
Exactly what recovery version are you trying to flash? What OS is on the phone? Get rid of the toolkit, they're nothing but trouble.
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
daviss101 said:
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
Click to expand...
Click to collapse
Try flashing the recovery again, followed by this command
Code:
fastboot erase cache
Then:
Code:
fastboot reboot
Then try booting into recovery.
PS. You've unchecked the "update CM recovery" option in Developer Options, right?
same problem for me. tried manually installing any custom recovery, tried two different toolkits. it flashes and reboots, but then you can never enter the recovery app. even attempting to put stock back fails. i attempted the format the cache and that didn't do a thing for me. basically had to enable cm recovery updates and reset to factory in the os. after that i was back to scratch at least.
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
GrizzlyD said:
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
Click to expand...
Click to collapse
No problemo. ^_^
So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good
usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.
fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked
schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push
schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome
im used to Nexus 6 which is differnt way...this is LO4 model bootloader is unlocked
i got drivers installed but not sure which files to use or how to do it
am i reading right? there is no lo4 root? if not any idea how long untill there will be?
Same procedure as L09
leo5111 said:
am i reading right? there is no lo4 root? if not any idea how long untill there will be?
Click to expand...
Click to collapse
Flash TWRP normally, then Magisk latest Beta
what do i put in fastboot to flash it? and do i use the berkly 3.2.10 one?
anyone? because i tried fastboot command with twrp 3.2.10 and it it says it went but then when i try to boot into it says software failure? so i think im using wrong version or command?
ok i dont know WTF it installed twrp i can even get phone to go into twrp but it reboots back out to fastboot rescue mode?
tried 3.2.11 and it just loops back to fastboot...i read that they could block magisk would that stop installtion of twrp as well? i uses fastboot command fastboot flash recovery_ramdisk TWRP.img yes i named the image TWRP.img
did huawei allready start blocking magisk/twrp install? because it will say twrp installed BUT will go into twrp for like 10 seconds and then reboot to fastboot and phone updated itself like yesterday
says im on build bkl-lo4 8.1.0.120 "c567" emui version 8.0.0 android 8.1.0 security patch july 1st kernal 4.4.103+ tues july 17th
https://openkirin.net/ i installed lineage from that ran it through fastboot after reinstalling stock rom
found out my issue i think before i re-installed the recovery with the downloader on the phone it would not kill the messed up twrp was on it and when it went to stock recovery woud not let me wipe it, re-install fixed all that i think first time i installed twrp ran wrong command and installed twrp to wrong place, now ill try installing twrp now that i know proper fast boot is fastboot flash recovery_ramdisk TWRP.img correct?
i give up for now im on lineage with that other app tried installing twrp with that command and does same crap goes into twrp for like 10 seconds then kicks out to fastboot
i dont know WTF i ran this................ fastboot flash recovery_ramdisk TWRP.img does one of 2 things either "A" boots into twrp for like 10 sec and kicks back out to fastboot or says software install failure or something like that oh ya its not bootlooped though if you just let phone go it will reboot into OS
Hey Guys,
So my idiot brain decided to mess around with substatum themes after I updated and rerooted my OP7P. I rooted with magisk but forgot to put TWRP recovery on.
Anyways, got the phone semi bricked when applying one of the overlays. The phone boots and I can see my lock screen wallpaper but the screen is just flashing on/off.
I cant use the fingerprint or pin to get it. Is there a way for me to backup my pictures and data or somehow remove substratum?
Biggest problem is that for whatever reason, the update revoked my ADB authorization so it looks like I cant do anything with ADB.
If someone has any way to salvage my situation, please reply. Factory reset is my last resort due to no backup.
Thank You
Try booting into TWRP and using ADB there.
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
tech_head said:
Try booting into TWRP and using ADB there.
Click to expand...
Click to collapse
pranacrockz said:
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
Click to expand...
Click to collapse
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
morphius88 said:
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
Click to expand...
Click to collapse
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
pranacrockz said:
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
Click to expand...
Click to collapse
Rebooted to fastboot, entered the PIN but Fastboot is a no go. Just keeps saying <waiting for any device> and nothing happens. Would that be because the authorization keys were not accepted after the update?
I am downloading the MSM Tool and will try that if I cant get it to work with fastboot. Will update if it works.
Thanks for suggestions
Ended up using the MSM tool. Did not know it wipes data and also put me back to Android 9.
Oh well, lesson learned. Gotta make monthly backups, make sure twrp is installed and working before messing around with substatrum.
Thanks for the help.