Related
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.
I've been trying to flash an AT&T HTC One M8 with the GPe ROM found here: http://forum.xda-developers.com/showthread.php?t=2706441
I've used this guide and everything went fine: http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
I was in the TWRP Recovery and wanted to format the internal sd card for a fresh start, so I formatted. Afterwards I was unable to get back into the recovery, for some reason I can't erase or format recovery using fastboot, erasing the cache and flashing the recovery image again only brings me to a flickering TeamWin screen, then tries to normally boot but nothing is there for it to boot into so it just sits in a boot loop.
I've tried Philz recovery as well. That works for a little bit but after 10-15 seconds the phone tries to boot normally again and I get stuck in the boot loop.
I tried running `fastboot oem rebootRUU`, that brought me to a black HTC screen and gave me the ability to use fastboot. In RUU mode, I erased the cache again and reflashed the recovery, then erased the cache again and rebooted to fastboot. Tried to boot into Recovery and was greeted with the flickering TeamWin logo and a boot loop.
Can anyone give me a hand here?
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I'm trying that now, will post back with results
androidbuff123 said:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..
http://forum.xda-developers.com/showthread.php?t=2708589
This should set you to the GPE that you were on.
If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
Click to expand...
Click to collapse
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
JustLikeThat said:
I tried that and I'm still in a boot loop. This was the output:
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.618s
$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip
target reported max download size of 1830711296 bytes
sending 'zip' (522633 KB)...
OKAY [ 18.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 18.404s
Click to expand...
Click to collapse
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
JustLikeThat said:
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb`
Click to expand...
Click to collapse
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
JustLikeThat said:
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
Click to expand...
Click to collapse
if you are able to do fastboot commands.. try using the firewater s-off http://firewater-soff.com/instructions/
you may not be to do this either since you said you don't have adb. Can't help you beyond here.. If you are able to get to RUU mode.. I would suggest trying flashing RUUs since they are most comprehensive.
Did you try flashing the sense RUU?
androidbuff123 said:
You need to be soff
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
You can also boot a recovery without actually flashing it. Once in boot loader try
flashboot boot recovery.img
Use the actual name of the recovery image instead of recovery.img.
Make sure the twrp or whatever recovery you are using is in the same folder.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
Using Philz, I see that it can't mount or open anything in `/cache/`... I'm guessing that that's because I wiped the internal storage with TWRP initially. Is there anyway I can mount my phone and add the directories manually?
It really sounds like I need access to ADB but I can't run anything because nothing can mount the internal storage.
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
androidbuff123 said:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.
Have you tried fastboot flash boot.img?
of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
Click to expand...
Click to collapse
I've tried that now. It looks as if it's trying to boot but then I just end up back in the bootloader. I'll try with a different image.
In the mean time: I had managed to get Philz CWM formatting the storage properly (with /system, /data, etc), and without any errors that it couldn't mount /cache/recovery (because I had managed to format /cache manually before it rebooted). It's still rebooting 10-15 seconds after booting into recovery, even in the middle of formatting...
I have done more exploring in between reboots and it doesn't look like there's an `/sdcard` directory that it can mount either
umjammerlammy said:
In the bootloader, what is next to OS-?
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
Click to expand...
Click to collapse
Nothing, since it was wiped earlier.
JustLikeThat said:
Nothing, since it was wiped earlier.
Click to expand...
Click to collapse
Try flashing the recovery using the htc one all-in-one toolkit. see if that helps. I'm pretty much out of ideas beyond this point.
JustLikeThat said:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...
But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
Click to expand...
Click to collapse
Restore a stock backup in twrp then flash the att ruu
If you are in the US message me your number and I can walk you through it
Sent from my HTC One_M8 using XDA Premium 4 mobile app
UPDATE
As mentioned in my initial post, I wiped/formatted my internal memory so I have no internal file structure.
My attempts at booting into or flashing a recovery are failing after 10-15 seconds since they can't mount to anything in the internal memory.
I'm stuck in Bootloader and it seems like the only tool I can utilize is `fastboot`.
I'm currently looking for a way to restore a file structure to my internal memory.
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
What about flashing the stock recovery and then trying a factory wipe?
Hi there,
I have just tried to root my HTC one, and I am now stuck in the boot loader screen and it is showing *Tampered* at the top.
Can someone please advise me, or point in the direction of what I need to do now?
Thanks.
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
jeanxx said:
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
millhhaus said:
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
Click to expand...
Click to collapse
Once you have unlocked your bootloader then it will show you tampered.
Download a custom recovery (I prefer TWRP) and flash it via fastboot.
Then download @Chainfire Supersu flashable zip from his site and flash it in recovery.
You have rooted your phone.
Ater placing my device into fastboot mode, I have tried flashing my downloaded TWRP file to my HTC One in Terminal using these instructions:
Now let's flash your downloaded TWRP file to your HTC One. Type one of the following commands into your terminal window, depending on which file you downloaded above.
For the International editions, type:
fastboot flash recovery Desktop/openrecovery-twrp-2.7.0.2-m8.img
However I get the following error:
command not found
any help would be most appreciated.
Did you setup your mac to use adb / fastboot commands?
lazydesi said:
Did you setup your mac to use adb / fastboot commabds?
Click to expand...
Click to collapse
I feel like a total N00b at the moment. LOL.
No. How do I do that?
try this
http://forum.xda-developers.com/showthread.php?t=2638673
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
millhhaus said:
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
Click to expand...
Click to collapse
hi,
plz try CWM, M8 got some issues with twrp.
philz_touch_6.26.6-m8.img is the stable version plz try that.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
millhhaus said:
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
Click to expand...
Click to collapse
is your problem similar to this?
http://forum.xda-developers.com/showthread.php?t=2784232
May be you are using the wrong version.If you have international device you should try international version of philz/cwm recovery.I would suggest you to use TWRP since it is basically meant for htc devices.
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
millhhaus said:
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
Click to expand...
Click to collapse
because you are using M7 files mate. you need to use M8.
M7 - Htc one - 2013 model
M8 - Htc One - 2014 model
http://download.cyanogenmod.org/?device=m8
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.
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.