Related
These are the following steps that worked for me. For the record I was upgrading to a newer stock firmware from an older rooted stock firmware. I believe you can use the same version as your current stock firmware too. If this does not work for you please don't hold me accountable.
Steps
- Installed latest Kies 3 beta (for usb drivers). After install insure Kies is closed.
- Obtained latest Odin 3.09
- Downloaded my phones firmware from Sammobile.com (latest firmware for my model/country/provider with no upgraded boot loader) and extracted the .zip file leaving me with a myphonefile.tar.md5 and an SS_DL.dll file. It's very important to grab the right model/country/carrier or you could be in for a world of hurt. Only thing I hate about Sammobile is it requires registration to download firmware even though the whole process was painless.
- Backed up all apps with Titanium Backup to my external SD Card, and copied all contents to my PC then wiped my SD Card.
- Went to settings->general->security and INSURED REACTIVATION LOCK WAS NOT SELECTED.
*note before beginning the following process I REMOVED NO ROOT APPS from my phone eg. framework xposed, wanam xposed, superuser, titanium backup, root explorer, adblock.
- Powered down phone and removed SD card.
- Held volume up + home +then power to get to stock recovery menu.
- Selected Wipe/Factory Reset Phone then selected yes. (note - volume up and down moves selection, and power selects)
- Repeated Wipe/Factory Reset step again just to be safe, as per a post I read.
- Then selected reboot
- On reboot I immediately held volume down + home and then power to prompt odin download mode. Then pressed volume up to confirm.
- Opened Odin 3.09 on PC (Windows 7, SP1, 64-bit) and then connected my phone via the usb3 cable that was included with my phone (my computer has usb3 ports and the connection speed is awesome). Under ID:COM my phone's com connection showed up in the box and turned light greeny blue. The only options selected were Auto Reboot and F. Reset Time (this was by default).
- Clicked on AP (guess it's PDA on old versions of Odin) and browsed to and selected myphonefile.tar.md5. It took about a minute for Odin to run a hash check on myphonefile.tar.md5.
- Once the hash check finished successfully (via the message box) I clicked on start. Once the flash completed my phone auto-rebooted. I stared at the Samsung logo that eventually dimmed and my phones blue notification light pulsated like a heartbeat for what seemed like eternity but after a minute or two my phone booted into android.
I was greeted with the initial setup screens that I had when I purchased the phone.
After setting up my google account, wifi etc. I immediately went into settings->general->security and unchecked Auto update security. I then waited for my phone which downloaded about 21 app updates. Once it finished I rebooted into download mode (drum roll)........
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void 0x0
Sorry this is so drawn out, just hoping someday it might help a couple peeps.
Sounds great.
1). Was your KNOX 0x1 before doing thus?
2) does software uodate work now or still says device modifued?
3) which w8 soft u downloaded,? It does no go by date, which us newest?
4) u never installed custom recovery?
Thank you
Sent from my SM-N900W8 using xda app-developers app
odeccacccp said:
Sounds great.
1). Was your KNOX 0x1 before doing thus?
2) does software uodate work now or still says device modifued?
3) which w8 soft u downloaded,? It does no go by date, which us newest?
4) u never installed custom recovery?
Thank you
Sent from my SM-N900W8 using xda app-developers app
Click to expand...
Click to collapse
Knox was always 0x0 even after root. Everything went back to official, software updates,OTA all work as expected. Went from MI5 rooted to MJ1 stock. Never installed a custom recovery that would of definately tripped knox. Already rerooted MJ1 with Universal Root De La Vega. Xposed framework,wanam xposed has status official and knox still 0x0.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Thanks a lot.
I have a rooted N900L with kingoapp.com method.
I'm in Korea and found out that MJ9 firmware came out this morning.
Words are new firm has greatly increased WiFi stability so I was seriously thinking of unrooting, go back to stock rom, upgrade and the root again.
Finding ways of getting back to stock rom without tipping the KNOX flag, sure your thread gives me a lot of help. :good:
Thank you for pointing me to that stock firmware. It got me out of a horrible mess from a bad firmware flash. I was getting force-closures everytime the Samsung Keyboard was activated, as well as almost any stylus functions. Now they seem to be working again.
With a team effort from myself and @tdunham I'm back again with a completely stock build of Android TW-Lollipop 5.1.1 (N920PVPU1AOGD) for the Sprint Samsung Galaxy Note 5.. I built this stock pre-rooted ROM using the official Samsung tar ball. The ROM will self root upon flash and it has init.d/busybox support (when custom kernels support it). Knox and Sprint Itson has been removed completely. It is completely stock with all of the original factory installed apps as well as a few added features. This build contains a fully deodexed framework and system apps.
Other than the removal of Knox and Sprint Itson, it is stock in almost every other way. This first build is stock and will stay that way. I may make a custom rom later on. This ROM is intended for people who want the stock rom in it's original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base and I highly recommend that you do so because it is bug-free and built from the official Samsung tar ball. However I do expect proper credit if you use this rom for any other project. If you discover any issues please send me a PM as I may not continuously monitor this thread. If you like my work please press that Thanks button, rate this thread, and consider a kind donation! Enjoy!
About ROM:
Android 5.1.1 N920PVPU1AOGD_N920PSPT1AOGD_SPR
Stock N920PVPU1AOGD kernel (root-permissive) by: @Manh_IT
All factory installed apps including the Sprint Setup Wizard, etc are included. Nothing was removed except...
Knox and Sprint Itson removed.
Hotspot mod enabled
Added camera shutter sound option in camera settings
Added call/message block in settings
Enabled call recording from the phone dialer
Private mode works out of the box
That's about it... for now. This should be as close to the original rom as possible.
Known issue:
tx_dbs_tx said:
I just wanted to let people know that Sprint "ID" is causing Carrier Setup Wizard to fc as well as ID itself. This is a known issue and it is caused by Sprint "ID". I have not been able to successfully deodex it. The apk doesn't like to be deodexed. Until ID has an update through Google Play or Sprint Zone I will not be able to update it in the rom. Once there's an update to ID please send me a PM and I will update the rom. Until then you will have to delete or freeze Sprint "ID" to stop the fc's. Sorry for this inconvenience. It is out of my control at this time.
Click to expand...
Click to collapse
If you are currently on the stock unrooted rom:
You ONLY need to flash the latest TWRP recovery ( for the N920P ) using odin on your pc. Nothing else. Then flash this rom afterwards. The ROM zip will pre-root your phone as well as flash the stock root-permissive OGD kernel by @Manh_IT
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal device storage to another location just to be safe.
2. Download the rom using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the md5!!! Once the download has finished, compare the AFH md5 using a md5 tool on your pc. (Google "md5 checksum windows").
4. Put the downloaded rom onto your internal storage..
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT internal storage. Wiping Internal storage is optional but recommended in certain circumstances. The reason is to remove left-over data from previous version of Android and start with a clean slate.
7. Choose the "Install" option and select the rom "Sprint_Hybrid_N920PSPT1AOGD" from your internal storage. It will flash the rom and give a confirmation once completed.
8. Press "Reboot" then "reboot system". You should get no prompts or warnings about not having root.
9. Initial rom "optimization" may take several minutes while ART builds its cache and the phone will remain on the yellow Sprint Spark screen for about 8 to 10 minutes. Let the phone optimize for at least 10 minutes and the screen WILL eventually turn off or show the setup wizard once it finishes. If the screen turns off then simply turn it on and proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically install the Sprint apps. (I know... nobody likes that suff!) You must either "accept" or "disagree" with each and every google prompt for these apps or else the installs pause until you do so.. That's it! You're done!
flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device.
Credits:[CENTER @tdunham for his initial kitchen updater script and his willingness to work together with me so we could tag team the initial dev'ing and testing phase. I must say it was a pleasure!
the same awesome group of testers which also are credited in T's OGD ROM thread found HERE. @Team DevDigitel @Chaz187 @fsunoles101 @JoeyDuran @GAPO @rlmiller @sml2004
Special thanks to: @Beastmode Brian for providing the updated google apk's i needed. Thanks a lot man!
If somebody was left out please let me know!
[/CENTER]
DOWNLOADSprint Stock N920PSPT1AOGD DeodexedEnjoy!!!.
XDA:DevDB Information
Sprint_Hybrid_N920PSPT1AOGD, ROM for the Sprint Samsung Galaxy Note5
Contributors
tx_dbs_tx, @tdunham @Team DevDigitel
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N920PSPT1AOGD
Based On: N920PVPU1AOGD_N920PSPT1AOGD_N920PVPU1AOGD_HOME.tar
Version Information
Status: Stable
Stable Release Date: 2015-09-06
Created 2015-09-03
Last Updated 2015-09-09
Mods
N920PVPU1AOGD_Odexed-Deodexed_Hotspot_Mod
(can be flashed on odexed or deodexed OGD roms. the script will remove appropriate odex files automatically)
Reserved
Nice man congrats on the release..... Glad to see sprint getting some love! !!!!
You moved over to the 5, Sweet!!!!!?
Ok, now I really need root!
The mans in the house thanks bro
Sent from my SM-N920P using XDA Premium HD app
So glad to see develpment starting to move along. Thank you so much for this. Awesome job.
Sent from my SM-N920P using Tapatalk
Rom doesnt get passed the sprint boot screen waitied 15 minutes it just randomly rebooted
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
Rom doesnt get passed the sprint boot screen waitied 15 minutes it just randomly rebooted
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
I just slammed my brake when I say this. I'll till this issue is resolved.
pbedard said:
Rom doesnt get passed the sprint boot screen waitied 15 minutes it just randomly rebooted
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
Did u download the ROM on ur phone? If so, u still have to verify the MD5. One thing about DBS ROMs is a completely clean slate is best. I would re-download the ROM on computer the verify and move to internal storage. U have a backup to go to JIC?
M2Iceman said:
You moved over to the 5, Sweet!!!!!?
Ok, now I really need root!
Click to expand...
Click to collapse
No I don't have the Note 5. I was invited to come help with the new stock base rom and thisis simply my own version with everything left in the rom and is hybrid odexed/deodexed.
Can somebody please download, verify md5 and test flash for me. I need to make sure there's not a problem with the rom. I need a comfirmation from a couple of people wether you successfully boot or not. Thank you.
tx_dbs_tx said:
No I don't have the Note 5. I was invited to come help with the new stock base rom and thisis simply my own version with everything left in the rom and is hybrid odexed/deodexed.
Can somebody please download, verify md5 and test flash for me. I need to make sure there's not a problem with the rom. I need a comfirmation from a couple of people wether you successfully boot or not. Thank you.
Click to expand...
Click to collapse
The md5 matched, but I'm also getting a failed boot at the spark screen. sits on it for a good 10 minutes, reboots, then does it again.
Do you care if i use this as a base? Gonna go through and pull bloat for the lazys and reup it.. credits due of course for your orginial work. Lmk
Thanks for the build. Gonna run in as soon as the dl finishes
So being that this is odex and deodexed and some system apps aren't deodexed, will xposed work with this rom?
tx_dbs_tx , Original poster is correct, flashed 3 times 3 dls, no go,, same result long wait on spark logo, random reboot and restarts again, wont fully boot as is
Team DevDigitel said:
Do you care if i use this as a base? Gonna go through and pull bloat for the lazys and reup it.. credits due of course for your orginial work. Lmk
Thanks for the build. Gonna run in as soon as the dl finishes
Click to expand...
Click to collapse
Hit me up on Hangouts if you can. [email protected]
If you have time you can help me test to find the problem. I can tell you exactly what to do to find the cause and you won't have to re-download the rom.
Sorry about this people. I don't have the Note 5 so I couldn't flash & test this build which is based off of our original test roms which are good to go. I made some changes, updated some framework files and re-uploaded this version and it's not booting. In the meantime I have to pull the download/link until i find and fix the problem. If anyone can help me test the rom, please contact me on google hangouts using my email address above. Thank you.
tx_dbs_tx said:
Hit me up on Hangouts if you can. [email protected]
If you have time you can help me test to find the problem. I can tell you exactly what to do to find the cause and you won't have to re-download the rom.
Sorry about this people. I don't have the Note 5 so I couldn't flash & test this build which is based off of our original test roms which are good to go. I made some changes, updated some framework files and re-uploaded this version and it's not booting. In the meantime I have to pull the download/link until i find and fix the problem. If anyone can help me test the rom, please contact me on google hangouts using my email address above. Thank you.
Click to expand...
Click to collapse
Any way to get that kernel? I think the Noble kernel is crashing my phone. Sprint Note 5
My is crashing. Every time i use hotspot
Jordan011 said:
Any way to get that kernel? I think the Noble kernel is crashing my phone. Sprint Note 5
Click to expand...
Click to collapse
A couple of people are currently working on the stock OGD root-permissive kernel. When they release it for testing or final build, i will include it in the rom. However I don't think the current kernel is the problem.
I sent an invite but I can't test until tomorrow I left my damn computer at work. But if you ever need some one to test something let me know, I'll gladly risk my device! Haha
painiac's Essential Guide to Samsung Galaxy S5 (SM-G900V) Flashing, Rooting, Fixing, and Customizing
This is a distillation of everything I've learned about rooting, installing custom recovery, installing custom ROMs, and customizing the Verizon Galaxy S5 SM-G900V. I am NOT the creator of any of the hard work that has made all of this possible, I simply compiled it all in one place. I have done this for the convenience of newer people, and to hopefully decrease the need for the same questions coming up every time somebody discovers they can improve their phone but doesn't yet know how. The Galaxy S5 has a steeper learning curve because of its locked bootloader, hence the need for a guide. I know I had a LOT of questions and more than a little worry about accidentally screwing up my phone, so I did a lot of research and accumulated a lot of information in a short amount of time.
CAUTION: Some of the more general information here might apply equally to all variants of the Galaxy S5, but much of it is specific to the Verizon SM-G900V (and attempts to flash any G900V-specific files to a non-G900V variant will in all likelihood brick your phone. You have been warned.)
This is meant to be a general repository of information, but for projects in active development (such as the 5.0 root method, SafeStrap, custom ROMs, etc) I encourage you to ask questions in their respective threads where their developers (who are most knowledgable about their projects) are best able to see and answer your questions.
If a piece of information originated from you and I have failed to credit you properly, please say so and I will do so immediately.
I encourage you to share this information freely, and I encourage you to submit even minor corrections.
Table of Contents
Android Versions
Updates and Flashable Stock Files
Restoring, Upgrading, and Downgrading
Recovery Mode and Download Mode
Flashing Files with Odin
Custom Recovery Environment
Fixing a Bricked Phone
Rooting 4.4.x and 5.x
Custom ROMs
Debloating
Disabling Knox
Xposed Framework and Modules
Android Versions
First, a brief introduction of the Android versions available on this phone. You find your version number by opening "Settings" and scrolling down to "About Phone" The version numbers look like (for example) "G900VVRU1ANCG", and only the last three or four digits are what we refer to. In this example, we would abbreviate this as "ANCG" or "NCG". You'll note that the version numbers are roughly alphabetical.
KitKat 4.4.2 versions (root with TowelRoot, more on this later)
ANCG = 4.4.2
ANE9 = 4.4.2
KitKat 4.4.4 versions (downgrade kernel to root with TowelRoot, more on this later)
ANHA = 4.4.4
ANI2 = 4.4.4
ANK2 = 4.4.4
ANK7 = 4.4.4 (incremental update to prepare for 5.0; it is not available for download, nor is it necessary to do so)
Lollipop 5.0 versions (root with KingRoot, more on this later)
BOA8 = 5.0
BOC4 = 5.0
BOD5 = 5.0 (last version of the bootloader that can be downgraded)
BOE1 = 5.0 (prevents downgrading the bootloader)
BOG5 = 5.0 (prevents downgrading the bootloader)
BOK3 = 5.0 (prevents downgrading the bootloader)
BPB1 = 5.0 (security update. prevents downgrading the bootloader))
Marshmallow 6.0.1 versions (not rootable yet)
DPD1 = 6.0.1
DPF4 = 6.0.1 (minor bugfix)
Updates and Flashable Stock Files
If you accept an OTA (Over-the-Air) update from Verizon, it updates everything. The same thing happens when you manually flash a "firmware" or "factory restore image" file. Note: If you are still on BOD5 or earlier, do not accept an OTA update.
You can also selectively update certain components by flashing only those files. Most files are flashed with Odin, but some can be flashed in a custom Recovery if they were so prepared.
CAUTION: If you are on BOE1, BOG5, BOK3, or PB1, do not under any circumstances attempt to flash any older versions, or you will brick.
Firmware: Collectively refers to the Operating System and Applications that allow the phone to function. A "Retail" firmware file also contains all the components listed below, so be sure you know what you intend to accomplish by flashing one. You should stick with the latest safe firmwares provided by jrkruse.
CAUTION: If you have BOE1, BOG5, BOK3, or PB1, do not under any circumstances flash an older firmware file unless it specifically says it it is either "for BOE1 or later" or that it does not include a bootloader.
Bootloader: Performs basic checks and then instructs the kernel and the other essential software to boot. On this phone, the bootloader is locked: if it doesn't find the correct (TouchWiz-based) kernel, it will not allow the phone to boot. As of the BOE1 update, a hardware "qfuse" is tripped permanently, which prevents downgrading. In order for a 5.0 ROM to boot, you need a 5.0 bootloader: If you have not previously accepted an update to BOE1, BOG5, BOK3, or PB1, then the best thing to do is update the bootloader to BOD5, which is the last bootloader that can be downgraded later.
CAUTION: If you have BOE1, BOG5, BOK3, or PB1, do not under any circumstances flash an older firmware file unless it specifically says it it is either for BOE1 or later or that it does not include a bootloader.
Note that on the special "Developer Edition" S5, the bootloader is not locked, but the price is unreasonably high.
CAUTION: If you do have a "Developer Edition" phone, do not under any circumstances flash any file that has a retail bootloader, or your phone will have a permanently locked bootloader and will, practically speaking, no longer be a "Dev Edition" phone.
Kernel: Basically the layer that allows the operating system (Android) and the hardware to communicate with each other. You can flash a different kernel version independently, but the operating system will not actually be able to start with an incompatible version of the kernel and it will hang forever on the splash screen. Downgrading the kernel temporarily is necessary for obtaining root on later builds, because the root exploits always get patched in later versions. Simply flashing the compatible kernel will allow the phone to again boot normally. You should stick with the latest safe kernels provided by jrkruse.
CAUTION: Do not attempt to flash a custom (non TouchWiz-based) kernel, or you will brick.
Baseband: This is the Modem, sometimes called a Radio. This is what allows the phone to communicate with the cellular network. Modems can be flashed independently and without regard to the firmware version you're running. You can experiment with which modem gives your particular phone the best reception in your area (which may or may not be the most recent one). You can find flashable modems here.
Non-HLOS: This contains other radios such as Wifi and Bluetooth.
PIT file: Re-partitions the internal storage. You do not normally need to do this, but it can correct specific problems.
Restoring, Upgrading, and Downgrading
If you are on 4.4.x, you can update to 5.0 and keep root.
CAUTION: If you want to preserve your ability to downgrade to 4.4.x, never upgrade via an OTA or other official update; Only upgrade with flashable ROMS or modified Odin files that do not upgrade the bootloader past BOD5.
If you are on 5.0 BOD5 or earlier, you can freely downgrade to 4.4.x, but do not upgrade your bootloader to BOE1 or later if you want to be able to downgrade later
If you are on BOE1 or later, you can freely upgrade but you CANNOT downgrade.
If you need any restore files for NCG through OC4, Misterxtc has provided them here.
I advise you to download these files now if you need them, because I have noticed with previous phones that as people lose interest in particular models, files that are hosted in only one place tend to disappear.
If you need BOG5 and BOK3 restore files, jrkruse has provided them here
Note that he has provided a version that will update (lock) the bootloader, and a BOD5 bootloader version that will not lock the bootloader if it has not previously been locked. If you are on Lollipop there is no good reason to not update to the latest BOK3 firmware, but if you're still on a BOD5 or earlier bootloader then use the "BOK3 firmware with BOD5 bootloader" it in order to preserve your option to downgrade to KitKat.
Recovery Mode and Download Mode
Recovery Mode: This phone has a built-in recovery environment (typically referred to as "stock recovery"), which you access by first powering off the phone (and making sure it's not plugged in), then holding the Home + Volume UP + Power buttons at the same time. After a couple seconds, blue text will appear at the top of the screen which says "Recovery Booting..."
CAUTION: Never attempt to install a custom ROM or unofficial update file from the stock recovery mode: the phone will flip out and brick.
The stock recovery mode contains the following options:
1) reboot system now
2) apply update from ADB
3) apply update from external storage
4) wipe data/factory reset
5) wipe cache partition
6) apply update from cache
Wiping the cache is an easy and painless fix to a lot of vague problems and even solves some boot failures after installing a custom ROM. Doing a factory reset can solve a lot of things too, but be aware that you'll have to reinstall and reconfigure all of your apps unless you keep good backups.
Download Mode: The phone also has a mode where you connect to software on a computer and flash files to it, sometimes referred to as "Odin Mode". Access Download Mode by first powering off the phone (and making sure it's not plugged in), then holding the Home + Volume DOWN + Power buttons at the same time ("down" = "download"...get it?). After a few seconds, a screen will appear giving you a dire warning that installing a custom operating system is known to the Surgeon General of California to cause cancer, or...something....I don't know, I've never actually read the whole thing. Just press Vol-Up to acknowledge the warning. While in this mode, connect the phone via a microUSB cable to a Windows computer.
Flashing Files With Odin
The operations in Download Mode will be performed with a piece of Windows-based software called Odin. This tool is reported to be the actual software that Samsung uses to flash and repair phones, which has been leaked to the Android community. I caution you to only download this from XDA-provided sources. Odin is used to flash files to the various system partitions of the phone (firmware, kernels, modems, factory restore images, etc). Odin cannot be used to flash custom ROMs.
Odin 3.09: can be downloaded here.
Note that when you have the phone in Download mode, your computer won't show it as a device in "My Computer" because it's not connected as a media device., but Odin (or any other software that knows how to look for it) can see it. Odin will highlight blue in its first "ID:COM" box when it detects your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You'll see several boxes on the right side when you open Odin.
BL = Bootloader
AP = Your system, recovery, and boot.img (this was labelled "PDA" in older versions of Odin)
CP = Modem
CSC = Cache and Hidden CSC features
Everything on this phone is flashed using "AP" box (highlighted in blue in this picture), and you'll want to leave every option at the default setting unless specifically told otherwise.
When you click "AP", a file browser window will pop up, and you browse to and select the flashable file you've downloaded. The file needs to be one that ends with a file extension "tar.md5", or Odin can't see it. If what you've downloaded is a zip archive, the image is inside that and you need to extract it first.
Only extract a flashable file if the contents of the archive are "FILENAME.tar.md5", because that itself is the Odin-flashable archive. But do not attempt to extract the contents of the tar.md5, just flash it with Odin. If the file is a .zip that contains "META-INF" and/or other files and folders, it is to be flashed with SafeStrap or FlashFire rather than Odin.
MD5 Checksum: Before flashing ANY file, you need to verify that it downloaded fully and accurately. To do this, you use an md5 checksum tool (such as this one provided by Misterxtc), which generates a hash string based on the exact bit content of the file you've downloaded. You then compare that string of characters to the one provided along with the original. For example, AndroidFileHost.com will always list it here (as I've highlighted in red). You don't have to manually compare them, as most md5 tools have an input box where you can paste the string for comparison. If the file you've downloaded is even slightly corrupted or incomplete, the md5 checksum will not match and you'll know immediately that you need to re-download it. Obviously, attempting to flash a corrupted file will fail. You should check the md5 after you download a file, and again after moving it to your phone's storage. Here you see the md5 hash, which I have outlined in red.
After you select your file, Odin will verify its integrity. When that process is complete, click Odin's "Start" button. The file will flash to your phone, then when the flash is complete (unless you unchecked that option) the phone will be rebooted automatically. The text box on the bottom-left of the Odin window will report the results of the flash operation, including any errors.
CAUTION: Do not unplug your phone or allow your battery to die while a flash is in progress!
Odin troubleshooting (if your phone is not recognized by Odin, or a flash fails)
1) Verify the md5 checksum of the file you're trying to flash
2) Ensure the USB drivers for the phone are installed and up to date on the computer you're using. If you have problems, you may have to "uninstall" the phone from the computer's "Device Manager" and then reinstall it.
3) Check that your microUSB cable is fully seated in both the phone and the USB port on the computer.
4) Try a different microUSB cable and/or a different USB port on your computer (a bad cable or bad USB port are very common causes of a flash failure)
5) Examine the microUSB port on your phone to ensure it's not damaged, or plugged with pocket lint which may be preventing a complete connection
Samsung provides a free tool called "Kies", which allows you to do various things including installing drivers, transferring files to/from your phone, etc. You may find it useful if you are having difficulty connecting your phone to your computer. Just be aware that if you have Kies running, it will prevent Odin from functioning.
If Windows is not an option for you, you might try the open-source alternative to Odin known as "Heimdall Suite". I have no experience with Heimdall so will not try to comment on it further, but if anybody has any important info about it I would be happy to edit it into this guide.
Custom Recovery Environment
Due to the locked bootloader, the custom recovery environments such as TWRP (TeamWin Recovery Project) and ClockworkMod Recovery (CWM) cannot be used. However, hashcode created SafeStrap Recovery (a heavily modified TWRP recovery environment) that is safe to use on the S5.
A custom recovery is optional, but it's a powerful tool and safety net, allowing you to flash files (except Odin files), install ROMs, selectively wipe partitions, and create/restore full system backups (known as NANDroid Backups), among other things.
SafeStrap was originally conceived to allow ROMs to be installed in different "ROM Slots", allowing the stock OS to be untouched and easily swapped between. Unfortunately, hashcode abandoned SafeStrap development before the slots were ever made to work reliably. If you are still using the KitKat 4.4x version of SafeStrap, only flash ROMs to the "Stock" slot and pretend the other slots do not even exist.
hashcode's original SafeStrap thread - Use this if you are still on 4.4.x
If you are on Lollipop 5.x, hashcode's version of SafeStrap is functional, but requires a workaround so it is a bit of a hassle. SafeStrap will not function with a 5.0 kernel, so you most first either use Odin or the NI2Flasher.apk to flash an older 4.4.x kernel, then boot into SafeStrap. You must then flash your appropriate 5.0 kernel with Odin or from within SafeStrap BEFORE rebooting, or your phone will not be able to boot. Fortunately, jrkruse has modified SafeStrap Recovery to work smoothly on 5.0: it automates the process of the necessary kernel flashes ( and has several other small improvements, such as removing the non-functioning ROM slots).
jrkruse's updated SafeStrap for Lollipop - Use this if you are on 5.x
FlashFire: If you don't want to use SafeStrap for some reason, an alternative is Chainfire's "FlashFire" app. It is fully capable of doing most anything SafeStrap can do, without you having to boot into a custom recovery environment. The only real downside is that Flashfire is an app, so if your phone won't start up then you can't use it to restore a backup. You can selectively use both FlashFire and SafeStrap depending on the circumcstances.
Fixing a Bricked Phone
"Bricked" means a phone will not start and can no longer be used; in other words, it's as good as a brick. Fortunately, in almost every case the phone is not totally ("hard") bricked, but is only "soft" bricked and can be repaired fairly easily. If you are unable to load your operating system but you are seeing any kind of logo or splash screen, relax: you are only soft bricked, and the phone can be fixed bexcause you can still boot the phone into Download Mode and Recovery Mode.
If you've just flashed a file (such as a custom ROM) and the phone won't start, don't panic.
1) The first thing to try is to wait: if you've just flashed a deodexed ROM, it can take up to ten minutes to load and boot, and all you'll see is the splash screen. Let the phone sit for 10-15 minutes to see if it's just busy.
2) If the phone still won't boot, unplug the phone and pull out the battery, then re-insert it and try again.
3) If the phone STILL won't boot, pull the battery again, then reinsert it. Enter Recovery Mode by holding the Home + Volume UP + Power buttons at the same time until the phone says "Recovery Booting" at the top of the screen. From there, select "clear cache" and then reboot.
4) If the phone STILL won't boot, repeat step 3, but select "factory reset", then reboot. CAUTION: In case you're not clear on what "factory reset" means, you will lose all apps you have installed and all settings you have configured.
If you've flashed a kernel and the phone won't boot, you may have used a non-compatible kernel version. Flashing the same kernel version as your phone's firmware version will allow the phone to boot. After you boot into Recovery mode, you will see the firmware version listed at the top of the screen.
If all else fails, you can always boot into Download Mode by holding the Home + Volume DOWN + Power buttons, then use Odin to flash a Stock Restore image file. This will restore the phone to its factory state. CAUTION: To be clear: all of your apps and settings, and everything on the phone's internal storage will be deleted (but anything on your external SD card will not be affected).
Unbrick Image: If you are unable to get into Download Mode, there is one thing you can try. There was a method developed (I believe) for the Galaxy S3 that also works on the S5.
1) First, you must obtain an Unbrick Image that has been created with the Unbrick Image Creator on a phone with the same version of firmware and bootloader as the one you're trying to restore. Use the forum search function to find the image you'll need (unless someone is willing to provide a permanent repository of unbrick images).
2) Rename that file to "unbrick_IMG.img", and use Win32DiskImager to flash that image file to a "16gb Class 10" MicroSD card.
3) Insert the Unbrick MicroSD card into the phone, and power it off by unplugging it and removing the battery.
4) Re-insert the battery, then boot into download mode by holding the Home + Volume DOWN + Power buttons.
5) Now connect with Odin and flash a factory restore image.
JTAG: If your phone is truly bricked, you have one last possible recourse. There is a hardware tool called a JTAG that may be able to help you. It's a fairly expensive piece of hardware, but some repair places offer a one-time JTAG repair for a modest fee.
ROOTING 4.4.x and 5.x
As of mid-January 2016, root has now been achieved on every firmware version from NCG all the way to PB1.
Root access is simply a configuration within the operating system that allows one write access to protected system files. This is HUGELY powerful, allowing one to modify or delete system apps or alter how they function. If you are not very computer literate, you may want to pass on rooting until you've learned more. If you don't know what you are doing, it's possible to do some damage to your phone's configuration (possibly rendering it unusable to you, at least until you learn how to repair it). It can be dangerous to play outside the boundaries of User Space. Here there be monsters...
Note that although we have root access, the Bootloader is still locked and is extremely likely to remain so indefinitely. The bootloader is booby-trapped with a hardware "qfuse": attempts to alter the bootloader result in a hard-bricked phone, which effectively dissuades developers from messing with it. Fewer and fewer developers care about this phone, anyway, and have moved on to brands that are less hostile to power users.
Root Kitkat 4.4.2 or 4.4.4 (uses TowelRoot after temporarily downgrading kernel to NCG)
Update from rooted 4.4.x to 5.0 and Keep Root
Root Lollipop 5.0 (uses KingRoot)
Busybox: Android is a gutted variant of the Linux operating system, stripped down to only those functions needed to run a smartphone. Busybox adds back in a lot of the linux/unix functions and commands that were removed. You'll need this once you root if you want to be able to do anything really useful.
Custom ROMs
With a rooted phone, it is possible to install a customized version of the operating system, which is known as a "ROM". These range from rooted Stock ROM, mildly to heavily debloated versions of the Stock ROM, to more heavily customized and themed ROMs.
Unfortunately, because the bootloader on the Verizon S5 is locked, it is only possible to choose from a small selection of TouchWiz-based ROMS. Cyanogenmod (and all the various AOSP-based ROMs) require a different kernel: if you try to use a non-TouchWiz based kernel, the locked bootloader will not allow it to boot.
Only install ROMS found in the Verizon Galaxy S5 Android Development section of the forum.
The Verizon "Developer Edition" S5 comes with an unlocked bootloader, so on that device you CAN run non-TouchWiz ROMs.
As of March 2016 an unlock method for one of the two possible bootloaders has been discovered and exploited, essentially allowing you to turn your phone into a Dev Edition. To determine if your model is unlockable, you need to check the eMMC version. Do this by using a file explorer to browse to /sys/block/mmcblk0/device/cid. The CID file will contain a string of characters: if the first two digits are 15, your phone has the Samsung chip that is unlockable. If the first two digits are 11, your phone has the Toshiba chip and is NOT unlockable.
Odexed vs De-Odexed: You will also see in a ROM's description if it is "odexed" or "de-odexed". This is referring to how all of the applications on the phone are packaged.
An ODEXED application is one where parts of it have been "optimized" in a separate file (with the file extension .odex). This makes the application take up a little less storage apace and also load a little more quickly. However, because the parts of the app are packaged separately, it makes it harder to alter that application on-the-fly (such as theming or modifying the way it behaves).
A DEODEXED application is one where this optimization has been undone. This is necessary for theming or other modifications, and the space and speed difference is probably not really noticeable. If you plan to do any theming or on running Xposed framework, you should install the DEODEXED version of your chosen ROM.
The basic procedure for installing a custom ROM:
1) Boot into SafeStrap Recovery
2) Make a NANDroid backup of your current system, saved to the MicroSD card. If something goes wrong, you can easily restore to where you are now.
3) Wipe cache, dalvik cache, and system partitions.
4) Install your chosen ROM (which will be a .zip file)
5) Install any optional modification zips included and compatible with that particular ROM
6) Wipe cache
7) Reboot
jrkruse goes into much more detail for installing Lollipop ROMS here
Always do a full system wipe from SafeStrap before installing a ROM, or you will have many problems with conflicting settings and system files. Wiping first is known as a "clean flash". The only exception is if you are updating to a newer version of the same ROM, in which case it may be successful to do a "dirty flash", where settings files are unlikely to have changed enough to cause conflicts.
Likewise, never restore "system" apps with Titanium Backup or anything else unless you're on exactly the same version of the OS, because this is almost certain to try to configure those system apps in ways they can no longer function. Doing so will introduce strange problems that can be very difficult to troubleshoot.
If something goes catastrophically wrong, you can always get back to a factory state with Odin, root, install SafeStrap, and restore your NANDroid backup (provided you saved it to the external SDcard like I instructed you, rather than wiping it into oblivion with a ROM flash).
Debloating
Once rooted, you can remove a lot of the bloatware from your phone. It is possible to just uninstall or delete unwanted bloatware, but this can cause problems if you unknowingly remove something that was required for something else to work.
The safest option is to use Titanium Backup to "freeze" the undesirable apps. Then run your phone normally for a few days to make sure everything is functional. Once you're sure an app is safe to delete, you can then do so, or you can just leave it frozen. If it turns out you need to re-enable a frozen app, just "defrost" it in Titanium Backup.
Disabling KNOX
If you choose to use a Stock ROM after rooting, you will want to disable a few things: Knox, security update notifications, and the Verizon Over-the-Air updater.
Use Titanium Backup to freeze the following system apps:
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
Security policy updates SPD_v2_1402_4_1 (Security update notification)
SDM 1.0 (Verizon OTA update)
Xposed Framework and Modules
I won't go into a lot of detail here at this point. Just a few notes. I'll probably flesh this out more later and list my favorite modules.
In order for Xposed to function, you must be using a DEODEXED version of your ROM.
Xposed is awesome, and you should look into using it. I've been using the GravityBox module, and it allows me to get most of the little features I've previously enjoyed in custom ROMs.
Xposed installer for Lollipop
The specific Xposed framework you need to use for S5 Lollipop
Xposed bootloop: If you install an incompatible Xposed module, the worst case is a bootloop. You fix that by getting into Safestrap, choosing file explorer, and creating a file called "disabled" in /data/data/de.robv.android.xposed.installer/conf/
Alternately, there's a flashable zip file somewhere that puts the "disabled" file where it needs to be.
Then you reboot, get into Xposed and turn off the offending module. Then use a file explorer to go delete that "disabled" file and reboot.
Awesome thread!! Thank you very much for spending the time and putting this all together!!
Sent from my still locked down SM-G900V ?
Lots of great info in here! I appreciate the time and effort.
Are there any roms beyond 5.0 for verizon? I'm still running 4.4.4 right now. I tried 5.0 and hated some of the changes with sounds settings (Normal/Vibrate/Silent). My understanding is that 5.1.1 replaces these with the older setup. If that's the case I'd love to move to 5.1 but haven't found any ROMs that do 5.1.x except for one in the Unified forum. But the links for that are dead.
RedRamage said:
Lots of great info in here! I appreciate the time and effort.
Are there any roms beyond 5.0 for verizon? I'm still running 4.4.4 right now. I tried 5.0 and hated some of the changes with sounds settings (Normal/Vibrate/Silent). My understanding is that 5.1.1 replaces these with the older setup. If that's the case I'd love to move to 5.1 but haven't found any ROMs that do 5.1.x except for one in the Unified forum. But the links for that are dead.
Click to expand...
Click to collapse
Not to my knowledge. The locked bootloader makes development very difficult. I think we will have to receive a stock 5.1 that functions with our locked bootloader before anybody can develop ROMs based on it.
I still prefer 4.4.4, too. However, if you want to give 5.0 another try, you may be able to use an Xposed module to restore the way you prefer the sound settings to work.
RedRamage said:
Are there any roms beyond 5.0 for verizon? I'm still running 4.4.4 right now. I tried 5.0 and hated some of the changes with sounds settings (Normal/Vibrate/Silent). My understanding is that 5.1.1 replaces these with the older setup. If that's the case I'd love to move to 5.1 but haven't found any ROMs that do 5.1.x except for one in the Unified forum. But the links for that are dead.
Click to expand...
Click to collapse
As of now, we are limited to 5.0. If you give 5.0 another shot, I'd suggest using Wanam Xposed and enabling expandable volume control. I couldn't stand the volume settings of Lollipop until I started using Wanam.
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Thank you, @painiac! Now I have a thread I can link every time someone asks how to do the basics. Having a device specific root/ROM thread makes things much easier.
I'm trying to help a fellow user who's trying to install the Optimal ROM and he keeps getting the OTA update message. I mentioned for him to try to freeze the SDM 1.0 but he said that it's not listed in TB. And to be honest, I don't see it listed anywhere in the MOAR ROM that I'm running. So if someone could point me in the right direction on how to freeze the OTA update. I/he would be greatly appreciated. He's posted the issue on the Optimal thread. Thank you in advance
al50 said:
I'm trying to help a fellow user who's trying to install the Optimal ROM and he keeps getting the OTA update message. I mentioned for him to try to freeze the SDM 1.0 but he said that it's not listed in TB. And to be honest, I don't see it listed anywhere in the MOAR ROM that I'm running. So if someone could point me in the right direction on how to freeze the OTA update. I/he would be greatly appreciated. He's posted the issue on the Optimal thread. Thank you in advance
Click to expand...
Click to collapse
It has been a long time since I've used MOAR, but I'm sure the OTA updater has been removed from it. The name of the app is SDM.apk. You should be able to find it in Titanium, but you can delete it manually if need be.
CVertigo1 said:
It has been a long time since I've used MOAR, but I'm sure the OTA updater has been removed from it. The name of the app is SDM.apk. You should be able to find it in Titanium, but you can delete it manually if need be.
Click to expand...
Click to collapse
Thank you for replying CVerigo1. That's what I was thinking about it may have been removed. We suggested that he wipe 2 timesbefore installing the ROM just in case he had some files lingering around. I'm hoping that will solve his issue. Thanks again and apologize for posting this in Painiac's thread.
Thanks for putting all of this together. I sent in a request for the thread to be stickied since we need an updated "How to" thread.
Dudash said:
Thanks for putting all of this together. I sent in a request for the thread to be stickied since we need an updated "How to" thread.
Click to expand...
Click to collapse
It appears your request has been approved. I appreciate everyone's kind words.
So, say I have a phone that is BOK3 rooted (sweet) and I want to go back to factory unrooted BPB1 (to sell it)... what steps do I follow?
Update (3/8): Found out one solution to going back to stock...
1.) (This Step Is Probably Optional) -- Flash the stock BOK3 Rom using Odin and the PA slot -- This clears the bulk of your custom/rooted files off the phone
2.) Check for system update, allow it to install (should be BPB1)
3.) Boot into recovery mode and clear the phone (WARNING: You will lose all data on your phone)
--- Turn the Galaxy S5 off.
--- Press and hold the Volume up button, the Home button, and the Power button together until you see the Android on screen.
--- Use Volume down to highlight the wipe data/factory reset option and press the Power button to select it.
--- Use Volume down again to highlight Yes – delete all user data and press Power to select it.
--- Wait until you see the reboot system now option and then use the Power button to select it.
--- When the S5 restarts it should be completely wiped and ready to set up again.
Thanks,
Wook
rxwookie said:
So, say I have a phone that is BOK3 rooted (sweet) and I want to go back to factory unrooted BPB1 (to sell it)... what steps do I follow?
Update (3/8): Found out one solution to going back to stock...
1.) (This Step Is Probably Optional) -- Flash the stock BOK3 Rom using Odin and the PA slot -- This clears the bulk of your custom/rooted files off the phone
2.) Check for system update, allow it to install (should be BPB1)
3.) Boot into recovery mode and clear the phone (WARNING: You will lose all data on your phone)
--- Turn the Galaxy S5 off.
--- Press and hold the Volume up button, the Home button, and the Power button together until you see the Android on screen.
--- Use Volume down to highlight the wipe data/factory reset option and press the Power button to select it.
--- Use Volume down again to highlight Yes – delete all user data and press Power to select it.
--- Wait until you see the reboot system now option and then use the Power button to select it.
--- When the S5 restarts it should be completely wiped and ready to set up again.
Thanks,
Wook
Click to expand...
Click to collapse
That works, but it has some extra steps. Just flash the PB1 factory image with Odin: there's no real reason to do BOK3 and then wait for an update to install. Flashing a factory image should have cleared all of your user data as well, but you can initiate a factory reset to be sure if you're selling it.
painiac said:
That works, but it has some extra steps. Just flash the PB1 factory image with Odin: there's no real reason to do BOK3 and then wait for an update to install. Flashing a factory image should have cleared all of your user data as well, but you can initiate a factory reset to be sure if you're selling it.
Click to expand...
Click to collapse
Thank you for clarifying that. I was afraid to just flash the PBP1 Rom without knowing how it would act.
When I flashed the stock OK3 Rom it took the OTA update just fine. Interestingly, flashing the stock Rom didn't clear anything off the phone, so a factory reset had to be performed in my case.
In all honesty, I love the phone overall... But I'm just really sick of the locked bootloader.
Thank you for the comprehensive thread (and response to my post above).
Thanks,
Wook
rxwookie said:
Thank you for clarifying that. I was afraid to just flash the PBP1 Rom without knowing how it would act.
When I flashed the stock OK3 Rom it took the OTA update just fine. Interestingly, flashing the stock Rom didn't clear anything off the phone, so a factory reset had to be performed in my case.
In all honesty, I love the phone overall... But I'm just really sick of the locked bootloader.
Thank you for the comprehensive thread (and response to my post above).
Thanks,
Wook
Click to expand...
Click to collapse
You're very welcome. I can't blame you... my next phone likely won't be a Samsung.
Thank you for putting all of this together. Does http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909 change any of the information regarding custom ROMs?
jokajak said:
Thank you for putting all of this together. Does http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909 change any of the information regarding custom ROMs?
Click to expand...
Click to collapse
It does, IF you have the specific chipset that can be unlocked. Thanks for mentioning that, I should add it to the guide.
This is a wonderful guide, thank you for putting it up. I'm a software engineer, but I rarely work with android code and have been using iPhones for awhile.
I used to root old droid phones back in the days of the Droid X2 and Droid 3, but I haven't done it in awhile. My girlfriend has an S5 that is causing her lots of problems, specifically terrible battery and no more space for adding apps because of the bloatware. When I used the older motorola droids, there was a process termed "sbf-ing" that would allow me to downgrade my phone to a different version. Is there any way I can do this with an s5 ? She has an S5 running 5.1.1, and I'm curious if I can bring it down to 5.0 or 4.xx to work with some of these roms.
Thanks!
Bought my phone used. LGE Nexus 5 Hammerhead - Android Lollipop 5.0.1
System Update comes up at a certain point. After downloading, installing and restarting:
Team Win TWRP v 2.3.0.8 (? not 100% on the version). Had a "Welcome to the Control Room" moment. Didn't know that was down here.
Ran Root Checker Basic to "verify root access and installation on this device..."
Came back with "Root access is not properly installed on this device." No ****?
Obviously, previous owner rooted phone and installed this. Thing is, the operating system is vanilla as far as I can tell. Certainly nothing to denote custom functioning or layout. And it's clunky as a muh. Looking for those sweet sweet upgrades...
My question is this: given current state of the phone (rooted), what our my best options on increasing functionality and efficiency of my phone?
In other words, should I try and update the 200+MB file sent by Google, or should I ditch that path and max out what is now pretty old tech, with a solid, tried and true, custom OS that XDA heads trust? Also, where might I find the info on DLing and installing said OS?
Also, any stray observations welcome.
Thanks
It depends. There should be a guide for doing a full restore to stock in the guides sub forum for the Nexus 5 . If you want, I would recommend a move to a marshmallow ROM for beginners.
First you must install an updated recovery. Follow instructions before continuing. https://www.google.com/url?sa=t&sou...nTwrk1RLdbbm4DHLA&sig2=868XID8flOqKUZlzjJUbfw will install a CAF recovery. You can only use a CAF ROM on this recovery.
Turn download updates radio s and baseband. https://drive.google.com/file/d/0Bxeul4rF_fZDTWpHMU5tTWV6ZGs/view is the latest for CAF
Then Download ROM and Gapps
https://www.google.com/url?sa=t&sou...tZ3F-YmW0i5TK_Dxw&sig2=mdmMDS0FRJByUWdv6bAchw is marshmallow (6.0)
https://www.google.com/url?sa=t&sou...IuqwdCU3C_N0Bfhmw&sig2=eG7alOlJQ9qXLocytcz8Aw is nougat (7.1)
Install instructions
1 power off phone
2 boot into recovery (hold power and volume down button to enter bootloader, use volume button to select recovery, , press power to select entry)
3 once in twrp press wipe, and follow on-screen prompt
4 now press back button until you reach main menu.
5 click install
6 install updates radio and bootloader from download folder
7 install ROM
8 install Gapps
9 wipe cache
10 reboot system.
Hope this helps. If you have any more questions, PM me.
My personal advice would be to return to full stock 1st and then start playing around afterwards.
Assuming you go that route all the instructions on how to do so are provided directly from google :
https://developers.google.com/android/images
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