Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
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 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.