I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
I just checked my Magisk 13.3-rooted Sprint htc u11, running 1.13.651.6 for htc s/w updates & d/l'ed the update abt 750Mb, which is said contained a security update & it was supposed to bring me to 1.28.651.3.
After d/l & clicking on install, it went thru 20% on the "gas gauge" progress bar, before the screen went black & 5 second
screen came up as usual & then the twrp main screen came up.
Not knowing what to do, I decided playing it safe was best, I simply rebooted the system & all went fine. I got a msg telling me that I have a system update & I chose to put installation off & chose to be reminded in 4hrs. In 4hrs, the fone will be off. I'm going to be AFK fm the fone - as I have to be away & the fone has to be of until Sat. nite when I'm done w/the other stuff I'm doing until then.
I'm not sure what to do, or why it rebooted, showed the 5 second screen & then went into the twrp main screen. I did nothing to make that happen. In the past I obviously unlocked the BL, installed twrp, & rooted w/Magisk 13.3 & Magisk Mgr. 5.11- carefully following posted instructions, but I have no idea why reboot went fm 5 second screen to main twrp screen & equally no idea if that should have happened- or what in hindsight I should have done.
***BTW, I have an icon in my notification bar fm the Updater program that is telling me I have a System Update Ready & I should tap on the notice to install.***
PLEASE ADVISE!
Is there any problem taking the 1.13.651.6 -> 1.28.651.3 update w/unlocked BootLoader & twrp & root that will damage my fone, the setup, or Bootloader, twrp, or root?
What should I do when I power-on & restart fone on Sat. nite when I will ostensibly get the update process kicking in after the 5 Second screen & then progressing to 20% of the update & then the Update process reboots & reboots me back to 5 second screen & then the twrp main screen (or maybe another prompt)? Or can I do something to prevent / remove the update if there are any problems.
Would going into a diff mode fm 5 second screen, like bootloader, download, or recovery mode & then have to do something else to get the System Update to work?, or do I have to do something else - related to unrooting, &/or removing twrp, &/or re-locking the bootloader ? - (please don't let it be any of that!), & how would I do whatever I have to do?. Or do I have to somehow avoid the update - don't know how to do that either- I've played w/this kind of stuff on a # of prev devices, but not on an htc device & I'm sorta like a newbie w/htc 'under the hood' stuff. ***Thanks very much in advance***. This is the only Sprint device I have… so I can't just switch to another fone & do whatever I have to do on this fone w/out any stress & plenty of time to sort out the details.
Again, TIA, oldwolf
oldwolf613 said:
I just checked my Magisk 13.3-rooted Sprint htc u11, running 1.13.651.6 for htc s/w updates & d/l'ed the update abt 750Mb, which is said contained a security update & it was supposed to bring me to 1.28.651.3.
After d/l & clicking on install, it went thru 20% on the "gas gauge" progress bar, before the screen went black & 5 second
screen came up as usual & then the twrp main screen came up.
Not knowing what to do, I decided playing it safe was best, I simply rebooted the system & all went fine. I got a msg telling me that I have a system update & I chose to put installation off & chose to be reminded in 4hrs. In 4hrs, the fone will be off. I'm going to be AFK fm the fone - as I have to be away & the fone has to be of until Sat. nite when I'm done w/the other stuff I'm doing until then.
I'm not sure what to do, or why it rebooted, showed the 5 second screen & then went into the twrp main screen. I did nothing to make that happen. In the past I obviously unlocked the BL, installed twrp, & rooted w/Magisk 13.3 & Magisk Mgr. 5.11- carefully following posted instructions, but I have no idea why reboot went fm 5 second screen to main twrp screen & equally no idea if that should have happened- or what in hindsight I should have done.
***BTW, I have an icon in my notification bar fm the Updater program that is telling me I have a System Update Ready & I should tap on the notice to install.***
PLEASE ADVISE!
Is there any problem taking the 1.13.651.6 -> 1.28.651.3 update w/unlocked BootLoader & twrp & root that will damage my fone, the setup, or Bootloader, twrp, or root?
What should I do when I power-on & restart fone on Sat. nite when I will ostensibly get the update process kicking in after the 5 Second screen & then progressing to 20% of the update & then the Update process reboots & reboots me back to 5 second screen & then the twrp main screen (or maybe another prompt)? Or can I do something to prevent / remove the update if there are any problems.
Would going into a diff mode fm 5 second screen, like bootloader, download, or recovery mode & then have to do something else to get the System Update to work?, or do I have to do something else - related to unrooting, &/or removing twrp, &/or re-locking the bootloader - (please don't let it be any of that!), & how would I do whatever I have to do?. Or do I have to somehow avoid the update - don't know how to do that either- I've played w/this kind of stuff on a # of prev devices, but not on an htc device & I'm sorta like a newbie w/htc 'under the hood' stuff. ***Thanks very much in advance***. This is the only Sprint device I have… so I can't just switch to another fone & do whatever I have to do on this fone w/out any stress & plenty of time to sort out the details.
Again, TIA, oldwolf
Click to expand...
Click to collapse
You cannot update the phone while rooted. You need to be on an Untouched System image. There is quite a few threads explaining this. Did you do a twrp System image and boot.img backup? If not, there are a few different ways to update. You can flash(a few different ways to flash the signed firmware update in BadBoys ROM/Firmware thread. RUU(wipes everything) and then take the OTA. Flash the OTA in TWRP, however you will still have to manually flash firmware.zip inside the OTA. You could have saved yourself the trouble of writing this page long explanation and read through a few threads, lol.
Since you are on Sprint, there is BadBoyz ROM/Firmware thread HERE. 5m4r7ph0n36uru's firmware HERE
Schmeggy929, thanks so much!
If I knew why I got that result I would've searched threads for an answer. I turned on my U11 tonite & told it to cancel update. It told me install would be removed. Whew! Was afraid I keep getting prompted to do update, or worse, I'd not be given the chance to remove!
So far, I've only unlocked BL (htc provided step by step), rooted, & installed twrp (courtesy of Capt Throwback's guide) so that's the extent of my htc dev experience / knowledge.
You mentioned flashing OTA in twrp. Did a quick search & scanned thru replies, got basic idea; but need to ask, will that wipe my 3d party apps & data & settings? I'm guessing not... also, in which mode would I flash? Recovery, Download, Bootloader? Also, you asked if I did a twrp system image & boot.img backup & if not you listed those approaches. What should I do if Ihad done twrp backup? Usually I b/u everÿhing but the cache & will be doing that soon, along w/my homework i.e. looking up threads…
I'll do w/out the update until I'm better prepared.
I've been considering going to BadBoyz ROM, but would be curious to see what main screens look like & I see you are a recognized themer & on Team BadBoyz; would itbe possible to please send me some screen captures of the rom via PM; looked in ROM thread but didn't find any…
TIA, Oldwolf
oldwolf613 said:
Schmeggy929, thanks so much!
If I knew why I got that result I would've searched threads for an answer. I turned on my U11 tonite & told it to cancel update. It told me install would be removed. Whew! Was afraid I keep getting prompted to do update, or worse, I'd not be given the chance to remove!
So far, I've only unlocked BL (htc provided step by step), rooted, & installed twrp (courtesy of Capt Throwback's guide) so that's the extent of my htc dev experience / knowledge.
You mentioned flashing OTA in twrp. Did a quick search & scanned thru replies, got basic idea; but need to ask, will that wipe my 3d party apps & data & settings? I'm guessing not... also, in which mode would I flash? Recovery, Download, Bootloader? Also, you asked if I did a twrp system image & boot.img backup & if not you listed those approaches. What should I do if Ihad done twrp backup? Usually I b/u everÿhing but the cache & will be doing that soon, along w/my homework i.e. looking up threads…
I'll do w/out the update until I'm better prepared.
I've been considering going to BadBoyz ROM, but would be curious to see what main screens look like & I see you are a recognized themer & on Team BadBoyz; would itbe possible to please send me some screen captures of the rom via PM; looked in ROM thread but didn't find any…
TIA, Oldwolf
Click to expand...
Click to collapse
Taking OTA, whether normal or flashing will not wipe apps. From what I gather you can (if you are stock and untouched System Image) can download OTA, Extract Firmware.zip , then back to OTA install, let it install(will reboot to TWRP and install) then reboot to Download Mode and fastboot flash Firmware zip.
If you did make a System, Recovery and Boot Image backup(even better) Boot to TWRP and restore those backups, reboot and take the OTA normal(as you would with a completely stock phone).
Or easier, download the updated signed firmware from BadBoyz Thread HERE. Flash with either scard method or computer fastboot method. Then download The latest ROM for 1.28.651.3.
None of these will wipe you apps and Data. Badboyz ROM is nothing more than a Stock ROM with great Tweaks. Other than my Boot animation , the two BadBoyz apps and some bloatware missing, you would never know the difference, except for performance and extra goodies.
this is the easiest way I've found to install a ota...preparation
-from 100% stock, unlock bootloader, flash twrp
-on 1st twrp boot, keep ready only & immediately do a system & boot img backup
-once backup is done, copy stock recovery into the twrp/backup stock imgs folder & rename it recovery.emmc.win
-flash rom, magisk, supersu, whatever changes u want
-when a ota is available, boot to twrp, & restore your system/boot/recovery imgs backup
-boot to OS, download & install ota
repeat steps from top
@ Schmeggy929 is this the latest updated signed firmware ? : ->
2PZCIMG_1.28.651.3_RUU.zip ? & is the scard method renaming that file on root of sd card to 2PZCIMG.ZIP & flashing it fm twrp in download mode? If so the next step, as you said, would be to d/l the ROM - would that be
{ Bad_Boyz_Sprint_HTC_U11_v2.0.zip } ? & then just flash that fm download mode in twrp?
@ OMJ, After unlocking BL, & flashing twrp, & rooting (or does it have to be unlock & then root & then flash twrp,I forget) I had some 3d party apps & I made a nand backup of everything but cache fm twrp, to have a clean, stock, relatively new setup. I noted in Solid Explorer that under twrp/backups/sdcard_hexname/twrp_bu_name directory, there is a recovery.emmc.win file - is that the 'stock recovery' you were referring to? & wouldn't I just restore that whole backup to take an ota? - after unrooting of course! Also, aren't there stock image files to either recover from or take OTA? Have I missed anything? TIA…
Thanks much to all, Oldwolf
oldwolf613 said:
@ Schmeggy929 is this the latest updated signed firmware ? : ->
2PZCIMG_1.28.651.3_RUU.zip ? & is the scard method renaming that file on root of sd card to 2PZCIMG.ZIP & flashing it fm twrp in download mode? If so the next step, as you said, would be to d/l the ROM - would that be
{ Bad_Boyz_Sprint_HTC_U11_v2.0.zip } ? & then just flash that fm download mode in twrp?
@ OMJ, After unlocking BL, & flashing twrp, & rooting (or does it have to be unlock & then root & then flash twrp,I forget) I had some 3d party apps & I made a nand backup of everything but cache fm twrp, to have a clean, stock, relatively new setup. I noted in Solid Explorer that under twrp/backups/sdcard_hexname/twrp_bu_name directory, there is a recovery.emmc.win file - is that the 'stock recovery' you were referring to? & wouldn't I just restore that whole backup to take an ota? - after unrooting of course! Also, aren't there stock image files to either recover from or take OTA? Have I missed anything? TIA…
Thanks much to all, Oldwolf
Click to expand...
Click to collapse
2PZCIMG_1.28.651.3_RUU.zip is a full RUU which will wipe your phone (except ext sd card) & restore factory imgs
this is the latest signed firmware, you can rename to 2PZCIMG.ZIP, copy to ext sd card & boot into download mode to flash...firmware is not flashed from twrp... 2PZCIMG_Sprint_1.28.651.3_signed_firmware.zip
signed firmware will overwrite twrp, so you'll need to reflash twrp after the signed firmware. my latest ROM is Bad_Boyz_Sprint_HTC_U11_v2.0.zip (based on 1.28.651.3), it's always flashed from twrp
unlocking bootloader is a 1 time thing, you've already unlocked so no need to worry about it. when u backup in twrp, you would need to make sure you chose the system img option to be able to restore for an ota, and you would only need to backup system & boot, if u chose recovery, it's not backing up stock recovery, it's backing up twrp.
if you flash my rom, there's really no need to worry about all this, I typically have a updated ROM ready for everyone the same day or within 24-48hrs of a ota. in this case, you would just need to flash the updated firmware, then flash my new/updated ROM.
for now, I would just flash the latest signed firmware, then flash twrp, boot to twrp & flash my ROM....no need to flash root prior to the ROM. if you do want to restore stock system/boot/recovery imgs for the next ota, I'll upload my backup...
OMJ, I was going to leave my fone on pure stock, but since BB is mostly stock, & there are improvements & less bloat & you quickly update for new OTA's & put up prev stock img's in case OTA is needed, & you have been *so* responsive, I'm going to go w/your rom.
I have some stuff I want to research myself & then I'll go to BB.
I do have some Q's that I'd like to ask you now: You said that flashing the latest FW would kill twrp, if I put the Official TWRP App on my U11, can I use that to reflash twrp?, it has a "Flash TWRP" button, but I don't know if that process will work in this situation.
Also, will flashing the FW & thereby killing twrp do anything to "under the hood" stuff like pointers/links to NAND backups I already did since I added twrp? I have original setup + some critically needed apps I loaded until the 10day return period ended in 1 NAND (didn't want to unlock BL & root until I was sure I had no h/w probs, like some had w/audio adapter) a 'base NAND backup' & I keep one other, 'latest' backup of everything except Cache to ensure I have a NAND image to restore in case of emergency.
I'd hate to lose access to those if flashing FW & killing twrp would also kill needed pointers/links to those backups.
Since you said flashing FW can't be done from twrp, pls confirm that going into Download mode is done by pressing Vol. Up, Power, & Home/fingerprint buttons. Is there any order & do I have to release any button at any point to get where I have to be?
One last Q: I looked on pg for your rom, & need clarification - which mode do I have to choose in twrp to install your rom?
TIA, oldwolf
p.s. once installed, I will add BB to my forum sig!
oldwolf613 said:
OMJ, I was going to leave my fone on pure stock, but since BB is mostly stock, & there are improvements & less bloat & you quickly update for new OTA's & put up prev stock img's in case OTA is needed, & you have been *so* responsive, I'm going to go w/your rom.
I have some stuff I want to research myself & then I'll go to BB.
I do have some Q's that I'd like to ask you now: You said that flashing the latest FW would kill twrp, if I put the Official TWRP App on my U11, can I use that to reflash twrp?, it has a "Flash TWRP" button, but I don't know if that process will work in this situation.
Also, will flashing the FW & thereby killing twrp do anything to "under the hood" stuff like pointers/links to NAND backups I already did since I added twrp? I have original setup + some critically needed apps I loaded until the 10day return period ended in 1 NAND (didn't want to unlock BL & root until I was sure I had no h/w probs, like some had w/audio adapter) a 'base NAND backup' & I keep one other, 'latest' backup of everything except Cache to ensure I have a NAND image to restore in case of emergency.
I'd hate to lose access to those if flashing FW & killing twrp would also kill needed pointers/links to those backups.
Since you said flashing FW can't be done from twrp, pls confirm that going into Download mode is done by pressing Vol. Up, Power, & Home/fingerprint buttons. Is there any order & do I have to release any button at any point to get where I have to be?
One last Q: I looked on pg for your rom, & need clarification - which mode do I have to choose in twrp to install your rom?
TIA, oldwolf
p.s. once installed, I will add BB to my forum sig!
Click to expand...
Click to collapse
good decision
good question about the twrp app, honestly I've never used it, I'm old school so I always manually flash via fastboot...I'll have to give it a try so I know.
new firmware usually does has fixes & improvements but HTC is not the greatest at sharing what has been improved...I always store my backups to ext sd, but no, updated firmware will not affect your backups.
yes you would flash twrp via download mode....when phone is powered off, hold power + volume down, once you feel the vibration or screen come on, let go of both....once on my ROM, I have a option on the reboot menu to reboot to download mode.
when flashing the ROM, from twrp main menu, choose install, then find the rom zip
oldwolf613 said:
OMJ, I was going to leave my fone on pure stock, but since BB is mostly stock, & there are improvements & less bloat & you quickly update for new OTA's & put up prev stock img's in case OTA is needed, & you have been *so* responsive, I'm going to go w/your rom.
I have some stuff I want to research myself & then I'll go to BB.
I do have some Q's that I'd like to ask you now: You said that flashing the latest FW would kill twrp, if I put the Official TWRP App on my U11, can I use that to reflash twrp?, it has a "Flash TWRP" button, but I don't know if that process will work in this situation.
Also, will flashing the FW & thereby killing twrp do anything to "under the hood" stuff like pointers/links to NAND backups I already did since I added twrp? I have original setup + some critically needed apps I loaded until the 10day return period ended in 1 NAND (didn't want to unlock BL & root until I was sure I had no h/w probs, like some had w/audio adapter) a 'base NAND backup' & I keep one other, 'latest' backup of everything except Cache to ensure I have a NAND image to restore in case of emergency.
I'd hate to lose access to those if flashing FW & killing twrp would also kill needed pointers/links to those backups.
Since you said flashing FW can't be done from twrp, pls confirm that going into Download mode is done by pressing Vol. Up, Power, & Home/fingerprint buttons. Is there any order & do I have to release any button at any point to get where I have to be?
One last Q: I looked on pg for your rom, & need clarification - which mode do I have to choose in twrp to install your rom?
TIA, oldwolf
p.s. once installed, I will add BB to my forum sig!
Click to expand...
Click to collapse
The twrp app worked like a charm...
Sent from my HTC U11 using XDA Labs
OMJ, Great news abt the TWRP app, thanks for trying it out & sharing. Will let you know how well everything went.
OMJ, can't try your ROM yet. Flashing the FW zip you showed above finished, but didn't bring fone to 1.28… 1st time twrp & Magisk root were killed; but wasn't upgraded to 1.28... that was w/buttons->Download. Tried again on Win10 laptop w/'adb reboot downdoad', but didn't try to re-root. Same result, no 1.28… Then I reflashed twrp successfully, & I tried again (adb) - no joy. Odd thing, the Download screen showed two iterations of 2PZCIMG.ZIP in yellow (color was expected) @ the bottom of the screen, even tho my SDcard root had only 1 copy of the file & the processing of the zip took place in two stages, scrn went dark between 1st & 2nd- but I got the expected msg at the end. BTW, I tried OTA, between 2d & 3d flash failure, it got thru to the reboot, & I missed something on the screen & that too failed.
Back to flashing: iCould it be I missed something abt what is supposed to happen after you get the msg to press power btn? Would you please elaborate on that? Everything else seems to be working fine & I have nand bu of relatively new, pre- rooting & another bu w/a much more recent image. Just had probs w/restoring nands, got msg abt SD card; but I'm sure it'll all get worked out.
TIA, oldwolf
oldwolf613 said:
OMJ, can't try your ROM yet. Flashing the FW zip you showed above finished, but didn't bring fone to 1.28… 1st time twrp & Magisk root were killed; but wasn't upgraded to 1.28... that was w/buttons->Download. Tried again on Win10 laptop w/'adb reboot downdoad', but didn't try to re-root. Same result, no 1.28… Then I reflashed twrp successfully, & I tried again (adb) - no joy. Odd thing, the Download screen showed two iterations of 2PZCIMG.ZIP in yellow (color was expected) @ the bottom of the screen, even tho my SDcard root had only 1 copy of the file & the processing of the zip took place in two stages, scrn went dark between 1st & 2nd- but I got the expected msg at the end. BTW, I tried OTA, between 2d & 3d flash failure, it got thru to the reboot, & I missed something on the screen & that too failed.
Back to flashing: iCould it be I missed something abt what is supposed to happen after you get the msg to press power btn? Would you please elaborate on that? Everything else seems to be working fine & I have nand bu of relatively new, pre- rooting & another bu w/a much more recent image. Just had probs w/restoring nands, got msg abt SD card; but I'm sure it'll all get worked out.
TIA, oldwolf
Click to expand...
Click to collapse
time for another lesson....flashing firmware only does not update the OS....when you update via official ota, both firmware & OS are updated...but if you only flash updated firmware, you need to flash a updated ROM to match
OMJ, ohhh thanks! Was losing root upon flashing FW to be expected like losing TWRP Recovery? BTW, maybe such comments abt flashing a matching updated ROM w/the updated FW should be included w/the FW update install text, so I wouldn't have to bother you w/these issues.
Also, short of trying to flash a matching updated ROM (which I presume will then show the new version numbers) how do you know if flashing the FW was successful?
What if there is a problem w/the FW installation, what happens when you a flash matching updated ROM?
Also, when you said "if you only flash an updated FW, you need to flash an updated ROM to match“
I'm guessing that since my fone is working, the need to flash an updated rom to match is to have the new version #, i.e. 1.28… , show up in Settings->About 7.1.1
… also, in the Settings-> System update section- what is UICC lock? Thanks for all your help.
oldwolf
oldwolf613 said:
OMJ, ohhh thanks! Was losing root upon flashing FW to be expected like losing TWRP Recovery? BTW, maybe such comments abt flashing a matching updated ROM w/the updated FW should be included w/the FW update install text, so I wouldn't have to bother you w/these issues.
Also, short of trying to flash a matching updated ROM (which I presume will then show the new version numbers) how do you know if flashing the FW was successful?
What if there is a problem w/the FW installation, what happens when you a flash matching updated ROM?
Also, when you said "if you only flash an updated FW, you need to flash an updated ROM to match“
I'm guessing that since my fone is working, the need to flash an updated rom to match is to have the new version #, i.e. 1.28… , show up in Settings->About 7.1.1
… also, in the Settings-> System update section- what is UICC lock? Thanks for all your help.
oldwolf
Click to expand...
Click to collapse
Again root has nothing to do with firmware as Root is software. Like OMJ said flashing the firmware will replace Recovery.img for S-on users. Like you did easy fix is reflash TWRP whether fastboot, sdcard or the Official TWRP app. While flashing Firmware with any method, on the screen will show progress and failed or successful install. That's how you know if it installed correctly. Even though your phone might be working with new firmware and old software, the new software will contain patches, fixes, features and security updates. The reason to update the firmware along with software is to have them work together perfectly.
UICC lock is for Sprint sim card. Basically unlocking it for another carrier, but it is not that simple I believe.
Also you being somewhat new, asking these questions is the best thing you can do. You will see many people brick(phone useless, will not turn on or keeps bootlooping) simply because they didn't ask questions until it was too late. Keeping as much as you and you will start understanding.
OTA= Firmware and software update
signed firmware= for S-on users, usually all the firmware.zip removed from the OTA for those who can't take the OTA.
modified firmware= s-off users with usually with stock recovery removed(for convenience)
ROM= the software or operating System.
oldwolf613 said:
OMJ, ohhh thanks! Was losing root upon flashing FW to be expected like losing TWRP Recovery? BTW, maybe such comments abt flashing a matching updated ROM w/the updated FW should be included w/the FW update install text, so I wouldn't have to bother you w/these issues.
Also, short of trying to flash a matching updated ROM (which I presume will then show the new version numbers) how do you know if flashing the FW was successful?
What if there is a problem w/the FW installation, what happens when you a flash matching updated ROM?
Also, when you said "if you only flash an updated FW, you need to flash an updated ROM to match“
I'm guessing that since my fone is working, the need to flash an updated rom to match is to have the new version #, i.e. 1.28… , show up in Settings->About 7.1.1
… also, in the Settings-> System update section- what is UICC lock? Thanks for all your help.
oldwolf
Click to expand...
Click to collapse
just to add a little more that what schmeggy929 said...
when u flash magisk or supersu, the install process modifies the boot.img, when u flash firmware that writes a new boot.img, you wont have root until you flash magisk or supersu again
disclaimers...never been a fan, I do not add a disclaimer on my ROM thread, it means nothing...anyone that wants to root/hack/modify their phone has the responsibility to do their research prior to doing so...learning that you need to update firmware along w/ software is part of the research process
as schmeggy929 said, when flashing firmware, always pay attention to what it's doing & if there are any errors, some firmware need to be flashed 2x but it states so after the 1st flash...once firmware is flashed, you can verify the firmware level in download mode.
Thanks again to both Schmeggy & OMJ,
I am trying to do my diligence, help on these forums makes a big difference. My request for comments in the ROM install thread was not my own idea. I saw that on other ROM install threads in the past. It saved everyone time: the users get better educated & the Dev didn't get as many questions bc problems were avoided. Now w/help in this thread I will likely always remember that boot.img is affected by flashing root & firmware. Rest assured, just as I did when I was into Moto modifying - I got advice fm xda folks & then when I was familiar w/the ins & outs, I helped others. And....
I have another problem. Since having flashing the FW, & twrp replaced by the native recovery, I am not able flash TWRP again. I keep getting the following error msg:
C:\Users\a\Desktop\Minimal ADB and Fastboot>fastboot flash twrp.img
unknown partition 'twrp.img' error: cannot determine image filename for 'twrp.img'
After losing twrp due to flashing the FW, the tarp.img file didn't work - so I downloaded fresh copy of the 3.1.1.0 htc u11 twrp file & renamed it to twrp.img thinking it was just corrupt. No joy. I have it stored in the same directory as immediately above; from where I am running the adb stuff.
My workflow was as following: connected fone w/orig htc data cable, checked connection via running 'adb devices', then ran 'adb reboot download', which started properly. Ran 'fastboot devices' & got expected confirmation. Then I did 'fastboot flash twrp.img' the error msg above was the result.
Please advise. TIA, oldwolf
oldwolf613 said:
Thanks again to both Schmeggy & OMJ,
I am trying to do my diligence, help on these forums makes a big difference. My request for comments in the ROM install thread was not my own idea. I saw that on other ROM install threads in the past. It saved everyone time: the users get better educated & the Dev didn't get as many questions bc problems were avoided. Now w/help in this thread I will likely always remember that boot.img is affected by flashing root & firmware. Rest assured, just as I did when I was into Moto modifying - I got advice fm xda folks & then when I was familiar w/the ins & outs, I helped others. And....
I have another problem. Since having flashing the FW, & twrp replaced by the native recovery, I am not able flash TWRP again. I keep getting the following error msg:
C:\Users\a\Desktop\Minimal ADB and Fastboot>fastboot flash twrp.img
unknown partition 'twrp.img' error: cannot determine image filename for 'twrp.img'
After losing twrp due to flashing the FW, the tarp.img file didn't work - so I downloaded fresh copy of the 3.1.1.0 htc u11 twrp file & renamed it to twrp.img thinking it was just corrupt. No joy. I have it stored in the same directory as immediately above; from where I am running the adb stuff.
My workflow was as following: connected fone w/orig htc data cable, checked connection via running 'adb devices', then ran 'adb reboot download', which started properly. Ran 'fastboot devices' & got expected confirmation. Then I did 'fastboot flash twrp.img' the error msg above was the result.
Please advise. TIA, oldwolf
Click to expand...
Click to collapse
I've been here at XDA for over 10yrs, one thing I've learn, most most don't read the OP, they just jump in with questions....I constantly have to repeat myself, so why waste my time in the OP....I just wait for the questions now
here is the correct cmd...
fastboot flash recovery twrp.img
..
OMJ, well, I'm not close to being a dev, so I won't comment further abt what to put into OP, based on your reply; I'd just wish there was a book w/all this stuff, or maybe I'll get pointed somewhere. I can give user viewpoint, & but I'm not a typical user. I used to teach in Novell's official edu-channel as a Certfd Netware Instructor, so I try to remember the 'good workflow habits' I preached in the Service & Support class.
But thanks for your help, the corrected command did it, but when notified of success & told to hit power to continue, nothing happened, so I used download mode to go into bootload mode & then rebooted system (saw on Root Junky's U tube vid) & now I have TWRP! THANKS SO MUCH!!!
Apparently, my copy of the BB2.0 has bad signature or something- so I'll have to re-D/L it & flash again.
Once I've taken care of that & 'kicked the tires' I'll get back to you & let you know how much I like it.
Thanks again, oldwolf
OMJ I got it working- but had to turn off zip signature verification. In fact, this is the case of all zip installs. I suspect that it is related to the fact that on install flash the scrn says data was decrypted w/the default password, & the verification signature failed (md5). This is even the case when I used the rom's tweaks to flip the order of the sdcard's name.
The vid that Root Junky made for the flashing twrp for the htc 10 showed to cancel using a password & to leave the (data or card) unencrypted. I never got that screen.
I was following the instructions on the u11 twrp thread- Start: as you corrected my syntax- fastboot flash recovery twrp.img & Finish: fastboot reboot.
Even the modules fm the rom's tweaks failed in the same manner until I unchecked the box for verifying the zip.
I trust your code, (constantly updating right after htc sends slw updates is gonna keep your coding fresh) but who knows what'll be if I flash other packages?
BTW, the tweak to long-press the Recent Apps button & assign Menu is a real big boon. It allowed me to use my fave & unfortunately outdated & no-longer-developed app- Loot … no menu button cut it off at the knees. It was well planned out, & a feature set that was just right, & I couldn't find a good replacement. Now that I have a Menu button; I was able to pull Loot out of the cobwebs… thanks! All the best, oldwolf
I have purchased a OnePlus 7 Pro from a friend of mine. He has already changed it from the T-Mobile to the International version via MSM. The current build number is 9.5.3.GM21AA and model number GM1915. I have currently installed TWRP 3.3.1-0 and rooted with Magisk 20.4. As I am new to OnePlus, I am confused as to go about updating the stock firmware, if I will lose root, updating to a custom rom. I have done this with other phones, Nexus 6P, 5X, Pixel 1 and Essential PH-1, but this seems different as I have a build number that is not necessarily meant for the T-Mobile version of this phone. I have read multiple guides and instructions throughout this forum, but don't seem to find the answers for my specific phone. Any help and direction would be very helpful.
If the phone has been updated to the international version then that's a REALLY old version, the latest version for International (Global) is 10.3.5, have you checked for an update via the phone already?
Update settings are in Settings > System > System Updates
If you want to upgrade manually, you can do that via Settings > System > System Updates > (Top Right) > Local Upgrade (Make sure the zip is in the main storage folder though or it won't be listed)
However, If you want to upgrade and keep root then you need to upgrade TWRP first, the latest is 3.4.0-0 from here : https://twrp.me/oneplus/oneplus7pro.html
Flash that first.
I've uploaded both the most recent versions onto my Android File Host :
Oxygen OS - Android 10.3.5 - Global - OnePlus 7 Pro (GM21AA) : https://www.androidfilehost.com/?fid=8889791610682950702
Oxygen OS - Android 10.0.8 - EU - OnePlus 7 Pro (GM21BA) : https://www.androidfilehost.com/?fid=8889791610682950715
My Android 10 Folder : https://www.androidfilehost.com/?w=files&flid=296897
So....
Grab the international version (which is the full rom)
Download the latest TWRP and Magisk
Reboot to TWRP (3.4.0-0)
Flash the full rom build (do not reboot yet)
Flash TWRP 3.4.0-0 (before rebooting) then reboot back into recovery
Flash latest Magisk then clear cache (not data)
Reboot
Check the Magisk version with the app : https://github.com/topjohnwu/Magisk/releases
I would suggest choosing the beta release in the app as Magisk 21.0 is available and works fine (see attached)
If it shows that the phone is not rooted then just reboot back into TWRP and flash Magisk again and reboot.
-----------------
If you're going to install a custom rom then ensure you read the first posts in the thread first as the dev will usually advise pre-requisites (i.e. A specific stock rom version to have installed first, a specific version of TWRP to use, etc)
(Also, try to use paragraphs, makes your post a lot more legible)
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
njsges said:
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
Click to expand...
Click to collapse
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
djsubterrain said:
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
Click to expand...
Click to collapse
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
njsges said:
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
Click to expand...
Click to collapse
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
djsubterrain said:
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
Click to expand...
Click to collapse
Thank you. The phone has already been switched from T-Mobile to Global. I'm not sure if the OPS patcher was done yet. I will text my friend and ask him. I wonder if it is detrimental to do it again while I am still on 9.3.5?
UPDATE: My friend flashed the ops file with the MSM tool download
SUCCESS!! Thank you for all of your help!!