Database Info

[Q] G920I

I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.

AAANNNDDDYYY said:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
Click to expand...
Click to collapse
I have the SM-G920I and it's rooted.
Rooting the G920I is apparently not as straightforward as others but still possible.
I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.
Details when I get back from work, or some kind soul decides to help.
There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread

Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?

AAANNNDDDYYY said:
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
Click to expand...
Click to collapse
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.
It is unlikely Spark firmwares have locked bootloaders.
So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.
Use the USB cable that come with your phone and make sure you have the drivers installed.
Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.
Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.
For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.

Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY

AAANNNDDDYYY said:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
Click to expand...
Click to collapse
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.

Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?

AAANNNDDDYYY said:
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
Click to expand...
Click to collapse
Nah, don't bother. The process will retain all your settings and data too.

So just confirm that i can root my g920I with build AOD1 with this meathod?
---------- Post added at 05:45 PM ---------- Previous post was at 05:33 PM ----------
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So just confirm that i can root my g920I with build AOD1 with this meathod?

d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help

s3ct0r said:
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
Click to expand...
Click to collapse
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off

Kjc99 said:
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Click to expand...
Click to collapse
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck

s3ct0r said:
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
Click to expand...
Click to collapse
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation

Kjc99 said:
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Click to expand...
Click to collapse
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success

My carrier is GCI wireless in Alaska, USA... No way to download there firmware...also is twrp it? No more cwm or philz recovery?

Sorry forgot to add current firmware pic

s3ct0r said:
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
Click to expand...
Click to collapse
Cool thanks for the info!

Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...

Kjc99 said:
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Click to expand...
Click to collapse
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic

s3ct0r said:
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
Click to expand...
Click to collapse
Is ktoonsez a stable kernel, I remember using it on my S4 but skipped it last year on my S5 because it had to many tweaks... Can I use it with a stock rom? Alliance?

Upgrading and custom ROM support

Hello, I purchased a new SM-G900P off ebay out of China which came rooted with KitKat installed. I can only assume they put this ROM on to make it universal. It's worked well in general, but I have been having some annoyances with it lately, particularly when related to roaming and some chinese characters that just persist (the CSC codes are CHN and TGY). I would like to upgrade to Lollipop and install one of the custom ROMs that look to be awesome.
My question is: how do I deal with this phone? I can't tell if a recovery is already installed. Can I wipe the phone and upgrade to Lollipop? Should I remove and re-initiate the root access? I am new to android but I've done a ton of reading and I'm quite tech savvy, so if someone can point me in the right direction I would be very appreciative!!

Bump. Even someone pointing me to a link as a starting point would be really helpful!
Cheers.

I'd use Odin to flash to a lollipop/mm stock image. And reroot/install a custom recovery yourself and start completely fresh.

i agree with @InsanePostman. If its an actual g900p (i only say it that way because some chinese products can be cleverly made knock-offs) then get the OK4 tar.md5 and Odin and flash the tar.md5 in the AP slot of odin.
Stock OK4 image
Odin
heres a good thread on a different site showing how to use odin to flash a stock image
and chainfires autoroot

Thanks guys, I'm going to give this a shot tonight. I have confirmed it is a genuine g900p so I'll start with flashing a stock image. Is there some way I can backup my current ROM should anything go wrong I can restore to that?

Install twrp and make a backup. Otherwise as long as you can get to download mode, then you always fine barring the lack of computer or tarball

youdoofus said:
i agree with @InsanePostman. If its an actual g900p (i only say it that way because some chinese products can be cleverly made knock-offs) then get the OK4 tar.md5 and Odin and flash the tar.md5 in the AP slot of odin.
Stock OK4 image
Odin
heres a good thread on a different site showing how to use odin to flash a stock image
and chainfires autoroot
Click to expand...
Click to collapse
Just wanted to say thanks, this worked great! Nice to have Lollipop installed now. I'm in Canada and with this stock Sprint ROM I might look at installing some of the custom ROMs instead to get rid of the SPRINT apps and stuff. Thanks again for the support!

Right on man! Be sure to hit the thanks button when people helped!!

georock said:
Just wanted to say thanks, this worked great! Nice to have Lollipop installed now. I'm in Canada and with this stock Sprint ROM I might look at installing some of the custom ROMs instead to get rid of the SPRINT apps and stuff. Thanks again for the support!
Click to expand...
Click to collapse
Oh, and moar 7.0 is a great touchwiz ROM btw

Flashing stock Roms, Bootloader problems

Hi,
iam glad this place still exits
I've got a S6 (SM-G920F), more or less a testing-device (poor Batterie^^) . It was on Android 7 Stock, may not updated for 6month+, not 100% sure . Was my first mistake, i don't know any more details...
First i tried a few old stock from sammobile (Android 5.1.1 etc.) and tried to flash with odin. As you may guess it didnt work. I thought "Stocks - should be easy " and there are many outdated guides who tell this. I searched for the error messages (onscreen) and found hints that this problems could be caused by Bootloader who deny downgrading, may also for good reasons. I didnt read any deeper, as i found this Guide here: https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
Followed this Guide with https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/DBT/download/G920FXXU2COH2/54694/ as "Source". I worked with the engineering bootloader and the told parts from the Stock. RecoveryMode was broken, but systems seems boot fine and no obvious Errors or Problems. A good guide for that goal, but no guide can teach me whats going up in detail. I want to understand a little bit more, and not searching for a "from any to ANY guide"
Actually iam trying to get on 6.0.1 Stock, but this guide doesnt work for me with a few stock-roms, not booting.
Flashing complete stocks with odin still fails. Flashing dont start or fail at hidden.img.
I came to this page with my first xda, later flashed a lot with my Galaxys...S2-S4, also custom roms- but stayed on stock at some point. So i should have basic knowledge, but i realize its outdated and there a few new "stummbling blocks" etc. Therefore i decided to get more in detail and ask here, before trial and error with other ways (like flashing with recovery)may leads to a brick. Not founded deeper informations myself. In the past i knew which parts a rom/firmware could have and their functions and whats possible with it.
Somebody here with time to help? Where can i find infos which bootloader i got, which others i may can flash (on what way) and which one is working with which Rom^^ Hope that the device wasnt on newest BL, and i still have the choice. Is the Kernel or other parts important as long as iam only trying to jump between stocks?
I backuped efs-partition with TWRP and stored the backup folder on PC, is that enogh to be prevent IMEI lost?
Hints or Links could be enough in some cases.
Thanks for reading and your work

Mattezh said:
Hints or Links could be enough in some cases.
Thanks for reading and your work
Click to expand...
Click to collapse
G920f is international version, so compatible with all roms. Frankly speaking, flashing is basically same as s2 etc. If you're on nougat, then nougat bootloader.
Idk why u want to go to Marshmallow, but some guys managed to flash a Marshmallow custom rom directly from nougat. It's called xtrestolite. It has no support whatsoever. https://forum.xda-developers.com/ga...xtrestolite-deodexed-mod-edition-1-0-t3094423
For TWRP & ROOT, follow the steps in this video https://youtu.be/BV1ELmu8T0I & that's it.
DO NOT USE supersu. USE & flash latest Magisk v15.0+ (stable) from here https://forum.xda-developers.com/app...80cb6-t3618589 Download latest Magisk Manager as well
So the steps are:
From the links in the video, download the specific twrp for g920f. This one: https://eu.dl.twrp.me/zeroflte/twrp-...roflte.img.tar The first file.
Install the Samsung drivers from the link in the video on your pc.
Download & extract Odin.exe.(link in video. Use the same version)
Enable usb debugging on your phone.
Put your phone to download mode
Start odin. Follow the steps in the video to install twrp
When install is complete, immediately reboot to twrp to flash latest Magisk. Wipe Dalvik.
Reboot. Install latest Magisk Manager
Check status in the Magisk Manager.
Done.
If not rooted, flash magisk.zip again in twrp
SuperSu gave problems to some users. Magisk was successfully installed in the first shot!
Nougat roms I'd suggest to flash. They're in S6 unified forum:
MiPa rom, A8 2016 v2, OdexLite v4.1
Try the Nougat roms I've mentioned since you're already on Nougat.
BTW Don't flash any kernels. Stay with those which came with the roms

