Database Users

[Q] Unable to Update phone because of bootloader.

I have a GS4 on version 4.3 rooted and I have a custom bootloader, clockwork. I've recently tried to ota update but it makes my phone reboot into recovery mode asking if I want to install an unknown package, paraphrasing here. Last time I accepted this install and softbricked my phone so I'd like to figure out the problem so I can fix it and update to KitKat. If I have to flash the original recovery or Rom I'd very much appreciate links on how to do so given I haven't done either in a year or so. Thanks in advance.

The problem is you cannot take an OTA unless you are 100% bone stock.
This problem and the solutions have been discussed many many times. Please search and you will find everything you need.

OTA update when rooted D855

Hey, I have a LG D855, and I'm rooted on A6NL D855 V10G. My phone suggested to OTA update to V10I. Now I want to know if it's safe to do so. And if that's the case, what would happen to my root? I'd actually be glad to be rid of my root since I think it's lagging my device. So, what exactly would happen if I updated? Anybody with experience?

Would think although showing an ota when you download it it won't install as it will detect your root. In order to update you will have to return to unrooted state. A search will show a couple of threads instructing how to.

From what I understand, as long as you haven't made any changes within the system folder or installed a custom recovery, the OTA should install just fine. Worst case is if anything has been changed, it will tell you and it won't install. But yes, you will lose root once it is installed.

root and ota should be ok.
but be very careful if your g3 is bumped!! if you had installed bump! on your device, an ota update fails and the reboot always ended in the recovery. i tried almost erverything - no way out. i had no chance to reboot into the system!!
only flashing back to stock had fixed the problem (incl. loosing all personal data).
kd

Mendeltje1313 said:
Hey, I have a LG D855, and I'm rooted on A6NL D855 V10G. My phone suggested to OTA update to V10I. Now I want to know if it's safe to do so. And if that's the case, what would happen to my root? I'd actually be glad to be rid of my root since I think it's lagging my device. So, what exactly would happen if I updated? Anybody with experience?
Click to expand...
Click to collapse
When u are rooted, it will download the new update (ota), but it will give a error when it installs. You have to update via pc.
Sent from my LG-D855 using XDA Free mobile app

Just had this happen to me on LG G3 for AT&T
Was rooted, got prompted to install the update, I kept declining until it stopped asking.
Then my phone died, after plugging it in and restarting my phone, it instantly jumped into the update window with no other options.
It updated automatically, and it didn't stop or error because of my root. I'm on 4.2.2 now, most up-to-date version on AT&T.
To make it clear: I'm rooted with TowelRoot, NOT with Bump!

Strange OTA update from LRX22C to LMY47O

