Related
Hi guys, I was following the post in the development forum to boot twrp to install the chains superuser zip, but when I do "fastboot boot <recovery filename>" I Just get "waiting for device". I know the USB connection and SDK is working properly because I unlocked the bootloader. I would just flash twrp straight out but the OP said he preferred to wait until factory images were out to do something like that and it sounded like a good idea to me as well. Any idea what I'm doing wrong? Never had this problem with my GNex but then I never tried to just boot a recovery with it instead of flashing either.
Wow sorry apparently I totally noobed that up. I was actually typing "fastboot boot recovery <recovery filename>" while in the bootloader and that's why it wouldn't work. Currently performing a backup via a booted but not flashed TWRP right now.
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Tulsadiver said:
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
jerethi said:
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
Click to expand...
Click to collapse
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
sfhub said:
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
Click to expand...
Click to collapse
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Tulsadiver said:
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Click to expand...
Click to collapse
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Click to expand...
Click to collapse
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
jerethi said:
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Click to expand...
Click to collapse
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
Click to expand...
Click to collapse
Listen to this guy. You can start with the old one if you want then upgrade to the new one later but Supersu modifies your boot.img for you. Like he said, after Fastboot flashing them, Fastboot reboot and before your phone boots up, boot right back into recovery. This will make TWRP stick.
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
jb0ne said:
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
I've always decrypted but that is my personal choice. All I do to root afterwards is flash SuperSU-v2.7.8. That is it. You can adb sideload it (i use twrp for that) or flash it in twrp if you have it already on your phone).
jb0ne said:
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Click to expand...
Click to collapse
You must have a customized boot.img now for root. What customizations you absolutely need to have in boot.img is dependent on how you want root installed, but since you are modifying boot.img, you might as well just stick all the changes you need in boot.img and leave /system untouched.
The default install for SuperSU will make the required changes to whichever boot.img you currently have installed on your system. Generally that consists of disabling dm-verity (integrity check), making encryption optional (not absolutely required), making sepolicy security changes, and adding init script support to load SuperSU binaries later in the boot process.
There are configuration parameters you can feed into SuperSU install to force it to install root on /system instead of systemless, but I would just suggest systemless. It is a cleaner install IMO.
So install the stock boot.img and boot directly into TWRP from the bootloader menu, then install SuperSU and it will modify the boot.img you have installed (and back up original)
The only requirement to keep TWRP (and/or decrypted userdata) is to NEVER boot the phone using a stock boot.img. If you always immediately install SuperSU after flashing the stock boot.img that will satisfy that requirement.
jb0ne said:
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-5x/general/unencrypted-faster-real-world-usage-t3365660
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
trentag1988 said:
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
Click to expand...
Click to collapse
Did you reboot after unlocking or go ahead and install TWRP right after unlocking?
I tried, but I kept getting the " cannot check for corrupt system because bootloader is unlocked" message, and it never fully booted. I managed to fix the 0data partition by fastboot format userdata, but pure Nexus never worked. It tried to boot, but it stuck on the spinning Google logo thing
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
trentag1988 said:
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
Click to expand...
Click to collapse
What firmware are you on?
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
Thanks very much for the detailed assistance. If I wanted to install a custom ROM, do I have to decrypt my user data first? Or can I just install TWRP and then flash?
trentag1988 said:
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
Click to expand...
Click to collapse
I do not believe Pure Nexus is a Nougat Rom. Try starting over and flashing a Rom compatible with your firmware.
I'm having trouble installing TWRP on my Oneplus 3.
I can install it fine through Fastboot, it installs without problem.
But when I actually want to go to the recovery menu (by selecting it in the bootmenu), the screen flickers briefly and I'm returned to the bootmenu.
However, I have found a way to boot TWRP.
When I use the All in One Toolkit, there is the option "Flash TWRP AND Boot it".
This way I can get in TWRP, but as soon as I reboot, I'm having the same problem..
Has anyone experienced this before or know what to do?
Never experienced this problem. But are you sure that you use the correct version of TWRP for your ROM?
And did you try not to flash it via fastboot but just boot it? The command is
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
yes even i had this issue once. i used to get a black screen when i try to enter recovery mode.but later i flashed modified twrp file. And its working fine now.
and try this while trying to enter recovery after installing through fastboot.
fastboot flash recovery twrp.img
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
if you are unable to resolve the issue following this. you can head over to this link.
https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-1.439108/ .
the modified twrp also can be found here.
I've exactly the same problem...No solution at this moment...
EDIT: I found the solution: flash this recorvery:
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
I solved my problem with.
I formated and reinstalled custom rom with gapps.
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Shayded said:
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Click to expand...
Click to collapse
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Flash stock recovery? Does it boot?
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Crazyhat said:
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Click to expand...
Click to collapse
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Puddi_Puddin said:
Flash stock recovery? Does it boot?
Click to expand...
Click to collapse
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
urvianoob said:
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
Click to expand...
Click to collapse
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Hi
Puddi_Puddin said:
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Click to expand...
Click to collapse
Yeah that is what I meant to say lol, I found something in another article on the same problem that worked for a guy, gonna try it soon
---------- Post added at 08:31 AM ---------- Previous post was at 08:22 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
OK I get all of it so basically I flash stock recovery from fast boot, boot into the new stock recovery via fast boot, then flash ROM and I'm done?
OTA works ONLY if you are on stock recovery, rom, kernel.
I suggest to format data in recovery (this will wipe ALL in youre phone),
flash modified recovery (.22, .23. 28 by eng.stk),
flash FULL rom,
flash SuperSU 2.79 stable, if you want root,
flash recovery,
reboot to recovery,
reboot to rom.
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where can I get the stock recovery download?
something like that happen to me when i try to go back from N to MM oxygen, i managed to fixed it by installing the stock recovery then install the 3.26 plus the 3.26 "modem" (if i didnt install this one, my touch screen wouldnt work) after that it just works, then i updated to 3.28
i havent install twrp and do the root for now because dont have time to tinker yet, but i can just do than whenever i have the time
I think ---- and my solution
I think some script is created as we click update...It's running on boot up and causing this problem...
I had this problem yesterday and it took me a lot of time to get my device to working...
SOLUTION: first backup the data(it backsup apps and such) from twrp and other files which are important for you...copy it to a PC.
follow the second step in this thread(it will wipe everything)
It's not allowing me to post link...It's the mega unbrick guide from Oneplus3 forums
It will take you to older version and then flash full zip(nougat build) from modded twrp..restore the backup..don't update until someone finds a solution...I did that and I'm waiting for a solution to continue...
hope it helps
This is how I solved mine.
1) Go back to stock recovery v2
2) adb sideload oos, flash magisk then flash systemless supersu.
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
eko_cahyono said:
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where did you get new stock recovery? link please
paul369741 said:
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Where did you get new stock recovery? link please
Click to expand...
Click to collapse
Yes It works
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
qyrus said:
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
Click to expand...
Click to collapse
If my phone is rooted, flashing through fastboot the stock recovery will remove root?
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Alcolawl said:
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Click to expand...
Click to collapse
I had the same problem, then I got a twrp boot loop, ended up having to boot into slot b and reflash stock img through adb, beware...
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
NYYFan325 said:
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
Click to expand...
Click to collapse
I was on RC1 also
Anyone got some insight to this? Can't be that uncommon of a problem...
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
noidea24 said:
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
Click to expand...
Click to collapse
I never had TWRP stick unless I added another step to your instructions --boot completely into the rom once, go back into the bootloader, open temp TWRP and flash the TWRP zip again. If I didn't do this my recovery would always revert to stock but, strangely, even though I was running a custom rom the combination of the custom rom and stock recovery never bootlooped my phone and I was able to boot from the stock recovery to the custom rom with no problems. The only reason not being able to boot into TWRP was even an issue was that you can't flash any zips in recovery without it. Otherwise the phone ran so perfectly I didn't even realize at first that TWRP wasn't still the installed recovery.
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Also pointing out flashing rooms and certain zips here in the forums WILL revert you back to a stock recovery. Just my last bit of helpful information, hope someone gets it figured out, flashing is already a chore for those of us who like to experiment.
pcriz said:
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Click to expand...
Click to collapse
I was able to boot into recovery after doing this. Got a bootloop booting into system though, but flashing the ROM (and TWRP) fixed it.
Hello,
Try booting to TWRP 3.0.2 RC1 then flash TWRP 3.0.2 RC1 + SR1-SU v2.82SR1 + SU Pixel Fix (from Chains beta thread) one right after the other in the same TWRP session then reboot. Should fix your issue, give you recovery+root without ram dump.
Cheers
Everytime you flash a rom you need to flash twrp before rebooting or you'll lose twrp recovery.
Unfortunately I've had to get my Pixel XL replaced due to a defect and received a Verizon edition XL running 7.1.1. This is what I get for buying it from Best Buy Therefore I cannot unlock the bootloader and this problem no longer applies to me.
I'll keep this thread open for a bit in case it's useful for anyone else. I'll just sit here in all of my Stock-ness.
I couldn't get this to work. Tried flashing stock boot.img, then booting off of the TWRP images but I keep getting TWRP boot loop. Any suggestions? Tried flashing the entire stock image as well and no dice...