I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later
Sudhanshu030299 said:
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later
Click to expand...
Click to collapse
Are you will it be successful L?
shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Click to expand...
Click to collapse
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Sent from my OnePlus3T using XDA Labs
shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img
BillGoss said:
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Click to expand...
Click to collapse
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk? I am confused what to do?
redpoint73 said:
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img
Click to expand...
Click to collapse
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
Temporarily boot into twrp with fastboot, copy zip files to memory using MTP (it will activate automatically, when TWRP boots successfully you can see the phone on your PC), flash them in TWRP, profit.
^ assuming you have already made a backup
Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Click to expand...
Click to collapse
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?
shree alwaz said:
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?
Click to expand...
Click to collapse
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Click to expand...
Click to collapse
Boot password is nothing but forced encryption on?
You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Sent from my OnePlus3T using XDA Labs
shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
As you've now figured out, your mistake is rebooting. As I already described, rebooting before flashing root (Magisk or SuperSU) or patched boot image (or custom ROM w. patched boot image) will by definition wipe TWRP. This is normal and expected.
Fastboot flash TWRP. Then in bootloader screen, select recovery, and it should go to TWRP. Then flash one of the above described files to make TWRP "stick".
---------- Post added at 09:25 AM ---------- Previous post was at 09:20 AM ----------
shree alwaz said:
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk?
Click to expand...
Click to collapse
No, that is not what he is saying. Yes, you need TWRP to flash a custom kernel or Magisk. Fastboot flash TWRP, then immediately select "recovery" from the bootloader menu and do not reboot the phone.
You don't need custom kernel/Magisk to flash TWRP (that would be a cart before the horse type situation, as you somewhat figured out). But doing so, makes TWRP "stick" and not get wiped (replaced with stock recovery).
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
shree alwaz said:
Boot password is nothing but forced encryption on?
Click to expand...
Click to collapse
Encryption is not the same as forced encryption.
Forced encryption means that if your phone is decrypted, flashing an update will (I believe) "force" it back to being encrypted. For folks that want to stay decrypted, they will want to disable forced encryption. If your phone is encrypted, it doesn't matter if you have forced encryption or not. It will stay encrypyted in either case.
BillGoss said:
You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Click to expand...
Click to collapse
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
shree alwaz said:
Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
Encryption is always useful if paired with bootup password - in case of theft no one can read your data.
You will be asked for password, if you explicitly set it up in OS.
And what option do you mean?
shree alwaz said:
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
Click to expand...
Click to collapse
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
shree alwaz said:
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?
redpoint73 said:
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?
Click to expand...
Click to collapse
Thanks you clarification. After reading your explanation even I got the same question 3 and 4.
Related
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Type: fastboot boot (path goes here)
You can drag and drop the twrp img into the command window. This will ensure you have the correct path
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
mingkee said:
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Click to expand...
Click to collapse
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
joesee said:
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
Click to expand...
Click to collapse
The instruction shows how to flash recovery.img with TWRP though I have no clue how to do it.
I got that error the first time I did it, it was because of a misspelling of the command.
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Vseprz said:
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Click to expand...
Click to collapse
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
joesee said:
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
Click to expand...
Click to collapse
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Vseprz said:
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Click to expand...
Click to collapse
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
joesee said:
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
Click to expand...
Click to collapse
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
99problemz said:
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
If boot loader is unlocked you should load twrp from fastboot.
Vseprz said:
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
If boot loader is unlocked you should load twrp from fastboot.
Click to expand...
Click to collapse
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
joesee said:
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
Click to expand...
Click to collapse
I'm glad it all worked out! :good:
finding I have to re-flash with flashify each time
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
jdoebean said:
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
Click to expand...
Click to collapse
You drop the twrp file
In fastboot folder open command prompt and flash twrp first just rename it simply to recovery.img while in the fastboot folder
Type fastboot flash recovery recovery.img
Or just fastboot flash recovery.img
Then it should boot you into twrp
Once booting into twrp flash the supersu zip in your internal sd
Once you have root and reboot all you have to do is use flashify app and download twrp from the app and flash it Twrp sticks from there.
Sent from my LGMS631 using XDA Free mobile app
Hello everyone,
so here is my configuration:
-latest TWRP (3.0.2) with F2S support
-bootloader unlocked
-the N6 is rooted
-ROM: AICP MM
2 days ago I tried to reboot to recovery to flash a more recent version of my AICP ROM. I just had the time to see the TWRP boot logo and then the phone rebooted to load the system. I can't access anymore to my recovery. I tried to rename the twrp directory on the internal SD but it does not change anything.
I reflashed TWRP with ADB and fastboot, but it didn't resolve the problem.
The only change I made recently was to flash a new radio to try to improve my connectivity.
I flashed 5.34 with the new bootloader in fastboot. Then I tried 5.32 without changing the bootloader and finally the 5.36 with the latest bootloader. So I don't know when the problem occured but now my phone even reboots randomly !
So if anyone has a solution you're welcome !
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Had this Problem on an other device . No recovery flash with fastboot . Dont no how , but Trwp manager APP from playstore did it .
you have to flash twrp right.. if you use a toolkit or flash the recovery with fastboot boot(instead of fastboot flash) then it will only boot into twrp 1 time, then you will need to flash it again if you want to use it again.
Strephon Alkhalikoi said:
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Click to expand...
Click to collapse
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
marcp39 said:
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
Click to expand...
Click to collapse
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
simms22 said:
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
Click to expand...
Click to collapse
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
marcp39 said:
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
Click to expand...
Click to collapse
sounds like you need to clear the recovery partition, then flash twrp again.
simms22 said:
sounds like you need to clear the recovery partition, then flash twrp again.
Click to expand...
Click to collapse
With "fastboot erase recovery" ?
marcp39 said:
With "fastboot erase recovery" ?
Click to expand...
Click to collapse
honestly, i dont remember how.
So here are my last attempts:
-I've tried to clean the cache with "fastboot erase cache", I thought it could be corrupted. BIG MISTAKE ! This time the phone is bootlooping when lauching the ROM...
And of course, I'm making some backups but they are on the "internal sd"... So I can't access my files anymore !
-I've also tried "fastboot erase recovery" and reflashed recovery. No improvement.
-I've downgraded the bootloader from 71.21 to 71.18. Nothing changed.
-I was asking myself if last time I didn't enter a wrong command in typing "fastboot flash boot bootloader.img" instead of "fastboot flash bootloader bootloader.img". So even if I've added benzocore on my AICP ROM, I decided to flash the boot.img from AICP zipfile on the boot partition (+ erase boot). So this time no more bootlooping of the ROM, because I'm stuck on the google logo :crying:...
I've never encounter such a desperate situation ! I don't even understand why I can't boot in recovery...
I could reflash a factory image on my phone, but this would erase all my datas !
Do you think I could reflash a factory image (except the data partition), just to be able to get a valid recovery, and access my files from the computer ? Then I could erase data partition, and reflash a new ROM ?
I don't want to precipitate the next actions because I don't have any joker... and with this stupid idea of not putting any µSD slot in most phones nowadays we're captive of the situation when the phone is bricked ! We can't recover data easily, even with adb pull (which does not work in my case of course).
So please share your ideas, they'll be welcome ! I've read A LOT of posts on XDA and others, but no solution until now....
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
marcp39 said:
I could reflash a factory image on my phone, but this would erase all my datas !
Click to expand...
Click to collapse
Don't use FlashAll, it's usually broken, anyway. But rather unpack the zip, flash boot and system. And either flash cache or erase it. It does the same.
HueyT said:
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
Click to expand...
Click to collapse
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
marcp39 said:
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
Click to expand...
Click to collapse
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
Click to expand...
Click to collapse
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
Click to expand...
Click to collapse
Yeah unfortunately we can do it with adb (like this http://stackoverflow.com/questions/8650407/how-to-copy-selected-files-from-android-with-adb-pull) but not with fastboot. Tomorrow I'll try to flash each *.img from MOB30M separately and see if I can recover a working recovery to access to my datas ! Thanks for your answer btw.
Hello everyone !
So here are the last news...
I've tried an older TWRP like 2.8.x.x same problem.
I've flashed all the *.img from MOB30M except data, but my recovery was still not accessible !!!
So I was resigned to format my data and flash the *.img on it.
This time it worked, my N6 was coming back to life !!! Then I had to root it, flash the recovery, remove encryption and format data with F2FS !
I still don't understand how a corrupted (?) data partition could block the running of recovery, that's strange !
So now I have to restore the data from a TWRP image dated 04-16 I had on my NAS...I can tell you that in the future I won't let my recent backups only on internal storage !
Will you believe me if I tell you that the same problem is occuring again :crying: ?
Several days ago, it started when the impossibility to enter the recovery but this time it does not reboot in bootloader, just stuck... Now I got random reboots and stange behaviour from applications !
I NEVER had a serious problem like that with my N6 before. So I don't understand how can I get data corruption like this ? Last time I was using Benzo kernel, now DeYuS kernel but with no exceptional settings, no overclocking.
I've just disabled "forceencrypt" and convert data to F2FS (no problem before).
So does anyone have a clue about this problem ?
Hi all,
What happens if you take a stock 3T, upgrade it all the way to Nougat the normal way, then proceed to unlock the bootloader, flash TWRP and supersu?
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard? Is that even a problem in the sense of waiting until a fixed version of TWRP is released? The point is to just flash supersu for the moment. No other need to access that partition from recovery, is there? Or does it directly impact my ability to upgrade TWRP in the future?
And another question: would decrypting the phone after the stock to Nougat update, and only then flashing TWRP&root be of any use? Is this even possible at the moment? I can hold on without encryption until there's a proper version of TWRP, kernel sources are released etc.
I don't seem to find any info on these scenarios. Has anyone tried any of this?
Thank you!
Good questions.
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard?
Click to expand...
Click to collapse
I can confirm 3.0.3.0 has problems with decrypting and mounting sdcard. A new version of TWRP should fix this.
No other need to access that partition from recovery, is there?
Click to expand...
Click to collapse
Well, the need to access partition from recovery depends. You won't be able to flash anything from TWRP. I could sideload different recoveries without decrypting but had to decrypt (with the format userdata command from cmd prompt) to revert to 3.5.4 from TWRP. In the end I mostly downgraded due to bluetooth issues.
I am having the same decryption issue... TWRP shows 0MB as the storage
What should be done now..?
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Amar97 said:
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Click to expand...
Click to collapse
Did that already but did not work.. Even tried the setting up of pattern method.. that too did not work...
Also force decrypted with Toolkit but still the same
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Amar97 said:
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Click to expand...
Click to collapse
why not use 3.0.3.0?
Solnir said:
why not use 3.0.3.0?
Click to expand...
Click to collapse
Don't really know, probably tried solving the problem by trying with the older version and then didn't feel like upgrading to the newer 3.0 after fixing the problem.
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Same issue
---------- Post added at 10:08 AM ---------- Previous post was at 09:58 AM ----------
try this
n your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
This is the TWRP thread... How can it help in my situation?
I flashed the dm-verity and forced encryption disabler zip, wiped all data and a custom rom. It doesn't help.
Primokorn said:
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Click to expand...
Click to collapse
In twrp: Advanced->Terminal
In Terminal type wipe_misc and press enter. Reboot to system.
EDIT: this erases misc partition by dding /dev/zero to misc partition. (I've tested both, wipe_misc sceipt as well as dd by hand - it's safe; you will not loose anything [if there would be something on data... SCNR ])
---------- Post added at 19:18 ---------- Previous post was at 19:14 ----------
networx2002 said:
Same issue
[...]
Go to [Reboot] -> [System].
Click to expand...
Click to collapse
Very true, but that answers not his question...
nvertigo67 said:
In twrp: Advanced->Terminal
In Terminal type wipe_misc and press enter. Reboot to system.
Click to expand...
Click to collapse
Already tried. Is there something else to do after entering this command? (wipe data, flash rom again..)
EDIT: flashing the stock recovery and full 4.0.2 OTA might help?
Primokorn said:
Already tried. Is there something else to do after entering this command? (wipe data, flash rom again..)
EDIT: flashing the stock recovery and full 4.0.2 OTA might help?
Click to expand...
Click to collapse
Stay on twrp (3.0.3-1). Wipe art, system, data and cache. Flash full 4.0.2. Go to twrphome->mount and check if system is unmounted (*)- if so: boot to system; if system is mounted reboot to recovery and dirty flash (without any wipe) full 4.0.2 again; boot to system.
Whenever I had this boot to recovery but not to system, wipe_misc was allways sufficient.
BTW: disconnect usb before rebooting. otg-sticks as well charger result sometimes in unpredictable reboot behavior.
(*) I've still not found what's triggering this, but if after flashing system is mounted, you can't boot directly into system, and twrp tells you on reboot, that no system is installed, even if you just flashed a rom...
Primokorn said:
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Click to expand...
Click to collapse
I ran into a similar problem with mine yesterday / today with 3.0.4-0....after countless tests, it came down to holding down the power button for 20s and releasing (hard shut down)...wait 20s, hold power for it to come back on, ROM loaded up.
I tried every boot option from TWRP, and just kept looping.
Give this a try, as trivial as it seems, fixed it for me.
stephlal said:
I ran into a similar problem with mine yesterday / today with 3.0.4-0....after countless tests, it came down to holding down the power button for 20s and releasing (hard shut down)...wait 20s, hold power for it to come back on, ROM loaded up.
I tried every boot option from TWRP, and just kept looping.
Give this a try, as trivial as it seems, fixed it for me.
Click to expand...
Click to collapse
How could it be possible?
It works! Thanks for your help.
I've flashed Tesla ROM and the phone boots. I'm charging my phone to enable encryption then I'll see how to set a boot password (without any issues this time lol).
I set a password to encrypt my data and flashed TWRP 3.0.1-0 again.
I'm not able to decrypt my data in TWRP...
After a reboot, the ROM doesn't recognize my password anymore. I'm fed up with encryption!
Primokorn said:
I set a password to encrypt my data and flashed TWRP 3.0.1-0 again.
I'm not able to decrypt my data in TWRP...
After a reboot, the ROM doesn't recognize my password anymore. I'm fed up with encryption!
Click to expand...
Click to collapse
imo just the unbrick tool to go back to fully stock and start the whole process again
I had this issue with the password.
I had to flash the stock recovery, go into stock recovery, it will ask you for the password, just choose forgot password and it will prompt to format everything. Click yes to accept. After it formats, flash the custom twrp recovery. Once it flashes, load recovery and flash the 3.5.4 bootloader here:
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
OR you can boot into bootloader/fastboot and type in these commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
m0d hipp¥ said:
I had this issue with the password.
I had to flash the stock recovery, go into stock recovery, it will ask you for the password, just choose forgot password and it will prompt to format everything. Click yes to accept. After it formats, flash the custom twrp recovery. Once it flashes, load recovery and flash the 3.5.4 bootloader here:
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
OR you can boot into bootloader/fastboot and type in these commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Thanks but I'll just enjoy my phone for now. Encryption can wait.
Only these two fastboot commands will avoid the wrong password issue? It seems to be helpful to remove the dm-verity error and I don't have it.
Sorry I guess I misinterpreted the issue. I thought that the dm-verity and the encryption issue were somehow linked. Anyway, the first few steps I took with flashing the stock recovery and wiping everything from stock recovery is what fixed the immediate encryption issue for me.
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
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.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
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.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!
Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going