New (to me) TMo OP7Pro and my plans - will this work? - OnePlus 7 Pro Questions & Answers

I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?

Jaxidian said:
I just bought one of those in-store display models off of eBay for ~$270 to play around with while I'm waiting for my next phone. First of all, those phones have incredibly severe screen burn-in - I don't recommend them.
The unit I bought was a T-Mobile model that is sim-unlocked (I'm also on T-Mobile, so I can eventually legitimately unlock it myself, if necessary, as I'll be running it on a spare line).
My high-level goals are:
1. Flash to Int'l
2. Flash & run xXx NoLimits
3. Flash & run Open Beta
4. Call Screening is a must! (I understand xXx NoLimits has it built-in but this is my Plan B for enabling it: Google Call Screening)
This is my more scripted-out plan for accomplishing these things:
0. Check out the device in general, make sure it works, and do a factory reset.
1. Install Drivers (Plug phone in -> install from Windows Explorer USB file share thingie)
2. Use MSM to flash stock TMo firmware
3. Fully update it via System -> Check for Updates
4. Use MSM to flash to int'l
5. Factory reset & fully update via System -> Check for Updates
6. Flash the latest Open Beta
7. Unlock bootloader, Flash TWRP, and install Magisk. (alternate guide)
8. Flash & run xXx NoLimits
9. Flash & run Open Beta
My general questions:
1. Is this a solid plan?
2. Am I missing anything important here?
3. Will these things work together?
4. What "gotchas" might I run into? Netflix support? Play Store support? Functional Call Screening? Anything else?
Click to expand...
Click to collapse
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom

jamescable said:
After reading all of that, just give up because you have no idea what you're doing. Why flash a ROM if you are flashing open beta? Open beta is the beta version of stock ROM(OOS) so it will overwrite xxx rom
Click to expand...
Click to collapse
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.

Jaxidian said:
My bad, I thought I posted in a Q&A forum where questions were encouraged. I also thought the Open Beta was an OTA update on top of stock OOS and that xxx claimed things like "Still working after OOS version upgrade" and "Support OOS Stock Rom OTA's" and "When a new OOS OTA is available, just run the OOS update, flash Magisk again and xXx NoLimits is still in place and working like before".
Not sure what your problem is but go piss in somebody else's punch bowl.
Click to expand...
Click to collapse
I am running open beta on a stock TMobile 7pro. Works great. You don't need to do all the updates. Just flash the open beta after you switch to international.

Hey if u do the call screening magisk way. Be sure to use the Google dailer 39. Apkmirror and make sure the updates is turned off for it.

Alright, so I was in the same boat as you, I bought a T-Mobile 7 Pro model earlier in the week; and nicely asked T-Mobile support through the App a few times to help me SIM-Unlock it so I could do my bootloader unlock and linked the Oneplus Support website and the Unlock page.
I ran into many issues so I'll help you out as I just finished my 6 day journey of making it functional.... Along the way, I lost cell service, I lost all my sensors.... So I'd recommend taking a TWRP backup everytime you're able to successfully boot into the device; Note: my goal was Havoc, so I ended up in a different place than where you're trying to go. I don't know what exact problems you'll run into, but I'm letting you know what I think makes sense from my previous experience over the week.
Your scripted-out plan:
0. Sure, test it, but you'll end up automatically wiping it later when you unlock the bootloader.
1. Sure, install the drivers.
2. You probably don't need to flash stock T-Mobile firmware as it's already running it.
3. You probably don't need to update it.
4. Yes, Flash it to international.
5. You probably don't need to update it. However I'd recommend to unlock the bootloader here;
5a. (The Damned T-Mobile model makes flashing TWRP a bit difficult) I'd recommend taking a note on what Slot is currently active (A or B).
Use "fastboot getvar current-slot" to find out; Then I'd recommend switching to the other slot ( If you're on Slot A, switch to Slot B, vice versa) to flash TWRP first (this overrides your boot image on your active slot, but is the only way to boot TWRP on the T-Mobile variant) and then flash the TWRP installer (this will flash TWRP to both Slots).
5b. After using the TWRP installer from your 2nd Slot, Use TWRP to swap back to the 1st Slot. Now make a complete full TWRP backup with all the boxes checked. Then, copy that backup to your computer so that it won't get wiped in the next few steps. (Do not skip this. If you did this correctly, You will have a place to come back to just in case you **** up your sensors, and cell service like I did.).
5c. Doublecheck if you can actually boot to your original Slot and if everything's functioning. Check if you can boot to your other Slot and see if everything's functioning. (This is where you super-need to make sure you have a safe place to come back to).
6. Sure, you can try flashing the latest Open Beta, but you might have to install TWRP again back in step 5b.
7. You might or might not have to unlock the bootloader, depending on what method you use to flash the Open Beta, your bootloader status might save; Sure, flash Magisk using TWRP.
8. Sure, flash xXx NoLimits using Magisk Manager.
9. Why undo your work and flash the Open Beta again? Don't do this.
With that you should be done.
If at any point you had an issue, I'd recommend using the TWRP backup you created earlier in 5b.
If you super-super have an issue, you'll have to use MSM to go back to stock International firmware.
In my case.... I had super-super issues and I had no TWRP backups.... and I had to use MSM to go back all the way back to T-Mobile stock firmware and start over because I had no service, and no sensors (proximity, gyroscope, accelorometer, etc).
But in the end, I think I have everything functioning the way I want to on HavocOS.

