Related
And every other step you need to transform and gain control of your stock ROM!
Given the fact that T-Mobile and Samsung have made it clear that the Galaxy S Vibrant will not receive Gingerbread, Honeycomb, ICS, or any other functionality update, I made the decision that it was finally time to root my beloved phone.
I didn't want to root for the purpose of trying a ROM for any of the above OS's. I merely figured that since there are not going to be any future updates to my phone, I'm basically on my own. And if I'm on my own then I can and should get rid of the TMo crap software that came pre-installed on my phone (and which can't be uninstalled by any normal means).
Hopefully this process might also help make my phone operate a little faster and cleaner. And in general, the rooting process would give me full control over my own phone. But if you have ever rooted a device the experience can sometimes be challenging, even for tech-savvy folks like me.
There are lots of sites for advice and how-to’s on rooting your Android device, but most of these sites run you through the process in a way that assumes all will work perfectly the first time. There aren't a lot that take you through the root process with at-hand solutions to many of the commonly reported errors.
I've just finished rooting my stock TMo Vibrant, fixing signature/Multi-CSC issues from the root process, installing and using Titanium Backup (TB) PRO to handle bloatware, and finally installing ROM Manager for the purpose of installing ClockworkMod Recovery (for creating and restoring backups of my current ROM). WHEW! And while it's all fresh in my mind, I'm writing it all down to share the process with you so that it's all in one convenient place.
Let’s Start With Rooting The Phone By Using Super Oneclick
After doing some reading in the XDA forums and a few other places, I wanted to try rooting with a one click option. There are many out there that are available for use. But the very first issue that plagued my rooting process was the incompatibility of many of these root installers with my home Win7 64bit pc.
I tried downloading and extracting various recommended solutions that use the "one click" functionality (Super Oneclick--various versions with and without drivers, Galaxy S One Click Root, and Vibrant One Click Root). I also downloaded and installed AIO Vibrant Toolbox, a program which also features a “one click” method for rooting a Vibrant once it has been installed on your pc.
What many posts on rooting never really mention with these methodologies is that you might have issues running the programs on a Win7 machine, which was my issue. Not all Win7 machines, but some. I downloaded the zip file for each with generally with no issue. * But once I tried to run the exe (best done via "Run As Administrator"), I got the following error message on virtually all of them:
"CLR Error: 80004005 The program will now terminate"
AIO Vibrant Toolbox wasn’t any better even though it was an installed program. It terminated as well.
(*NOTE: Anti-virus programs will mistake parts of the root zip files for Trojans, usually quarantining them after download. You are then left with the uncomfortable choice of turning off your anti-virus and taking that chance, or looking for another zip solution. I opted for the latter. Never take a chance with a Trojan!)
These errors messages did not show up on my work pc which is also Win7 64-bit. But that was no comfort as most of my root work was going to be done at home. After much searching on the internet, I read a random post that mentioned two helpful suggestions:
Use a rear or powered USB port, not a front port (because they often can’t power the root install sufficiently)
Use Super Oneclick v1.7 as opposed to any newer versions. The newer versions can cause problems with this particular Galaxy S root.
Two simple suggestions that made a world of difference! The root process worked smoothly afterward, and was finally a "success".
Reminder - Remember to put your phone into USB Debugging mode for the root process, and don’t mount the external SD card when attached.
Along the way to “rooting” you might be confronted with messages about your Samsung drivers for your phone. You may see messages like these:
Device drivers not found
Samsung android USB composite device failed
A quick search on these forums will yield updated drivers for your phone. The successful install of these drivers can also be a function of using the proper USB ports, as in the situation above. The installation of Samsung drivers failed on the front USB ports of my Dell. Success was again found using the rear ports. The main point here: use the rear ports (or powered USB ports) no matter how much of a pain it is maneuvering under your desk and behind your pc!
You’re Almost There…Kinda!
You can check to see if you are successfully rooted by checking to see if Superuser is installed in your apps. It was there… whew. The next step was to install Titanium Backup so that I could have root control over my apps, allowing me to delete bloatware that was slowing my phone. I downloaded TB from the Market, opened it, tried to give it Superuser permissions, and was notified with an error message that permissions were unsuccessful because the phone was not rooted. WHAT???
More online research revealed that I had achieved a “soft root”, whereby you have successfully rooted your phone but you don’t have all root permissions because the install wasn’t complete. The solution? Basically you just have to keep doing it more than once. All steps of this process seem like they will take the first time if you do what you are supposed to do. But more often than not, you have to repeat your steps over and over to make sure that it takes. After two more Super Oneclick rooting attempts, TB finally gave me the thumbs up for root.
Some may say it’s not necessary, but I upgraded to TB PRO. It allows for more options and better functionality with the apps and system data on the phone. And really, at about 6 dollars it is more than worth the price. Heck, two Starbucks lattes will run you more than 8 or 9 bucks. So if I can get piece of mind with respect to app management on my newly-rooted phone, 6 bucks is more than worth it.
I immediately wanted to learn how to remove bloatware -- and it’s amazingly difficult to find clear directions on doing so. After my backup of all apps and data, I went to the backup/restore tab and found the programs I wanted to get rid of. Many online users recommend “freezing” an app first to make sure that removing it won’t make your phone all wonky. So after “freezing” the offending apps (by pressing the menu button, selection batch, and then scrolling down to the appropriate section on freezing apps), I long-pressed the desired app and only saw one option for uninstalling via an exploit. I selected it and long story short, it failed. As the phone boots to stock recovery, this message popped up:
E:failed to verify whole-file signature
E:signature verification failed
Applying Multi-CSC Installing
Multi-CSC Installation Aborted
In simple terms, the rooting tool (Super Oneclick) doesn’t contain all of the necessary items for a complete root. A fix is needed for the invalid signature problem that will help you get to a full root state. Fortunately there are fixes out there you can find for this particular fix.
Here are some helpful links:
http://androidforums.com/galaxy-s-a...iled-installation-aborted-one-click-root.html
http://forum.xda-developers.com/showthread.php?t=1052991
Read the instructions for the fix on the first page, but get the correct file from the second page as the link for the fix from Dropbox is a little messed up in the first URL. The second URL has the correct link. Use the automatic method so that you don’t have to use the terminal emulator. If you are like me, this process has already given you more gray hairs than you would really like to admit. So take the easy route.
Run the install.bat file and you will be fine. When you reach stock recovery again remember to reinstall all packages. This will make sure that the fix is installed properly. I didn’t know that was needed and was wondering why the fix wasn’t taking initially. So I’m sharing this with you to head off your frustrations at the pass. ;-)
Getting Rid Of The Bloat
Check to make sure that you are fully rooted by opening TB. It will automatically take Superuser permissions from the first time you allowed it IF you are rooted. If not, it will tell you. And by now you should be rooted. Heading back to the bloatware, I was able to figure out that the “long press method” was not the correct one for uninstalling apps.
Once again, press the menu button (bottom left) and select batch. Scroll down and you will see a section for uninstalling apps. Select uninstall user and system apps, and make sure to DESELECT ALL before you do anything else. From there you can pick and choose the apps to uninstall, then “run the batch operation” to complete the task. Bye bye bloatware!
The last crucial step to complete now that your phone is rooted is to make sure that you have a backup of your current ROM and configuration. The backup you created using TB is only for apps and data. It is not a backup of your current stock ROM.
Nandroid backup works best for the purpose of backing up and restoring ROMs. And if you have done any previous rooting on an Android device, you will recognize that Nandroid is a function of ClockworkMod Recovery. Sigh. I know... frustration starts to set in as you realize that there is yet another necessary install needed for a totally successful root process ON TOP OF and AFTER everything else you have had to do. So what is the next step?
ROM Manager To The Rescue
Install the free ROM Manager from the Market and you will be good to go. This app allows you to flash CWM Recovery as well as mount various ROMs on your phone. After installing the app (and declining the various offers that pop up), press “Flash ClockworkMod Recovery” at the top of the menu. It will cause the phone to reboot. And CWM will be downloaded…but not installed. To install after reboot, open ROM Manager and now select Reboot into Recovery. It will challenge you with a question on whether you really want to do this or not. Say Yes.
Important: This is another one of those places where it’s not intuitively obvious what to do for CWM Recovery.
When I first rebooted into recovery I didn’t see any changes from my stock recovery menu…because there were none. What I needed to do (which I found in yet another forum posting) was again to select Reinstall all packages. CWM had been downloaded and was ready to install… this would do so.
Happily, the phone went into Clockwork recovery*immediately after "Reinstall all packages" . If it wasn't clear earlier, use the volume buttons toggle up (or down) to select backup/restore. *You can then implement your selection by pressing the power button on the right side of the phone. On the next screen select backup, and then let it do its’ thing. It may take a while to complete, but will be well worth the time and effort if you have any future problems.
The Entire Process Is Finally Complete
So there you have it. In a nutshell, here were my steps:
1. Samsung drivers
2. Super Oneclick v 1.7
3. E. Signature fix
4. Titanium Backup PRO
5. ROM Manager (free version)
Use the rear USB ports or powered USB ports for the phone connection. Phone should be in USB debugging mode, and external SD card should not be mounted. For each process, it may take up to 2 or 3 attempts for successful completion. So keep trying after the first FAIL message. When applicable, “Reinstall All Packages” to make sure that downloaded files are actually installed.
And lastly, if absolutely nothing works correctly for you, PLEASE PLEASE PLEASE use Google for help. Many others have successfully worked through all of the problems you might encounter that aren’t listed here. Actively use Google to help find solutions to any problems, using the exact error messages shown and adding in your phone type. You will be amazed by the depth of experience out there that can help you.
Above all else, keep up a good attitude. Rooting might be a pain in the ass while you are doing it, but it’s for a greater purpose. My four days of rooting have now given me a phone that is FREE from all the bloatware that bugged me for the past two years. And soon I’m sure I will experiment with a different ROM. But for now I’m just happy that I have my phone, my way. After all, if they (TMo and Samsung) aren’t going to make our phones better, we can do so for ourselves.
Good luck, and I hope this complete set of instructions from my own past 4 days of experience will help someone else!
A good read. A few things though with the Titanium part.
First I whole-heartedly agree to kick down the $ for the Pro. It really ups the functionality of the app and what all it can do.
The part about "freezing". This part is tricky b/c you need to make sure he apps that you are freezing are indeed bloat and not something that is needed for something else (i.e. did you know that GTalk directly effects the market on some ROMS). I don't use Gtalk but I still have it installed and frozen so I can defrost at will. This is the reason for Freeze. It lets you know of any adverse effects on your ROM, other apps,...then you have the option to defrost if need be. I also always avoid doing anything in "Batches" on TBPro, as it can sometimes be a little wonky, especially when restoring batches, causes reboot and freezes resulting in batterty pull.
I freeze for at least a week on new ROMs so that I get the full experience with daily life to make my determination on uninstall, defrost or wait longer.
Another way to do it is once you know the apps that are frozen do not effect any other parts of your ROM, you can back them up with TBpro for later use and uninstall or you can do it this way. Since you have root, go into /system/app or and pull the APK out and put it in a folder or something like that on your SD card. You would do this to some of the /system apps that TB shows as only haveing a checkmark next to and not the yellow/orange circle with the M in it. If you uninstall these with the checkmark you will not be able to restore them b/c part of the executable portion of the APK is not able to be backed up. This is the reason to pull the app out of /system/app and put it on your SD card. Hit menu, more, Clean up Dalvik cache and viola!! you have some free space on /system and the offending APK's dex will be deleted too.
Sidenote: I have never been able to get SuperOneClick to work on any phone I have ever tried. Maybe I'll unroot and try again but the SU exploit is a flashable zip located here. Option A. Put it on your SD card, boot into recovery and Bam!!! you are rooted
Nice work though.
Where can we still get Super Oneclick v 1.7?
http://forum.xda-developers.com/showthread.php?t=739300 make sure you have ADB turned on and use the USB ports from the back not front
too lengthy.
Just got vibrant
Sent from my SGH-T769 using xda app-developers app
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Delete..
In trying to free up some space on my KF today, I noticed that apps that I had uninstalled, both before and after I rooted my KF, still left the entire app on my KF.
What's up with this?
For example, one of the first things I installed, kinda jokingly, was the Nook app. This was days after I got my KF and I had also downloaded a few free books for it. I uninstalled that app 6 months ago, yet all the Nook files were still there, including the .apk. I was able to delete them all and not cause any noticeable problem with my KF, but I have d/l'd a lot of apps and deleted them since I got my KF on the first day it was released. So if it had an easy name to remember, not too big of an issue, but app names in the directory aren't always straightforward to what they are... they may be listed by their developer's name or such.
I'm not opposed to completely wiping it and re-installing everything, but there are a number of games that I would lose my progress in if I did that. Plus, I am not in desperate need of space... yet. Granted, the TWRP backup doesn't help much when it comes to space, but it is a nice thing to have.
[BTW, my KF has been rooted for several months now, and was just updated with the latest KFU v9.6, running GoLauncher. It's a pretty straight forward rooted device that I haven't tweaked much because I really do read a lot on it.]
So I was wondering if there was an app that works better than the free version of SD Maid to clean up all this left over garbage? Even SD Maid didn't detect the Nook app still being there (the free version doesn't do all the paid version does, but, for the most part, it still shows ya what it found). Or if someone has a detailed guide of walking you through how to clean up useless files... that would be cool too.
Like I said, there is definitely a lot of crap taking up space that can be deleted. But I don't know Android (I'm really a Windows/Cisco guy), so I don't know to what extent I can delete stuff without causing problems.
Any help would be appreciated.
BTW, could the Image Verification images be any harder? LOL
PBFred said:
In trying to free up some space on my KF today, I noticed that apps that I had uninstalled, both before and after I rooted my KF, still left the entire app on my KF.
What's up with this?
Click to expand...
Click to collapse
I believe this is an issue in older Android versions. I noticed my phone doing the same thing while it was in Eclair, then in Froyo and then in GingerBread.
It looks to me like ICS will automatically remove any orphan data it finds - I've tried deleting just an application's apk and, after rebooting the system, its data was gone as well (tried on both my phone and KF).
PBFred said:
So if it had an easy name to remember, not too big of an issue, but app names in the directory aren't always straightforward to what they are... they may be listed by their developer's name or such.
Click to expand...
Click to collapse
I guess you can try "pm list packages -f" to get the names of the apks and their matching data folders.
PBFred said:
I'm not opposed to completely wiping it and re-installing everything, but there are a number of games that I would lose my progress in if I did that.
Click to expand...
Click to collapse
You can most likely extract their data. Alternatively, you may want to look into Titanium Backup for backing up both apps and their data.
PBFred said:
Granted, the TWRP backup doesn't help much when it comes to space, but it is a nice thing to have.
Click to expand...
Click to collapse
You could also move the TWRP backup to the computer...
I would just backup any apps/games on TB while also saving the contents of your SD on your computer. Then simply use TWRP to wide SD card. You can then move your TWRP backups to the SD card from your computer and restore app and data on TB.
Hey guys I've been browsing around simply everywhere trying to find a fix to my issue but haven't been able to so I thought I might post on here to see if I could get some help.
Simply put, I downloaded luckypatcher a fair while ago and tried removing some adverts as well as trying to apply a patch to an application I got, in doing so I believe I may have screwed my phone up because now I can't install updates from most of my applications and some applications cannot be installed at all and I'm basically screwed with no fix at all for myself. Along with that I have 1.8 gigs of free space left so it can't be the issue of storage and I've already tried looking in the data/app-libs folder through root explorer but there isn't one nor any odex files of any sorts, also tried fixing it through lucky patcher to by fixing the permissions in the troubleshoot menu to no avail.. any ideas?
Thanks! -zeksta
First of all, thanks a lot to Cpasjuste for making the working gapps flashble zip, here's a link to that. I take no responsibility for doing this, all credit goes to Cpasjuste. Also I do not know a lot about deving myself but i've had two android devices before this and have been avid in modding them, just thought i'd put that out there.
So, first thing I did was get root, factory reset and get safestrap recovery. then I made a backup of my stock ROM, kept it on my kindle, and moved it to a safe spot in my computer (I recommend everyone does this, no matter if they choose to follow this setup or not.) I created a new ROM slot with default partitions, and restored my stock ROM to it (you do this in case any thing happens you have your stock ROM to fall back on). I tried flashing Cpasjuste's gapps rom, but for some reason there were multiple issues with it so instead, i restored to stock, on ROM slot 1, and flashed his gapps zip mentioned earlier. Rebooted and everything (well almost everything) worked perfectly. playstore works and only app that I have discovered to be incompatible is instagram for some reason, but i found a apk download online that installed perfectly to replace it. I installed a app from play store called recent apps quick button, which basically activates android's recent apps, then I installed a app from play store called Home2 shortcut. this lets me assign the resent apps quick button to double tapping the home button so now when i double tap the home button it brings me to recent apps. It's really nice since kindles default Rom doesn't have a recent apps button! Right now I am working on blocking updates from amazon to prevent losing root or bricking, using the tutorial found at the end of the root link. Let me know what you guys have done to make your kindle fire HDX experince better, or any questions you have.
Also, I forgot to mention that using the gapps flashable zip broke my amazon appstore and most amazon services, except video it seams like, but since we have safestrap recovery this isn't a big deal to me because i can always get it back, and im sure it will be fixed in future. Have fun and be safe while experimenting with your kindle.
I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO YOUR DEVICE, KNOW WHAT YOUR DOING BEFORE YOU DO IT!!!!!!!
Ah! Thats what I missed, I didnt realise I could use restore on a different ROM slot! Thanks for that, going to try it later!:good:
OurFriendIrony said:
Ah! Thats what I missed, I didnt realise I could use restore on a different ROM slot! Thanks for that, going to try it later!:good:
Click to expand...
Click to collapse
No problem! Also if I were you I would delete most of the user apps on your stock ROM, Idk if you did what I said and factory reset before you got safestrap (I would not try it if you already safestrap since you will lose safestrap and possible break you device!) but if you didnt I would just go back and delete most user apps and data off stock ROM and then redo the backup and restore with that. because you most likely wont be using the stock ROM (you don't want to alter it since you want to have a safe spot to restore to) you want it to take up as little storage as possible. My advice, pretend that you don't have root and don't do anything with it, like editing parts of system, or flashing mod packages, etc... (only exception is having super user and safe strap app installed.) Let me know if any part of this was to confusing. Hope this helped!
Haha, I saw your reply about 2 minutes after starting up the factory rest. I can, however, confirm that safestrap is still installed between the boot and IS load, so I'm actually in a perfect position. Have taken a new backup of pure stock rom!
Happy days!
I got a copy of my Stock ROM installed into ROM slot 1 and then added the gapps package, it worked beautifully!
I now have a tablet with all the google features on and have no issues so far.
except...
when I boot to ROM slot 1, I get a message saying "Kindle is Updating/Upgrading". It doesn't do anything and it only takes a few seconds before it gives up. I was just wondering if there was a way of getting rid of this??
As someone who hasn't had any prior experience with Android (although a fair share of experience with GNU/Linux), I appreciate a thread like this.
I also rooted the device (works well from GNU/Linux), installed SuperSU and some essential apps to make the stock OS usable (busybox and a terminal emulator, of course; and also a lightweight file browser that doesn't take much space and does exactly that, lets me browse local files). Then installed SafeStrap and backed everything up to both the Kindle and the PC (the backup is accessible via MTP, in the internal storage, so you can just connect the USB cable and copy the TWRP directory – at least in KDE).
Now I'm going to try the new AOSP ROM. Though since I'm new to the whole Android business, the partition sizes have me a bit confused. I'd want to have three slots – the stock ROM (obviously), the stock FireOS (one that I can modify) and AOSP. What partition sizes for the two slots would be the best, if it's the 16GB HDX? Also, say I download a PDF file; would both FireOS and AOSP see the file if I put it in internal storage, or would I have to manually copy it over to the other slot through my PC?
@GreatEmerald, whats AOSP? I'm thinking of playing around a bit more. I want to try out some more ROMs.
I put my first ROM slot (Stock with gapps added and amazon crap removed) on Flight Mode and now when I try and put it on wireless it restarts....
OurFriendIrony said:
@GreatEmerald, whats AOSP? I'm thinking of playing around a bit more. I want to try out some more ROMs.
I put my first ROM slot (Stock with gapps added and amazon crap removed) on Flight Mode and now when I try and put it on wireless it restarts....
Click to expand...
Click to collapse
AOSP = Android Open Source Project
Many other devices have an AOSP build and is typically a very nice build to flash if you like the core android feel with some extra very nice features.
OurFriendIrony said:
@GreatEmerald, whats AOSP? I'm thinking of playing around a bit more. I want to try out some more ROMs.
I put my first ROM slot (Stock with gapps added and amazon crap removed) on Flight Mode and now when I try and put it on wireless it restarts....
Click to expand...
Click to collapse
Yea, as mentioned, AOSP is a ROM for stock Android 4.2.2, pretty much the only big ROM available for the HDX7 right now: http://forum.xda-developers.com/showthread.php?t=2607185
It works pretty well as it is, I'm impressed it's as good already given how new the project is. Though it still has some issues for normal use. Aside from the bugs mentioned in the post, Chrome crashes as soon as it's launched (but you can use Firefox instead), as does the Kindle app (which is mainly what is stopping me from using it, because the point of a Kindle is the integration with Amazon services...). Also, the Facebook app fails to install for some reason.
Everything else I tried works fine. I installed F-Droid, a file manager, Busybox and a terminal, then the Amazon app and some of the Amazon cloud apps, and finally Skype. All of them work very nicely on AOSP. Even tested a video call on Skype and it worked without any problems (including the camera working correctly).
As someone new to Android and from a GNU/Linux background, I'm really happy that F-Droid exists. It's an app store/package manager that offers only free and open source software. For regular users that might sound as not a big deal, but actually filtering software by license is more powerful than one would think. You're guaranteed to have only apps that have no spyware and adware, because you can't hide them in open code. And those who make apps without publishing their code obviously have something to hide. So much like in GNU/Linux, the first place to check for new apps for me is F-Droid, and after that the main store of the OS (be it Google Play or Amazon Store), and only then 1Mobile market.
I still would like to know more about that partitioning, though. I figured out that the emulated SD card is shared between ROMs (I uploaded F-Droid to the Downloads directory on FireOS, and could see it on AOSP just as well), but I still don't know what exactly the two partitions you have to make to set up a ROM slot are and how much space should be allocated to them.
GreatEmerald said:
Yea, as mentioned, AOSP is a ROM for stock Android 4.2.2, pretty much the only big ROM available for the HDX7 right now: http://forum.xda-developers.com/showthread.php?t=2607185
It works pretty well as it is, I'm impressed it's as good already given how new the project is. Though it still has some issues for normal use. Aside from the bugs mentioned in the post, Chrome crashes as soon as it's launched (but you can use Firefox instead), as does the Kindle app (which is mainly what is stopping me from using it, because the point of a Kindle is the integration with Amazon services...). Also, the Facebook app fails to install for some reason.
Everything else I tried works fine. I installed F-Droid, a file manager, Busybox and a terminal, then the Amazon app and some of the Amazon cloud apps, and finally Skype. All of them work very nicely on AOSP. Even tested a video call on Skype and it worked without any problems (including the camera working correctly).
As someone new to Android and from a GNU/Linux background, I'm really happy that F-Droid exists. It's an app store/package manager that offers only free and open source software. For regular users that might sound as not a big deal, but actually filtering software by license is more powerful than one would think. You're guaranteed to have only apps that have no spyware and adware, because you can't hide them in open code. And those who make apps without publishing their code obviously have something to hide. So much like in GNU/Linux, the first place to check for new apps for me is F-Droid, and after that the main store of the OS (be it Google Play or Amazon Store), and only then 1Mobile market.
I still would like to know more about that partitioning, though. I figured out that the emulated SD card is shared between ROMs (I uploaded F-Droid to the Downloads directory on FireOS, and could see it on AOSP just as well), but I still don't know what exactly the two partitions you have to make to set up a ROM slot are and how much space should be allocated to them.
Click to expand...
Click to collapse
The system partition only needs to be as big as the Rom or backup you flash is, the data partition I typically make as big as possible (4000 mb) since this is what your Rom will consider internal storage. This is where apps and app data will be downloaded onto, where the rest of the data on your ad card is shared and is used for music, videos and lots of other custom stuff you can add. As for the cache I leave it at the default, this is where temporary data for apps is stored ( for example when you play a youtube video, it is temporarily stored on this partition.
spaghettiknight said:
The system partition only needs to be as big as the Rom or backup you flash is, the data partition I typically make as big as possible (4000 mb) since this is what your Rom will consider internal storage. This is where apps and app data will be downloaded onto, where the rest of the data on your ad card is shared and is used for music, videos and lots of other custom stuff you can add. As for the cache I leave it at the default, this is where temporary data for apps is stored ( for example when you play a youtube video, it is temporarily stored on this partition.
Click to expand...
Click to collapse
Ah, that's good to know. It makes me wonder, though – can I resize partitions in some way? Say, I created a smallish partition setup for ROM slot 1, then another one for ROM slot 2, and then have a bit spare; can I allocate the whole space to ROM slot 1 if I no longer need ROM slot 2? Or to do a backup, clear the partition setup, then restore the backup into newly sized partitions?
GreatEmerald said:
Ah, that's good to know. It makes me wonder, though – can I resize partitions in some way? Say, I created a smallish partition setup for ROM slot 1, then another one for ROM slot 2, and then have a bit spare; can I allocate the whole space to ROM slot 1 if I no longer need ROM slot 2? Or to do a backup, clear the partition setup, then restore the backup into newly sized partitions?
Click to expand...
Click to collapse
yes, what i would do is backup my current setup, delete the rom slot your using, then remake it with your newly picked partitions
Nevermind. Got it working now. Thanks for the guide!
safestrap not working on my kindle hdx 7"
Hi my kindle is already rooted and I used towelroot. I have supersu installed too. I'm currently on the step of where I should install safestrap, but it seems safestrap is not working on my tablet. I tried 3.65, 3.72, 3.75 version of safestrap but it does not work. It always restart normally. Not in recovery. Pls help. 13.3.2.8 version. Thank u in advance.
pinksummer17 said:
Hi my kindle is already rooted and I used towelroot. I have supersu installed too. I'm currently on the step of where I should install safestrap, but it seems safestrap is not working on my tablet. I tried 3.65, 3.72, 3.75 version of safestrap but it does not work. It always restart normally. Not in recovery. Pls help. 13.3.2.8 version. Thank u in advance.
Click to expand...
Click to collapse
Have you blocked OTA with HDX Toolkit? If not your device will likely brick if Amazon attempts to push an update. At present the blocker in HDX toolkit is the only one that works on 3.2.8.
Your attention should be focused on this task; can deal with safestrap once OTA block is in place.
ya I had to learn about that the hard way
Hi all.
Dug an original 2012 nexus 7 (16GB) out of the drawer to see if it could be refreshed a bit and brought back in to some sort of use.
I've put Lineage 14.1 on it and rooted with the nexus toolkit but I had to install the pico Gapps as there is only 689mb of system space. I've trawled the internet looking for a solution on how to make the system partition slightly bigger to accomodate a larger rom and all i came up with was using "Parted" to try and resize the partitions. I've tried everything but i can't get a reading from mmcblk0. Keeps telling me that there's no such file or words to that effect. I know it's there because i can see it. I'm clearly doing something wrong in adb. I see Roms for CRDroid that combined with Gapps pico are too big to fit on. They've been made so there's obviously a way to get them on there that i'm missing.
Would anybody be willing to give me a guide on how to get the system partition bigger?
Thanks very much
There is no possibility to re-orgainize partition sizes for the Nexus 7. The only idea which could work in my opinion: create an image file on the /data partition, move the content from e.g. /system/apps there and bind mount the image file to /system/apps
Unfortunately this new concept needs to be supported by your custom recovery, too, otherwise you would not be able to install any app. Long story, short answer: much work to be done and it's not really needed as you can download almost all Gapps from the playstore and then these apps will be installed on the /data partition.
Btw. custom ROMs occupying too much space on /system probably should try to reduce the number of supported languages / features or renounce on pre-compilation of the build-in apps. First startup will take longer but on the other side you gain some additional space ... Just a hint.
Try google "nvflash" for Nexus 7. Attention! This is a low-level utility, if used improperly and there are no backups, RESTORE THE DEVICE WILL BE IMPOSSIBLE!!!
I strongly do not recommend this, the risk of turning the tablet into a brick is very large.
Instead, you can use root file explorer to remove unnecessary system applications and files (for example, media - boot animation, sounds, etc.) to free space.
gmikhail said:
Try google "nvflash" for Nexus 7. Attention! This is a low-level utility, if used improperly and there are no backups, RESTORE THE DEVICE WILL BE IMPOSSIBLE!!!
I strongly do not recommend this, the risk of turning the tablet into a brick is very large.
Instead, you can use root file explorer to remove unnecessary system applications and files (for example, media - boot animation, sounds, etc.) to free space.
Click to expand...
Click to collapse
Hi.
Spent the last hour or so trying to decipher what nvflash actually was. I think the penny has dropped. You wern't recommending it as a way to get more space. You were potentially recommending it as a failsafe so i could mess about with the partitions without bricking it????
Anyway, thanks very much. I think i'll just have a look at uninstalling some of the non required files to free up the space. I assume the best way would be to install the ROM of choice, go in and uninstall stuff and hopefully if enough space has been created, be able to flash gapps?
@blueplasticsoulman probably you would like to have a look at Magic GApps 2017.11.9, they are implementing more or less the solution I pointed out in my other post. I didn't try yet, but sounds promising to me.
AndDiSa said:
@blueplasticsoulman probably you would like to have a look at Magic GApps 2017.11.9, they are implementing more or less the solution I pointed out in my other post. I didn't try yet, but sounds promising to me.
Click to expand...
Click to collapse
Thanks for that. I did get the problem sorted by installing the rom and then removing things that wern't required such as stock email, telephone functions (not sure why they are in the rom anyway) gallery and some wallpapers. That created enough space to then be able to install pico gapps. Runs quite nice on CRdroid although it probably wont get used as we all have newer tablets. Still, nice to know it runs good after 6 years. :good: