Check out the image
Good news but it will be next year i think ... We will have to wait.
Wysłane z mojego HTC M9w przy użyciu Tapatalka
Wow two updates thats more than I expected for a cheap Android phone. Makes me a little upset that I had to stop using this phone to switch to T-mobile
Update will be available around Januari-Februari 2016. Very good of HTC for the support at 8xx series.
ronnie72 said:
Update will be available around Januari-Februari 2016. Very good of HTC for the support at 8xx series.
Click to expand...
Click to collapse
This update will come with sense 7.
yeah
What about 816g
yeah
That's a nice support from HTC, on contrary Samsung just cares about its latest flagships
Sent from my GT-I9500 using Tapatalk
Too bad updating after being rooted is a pain in the butt. Perhaps when it comes out, it'll convince me to go the custom rom route.
yeah
Will be avaible in 2nd quarter 2016
M8 user from Malaysia already received it yesterday...
matshah said:
M8 user from Malaysia already received it yesterday...
Click to expand...
Click to collapse
Well! Maybe we will come next month.
I wonder if this method will be implemented on our devices as well. It will make life a lot more easyer ... http://androiding.how/use-sd-card-as-internal-storage-marshmallow/
crazybasss said:
I wonder if this method will be implemented on our devices as well. It will make life a lot more easyer ... http://androiding.how/use-sd-card-as-internal-storage-marshmallow/
Click to expand...
Click to collapse
If this is not the official firmware, it will help CM13.
i rooted my 816g cuz the low internal memory space so is there a way to upgrade to 6 when it comes out ?!
ShakeItBaby said:
i rooted my 816g cuz the low internal memory space so is there a way to upgrade to 6 when it comes out ?!
Click to expand...
Click to collapse
I have the 816 a5_chl virgin mobile rooted and you would need to unroot through your SuperSU app in it's settings as well as undo any other system changes you might have made like Xposed frameworks for example then find and flash back your stock phones recovery, lock your boatloader then you could update. The less you have changed your stock system the easier it will be to restore it so that any " signed" stock update file will flash. These "signed" update files check the stock system before updating and any changes usually stop it . Hope this helped.
thoctor said:
I have the 816 a5_chl virgin mobile rooted and you would need to unroot through your SuperSU app in it's settings as well as undo any other system changes you might have made like Xposed frameworks for example then find and flash back your stock phones recovery, lock your boatloader then you could update. The less you have changed your stock system the easier it will be to restore it so that any " signed" stock update file will flash. These "signed" update files check the stock system before updating and any changes usually stop it . Hope this helped.
Click to expand...
Click to collapse
What happens if you are coming from a custom ROM like CM? I don't think there is any stock firmware for the a5_CHL, but I could be wrong. Maybe I could flash a different variant's version?
Not sure if you know, I'm wondering out loud. Thanks.
Bandit Development said:
What happens if you are coming from a custom ROM like CM? I don't think there is any stock firmware for the a5_CHL, but I could be wrong. Maybe I could flash a different variant's version?
Not sure if you know, I'm wondering out loud. Thanks.
Click to expand...
Click to collapse
Actually I do but just because I found out from someone else while I went looking for a flashable zip for my ROM. HTC has the executable RUU file in it's downloads section of it's website for the U.S. variants of it's phones. This file downloaded to your P.C. can be run as an executable program hooked to your phone by USB with the phone in hboot/fastboot mode but you must first reflash your models stock recovery , found elsewhere not at HTC site, and relock your boatloader then run the exe program. It wipes the whole phone and reformats it back to pure stock of whatever current version the file is. I found the a5_chl stock recovery on a couple of linked sites that had a flashable zip of it. I also believe you can flash this RUU(Rom update utility) as well from ADB/fastboot but I've never tried that method.
There are also just flashable zips of this version on the web, not executable, and I believe I even downloaded one but again I used the RUU on mine. Only issue I had was to get into stock recovery I had to hold the power button and volume up to get the recovery then release volume button immediately after for recovery to show even after booting into stock recovery to get pass a red ! In a square that showed up. I believe that it was because HTC recovery can tell the system had been altered, rooted, whatever and this was a notice to any tech that the phone had been altered. I didn't care because I was out of warranty anyway. I just wanted to get back to stock to do an update. Others haven't had this issue but I bring it up because I did. My stock recovery was flashed but I had to get past that red ! in a square so I could enter hboot/fastboot mode. Don't flash the the wrong firmware or it could soft brick your phone. Hard brick if your S off. Verify model firmware and carrier version before flashing anything.
Below is htc link but you'll still need stock recovery zip file. Also make sure you backup your current ROM in custom recovery and save it to external SD card and or P.C. Just in case something goes wrong you still have a backup of your current setup and ROM.
http://www.htc.com/us/support/rom-downloads.html
---------- Post added at 02:20 AM ---------- Previous post was at 01:50 AM ----------
And here's a link in XDA with a link to the stock recovery and instructions on how to do it. A senior member said he didn't have to relock his boatloader and it worked but you could try it that way first and if it fails just lock the boatloader knowing that it wipes your phone when you do so backup your contacts etc with Google's own contacts and phone numbers backups and or titanium backup or super backup apps from the play store. I use all 3.
http://forum.xda-developers.com/desire-816/general/ruu-t2952058
Related
Who knew a MONDAY would be such an awesome day! New OTA Update MF9 as 1st reported HERE by @jonathanhtc . Any questions can go here guys....
I'll start off with a question I have: Does this mean that all of our mods will have to be re-done to be able to be flashed on the new update? ie: Hotspot mod, 4 in 1 reboot mod, etc. all have to be re-done to be able to work on the new software update?!
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
That's why I'm definitely waiting till the devs take a look at it before I download it. It definitely wasn't there with MDC and MDL.
Sent from my SPH-L720 using xda app-developers app
Yes same here. BUT some new things that were reported are: Transparent notification bar with any wallpaper, new smart pause toggle, smoother UI (less lag), move apps to SD card, and KNOX is finally deployed along with Briefing and SPDclient.
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
garwynn said:
First things first. Let's see what partitions got an update.
And someone should put a bug in Agat's ear to patch his kernel with the latest updates.
Click to expand...
Click to collapse
I already posted in his thread about an hour ago that source is up
Sent from my SPH-L720 using Tapatalk 4 Beta
I wonder if this is basically the same update that the international version got. Hopefully it is, and it fixes the "smearing issue" and also we get the HDR video recording!
I heard people were unable to unlock to use internationally. Some said sprint unlocked but software restrictions remained. Do you think this update might fix that? And im not talking for use withing the U.S. mainly outside (Europe)
Sent from my SPH-L720 using Tapatalk 2
Okay, new bootloader, modem, kernel.
2 secondary bootloaders updated as well as rpm and tz.
Interesting that everything backs up to mmcblk0p22 before writing the new one.
Don't recall seeing that in updates for other devices.
New Fingerprint is just swap out MDL with MF9.
As mentioned, Knox is there. Makes me wonder what else was locked down with it.
Updated OCR among many updated binaries.
A lot of the binaries - in particular, vendor blobs - have an update.
I'll need someone to dump the system partition once it's patched for the new vendor files.
Hopefully good news for AOSP builds.
I'm asking to see if the previous sources have any info - but they've already stated not to expect anything.
There are a few questions that need to be figured out:
1) What is in the new bootloader? Are we locked like most of the others?
2) Can we revert bootloaders after flashing - and if so, what does it take to do so?
3) Root on new build?
All of this is going to require a test device, which sadly at the moment I am now without.
All the problems with the N2 left me with a Spare N2 and now without an S4.
xonone said:
Question that's on everyones mind is:
Are the bootloaders locked? That "Secure boot status: Samsung" thing was not there before if I remember correctly.
Click to expand...
Click to collapse
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Could you post the steps you used to update & restore root please?
illdini said:
Could you post the steps you used to update & restore root please?
Click to expand...
Click to collapse
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
shabbypenguin said:
you apply the ota, flash recovery via odin and then flash supersu. if youd rather skip a step im pretty sure you can use ota root keeper
Click to expand...
Click to collapse
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
chenry944 said:
When applying the OTA, were you rooted and flashed with a Custom Recovery (i.e.-CWM or TWRP)? Or were you completely stock?
Click to expand...
Click to collapse
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash.
I have the same question BTW I'm rooted, with TWRP recovery, but stock ROM. Have installed a few mods (hotspot, camera shutter sound disabled. Had XPosed framework installed with a couple of mods, but removed those later).
What would be the safe way for me to install the new update? I actually like some of the features that Samsung added, so not looking to switch away from stock ROM for now.
I'm hoping that knowledgeable developers will provide guidance in the next few days
jj14 said:
Judging by his earlier post I'm guessing custom recovery is probably not the best way to flash
Click to expand...
Click to collapse
Yea I read that post I am just trying to get clarification for myself and everyone else in which way he did flash it.
shabbypenguin said:
bootloader isnt locked, mine is already back to rooted with twrp. that secured by samsung is the new knox stuff, so you can assign your own bootloader chain etc. i dont know all the details nor do i pretend to, but what i do know is its for companies to lock their phones down and not a concern to us
Click to expand...
Click to collapse
Best news of this thread! Thanks for taking the chance!
Sent from my SPH-L720 using Tapatalk 4 Beta
yea i was stock odex from crawj and i hit errors while flashing it twrp, i flashed stock kernel and stock recovery and tried and it still failed so i modded teh zip to forcibly install, i now have no mobile data and my modem isnt updated. so my suggestion, dont follow my lead
im currently flashing MDC stock tar to fully update all the way.
Got the Modem Updated to MF9 using Odin without going back to Stock, uploading the odin package now, and will be updating the thread here -> http://forum.xda-developers.com/showthread.php?t=2338919
Does this include the security update Google announced would be coming to OEMs?
Now if i update to mf9, will it affect custom roms that are built around MDL, or AOSP?
Are you bricked after the OTA? Here's how to unbrick it, locked or unlocked.
One other note: this is NOT an official 183 FXZ, so if this doesn't work, it won't make things worse, but you'll just have to wait for the "official" 183 FXZ.
Thanks go to stras1234 for providing a KK FXZ for those that needed it to unbrick their phone.
Another big thanks goes to SamuriHL for providing a tool to use the FXZ provided by stras1234 to make your job easier to unbrick your phone and get you running with KK.
Go here to get the FXZ and tool to help you profit in the glory that is Kit Kat on the XT926 Droid RAZR HD -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I have removed all my instructions as they are useless and no longer necessary with the FXZ being released.
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
hi @iBolski i just want you to know that i share your post on the kk tracking post!
cmchance said:
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
Click to expand...
Click to collapse
If you're already on stock 9.30, then it should work. I think the hang-ups for many who are manually loading it themselves via taking the OTA directly, were where if you were pushed the OTA and immediately accepted it and allowed it to go through and update it, it might have worked as long as you were unrooted on stock 9.30.
However, I chose to save the OTA off to the side (from the /cache directory) and hence, booted into the recovery manually, not realising that it installs a newer stock recovery and that's where I got hung up at. I thought the install failed, when in reality, I had to go back into the recovery and install it again. Of course, I tried using vol-down + vol-up and it wouldn't work.
If you currently have root though under 9.30, you might want to hold off until someone verifies if root can be obtained again. Because, without an unlocked boot loader, you will more than likely lose your access to root, especially if the latest "exploit" for 9.30 doesn't work under KK.
Your mileage may vary, but I don't have a locked bootloader phone to test this out on, so please, I do not accept any responsibility for what may happen if you try it, whether you have a locked or unlocked bootloader.
Thanks!
Just what I was needing to hear! I am currently rooted so I'll probably hold off. I've got a used Moto X on order though, should get it in today. After I test it out and verify that I can tolerate it and the smaller battery, then I might do some experimenting with the xt926 model I have and report back. Though, as anticipated as this update is, I'm sure someone will have already beat me to all the testing within a few hours from now lol
I'm on 9.30 with locked bootloader. I've tried your method but can't get pass signature verification. It just won't be installed on 9.30 firmware. There must be anything can be mess in updater script to avoid error signature.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Sabissimo said:
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Click to expand...
Click to collapse
I can't share the file, but if you look in the KitKat Tracking thread, you should find it there somewhere.
As an official soak tester, I'm not supposed to share the update. Technically, I'm not supposed to share ANY info, but I wanted to share this with other users who were having the same issue as I.
Thanks!
I do not believe the KK update for 9.30 has been shared anywhere.
No where that I can find. I've been scouring and following the forums waiting to find one myself.
sent from my ? and rooted XT1080 that thinks it's an XT1060
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
I'm not worried about it right now, Moto Verizon just posted saying they approved the soak test and updates would be rolling out.
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
http://www.droid-life.com/2014/05/1...id-razr-hd-and-razr-m-on-verizon/#more-139933
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
Sabissimo said:
There you go, found it:
https://drive . google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Sabissimo said:
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
I got it! I used this link 'below' to finally get it to update while using this thread for advice. Thank so much!
http://sbf.droid-developers.org/phone.php?device=5
Now to try saferoot...???
For all my 9.30.1 people, I love you guys too.http://pan.baidu.com/s/1eQimdea
Enjoy that official KK ota for 9.30.1 over that slow ass chinese server and stop trying to get the 9.18.94 to work.
bweN diorD said:
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Click to expand...
Click to collapse
I flashed to 9.30. When I received the OTA from the soak push, I saved the OTA off to the side and didn't apply it immediately. Then, when I attempted to apply it (after using House of Moto to fastboot it back to 9.30 stock), it rebooted after it started applying and then went back to the recovery screen, but at that point, they had changed how you get into it. It's now volume-up + power, not volume-down + volume-up.
In any case, that second step needs to happen where you go back and re-apply the OTA.
I'm thinking if I would have taken the OTA automatically right after it downloaded, it was probably automated. That, or maybe Motorola/Verizon decided to make it a game and see if people could figure it out? :silly:
Safe root for me was a no go. But kitkat is pretty nice!
Sent from my DROID RAZR HD using Tapatalk
Thanks for all the info. Got KK up and running
I used these instructions - http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1
and I used this file - http://forum.xda-developers.com/showpost.php?p=52610188&postcount=11
All last night I tried using the leaked file someone put up from that "slow ass Chinese server" haha. Long story short, it didn't work at all.
This morning I tried again, and nothing. So I tried this file (the one I linked up top) and it worked like a charm. I installed it via recovery, phone rebooted, used vol up + power to get into new KK recovery, applied leaked file again, and boom I got KK.
As someone in another thread said, during the update it does say "Phase 1 possibly complete". WTF is that all about?
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
huatz84 said:
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
Click to expand...
Click to collapse
Glad it's all working for you now. It definitely performs better than JB ever did.
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Leraeniesh said:
I've got an Unlocked bootloader, status code 3, and when flashing Dhacker29's TWRP 2.7.0.0, I can no longer boot into recovery.
Anyone else noticing this?
Is there an updated version of TWRP compatible with official kitkat?
Click to expand...
Click to collapse
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Eclipse00 said:
Sadly not yet
http://forum.xda-developers.com/showthread.php?p=53183031#post53183031
But this should help get the ball rolling:
http://www.androidpolice.com/2014/0...and-4-4-2-kernels-for-the-razr-m-and-razr-hd/
And I'm checking here daily assuming Dhacker is going to be the one taking this on:
http://androidhosting.org/Devs/Dhacker29/msm8960/
There is a working clockwork, but if you're a TWRP user like myself that's not much help for restores.
Click to expand...
Click to collapse
is the CWM 100% operational ?
Last time I checked it was half baked still.
Give the Devs some time. =) atleast we got KK officially =) Loving it.
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
j27h said:
Seems like Dhaker29 just uploaded a new TWRP image for KitKat (2.7.1.0):
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR-HD_M-KITKAT.img
Click to expand...
Click to collapse
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
Saw that tweet.
Gonna have to stick to CWM till he updated TWRP for HDPI.
Its nearly unusable in XHDPI
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is the forum he was using to post that update. I sent him a PM letting him know about the resolution issue(XHDPI).
http://forum.xda-developers.com/showthread.php?p=53245960
It's here
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Just used it this morning to install root on 4.4.2. Worked fine.
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
I'm assuming you have an unlocked bootloader. I had that same issue after the initial upgrade to the new OTA and bootloader. I ran through a few steps like unlocking the bootloader again (may have not done anything), I used a pre-rooted RSD flash of stock and I used the ADB method of installing the recovery instead of using fastboot.
To use the adb method I downloaded the batman 1.2 recovery tool, just renamed the version of TWRP (in this case TWRP2710-RAZR_M-KITKAT.img) to TWRP.IMG and placed it in the root of the batman folder, then I ran the flash TWRP recovery option. Note that the batman tool was designed for older firmware and you should probably not run any other functions on it if you are on the new firmware.
Batman 1.2
Murph28 said:
It doesn't seem to be working for me. I must not be doing something right. I am using these commands,
adb reboot bootloader
fastboot flash recovery TWRP2710-RAZR_M-KITKAT.img
it appears to work, it says successful but when I boot the phone into recovery it is still the stock. Any ideas on what I may be doing wrong?
Click to expand...
Click to collapse
You need to remove or rename,
Code:
/system/[COLOR="Red"][B][I]recovery-from-boot[/I][/B][/COLOR]
Thanks I will give this a try. I may hold off for now I read there was a possible update coming. I would guess you would need the stock recovery to get the update to work.
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
ezdi said:
You could always flash the old recovery back. Since the soak test invites just came out it will probably be a month until it's released.
Click to expand...
Click to collapse
Two weeks at best, considering it's the 4.4.3, which is probably the last update we'll get from Moto, unless a miracle occurs and we're given the 4.5 or 5.0, which shouldn't land until at least 5 months after it's release (if it does release next week).
I can't believe they're already planning another update. Sitting on jb we were all pretty sure that the kk update would be the last
Sent from my DROID RAZR M using Tapatalk
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
GnatGoSplat said:
Either the KK build was just too buggy to ignore, or Verizon is making them close the bootloader exploit hole again.
Click to expand...
Click to collapse
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Sent from my DROID RAZR M using Tapatalk
thewraith420 said:
It's a shame that they'd even bother closing that on a 2yr old phone but that's probably right. Too bad really. it's probably the only thing that would keep this device going for much longer. I know I was about to move on b4 towel root + bootloader unlock became available
Click to expand...
Click to collapse
Yeah, I'm hoping the update is because there were bugs that were too big to ignore, but Verizon forcing them to patch the exploit is probably more likely. Definitely a shame to close it on a 2yr old phone. IMO, we need some kind of consumer protection law that forces VZ and AT&T to allow BL unlocks once a device reaches EOL. It would even be better for the environment as it does keep devices relevant for much longer and less likely to end up in a toxic Chinese burn pile.
I feel like the reason we got the exploit back was a Moto dev saw the device is reaching EOL and decided it wouldn't hurt to help the community by putting the exploit back in, because it would almost have to have been deliberate.
Well it's actually lucky that 4.4.4 didn't patch towelroot, so root, I THINK, will stay, but for the bootloader unlock, it's better now than wait with Verizon.
Hi all,
For those with the AT&T version of the LG G Pad 7 the Android 5.0.2 update is here. Looks to have been released 2 days ago actually. See http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425003&cv=820
My tablet is not rooted or modified in any way. I checked for updates, says none available so no upgrade for me yet. Will post back once I get it. I've upgraded other devices from KitKat to Lollipop and they are always laggy after the upgrade. I plan to upgrade then factory reset the tablet as that seems to work out much better.
Finally received the update. All went well since I as not rooted or anything like that. Not used it for long but seems a bit more responsive. I did factory reset and set up as new after doing the Lollipop upgrade.
Does anyone know a successful root method. I've tried everything with no luck. There's got to be some way.
Tersanyus said:
Finally received the update. All went well since I as not rooted or anything like that. Not used it for long but seems a bit more responsive. I did factory reset and set up as new after doing the Lollipop upgrade.
Click to expand...
Click to collapse
hi, were you connected to att network when recieved the update?
Yes my G Pad 7 has a valid/active AT&T Sim card in it. I have it on my mobile share value plan.
Is there a way to root 5.0.2? Everything I have tried seems to fail.
draexo said:
Is there a way to root 5.0.2? Everything I have tried seems to fail.
Click to expand...
Click to collapse
Anyone???
No way to root lollipop. I'm back on KK and working on PAC Rom build.
Sent from my D6503
I have the KK source code for the v410. Is there no way to build a KDZ from it? I am guessing there is not because someone would have though of this by now.
I still don't see this update available. Im using it on wifi only, with no sim card. Can this be the issue?
The mobile(SIM) network is used to access protocols(most common is time/date and OTA) that routers ignore. To update go to AT&T and ask for a new SIM or root; custom recovery; flash update.
Tersanyus said:
Hi all,
For those with the AT&T version of the LG G Pad 7 the Android 5.0.2 update is here. Looks to have been released 2 days ago actually. See http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425003&cv=820
My tablet is not rooted or modified in any way. I checked for updates, says none available so no upgrade for me yet. Will post back once I get it. I've upgraded other devices from KitKat to Lollipop and they are always laggy after the upgrade. I plan to upgrade then factory reset the tablet as that seems to work out much better.
Click to expand...
Click to collapse
hay man i am too waiting for the fu***in thing to come up but it doesn't know the way out there. Now i think you guys should find a way to diggout that OTA bur****d and please share it here @talvigi
wrtechnopath said:
The mobile(SIM) network is used to access protocols(most common is time/date and OTA) that routers ignore. To update go to AT&T and ask for a new SIM or root; custom recovery; flash update.
Click to expand...
Click to collapse
theres a zip with the update? or you mean things like blisspop or cm?
dreamtheater17 said:
theres a zip with the update? or you mean things like blisspop or cm?
Click to expand...
Click to collapse
Hay, dear , you mentioned a zip update here but you didn't provided the link, if you have seen such thing please give me a link of that thanks.
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
dreamtheater17 said:
theres a zip with the update? or you mean things like blisspop or cm?
Click to expand...
Click to collapse
Hi, dear, I have been looking for that zip for a long time, can you please give me a link of that as you have said there's a zip with the update, But you didn't share the link of that update kindly do please.
As far as i don't have an AT&T SIM and if i would have one i don't live in the US of America so the OTA on the SIM card is impossible, that way i have asked you guys to share a link you have or someone might have seen it somewhere around the world.
gridironbear said:
Anyone???
Click to expand...
Click to collapse
I downloaded KingRoot from app store and that does the trick.
Is there a manual zip file or something for lollipop? Att with no sim. No OTA available
KingRoot APK worked for me..took two tries..then I replaced their flavor of SU with SuperSU....I still have not been able to custom recovery the beast tho.. Lollipop 5.0.2..tried to Flashify with TWRP 3.0.0.0 Bumped..I get boot certification error when I try to go into recovery.. But I can reboot back into Stock ROM..kinda got cold feet..don't want to hose the device!
hifi1969 said:
KingRoot APK worked for me..took two tries..then I replaced their flavor of SU with SuperSU....I still have not been able to custom recovery the beast tho.. Lollipop 5.0.2..tried to Flashify with TWRP 3.0.0.0 Bumped..I get boot certification error when I try to go into recovery.. But I can reboot back into Stock ROM..kinda got cold feet..don't want to hose the device!
Click to expand...
Click to collapse
Any body have stock lollipop update of this device either zip or kdz file please share your thoughts with us. Some us really in great need of that.
Sent from my LG-D850 using Tapatalk
Memory woes
I've been running my v410 with lollipop for a while now and was getting pretty discouraged that apps keep crashing. Large apps like games will crash when a calendar notification pops up, etc.
I used KingRoot to gain root and then SuperSUme to replace SU and remove KingRoot bloat. Mostly to kill ads since I'm running stock with no custom recovery (there are only about 6 apps I use that require SU)
So anyway, I recently installed Kernel Adiutor to take a peek at some kernel tweaks. Low and behold, the default low memory killer settings are set super aggressive! The most aggressive preset available in Kernel Adiutor is still only half of the default values. I knocked it down to "moderately aggressive" and my memory problems are gone (mostly). I'm now playing with the Z-RAM settings to try and get my memory usage to be more efficient.
I was afraid I would have to downgrade to KK to get this thing back to usable. Perhaps not...
katsmacker said:
I've been running my v410 with lollipop for a while now and was getting pretty discouraged that apps keep crashing. Large apps like games will crash when a calendar notification pops up, etc.
I used KingRoot to gain root and then SuperSUme to replace SU and remove KingRoot bloat. Mostly to kill ads since I'm running stock with no custom recovery (there are only about 6 apps I use that require SU)
So anyway, I recently installed Kernel Adiutor to take a peek at some kernel tweaks. Low and behold, the default low memory killer settings are set super aggressive! The most aggressive preset available in Kernel Adiutor is still only half of the default values. I knocked it down to "moderately aggressive" and my memory problems are gone (mostly). I'm now playing with the Z-RAM settings to try and get my memory usage to be more efficient.
I was afraid I would have to downgrade to KK to get this thing back to usable. Perhaps not...
Click to expand...
Click to collapse
Wait - you have root on 5.0.2?? Can you post a zip?
So, I know nothing about HTC devices, very new to them. I have a box of spare phones from an old job I know longer have... I found a M7 in that box, realized it works... except it was black listed.
hBoot Version: 1.55
Android version: 4.3 rooted with a rom I'd never heard of
I ran RumRunner, and now its also S-Off'd!
Any ROM Recommendations or should I leave it on the 4.3 it is currently running? Any tips or things I should know before I really dig around this thing?
If your phone is s-off and it is international model I would recommend you to update your firmware to latest Google Play edition version from this post. Just download and flash in fastboot "complete firmware (without boot.img and recovery.img)". If you don't know how to flash firmware in fastboot follow steps for flashing from this thread. Also update your recovery to latest TWRP from here and you should be good to go.
You can choose any sense lollipop rom if you preffer sense or if you like aosp roms you can try google play edition rom 5.1 or even nougat rom like lineage 14.1
Think about to flash my M7 too, current on default Lollipop with Sense and dont want to loose the function to stretch the song cover to fullscreen when take a fast look to lockscreen...hmm, never found an app to make it work on other devices. Is it a Sense function on HTCs only or something? The first version of Blinkfeed felt fast as ****, on sth. without advertising, or notices app fallback to localhost, i didnt tried rooting but maybe there is fun possible by auto shutting down again and again when the sheduler is restarting and restarting the same app.
crimson_stardust said:
Think about to flash my M7 too, current on default Lollipop with Sense and dont want to loose the function to stretch the song cover to fullscreen when take a fast look to lockscreen...hmm, never found an app to make it work on other devices. Is it a Sense function on HTCs only or something? The first version of Blinkfeed felt fast as ****, on sth. without advertising, or notices app fallback to localhost, i didnt tried rooting but maybe there is fun possible by auto shutting down again and again when the sheduler is restarting and restarting the same app.
Click to expand...
Click to collapse
Do you still have the rumrunner file by chance?
maciclazar said:
If your phone is s-off and it is international model I would recommend you to update your firmware to latest Google Play edition version from this post. Just download and flash in fastboot "complete firmware (without boot.img and recovery.img)". If you don't know how to flash firmware in fastboot follow steps for flashing from this thread. Also update your recovery to latest TWRP from here and you should be good to go.
You can choose any sense lollipop rom if you preffer sense or if you like aosp roms you can try google play edition rom 5.1 or even nougat rom like lineage 14.1
Click to expand...
Click to collapse
Do you lose your sunshine liscense if you were to clean flash your device?
zeeBomb said:
Do you lose your sunshine liscense if you were to clean flash your device?
Click to expand...
Click to collapse
If you meant to flash a different custom rom your phone will still be a s-off but if you flash ruu or go back to s-on you'll maybe need to pay for sunshine again. I never used sunshine so I can't tell you. I did s-off using rumrunner long time ago.
zeeBomb said:
Do you lose your sunshine liscense if you were to clean flash your device?
Click to expand...
Click to collapse
You never lose your sunshine license if you dont change your imei (and thats forbidden anyhow). You can s-on and s-off as often as you like if you paid for the device once.
maciclazar said:
but if you flash ruu or go back to s-on you'll maybe need to pay for sunshine again.
Click to expand...
Click to collapse
http://theroot.ninja/faq.html
(...)one license is good for one device. You can reuse SunShine on that device, if necessary(...) Codes are one time use only, and bind the license to your device's motherboard, just like in app purchases. If you need to run SunShine again on a licensed device, the app will recognize the motherboard and download the license automatically..
Click to expand...
Click to collapse