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.
Related
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
I don't have it, but I can look into it...
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
FlynnErik said:
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
Click to expand...
Click to collapse
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
I did a back up after I rooted with CWM
Bibicp said:
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
Click to expand...
Click to collapse
So is my backup going to be rooted? Or will it be the stock? I am currently rooted stock 4.0.4.
Btw, I have found no information about the update anywhere on the net. Maybe they accidently did a push to us, and pulled it back?
Should I wipe cache, dalvik and FDR before I flash the firmware from those sites or use the backup I made already? (which I am unsure if I should even use since idk if it will be rooted or not lol)
I wasn't going to update till it was time to get JB, but this update that vanished is intriguing enough I might lol
As i know yes when you restore backup with cwm the result will be rooted also as the cwm takes image of the system when doing backup and as you when doing backup was rooted so when restore this backup you will be still rooted if you flash via odin no need to wipe cash and dalvik cash i never read anyone doing this
Even if you do this wipe no harm at all
Sent from my GT-I9100 using xda app-developers app
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
There's several reasons why this may happen
Bibicp said:
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
Click to expand...
Click to collapse
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
FlynnErik said:
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
Click to expand...
Click to collapse
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Awesome!
Bibicp said:
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Click to expand...
Click to collapse
So the one on the site even though its XAR is us? Can I ask why we have that tag? Not something like US or etc? I mean I don't care, just kinda curious since that would make it more simple to know which region gets what, at least for me it would lol.
Thank you so much for the help and the knowledge, I figured I would end up with stock recovery, which is why I wanted to make sure about what if something goes wrong.
As a side thought, where does the backup that CWM makes located? Can I copy and paste that on to my PC so I always have a back up handy? (I would sync it into the cloud). Can I flash that with odin down the road? Or is that only a CWM usable file?
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Gizmo said:
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Click to expand...
Click to collapse
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Bibicp said:
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Click to expand...
Click to collapse
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Gizmo said:
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Click to expand...
Click to collapse
Alright, tell me if you notice anything different.
Nice
good!
Im downloading it now. Ill post it when its rooted and deodexed
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
I tried updating it once with KIES and it got to a point and froze on the screen. I had to force the tablet to shut down and rebooted and the tablet was OK. Being a glutton for punishment I tried again with KIES and the LH1 update successfully updated my GT2 7 and the About screen confirms it. Directly after installing and rebooting I started getting error messages about Chrome crashing. I uninstalled Chrome browser and reinstalled it and all is well. No other problems. Do NOT really notice ANY difference at all.
The only problem I have is that NOW I have decided that I would like to root my GT2 7 and I am NOT sure the methods I see out there will work with the P3113UEBLH1 update.
Does anyone know if my GT2 7 - P3113UEBLH1 can be rooted safely??
grobin
I dont think IT is better than CM9
RomsWell said:
Im downloading it now. Ill post it when its rooted and deodexed
Click to expand...
Click to collapse
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Bibicp said:
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Click to expand...
Click to collapse
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
RomsWell said:
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
Click to expand...
Click to collapse
Sorry for the question, but what do you mean comfirmed OTA? Once kies told me about the UEBLG5 update, I couldn't install it with kies as it was lagging.
Next day I found it on the OTA update.
This one showed on kies for a day, then next day neither kies or the OTA udpates showed there was an update so it probably got pulled back?
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
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.
Just saw this:
http://phandroid.com/2015/05/18/note-pro-12-2-lollipop/
I was planning on giving it a try. I don't have any files I need to save on the tablet.
I rooted the tablet recently and am running a rooted stock 4.4.2 ROM. I have titanium backup on there with a lot of stuff frozen, and xposed frame work.
I realizing flashing this lollipop ROM will unroot my tablet, but I'm wondering if I should do some kind of full wipe/dalvik clearing etc? Is there any other steps I need to take before installing a non rooted ROM on an already-rooted device?
I'm running the stock recovery at this time (but could flash something else if recommended.)
i checked out the link. it seems like the update is only for the LTE version (p905), unless im seeing it incorrectly, i wouldnt mind losing root whilst trying the new update
crap... you're right, the article itself refers to the "wifi only" version multiple times, but then the file is for the LTE... what a bummer. Erroneous article. Thanks for pointing it out before I flashed it.
Good catch !
Good catch there, I must admit I got quite excited seeing that lollipop was ready for the Note Pro 12.2!!!. I too have the WiFi version of the NotePRO 12.2'' P-900, and am chomping at the bit for Lollipop, more-so than for my main use phone (Note 3 SM-N9005).
I'm still on the stock firmware, enjoying the tablet as-is, but struggling to find many Apps where the UI has been crafted / coded / mod'd / re-written etc, with a tablet in mind!!
I've been patient to-date re: Lollpop, but will subscribe to this forum thread in case of news . Are there other sources I can / should be subscribed to, that you would suggest? .
Thank you, and cheers... :silly:
Owd-Larrd said:
Are there other sources I can / should be subscribed to, that you would suggest? .
Click to expand...
Click to collapse
Just keep an eye on Sammobile. They're the ones with the firmware and the news. (The original article is from Sammobile.)
http://www.sammobile.com/firmwares/database/SM-P900/
spaceturd3000 said:
Just saw this:
http://phandroid.com/2015/05/18/note-pro-12-2-lollipop/
I was planning on giving it a try. I don't have any files I need to save on the tablet.
I rooted the tablet recently and am running a rooted stock 4.4.2 ROM. I have titanium backup on there with a lot of stuff frozen, and xposed frame work.
I realizing flashing this lollipop ROM will unroot my tablet, but I'm wondering if I should do some kind of full wipe/dalvik clearing etc? Is there any other steps I need to take before installing a non rooted ROM on an already-rooted device?
I'm running the stock recovery at this time (but could flash something else if recommended.)
Click to expand...
Click to collapse
Could you help me out? I have a Note 12.2 that I tried to root when I first got it a year ago. It tripped Knox but still did not get root. I would love to get to where you're at: KK 4.4.2 with TiBu, xposed, etc. Can you point me to some instructions that work?
Vlip3 said:
Could you help me out? I have a Note 12.2 that I tried to root when I first got it a year ago. It tripped Knox but still did not get root. I would love to get to where you're at: KK 4.4.2 with TiBu, xposed, etc. Can you point me to some instructions that work?
Click to expand...
Click to collapse
Sorry for the late reply! If I remember correctly, I used the "near stock untouched" version found here:
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
But I forget! I do know that I have the stock recovery. I rooted/Flashed ROM with ODIN. But didn't install custom Recovery.