Is this bricked

I seem to be in and endless loop of hope and despair with my Samsung Galaxy S7 - can anyone shed any light on this?
Long story short, I was on Android 8 and wanted to roll back to 7 (using a ROM I took from Sammobile) because I needed a previous configuration of Google Play Music for my Smart Watch to work. I used Odin to flash the phone and it declared the procedure as FAILED. Now I can't seem to even flash it back to version 8. It is just stuck on the below three screens, no matter what I do.
At this point I would happily just upgrade it to whatever firmware will work and not have a £500 brick on my hands!
Please note the images are at h t t p s ibb.co slash the below (sorry this forum doesn't allow me to post them as links!)
JcwK0vK
55F2cSf
B3Js056
Thanks
Charlie

phikal2013 said:
I seem to be in and endless loop of hope and despair with my Samsung Galaxy S7 - can anyone shed any light on this?
Long story short, I was on Android 8 and wanted to roll back to 7 (using a ROM I took from Sammobile) because I needed a previous configuration of Google Play Music for my Smart Watch to work. I used Odin to flash the phone and it declared the procedure as FAILED. Now I can't seem to even flash it back to version 8. It is just stuck on the below three screens, no matter what I do.
At this point I would happily just upgrade it to whatever firmware will work and not have a £500 brick on my hands!
Please note the images are at h t t p s ibb.co slash the below (sorry this forum doesn't allow me to post them as links!)
JcwK0vK
55F2cSf
B3Js056
Thanks
Charlie
Click to expand...
Click to collapse
OK i've seen them, don't panic.
What region / country are you
What network are you on?
p.s. YOU CANNOT DOWN GRADE OFFICIAL FIRMWARE

I'm with O2 in the UK.
I'd be happy just to get anything installed on it at this point. At least then it's useable.
Whenever I try a new flash (even with Oreo obtained from Sammobile) it just gets nowhere. The COM shows connected (I have the USB drivers installed and have ditched Kies) and I browse to the extracted AP file then click start it either goes away indefinitely not showing failed or success or (with another AP file e.g. for older firmware) it just says Failed.
Thanks very much.

phikal2013 said:
I'm with O2 in the UK.
I'd be happy just to get anything installed on it at this point. At least then it's useable.
Whenever I try a new flash (even with Oreo obtained from Sammobile) it just gets nowhere. The COM shows connected (I have the USB drivers installed and have ditched Kies) and I browse to the extracted AP file then click start it either goes away indefinitely not showing failed or success or (with another AP file e.g. for older firmware) it just says Failed.
Thanks very much.
Click to expand...
Click to collapse
Ok you have to down load the firmware that was on the device from O2, so download O2 Oreo from sammobile or the unbranded BTU firmware and flash with Odin. This should give you access to the device but the google account needs to be bypassed and then wiped by following this method https://www.progeeksblog.com/frp-bypass-apk/

Ok I'll give that a go. Wow pretty detailed guide there. I've not heard of the frp bypass requirement. Another thing to get my head around. Why can't phones just be like PC's. Image them, clone and be done!
Thanks again will let you know how I get on.

Restoring to the BTU firmware posted here forum.xda-developers.com/galaxy-s7/how-to/galaxy-s7-flat-oreo-firmware-download-t3785309 worked! In my case I didn't even need to run the frp-bypass-apk. Turns out that my phone was restored to exactly as it was before I attempted to downgrade so I even have my data back.
Thanks so much for helping me out!

Brilliant. Now to save yourself a world of pain in future turn on OEM unlocking in development options.

Just a couple more questions if you don't mind?
1) What is OEM unlocking
2) Do you know of any way to "roll-back" my version of Google Play Music? I am currently running version 8.14.7427-1H and would love to return to an earlier one since it handles the Android Wear playlist differently.
Thanks!!

