• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

boots to twrp then have to choose bootloader then start help!

S

Some Guy Here

Well-Known Member
I was board and reinstalled my stock rom from a twrp back up then I tried OTA update and that failed so I went back to LinegeOS twrp backup I did right before and it asked for a pin so I just did a fresh install and I have this problem when the phone boots it boots to twrp and then I have to choose reboot bootloader and choose start and it works, any ideas why it wants to boot to twrp instead of the system instead?
 
Some Guy Here said:
I was board and reinstalled my stock rom from a twrp back up then I tried OTA update and that failed so I went back to LinegeOS twrp backup I did right before and it asked for a pin so I just did a fresh install and I have this problem when the phone boots it boots to twrp and then I have to choose reboot bootloader and choose start and it works, any ideas why it wants to boot to twrp instead of the system instead?
Click to expand...
Try to run these commands in fastboot and reboot:
fastboot erase ddr
fastboot oem fb_mode_clear
 
did not work looks like the first command fails
I am on twrp 3.1.1 could the OTA update screwed it TWRP up ? should I install 3.2.2 ? and if so can it be done through twrp flash zipp? or would I have to do the whole twrp instal through fastboot as if it where the first time ?
 

Attachments

  • phone.PNG
    phone.PNG
    14.6 KB · Views: 232
Last edited:
I do have it on my laptop so I can just open terminal in linux and type this in
sudo fastboot erase ddr
sudo fastboot oem fb_mode_clear
?
 
I have 3.1.1 installed on my phone xt1775 owens it boots into linageOS but like I said when I restart it boots to twrp and I have to choose reboot then bootloader then start
 
ok I flashed it and verified everything went correct no errors booted into recovery and 3.2.3 version installed but guess what it does the same thing, as befor boots to twrp and I have to repeat the same thing
 
ok I searched all day and nothing seems to work so my only option is to go full stock at this point, I reinstalled a backup of stock twrp I had and the qestion now that I have I don't see my retail exact match in the firmware's I bought a Best Buy unlocked version no carriers installed could you tell me if you see it in the list here in a screenshot
 

Attachments

  • Screenshot_20181124-153954.png
    Screenshot_20181124-153954.png
    82.2 KB · Views: 185
thank you so much for all your help I would have bricked it
back to stock and everything is good can't believe the security patch level is like may 1st after I did ota update thought it was like October
 
Last edited:
Some Guy Here said:
thank you so much for all your help I would have bricked it
back to stock and everything is good can't believe the security patch level is like may 1st after I did ota update thought it was like October
Click to expand...

Yeah, I hear that. Motorola has actually been keeping these things updated in light of all the security concerns recently I guess. I don't know why your having the trouble you are but I'd like to figure it out. I thought that newer twrp should work but I think I may now why. I'll look into it when I can
 
I think when I ran a ota update when I installed my stock OS in twrp it altered the partitions and twrp didn't know where to boot from, so now that the bootloader is still unlock it should be easy to go back to linageOS if I want, or I should find other things to do then #$% up my phone lol!
 
Some Guy Here said:
I think when I ran a ota update when I installed my stock OS in twrp it altered the partitions and twrp didn't know where to boot from, so now that the bootloader is still unlock it should be easy to go back to linageOS if I want, or I should find other things to do then #$% up my phone lol!
Click to expand...

May be what happened. It's not possible at all to flash an ota with twrp unless the ota has been modified for it. LineageOS is working just fine if it's built with @bcrichster, @jasonmerc or my trees newer ones anyway, and security patches are up to date so it shouldn't #$% up your phone if done right.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom