Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] [HELP] Missing recovery 4.3

I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
EDIT: when I get the no command "fallen android" when i select recovery from the bootloader on pressing power+vol up does give me acces to the stock recovery. But even on using wug's 1.6.6 root kit I'm unable to root the device and install a custom recovery

Vikas Rao said:
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
Click to expand...
Click to collapse
Have you tried redownloading twrp seems like a bad download?

yamani.m said:
Have you tried redownloading twrp seems like a bad download?
Click to expand...
Click to collapse
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot

Vikas Rao said:
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Click to expand...
Click to collapse
I would try to flash the full stock google image with fastboot and see what happens ?

Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!

EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
I also did it this morning, works fine

EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
Nope did the same thing! gives me the cannot load error, I just copy pasted the filename so can't go wrong there. And a stock rom flash is an option but the thing is i don't have a custom recovery nor root access for titanium backup don't wanna spend time again personalizing. I'm sure there is a simpler way.

[Q] TWRP wont start after Updating to 4.3

Hey guys,
I had installed TWRP on my Nexus 7 when it was on 4.2
Then updated to 4.2.2, and everything worked perfectly.
But now few days back, I updated to 4.3 and since the update, TWPR has stopped working.
When i go in recovery i get "!" marked Android (Photo attached).
Pls help, what should i do ?
EDIT : I have also tried flashing (through fastboot) new versions of TWRP, still no Luck !!

What you are seeing is stock recovery. You need to flash a new version of twrp
Sent from my iPhone using Tapatalk

The update flashed the stock recovery into your N7. Make sure that your bootloader is unlocked and flash TWRP through fastboot, with "fastboot flash recovery [thenameofthefile].img".

Pls read the post guys, I already tried flashing new twrp, it didn't solve the problem, that's why have posted!
Sent from Nexus 7 using XDA developers app

Nikhs said:
Pls read the post guys, I already tried flashing new twrp, it didn't solve the problem, that's why have posted!
Sent from Nexus 7 using XDA developers app
Click to expand...
Click to collapse
Hi, Nikhs...
That's kind of odd... never had any problems myself using fastboot flash to flash a Custom Recovery.
Are you sure you have a working fastboot connection? Type fastboot devices at the command prompt to confirm this. You should see a serial number, followed by the word "fastboot" (without the quotes)... something along these lines...
Code:
025d2d424bxxxxx fastboot
If you don't see something like this, then attempting to fastboot flash anything is a pointless waste of time. You could have a driver problem, ubiquitously known as 'driver hell'. This need to be resolved before you can proceed.
If fastboot flash still fails to flash TWRP, then I'm out of ideas... the only other solution I can suggest is you try flashing the TWRP .img file using either one of these two apps; Flash Image GUI or Flashify. (The TWRP .img file to be flashed will need to be either directly downloaded to the Nexus 7, or copied over to it first).
Both are pretty self-explanatory to use... just follow the on screen instructions.
I have successfully flashed both TWRP and CWM .img files in the past, using these apps, on my Nexus 7, without problems.
Although I've never used it myself, I understand that GooManager will download the most recent TWRP .img file, and automatically flash it for you.
However, the problem with all these apps is... you first need to be already rooted for them to work. So if you're trying to install TWRP in order to initially gain root access, then these apps won't be of much use to you, unfortunately... in which case, you'll have to persevere with fastboot, and see if you can get it to work.
fastboot flash recovery recovery.img should work though, and (barring driver problems) the only thing I can see preventing you from successfully flashing a Custom Recovery is a partition corruption, or some sort of underlying hardware problem.
On a final note, (and clutching at straws a little here), try a different USB port or USB cable or even a different PC (if you have one). Tech can be bizarrely capricious at times, and sometimes something as seemingly trivial as changing to a different USB port can resolve the most intractable of problems.
Hope this helps... and good luck.
Rgrds,
Ged.

