This is for D800 (AT&T LG G2) users ONLY.
This package will update a phone with D80010d firmware to a "mixed" firmware that boots normally to D80020c (kitkat), but retains the older boot loader and compatibility with loki patched custom recoveries. The "normal" boot is 100% unmodified stock.
This "mixed" firmware is currently the only known way for a stock D80020c (kitkat) system that also allows custom recovery.
What's installed:
rpm, tz, modem, and system partitions from the stock D80020c (kitkat) LG G2 firmware.
LG's D80020c kernel, recompiled by @Savoca, and made compatible with the D80010d bootloader.
That will leave your existing D80010d boot loader (aboot) intact, as well as whatever custom recovery already installed.
This firmware package will (or at least should) refuse to install on ANY firmware other than the D80010d firmware. Please don't reply to this thread if you are using anything else. (That was as polite as I'll be on that issue...)
I STRONGLY suggest doing a full wipe on your device after flashing this. You don't have to, but it'd be a really good idea...
This is NOT my software. This is 100% LG's software and firmware. Don't ask for support in this thread. It won't be provided.
Instructions:
Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
Root the device and install recovery (recovery is required, root is not.) This is a link for rooting instructions. While you are welcome to use CWM for your recovery, this is a link for installing TWRP recovery. (Since cyanogenMod took freely given contributions to their codebasse and went private/for-profit, I have a personal bias against them - so my personal recommendation is for TWRP.)
Copy the d80010d_to_20c.zip package linked below to your phone.
Reboot into recovery and install the d800_to_20c.zip package.
Optionally, also install a superSU or other root package.
Optionally, but suggested, Perform a "factory reset" on your device.
Download Links:
The main package (about 1.7GB): Dev-Host (md5: 7cfe7de4ab31f727b72178b8fb618fd3)
SuperSU: Direct from Chainfire's webpage
Credits:
Several people spent countless hours working on finding a way to get recovery working with LG's kitkat. The kernel used in this package was made by @Savoca - who used the solution found by @JackpotClavin. Others involved are (as far as I'm aware) @AndroidUser00110001 and @jakew02. Of course, @Chainfire for the 'su' package.
Source:
All the images in the recovery package are completely stock with the exception of the kernel and kernel modules. The kernel is modified and recompiled with only the following patch: https://github.com/JackpotClavin/an...mmit/7b6187a0e5fb8ca59888cacf5f5b863baa8d1064. (The installer overwrites the kernel images in /system with those from the kernel compile.) The base kernel source is found on LG's opensource website under the D800 heading.
May 2014 Update:
I'm no longer able to tinker with my G2. My wife took it from me (for her own use), and she gets angry when I mess up all her settings.
(I ended up getting a HTC One M8 to tinker with.)
While I'll leave the thread unlocked so users can assist each other, please don't expect prompt responses from me or maintenance.
switched main package link to dev-host
added "source" section.
As soon as it's done downloading I will let you know that it works unless someone beats me to it that is
EDIT: Finally finished downloading I already flshed back to 10d rooted installed recovery and am now installing kk.zip
Re-Edit: just finished installing also just so you know flashing system only took about 2mins a little bit over that in terms of seconds anyways everything seems to be running fine ill report back tomorrow when its not 1am my time and can test things more thoroughly but I can confirm that everything flashes like its supposed to and also I like the little check you added where it says d80010d bootloader good!
Sent from my LG-D800 using xda app-developers app
XxZombiePikachu said:
... and also I like the little check you added where it says d80010d bootloader good!
Click to expand...
Click to collapse
It's actually checking that loki_patch reports a d80010d bootloader. If not, it'll abort flashing.
Thanks man, now i have kitkat with root and recovery (D80020c)
Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2
DowntownJeffBrown said:
Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2
Click to expand...
Click to collapse
This is the only way for now to have a recovery on kit Kat
Sent from my LG-D800 using XDA Premium 4 mobile app
Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?
FlyingColors said:
Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?
Click to expand...
Click to collapse
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.
Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?
garyd9 said:
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.
Click to expand...
Click to collapse
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.
FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.
Click to expand...
Click to collapse
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app
XxZombiePikachu said:
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
more people asking questions that have already been answered. then when you point out that their question has already been answered they say they are trying to clarify even though it's already been clarified in the OP. it's a phenomenon on xda.
xLordNitro said:
Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?
Click to expand...
Click to collapse
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Click to expand...
Click to collapse
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.
garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse
xLordNitro said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse
after you went back to jb then rooted and installed custom recovery then flashed this firmware, did you do a factory reset upon first boot? meaning did you get past the initial set up then go to settings/backup and restore and reset the phone? if not then that could be your problem. the factory reset does indeed reset everything after you initially install kitkat. it worked for me also, i had mms issues every time i initially installed kk. after a factory reset the mms is resolved.
Yep, did that. Still same problem. So im assuming its something to do with the files themselves, and maybe the fixes that are being done to keep recovery. I dont know. But im back on Jellybean for now, i cant let my battery take that huge a hit.
xLordNitro said:
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. ... . It went from 100%-60% within 1 hour of just standby, didnt even use the phone.
Click to expand...
Click to collapse
Wow. That's REALLY strange. I wonder why it's impacting only some users, and not all. (It would make sense that if it happens when BT is turned off, it would impact 100% of users.) Something else that's odd is that it happens with this, but not with the OTA. Even more strange is that it happens with that other "stock kitkat" firmware, as that essentially is the OTA with zero changes - it's even using the OTA provided bootloader and kernel.
I'm not really sure how to guide you on troubleshooting this. Anything I might suggest would take a few days of reverting and flashing various things, and I somehow doubt you'd want to spend the rest of your life doing random experiments for me. Perhaps you should try that poweruser firmware with things added one at a time - as you suggested.
Take care
Gary
garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.
Click to expand...
Click to collapse
Too late, I've already installed it and successfully have Kitkat. Even though you probably don't like me, thank you.
Problems going back to other rom
I was running flex rom before end flash kk end the motion sensor calibration work but doesn't work on my other roms only work on kk only. please fix
Related
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
misteral1970 said:
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
Click to expand...
Click to collapse
Mate, it doesn't sound good.
What I would do, at this point, is Fastboot the 4.1 image again.. And stay the heck out of CWM. If you Fastbooted the 4.0.4 image, and you still have it showing 4.1, then you have a serious issue. So boot to fastboot, and try it again. Clearly, whatever you did with CWM, didn't work,
Installing a rom from CWM, requires certain things to be done, either in the install script, or via CWM.
Most notably, Formatting User data, cache, dalvik, system, and data. If any of these do not get done, chances are, the rom install will not go good. The basic install script, generally only formats System and Flexrom. This is because Acer distributes a full rom with the understanding there is nothing on it. Most rom modders know this, which is why they give extra instructions via cwm.
The big thing, is when you boot your tablet, is if it says which bootloader you are on. So you have to look,. You want to be on the JB bootloader.
MD
Thanks for the response MD,
A tiny bit unsure how to proceed. I understand everything that you said (well, I think I understood correctly!)
I have in fact tried to fastboot the 4.1.1 image again, and again I am stuck on the language and location screen (did this last night before giving up for the day)
I have read and understood "Stay away from CWM" (and I know that it is in this case only - have used CWM on my Gnex without issue)
Please forgive me if what I am about to write is ridiculous - this is kind of where we'll see whether I understood correctly or not.
I'm thinking that if the various areas were not wiped, and that could be the reason for the snafu, then it would be worth going into CWM (which I have been warned to stay away from, and which I would stay away from except for this one thing) and formatting the user data, system, dalvik etc, then applying either the 4.1 or 4.0.4 to result in a working tablet.
Or possibly flashing the bootloader to make sure it is JB
Or going back to the weird 4.0.4/4.1.1 hybrid which works but doesn't allow Play Store and finding a way around that issue.
Mate, I'm not sure which way to go at this point!
Fastbooting 4.1 is a dead end at the moment (but could that be a bootloader issue....)
Fastbooting 4.0.4 gives me the hybrid (though I can check this again tonight)
BTW, the only CWM Rom work I have tried to do has been with the patched update (second downloadable file I think) - everything else has been done via ADB
So.....CWM to wipe/format caches? (I'm thinking 'NO! DID YOU NOT HEAR WHAT I SAID ABOUT STAYING AWAY FROM CWM????' but I'm asking anyway!)
Flash a new bootloader on? If so, any idea where I would find it (will obviously search here and Google)
Thanks anyway, and thanks in advance if you have any more advice. I really do appreciate the support!
Al
Well Al,
This is perplexing to say the least. Clearly fastbooting the 411 results in frozen at the wizard. My question, when you have the unlocked bootloader, does it say JBxxxxxxxx unlock mode when you boot the tab? Because it should. If it doesn't, then you're still on ICS bootloader. And will have to do the CWM thing to get JB installed. The 411 image flash, is to get a rooted version.
And this is the point. Personally, I do not trust the CWM's at this point. That's just me (already bricked 1 tab 3 months ago with a faulty CWM) I know the folks with ICS are using Pawitp's CWM, and haven't reported issues. But I don't know if they are doing wipes or not.
As with the 404 image, well, why playstore doesn't work is perplexing. You could try reinstalling the playstore via manual method (root required). Which is to delete the vending.apk, install a new vending.apk (making sure permissions are the same as the other files), then reboot. Go to settings, wipe the playstore cache's. Then try Playstore again. This was an old method we used with market issues in HC.
Personally, I feel the issue is with the wipes before running the patch. But I would hate you do the wipes and formats, then discover the emmc chip bricked. So it's 50/50.
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
Wish I could give you a definitive answer, but these processes are too new.
MD
Keep warranty
Moscow Desire said:
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
MD
Click to expand...
Click to collapse
Can you make a short tut how to replace the old unlocked Bootloader?
My Tab has some Problems with the Display so it need a service ...
witch cwm to use?
witch update.zip?
remove cwm and su if necessary
Android Version: 4.0.4
Baseband: 11.810.922.00
Kernal:2.6.39.4+
Image:ACER_AV043_A701_RV08RC02_EMEA_DE
Build: ACER_AV043_A701_1.017.00_EMEA_DE
Hi MD,
Thanks for such a speedy and useful response!
Warranty: nope! I'm in China, bought the tablet in Shanghai (now way down south in Shenzhen) and it was a dodgy deal to say the least. I suspect they were being lifted from the factory. No complaints from me about this, or about any difficulties caused by rooting/flashing/CWM. My choice of action all the way along and I am aware of the risks
Just flashed 404 again and it is fine so far, again very nice and smooth. Going to look at the Play Store and see how it behaves, see what I can do as far as vending.apk is concerned (although I'm lost when it comes to permissions. Obviously I know what permissions are in tech terms, but no idea where they would be set, how to change them, what to use as a reference) I figure this is the path of least resistance for right now.
Then I'm going to see if I can apply the standard A701 update to JB (which I won't be able to because of rooting/unlocking but I will fiddle around) and see if I have any joy.
Got my keen eyed gf to check the message on boot, you were right that with the 411 image applied it still had an ICS bootloader, so that's good to know if I want to try going back to the flashed JB image. However, I have no idea how to flash the JB bootloader/kernel, and the CWM process for the patched update fails each time (despite editing the first line of the necessary file in META-INF/Google/Android)
So, I will keep you up to date with progress. Fingers crossed!!!
Al
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
misteral1970 said:
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
Click to expand...
Click to collapse
Well, seems like Nova is the culprit. I assume you are talking about nova launcher? Or nova the game?
Hi MD
Yes, Nova launcher but no, it's not the culprit. At least I don't think so.
The play store stopped as soon as I ticked 'Install from unknown sources', before I installed Nova.
Very odd.
Quick questions:
1) Any advice/links/downloads for changing to JB bootloader if I apply the 4.1.1 again? Given that I cannot run the patched update/flash from CWM, I am guessing I would need to directly install/flash the bootloader from ADB...
2) Don't kill me for asking this. I know to stay away from CWM, I have seen you post it a good few times here, I heed the warning....BUT.....
Given that I have CWM installed and it's working ok (apart from failing to apply updates) - I have 6.0.1.4 - many of the guides to updating the 701 say it needs 6.0.1.1. Would the slightly more recent version of CWM make a difference in terms of success or failure of the update? Update is failing with a 'set_perm:some changes failed' very early in the update.
Seriously, I am being extremely wary of CWM, it's just that currently I have a slightly disabled tablet and it would be great to get this sorted.
Thanks, once again, for all your help,
Al
Update again, put 404 back on (after issue with play store and unknown sources)
Opened play store, downloaded Apex launcher - all good.
Ran Apex, all good....then suddenly Play Store stops, Apex stops, never to return.
With 404 img on, About Tablet still says 4.1.1
The saga continues!!
Aaaand that's the end of that!
Put 4.1.1 back on, pushed the boot.img from the official update.
Now no CWM, so it seems no recovery mode....if I try to get there by volume down and power on, it goes into update mode.
And of course neither the official update nor the 'patched' one will apply.
Can boot to the first start screen (language/location) but can't get any further.
Maybe I can find a service center here in Shenzhen who can sort it out.....as I said before, no harm no foul, I knew the risks!
Thanks one more time MD for all your support and advice )
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
misteral1970 said:
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
Click to expand...
Click to collapse
HA HA, you found the User Data wipe.... Yeah, a little known secret from the 500 forums.
MD
It's so strange....so now I'm back to having flashed 404 but the tablet thinks it's 411.
Play store was fine for about 40 minutes, I quickly got chrome, currents and BBC news.
I turned off the Acer ring and play store died...
But here I am, typing to you on the tablet and it's fine. And what a change in performance. It's most noticeable in currents..the increase in speed and smoothness when scrolling between pages makes it at least ten times better than before.
But the last flash was 404....weird....
I'll leave it like this for now. No market but at least it's not semi bricked!
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
misteral1970 said:
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
Click to expand...
Click to collapse
Well, good news then. I think it's an interesting set-up. Hybrid. Still not sure though, why it pulls 411 from the build.prop as it should have been changed when you flashed the 404image. But honestly, after reading the OP's steps, I believe he references going back to 404 via CWM, and not fastboot. This of course would mean installing a full 404 original rom. I'll have to look over my JB system dump and see where the other prop would be. Maybe something changed in JB.
So if you can live with it, it's probably better to leave it be till we come up with something more definitive.
MD
"So if you can live with it, it's probably better to leave it be till we come up with something more definitive"
Yeah, totally agree.
Mate, seriously, thanks for the support and advice on this. It makes a big difference. Even as I sat there last night with what seemed to be an unusable tablet, being able to chat to you about it meant that at least I didn't feel completely adrift!
Big big thanks
Q&A for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [COMMUNITY] ANDROID 5.1.1 OCTOS *Obake*. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can I install it without bootloader unlock?
Summersett said:
My bootloader unlocked Maxx is on 4.4 (19.5.3.obake-maxx_verizon.Verizon.en.US). Since my bootloader is unlocked, do I really have anything to fear when flashing ROMs or am I pretty much guaranteed to be able to always have WP off and root? I'd like to give this one a shot but don't want to cross any bridges I may not be able to come back across if need be.
Click to expand...
Click to collapse
My bootloader is locked, I'm on 4.4.4 with root, but I don't now how I can unlock my moto, I must to have TWRP? How can I install this recovery? Help me please, I want lollipop, and verizon is so slow.
This isn't the place to ask that, and right now you are stuck on stock. Please dig around the forums and do some research before spamming threads where content does not belong.
No GPS
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
I haven't had this issue and have reflashed this ROM a few times. Tbh I have never even heard of that as an issue (though it's not like I researched Lollipop problems since I wasn't having any).
I used TWRP 2.8.4.0, factory reset, flashed the ROM, and then flashed these GApps. Idk if that makes a difference. Give it a shot if nothing else is working for you? Good luck.
Dang... That is exactly how I did it. I used that same exact gapps file and also am on TWRP 2.8.4.0. Seems like none else is reporting this problem on our phones. Maybe the radio got screwed up? Just thinking out loud here
Installed OctOS on two separate MAXXes. My gfs seems stable. Mines been touchy though-
A) Like someone else mentioned, using the flashlight for an extended period often ends up in the phone doing a hard reboot. Haven't tested this with her phone but she hasn't reported anything to me either.
B) WiFi has been unstable. Initially it was fine, but every now and then it starts refusing to connect to any network. It doesn't kick back any error. It will say connecting, etc, then at some point fail and go back to just noting it's a saved connection. Have to go through some combination of forgetting the connection, wiping cache/Darvin, think I even tried running fix permissions. Eventually it will work normally again, but not for long before having the same issue. There haven't been any wifi issues with the other phone. The first time this ever occurred was right after using it as a hotspot, but its happened more often without any hotspot usage than with it.
C) Did great at first, but without installing very many apps, it feels like it's gotten slightly sluggish and is often low on memory, and is burning through the battery much quicker. Used the be able to clear 24 hours before needing to charge, now I'm lucky to get 16. I haven't had the chance to see if this is also an issue on the other phone or not.
GPS works nicely for me with this rom. My phone got a fix in seconds with 16 satellites.
Question: which is the best way to theme this (or others, for that matter) rom? Download CM12 themes from mayket?
jwieler88 said:
Flashed this ROM on my Droid MAXX and love it. Everything seems to work except I cannot get any GPS lock on any application I tried. Downloaded GPS toolbox and reset and downloaded aGPS data but no change. Anyone have this problem? From what I've searched on forums it seems to be a somewhat common issue in Lollipop. FYI I also flashed a different 5.1.1 ROM and it had the same problem.
Click to expand...
Click to collapse
Did you ever get GPS back? Some say going back to stock, getting a lock, and then go back to the custom rom works. There is also a link in the exodus thread about doing two fastboot commands, which worked for me for a bit, bit now I'm back on stock with no GPS at all. Curious if you got yours working.
I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !
I'm not on the PK1 firmware yet, but I just upgraded from PG1 to PIA.
As far as performance goes, I found this thread VERY helpful: http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
Maybe it will serve well for you as well. As far as rooting is concerned, not too sure from personal experience, but I heard the ENG boot works with the newest firmware and I'm guessing the modified SU should work for it too.
If you would like to try reverse engineering the files yourself, maybe these guides will help out:
http://arm.ninja/2016/03/04/reverse-engineering-samsung-s6-modem/
http://forum.xda-developers.com/android/software-hacking/how-to-reverse-engineer-kernel-t3137384
http://www.fortisfio.com/extract-android-rom-for-reverse-engineering/
In regards to removing bloatware, I prefer removing apps over services because you never know when you might need a service that you accidentally removed from a previous time. Also I've been going through many cases of trial & error with removing bloatware and a few times ended up messing up other apps in the process that would force crash, but with my current setup everything seems to be working well.
If you need help with removing bloatware, there are 3 apps that really helped me out.
https://play.google.com/store/apps/details?id=com.piriform.ccleaner <-- Surprisingly ccleaner is awesome for the android as well as the PC.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en <-- this is very useful as well
Another tool I found very great and you run this from your computer is Debloater: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Hope this helps. I'm trying to currently work on a way of creating custom odin flashable roms so I can optimize roms to the best of my ability and provide the community with more options as well. This is still a work in progress though. :S
EDIT:
Here is an output of my program list. It was too long for me to post directly in the message
adb shell pm list packages -f
thanks a lot!
I have read about ENG boot being an improvement as well, yet nobody is stating that it is stable as it is prior to root, just improved lag, performance and stability. I know in my experience, root, for the first time in 8 years of rooting is not worth the benefits. This is sad. Must be stable. (in addition -no roms, no nanroids, no samsung Sumsung Pay..etc..etc..) So I'm hopeful things will change soon, or will be forced away from Samsung. Tmobile privacy invasion issue, and bait-and-switch with their plans is even further less encouraging news. Imagine "unlimited" = less.... wow.
Well said, and I completely agree. I've been a BIG fan of previous Samsung models, but it seems with every new model that comes out there are less and less options for customizations. I'm currently in the process of trying to figure out how to repack tar.md5 files *properly*.
I've gotten close, but then it fails right at the very end. I'm still waiting for a response from someone hopefully with more knowledge than I, but I guess I have to be patient. Here was my thread: http://forum.xda-developers.com/tmobile-galaxy-s7/help/creating-flashable-odin-file-t3500139
Any way, I'd love to see more customization for the S7. I think it's a great phone and it has so much potential. I also love android and always felt it gave users more ability for customization as opposed to Apple. Like you, I just hate all the bloat ware and all the crap that comes on phones these days. Not only that but the markup price is ridicules. Having to pay $600+ for a phone that is "laggy" due to all the bloat on it is frustrating to say the least. This is why I'm trying to give the community more options or at least steer them in a direction to customize their devices easier. Currently despite all the various amounts of software that is provided through this community I feel like there aren't too many people that know how to properly use it.
Any who, good luck with your phone. Let us know if you figure anything out with it. Also, are there any significant advantages with the newest firmware over the PIA? I usually like to hold off from upgrading right away so that all the "kinks" get worked out first since it's difficult to downgrade afterwards.
xena499 said:
I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !
Click to expand...
Click to collapse
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.
Its bootlooping because you accepted the security update popup.
You know what, that happened to me once, I forgot. What I needed to do is reflash the ENG boot file then when I got back into the phone, remove and reinstall SU. After your phone restarts, go into playstore --> you apps --> and uncheck "Auto Update" for Super User.
KillerClaw321 said:
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.
Click to expand...
Click to collapse
thanks I tried going back to PIA and used fixes only, as the debloater might be the culprit !
I got it work now here:
@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.
m0d hipp¥ said:
@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.
Click to expand...
Click to collapse
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.
xena499 said:
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.
Click to expand...
Click to collapse
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
NO you need the Tmobile files, available in links here, or better from the sammobile.com site i mentioned above.
I would never flash verizon firmware on a tmobile-connected phone.
In addition, are you following the verison unroot method from the verizon s7 rooting guide? the verizon root references for me were just where the best info is for all S7 people, but the software links are to older firmware that didnt work...
Basically, you are using odin to flash ALL files at once (ie AP, BL, CP, CPC), then you are back at tmobile stock as per date of package used (PIA, PG1..etc).
Earlier versions before PIA do not flash, for me. I believe this is b/c i took an OTA security update that did something to prevent this. PIA worked fine for me, and is working not bad.
I'm satisfied for now, and I will wait for stable Nougat before anything else, and done with customizing and playing.
I hope this helps you
m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....
Any luck?
sardor_x_z said:
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....
Click to expand...
Click to collapse
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.
silversusanoo said:
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.
Click to expand...
Click to collapse
I just rooted mine this morning. I played around with it a few times. What worked for me was run root.bat with my phone unplugged then plug it in. It took a few minutes for everything to go through. Hope this helps.
Sent from my SM-G935T using XDA-Developers Legacy app
Also would like to know bypass for limited tether greatly appreciated
Sent from my SM-G935T using XDA-Developers Legacy app
I’ve recently been trying to root my Samsung SM-J710FN. I managed to find a sequence of actions that consistently produces a rooted phone. I found TWRP 3.0.2 (I know that later versions exist, but this is the latest I could find for this model) and flashed it using Odin. I then use it to wipe the data partition (because, apparently, TWRP doesn’t work well with encryption). I use adb push to copy SuperSU 2.79 (downloaded from here) and no-verity-opt-encrypt-6.0 (in accordance with instructions in this thread, downloaded from here) to /data, then I install both of them using TWRP and reboot.
While the phone does appear rooted, it does end up having some serious problems. Here are some that I managed to find:
The camera doesn’t work. When I try to start the Camera app, it just crashes after a few moments.
The flashlight doesn’t work. When I try to turn it on using the button in the quick settings panel at the top, I get a message saying that the Camera app is using the flashlight (and the flashlight doesn’t turn on, obviously).
The phone does not automatically change orientation as I rotate it (in apps that are supposed to support it, such as Google Chrome), even though the appropriate settings are enabled.
The brightness controls do not affect the screen’s brightness in any way.
(I also can’t manage to re-encrypt the phone after rooting it, but that’s probably better left for a different thread.)
Has anyone else encountered similar problems? What can I do to solve them?
Have you tried to reflash stock ROM again?
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
I finally figured it out. Looks like I should have used a different SuperSU version. I repeated the process using SuperSU v2.82 SR5 and the problems stopped.
(I’m still trying to get the phone to be both rooted and encrypted, but that’s a separate story…)
EDIT: I gave up on SuperSU and used Magisk instead. It’s much easier and seems to work perfectly even with encryption!
Can you give me link to download a Android system and Magisk. Which one you used. I have the same problem :c
Here’s Magisk: https://forum.xda-developers.com/apps/magisk
As for “Android system”, do you mean stock firmware? In that case, I’m really sorry but I haven’t really kept a link to the place I downloaded it from Besides, you need stock firmware that matches your specific phone (based on the part of the world where you bought the phone, I think? I’m not quite sure), which may not be the same as mine.
I've already done it, I downloaded all the necessary files from sammobile.com
But thank you for your willingness to help
voidphantom said:
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
Click to expand...
Click to collapse
Can you give me the link of the Stock ROM?
When twrp install j7 max then phone go to bootloop problem please tell me how I fix this problem
dealiyo said:
Can you give me the link of the Stock ROM?
Click to expand...
Click to collapse
As I said before, unfortunately, I have not kept a link to the stock firmware. Further, judging by your other posts, you don’t seem to have a device of the same model as mine (I have SM-J710FN, you said you have SM-J710GN), which means my stock firmware isn’t going to be useful to you anyway.
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.