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
Related
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
patrickgrantm said:
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
Click to expand...
Click to collapse
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
lurkeratthegate said:
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
Click to expand...
Click to collapse
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
LS.xD said:
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
Click to expand...
Click to collapse
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
lurkeratthegate said:
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
Click to expand...
Click to collapse
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
LS.xD said:
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
Click to expand...
Click to collapse
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
lurkeratthegate said:
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
Click to expand...
Click to collapse
RUU flashing is fastboot based I suppose. So you won't need adb at all.
LS.xD said:
RUU flashing is fastboot based I suppose. So you won't need adb at all.
Click to expand...
Click to collapse
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
lurkeratthegate said:
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
Click to expand...
Click to collapse
Connect phone in fastboot mode, run RUU, click next plenty of times, and done
If your phone is S-ON, flash stock recovery first and relock the bootloader before running the RUU
Hi everyone,
I'm hoping you can help me. I've had a OnePlus One since August 2014, completely stock. Never modded it, never 'flashed' anything, never installed anything outside of the Google Play Store. Always installed the official OTA updates as they pop up on the phone itself. Basically a reeeeealllly boring android user!
So Thursday morning (09/06/2016) I got a notification that a system update was downloaded and ready to install. Clicked install, the process began, phone rebooted as per usual. However, on the install progress screen (the green android with the spinning cogs), about one third of the way through the phone freezes. About 20 seconds later the phone reboots itself and then tries to install the update again. Freezes. Reboots. Tries to install. Freezes. Reboots. Tries to install.... I think you get the idea. It was doing this for a couple of hours before I checked it.
I'm moderately tech-savvy but never really got involved with android modding, rooting or flashing. So I'm a bit confused as to why my completely stock phone is stuck in a bootloop after installing an official CyanogenMod OTA update. The current status of my phone is that I can only boot into Fastboot mode via VolUp + Power. I can get my computer to detect my phone in Fastboot mode, however it informs me that my bootloader is locked. Attempting to boot into recovery mode via VolDown + Power just starts the update install and enters the bootloop.
I've done some research in to flashing a recovery image or manually applying the OTA update. One problem I've noticed is that I have absolutely NO idea what version of Android / CM my device was at before the update, and I have NO idea what version it was trying to update to. I do know that it was some version of Marshmallow before it broke. I've had no issues with the phone before this, aside the occasional self-reboot.
I REALLY want to keep all my data (pictures, contacts etc.) and am very nervous about actually doing anything because I have very little idea as to what I'm really doing.
Can anyone offer any advice on how to get my phone to boot/update/recover through Fastboot with a locked bootloader and without losing any data?
Thanks,
Stormin'
AKA the "HOW DO I PLAY BOOM BEACH NOW?!" guy
Edit: I solved my issue. It might work for you too, permalink to my post (#9) below: http://forum.xda-developers.com/showpost.php?p=67278091&postcount=9
Are you able to get into recovery mode? If so, you should be able to just flash a new ROM. Sideload one using the adb push command, wipe your data (this will clear settings, apps, etc. DO NOT SELECT SD CARD - that will wipe your personal files including your photos). Then install. Hopefully it should all work fine.
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery. Then try the above.
If you can't even get to that stage you're screwed, just like me (unless anyone has any ideas). I've had soft bricks many times before but today I can't even get to the bootloader screen. ADB says the phone is offline. The screen is back and flickers on for a split second every now and then. Bloody CM Updater.
As IBM9001 has said, if you can get into recovery - even being stock - you can still clear your cache - don't do a full factory reset, just the cache, this may help, but even if it doesn't it still rules out one option.
I can't access recovery mode, using the key combo it just boots straight into the installer.
I've got a support ticket open with OnePlus and a scheduled remote assistance tomorrow. However from the preparational email it looks like they are going to factory reset the phone and then clean install CM. They've instructed me to make sure that all my files are backed up... I assume this means I will lose them.
Is there ANY way just to access or pull the photos off my phone? That's the most important bit. Dropbox hit its storage limit at the beginning of 2015 and I refused to pay, so now I have 18 months worth of pictures that I have no other copies of on death row
The only thing I can access is Fastboot...
Edit:
ibm9001 said:
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery.
Click to expand...
Click to collapse
I can boot into Fastboot mode, and plugging my phone into my PC works i.e. it is recognised. I have the fastboot .exe and USB drivers, and can issue commands to my phone through cmd such as
Code:
fastboot reboot-bootloader
which works.
How do I use a recovery .img through Fastboot? or can I pull the contents of the sd card through Fastboot?
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Hi guys,
I have the same issue!
If I flash a new recovery from fast boot will I lose my data on sdcard?
Thanks.
Sent from my iPad using Tapatalk
masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I cannot boot into recovery mode, unfortunately
masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I'm currently having a very similar issue, but my phone completed the update. It's just stuck in a reboot/"optimizing apps" loop. I can boot into recovery and I tried to clear cache, but It's still just optimizing apps then rebooting and optimizing again over and over. Do you think your suggestion would help me too?
Wooooo, I've fixed it! I don't know why what I did fixed the issue (probably bypassed something) but my phone is up and running again! First thing I'm doing is making a freakin' backup!
So I was just trying everything in desperation. So that others can attempt to fix the same problem, here's what I did:
1. State of phone was either boots normally and crashes when installing update, or boots into fastboot. Would NOT boot into recovery!
2. Booted into fastboot using key combo (hold Volume Up, then Power Button)
3. Attached phone to computer via data usb lead
4. Started up cmd console, used command "fastboot devices" to check that device was recognised (note you need the fastboot files and USB drivers etc., Google it if you're not sure)
5. Used command "fastboot continue" to continue with 'autoboot'. This rebooted my phone but skipped the installer and went to the 'optimising apps' stage. Left phone alone for a couple of hours but it got stuck in another bootloop optimising apps, rebooting, optimising apps and so on.
6. Turned phone off, then booted normally with just the power button. This started the update install again except it didn't crash, and completed the update install. Then it optimised the apps again (albeit with a different total app count) and once finished, phone starts up normally.
Thanks for all the suggestions everyone! Happy to have my phone back. Now to go through the half-dozen or so voicemails I've collected over these last few days... great.
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
From the FAQ:
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.
Click to expand...
Click to collapse
Does it mean I can flash an official CM firmware without unlocking the boot loader?
Thanks.
hibernick said:
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
Click to expand...
Click to collapse
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Same problem, Also PC not detecting my phone
Hey Guys, I am Stuck at the same thing at Bootloop. But to do anything further I need to connect my phone to the PC. I haven't been able to connect my phone to PC since the time I have got the phone. I tried all available drivers and even tried different cables. I dont know what has been left out to try.
If any one has a working driver pls share the link. Its been three days now that my phone is dead.
Pls help!!
Thanks in advance.
masterjigar said:
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Click to expand...
Click to collapse
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
hibernick said:
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
Click to expand...
Click to collapse
You can't adb sideload .img or a partition.
You have to use fastboot.
Code:
fastboot flash boot boot_img_name.img
or
Code:
fastboot boot boot_img_name.img
saurav007 said:
You can't adb sideload .img or a partition. You have to use fastboot.
Click to expand...
Click to collapse
Yes but then I have to unlock my bootloader first. And unlocking bootloader erase all the user files....
Is there other way to to run cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img on the devise?
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
justinstrack said:
I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
Click to expand...
Click to collapse
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
only4dank said:
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
Click to expand...
Click to collapse
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
justinstrack said:
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
Click to expand...
Click to collapse
Sorry to hear. You are going to have to provide logs of what commands you are typing into terminal, and what is the output.
So are you in TWRP or not. I literally have no idea what is going on with your device or what you are doing.
Next time, maybe check guides in this forum of how to do what you are doing.
Randomly uninstalling/installing/flashing/issuing commands via terminal/random backup and restores/etc.... does not sit well with android devices.
I'll try another pc tonight.
If you can get back to twrp you need to flash magik to boot normally
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
justinstrack said:
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
Click to expand...
Click to collapse
Still.... what are you typing into terminal... take a screen shot .....
ARE YOU SURE you are typing 'fastboot boot twrp.img' - BOOT, not FLASH!!!???
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
justinstrack said:
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
Click to expand...
Click to collapse
I would start by reading forum page 1 information about what you are trying to do.
I already explained to you the order to flash to make things work.
If that is not enough, once again, go learn what you are trying to do (via the forum thread).
You will probably save yourself these types of situations in the future if you understand what you are doing.
Good luck.
Everything is FULLY Operational Thank You. What a experience but Ive learned.
justinstrack said:
Everything is FULLY Operational Thank You. What a experience but Ive learned.
Click to expand...
Click to collapse
And not even a single thanks button hit or anything... Weird flex, but OK
I'm so sorry LOL. found it. Have a good day xda forum members, I found the button. THANK YOU
I'm having a problem fastbooting a boot.img on my phone, I got the right room and have the bootloader unlocked and everything, but it keeps saying a command error from the phones side...... At least I think so.
Reinstall ADB drivers.
JJay666 said:
Reinstall ADB drivers.
Click to expand...
Click to collapse
That was the adb drivers, the same ones that I used to originally unlock the phone, you can't tell me that they weren't working, because they were working
I was trying to use them off of my windows 10 pc, but couldn't figure where the stupid folder went
Like, why would my adb drivers be not working even though it would work normally for unlocking the bootloader, and does it matter that I'm using the T-Mobile variant of the software?
youngherobrine1 said:
Like, why would my adb drivers be not working even though it would work normally for unlocking the bootloader, and does it matter that I'm using the T-Mobile variant of the software?
Click to expand...
Click to collapse
No it wouldn't. Try removing screen locks if any. Shouldn't be an issue if you can connect though. Easiest way is to use the AllinOne tool available here in this forum .
I had the same issue. I was trying to boot to the latest unofficial TWRP (fastboot boot twrp.img) and install it. I tried different USB ports, cables, etc... and even downloaded the official Google SDK (tools only) and replaced every binary on my laptop with them. Same thing (just slightly differently formatted output, but same "unknown command" error).
Fortunately, I realized that I only needed that to boot the phone prior to installing TWRP, which I already had (it was late!). I booted into the older installed TWRP and flashed the TWRP installer, then magisk.
I would still like to know what is happening, though. Like you said, this is the same Minimal ADB and Fastboot that I used to setup the phone in the first place.
Flapjack said:
I had the same issue. I was trying to boot to the latest unofficial TWRP (fastboot boot twrp.img) and install it. I tried different USB ports, cables, etc... and even downloaded the official Google SDK (tools only) and replaced every binary on my laptop with them. Same thing (just slightly differently formatted output, but same "unknown command" error).
Fortunately, I realized that I only needed that to boot the phone prior to installing TWRP, which I already had (it was late!). I booted into the older installed TWRP and flashed the TWRP installer, then magisk.
I would still like to know what is happening, though. Like you said, this is the same Minimal ADB and Fastboot that I used to setup the phone in the first place.
Click to expand...
Click to collapse
aparently I was using a chommand that wasnt working with the system, or was incomplete, heres the chommand I ended up using to get my phone rooted finally
fastboot flash boot magisk_patched.img
youngherobrine1 said:
aparently I was using a chommand that wasnt working with the system, or was incomplete, heres the chommand I ended up using to get my phone rooted finally
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
That command actually flashes recovery. I thought the proper method was to fastboot boot to the recovery, then run the installer.