GedBlake said:
Hi, Nikhs...
That's kind of odd... never had any problems myself using fastboot flash to flash a Custom Recovery.
Are you sure you have a working fastboot connection? Type fastboot devices at the command prompt to confirm this. You should see a serial number, followed by the word "fastboot" (without the quotes)... something along these lines...
Code:
025d2d424bxxxxx fastboot
If you don't see something like this, then attempting to fastboot flash anything is a pointless waste of time. You could have a driver problem, ubiquitously known as 'driver hell'. This need to be resolved before you can proceed.
If fastboot flash still fails to flash TWRP, then I'm out of ideas... the only other solution I can suggest is you try flashing the TWRP .img file using either one of these two apps; Flash Image GUI or Flashify. (The TWRP .img file to be flashed will need to be either directly downloaded to the Nexus 7, or copied over to it first).
Both are pretty self-explanatory to use... just follow the on screen instructions.
I have successfully flashed both TWRP and CWM .img files in the past, using these apps, on my Nexus 7, without problems.
Although I've never used it myself, I understand that GooManager will download the most recent TWRP .img file, and automatically flash it for you.
However, the problem with all these apps is... you first need to be already rooted for them to work. So if you're trying to install TWRP in order to initially gain root access, then these apps won't be of much use to you, unfortunately... in which case, you'll have to persevere with fastboot, and see if you can get it to work.
fastboot flash recovery recovery.img should work though, and (barring driver problems) the only thing I can see preventing you from successfully flashing a Custom Recovery is a partition corruption, or some sort of underlying hardware problem.
On a final note, (and clutching at straws a little here), try a different USB port or USB cable or even a different PC (if you have one). Tech can be bizarrely capricious at times, and sometimes something as seemingly trivial as changing to a different USB port can resolve the most intractable of problems.
Hope this helps... and good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
thanks for the help !
Problem solved,
I installed the Same version (Old version) of TWRP as i had before upgrading to 4.3
then installed the latest version of TWRP over it.
Seems like that solved the problem..
I wonder what and why and how it solved

Nexus 6p won't boot up

Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks

roelmmata said:
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
Click to expand...
Click to collapse
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921

Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.

roelmmata said:
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
Click to expand...
Click to collapse
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Sent from my Nexus 6P using Tapatalk

ultyrunner said:
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Click to expand...
Click to collapse
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.

roelmmata said:
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
Click to expand...
Click to collapse
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.

Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
Thanks I try it out!

ultyrunner said:
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Click to expand...
Click to collapse
Hey again
I used guide specifically to go back to stock, combined with a couple times of wiping in stock recovery I finally got the phone to boot up! However I've learned something new, the phone will only stay on if I'm plugged into charger, and as soon as it's unplugged it turns off. Any other suggestions?

How do I update my 6T rooted without erasing datas?

Dear all,
first of all I would like to be sorry if I'm saying something worng. I'm not so expert about Android world.
I've got a OnePlus 6T that I've rooted with the help of a friend some months ago.
Not it's a lot that I keep see the notification abount the OS update and I keep skipping it but it's bothering me so... I searched for a guide and I found this (https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/) (I hope I can post it also if it's from another website).
It seems so simple, I've downloaded the OTA update, the TWRP and the Magisk. My issue is that whene I reboot to the recovery I'm not booting into TWRP but I suppose into the OnePlus recovery instead.
I searched angain and found this other guide (https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953) that is more complete but I can't understand if it's the proper guide I need to follow to update my device keeping it rooted and most of all without loosing any data.
Thanks,
Riki

The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.

OhioYJ said:
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
Click to expand...
Click to collapse
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Thanks again,
Riki

RikiBez said:
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Click to expand...
Click to collapse
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.

OhioYJ said:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
Click to expand...
Click to collapse
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
Old_video_link_removed
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.

RikiBez said:
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
https://youtu.be/7Re-p7Z1yhc
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
Click to expand...
Click to collapse
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?

OhioYJ said:
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
Click to expand...
Click to collapse
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.

RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app

RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.

CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app

i7vSa7vi7y said:
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot was working until I reinstalled adb and OnePlus drivers.

CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.

RikiBez said:
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
Click to expand...
Click to collapse
Try uninstalling adb. Delete the whole folder and install it again. Try updating your netframework on your PC and the latest C++
Sent from my OnePlus 6T using XDA-Developers Legacy app

I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.

RikiBez said:
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
Click to expand...
Click to collapse
Use the msm tool for that
Sent from my OnePlus 6T using XDA-Developers Legacy app

Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.

OhioYJ said:
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
Click to expand...
Click to collapse
Those fastboot roms have sure saved me from raging before
I would also recommend using migrate, it's in the play store and it backs up all your data and then puts it in a flashable zip

i7vSa7vi7y said:
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do a factory reset from TWRP and flash the full ROM.

One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.

sanjeev7 said:
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
So I don't have to wipe my system data or anything. I heard some people had the problem of getting stuck or that there was a red warning screen that popped up when booting, and I'm not talking about the bootloader message. I'm currently on 9.0.11. Also should I download the latest version of TWRP or should I use the one I'm using currently. Don't wanna mess anything up. Another guide I read said I should flash the oos rom, then TWRP, than magisk