phikal2013 said:
Just a couple more questions if you don't mind?
1) What is OEM unlocking
2) Do you know of any way to "roll-back" my version of Google Play Music? I am currently running version 8.14.7427-1H and would love to return to an earlier one since it handles the Android Wear playlist differently.
Thanks!!
Click to expand...
Click to collapse
Well there's some settings on the phone itself which, when you mess up trying to flash etc makes life a whole lot easier to bring your phone back to life. A good explanation of OEM is here https://www.quora.com/Whats-an-OEM-unlock-in-Android
With regards to rolling back Play music yes you can almost always roll back an updated app either by uninstalling the update via settings>apps or finding an earlier version of the .apk file online by simply searching for it in google.
When downloading .apk files, to be able to install you have to enable "install from unknown sources" settings>security>unknown sources.
Hope this helps

Brilliant. Thanks I will give that a go.

flashing twrp via odin

Hi I just got this tablet GT-P5113. It has been a long time since i used odin or did anything with samsung devices. In fact I havent really had to do any modding in years because I switched to nexus/pixel and those just work snappy and clean out of the box. But samsung has far superior hardware so I want to breath new life into this. It is running 4.2.2 now. I dont need to put android 11 on this thing but something like 6 or 7 would be good.
I downloaded odin i see it has changed a bit. so to put twrp on this what part of odin do i use? BL, AP,CP, or CSC?
Most of the stuff on these fourms are outdated and the links dont work. once I get twrp on this I should be food to go and figure out the rest.

I haven't flashed more than 3 devices, but for TWRP it has always been AP in those cases.
If you flash a complete stock ROM it's much more than Recovery, so in those cases you flash separate files like bootloader (BL) etc...
Decide which ROM you want to try and read what Dev recommends in terms of Odin version and TWRP version. But a newer version than recommended should be fine (Odin).
I use 3.09 for my old P3100 but also 3.14 worked for me.
I also recommend getting the same stock ROM you already have from Sammobile.com + make a backup before modding.
For Root I have no recommendation. If Dev recommends Magisk for the ROM, try it and see.
The ROMs I tried was rooted with SuperSU 2.82 even if it's outdated nowadays. Our devices are so old so SU is fine if you ask me.
And most of the time it's SU in the ROM thread by the Dev anyway, so choose ROM and the thread for that and go from there

Android go apps
So I have the latest version of twrp on this and android is running really good and stable. The issue is it has no ram. Just basic with nothing else. Running it is taking up 85% of the system resources.
I found a. Zip that is supposed to. Enable low. Ram. Mode. But it fails on twrp install. It class. To work with devices 4.4.4 and higher. I did disable the Google app and install the lite version which helped alot and I got a memory cleaner app. Supposedly flashing this zip makes the system think it's android go and will allow to install go apps. I think this tablet would benefit greatly fr{m this mod. I was wondering if I have to mod the build. Prop. I will. I. Just want to know.Your thoughts on this matter as always thank. You for your opinions I respect. You and your advice. I found these two files on the web.

mojorisin7178 said:
So I have the latest version of twrp on this and android is running really good and stable. The issue is it has no ram. Just basic with nothing else. Running it is taking up 85% of the system resources.
I found a. Zip that is supposed to. Enable low. Ram. Mode. But it fails on twrp install. It class. To work with devices 4.4.4 and higher. I did disable the Google app and install the lite version which helped alot and I got a memory cleaner app. Supposedly flashing this zip makes the system think it's android go and will allow to install go apps. I think this tablet would benefit greatly fr{m this mod. I was wondering if I have to mod the build. Prop. I will. I. Just want to know.Your thoughts on this matter as always thank. You for your opinions I respect. You and your advice. I found these two files on the web.
Click to expand...
Click to collapse
Are you talking about Low-RAM Property Patcher the thread is here:
https://forum.xda-developers.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373
Perhaps your ROM doesn't support Go features, and in that case the developer has to update the ROM.

