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.
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
{
"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"
}
Oops, rooted I-545 running 4.3 was accidently updated to KitKat 4.4.2 and I lost root HELP!
I am starting a new thread because I think my message got lost in a 45-page thread and this is urgent.
My original S4 had the updating software renamed so that I wouldn't even be notified about updates, but I had to get a warranty replacement. I rooted it, but forgot to turn of the ability to update. Last week, while I was undergoing surgery for a kidney stone, my wife was using the phone in the waiting room. She saw a message that an update was ready and, since her S3 is totally stock and she always updates, she hit the ok button. That night, I discovered I was no longer rooted and that KitKat 4.4.2 was the new O/S.
I am very dependent on functionality that will only run rooted, so I really need to clear this up. For example, I use RCB as my phone and text blocker and it requires root to run. It's big advantage is that it does this all silently before the call bubbles up to where non-rooted call-blockers do a pickup and hangup (with an annoying fragment of a ring each time). Since I'm unable to run RCB or a root-level file browser to recover the logs of blocked numbers to use (temporarily, I hope) in something like Mr. Number.
Is there anything I can do to either root under KitKat, or back down my version of Android to 4.3 and then re-root the standard way?
Blue Sun
"Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity."
-- Charles Mingus
Here you go.
http://forum.xda-developers.com/showthread.php?t=2726868
Dooley69 said:
Here you go.
http://forum.xda-developers.com/showthread.php?t=2726868
Click to expand...
Click to collapse
This does not help him because he lost root & wants to get it back. This instructional thread assumes root has been maintained. Currently, there is no root solution for the 4.4.2 version. Apparently, patience is the only solution.
OffcerClancy said:
This does not help him because he lost root & wants to get it back. This instructional thread assumes root has been maintained. Currently, there is no root solution for the 4.4.2 version. Apparently, patience is the only solution.
Click to expand...
Click to collapse
Actually it should because you can downgrade partially back to MK2 and then root using saferoot and then follow the top instructions to go back to fnc5 and it works because I have done it. If you havent done it you shouldnt comment.
That's what I learned TechGuy. Just trying to help out!
Techguy2002 said:
Actually it should because you can downgrade partially back to MK2 and then root using saferoot and then follow the top instructions to go back to fnc5 and it works because I have done it. If you havent done it you shouldnt comment.
Click to expand...
Click to collapse
Yeah, whatever you say Supreme Leader. In any case, if you have actually done this, you should share your gift w/this thread: http://forum.xda-developers.com/showthread.php?t=2734309
Reply
Blue Sun said:
Oops, rooted I-545 running 4.3 was accidently updated to KitKat 4.4.2 and I lost root HELP!
I am starting a new thread because I think my message got lost in a 45-page thread and this is urgent.
My original S4 had the updating software renamed so that I wouldn't even be notified about updates, but I had to get a warranty replacement. I rooted it, but forgot to turn of the ability to update. Last week, while I was undergoing surgery for a kidney stone, my wife was using the phone in the waiting room. She saw a message that an update was ready and, since her S3 is totally stock and she always updates, she hit the ok button. That night, I discovered I was no longer rooted and that KitKat 4.4.2 was the new O/S.
I am very dependent on functionality that will only run rooted, so I really need to clear this up. For example, I use RCB as my phone and text blocker and it requires root to run. It's big advantage is that it does this all silently before the call bubbles up to where non-rooted call-blockers do a pickup and hangup (with an annoying fragment of a ring each time). Since I'm unable to run RCB or a root-level file browser to recover the logs of blocked numbers to use (temporarily, I hope) in something like Mr. Number.
Is there anything I can do to either root under KitKat, or back down my version of Android to 4.3 and then re-root the standard way?
Blue Sun
"Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity."
-- Charles Mingus
Click to expand...
Click to collapse
Okay so the way to do this is simple: You will need to factory reset to stock. This will wipe all of your data, but if you do this correctly with Odin, then you will be surprised with how it works.
Use this thread to do a full or no wipe: http://forum.xda-developers.com/showthread.php?t=2578209"]http://forum.xda-developers.com/showthread.php?t=2578209
Once you do that, you have to go through the processes and go to settings>phone info>software update and update your system software.
After that, you can re-root your device through this thread: http://www.ibtimes.co.uk/root-galaxy-s4-snapdragon-600-exynos-5-android-4-3-without-warranty-void-1431730
Your welcome.
Do I neet root to use Surges downgrade??
I upgraded to leaked kitkat nc2 and lost root of course..I want to downgrade with Surges method back to mk2..does his downgrade process require root to downgrade?? First post.... Thanx..
OffcerClancy said:
Yeah, whatever you say Supreme Leader. In any case, if you have actually done this, you should share your gift w/this thread: http://forum.xda-developers.com/showthread.php?t=2734309
Click to expand...
Click to collapse
Somebody already told that guy to do that. It is a known method.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
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.
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.
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
mrz80 said:
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
Click to expand...
Click to collapse
Is kingroot the only way still? I have OF1 but I cant get kingroot to uninstall properly.
bobturismo said:
Is kingroot the only way still?
Click to expand...
Click to collapse
I *think* it is. After desiccating my eyeballs reading a bazillion posts about rooting late-code S4 phones, this is the most promising thing I came up with:
https://forum.xda-developers.com/ga...-to-root-verizon-galaxy-s4-android-5-t3655127
bobturismo said:
I have OF1 but I cant get kingroot to uninstall properly.
Click to expand...
Click to collapse
I took a flyer and tried Kingroot on my GPL1 phone, with (pretty much as expected) nil results. I finally got Kingroot uninstalled by long-press selecting it & dragging it to the trash, clicking "uninstall", then clicking thru the "can't uninstall 'cause it's an administrative app" screen. That landed me on a screen where I could deactivate it. Once it was deactivated, it (at least theoretically... let's see what happens after a reboot... yep, all gone) could be deinstalled.
mrz80 said:
I.
Click to expand...
Click to collapse
When I would try supersu me, it would delete kingroot, then restart like halfway (like crash or error) then I would restart and not have root anymore.
I ended up doing this and it was super simple
https://forum.xda-developers.com/android/general/guide-to-replace-kinguser-supersu-t3185998
BUT this was using an older kingroot 4.1.something and then after supersu me froze, then I did this and during the process while trying to delete kingroot files, it kept saying "File not found". So there is a possibility I didn't need to run the MRW script....
mrz80 said:
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
Click to expand...
Click to collapse
I just swapped out main boards from my old GS4 to my semi newer one. So now I'm back on MK2 with Safestrap installed and thank God I had Safestrap because it allowed me to bypass my lockscreen since it wouldn't accept my old pattern or pin number.
mrz80 said:
Ebay score of the year, and it's not even February yet! Just landed a working ICH545 with an unbroken screen and **OF1*** still on it! LineageOS here I come! My S4 has GPL1 and a broken screen. After getting the wife a Pixel2 for Christmas I wasn't exactly looking forward to spending major cash for another new phone.
Click to expand...
Click to collapse
Sorry to tell you, OF1 is still locked. Lineage OS can't be run on your device. MDK was the build that was unlockable.
bobturismo said:
Is kingroot the only way still? I have OF1 but I cant get kingroot to uninstall properly.
Click to expand...
Click to collapse
This is much easier - https://forum.xda-developers.com/showthread.php?t=3254434
{
"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 used kingroot to root GPL1. Getting rid of kingroot for superSU to take over was a slight pain. I had to download ES file explorer, terminal emulator, and some kingroot_to_superSU.zip file that had 4 files inside. After it was all said and done, I finally got superSU to work and got rid of kingroot (I think).
npjohnson said:
Sorry to tell you, OF1 is still locked. Lineage OS can't be run on your device. MDK was the build that was unlockable.
Click to expand...
Click to collapse
Yeah, I realized I got my research crossed up. Oh, well... at least I've got an extra phone with no broken glass. Wonder if anyone's got an S4 in a box in a closet somewhere that never got past kitkat.
Hi!
Just picked up one of these in great condition not crackedd or anything its verizon of course not on OF1 its oni545vrufnk1
anyway, was wondering if you could share some info with me on this device. I have tmobile and im wanting to go with the tmobile version of this phone.. (i dont know if there a unlocked firmware version)
is this the way to go should i just flash it with tmobile or unlocked firmware?
thanks
xsnrgx said:
Hi!
Just picked up one of these in great condition not crackedd or anything its verizon of course not on OF1 its oni545vrufnk1
anyway, was wondering if you could share some info with me on this device. I have tmobile and im wanting to go with the tmobile version of this phone.. (i dont know if there a unlocked firmware version)
is this the way to go should i just flash it with tmobile or unlocked firmware?
thanks
Click to expand...
Click to collapse
Nope, you're out of luck.
No ROM's either.
Best bet is to update to PL1 (the newest build) via OTA, and just pop the TMO SIM in, and set the APN by hand.