Related
UPDATE: Still no solution found - new Ideas very welcome.
Hi there,
I'm at the end of my wits with my HOX which is with a german o2 branding. After getting stuck in bootscreen after athe OTA-Update from 1.26.207.2 to 1.28.207.9 - which failed for some reasons. I tried to install different Custom-Roms, none of which would boot beyond the first HTC-Screen.
The latest one I tried was Cyanogenmod, that did boot fully but I got constant "andoidupi crashed" messages, so I tried to reflash it.
After that things got weird, because right now I can't really do anything anymore. If I try to relock it via "Fastboot oem lock" it just reboots and it boots straight into CWM 5.8.3.1 but when I get back to bootloader its still "**** UNLOCKED ****"
I can flash boot.imgs via fastboot flash... but even so its says at the command prompt that it was successful flashed, it really isnt. No matter what - at reboot I will boot into CWM.
It is like working on a virtual machine - the HOX gives all the right responses, but noting I try to flash is permanent.
I can't relock, I can't flash new recoverys, can't flash new boot.img and everything I push onto the SDCARD via adb is gone after reboot. If I delete a file that is actually on the SDCARD it will be back after reboot, like it was never really deleted.
I already checked my drivers, switched off Antivir, tried it on a different PC, reinstalled the drivers etc etc.
My HOX is from German o2
I've got HBOOT 0.94.0000 and Radio 1.1204.90.13
If anyone has any suggestions besides "You have to fastboot flash recovery/boot..." and "Don't forget to erase cache after every flash" I'd be very thankfull
Best regards,
Thad
did you try to re-download your fastboot ?
and did you navigate on CMD to the right place where your fastboot folder is stored ?
You need to flash the stock recovery before you relock your bootloader.
Flash stock recovery
Relock bootloader
Install ruu
Hope this helped
EDIT: Just read your post again and you said you've tried flashing recoveries, sorry, its late here
Sent from my HTC One X using xda premium
i made a compilation of threads about this matter, it might help you. check it out..
http://forum.xda-developers.com/show....php?t=1692681
Thanks for all suggestions on the topic
@muamers
I redownloaded fastboot multiple times, but its all the same, sadly The problem is: It seems to work. I get all the right replies on the command prompt, but after rebooting nothing is flashed.
@mikey0105
The link goes to a 404 page - could you post it again?
Thank you
tadeausz said:
Thanks for all suggestions on the topic
@mikey0105
The link goes to a 404 page - could you post it again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1692681
Thank you Gibeon & mikey0105
I retried all the steps there, but still no change.
The problem still is the same. This is what I get in response:
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.044s]
finished. total time: 0.045s
>fastboot flash boot boot.img
sending 'boot' (4156 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.470s]
finished. total time: 1.008s
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.034s
>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
sending 'recovery' (5760 KB)...
OKAY [ 0.829s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.548s]
finished. total time: 1.377s
So everything should've worked out great. But not so, because in reality he really hasn't flashed anything to the HOX permanently. When I reboot to recovery I still have the OLD CWM without fixes. The boot.img isn't flashed either.
As I said: It's like working on a virtual machine, where nothing really has any effects, it's a if all the fastboot commands only affect the RAM but are not really flashed to Memory.
And I still can't relock, still can't reboot-bootloader from Bootloader.
Any other ideas are welcome...
Greetings,
Thad
Bump.
Nobody any more ideas?
Bump. Still no solution after many month
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
robchongke said:
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
tadeausz said:
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
Click to expand...
Click to collapse
are you doing
fastboot flash recovery recovery.img
Or
fastboot boot recovery.img
I'm not sure the second one works, but if it did, it would do what you describe. So do the first.
help
I'm running ICJ ROM AOKP. last time I flashed this rom and flashed the gapps too,
Now I want to install a new package of gapps, SO, do I need to wipe data, cache, dalvic cache to install the gapps ???
Note that I'm going to install ONLY the gapps...
THANKS
aimen7 said:
i'm running icj rom aokp. Last time i flashed this rom and flashed the gapps too,
now i want to install a new package of gapps, so, do i need to wipe data, cache, dalvic cache to install the gapps ???
Note that i'm going to install only the gapps...
Thanks
Click to expand...
Click to collapse
That's the third time I've read this question from you.
STOP POSTING IT NOW!
BenPope said:
That's the third time I've read this question from you.
STOP POSTING IT NOW!
Click to expand...
Click to collapse
sorry, I'm CONFUSED about that
Aimen7 said:
sorry, I'm CONFUSED about that
Click to expand...
Click to collapse
Make 1 new thread or search....don't go posting it in every Q&A thread !
That is confusing ! :thumbdown:
Hey,
I have here a Galaxy Nexus Device, bought from ebay.
Nothing will really work right now. I try to flash the original google factory image.
Loaded everything, have fastboot access.
Followed the steps to flash the files over fastboot.
On Step: fastboot -w update factory-image-name nothing happens
The device says "flash:system" and the promt says writing "system" - but thats for about 20 Minutes. Tried these a lots of times.
Downloaded the toolkit here on xda. Flashed the stock-recovery. Tried that again. Nothing happens.
I'm don't know, what I'm doing wrong.
Something is wrong with the device.
There is a rom on the device. Everytime I safe an e.g. image or data on the sd and restart the device, the file is lost. I can't even restore factory setting via rom. The device boot and then appears a android man with an red triangle. After 2 minutes the device restart itself and nothing happens. Same rom as before.
The other thing thats strange. Tried to flash the new JB google factory reset. In the steps, where i should update and flash a new bootloader - the one with the C03 on the end, everything went fine. After I reboot the bootloader - the old bootloader is sill on the device - A03....
Dont know whats going on there.
Would be awesome if someone could help me.
Shizophren said:
Hey,
I have here a Galaxy Nexus Device, bought from ebay.
Nothing will really work right now. I try to flash the original google factory image.
Loaded everything, have fastboot access.
Followed the steps to flash the files over fastboot.
On Step: fastboot -w update factory-image-name nothing happens
The device says "flash:system" and the promt says writing "system" - but thats for about 20 Minutes. Tried these a lots of times.
Downloaded the toolkit here on xda. Flashed the stock-recovery. Tried that again. Nothing happens.
I'm don't know, what I'm doing wrong.
Something is wrong with the device.
There is a rom on the device. Everytime I safe an e.g. image or data on the sd and restart the device, the file is lost. I can't even restore factory setting via rom. The device boot and then appears a android man with an red triangle. After 2 minutes the device restart itself and nothing happens. Same rom as before.
The other thing thats strange. Tried to flash the new JB google factory reset. In the steps, where i should update and flash a new bootloader - the one with the C03 on the end, everything went fine. After I reboot the bootloader - the old bootloader is sill on the device - A03....
Dont know whats going on there.
Would be awesome if someone could help me.
Click to expand...
Click to collapse
I flash a lot of time on this type of device so far doesn't give a problem to me. Maybe something wrong with your device or maybe you can try to flash it via GNex toolkit and download the .tgz file from program first maybe you will have a luck.
sounds a little like bad flash ROM but I'd leave that to the pros to diagnose... mabye there was a cause why somebody put it on ebay ^^
Instead of flashing the factory image zip you could extract the system.img, boot.img, and data.img from that zip and flash them one by one.
Follow this guide: http://forum.xda-developers.com/showthread.php?p=25477039
Sent from my Nexus 7 using xda premium
@compuzones thanks for your answer. I tried this already. But no success.
@Hannes The Hun you could be right, but whats could cause the problem? I have no clue
@El Daddy I'll give it a try.
Edit:
So this is what happend. Would appreciate some expert thoughts on it.
I extracted the factory image and tried to flash the seperate files manually.
First the bootloader:
In fastboot mode my device shows me, that theese bootloader is on it:
PRIMALA03
So i pushed the newer one on it - fastboot flash bootloader bootloader-maguro-primelc03.img
sending bootloader - OKAY
writing bootloader - OKAY
the operation seems to work. But, when I'm restart-bootloader again, I have still PRIMELA03 as my bootloader.
Ok, I thought that unimportant. So tried to go on with the system.
fastboot flash system system.img
sending system OKAY
writing system..............
So here we go. It writes the system for over 20 minutes. Don't know why it exactly happens.
This happens wether I try to flash a factory image with the toolkit here from xda, or the google way or just this way.
Whats strange too.
Wanted to flash via CMW a custom rom. Just to trie it, if this woul work.
I flash CWM via the toolkit. The operation went fine. When I trie to boot in recovery, I get still the little Android with the red triangle and nothing happens.
Althouh the rom, that I put on the sd is gone after restart! Nothing there. Everythings wipe the whole time I start the device.
Edit2: After 25 Minutes it says system write ok. Here what i did:
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash system system.img
sending 'system' (396675 KB)... OKAY
writing 'system'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)... OKAY
writing 'userdata'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash boot boot.img
sending 'boot' (4366 KB)... OKAY
writing 'boot'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fsatboot flash recovery recovery.img
Der Befehl "fsatboot" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (4708 KB)... OKAY
writing 'recovery'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot reboot
rebooting...
Click to expand...
Click to collapse
But still the old rom on my device ^^ can't figure out whats all about. The device saves absolutely nothing.
Is there a possibility to check the file system or sdcard for errors or something?
Even factory reset over the android option doesn't work. It reboots and then appears the Android with the red triangle again. After some time, the rom boots again^^
I update, my ROM from cyanogenmod ROM 10.1 m1 to 10.1 m2 ROM and know my galaxy nexus is stuck on boot loop animation! I tried, tacking out the battery and then turning it back on no luck in also tried the ( volume button and power button method) and still no luck with that. Is,there a way I could fix it?
wipe data and reflash rom.
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
Never, mind i got it working know!
mrcoleminer said:
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Zepius said:
mrcoleminer said:
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
Chamaeleon said:
Zepius said:
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
Soulaysahmi said:
Chamaeleon said:
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
I was using the ClockworkMod (I don't remember exactly the version number but I updated recently and it was the touch screen one). I'll try to re-install also the recovery with the very last version (6.0.4.7). Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
Chamaeleon said:
Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
have you tried adb sideload?
Soulaysahmi said:
have you tried adb sideload?
Click to expand...
Click to collapse
Just tried.
On the terminal after the command
adb sideload cm-11-20141115-SNAPSHOT-M12-maguro.zip
it tells me "error: closed"
I also tried to reinstall the Clockwork via bootloader but didn't change the situation (still not able to do a complete factory reset)
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Soulaysahmi said:
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Click to expand...
Click to collapse
You are right, I didn't click "install zip from sideload" before. Now I tried in this way and, effectively, it worked: I managed to send and install the zip apparently without any problem but than after rebooting I'm still not able to turn on the phone completely. Again the same problem. I re-tried to do wipe data/factory reset both from the recovery and using adb but didn't managed to finish the process...
It seems I tried all the options since now.... but my nexus is still unusable...
did you try getting back to stock rom using any guide on this forum?
Soulaysahmi said:
did you try getting back to stock rom using any guide on this forum?
Click to expand...
Click to collapse
I tried but still with the same result. I'll try to follow the guide I found here
I mean through methods other than recovery, through fastboot mode or odin mode.
Soulaysahmi said:
I mean through methods other than recovery, through fastboot mode or odin mode.
Click to expand...
Click to collapse
I tried to Restore Galaxy Nexus to Stock (as described here) with the proper google image but in the last passage I get:
$ fastboot -w update image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMELC03
Baseband Version.....: xxx
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
FAILED
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'
I put all I need in one folder and I decided to update the bootloader at the PRIMEMD04 version but apparently I didn't managed because doing again the procedure I was getting the same error
ps: I'm using linux so I don't have odin
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Soulaysahmi said:
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Click to expand...
Click to collapse
Yes I have BOOTLOADER VERSION - PRIMELC03
With fastboot I tried to install the PRIMELC04 bootloader
$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.969s]
finished. total time: 8.278s
$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But than, after the reboot, on the screen it's still written BOOTLOADER VERSION - PRIMELC03
I think this is the main problem now... if it's not updated the bootloader I can not reinstall the rom probably...
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Soulaysahmi said:
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Tried as you suggested to install the PRIMELC04 bootloader flashing each image.
Apparently is not possible also in this way. After rebooting on the screen is still written BOOTLOADER VERSION - PRIMELC03.
So I tried to install a stable cyanogenmod 10.2.1 (which should work with the bootloader 03).
I used adb sideload and after the "installing updates" message, everything stopped with the message "fixing fs_size in crypto footer". After more than 30 min I rebooted and the situation was the same as before.
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 !
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.