Getting confused.
Loaded Nougat on my Nexus 5x... unlocked boot loader, loaded TWRP 3.0.2-2 rebooted, saw TWRP,
Moving files to the phone to restore using TB, but have not yet done SUPERSU.. reboot back into recovery, Android Flat on back Red Triangle, No command??
Can reboot into the phone it works, just can't get back to TWRP for reasons I can't figure out.
Feels like I missing a step, but can't figure out what. Looked at a lot of pages, but nothing really stands out.
Update: Used fastboot boot [twrp imagename].img
And it got me directly to TWRP. Able to load SuperSU then.
Update #2: What I didn't make clear in this original post was I did in fact flash the TWRP recovery, it just didn't stick.
Command used originally:
Code:
C:\SDK\platform-tools>fastboot flash recovery twrp-3.0.2-2-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.579s
My mistake was to then reboot where it was apparently overwritten hence the confusion.
krelvinaz said:
Getting confused.
Loaded Nougat on my Nexus 5x... unlocked boot loader, loaded TWRP 3.0.2-2 rebooted, saw TWRP,
Moving files to the phone to restore using TB, but have not yet done SUPERSU.. reboot back into recovery, Android Flat on back Red Triangle, No command??
Can reboot into the phone it works, just can't get back to TWRP for reasons I can't figure out.
Feels like I missing a step, but can't figure out what. Looked at a lot of pages, but nothing really stands out.
Update: Used fastboot boot [twrp imagename].img
And it got me directly to TWRP. Able to load SuperSU then.
Click to expand...
Click to collapse
The reason that happens is if u fastboot boot twrp.img u will only have a temporary twrp until u reboot..if u had typed fastboot flash recovery recovery twrp.img then when u reboot the recovery would be permanent...
Sent from my Nexus 5X using XDA-Developers mobile app
dog121 said:
The reason that happens is if u fastboot boot twrp.img u will only have a temporary twrp until u reboot..if u had typed fastboot flash recovery recovery twrp.img then when u reboot the recovery would be permanent...
Click to expand...
Click to collapse
Actually, I did use flash the recovery. It came up just fine. However, after a reboot, when I booted back to recovery I got the No Command.
I had to re-flash TWRP, and then reboot back to Recover from TWRP, then reboot, then it worked like it should.
The command you posted was to boot a recovery, not to flash one in the recovery partition.
Anyway, you can't just flash TWRP and boot, because the boot will replace stock recovery, you got to flash supersu/another kernel from the recovery after flashing for it to stick.
You Can try this adb command :
fastboot flash recovery twrp_3.0-2-2.img
fastboot boot twrp_3.0-2-2.img
And normaly it's ok you have twrp installed
Thanks for the other responses...
Just to confirm what I did originally (I just unrooted so that I could use Magisk and PPH Root)
Code:
C:\SDK\platform-tools>fastboot flash recovery twrp-3.0.2-2-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.579s
However, If after doing this I rebooted the phone etc... TWRP was no longer there again. I had to do the same, force a boot to twrp, and then install Magisk before rebooting for it to stick.
Just in case someone else runs into this confusion.
I am now on Android 7 Nougat on a Nexus 5X with Magisk using PPH Root and can now use Root, Android Pay and some other apps which won't run with root enabled. Happy Camper for now.
The step your missing is after you fastboot flash the recovery don't reboot the phone just yet. You have to reboot the bootloader by typing fastboot reboot bootloader. After doing that use the volume up button to access recovery. Once you do that then you can start the phone.
Sent from my Nexus 5X using Tapatalk
krelvinaz said:
However, If after doing this I rebooted the phone etc... TWRP was no longer there again. I had to do the same, force a boot to twrp, and then install Magisk before rebooting for it to stick.
Click to expand...
Click to collapse
If you boot with a stock boot.img the android boot process will replace your recovery partition with stock if the SHA256 for the recovery doesn't match what it expects. The way you can stop this is to modify your boot.img, which would happen if you install SuperSU prior to first android boot after a new flash.
Related
Okay, so I tried my best to search the forums and read the Q+A first, but the suggestions I've found so far didn't help me solve my problem.
I started with Hasoon200's tool kit and successfully unlocked the boot loader. Then, however, I got stuck at installing CWRM (it just wouldn't boot into recovery after installing). So I gave it a try with the "One X one Click" tool kit. I downloaded the n3okernel v34 and -modules as well as the newest nightly build of Cyanogen Mod (cm-10.1-20130414-NIGHTLY-endeavoru).
Now my HOX is caught in a boot loop. No matter which option I choose (fastboot / hboot, recovery, factory reset), it'll always go to the white HTC screen and stay there. Since Q+A's Q11 mentions it: yes, the last time I could boot into the OS (then still the stock image) I disabled fast boot in power settings.
Currently I can only access my HOX via fastboot, I already got a stock image and extracted the boot + recovery images, which I then flashed with the fastboot utility, as suggested in the Q+A's Q9. I erased the cache and rebooted to no avail. I also tried the firmware executable (RUU_ENDEAVOR_U_ICS_40_O2_DE_1.26.207.2_Radio_1.1204.90.13_release_251288_signed) to no avail.
Q+A's Q15 suggests sideloading via adb, but adb won't recognize my device.
I've also relocked the bootloader, this was suggested in another online ressource after flashing the stock boot+recovery images.
The phones HBOOT Version is 1.36.0000. I've noticed a different radio version than the one mentioned in my downloaded RUU; phone says 5.1204.162.29, downloaded file says 1.1204.90.13. I've not yet found a working download link with the right version number.
Please help.
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Mr Hofs said:
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Click to expand...
Click to collapse
Unlocking the bootloader works, but I'm not able to enter the recovery mode. It only shows a black screen (see attached picture).
EDIT: ok, wait... after flashing the clockwork recovery, I'm now getting into recovery mode. Will now try the next steps you suggested and give feedback later. Thanks a lot so far!
Press the Power and Volume down buttons which will take you the the hboot screen. From there select fastboot and flash a custom recovery like CWM via fastboot.
Now select hboot again and then select recovery!
Okay, so I successfully flashed CWM. I'm now able to boot into recovery. I also succeeded in flashing a boot.img which i took from cm-10.1-20130414-NIGHTLY-endeavoru.zip
c:\One\One\Data>fastboot flash boot boot.img
sending 'boot' (4960 KB)...
OKAY [ 0.684s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.498s]
finished. total time: 1.186s
Now - when selecting hboot - the phone gets to another screen, the one where it displays the "HTC One" logo; I tried flashing the CM-image using fastboot (adb still doesn't work), but got following error message:
c:\One\One\Data>fastboot flash /sdcard update.zip
sending '/sdcard' (200098 KB)...
OKAY [ 25.507s]
writing '/sdcard'...
FAILED (remote: not allowed)
finished. total time: 25.716s
So close, yet so far...
So you have a working CWM installed right?
After flashing the boot.img... do "fastboot erase cache"
now go to CWM(recovery) and mount your sd card... copy the CM10ROM.zip and the gapps.zip to your HOX...
after that select wipe data and then wipe dalvic and cache...
Now select install zip from SD and install the ROM and then the gapps... reboot!
The problem is that I can't - or could'nt - transfer files any other way than using fastboot. However, I've now flashed Team Win TWRP2, and finally I'm able to access my phone over adb or just mount it and access it via explorer. Phew.
FINALLY!
So, if another noob like me finds this thread in the future...
After installing the TWRP2 recovery with flashboot flash twrp2.img, then booting into recovery and mounting my device, I was able to copy the CM-ROM-zip file onto the HOX. Then I rebooted into fastboot again and flashed the boot.img from aforementioned zip-file using "fastboot flash boot boot.img".
Booted again, selected the recovery system, installed ROM from zip file.
I'm getting too old for this ****. Almost had a heart attack when I thought I had bricked my phone. Thanks everyone for holding my hand, I appreciate it.
Good mate !
CASE CLOSED !
I'm trying to flash twrp to my lg g4. I've reached the part where I run
Code:
fastboot flash recovery twrp.img
And everything seems to work fine, but when I try to enter recovery mode, I get the default lg recovery (restore factory mode options) and not twrp.
Here's what it prints out when I run the flash command:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 0.341s]
finished. total time: 1.168s
What am I doing wrong?
I tried doing it from a different computer and tried flashing older version of twrp.
No mate, you're not doing something wrong. You must overwrite the stock recovery, because it auto-flashes every time when phone starts. Best way is to use these commands :
adb reboot bootloader
fastboot boot recovery.img (rename recovery recovery.img , without .img (that's the extension, only "recovery", to make it clear)
I'm waiting the results....
Boot the image like. Azza_09 said then when TWRP has booted click on install then change to img instead of zip and select your twrp image. That should work, but Lg front end will be shown when booting to bootloader, simply answer both questions with yes then TWRP will load
FOR LG-H815, bought in Germany.
a) Went through the effort and unlocked the bootloader through LG's official method.
b) Confirmed, several times, that the bootloader is indeed unlocked.(via 'fastboot getvar unlocked' and verifying that the response is "unlocked: yes")
c) Tried to swap the Stock Recovery Mode with TWRP, using 'fastboot flash recovery twrp-2.8.6.0-h815.img'. The process ends in 1 sec. After booting in recovery mode, I find out it doesn't actually flash it.
d) Inside cmd: adb reboot bootloader
fastboot boot twrp-2.8.6.0-h815.img
At this point I am trying to boot TWRP for a one-time job of rooting the device.
-Install>>Select UPDATE-SuperSU-v2.46.zip>>Swipe to Install>> Reboot System
e) After reboot: PERMANENTLY STUCK, will not boot past LG's Logo. It is still possible to enter the Stock Recovery Mode, and Stock Download Mode.
I have repeated the process twice, reflashing the stock ROM, to the same effect. Any help is greatly appreciated.
You're flashing outdated versions of TWRP and SU...
I helped with this problem about 100 times now but I will do it one more time...
Firstly, reflash the stock MM ROM again.. Then download the better looking TWRP 3.0.2-0 from official twrp site -> https://dl.twrp.me/h815/twrp-3.0.2-0-h815.img.html
Now a little explanation. As far as I know in 6.0.X Google changed their policy a bit and the option to root the phone/ flash recovery is locked even though you have unlocked bootloader, and as well system root doesn't work, so instead of old SuperSU 2.46 you want to download newest systemless root zip -> http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 . Now, since there is no stock modified boot.img for G4, you have to download and unpack the custom kernel like SimpleGX and take it's boot img that you want to flash via fastboot, or you can try flashing boot.img from the Autoprime's V20D flashable zips, I didn't try that one and I will not be able to because my G4 got a bootloop issue that I recovered it of by my self but I cannot boot it up on Marshmallow stock firmware. Anyway once you flashed the modified boot img you should be able to flash recovery and boot it up normally, then flash systemless root and if you used boot.img from custom kernel, flash the full package because you did not flash all the stuff from the package what may cause software problems in the long term I suppose. I think that's all you need to do to root it on MM.
Adam Myczkowski said:
I think that's all you need to do to root it on MM.
Click to expand...
Click to collapse
And you would be correct. Although I have to wonder why guides on XDA don't even mention flashing a custom kernel like SimpleGX_KERNEL_H81520X_v1.3.2.zip
Additional steps for installing ROOT/TWRP on LG G4:
Inside CMD:
C:\adb>adb reboot bootloader
error: device '(null)' not found
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot bootloader
C:\adb>fastboot boot twrp-3.0.2-0-h815.img
downloading 'boot.img'...
OKAY [ 0.956s]
booting...
OKAY [ 0.028s]
finished. total time: 1.000s
Inside TWRP: Install>>Select SimpleGX_KERNEL_H81520X_v1.3.2.zip>>Swipe to the right>>Reboot // .zip file is ~19MB
Inside CMD:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-3.0.2-0-h815.img //now attempting to overwrite the stock recovery
target reported max download size of 536870912 bytes
sending 'recovery' (31652 KB)...
OKAY [ 0.969s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.365s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot recovery //to verify that TWRP has been installed.
Inside TWRP:
Install>>Select BETA-SuperSU-v2.71-20160331103524.zip>>Swipe to the right>> Reboot
DONE.
Hi, Guys.
I am trying to install the recovery in my phone, but without success.
I already tried some versions of twrp for our moto z play and able not to flash the trwp.
My bootloader is unlocked.
When i typed , show me the message below.
C:\Users\myuser\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY [ 0.400s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.197s]
finished. total time: 0.601s
fastboot flash recovery ( here the name of your twrp recovery).img
f1fan said:
fastboot flash recovery ( here the name of your twrp recovery).img
Click to expand...
Click to collapse
I already tried severa times and not worked.
iago1966 said:
I already tried severa times and not worked.
Click to expand...
Click to collapse
Are you sure it didn't work? The message is just a warning. The second OKAY indicates that it has been flashed sucessfully.
tomparr said:
Are you sure it didn't work? The message is just a warning. The second OKAY indicates that it has been flashed sucessfully.
Click to expand...
Click to collapse
Hi,
I'm sure that, but when show me "writing 'recovery', i think that the hour what the recovery is instaling in the device, but don't write.
When i choose the option for to go recovery, show me " no comand" and the robo of android .
iago1966 said:
Hi,
I'm sure that, but when show me "writing 'recovery', i think that the hour what the recovery is instaling in the device, but don't write.
When i choose the option for to go recovery, show me " no comand" and the robo of android .
Click to expand...
Click to collapse
What recovery are you trying to flash?
If you are flashing stock recovery , the "no command" screen with the android robot is correct.
tomparr said:
What recovery are you trying to flash?
If you are flashing stock recovery , the "no command" screen with the android robot is correct.
Click to expand...
Click to collapse
I tried recovery of Alberto97(tree versions), tried also chinese recovery, both does not worked.
Did you test the recovery you want to flash by using
fastboot boot recovery
?
It is a bad idea to directly flash an untested recovery. You may get the wrong file. Your download may be broken. Just test it at least once using fastboot boot, and if it runs you may try to flash. I am sure I don't want to flash anything that does not run. Usually I do not flash, but run using the cable if I need it. Do you really need the recovery when you're away from your computer?
I hate doing this since I've been a long time user and usually am able to figure stuff out on my own, but I'm hoping there is an easy fix. I dirty flashed the new aokp update over an older aokp version for the pixel xl and i forgot to flash the twrp image after. Now the system ui crashes upon boot (no surprise there) and I can only get into bootloader and the stock phone recovery. How do I get twrp back?
localceleb said:
I hate doing this since I've been a long time user and usually am able to figure stuff out on my own, but I'm hoping there is an easy fix. I dirty flashed the new update over an older aokp version for the pixel xl and i forgot to flash the twrp image after. Now the system ui crashes upon boot (no surprise there) and I can only get into bootloader and the stock phone recovery. How do I get twrp back?
Click to expand...
Click to collapse
You fastboot boot twrp then flash it in twrp. The same way you got it the first time.
pcriz said:
You fastboot boot twrp then flash it in twrp. The same way you got it the first time.
Click to expand...
Click to collapse
I used the toolkit last time, but I cant adb to recognize the phone in its current state
localceleb said:
I used the toolkit last time, but I cant adb to recognize the phone in its current state
Click to expand...
Click to collapse
This why I wouldn't use a toolkit, you're just kind of handicapping yourself..
You don't need adb to fastboot. either you are using adb (in the booted OS or in recovery) or you are using fastboot (in the bootloader).
You should take a gander at a few of the guides in the Guides section on how to install recovery.
TWRP Thread:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
How to Guide for Beginners (look for the portion on installing twrp):
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Good luck.
localceleb said:
I used the toolkit last time, but I cant adb to recognize the phone in its current state
Click to expand...
Click to collapse
If you are in bootloader mode when you type adb commands it will fail. You use Fastboot commands at that point.
ADB commands are for when tbe phone is booted normally.
TonikJDK said:
If you are in bootloader mode when you type adb commands it will fail. You use Fastboot commands at that point.
ADB commands are for when tbe phone is booted normally.
Click to expand...
Click to collapse
Can you mount the system and use adb commands through the stock recovery? I can't seem to get any fastboot or adb commands to work at all. Even when the system is booted up. The system ui crashes, but shouldn't adb commands still work at that point?
localceleb said:
Can you mount the system and use adb commands through the stock recovery? I can't seem to get any fastboot or adb commands to work at all. Even when the system is booted up. The system ui crashes, but shouldn't adb commands still work at that point?
Click to expand...
Click to collapse
Who knows what else crashed if the ui crashed. Power down, count to ten. Then power and vol down. Once in recovery, connect it to the computer. Not before.
Fastboot devices
If it shows flash the factory image. Modify the bat file and remove the -w to save your data.
If it doesn't connect try other usb ports. Mine won't connect to my front panel, only the rear.
And try another cable.
TonikJDK said:
Who knows what else crashed if the ui crashed. Power down, count to ten. Then power and vol down. Once in recovery, connect it to the computer. Not before.
Fastboot devices
If it shows flash the factory image. Modify the bat file and remove the -w to save your data.
If it doesn't connect try other usb ports. Mine won't connect to my front panel, only the rear.
And try another cable.
Click to expand...
Click to collapse
Well, in theory if I can get fastboot to work I would want to flash the twrp recovery image and then restore a backup, right?
localceleb said:
Well, in theory if I can get fastboot to work I would want to flash the twrp recovery image and then restore a backup, right?
Click to expand...
Click to collapse
I am not a fan of TWRP backups on the Pixels. Seen a few bricks, especially on R2.
So i have attempted to fastboot flash a twrp img and its failing.
C:\Android\TWRP>fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (26588 KB)...
OKAY [ 0.917s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.020s
Am I safe to try a factory image or am I doing something wrong trying to flash the recovery image. ADB commands don't seem to work at this point for some reason.
Thanks for any help!
localceleb said:
So i have attempted to fastboot flash a twrp img and its failing.
C:\Android\TWRP>fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (26588 KB)...
OKAY [ 0.917s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.020s
Am I safe to try a factory image or am I doing something wrong trying to flash the recovery image. ADB commands don't seem to work at this point for some reason.
Thanks for any help!
Click to expand...
Click to collapse
You are doing it wrong. You copy the TWRP zip to the phone.
Then
Fastboot BOOT twrp twrp-3.0.2-0-RC1-fastboot-marlin.img
That boots you to twrp. Then you install the twrp zip while in twrp.
You can not install twrp any other way.
TonikJDK said:
You are doing it wrong. You copy the TWRP zip to the phone.
Then
Fastboot BOOT twrp twrp-3.0.2-0-RC1-fastboot-marlin.img
That boots you to twrp. Then you install the twrp zip while in twrp.
You can not install twrp any other way.
Click to expand...
Click to collapse
I need to add that I cant boot into the system as the system ui crashes so I have no way to transfer files to the phone at this place.
localceleb said:
I need to add that I cant boot into the system as the system ui crashes so I have no way to transfer files to the phone at this place.
Click to expand...
Click to collapse
Fastboot boot to twrp as I described. TWRP has ADB in it, so then from your computer you can ADB push the twrp zip and install it.
But I still advise you to flash the factory image after removing the -w from the flashall bat file.
TonikJDK said:
Fastboot boot to twrp as I described. TWRP has ADB in it, so then from your computer you can ADB push the twrp zip and install it.
But I still advise you to flash the factory image after removing the -w from the flashall bat file.
Click to expand...
Click to collapse
He shouldn't bother removing the -w. A fresh image is what he is in need of. Wipe the phone and start over. Easy.