Hi Gurus,
While everybody is trying 2.2, I am still stuck on FJ6 (or incomplete JH7).
Here's the history:
1. Got the phone on day 1 of release.. loved it and still love it. No GPS issues - first lock took 20 secs and subsequent locks took 6 seconds at most.
2. Rooted and unlocked the phone, deleted all AT&T crapware. Running Launcher Pro, Tiatinum backup etc.
3. Installed Lagfix - was happy with a high quadrant score
4. Saw that the JH7 OTA is out
5. Read up on the forums here and unlagged lagfix.
6. Initiated the OTA update, went all the way thru, and got the message "update failed - No updated available" after restart. GPS is messed up.
7. Settings --> About Phone shows this
- Firmware version: 2.1-update1
- Baseband Version: I897UCJH7
- Kernel Version: 2.6.29 [email protected] #2
- Build Number: ECLAIR
8. Went to plan B - Kies Mini, was able to connect but stuck at "Unregistered screen".
9. Got frustrated and called Samsung.
- They said that the OTA upgrade worked "half way thru". They were expecting something after the "ECLAIR" in build number and I should not see the "PC Internet" as an option under USB Settings.
So Samsung said that they will have to reflash the phone to JH7 and have asked me to send the phone in.
1. I will be without a phone for 4-5 days which sucks.
2. They may (an will?) see my shenanigans (root etc) on the phone even after a hard reset ??
What are the implications? Is there any way around this? Can I do something (or follow some instruction by myself) to fix this? I am ok going back to stock AT&T firmware - to need to mess around with removing crapware etc. I would just like to keep the phone "unlocked" (I travel overseas quite a bit).
I have read thru most of the form postings.. which confused me more. At this point of time, I have a "brain freeze" and would appreciated a "just do this and then this" type of instruction.
Ironically, ever since switching from Windows Mobile to android, I have been a big proponent of this phone and operating system. Now I am beginning to see the downside of being on the leading/bleeding edge..
Please help..
Nick
You can always use ODIN and flash it that way...
http://forum.xda-developers.com/showpost.php?p=8567598&postcount=6
defriend said:
Hi Gurus,
While everybody is trying 2.2, I am still stuck on FJ6 (or incomplete JH7).
Here's the history:
1. Got the phone on day 1 of release.. loved it and still love it. No GPS issues - first lock took 20 secs and subsequent locks took 6 seconds at most.
2. Rooted and unlocked the phone, deleted all AT&T crapware. Running Launcher Pro, Tiatinum backup etc.
3. Installed Lagfix - was happy with a high quadrant score
4. Saw that the JH7 OTA is out
5. Read up on the forums here and unlagged lagfix.
6. Initiated the OTA update, went all the way thru, and got the message "update failed - No updated available" after restart. GPS is messed up.
7. Settings --> About Phone shows this
- Firmware version: 2.1-update1
- Baseband Version: I897UCJH7
- Kernel Version: 2.6.29 [email protected] #2
- Build Number: ECLAIR
8. Went to plan B - Kies Mini, was able to connect but stuck at "Unregistered screen".
9. Got frustrated and called Samsung.
- They said that the OTA upgrade worked "half way thru". They were expecting something after the "ECLAIR" in build number and I should not see the "PC Internet" as an option under USB Settings.
So Samsung said that they will have to reflash the phone to JH7 and have asked me to send the phone in.
1. I will be without a phone for 4-5 days which sucks.
2. They may (an will?) see my shenanigans (root etc) on the phone even after a hard reset ??
What are the implications? Is there any way around this? Can I do something (or follow some instruction by myself) to fix this? I am ok going back to stock AT&T firmware - to need to mess around with removing crapware etc. I would just like to keep the phone "unlocked" (I travel overseas quite a bit).
I have read thru most of the form postings.. which confused me more. At this point of time, I have a "brain freeze" and would appreciated a "just do this and then this" type of instruction.
Ironically, ever since switching from Windows Mobile to android, I have been a big proponent of this phone and operating system. Now I am beginning to see the downside of being on the leading/bleeding edge..
Please help..
Nick
Click to expand...
Click to collapse
You hacked your phone, now it won't update and you think it is because android is on the bleeding edge.
If you had reverted to stock first (odin one click) you may have had success. Maybe it would kill your unlock -some it does, some it doesn't.
Some phones had trouble updating even from stock - but unless you put it back - you will have no baseline. You need to make it stock before you send it anyway - or they may just return it because you did root and modify it.
Use Odin to do a master clear, flash back to JH6 with Odin, then do the JH7 update via your phone or with Kies, then you can do the one-click root.
Or just skip JH7 and bump up to JI6.
Thanks for the link...
Some more questions:
1. Will this clear my unlock? I forgot to write down my unlock code. Is there a way to get it out again before the flash?
2. Will this completely eliminate all traces of modifications?
3. What about my apps? I have a appbrain account, will I use that to revert? What about paid apps?
Thanks in advance..
Regards
Nick
verysafety said:
You can always use ODIN and flash it that way...
http://forum.xda-developers.com/showpost.php?p=8567598&postcount=6
Click to expand...
Click to collapse
Thank you all for your help. I was able to upgrade to JH7.
1. Did the JF6 Odin 1-click update (did NOT do a Master Clear)
2. Once back to baseline, I uses Keis Mini to upgrade to JH7 - worked flawlessly
3. Rooted using Lagfix (did not install lagfix though)
4. Installed appbrain app - I see all the apps that I need to re-install. I installed some, but will wait to get home and do the "Once Button" install over wifi
5. Titanium Backup was not able to Restore Apps (no 3rd part app installation allowed). Will just wait for appbrain to do its thing and restore app data only from Titanium backup (hopefully this option exists).
6. Restored all screen from Launcher Pro backup - widgets are messed up, but not a big deal
This definitely worked out, especially comparing to the alternative of sending in the phone and what not..
As a bonus, GPS performance is fantastic - caught 7 satellites in 5 seconds 30' accuracy with my phone near my office window (did not even have to go outside). Will test more with maps on my way home..
Falling in love with Android all over again
Once again, a BIG thanks to those who helped.
I will wait for a few days before taking on 2.2 .. gulp..
Regards
Nick
defriend said:
Thanks for the link...
Some more questions:
1. Will this clear my unlock? I forgot to write down my unlock code. Is there a way to get it out again before the flash?
2. Will this completely eliminate all traces of modifications?
3. What about my apps? I have a appbrain account, will I use that to revert? What about paid apps?
Thanks in advance..
Regards
Nick
Click to expand...
Click to collapse
Just wanted to report back, GPS is awesome now. Takes max 10 seconds (first time) when fired from Google Maps. Subsequent locks are taking no more than 6 seconds.
Also, did not find a way to just restore app data from Titanium Backup. So had to recreate some stuff .. no biggie. Anybody know of an alternative backup app that will actually let me restore apps and stuff - which is the point of a backup app!!
Regards
Nick
defriend said:
Thank you all for your help. I was able to upgrade to JH7.
1. Did the JF6 Odin 1-click update (did NOT do a Master Clear)
2. Once back to baseline, I uses Keis Mini to upgrade to JH7 - worked flawlessly
3. Rooted using Lagfix (did not install lagfix though)
4. Installed appbrain app - I see all the apps that I need to re-install. I installed some, but will wait to get home and do the "Once Button" install over wifi
5. Titanium Backup was not able to Restore Apps (no 3rd part app installation allowed). Will just wait for appbrain to do its thing and restore app data only from Titanium backup (hopefully this option exists).
6. Restored all screen from Launcher Pro backup - widgets are messed up, but not a big deal
This definitely worked out, especially comparing to the alternative of sending in the phone and what not..
As a bonus, GPS performance is fantastic - caught 7 satellites in 5 seconds 30' accuracy with my phone near my office window (did not even have to go outside). Will test more with maps on my way home..
Falling in love with Android all over again
Once again, a BIG thanks to those who helped.
I will wait for a few days before taking on 2.2 .. gulp..
Regards
Nick
Click to expand...
Click to collapse
Updating my friend's stock Tigerdirect G-Tab via OTA updater to what it says is:
Version 1.2-4349
This came up after the 3588 update when I opened the updater again.
So what is different?
lllGurulll said:
So what is different?
Click to expand...
Click to collapse
The update notes are:
-Adobe Flash Support in the Browser
-Support for an external Docking station
-Support for USB keyboard and mouse
-Support Weather for international cities
-Support for Spanish and French languages
-Lock screen that optimizes power consumption when idle
Wondering if there's a clockworkmod style recovery in this like what was in the pulled 3991 update.
Volume up while powering on to check it.
interesting.
This is the first I've heard of this version. I wonder if it has all the changes from the previous (now pulled) version 3991
Anyone want to make a quick video of the new stock with the enhancements?
Sent from my GT-I9000M using XDA App
going back to stock to check this out
Everyone be VERY careful, please
I didn't get this earlier today - but it's showing up now on my 3588 stock device.
Let us test it first, as this is their first 1.2 release and we want to check that bootloader. Thanks!
I know what I'm doing, tonight.
Btw, the release notes:
- Flash
- Dock support
- USB KB AND mouse support
- Spanish / French language
- Lockscreen
This is the one we've been waiting for.
updated my gtablet:
very good lock screen
Native Adobe Flash player browser
added Spanish and French
Energy saving screen
roebeet said:
I didn't get this earlier today - but it's showing up now on my 3588 stock device.
Let us test it first, as this is their first 1.2 release and we want to check that bootloader. Thanks!
I know what I'm doing, tonight.
Btw, the release notes:
- Flash
- Dock support
- USB KB AND mouse support
- Spanish / French language
- Lockscreen
This is the one we've been waiting for.
Click to expand...
Click to collapse
I know what I'll be doing; patiently awaiting your verdict on this update. =]
Updating as we talk . let's see what it bring to us...
Important, please read
I just went back to 2967, and I'm only seeing 3588 as an update.
I think 3588 is a gateway ROM, which is what I suspected last month. If you update your stock device to 4349, please do NOT flash to any mods, after that (at least not yet). Please let us test this, first - give me about an hour to run a few scenarios.
I will explain the reasons for this, as I do my tests to confirm what's going on.
EDIT: 2967 stock to 4349 stock causes a soft-brick. I think we have the same bootloader issue. Still running tests.
Thanks!
Updateing now. Wonder how much this will be like two tap x?
roebeet: Love your work man.
This is my first post ever and I just wanted to say thanks to all the Dev's out there.
Made some spelling mistakes and couldn't edit this post for five min.
Thanks Roebeet!!! I feel like you made this happen.
hmm for some reason i can boot after i use nvflash to go to stock...its stuck on the tnt screen...any ideas how to get past that??? I am coming from the Vegan GB RC1 rom
Its not bad, my only issue at the moment is long holding on the desktop and trying to change the wallpaper gives me an error. The on screen keyboard is definitely faster though.
I never got much chance to play with the previous builds, so I can't give comparisons. I had an issue where everything came to a halt. I had to to a hard shutdown. When it rebooted, I had to reinstall everything I downloaded from the Amazon Appstore. Seems to be working fine now.
rbansal2,
It takes a long time to get past the Tnt screen. If being patient doesn't work, you will need to load or flash CWM and go in and do the repartition, wipe dalvic cache, fix permissions, wipe cache, wipe/reset factory data routine to clean the tablet up.
Then reflash stock again and see if you don't get a usable base to OTA up to 3588.
Rev
P. S. -- This was a quik note so if you don't remember, ask me.
Seems good to me! Of course I like the stock tnt setup
I didn't play with custom roms because they looked like my tab was a giant phone most even had a phone icon.
rbansal2 said:
hmm for some reason i can boot after i use nvflash to go to stock...its stuck on the tnt screen...any ideas how to get past that??? I am coming from the Vegan GB RC1 rom
Click to expand...
Click to collapse
You'll probably need to repartition the sdcard. You can install clockworkmod using the microSD method or nvflash method and then use it to repartition to 2048 and 0. Remember that repartitioning will delete everything on the user partition (what's called "sdcard" in the rom). Back up your data before doing this.
I had this same problem a while ago after a nvflash and that's how I fixed it.
Hey guys,
Like many T-Mobile G2x users i got seriously fed up with the poor gps K on the phone. When i first got my phone, after i rooted it I tried many of the roms here on the development forum but none of them could fix the gps locking issue. IN the past few days, the phone could not even "view" satellites at all. I was running the JUL 2011 baseband at the time. However after digging around, I went ahead and updated from the LG website with their update software. now my current baseband is M6600A-SCAUTNZ-2.0.9720T 1 [MAR 11 2012 10:00:00] MP:TRULGE_08.09.02R-MDM and gps functionality comletely came back. I have a lock under 1 min, the phone still works for calls/text, and data still works.
I ran this process on a computer with Windows 7 Ultimate 64-bit. After the LG update completes it will revert the phone to stock recovery.
Here is a step by step of what I did. Please read everything first before doing the steps.
1. Use TGA_Gunman's guide to restoring a stock Nandroid OS that is unrooted. http://forum.xda-developers.com/showthread.php?t=1048274
A Stock ROM (v21e, v10f, or possibly others) is required for the "LG MOBILE SUPPORT TOOL" to work. Either from a personal backup or downloaded. Recovery version doesn't matter, but suggested to have latest CWM to make Nandroid backups & restores easier.
2. (optional) After you boot into the system link your google accounts, just as you would when opening a phone for the first time.
3.Visit LG's Website and download the T-Mobile LG G2x software update tool.
http://www.lg.com/us/support-mobile/lg-P999 (click on the software update tab and follow the 4 steps)
4.After installing LG Update software on your computer, run it, and follow the steps it tells you exactly.
5.Have PATIENCE! This will take around 15 min. and patience is the key. Let it sit there and do it's thing. Make sure your computer doesn't turn off or go into standby during the process and don't disconnect your USB cable until the installer is at its last step and its tells you it's done with the update.
6. Enjoy your functional gps!
P.S.: Thanks to everyone for the helpful feedback and tips to making this guide better!
If you are looking to downgrade your baseband or have unknown baseband error check out xBkKx's guide http://forum.xda-developers.com/showthread.php?t=1680292
EDIT 06/2/2012:
The CM7 RC3 update has been verified that it will work with the new March 2012 baseband. If you wish to update to the rc3, apply a "dirty flash" of the 27th nightly update after it (this resolves the gps locking time back to a couple of seconds again).
CM7 RC3 Update link : http://download.cyanogenmod.com/get...t/archive/update-cm-7.2.0-RC3-p999-signed.zip
CM7 27th Nightly Build: http://download.cyanogenmod.com/get/jenkins/1991/update-cm-7-20120527-NIGHTLY-p999-signed.zip
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
You don't have to be on that nandroid or link your Google account prior to the update.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
xBkKx said:
Why wouldn't you have calling/data after updating only calling issue is people not wanting to stay stock with this baseband.
Isn't there already guides to update the phone?
You don't need to be on that nandroid or link your account.. I restored my rooted stock nandroid downloaded drivers, installed lg tool and it updated fine as I just walked away and came back to it sitting in home screen with new baseband
Sent from my LG-P999
Click to expand...
Click to collapse
When i said calling/data still works i was referring to what some other people in the forums had said that they couldn't get a signal after updating baseband. I, however, did not find anything about using LGs update tool on windows 7. All the topics that came up were about procedures on doing it with windows xp only.
If this way works with the other nandroid versions that thats great news . However, when i was on the July 2011 baseband and I loaded one of the other stock nandroid versions the earpiece and microphone were not working at all. I could place/receive calls but the other person could not hear me nor could i hear them. when I loaded the v10f stock this problem did not come up, so just to be safe I recommend using that one.
Also you said there's calling issues for people that want to use other roms with this baseband? Does that mean I can't load up one of the recent EB ICs roms, etc with this baseband version?
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
BuddhaTeh1337 said:
call audio doesnt work with newest baseband and modded roms (tother than kwes's and buru's, both of which are based on V21Y). it just clicks and pops unless you are on wifi calling. basically devs need to start basing their ENTIRE rom on this baseband if they want call audio to work.
Click to expand...
Click to collapse
actually now the 27th CM nightly update and the CM7 rc3 update have fixed the in call audio problem. im running this update with the new baseband on my phone and everything is working fine. the only thing that doesnt work yet are the old ROMs .hopefully devs do something about that
I also updated from rooted stock (xboarders 2.3.3). I didn't go back to stock recovery. I just ran the LG updater (already had drivers installed), plugged in the phone, hit the update button, and let it do it's thing. It took about 20 minutes
I'm confused about all of the confusion.
XDA Mobile
Hi all,
I did the above procedure, and did the restore from the "LG-P999-V10f" image.
On reboot, the phone comes up and shows the stock "LG" boot up screen.
The scrolly thing goes across for a bit, and then *stops*!
At this point, it is locked up, it won't boot any further up, and when I attempt to use the LG Updater tool, it does see the phone, and says "Phone connected", but the 2nd part of it when checking the phone communication, it fails with "Problem with communication between the cell phone and PC".
So I am stuck...
(Hopefully not bricked?)
Any thoughts? Suggestions?
Thanks!
Scott
I figured it out, after some minor panic!
The problem was, my ClockWork Mod Recovery bootloader version on the phone was too old!
I used a factory ROM image that was taken from a newer version, and it included some (.tar's I think) file types that weren't supported on the old version of the Recovery.
Thus, I burned an incomplete version of the stock firmware to the phone!!!
(Which is why it was stuck at boot!)
I was able to "One Touch Recovery" with a newer version of Clockwork Mod, slap my Backup of my CM in place, and get back to where I started.
And as part of the "One Touch Recovery", it updated my boot loader to a newer version, and so now the loading of the factory ROM image worked.
I then just ran the LG Updater software after going back to the factory ROM Image, and indeed, it finally works as expected!
Scott
Glad to hear that it worked Scott! And thanks for the feedback, i have updated step 1 to say you need latest version of clockwork recovery
It looks like LG may have taken the update file down, or for whatever other reason, the software update tab is blank. Could someone put up a link to the update file?
@sigmabeta: I noticed during a particularly slow page refresh that the links for the usb driver showed up briefly as the page loaded, then disappeared. I managed to stop the page from loading completely and got the 4 steps listed (under manuals, of all places) one of the links was the update tool, here is the link:
h-t-t-p://csmg[dot]lgmobile[dot]com:9002/clientapp/B2CAppSetup.exe
I downloaded it successfully from there. Enjoy!
(sorry I'm new and it won't let me post links yet)
LG update tool won't update
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
aft3rgl0w said:
I managed to download it from LGs site, but despite flashing the v10f rom onto my phone, the update tool says software version is 11f (even tho the phone info shows 10f) and that it is up to date, and won't let me perform the update. Baseband is still Jun 2011. Any ideas, or a link to the version of the setup tool you used?
Click to expand...
Click to collapse
hmm. im not sure about this one. try this: reboot into clockwork recovery mod and do factory reset . after clear your cache, then clear your dalvik cache. then install the v10f from the restore menu in clockwork mod . after restart, set up your phone as you would do for first time (link google account to it) and then plug it in to your computer and run the LG update tool. thats what i did and it worked for me
also you said version v11f? you must have not flashed the restore correctly. do the above.
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Phone info SW ver says LG-P999-V10f. Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll re-download it again and try in the morning. what version of the LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
aft3rgl0w said:
The first time I flashed it, I followed the instructions, which said to factory reset AFTER the flash, but I did think of what you suggested and tried it again, factory resetting, clearing cache and dalvik twice before restoring, but the tool is still saying the SW version is 11f. If I go to Customer Support -> Update history, it shows SW v21e (even after reading phone info). Weird. Should I factory reset/cache/dalvik _after_ flashing the v10f rom as well? i'll redownload it again and try in the morning. what version of te LG updater tool do you have? mine is v1.5.7.0. many thanks for your help.
Click to expand...
Click to collapse
yes. you should do a complete factory reset even after installing the v10f rom. this is detailed on the original post on how to flash back to stock rom in TGA_Gunmans post.
I just noticed too that it reverted back to froyo (v2.2.2) and not GB, could this be part of the problem? should the stock be 2.3?
just to clarify your last reply re factory reset after v10f flash - should i clear dalvik as well?
yes it should revert back to froyo. and yes reset the dalvik cache too
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my phone
Sent from my LG-P999
xBkKx said:
Have you tried the V21E? I just flashed back to my Jul baseband and restored my 2.3.3/V21E nandroid and the updater found the 2.3.4 release instantly for my
Sent from my LG-P999
Click to expand...
Click to collapse
yes you could try the 21e. however for me, that version always failed to download from the website gunman uses to host those files so i used the v10f inatead. much faster download.
btw how do you revert back to a previous baseband?
I just Googled how to do it using like 6 different guides :/ I edited my thread on iso help on it with what worked for me if you want to try it: http://forum.xda-developers.com/showthread.php?t=1680292
V21E/2.3.3 Mirrors, just restore it, connect phone to computer, run updater, should go smoothly :
Dropbox
MediaFire
RapidShare
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