Related
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
This is the stock US KitKat ROM for The Galaxy Tab 3 7" Tablet. Finally found it after a bunch of hassle online, and figured I'd post it here to make things easier for everyone.
When I Odin'd this ROM, it actually upgraded my tablet, and left all my items installed (not guaranteeing this will work the same for everyone else).
Afterwards, I just Odin'd TWRP to reroot using Chainfire's SuperSU (no other Superuser would work) and called it good.
Caution: if you are using a custom ROM, this may not work without reflashing stock 4.1.2 since the 4.4.2 ROM appears to be an update, rather than a full ROM.
Rooted devices and custom kernels that are otherwise stock should be fine.
The cache, and if possible dalvik-cache should be cleared before flashing. Some of those files can sometimes interfere with upgrades.
It might be necessary to pinpoint apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
If that fails, it might be necessary to factory reset the device.
The Stock 4.1.2 ROM for the T210R is available here: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
The T210R...XAR file is for the 210R:
https://drive.google.com/open?id=0B2iEgzRTFjrQTmI0ZjRBbWtOajQ&authuser=0
The ITV file is for the T210 (no R)
To download these ROMs, a torrent client is required (such as utorrent).
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)
Can I flash this on the SM-T210?
john410 said:
Can I flash this on the SM-T210?
Click to expand...
Click to collapse
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Greaper88 said:
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Click to expand...
Click to collapse
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
[email protected] said:
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
Click to expand...
Click to collapse
I did not have this problem, but I didn't have much on my Tab either. (Some apps don't play well with KitKat upgrades.)
Torrents have multiple segmented hashchecks to make sure you get an uncorrupted download, but it might still be possible. I'm reasonably sure my file is OK since I've used it (can't speak for the non R file though).
Did you clear your cache, and if possible your dalvik cache? I've read that some of those files interfere with upgrades.
If you can pinpoint the apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
Other option would be to try a factory reset and see if that fixes it. (I understand not wanting to do that though.)
One more thing, if your ROM isn't stock, or stock rooted (custom kernel should be ok too), you may have to flash 4.2 before the 4.4 ROM will work on the device.
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
void.naught said:
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
Click to expand...
Click to collapse
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
thank you for finding and posting the correct files for this tab
hi i have a galaxy tab kid t2105 rooted, is it possible to install any other rom after 4.1.2?
Greaper88 said:
Rooted devices and custom kernels that are otherwise stock should be fine.
Click to expand...
Click to collapse
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
ubuntujason said:
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
Click to expand...
Click to collapse
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Greaper88 said:
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Click to expand...
Click to collapse
Awesome, thanks!
~J
Could you upload the T210 ITV file? This torrent is going to take 10 hours
No system file
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Sorry, m'y post an error
ragnaroksangel said:
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Click to expand...
Click to collapse
Are you looking for the Stock Rom?
Darthlord064 said:
Are you looking for the Stock Rom?
Click to expand...
Click to collapse
I am, can you help?
Greaper88 said:
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
Click to expand...
Click to collapse
For some (unknown) reason, Odin3 nor JOdin3 doesn't seem to work for flashing my Samsung Galaxy Tab3 device. For that reason I tried Heimdall-Frontend, but to make that work you need to extract the content of a stock ROM first.
Anyways, it still didn't lead to get my device into factory reset yet.
But that's another story on which I still have not yet found the answers needed to get the device successfully back into factory reset.
My guess is that the 'system.img' file, of Android 4.4.2, successfully has been loaded from Heimdall-Frontend, yet by going into reboot right away after Heimdall-Frontend releases the connected device, the download may be deleted.
I read that the cause of that may lie in the fact that Android 4.4.2 is only an update and no full ROM.
My 959V is rooted, had plenty of roms,ect over the last 3 years decided to do Gremlin remover and update it...,
Couple days ago upgraded to the "909" download of CM11,4.4.4, but every site I get it from gives me 908 (even though they all say 909) (last 3 digits of download version). The 908 will not recognize on my Win 7 laptop, but was fine up to now with previous cm11 same phone..
I have used the same cable for the last year for both my Galaxy and 2 Sidekicks phones, data and charging, now the Galaxy only charges, Windows detects but wont recognize, does on the sk4g's
Also (908) will not allow me to paste into sys/media with a " read only issue", although up to now swapped 15 different bootani without problems. Tried 3 different root file managers,same outcome.
Is the driver for the phone firmware windows looks for(on the phone itself) replaceable from sdcard? Im guessing its a bootloader issue and the 908 is the one not to of put on my phone.
Whats the probability I am getting the 909 but the 908 will not allow it to surpass it. Goes through the whole flash and on reboot I have to reenter emails,playstore apps,ect, but on 908 still in settings.
I can/ have been able to swap 1 rom via twrp and sdcard on 908 ( to slimkat4.4.4 and back to 909, but comes up 908) any other roms error before flash(and slimkat does not recognize on usb either).
is it a Kernel fix, and can it be flashed via sdcard? Bootloader via sdcard? Bad usb port? Does charge, and the drivers/ cable verified.
Thank you for any help, been 3 days now, redone my laptops (2) from scratch, everything ,c++,java,netframework,samsung,zadig 2.0, and more.
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
FBis251 said:
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
Click to expand...
Click to collapse
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
I didnt do a backup, if thats an issue , can I backup 2nd motherboard and apply to the first?
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
FBis251 said:
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
Click to expand...
Click to collapse
O.K., so Ive been playing with the second mobo just to test different angles.
1) E.S. File manager is the culprit, swapped out for a paid app Ive used with Sidekick 4g, Root Explorer, and boot ani. goes fine, on both mobos.
2) The latest gapps (cm 11 w/ gaps 4.4.x) was giving me a "Google servers cannot be reached" error on both mobos, used the gapps for cm 10.1 (jb 4.3) and all is working, both mobos.
3) Was reading that possibly the adb driver is in the kernel, and thats what windows is looking for? Ive tried but can only sd card flash at this point so, giving up. I can bluetooth,wifi share or email files to myself if need be. Im guessing its a hardware issue beings that the 2nd mobo was reflashed identical to to the first. (with exception of one click 2.3.6,and w/a twist oc/uv on the 2nd),1st one will not downgrade at all below 4.4.4 by sd, I was trying to ics a rom guessing the foundation might overwrite any missing stuff then upgrade back to 4.4.4.
One post mentioned that the mtd/bml cross flash is a no-no, could that mess up usb driver identity on the phones side?
Not a big deal, both phones/ roms are working great and have no issues (except 1 doesnt connect to a computer for file transfer). Thank you for your help.
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Also, the phone was working fine up to about a month ago, it was recognized by the computer, only difference I made was trying apps, off playstore, five fingers for ebay,different weather apps for widgets,silver/gold prices apps. Thats when it started not recognizing.
I was getting the same error about the google servers, then I tried a earlier version of gapps. Connects now.
Floridasun said:
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Click to expand...
Click to collapse
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
As far as the phone itself goes, the phone should be recognized even if there is no driver for it installed on your computer. You can use this software to verify that
http://www.nirsoft.net/utils/usb_devices_view.html
I don't believe you can even edit anything on the phone to make the USB device not be recognized when plugged in short of bricking your phone, so if there isn't even a USB connection being made, as I mentioned before, it looks like a hardware issue is causing your problems.
In that case, it'll be hard to flash anything without going through a lot of hassle since all the reliable recovery methods we have need that you are able to use your USB port on the phone.
EDIT
If you do still have TWRP available on the phone, flashing any ROM will reflash a kernel, but be careful because the recovery is tied to the kernel and some ROMs have a non-working recovery, so if you happen to flash some of these you'll be stuck with a nice paperweight . The latest CM11 I have posted does have a working kernel/recovery but I still don't think it'll fix your issue.
FBis251 said:
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
Click to expand...
Click to collapse
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
bhundven said:
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
Click to expand...
Click to collapse
I still use two of them. Great little phones really. I see no need or use for 5.0 I think running this CM11 from you guys is about the end of the road for these phones. A great ride indeed. Ill be sticking around regardless just to see what happens. Thanks guys☺
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
Hi all, I do not understand your magic and really hope I don't have to learn too much of it. I have never rooted a device, so please bear with me. I just purchased a used Galaxy Note Pro 12.2 off eBay. I did my research and planned to just follow instructions to root it and upgrade to Android 10. However, I had a few issues and when I tried to boot to recovery mode, I get an android on its side with a red triangle. In the upper left hand corner, it says
Android System Recovery <3e>
KOT49H.P())XXUANB2
Volume up/down to move highlight
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Power-Volume down takes me to a screen that says
WARNING!
A custom OS can cause critical problems in phone and installed applications
If you want to download a custom OS press the volume up key
Otherwise, press the volume down key to cancel
When I press Volume up, I get a screen with the green android and the message
Downloading...
Do not turn off target
In the upper left hand corner it says
ODIN MODE
PRODUCT NAME: SM-P900
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOW WARRANTY VOID: 1
AP SWREV A1
It then is stuck there. It seems like I cannot turn it off for a while like it is timing out.
It has Android 4.2.2. When I go the update in settings, it downloads a file but will not install it.
So I did some more research, and I believe that the device is already rooted with Odin (not quite sure what that is). If my hunch is correct, a lot of the work has already been done. The device was restored to version 4.2.2. By the way, an upgrade in settings downloads a new version, but it will not install.
If anyone could walk me through the process from where I am to install Android 10, I would be ever so grateful. I need a stable version, so if Android 10 is not finished, whatever version makes sense. Right now, it will not install things like Hulu or Outlook.
Although I do not know much about Android, I can follow instructions. And I know very well that I proceed at my own risk.
Thanks!
Bubble-burst here...
First and foremost... you can't get Android 10 on the SMP-900. This is an older device and is no longer supported/updated by Samsung, so the binary blobs that connect the hardware to the operating system are stuck at Android 5.0.2 (I think - the numbers AFTER the decimal may be off by a few, but point is that Samsung's last supported update was for Android 5.xxx). There are some later ROMs (what you're trying to load) that were made by some great developers that shimmed those binary blobs into a newer version of Android (AOSP) or LineageOS that makes the tablet quite usable and enjoyable.
I personally am running LineageOS and OpenGapps (the OpenGapps project is an open source version of Google's proprietary framework that makes things like Gmail, Calendar, Play Store, etc, work) and it works great. That at least gets you a more up-to-date tablet that runs better than Samsung's last update.
It sounds like you got a corrupted op/sys or bootloader and a corrupted (or missing) recovery image. The reference to Odin is the mode it is currently sitting in - Odin is the software that Samsung uses to load the images onto the device. You are basically holding a 'raw' SMP-900.
You are going to need to:
1) Download a copy of Odin for whatever operating system you use, i.e., Windows/Mac/Linux
2) Download a copy of an official Samsung Android 5.xx ROM (to get the new bootloader you'll need to upgrade to LineageOS later - trust me, you want this!)
3) Use Odin to load the official Samsung ROM on the device
4) Once you have the device booting up on the official Samsung ROM, you're back in business
5) Download TWRP recovery for this device (v1awifi) and use Odin to install it
6) Root the tablet
7) Install LineageOS
8) Install OpenGapps
9) Install the LineageOS root app (or install Magisk... your choice)
10) finish up the installation with whatever software you want to install from Play Store
Since most, if not all, of this is well documented in various places on this site... the search box can be your best friend. Most everyone here will offer help if you run into trouble, but please search this site first - there are some really, really good instructions and videos of just about everything you will need to do to get the SMP-900 to an nice, usable tablet. Oh, and remember that this is a 32-bit device, so when you go to OpenGapps, make sure you select the 32 bit version.
Good Luck, and remember to read/watch stuff twice, THEN do it.
Thank you so much, friend. This is exactly what I was looking for. I am quite capable of searching and I have been a lifelong of measure twice, cut once.
I have downloaded Odin for Windows, and it recognizes the SMP-900, so that is something. I really appreciate the heads up about Android 10. I wondered about it. Double thanks for the 32 bit warning. I downloaded the 64 bit.
You have given me a clear road map, and I no longer feel lost. I completely understand about searching before asking questions and will try to make any questions I ask focused. People here have been very generous with their time in the past, and as you said there is a lot of wisdom for the asking here.
I think I will track my progress and perhaps put up a post detailing my experience for comic relief if nothing else.
Your reference to Lineage is new to me, but if I understand you, it will serve my purposes.
I will upgrade the SMP-900 to the latest Samsung ROM as you indicated. That makes sense, and I tried earlier, but it would not install.
Again, I cannot thank you enough.
You da bomb!
Thanks again for your help. I am not at Android 5.0.2 and ready to move on with TWRP, boot and lineage. You have made a terrifying process understandable.
Mission Accomplished I think
I followed your instructions carefully and had to do some research along the way. I did not find an official lineageos file for the P900, but did find files here for 14.1 and 17.1. I ended up installing TWRP from Google Play, and once I figured out how to start it, things seemed to go well. Took a while for me to understand not to unzip the zip file. I downloaded
lineage-17.1-20200412-UNOFFICIAL-viennalte
lineage-14.1-20200523-UNOFFICIAL-v1awifi
open_gapps-arm-10.0-stock-20200523
open_gapps-arm-7.1-pico-20200523
to my SD Card. Then, in TWRP, I wiped everything and tried to install lineage-17.1-20200412-UNOFFICIAL-viennalte and open_gapps-arm-10.0-stock-20200523. That did not work. I got some kinds of error or reset message. I wondered if 17.1 was pushing things, so I tried again with lineage-14.1-20200523-UNOFFICIAL-v1awifi and open_gapps-arm-7.1-pico-20200523. That time, it went very smoothly. The device now boots up with LineageOS. It seems to have Android 7.1.2.
My purpose for the table was to watch Hulu, Netflix, Amazon Prime video and Youtube basically. Maybe play games if I ever have the desire. Nothing would loan on 4.4.2. This time, I was able to install everything from Google Play except for Netflix. I kept getting a message that my device was not compatible, but a little searching took me to a Netflix page with a direct download, and now everything seems to working great.
I cannot think of any Android advances after 7.1.2 that I really want or need. It seems to suit my purposes as is, so unless I discover a reason to throw caution to the wind, I think I will leave it as-is.
You took a task that seemed impossible and gave me the guidance I needed to figure it out. I am sure that you saved me at least 20 hours of searching that may not even have been successful. It is so wonderful to encounter people like you who will take a few minutes to help people you don't know. I will always be grateful, and I will think of you every time I start the device. Thank you.