It's been a minute but I now have an update to my journey.
I had to take a quick pause at step 4 of my plan. The phone was SIM-unlocked but the bootloader itself was locked. So I had to do the dance with OnePlus and wait a couple weeks for that unlock code. Well, I finally got that puppy, so was able to start this project this weekend. Here's what I've done and where I'm at so far:
0. Device checked out well. Works great, aside from the screen burn-in issues (which is why I got it so dang cheap).
1. Drivers installed. ADB & Fastboot work great.
2. I used MSM to flash back to TMo firmware after my previous failings when I hit the locked bootloader wall. It worked great to get me to the point where I could generate the phone unlock code request to send to OP.
3. Not needed, although I did this while waiting 2 weeks for OP to send me a code.
4. Done. Worked perfectly. Hello, TMo-less firmware. Also, hello SIM #2 (the 2-week delay gave me time to buy a dual-sim tray).
5. Factory reset as part of the flashing and unlocking. Not bothering with system updates yet.
6. Not yet done this.
7. Bootloader is now unlocked. Magisk is installed but TWRP is not yet installed. This is where I'm at now.
Not hitting any problems. Just ran into dinnertime and my kiddo's bedtime. Thought I'd post this update before I started back up. So far, so good, other than that surprise 2-week delay waiting for an email.

Related

How 2handle HTC s/wupdate install & twrp

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

Consideration and Steps to root

Hi Everyone,
Honor View 10 is going to be launched soon in my country (this end of month). I have considered it as my next phone upgrade. Before, I have looked upon N*k** 8, but that subforum is dead already (no UBL, no root, nothing to see). I am currently waiting for X***mi RN5P which still have no news about the official launch here (probably another 3 months). But they decided to do some twist, by disabling the UBL ability for the phones they launched officially here. Kinda ironic.
To make sure I can live with the phone as it, I have to confirm several things first :
1. Does the phone has native VoLTE that works out of box without installing any additional app? I read from several thread here, it has support Dual VoLTE, but still doubt. I have checked some other phone who said they support VoLTE but in reality doesn't work. My main carrier used to be CDMA carrier, which has completely moved to 4G (only). So we can only call/sms thru VoLTE. If someone can post the screenshot of the VoLTE call setting, or "Enhanced HD" setting or similar, it will be a great confirmation. (I don't need the video call, only voice call/sms).
2. I am using Automagic (tasker alternative). I am quite active in that forum for several months. From there, I read a lot of incompatibility or something won't work, mostly from Huawei Devices. It seem the aggressive battery saving from the ROM has been disrupting Automagic from running properly. Is there anyone here who use Automagic/Tasker or similar automation app and found problem specific for Huawei devices, specificly for this View 10? (using stock ROM). I mean something like wifi scanning or location which work in Phone A or Phone B using the same android oreo 8.0; but doesn't work in View 10. If only minor problem, I can accept it.
3. Is there anyone having problem with the UBL process? X***mi just pull it tricks by kinda banning all user from my country to unlock the Bootloader. (error 86023:hardwareID) I am afraid of the same, as I need root. But I don't need to change the ROM.
Best case
If all the problems are solved and I have bought the device; I am going to root and install TWRP as usual. But I will stay on Stock ROM, most custom ROM still have problem with VoLTE. I might use LineAge or AOSP-ish ROM if there is any and has solved most bug. This is the step that I am going to do after I bought the phone.
1. Unlock the bootloader. https://forum.xda-developers.com/honor-view-10/how-to/honor-view-10-bootloader-unlock-t3749426 Result : Bootloader Unlocked
2. Install Magisk (latest is 16.2) via fastboot https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280 Result : Root achieved, Magisk Installed
3. Then proceed on to backup the original recovery https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3 Result : Original recovery backed up. I am thinking to do additional backup by using partition backups, but don't know if it works.
4. Flash Official TWRP https://forum.xda-developers.com/ho...recovery-twrp-3-2-1-0-touch-recovery-t3752397 Result : recovery changed to TWRP.
5. Backup all available partition. Result : all partition backed up, except /data. Since FBE still won't work
After the ritual, the phone will be rooted, Magisk installed, TWRP, and have full backup of all backup-able partition from TWRP and the original recovery. Xposed still won't work, so need to find alternative in Xposed. I mostly use Gravity box and App Settings Modules. Maybe there are alternatives available in Magisk. (haven't research much about it). To backup app's data, the only choice is Titanium Backup then, since /data partition can't be backed up in TWRP. We don't have stock firmware yet available, so need to be careful with the modification.
Do I miss something in my steps above?
Thanks for the answer in advance. And sorry for the long post.
Regards,
Desmanto

How to properly flash tulip with twrp and ota on stock?

Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703
Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.
Have you tried wiping system and installing?
Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.
well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.
It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.

Gyroscope and Proximity Sensor not working

Hi Team,
On the latest OOS 10.3.2. Have done multiple resets, downgraded using msm tool to OOS 5.1.3 and then manually updating them. Factory reset done a couple of times.
Anyone can help?
Currently running Magisk 20.4, bootloader unlocked.
Same here
I even tried using msmtool and even installing custom rom still no luck in fixing this issue . Most irritating part about this is not able to use auto rotate .
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
oldmanz said:
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
your the best man i can finally use other ROMs again
my fix was to use oneplus 7 port on my 6 but it was annyoing me
oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thank you kind person. For more than two months I tried to return the phone to normal operation and all to no avail. So I came across your post and now my phone is full again. Thank you very much.
oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thanks a lot man !!!!
Following your steps, the automatic brightness and also the automatic screen rotation works for me again.
Thank you @oldmanz

New OnePlus 7Pro Owner Questions

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!!

Categories

Resources