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
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
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
snovvman said:
This came from Sammobile. I downloaded it so I can start working on a rooted ROM. You will need this to update the baseband, etc. anyway, so I figure I post it in case anyone needs it. This is the one to use to upgrade to stock 5.0.1. or return to full stock.
As usual, all at your own risk. Check MD5 before flashing!!
DOWNLOAD HERE
Enjoy...
Click to expand...
Click to collapse
MAN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
...just... man.... i soft-bricked and my router was blocking sammobile for some reason. just finished restoring after kicking out bucks for a fast sammoblie download and playing Ethernet games
thanks though
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
dinaps86 said:
Damn man if i only would have waited instead of making the jump early.....once u flash the or update via ota there's no way of flashing back to kk unless u didnt flash the lollipop bootloader....right?
Click to expand...
Click to collapse
yeah, that's what happened to me. the boot loader was not having it. my system is still recovering. the boats are burned!
{
"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"
}
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
There needs to be a real guide to rooting lollipop
Sent from my SM-N915P using XDA Premium HD app
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
i accepted the OTA. i should have not done that, now i'm trapped
snovvman said:
Yeah... in general, if you odin'ed the stock package, which includes the bootloader, you can't go back to KK.
At this point, you guys can root and flash the recovery, and just wait for me to complete the deodexed ROM. At that point, you can just flash the ROM via recovery. You will already have the L bootloader and baseband.
Click to expand...
Click to collapse
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
cvaria said:
i accepted the OTA. i should have not done that, now i'm trapped
Click to expand...
Click to collapse
Not at all. I was waiting for lolly to drop for root.. I just did the chainfire method and you're done.
Rooty
jdidtht said:
So your saying you've tried to odin back to kk? Past samsung has always been pretty liberal with going backwards.
Click to expand...
Click to collapse
I'm saying that based on what I have read and experienced, you *generally* cannot revert to a previous major version. Aside from bootloader issues, you may not be able to flash over the modem. This was the case with the Note 2 and 3. I have not tried with the Edge. If you do, please do report.
dinaps86 said:
Rooting lollipop is the same as kitkat n snovman this .zip u posted can be flashed via recovery? Or u just posted the .tar to be flashed through Odin im goong to try n build a kernel for us to set sulinux to permissive bc i cant take not having viper4android
Click to expand...
Click to collapse
This is the Samsung stock image, so it is not a recovery flashable zip. It is a tar that must be flashed via odin. It contains bootloader, baseband, and system image.
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
snovvman said:
FYI--I am uploading a deodexed/zipaligned PRE-BETA rooted Lollipop as I write this. READ: PRE-BETA.
Click to expand...
Click to collapse
Ready to test maybe i get xposed back working
Well, here goes nothing....
http://forum.xda-developers.com/not.../rom-sprint-note-edge-915p-5-0-1-oc8-t3082802
For what it's worth, on the regular Sprint Note 4 you can go back to KK once you have taken the Lollipop ota or odin'd the Lollipop tar. The bootloader is backwards compatible on the regular Note 4. However you cannot run a Lollipop rom using the previous KK bootloader. That definitely causes big problems. Another thing you have to keep in mind is that the Lollipop tar writes carrier partitions and other important partitions so you MUST either odin flash the lollipop tar or have taken the lollipop ota BEFORE you flash ANY stock or custom Lollipop ROM via custom recovery. And before you odin the stock Lollipop rom tar you have to first reboot into custom recovery and do the factory reset several times and also wipe system, cache, dalvic etc several times.Then reboot into download mode and flash the Lollipop tar. Do this first or else you will odin the Lollipop tar and have left over data which I guarantee will cause issues. You would think the rom tar would completely wipe these partitions but apparently this isn't happening because there are reports of left over data from previous roms after flashing the stock Lollipop rom tar. I would assume this would apply to the Sprint Note Edge also. This is just a heads up.
Surf and talk
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
platniumrover said:
Quick question. I just bought my edge today and I wanted to verify that If I root it I will be able to surf and talk correct?
Click to expand...
Click to collapse
Sounds like you have some reading to do. Educate yourself before you get started.
primo523 said:
Sounds like you have some reading to do. Educate yourself before you get started.
Click to expand...
Click to collapse
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
platniumrover said:
I have done alot of reading, just haven't been able to find much on the forum about it. So its true that the sprint variant only comes with one antenna? But the big question for me is how permanent is it? Because there is a chance of doing voice and data over the one antenna in the future. But I dont know which direction they are going. What are the correct strings to search on xda?
Click to expand...
Click to collapse
You can usually find a stock version of any device's firmware. That'll bring it back to unrooted factory condition. HOWEVER, keep in mind that Samsung has included a piece of software called Knox on their newer devices. As soon as you modify the firmware (which you will have to do for root), you will trip a counter that lets Samsung know the device is modified. Basically, your warranty is literally void as soon as you root your phone. There are some apps I've seen that try to undo this, but I'm not sure if they work.
But it really sounds like you don't know enough about root to go messing with it. Do more research first.
Here's a link to a pretty good guide that'll give you an idea of what rooting is for.
http://www.androidauthority.com/root-android-277350/
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.
UPDATE: Axon 7 A2017U Build 29 (MR3)
New OTA update is arriving and looking forward for what bring to the table.
aerospaceman Employee Oct 30, 2016 6:01 PM
Over the next 24 to 72 hours, you can expect our 3rd software update (MR3) to the Axon 7 (A2017U). This update will bring your device to the latest build, B29. This update comes less than one and a half months from the previous one, but the more exciting news is that we're in parallel paths to deploy Nougat as quickly as possible.
Here are the latest updates you will see on B29 (coming from the previous build, B27):
Notification bell is now optional (hooray!)
New application management policy to enhance battery life
Optimized video camera focus on moving objects
Resolved .FLAC file playback issue
Visual Voicemail optimized for dual SIM
Updated fix for Mute Call issue
Other general enhancements
Note: This is an over-the-air (OTA) update. To check availability of an update, click on "Settings -> Updates."
Aside from this update, you can bet on our R&D team being hard at work on Android N. Early tests from your Mod Squad have been very positive and we trust that many of you will also not sleep for the first several days after upgrading. Setting Nougat aside, we remain heads down prioritizing fixes and enhancements for our community. Your constant feedback, both positive and negative, continue to motivate our R&D team. So please don't let up on your interactions with us and each other about the Axon 7. Until the next update, please drop a comment below to add further motivation for your R&D team!
Click to expand...
Click to collapse
-------------------------------------------------------------------------
UPDATE: Axon 7 A2017U Build 29 (MR3) Announcement Link
-------------------------------------------------------------------------
TWRP Flashable Files can be found here : TWRP_A2017U.B29_Bootstack_StockSystem_Files
What's does the " Parallel paths" mean....
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
S8ntsHaz3 said:
What's does the " Parallel paths" mean....
Click to expand...
Click to collapse
jonathan3579 said:
Ha! I was thinking the same thing. It sounds like more vague crap from ZTE like normal.
Click to expand...
Click to collapse
S8ntsHaz3 said:
I'm wondering if it means that it's at a parallel in development as far as time between updates... Like b27>b29 was 1 and 1/2 months and that's what they're lookin at for a time frame?
Click to expand...
Click to collapse
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
DrakenFX said:
my guess is " performing of multiple operations simultaneously " meaning getting MR's OTA and working Naugat (Android 7) at the same time???
well i'm just assuming so , and i assume next Update will be N release., you know B3x
Click to expand...
Click to collapse
Oh how I hope your right!!!!
Now to wait for the download link
xtermmin said:
Now to wait for the download link
Click to expand...
Click to collapse
It's here!
{
"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"
}
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
It's here!
Click to expand...
Click to collapse
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
jonathan3579 said:
How'd you get the embedded battery percentage?! I sorely miss that from my Nexus 6P.
Click to expand...
Click to collapse
There's an app in play store to enable it in any device!
Sent from my ZTE A2017U using Tapatalk
toyanucci said:
There's an app in play store to enable it in any device!
Click to expand...
Click to collapse
Oh sweet, thanks. I think I tried it before but it didn't stick after rebooting. Has it changed since then? If so, I'm definitely gonna have to search for it again.
I have the option for the update as well. Waiting as I'm rooted.
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Thanks for looking into a twrp version!
Sent from my ZTE A2017U using Tapatalk
Parallel paths does indeed mean they are simultaneously working on updates and the long awaited Nougaaaattttt update. ZTE has done a good job updating and listening to their customers in the z-forum. Lets hope this plus Official CM and unlock bootloader without breaking warranty will help ZTE be known as a developer friendly Own.
How do we install if we are unlocked bootloader and rooted??
Do we have any idea if flashing U roms on G device works? Would love to get rid of the bell
Here over in europe, i just received for my A2017G an 703mb big B05 Update.(previous B03)
Strange that ours is 703mb big (hope they fix the youtube freeze Problem) and also supports optional notification bell (no info for that in the change log)
Take a look:
DrakenFX said:
Here is the download link if anyone wants to play with it.
update_P996A01_B27_to_B29.up
I'll be looking into it and try to create a flashable zip for us TWRP users
Click to expand...
Click to collapse
Here is an Mega Mirror for the B29 update. Just in case.
I have simply copied it from its location "data/data/com.zte.zdm/files" where the updater places its OTA files.
https://mega.nz/#!K050XAqT!6EBTgtX13VTdAOiUjiYqeE6jemeOJ2mN8smrrreai6o
MD5: 9a7f45caf459a21a905de0c543748309
If you place the file into that directory. You should be good to go using the inbuild updater.
Dewaynelives said:
How do we install if we are unlocked bootloader and rooted??
Click to expand...
Click to collapse
I was on B27, unlocked bootloader, TWRP recovery, rooted, with changes to /system, and have successfully upgraded to B29 (w/ same modifications). Since I made changes to /system (AdAway, Titanium Backup, AFWall) and wanted a clean slate for everything, I wiped my A7.
If you don't want to factory reset your device and didn't make any changes to /system, you might only have to unroot, restore stock boot.img and stock recovery.img via TWRP (from rczrider's topic linked below), install B29.zip in stock recovery, flash TWRP, then flash root, but I didn't do it personally, so no guarantees.
Anyway, this is what I did. Some of these steps might not have been needed, and probably could have been done differently, but it's what worked for me, and yes I like rebooting:
1. Download the B29 update, DrakenFX's B27 StockSystem zip for TWRP (which also flashes stock boot.img), stock B27 recovery.img from rczrider, and SuperSU 2.65. Put all on microSD.
2. Booted into TWRP and did a factory reset, rebooted back into TWRP and flashed DrakenFX's B27 StockSystem ZIP, rebooted back into TWRP and flashed stock B27 recovery.img, rebooted device.
3. Powered on the device and made sure it booted into OS fine and was still reporting the correct amount of internal storage space. Rebooted into stock recovery and flashed the B29 update.zip from my microSD card. Installed fine, rebooted into OS to made sure it still worked.
4. Rebooted into fastboot, connected to my computer and flashed Unjustified Dev's TWRP via Minimal ADB & Fastboot, booted into TWRP and flashed SuperSU 2.65 from my microSD, let the device reboot itself a couple of times.
I now have B29 with unlocked bootloader, TWRP, and root.
NOTE: Something I noticed when I was going through and disabling system apps: WeShare can't be disabled from the Settings > Apps menu, but can be disabled by opening the app drawer, pressing and holding on it, and dragging it up to "Disable" at the top of the screen.
However, it would probably be easier to just wait for DrakenFX to create custom TWRP install zips for B29.