Tab_Triggerhappy said:
Are you talking about Low-RAM Property Patcher the thread is here:
https://forum.xda-developers.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373
Perhaps your ROM doesn't support Go features, and in that case the developer has to update the ROM.
Click to expand...
Click to collapse
my rom is 6.0 will the one you linked to work since its for 8?
yeah the rom is basically bare bones aosp. But without anything installed besides gapps nano it uses 80% of the memory. I did disable the google app and install the go app and that helped alot. I am trying to enable low memory mode I found this:https://www.nextpit.com/turn-smartphone-into-android-go-device It says it enables low memory mode and then when you go to the play store all the go apps are availabe. so it looks like it tricks it into tinking that android go is the os. I dont know what the specifice differences are between android and android go besides go is a more stripped down version made for devices with lower end specs. They dont nmake a go version for the galaxy tab 2. Im just trying different things to make it work. This is how I learn how to do things. The great people at xda sharing their knowlage with me.

Tab_Triggerhappy said:
I haven't flashed more than 3 devices, but for TWRP it has always been AP in those cases.
If you flash a complete stock ROM it's much more than Recovery, so in those cases you flash separate files like bootloader (BL) etc...
Decide which ROM you want to try and read what Dev recommends in terms of Odin version and TWRP version. But a newer version than recommended should be fine (Odin).
I use 3.09 for my old P3100 but also 3.14 worked for me.
I also recommend getting the same stock ROM you already have from Sammobile.com + make a backup before modding.
For Root I have no recommendation. If Dev recommends Magisk for the ROM, try it and see.
The ROMs I tried was rooted with SuperSU 2.82 even if it's outdated nowadays. Our devices are so old so SU is fine if you ask me.
And most of the time it's SU in the ROM thread by the Dev anyway, so choose ROM and the thread for that and go from there
Click to expand...
Click to collapse
I did alot of work to get this thing back to life. First sammobile doesnt have the stock files anymore its too old. But one of the guys on the fourm had one and gave it to me. I had an older version of twrp installed and thats why i could not get anything higher than 4.4.4 or magisk. I found a newer version of twrp under the unified galaxy tab 2 development. Once i installed an updated version of twrp I was able to instal android 6 and root with magisk. it even passes saftey net. Now I am trying to disable as much as i can because it is using too mjuch ram. over 80%. It is a work in progress. Thank you for your tips. This is how I have always learned was by asking and the very knowledgeable people here at xda giving me tips. The development community is full of good smart people who like to share their knowledge.

Hello again,
I have the Tab2 P3100 and found stock firmware at Sammobile, but I had to register and become Premium user if I remember correctly. Old firmwares are archived.
Anyway... it looks like the thing I linked is the same that you linked.
I'm going to test it in my tab. My ROM is based on 6.1, will report back
Edit:
No, I get error message when installing zips and can't get it to work. LineageOS.
Best tip I can give is to install everything you want to use and then get rid of Gapps. Well, unless you use some Gapps stuff...

Tab_Triggerhappy said:
Hello again,
I have the Tab2 P3100 and found stock firmware at Sammobile, but I had to register and become Premium user if I remember correctly. Old firmwares are archived.
Anyway... it looks like the thing I linked is the same that you linked.
I'm going to test it in my tab. My ROM is based on 6.1, will report back
Edit:
No, I get error message when installing zips and can't get it to work. LineageOS.
Best tip I can give is to install everything you want to use and then get rid of Gapps. Well, unless you use some Gapps stuff...
Click to expand...
Click to collapse
Yeah gapps are really memory hungry. I dont really need to use this tablet for anything special. Its more the chalenge than anything else. And I learn so much doing stuff like this. Years ago I got y first android phone the lg g2x. Not too long after that I discovered xda and just started reading and asking questions. Then one day I took the jump and learned so much just by asking the devs questions and you know getting them a beer here or cup of coffee there. I love xda for that.