[Q] i535 - Custom Recoveries Cannot Mount Anything! - Verizon Samsung Galaxy S III

UPDATE: See post #5 for the fix. It's really simple!
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.

jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
It should work. Once latest version of casual is done try upgrading to latest version of whichever recovery you are gonna use. All the recoveries in casual are out of date and may just need to reflash recovery. Sounds like gonna use AOSP base so might as well stick with CWM as that is what you are going to end up with and what the AOSP devs support. While on TW can try upgrading it also as it the dev preferred recovery on TW. Shouldn't be the Mac if everything is actually unlocked, rooted and is flashing a recovery.

prdog1 said:
While on TW can try upgrading it also as it the dev preferred recovery on TW.
Click to expand...
Click to collapse
Can you please clarify this particular thought for me? I understood everything else.

jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
You must have a newer GS3, the newer devices (made within the past few months) have a higher revision internal card reader that breaks some recoveries. (I know because I flashed a sprint gs3 that had the same exact issue).
The fix for this is to have a recovery built with the fix in it, which is upstream in the cm-10.2 kernel, but not in any official recoveries yet.
Let me see if I can find the exact commit for you... I know invisiblek fixed it
EDIT: heres the sprint thread of info (DO NOT FLASH THE FILES THO THEY WILL MESS UP THE VZW GS3)
http://forum.xda-developers.com/showthread.php?t=2391616&page=31

I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!

jmsclbwmn said:
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
Click to expand...
Click to collapse
Oh man! Thanks for posting how you got it to work. I've been trying to figure out what to do for almost 2 days.
I would of probably still be googling away if I hadn't found this. Thanks!

Related

[Q] [CM9] (status 7) installation aborted...

Good day everyone.
I've run into a rather frustrating issue I haven't seen anyone solve, especially for this specific phone.
I'm running CM9-alpha5 right now, and I'm trying to flash one of the newer versions but I keep getting this "(status 7) installation aborted" no matter what ROM I attempt to flash now, even when I try to flash alpha-4 in which I was previously running.
I've made sure the permissions are set to read and write for everyone from within my computer(running pangolin ubuntu right now) and alas, the status remains 7.
Luckily I'm able to still re-flash alpha 5 and use my phone but... what gives?
Any help would be appreciated, thanks!
I feel I should clarify that I've been downloading these from get.cm like I have been, and transferring them directly to my sd card.
It feels like an odd permission screw-up, but I'm wondering if either that's not it or if there is any easier route to take than backing up and completely formatting my sd..
You didn't mention what recovery you're on, but I'd suggest trying a different one. There have been issues with some of the ROM Manager versions. We've had good success with:
http://forum.xda-developers.com/showpost.php?p=24085665&postcount=1
cschmitt said:
You didn't mention what recovery you're on, but I'd suggest trying a different one. There have been issues with some of the ROM Manager versions. We've had good success with:
http://forum.xda-developers.com/showpost.php?p=24085665&postcount=1
Click to expand...
Click to collapse
Thanks for the reply! I'm running CWM non-touch v.5.0.2.7 right now. The strangest thing is I came home, downloaded the 6-20 Nightly, and flashed it with success! so I guess the previous point is kind of null now, but I still feel I should update my CWM. Do you have any suggestions as to how I should go about updating from my old non-touch to the new touch? Thanks again for the reply!
barbrastreisand said:
Thanks for the reply! I'm running CWM non-touch v.5.0.2.7 right now. The strangest thing is I came home, downloaded the 6-20 Nightly, and flashed it with success! so I guess the previous point is kind of null now, but I still feel I should update my CWM. Do you have any suggestions as to how I should go about updating from my old non-touch to the new touch? Thanks again for the reply!
Click to expand...
Click to collapse
Sure, there are instructions in the post that I linked describing how to flash a recovery tar via ODIN.
cschmitt said:
Sure, there are instructions in the post that I linked describing how to flash a recovery tar via ODIN.
Click to expand...
Click to collapse
Installing on linux... not so fun. I said forget it and came to use my parents windows machine to just easily use ODIN real quick. I wasn't sure if I had to do any specific backups or anything before flashing but, nope, it was simple enough. Thanks again for your help!

[Q] Cannot use Clockworkrecovery Mod