I've tried to search for this issue in the forum but it seems that nobody ever encountered it.
I'm running the rooted stock ROM 5.1.1 on a Nexus 4 (LMY47V) that I've updated since the initial version using always OTA downloads. My provider is T-Mobile USA.
Recently, I keep receiving a notification for a system update that looks a bit weird to me.
The update should be from 5.0.1 (LRX22C) to 5.1.0 (LMY47O), but I'm wondering why I would get it if I'm already running a newer version.
The full path of the download file [1] has a hash that doesn't match any of the original images, but I don't know if this is necessarily a bad thing (since it's just an update and not a complete install).
Initially I tried to update because I didn't know it was the wrong update, but (lucklily?) it didn't succeed so I investigated a bit. I had a few issues in the past with other OTA's failing because the system was rooted, but I managed to decompress and manually install the single components. Although, I don't think I want to do it in this case, because of the version mismatch.
Does anybody has a clue about what's going on?
Also, since I suspect that this update is useless, is there a way to silence or delete this update without installing it?
Thanks in advance.
[1] /storage/emulated/0/Download/e6789b4e57176ed28cd8b24747c134366b3908fc.signed-occam-LMY47O-from-LRX22C.e6789b4e.zip

Software: Modified... Not rooted... want to be able to get updates

I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
My phones info;
Software status: Modified
Android Security patch level: May 1 2016
Baseband version: M8992_1253331 .29.01.88.02R SUPER_NA
Kernal Version: 3.10.84-perf-g329ac5f
[email protected] #1
Thu Apr 21 00:11:23 CDT 2016
System Version: 24.221.4.clark_retus.retus.en.US.retus
Build Number: MPHS24.49-18-4
The pending update: New version:24.221.8.en.US
Thank you.

u need to flash official factory image inorder to get the updates
i hardly recommend you to use fastboot and install stock firmware from this site
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick...
install the latest firmware and then check for updates
if u have any queries then go through this.... make sure that u don't mess up
https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

Cjet said:
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
Click to expand...
Click to collapse
If I understand your post correctly, and the COMPLETE firmware image was flashed, then you should have no issues taking an OTA update... the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt.
Try this, before you accept and download the update, boot into stock recovery and wipe cache. Or better yet, do a full factory reset and accept the update and apply it, then let it boot fully, do another factory reset and then set it up clean.
I don't know why this happens... it just seems like a few every update won't take it no matter what we do, and for we do not have the latest full factory image yet so there isn't much we can do to find another way.

Thank you both for your reply. However, I am still not clear on something.... there seems to be confusing/conflicting advice regarding the Software "Modified" status and it's role in accepting updates.
1. "if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick..."
2. " the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt."....... If the Software status says "modified" doesn't that mean that the system is indeed modified, and that trying to load the OTA in this state will result in a bootloop? .

u neee to flash official firmware.... the only way to remove modified and change it to official....
it actually doesn't matter that if bootloader is unlock u can install the updates...... i was on may patch and i also wanted to change the software status from modified to official in order to get sept patch... but in moto firmware center the latest was feb 2016.... so i had to downgrade... i tried and it worked... then i was eligible for ota and yes im on sept patch
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/

Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk

Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....

Prazaar said:
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
I disagree... it CAN go back to Official, I had several ROMs on my device, then flashed stock image and somehow mine went back to Official. Was mine a fluke? I don't know, but it is clearly Official now. Note the picture clearly shows the bootloader was unlocked (Status 2) and I had at least dozen different ROMs flashed over time before going back to stock using the May 2016 security image and then successfully OTAing up to October security update.
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.

I know what you mean. My Software status is with LineageOS "official" i can flash every rom an the status stuck in official.
Factory img is no warranty for official status but also makes no difference for ota
Getapatalkt vom meinem Moto X Style

thebaconbox said:
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Click to expand...
Click to collapse
Because I am new to all of this and don't know anything about custom Roms. All I want to do is get this thing back to stock.

[/QUOTE
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.[/QUOTE]
Wow, thanks everyone for the suggestions and patience!
OK, so the software status does not affect OTA update installation. Software status being modified does not necessarily mean that the SYSTEM is modified. Yet if the SYSTEM is modified then taking the OTA update will cause a softbrick.
How can I tell if my SYSTEM is modified before deciding on taking the OTA update?
I have had the official Motorola firmware flashed/reinstalled previously by friend's son, and that didn't take the OTA update. It caused soft brick (No Command error bootloop)
I then went to the Motorola site myself, downloaded the firmware and flashed/reinstalled it. This is where I am currently, trying to decide if I should take the update or put it off until I have a couple of hours free to troubleshoot in case the OTA softbricks this thing again (it takes me much, much longer to figure this stuff out than it does for you guys. )
And if that does soft brick it again, then I am not sure what I am doing wrong with the flashing. So, is there any way for me to check to see if the SYSTEM is modified before I try the update.? Thank you!

Sagar_1401 said:
u neee to flash official firmware.... the only way to remove modified and change it to official....QUOTE
This was done twice and still says modified
Click to expand...
Click to collapse

Status modified will change to official after an OTA update.
Sent from my XT1572 using Tapatalk

Anyone? No one knows if there is any way for me to check to see if the SYSTEM is modified before I try the update.?

Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style

Prazaar said:
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Click to expand...
Click to collapse
I don't understand what you are saying. I cannot see "what" if it is modified? Edited - removed earlier rant.
(Sorry)
SOLVED.....
Today I backed everything up, bit my lip and hit "install update". It did update the phone and it did change the software status to "Official". I did this with the bootloader unlocked, and it worked . It does say Status Code 3, and the bootloader unlocked warning screen on startup appears, both of these I am guessing is normal. Everything seems good.

Need Instructions to avoid almost bricking again

Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.

CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)

Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.

CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware

Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...

Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling

LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900