I have the LTE version on Boost, its already on 5.1 but there is obviously an update for it, I get the prompt to download update but when I go to install it, the install fails. The notification gets annoying b/c it seems to come up while i'm trying to use the phone. How can I force the update? Or disable the notification for the update entirely....I like the phone as it is right now
is it fully stock ?
once you tinker with it you may lose ability to get OTA updates i think right.
and that update could be a "Stagefright" update.
update failure is due to modified recovery/system
Dvdxploitr said:
I have the LTE version on Boost, its already on 5.1 but there is obviously an update for it, I get the prompt to download update but when I go to install it, the install fails. The notification gets annoying b/c it seems to come up while i'm trying to use the phone. How can I force the update? Or disable the notification for the update entirely....I like the phone as it is right now
Click to expand...
Click to collapse
now to verify if ur system is modified then do one thing, reboot into ur bootloader and there will be displayed some text in yellow that device connected via USB or something like that above this text is : system status: official/modified(depending upon ur device ). And my guess here is that ur system status is modified and hence u might not recieve updates. Don't worry bro! it doesnt matter, anyways we wont recieve updates for android v6.0. As for 5.1 use any custom rom like CM12.1 or PACMAN.
I bought the phone off eBay and its already rooted, so obviously it has been modified, i clicked on "Disable" on the moto udpate thing and it seems to not be bothering me with the updates. I think its crazy that it downloads the updates and then tells me to install it, but it won't actually install....i'll just leave it as it is for right now. The phone is only used for PerkTV apps, so its not even used for service
i searched this sub-forum for update failed and pretty much every single topic showed up LOL
it seems i too am getting this update prompt too.
i tried letting it update and it always fails then eventually i get into a loop.
my phone keeps restarting to recovery automatically.
but it stopped when i re-flashed my Squid kernel.
But i do want to install the update though.. the update details said it was a stagefright fix.
i figured out what was going on by reading the logs.
the update for me downloads and tries to install.. it asks you to restart to apply the update.
when it restarts it fails with an error mentioning "Keys" and the versions found / needed.
i am thinking i *might be able to adb side load the update with TWRP but i have not used that before yet.
i also think forcing the update may be a bad idea.. i don't want to brick it LOL
so i don't know..
edit:
I guess it's common for these to fail.
something set test Keys on my phone prob SuperSU
It got detected and then the update failed.
i found some side loading info and possible TWRP flashable version info for another phone.
But they say flash to a stock firmware and i have done that a lot lately and can't be bothered right now.
So it seems if i want the OTA update installed it's gonna be some work/waiting.
Going to keep an eye out for a TWRP ready flashable.zip though
I have the same issue as xpmule, when phone restarts to install the update it boots into recovery (TWRP) so the update fails. I restored a backup and now I am waiting for an update that I can flash using TWRP, stagefright is serious business.
I have an euro XT1524, rooted, Stock 5.1 US ROM flashed and squid kernel r10f.
I have a Canadian XT1527, rooted, Stock 5.1 US ROM flashed and squid kernel r10f.
And i still have not had much time to research more but i think the problem lies
with the singing keys..
i can see WHY it failed when you open the TWRP log (middle button)
my log said it failed to execute the update script because of bad keys..
It mentions i have test/keys and it expects to see Retail/Keys
When i looked on the web i see that could be because of SuperSU (being signed with TestKeys)
Or i thought maybe even Squids Kernel i am running.
If anyone seen a topic on this or what ever then let us know
i will prob keep poking around and see what i can do.
Problem is i am being VERY cautious i don't want to brick my phone.
Official OTAs tend not to flash on rooted or modified devices. Specifically with custom recoveries. The zips script verifies partitions and if something doesn't match it'll fail. Usually to get the ota you'll have to go back to completely stock unrooted firmware with the stock recovery.
After growing tired of seeing the update popup each time the phone decided to switch networks I did this:
Full TWRP Backup (just in case)
Flashed XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip from here
I flashed back TWRP (well, just replaced the recovery.img from the stock rom, did the same with the logo)
Restored data backup
Reinstalled squid's kernel
Reinstalled SuperSU
Had some minor quirks, like losing the swiftkey language (just enter the config and download again, didn't lose predictions) and having to open apps that needed root and reapply SuperSU permissions, but all of those sound normal. Everything seems to be working correctly, there's no annoying popup nor Stagefright vulnerability.
{
"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"
}
ya i was thinking of doing similar pretty quick..
was waiting to hear back from people if that included stage fright fixes.
people are slow to reply here lol
thanks for the info.. i was not sure what parts of the back up i was going to restore.
also i use Swift Keyboard to.. i just wish the Lollipop UI had the Holo Theme or some dark theme.
but ya me too that prompt was getting a bit irritating lol
I have a virgin mobile xt1526 running 5.0.2 rooted but i need to update to 5.1, if i flash the ret_us update will it correctly identify my phone as VM? Boost users, did android correctly identify your phone as boost when you flashed the ret_us 5.1 update?
Sent from my XT1526 using Tapatalk
Sands207 said:
I have a virgin mobile xt1526 running 5.0.2 rooted but i need to update to 5.1, if i flash the ret_us update will it correctly identify my phone as VM? Boost users, did android correctly identify your phone as boost when you flashed the ret_us 5.1 update?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
The update is for people on 5.1 already.
There is a different update for the 5.0.2 versions.
The retail update will look for the right version to update or it will fail.
And it is VERY picky at what it expects to see too !
Your going to need the newest full firmware package (easiest way)
that is a whole new can of worms to open LOL
@direi
i did the same thing now..
i seem to be up running ok and not vulnerable using the same Stage Fright Test tool as you.
Although i had to let it fire up once after flashing then turn it off so i could get the partition restored.
Reinstalled squid kernel with twrp and problem solved. Then froze motorolaOTA. Working fine so far.
Related
Hi All,
Some background info:
I have a P769BK, rooted on P76910e running 4.0.4.
The phone has been rooted and I have previously overclocked it through the Basic L9 Overclocking instruction.
I had also frozen some of the t-mobile bloatware using the running the T-mobile P769 bloatware disable script.
...so when I heard about the P769 jellybean OTA upgrade, I tried to get the OTA upgrade and even tried the forced checkin (dial *#*#CHECKIN#*#*) but I keep getting the same 2 results:
1) phone says it is up to date
2) phone downloads the P76910g update but I get that awesome dead Andriod icon after it reboots to install
{
"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"
}
I've tried to do the Hard Reset thinking that should revert everything to stock but I get the same results.
Any suggestions?
projectedv said:
Hi All,
Some background info:
I have a P769BK, rooted on P76910e running 4.0.4.
The phone has been rooted and I have previously overclocked it through the Basic L9 Overclocking instruction.
I had also frozen some of the t-mobile bloatware using the running the T-mobile P769 bloatware disable script.
...so when I heard about the P769 jellybean OTA upgrade, I tried to get the OTA upgrade and even tried the forced checkin (dial *#*#CHECKIN#*#*) but I keep getting the same 2 results:
1) phone says it is up to date
2) phone downloads the P76910g update but I get that awesome dead Andriod icon after it reboots to install
I've tried to do the Hard Reset thinking that should revert everything to stock but I get the same results.
Any suggestions?
Click to expand...
Click to collapse
The update is not ready yet. That is why you have not received it.
Please do not post new threads about stuff that already has a thread: http://forum.xda-developers.com/showthread.php?t=2246037
kevev said:
The update is not ready yet. That is why you have not received it.
Please do not post new threads about stuff that already has a thread: http://forum.xda-developers.com/showthread.php?t=2246037
Click to expand...
Click to collapse
well i'm posting about why a hard reset would still prevent me from upgrading to P76910g, which according to t-mobile is the correct up-to-date software pending JB's P76920d.
the other threads about flashing roms and such seem to say that a hard reset would fix everything back to square one, which isn't the case for me.
projectedv said:
well i'm posting about why a hard reset would still prevent me from upgrading to P76910g, which according to t-mobile is the correct up-to-date software pending JB's P76920d.
the other threads about flashing roms and such seem to say that a hard reset would fix everything back to square one, which isn't the case for me.
Click to expand...
Click to collapse
I am in the same boat. Can't update to 10g. Hard reset doesn't help. I only rooted mine no overclocking or custom recovery. I tried unrooting but that didn't help.
I had exact same problem and the only thing that worked for me was flashing the stock 10g update. It was a hassle and I loss root but it will work.
Got the JB update yesterday and loving it so far!
syckman said:
I had exact same problem and the only thing that worked for me was flashing the stock 10g update. It was a hassle and I loss root but it will work.
Got the JB update yesterday and loving it so far!
Click to expand...
Click to collapse
Can you link where you got stock 10g from? Thanks
Sent from my LG-P769 using xda app-developers app
Testman08 said:
Can you link where you got stock 10g from? Thanks
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yes, file and all directions are in thread titled: [GUIDE] FLASH Any LG Factory ROM (kdz) WITH OFFLINE FIX METHOD [UNBRICK]
I'm a newb, so sorry, cannot link
To get the update and to install it
to get the update go to settings click on 2G networks only and the go back to apps got to all scroll down to google services framework force stop and then clear data. then go to about phone and search for the update you should recieve it. if you dont try it once or twice. to install the update you have to have all the stock bloatware and the original recovery image. if you dont you wont be able to install it will fail. if you dont have a stock phone you will have to either flash with offline kdz or find each individual file to download from app store here is the link for kdz flashinghttp://forum.xda-developers.com/showthread.php?t=2085344
mderuelle said:
to get the update go to settings click on 2G networks only and the go back to apps got to all scroll down to google services framework force stop and then clear data. then go to about phone and search for the update you should recieve it. if you dont try it once or twice. to install the update you have to have all the stock bloatware and the original recovery image. if you dont you wont be able to install it will fail. if you dont have a stock phone you will have to either flash with offline kdz or find each individual file to download from app store here is the link for kdz flashinghttp://forum.xda-developers.com/showthread.php?t=2085344
Click to expand...
Click to collapse
Thanks but that didn't work, either. I just don't understand this. I guess we all just need to wait it out.
EDIT: Well, I guess I was right. Wait it out. No sooner did I post this then my phone gave me the update notice. Maybe there's something to the 2G thing. Or, just keep trying. Thanks.
syckman said:
Yes, file and all directions are in thread titled: [GUIDE] FLASH Any LG Factory ROM (kdz) WITH OFFLINE FIX METHOD [UNBRICK]
I'm a newb, so sorry, cannot link
Click to expand...
Click to collapse
I tried following this guide but for some reason I can't install B2CAppSetup. Little window pops up for 2 seconds and then it closes and nothing happens. I tried different compatibility modes but no avail. Any suggestions ?.
Nvm , I didnt put shttp in root. that was the problem
I just received the prompt to do a System Update, see the image below:
{
"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"
}
Does anyone have any idea what it is? Lollipop??
If anyone has installed it, does it break root?
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Interested in knowing if this breaks root as well. Til then, no install for me.
No idea. Got the update notification just now but since I'm rooted and on a custom ROM, I don't think I should flash it.
If you're rooted, and unlocked, I would avoid this update like the plague. Give the devs time to look at it.
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
ryman222 said:
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I suggest never taking an OTA update if you aren't 100% stock.. and def never do one if on TWRP.
Fix being stuck in twrp - http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
General info on taking OTA - http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'd assume this new OTA update today will block ioroot and stump from working. Whether a previously rooted phone will retain root through the OTA is a gamble.. may or may not work. Some have reported already that root has stuck thru the OTA. So might luck out with this one. For those who are not rooted and take the OTA update.. gaining root again may not be so easy (without downgrading).
Without seeing the bootloader.. can't say if Bump is blocked. Most likely not yet though.
Dobrah said:
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
Click to expand...
Click to collapse
Yeahh if we could get that, that'd be great. I don't wanna have to deal with breaking root/unlocked bootloader.
What I did when it asked for a time to update was just press the home button. Then it went into a notification saying an update is available. I think that'll keep it at bay.
Dobrah said:
Just got the same message. It looks forced, you cant get rid of the message without adding a time to postpone until. I did 10am tomorrow, hoping it wont auto-update at that time and will bring the prompt back so i can postpone again. If anyone knows what apps to disable so that this cant happen that info would be great right now
Click to expand...
Click to collapse
If you just press the back button itll stay in your notifications, but it wont force you to do anything. Notice the blue checkmark.
Guys come on updates should never be taken period rooted. Sooo wait few days until there is time to examen and provide the community with info
dabug123 said:
Guys come on updates should never be taken period rooted. Sooo wait few days until there is time to examen and provide the community with info
Click to expand...
Click to collapse
+1 lol...
Guys just freeze system update with titanium backup...
Lollipop? On Verizon? Hilarious.
I took the update. I'm not an expert but it looks like it's just an update from software version B to C. It puts a camera shortcut on the lock screen, which isn't really necessary given the back button shortcut. Still missing the rom I had on my Galaxy Nexus, which was more current than this. Love my phone, hate having outdated Android.
Root does not appear to be affected. I am not a dev, just a rooted phone owner so take that for what it's worth.
To Block OTA's visit this thread:
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-disable-ota-downloads-verizon-t2914735
I caught wind of this on reddit before the update showed up and had a feeling my IORoot/Bump unlock setup wouldn't agree with this OTA. I used TiBu to freeze "System updates 1_13_10_0" and made a nandroid backup just in case. All good so far. Several redditors with custom recovery softbricked when they tried to install it, so this seems like the way to go for now.
ryman222 said:
I installed it and now I'm stuck in recovery (TWRP). Can't figure out how to boot back into system no matter what I do. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I just accidentally installed it and the same thing happened to me. This got me out of it:
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
I noticed this sitting there today and was wondering about it before i proceeded. I never use WiFi so it won't download so for now I am safe.
I just don't get it..Blow away!
Anyone know where the update is stored once downloaded? I'm assuming it's somewhere in the system folder, but not sure where to look.
I'm not sure if this is the right section, but has anyone else received the 5.0.2 update? I got mine about half an hour ago, but I can't find a changelog. These are the changes I've noticed so far:
It's somewhat faster
Apps no longer fail to launch (I'd try to open them before, but they would close immediately, and I'd have to dim the screen before trying to open the app again)
By the way, does "sunlight mode" do anything at all?
Screenshots:
{
"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"
}
I just got this, I haven't loaded it yet, I have Gohma loaded. It will not let me swipe the notification away, Is installing my only option because that kind of messes up getting any other notification.
Just got this but cant find anything new. Sunlight mode was already available via lollipop update. Never used it but i assume if you use low brightness levels a quick swipe will make it brighter and vice versa rather than manually altering the brightness. Not an issue for me as i used mini launcher but they can't assume everyone does
http://www.talkandroid.com/237608-a...o-the-samsung-gear-live-and-the-lg-g-watch-r/
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
I don't suppose any of you guys have the system image for this do you? I'm itching to get my hands on this, but my watch is saying that 5.0.1 is up to date.
Apoplectic1 said:
I don't suppose any of you guys have the system image for this do you? I'm itching to get my hands on this, but my watch is saying that 5.0.1 is up to date.
Click to expand...
Click to collapse
Don't feel bad mine too I'll probably still be on 5.01 when everyone else is on 5.1 update in mar.
dligon said:
Don't feel bad mine too I'll probably still be on 5.01 when everyone else is on 5.1 update in mar.
Click to expand...
Click to collapse
I'm just hoping someone can catch the OTA files and upload them onto here, sort of like this:
http://forum.xda-developers.com/showthread.php?t=2796326
Apoplectic1 said:
I'm just hoping someone can catch the OTA files and upload them onto here, sort of like this:
http://forum.xda-developers.com/showthread.php?t=2796326
Click to expand...
Click to collapse
Here it is my update.zip from the 5.0.2 OTA inside the /cache partition:
prototovsky said:
Here it is my update.zip from the 5.0.2 OTA inside the /cache partition:
Click to expand...
Click to collapse
Thanks man! Does one just flash it in a custom recovery, or do you have to sideload it?
Apoplectic1 said:
Thanks man! Does one just flash it in a custom recovery, or do you have to sideload it?
Click to expand...
Click to collapse
It does not work by installing OTA with TWRP or flashing directly. I´ve tried to upload it with adb sideload and the original recovery, but it says "Error: protocol fault (no status), because I need adb 1.0.32 version.
I´ve installed also the new version, but now it says "unexpected contents on the update.zip"...
prototovsky said:
It does not work by installing OTA with TWRP or flashing directly. I´ve tried to upload it with adb sideload and the original recovery, but it says "Error: protocol fault (no status), because I need adb 1.0.32 version.
I´ve installed also the new version, but now it says "unexpected contents on the update.zip"...
Click to expand...
Click to collapse
Do you have the Gohma ROM or Arter Kernel installed? Have you tried flashing a stock boot image from the LG G Watch Toolkit before flashing the update?
I'd fiddle around with it myself, but I keep my dock at work during the week.
Apoplectic1 said:
Do you have the Gohma ROM or Arter Kernel installed? Have you tried flashing a stock boot image from the LG G Watch Toolkit before flashing the update?
I'd fiddle around with it myself, but I keep my dock at work during the week.
Click to expand...
Click to collapse
No, I've stock rom with root and TWRP recovery. A user says me that the OTA doesn't work because root overwrites this two files: install-recovery.sh and recovery-from-boot
prototovsky said:
No, I've stock rom with root and TWRP recovery. A user says me that the OTA doesn't work because root overwrites this two files: install-recovery.sh and recovery-from-boot
Click to expand...
Click to collapse
Do you know the path for those two files? We may luck out and the root process may have renamed them install-recovery.bak and recovery-from-boot.bak before writing the new files.
Apoplectic1 said:
Do you know the path for those two files? We may luck out and the root process may have renamed them install-recovery.bak and recovery-from-boot.bak before writing the new files.
Click to expand...
Click to collapse
No, but I'll try some things ...
I just tried to flash it using TWRP after completely wiping everything but internal storage, thinking it might need a clean flash, but it gave me an error saying that it was unable to flash due to an error in executing the updater binary.
I'm going to flash the stock recovery on it, wipe the data and caches and see if adb sideloading it is any more effective.
EDIT: It isn't.
Im trying to manually push this update to my watch as well, has anyone figured out any solutions?
I tried flashing update-LWX48P5.0.1-to-LWX49K5.0.2.zip from http://rootjunkysdl.com/?device=LG G Watch&folder=OTA but it errors when I try through TWRP. I went back to stock but I do have an unlocked bootloader, I will try relocking and trying then.
Okay so thats weird, im on 5.0.1 but when i try and flash 5.0.2 from TWRP is errors saying that the device "lge/cm_dory/dory:4.4.2/KVT49L/567135e166:eng/test-keys"
how get it to read as 5.0.1 which I am on?
edit:
Soo, I wound up on 5.0.2 while trying to fix some of the random flashes I was trying to update. I wound up erasing my system.img and it was only booting to recovery, so I did the "back to stock" option from rootjunkys toolkit and it reflashed boot/system etc, and when I booted up to turn dev options back on it looks like it put 5.0.2 back on. So that fixed that
Bugs after LWX49K update
Since my watch was updated I cannot open any app on phone using my watch. Moreover - several watchfaces like those of Smartwatch Bureaux do not sync anymore. I own LG G3 and use Chupachups ROM v.4.2 V20h.
Can anyone solve that problem?
Hey guys!
Since it seems some of you are a bit confused about all this: Just use THIS tool here (LG G Watch Restore Tool, make sure you use version 9.5), go into fastboot mode (rebooting, when LG logo appears swipe from left upper to lower right corner) over USB and choose the option "6 Restore your G watch to stock".
Voila! Now you're on 5.0.2 with less effort than OTA updating
I discovered this by accident actually. I tried to restore stock so I can OTA update to 5.0.2, then I saw it's a pre-rooted system.img (because root overwrites OTA critical things so it fails) and already suspected it'd be the newest one
danr said:
Since my watch was updated I cannot open any app on phone using my watch. Moreover - several watchfaces like those of Smartwatch Bureaux do not sync anymore. I own LG G3 and use Chupachups ROM v.4.2 V20h.
Can anyone solve that problem?
Click to expand...
Click to collapse
I was getting a lot of bugs also, but I'm not sure if it is watchmaker or update. Super slow now and notifications are random. I'm uninstalling watchmaker first to check.
going back to stock cause fricking anoying notification...
and some one made a kernel for 5.0.2. a new guy
Today, I got this new System Alert showing that there's a new DELL System Update available...
{
"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"
}
Since the 7840 has been wide open for Stagefright attacks, I decided to apply this update asap.
OTA download worked smoothly, the initiated reboot sequence does take a bit longer (as advertised), then the system update cycle starts, the Android Toolbox Droid appears - and then breaks down with the usual red excamation mark protruding from its metal body, accompanied by a nondescript "Error"-message....
Only thing I can do then is to do a hard power-off (10 seconds power button-method) and then start the thing up again....
Then the Dell/Intel bootup sequence begins and after a thorough startup period, I'm back at where I started from - no harm done to the system, but no update either.... and the Dell System icon again displays the "new update available"...
Was wondering if any of you had the same problem/experience? And if so, did you find a workaround?
I had the same problem as you. I thought it was just me. Was rooted and the OTA didn't work. Then I unrooted, still same result.
Mine downloads, seems to install, reboots and when back in Lollipop, the update is proposed again.
thebreezer said:
Mine downloads, seems to install, reboots and when back in Lollipop, the update is proposed again.
Click to expand...
Click to collapse
I just got my tablet off eBay and today I got the update message. 3 times it downloaded and nothing happened. A fourth download triggered by checking for system updates via About menu went smoothly (if you consider 30 mins for a 1.8gb download smooth) and it installed correctly. The android version is now 5.1 instead of 5.0.1.
We are not talking about the 5.1 update.
Worked fine on my unrooted tablet, although it seems to have installed a bunch of rubbish such as Evernote, Camcard Free, Google Keyboard (with Pinny and Indic languages, huh?), etc, etc, etc.
if we could get the update.zip, it would most likely be possible to flash it via custom recovery. But after downloading, the file is moved from /sdcard/update.zip to somewhere else just before you can copy it to any other location. So if someone managed to keep the file, i'd be happy if it would be shared here.
I have it, will upload when I get home. The file is saved in data/data/dell ota update *or something similar under data/data.* I copied it to my sd before rebooting.
Sent from my LGLS990 using XDA Free mobile app
Here is the zip file. https://drive.google.com/file/d/0B8MfsJT1QP9NY0ZXblJyLWt0Wnc/view?usp=docslist_api Mine is only ~230mb and I have not attempted to flash it so don't blame me if it doesn't turn our like you hope.
Well it was 5.0.1 before and the Stagefright fix brought it to 5.1.
awesome, thanks. I'll try it out today in the evening and report back. Current plan is go install old 5.0 boot-img, launch tethered TWRP, install the fix and patch 5.1 boot-img back. It's about time to get permanent recovery for this shiny piece....
same for me
---------- Post added at 02:52 PM ---------- Previous post was at 02:09 PM ----------
toxic_garden said:
awesome, thanks. I'll try it out today in the evening and report back. Current plan is go install old 5.0 boot-img, launch tethered TWRP, install the fix and patch 5.1 boot-img back. It's about time to get permanent recovery for this shiny piece....
Click to expand...
Click to collapse
Wont work, will give status 7 error, tried on TWRP and CWM
olvrick said:
same for me
---------- Post added at 02:52 PM ---------- Previous post was at 02:09 PM ----------
Wont work, will give status 7 error, tried on TWRP and CWM
Click to expand...
Click to collapse
even when trying it from SD? Meh....
I'll google around if there's some way of getting the original recovery back. Since first root, it only boots back into bootloader when trying to access stock recovery. I guess it's in some way needed for this update.
I certainly hope Marshmallow arrives soon as the current situation is really a pain in the a$$
will be fun, if rooted devices wont be able to install MM6.0 update
so i gave it a try. Looks like the update checks the fingerprint of some build.prop string (most likely ro.build.fingerprint). I guess this could easily be changed, but chances are good that we mess up the whole system when being on 5.01 droidboot and applying a fix that's suited for 5.1. As i messed up my system anyways while experimenting with this whole stuff, i just started from scratch, which means putting the phone to factory state using the flash_DDO_BB.xml, dd'ing the system.img back to it's place and downloading the 5.1 update right now. After that, i'll try downloading and installing the stagefright-patch before rooting.
toxic_garden said:
so i gave it a try. Looks like the update checks the fingerprint of some build.prop string (most likely ro.build.fingerprint). I guess this could easily be changed, but chances are good that we mess up the whole system when being on 5.01 droidboot and applying a fix that's suited for 5.1. As i messed up my system anyways while experimenting with this whole stuff, i just started from scratch, which means putting the phone to factory state using the flash_DDO_BB.xml, dd'ing the system.img back to it's place and downloading the 5.1 update right now. After that, i'll try downloading and installing the stagefright-patch before rooting.
Click to expand...
Click to collapse
system.img provided here is already rooted
olvrick said:
system.img provided here is already rooted
Click to expand...
Click to collapse
well at least i wasn't able to gain root before explicitly installing the SuperSU-Package via CWM.
Back to topic: i tried nearly everything yesterday, but after 4 hours of experiments, i rest my case. For me, there's no option on installing this update without having a proper working custom recovery on 5.1.
Did anyone try going back to stock, yano like real stock, install the update via OTA and root as known?
Illux said:
Did anyone try going back to stock, yano like real stock, install the update via OTA and root as known?
Click to expand...
Click to collapse
we'd need an unrooted stock image for that. At least i don't know if there's one flying around already. Also, we'd need to create a 5.1 boot.img and droidboot.img after the stagefright patch.
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
87lwrdr said:
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
Click to expand...
Click to collapse
1) This phone has a locked bootloader and has to remain on Touchwiz. Rooting methods are posted in the General section. You're stuck on Lollipop with this device, however you can flash other ROMs with Flashfire.
2. That would be software. Hardware is things such as the speaker, Home button, or the device itself.
{
"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"
}
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
87lwrdr said:
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
Click to expand...
Click to collapse
Pretty much, after 18-24 months companies just stop putting out new software (to get you to buy a new phone), that's part of the reason for using custom ROMs. This device is much older than that and has a locked bootloader, keeping you from doing a lot of things, like using a ROM with an unofficial kernel, so the latest software is not possible. The Sprint and TMo versions of this phone do not have locked bootloaders and are able to use Marshmallow and Nougat, etc. So root the phone using the one methods outlined in the General section (you need to use one that uses SuperSU to use Flashfire) of this forum and then use Flashfire to flash a custom ROM in the Android Development. New features and better functionality. I also recommend removing apps you don't use to decrease RAM consumption and increase performance.
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
87lwrdr said:
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
Click to expand...
Click to collapse
SuperSU is required to use Flashfire, but yes. I would Odin OF1 first or WiFi won't work, I would suggest Stanglitre's ROM it was the most stable I tried for the short time I had this device.
What do I use on build LRX22C.I545VRSGPL1?
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
87lwrdr said:
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
Click to expand...
Click to collapse
Yes they are for specific builds. You really picked one of the worst phones to start with. Do you have a PC?
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
87lwrdr said:
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
Click to expand...
Click to collapse
This device is more than a couple years old... But I would recommend downloading the OF1 firmware from wwe.sammobile.com and using the Odin program to flash it. Then you can use a few of the ROMs on here.
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
87lwrdr said:
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
Click to expand...
Click to collapse
You can now root it and flash a ROM. Just follow the rupturing instructions in the General section of the forum.
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
87lwrdr said:
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
Click to expand...
Click to collapse
Reflash OF1 with Odin and start over. I told you SuperSU was needed for Flashfire to work right. You need to use a root method that uses SuperSU. There is a couple guides in the General section of this forum.
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
87lwrdr said:
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
Click to expand...
Click to collapse
Try OC1 tar instead.
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
87lwrdr said:
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
Click to expand...
Click to collapse
Yes
Hi tell us how it was please...I am with the same trouble can not pass from lollipop don't have any rom mod nothing