So last night I decided to root my Verizon Samsung Galaxy Note II and used this thread as a guide: http://forum.xda-developers.com/showthread.php?t=2024207. All worked fine in the end, no problems. So today I decide I want CM10. So in the guide to install CM10 I am instructed to use CWM to do the actual installing part. Well, I have used ROM Manager and a plethora of alternative methods. Not a single of them work. Every time I try to boot into CWM I get this menu titled: Android system recovery <3e>, not the CWM one. Even the actual ROM Manager app says I have CWM installed properly. I would appreciate any help.
Also note this is my first Android device I've ever owned, and am a total noob to the entire rooting community.
I guess CWM cannot be upraded by ROM manager, try other method mentioned in your device forum to uprage it really.
keep tryin'
Lepryy said:
So last night I decided to root my Verizon Samsung Galaxy Note II and used this thread as a guide: http://forum.xda-developers.com/showthread.php?t=2024207. All worked fine in the end, no problems. So today I decide I want CM10. So in the guide to install CM10 I am instructed to use CWM to do the actual installing part. Well, I have used ROM Manager and a plethora of alternative methods. Not a single of them work. Every time I try to boot into CWM I get this menu titled: Android system recovery <3e>, not the CWM one. Even the actual ROM Manager app says I have CWM installed properly. I would appreciate any help.
Also note this is my first Android device I've ever owned, and am a total noob to the entire rooting community.
Click to expand...
Click to collapse
eldongal said:
I guess CWM cannot be upraded by ROM manager, try other method mentioned in your device forum to uprage it really.
keep tryin'
Click to expand...
Click to collapse
Dang. I've tried pretty much everything. One of the update methods says to put it into download mode to update via Odin. Every time I try to do that it takes me to that Android system recovery menu I talked about.

Full on Noob, need help if possible.

Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:
I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9
Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:
Goodluck! :laugh: :good:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt

Trying to update twrp..."trying"

I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Google "Nexus Root Toolkit". Works great with Windows 8.1.
rhyang said:
Google "Nexus Root Toolkit". Works great with Windows 8.1.
Click to expand...
Click to collapse
I found something after a lot of searching and reading around back and forth on different places, thanks, I will keep it in mind anyway cause right now there is not that many sources for info on Nexus S.
fenrry said:
I found something after a lot of searching and reading around back and forth on different places, thanks, I will keep it in mind anyway cause right now there is not that many sources for info on Nexus S.
Click to expand...
Click to collapse
I have uploaded TWRP v2.8.0.1 flashable zip. Flash it like any normal ROM in the existing recovery.
Link: http://forum.xda-developers.com/showpost.php?p=55616780&postcount=115
Also, let me if you need help in installing drivers in Windows 8. I too am using Nexus S on Windows 8.1
smit.sanghavi said:
I have uploaded TWRP v2.8.0.1 flashable zip. Flash it like any normal ROM in the existing recovery.
Link: http://forum.xda-developers.com/showpost.php?p=55616780&postcount=115
Also, let me if you need help in installing drivers in Windows 8. I too am using Nexus S on Windows 8.1
Click to expand...
Click to collapse
Thanks so much fo the Zip, is way easier to just have this done via TWRP/ZIP, than trying to install drivers and so on, it becomes a pain when one thing fails and then u have to start downloading files drivers and more.
Now I'll just start checking roms!
fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Hi There,
The latest Recovery for Nexus S is TWRP v2.8.x. Well u will need to flash the Twrp v2.8.x using fastboot because if you try installing the recovery using the TWRP Manager it will crash. I have a guide on how to root nexus s in the nexus s development section..Go through it . If you have a rooted Nexus S then skip to contect showing how to flash a custom recovery using Fastboot in my guide go through it and Enjoy..
Happy Flashing.
Good Luck
fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Hi there,
i just made a .doc in which i have briefly described how to flash twrp on nexus s just download the file and go through it.
Thanks!, I forgot to reply about this, I managed to get things working, I really don't know how it happened but after repeating the steps several times something must have kicked and things finally worked.
fenrry said:
Thanks!, I forgot to reply about this, I managed to get things working, I really don't know how it happened but after repeating the steps several times something must have kicked and things finally worked.
Click to expand...
Click to collapse
Ok Brother, Chill and Enjoy.

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.

Categories

Resources