Related
If you dont understand what this Modification is doing, why it needs to be done, or what possible benefits come from it, then...
PLEASE DO NOT TRY THIS MOD.
***Even tho it is impossible to brick your phone when flashing this i still highly recommend you UNDERSTAND what you are attempting to do before you do it. If someone explains you are freeing up internal memory from other places not using it and you still have to ask what the benefit is, then you obvisouly dont fully understand the mod and your phone and should turn away now.***
Thank You.
Click to expand...
Click to collapse
Now onto the mod: Heres a quick description of what this mod is doing. Pretend your phone is a pizza cut into 3 even pieces. Each piece is memory for /cache, /system, /data. Your aneroxic sister "aka cache" doesnt eat a lot so most of her slice will always be left, your fat obese brother "/data" always eats his whole slice and is left wanting more. You are healthy "/system" and only eat what you need and never less never more.
What this mod is doing is taking that original pizza and RECUTTING the slices to better fit whos eating them, so since your aneroxic sister barely eats and your obese brother is always hungry it takes all the extra pizza "aka memory" from your sister and gives it to your brother. As for you "aka /system" you only eat exactly what you need "aka the size of the rom and files it install" so it resizes your own slice to exactly the number it needs to install the rom and its gapps/files and leaves you with just a little wiggle room.
That being said, i tried this on my buddies CDMA Hero that i rooted for him and it worked like a charm. he went from something around 170mb internal storage to around 350+mb internal storage while on CM6 - Froyo 2.2.
***One thing i noticed when using a hero CDMA is that adb is crucial. one of the steps after flashing the recovery file is to reboot back into recovery and i noticed it was impossible to do it the right way without plugging your phone in and using ADB***
Original Files and Instructions: Firerats Original G1/MT3G thread found here - http://forum.xda-developers.com/showthread.php?t=717874
After you read thru firerats original instructions just know that itll be slightly different on your hero!
1. Click on the link i posted above and download these files: FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
2. Put both those files onto your SDCard.
3. While in your SDCard, make a .txt file named "mtdpartmap.txt"
4. Open your new mtdpartmap.txt file and...
- If you are using CM6 then type
Code:
mtd 102 2
- If you are using a larger Sense Rom like Fresh or ZenHero then type
Code:
mtd 182 4
5. Once all 3 files are saved on the root of your SDCard, reboot your phone into recovery
6. Format/Wipe your system and cache.
7. Flash the file: FR-recovery-v1.5.3-CustomMTD_S.zip
8. Once the file is done flashing, itll prompt you to wipe cache, system, and dalvik again.
9. Once its wiped, plug ur phone in and pull up command to adb reboot recovery (if you try to reboot into recovery any other way itll mess up the partitions and ull get cache memory.log errors and that will mean the mod didnt work correctly) by using this
Code:
adb shell
reboot recovery
10. if you did step 9 correctly, then youll get back to your recovery menu and itll say "formatting cache..." at the bottom of your screen but your recovery menu is instantly able to be used and you dont have to wait. ***On the newest version i think it no longer says this and your just got to go***
11. Flash CM6 if you used 102 for /system or Flash your larger Sense Rom if you used 182 for /system
12. Optionally, flash any kernal you may be choosing to use
13. Flash the file: FR-boot-v1.5.3-CustomMTD_S.zip
14. Click the top option on your recovery menu to reboot your system.
15. Once your system is fully booted you can go into menu > settings > sd card and internal storage , and check all the new added internal memory you have.
FYI : anytime you flash a new rom after this mod, or flash a new kernal to a currently flashed rom, you will ONLY NEED TO FLASH THE SECONDARY FIRERAT BOOT file named "FR-boot-v1.5.3-CustomMTD_S.zip".
so say after this mod you want to try a new kernal, you flash the kernal, flash boot, and reboot the system.
or say you want to flash a new cm6 nightly update, you flash the new rom/update, flash boot, reboot.
or say u want a new nightly and a new kernal, you flash the nightly, flash the kernal, flash the boot, reboot.
its very simple, if anything u flash overwrites current kernal specifications, u need to flash the boot file to make sure it knows how to set itself up. this goes for nandroid back ups aswell.
Fine Tweaking/Trouble Shooting: To get the most space you possibly can do go into adb or terminal and type
Code:
df -h
and it'll tell you what % you are using on your system. if you are at 60% then you can go ahead and decrease your /system value in your mtdpartmap.txt to about 2mb over the value it says you are using. so if your rom uses 115mb of /system you can change your mtd to "mtd 117 2".
So if you are getting an error while trying to flash a rom after doing this modification you most likely dont have enough /system space and will want to up your value to something more then enough like "mtd 200 4" then run the above code and re-scale down back to 2mb over what the current rom is using.
Enjoy CDMA users!!!
Not sure if Ill try this personally, but thank you.
tailsthecat3 said:
Not sure if Ill try this personally, but thank you.
Click to expand...
Click to collapse
Trust me, well worth it. At first i thought it was amazing gains on the g1 and mytouch, but after being the first person in the world to try it on the Sprint Hero CDMA the benefits blow all passed expectations out of the water.
It nearly doubled my buddies internal memory.
i remember on his stock rom with a handful of his favorite apps he was at around 40mb internal memory. after i rooted his phone and flashed FRESH HERO onto his phone with apps2sd he had around 150, now with this mod-cm6-apps2sd hes got over 300.
my win7 drivers are goofy and sometimes won't do adb when its in recovery mode. if you screw up the restart part - ie: can't get into adb to reboot by typing the command and those messages appear - is the device bricked or anything? Is it a one-time? Recoverable? etc...
thank you for the info. i was down to bout 20 mbs free and now well over 100. kept running into problems until i changed the cache size to a little bigger. i had a spare hero to experiment with so alls good.
Skeptical...idk why. I don't wanna risk bricking yet another Hero I guess.
SammyM00782 said:
Skeptical...idk why. I don't wanna risk bricking yet another Hero I guess.
Click to expand...
Click to collapse
Can you please enlighten us as to how you bricked your Hero?
I've been thinking about trying this. I hate having 80+ mb free in system that I can't use. Would love to just add it to /data
This won't brick your hero. The only way you can brick it is by flashing the wrong bootloader or radio. This does none of these.
Hey has anyone tried this on a different rom..
oldjackbob said:
Can you please enlighten us as to how you bricked your Hero?
Click to expand...
Click to collapse
Well.....first time was an accident. First time rooting, first time messing with a phone. I just kinda jumped right into it because when I found XDA it was pretty exciting. I always support the small guy coming from small businesses my whole life. Anyway, second time was probably due to incorrectly flashing a rom or something but regardless, I went to reboot and the phone was totally unresponsive afterwards. I trust you guys though, especially the devs. So do you think it's worth a shot?
I just did it, running cm6, and it took away that extra 80mb in system, took away all that unused space in cache, and moved it all to data. I went from 20mb free (still using apps2sd mind you) to almost 200! and so far, no issues, market works fine, everything works. Just one little note: I took somethings out of /system/app before flashing both in the rom and the gapps, things I don't use, like calculator (prefer realcalc), voice search, maps, quicksearch(all updated and installed elsewhere), and I only have 3mb free in system, so you may want to see about the customizing given in firerat's thread to increase system to say 100mb (it's 90 by default)
im trying to do this mod but every time i flash the recovery all i get the htc logo and it stays there.. i am using cm6.. any help please
You don't flash a new recovery, this patches your current one. Flash the one labeled recovery like any rom.zip in the recovery, wipe everything, flash your rom or restore, then flash the boot zip as an update.
Sent from my HERO200 using XDA App
danaff37 said:
You don't flash a new recovery, this patches your current one. Flash the one labeled recovery like any rom.zip in the recovery, wipe everything, flash your rom or restore, then flash the boot zip as an update.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
i also was stuck on the white htc screen...
can you explan which file to us.
i couldnt get this to work with clockwork recovery, so changed my recovery first to darchs 1.7.0. you have to make the custom file first and put it on your sd card. i had to have at least 10mb of cache memory specified or i got stuck on the white htc screen.
have to read firerats thread for that.
danaff37 said:
I just did it, running cm6, and it took away that extra 80mb in system, took away all that unused space in cache, and moved it all to data. I went from 20mb free (still using apps2sd mind you) to almost 200! and so far, no issues, market works fine, everything works. Just one little note: I took somethings out of /system/app before flashing both in the rom and the gapps, things I don't use, like calculator (prefer realcalc), voice search, maps, quicksearch(all updated and installed elsewhere), and I only have 3mb free in system, so you may want to see about the customizing given in firerat's thread to increase system to say 100mb (it's 90 by default)
Click to expand...
Click to collapse
Hell yea, glad to see people flashing this mod correctly and enjoying the results!
if you end up customizing your partitions to diff sizes let all the guys know what values they should set and/or how to set them up themselves.
I dont get to use my buddies CDMA Hero a lot so i dont know how smoothly everything has been working over the past 2 days but i havent gotten any complaints or calls to fix bugs so i assume its all working very well with firerats default values but i dont know for sure.
so far ive seen these suggestions
1. up cache to 3mb
2. up system to 100mb
@danaff37, did you set your own values or are you using defaults still?
can you us this on cyanogenmod? its 2.2.... i have tryed every way and all it gets me is the white htc screen and never does on from there... please help
i checked before i flashed to see what all i was using. i had quick system info installed already so was easy for me to see. i was already using 130mb for system, prob because of dalvic-cache, so i upped it to 150mb for future use. default setting for cache was no go, changed it to 10 mb and all is fine.
I'm using default still, but downloading the latest nightly and noticed it's about 5mb bigger than before, so I'm going to go ahead and change it to 100mb when I flash it later (after I make my mods). Anybody using it should keep in mind that most rom files, the bulk of the space it takes up is in system, so be sure to partition accordingly (including gapps on aosp roms)
I left the cache at the default, try to go to /cache afterwards and it symlinks straight to /data/cache, so I don't understand how leaving it bigger would solve anything, but I've seen stranger things occur with these damn phones. lol
Right off the bat I hear some of you groaning, and I want to understand/hear why.
I am still new to the whole flashing thing, however I think I have a basic understanding about these things.
Put rom on SD card (just like I did with the root file I used)
back up device
wipe everything (dalvik, cache, etc)
flash from from SD card
flash Gapps from SD card
If running into boot loop/doesn't boot (I would be really sad and freak a bit first then...) restore backup (side note, where are the backups stored? Can I copy the backup to my PC for an in case of emergency?)
So why don't most of us use Rom Manager? It will update you when your rom has an update, you save time and energy. I understand the draw of using ADB, and doing it manually, I am a geek and a programmer, but not in linux, never peaked my interest.
So for someone like me (simple, and I won't be flashing 100 different roms), is this a good option? What can go wrong that I am not expecting? I mean worst case scenario, can't I just flash stock rom with odin if all else fails and call it a day/start the process over?
Maybe I am simplifying things, if so please share with me how, its the only way I will learn.
PS I have looked all over for information about RM on my p3113, however there isn't much talked about with RM since 2011 at the most recent, and not about it being used on p3113, so any extra insight would be appreciated.
After searching for ages, I stumbled upon a solution for my tablet. Although all GTab ROMS work in the Zpad, I haven't been able to use the full 1GB RAM present in my Zpad.
So Finally today I stumbled upon a solution posted in slatedroid by Micky.
Instead of flashing the Viewsonic ROM to start with, we need to flash this ROM instead.
After you download the ROM from the link above, search for the TeamDRH CWM 5.5.0.4 and download. Extract the RAR file and replace the recovery.img in the folder with the TeamDRH CWM, cuz the one in the ROM is too old and doesn't support the latest ROMs.
[Note: If you want a larger system partition, follow this.
Open the file flash.cfg and find this no. 209715200 and replace it with this no.419430400
Now when you flash this ROM, you will get a system partition of 400MB.
If you use this method, you don't need to delete any system files after install from the ROM.]
Reboot the tab to CWM and wipe data/factory reset and wipe dalvik cache. Twice.
Shutdown and reboot to APX mode and connect to PC
NV Flash the ROM, let it boot and then shutdown.
Now to flash Jelly Bean.
Download Smoother Bean by nobe1976
Then boot the tablet to CWM
Again wipe data/factory reset and wipe dalvik cache. Twice just to be sure.
Flash the Smoother Bean zip file
Do not wipe data/factory reset or wipe dalvik cache this time.
Just reboot
Let it boot and run for a few minutes.
[Optional: Now install an app from play store to delete system apps and also a keyboard, Swipe or as such.
Open the system app remover and uninstall Gmail and AOSP Keyboard.
A few more apps can also be uninstalled, such as wallpapers, DSP Manager, Music FX, but not all.
Before deleting the AOKP Keyboard, you can copy it from the system folder if you want the stock keyboard. LatinIME.apk file.
(This does not apply if you modify the flash.cfg for larger system partition)
We need to uninstall these apps cuz after flashing with the above ROM, the system partition is only 209MB, so after flashing JB, we get around 5-6 MB free in the system partition. After uninstalling the apps, we get around 34 MB free.]
Hats off to nobe1976. He is able to develop a JB ROM that can be installed in a 200 MB system partition.
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
[After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Its a small request from us Zpad users.
(Note: From the help of all the users, I have been able to increase the system partitiom to 400MB)]
If anyone could help, I will be gratefull, we all will be very gratefull.
This is really pushing the limit.
Edit: Now you can use 1GB RAM present in your tablet and all the space available in the flash memory.
Note: This method can be used in all variants of the Zpad which has 1GB RAM and 16GB ROM.
Note: This tablet is sold by different names all over the world. The one I use is HCL AP10-A1
kank_fraud said:
Well after everything, I hope whoever tried this in their MALATA Zpad is able to see full 1GB RAM, or around 850 MB approx.
Click to expand...
Click to collapse
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]su -c dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
After this succesfull experiment, I would like to request a developer to kindly help us modify the system partition of the above ROM to 350 MB or more if possible.
Click to expand...
Click to collapse
Though @rajeevvp is the best person on xda to give you solution that is more logical on this, I will tell you quick and dirty way to do this, which I have adopted.
1> download stock zpad rom if you don't have it already "ftp://112.5.164.225/tablePC/T2_nvflash_mp_3g(WCDMA)_20110824.rar"
2> unzip it, delete recovery.img from unzipped directory, copy part9.img from DRH nvflash which is used for prep 350M system partition to this directory, rename it to recovery.img
3> edit "android_fastboot_full_i_malata.cfg” change "size" of partition id 11 (which is a system partition)
Make sure you do not give any arbitrary size here; calculate it with the formula @rajeevvp posted here "http://forum.xda-developers.com/showpost.php?p=22138304&postcount=14"
4>now nvfalsh your tablet in apx mode with download.bat, now format /data /system /cache and flash whichever rom you want on top.
memory/partition config is supplied to kernel through CMDLINE parameter, so even if you nvflash tab with above procedure, its not necessary that default memory/partition sizes are maintained created by above prcoess, Team DRH boot.img has a blank CMDLINE. That is the reason
Above process will work on most of the ROM, which is using TeamDRH boot.img.
(more technical explaination stright from one of the posts of @rajeevvp "When the bootloader runs, it reads PT (partition 3) and constructs a command line telling the kernel what the partition layout is on the onboard NAND flash. Normally, the bootloader will pass this command line to the kernel as part of the boot-up process. However, if the bootloader sees that the boot.img already contains a default command line then that will take precedence")
I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
I replaced the recovery image in the ROM as instructed in the first post but before flashing I edited the flash.cfg file to change the APP partition (id=11) size to 262144000 (250MB). I then followed the steps above but after flashing Smoother Bean it would always restart in recovery. I found I had to partition the internal SD to 4096/0 and then reload the rom and flash again. I now have a ZPad with a 250MB system partition and a total RAM of 871124 bytes. Thanks very much as it seems much faster now. Note I didn't have to remove any system apps in the process.
Click to expand...
Click to collapse
glad to hear that it worked, BTW you will have to change /system size to minimum 350MB if you plan to use TeamDRH rom in future (hopefully with camera working)
I'll have a try later.Thanks So much.
Thank You all for the help.
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
It shows 419 MB in Titanium Backup
I am happy with it.
Its way better then before.
Thanks evryone
Problem solved
If anyone has formated or resized the internal memory resently, please try the maximum possible size for the system partition.
I tried 512MB but it didn't work. Maybe 490MB might work.
According to my knowledge, Android should support atleast upto 999MB for any partition.
Is it cuz of our tab or is it cuz of the architecture.
And if anyone knows, is it possible to create a larger internal partition.
As in 8GB or if possible the whole internal memory.
CWM doesn't allow more than 4GB internal space.
kank_fraud said:
I have already replaced the stock recovery CWM to 5.5 from the first flash.
Well I have tried to modify the system partition to 512 MB(536870912) in the flash.cfg and it failed. So I tried 400MB(419430400) and it worked.
Click to expand...
Click to collapse
Well this was expected result, /system partion resides on NAND flash chip (with is only 512MB) and not on SDcard.
Read this "http://raywaldo.com/2011/07/format-the-gtab/" and this "http://forum.xda-developers.com/showpost.php?p=15558724&postcount=12"
Also you need to bare in mind that other partitions also use 512MB nand flash as per explanation in above threads.
so if you take a close look at falsh.cfg file in nvflash directory you will understand that size allocation is sequential ("allocation_policy=sequential") and system partition (11) which is last to allocate the space, so you need to calculate it accordingly if you want to utilize all remaining space from NAND flash chip.
Well I cant open the page "http://raywaldo.com/2011/07/format-the-gtab/".
So according to this info I have hit the limit. I am already using 489MB of the 512MB flash. And as always, cuz of our storage manufactures, we get only 490MB in a 512MB chip.
What I wonder is why Malata and Viewsonic did not utilise the full NAND space available in the first place.
Is it used for something else.
I mean even the 350MB prep for Viewsonic GTab uses 350MB instead of 400MB.
It is so easy to to utilise and partition the NAND, then why not use the full available space.
What is the empty space used for!???
Or is it just a waste!!!
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
fanguru said:
hi all,
tks for the useful informations above..but since my poor tech knowledge, its possible to produce a flashable rom for all T2 user with the max 490MB flash?
thanks in advance!
FG
Click to expand...
Click to collapse
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
rajeevvp said:
Can you post the 3 .txt files produced by these commands (reboot the tablet first)?:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
$ [B]cp /proc/meminfo > /mnt/sdcard/meminfo.txt[/B]
$ [B]free > /mnt/sdcard/free.txt[/B]
Click to expand...
Click to collapse
Well I am very sorry for such a late reply. :angel:
I missed your post as I was out of station.
After I came back there were already solutions posted by a couple of users. :victory:
Well today while updating my original post, I noticed ur first reply. :silly:
Well thank you for your reply.
And thanks to all the ppl who provided for the solutions to our ZPad.
I guess the problems are solved for now.
:highfive: :highfive: :highfive: :good:
kank_fraud said:
Its already there.
Goto the first post and download the ROM
Extract the RAR file and find the file flash.cfg, right click and edit
Search this no. 209715200, it should be in the last 5-6 lines.
Delete the whole no. and type this no. 419430400
Save the file and close it.
Start your tablet in APX Mode and flash your tablet using download.bat.
Now you are using the full flash memory available.
You loose a few hundred kilobytes but thats it.
You cant use the whole flash memory as system partition.
There are additional partitions for the bootloader, recovery, logo, etc. which take up 89MB approx.
So 400MB is what you will get for system partition.
I would suggest flash as less as possible. Flash memory can written only a few hundred times. If it reaches the limit, then our tablet is dead.
Flash only major updates or if your ROM gives problem
Click to expand...
Click to collapse
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
kank_fraud said:
I guess the problems are solved for now.
Click to expand...
Click to collapse
I'd still like the output of those commands--for my own edification.
fanguru said:
Thank You kank_fraud,
i do these steps, and it works!
after, i've tried to flash "Smoother Bean " but tab continues to reboot i nrecovery mode. I've tried also to partition 4096 like suggested above, but same results.
So, the onlyu one rom working is the first?
ty again!:good:
FG
Click to expand...
Click to collapse
Well for Me it worked the first time itself.
Why don't u try giv it a few more couple of times. :laugh:
BTW, are you using the Malata Zpad or Viewsonic Gtab
If you are using Gtab, try TeamDRH method but modify the size of the partition.
If u are using Zpad, try again.
Clear cache and reset before installing.
Try previous older ROMs and gradually update to newer ones.
Reset and wipe before each update.
As I didn't get any problems, so I can't say whats wrong with your installation.
And very sorry for the late reply.
I have exams.
But my tablet is very stable after this.
Everything is running smooth, even HD games.
Goodluck :fingers-crossed::fingers-crossed::fingers-crossed:
rajeevvp said:
I'd still like the output of those commands--for my own edification.
Click to expand...
Click to collapse
I tried it in terminal emulator, but it says 'Operation not permitted'
kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
same here.
kank_fraud said:
I tried it in terminal emulator, but it says 'Operation not permitted'
Click to expand...
Click to collapse
Fixed commands. Try them again.
I seem to have everything running and it seems really fast, the only problem I have is that the home button (hardware and soft) does not work!
I've tried installing a different home app, tried home switcher and I get asked when the tablet boots as to which home app to use, but still the buttons don't work (back and recent apps work).
Any ideas???
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like movies, music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files (the installed apks will be gone though, but no biggie if you backed up them with Titanium).
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Edit:
I have a p6210, no idea whether it works on other models or not. I guess it does but who knows...
Give it a try if you feel like it, but don't forget to make a back up before in case it goes wrong.
After flashing, your files won't be in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
unclefab said:
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files.
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Give it a try if you feel like it...
Click to expand...
Click to collapse
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Re: Easy way to keep one's personal data after flasing a new ROM
ALWAYS create a backup before erasing/flashing ANYTHING!! It's always as a precaution, to avoid losing something that you don't want to. And it only takes like 5 seconds literally. I lost some stuff when I unlocked the bootloader on my nexus10 by factory resetting, and I must say I didn't have a smile on my face. But it happened, u live n learn. I'm afraid if u wiped without making a nandroid backup your probably out of luck. Unless your skilled in using forensics techniques to try to recover it. Can't think of any options tho.
Sent from my SCH-I535 using xda app-developers app
Balaram12 said:
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Click to expand...
Click to collapse
What did you do?
Did you follow the exact procedure?
I flashed again some roms today and it worked again.
But one thing is that the files are not in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
This said, meishkov is right, one should allways have a back up in case anything goes wrong, I should have mentioned it in the OP but I forgot, my bad...
Edit:
OP edited.
Oh well, noone tried?
Would be nice to hear some reports...
Balaram, it would be fair from you to detail a bit what happened and to tell if you found back your files.
Anyway, this method worked for me and I thought that it might have interested some people here, roms flashers and devs alike, but if that s not the case then no worries.
If someone feels that I should erase the whole thread just tell me and I ll do it...
TF700t
I am on twrp-3.0.2-0. I followed the following steps.
1. Full wipe
2. Format /data
3. Change /data to f2fs
4. Flash KatKiss-6.0_TF700T_029.zip
5. Flash OpenGapps ARM 6.0 Pico
6. Flash SuperSU BETA 2.52
7. Wipe cache/dalvik
8. Reboot
The tablet boots with the message "Storage space running out. Make sure there is at least 250mb free space". This is not only cosmetic but prevents me from installing some apps and enable sync on gmail.
I tried following the steps 2 times thinking I may have had done something wrong the first time each time with format of /data.
What am I doing wrong? Is there any way to increase the size of the system partition from TWRP? What are my options?
Are you trying to install apps to /system? They should go to /data, your system partition is pretty much filled with the rom.
In adb shell run cat /proc/partitions and post the result
Sent from my Nexus 5X using Tapatalk
Out of space in /system after clean install
I have pretty much exactly the same problem as @smodak - after formatting all partitions in TWRP and changing /data to f2fs I followed the published instructions - installed KatKiss from recovery, then SU 2.52 beta, then open gapps ARM 6.0 pico. All went well except that gapps won't install as there is only 102Mb free in the /system partition.
So I'm just flashing the gapps package in TWRP but it is obviously trying to install to /system instead of /data as you suspected @berndblb... I wonder if this is an error in the installer package configuration?
I had a look through the gapps zip but couldn't find anything explicitly referencing /system, so I'm not sure how to direct the installer to install to /data instead... any suggestions gratefully received. Meantime I might download a different flavour gapps and see if it behaves differently.
Thanks!
I downloaded open_gapps-arm-6.0-full and tried again - still trying to install to /system.
Is it possible to change this behaviour?
You cannot install the full gapps version. The system partition is not large enough. Download and flash the pico version. It has only the essential Gapps, those that need to be in /system to work.
If you're missing any Google apps install them from Play. Then they will install to /data
Yep, already tried pico first - not enough space. Was hoping that the /system target was an error but have since learnt this is by design in open gapps.
I'm having trouble finding any other distribution that targets /data - do you know of any?
Thanks.
Thousands of people have downloaded the rom and flashed the recommended pico gapps without a problem, including yours truly.. And your system partition is not large enough??? I don't think so. I have no idea what it is you are doing, but you are doing something wrong....
Back to basics I would recommend: double check each step and start over
Sigh... I've come so far - from a soft brick to a working OS, I can almost taste it! OK, back to square one. Wipe and try again.
Tell me if this sounds right though - TWRP is reporting that my /system is 503Mb in total, and after installing KK and SU 401Mb is used. So, only 102Mb free. Am I somehow chewing up extra space during the install, or is this what you'd expect, and the partition size you'd expect? The gapps pico zip is 155Mb so if it's trying to extract everything to /system during install, and these sizes are right, it's hard to see how it's ever going to work.
multiSingularity said:
Sigh... I've come so far - from a soft brick to a working OS, I can almost taste it! OK, back to square one. Wipe and try again.
Tell me if this sounds right though - TWRP is reporting that my /system is 503Mb in total, and after installing KK and SU 401Mb is used. So, only 102Mb free. Am I somehow chewing up extra space during the install, or is this what you'd expect, and the partition size you'd expect? The gapps pico zip is 155Mb so if it's trying to extract everything to /system during install, and these sizes are right, it's hard to see how it's ever going to work.
Click to expand...
Click to collapse
Where do you see the 503mb size? The TF700 has a 768 mb /system partition.
Format system, then flash rom, gapps and super su in that order.
With Nougatella, pico gapps and SuperSU I have 563 mb on /system.
Install and run DiskInfo from Play to see your partition size and what's in use.
Ooops, sorry - you can't boot the thing.. Didn't mean to twist the knife. :laugh:
Open a terminal in TWRP and run: cat /proc/partitions
You'll see that mmcblk0p1 is 786432 kb which equals 768 MB.
I would be stunned if you see anything dirfferent
berndblb said:
Where do you see the 503mb size? If I remember correctly the TF700 has a ~760 mb /system partition.
Format system, then flash rom, gapps and super su in that order
Click to expand...
Click to collapse
TWRP 3.0.2.1 > Wipe > Advanced Wipe > Select "System" > Repair or Change File System. Shows 503Mb for /system, ~59Gb for /data.
I'm wondering if there might be temp directories left over from installs that need cleaning up? Could I resize those two partitions without a high risk of bricking my tab again?
I'll try reflashing in your order... I was going from the instructions in the KK thread that said to do SU before gapps. Maybe that will help.
---------- Post added at 03:27 PM ---------- Previous post was at 03:13 PM ----------
berndblb said:
Install and run DiskInfo from Play to see your partition size and what's in use
Click to expand...
Click to collapse
Heh, it's a bit hard to access the Play Store without being able to install gapps!
multiSingularity said:
Heh, it's a bit hard to access the Play Store without being able to install gapps!
Click to expand...
Click to collapse
Yeah, I realized that, read my edit above
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
multiSingularity said:
TWRP 3.0.2.1 > Wipe > Advanced Wipe > Select "System" > Repair or Change File System. Shows 503Mb for /system, ~59Gb for /data.
I'm wondering if there might be temp directories left over from installs that need cleaning up? Could I resize those two partitions without a high risk of bricking my tab again?
Click to expand...
Click to collapse
Mhh, definitely format system because in the same place TWRP shows me 755 mb for /system.
No, you cannot resize the partitions and you don't need to....
berndblb said:
Open a terminal in TWRP and run: cat /proc/partitions
You'll see that mmcblk0p1 is 786432 kb which equals 768 MB.
I would be stunned if you see anything dirfferent
Click to expand...
Click to collapse
Prepare to be stunned.
mmcblk0p1 is 524288 in size.
Unsurprisingly, formatting and reflashing KK then gapps still failed. I've attached the gapps installation log for some light reading.
(Scratches head) Soooo... something is screwy with my system partition size. I've never resized it (if that's even possible) so I don't know what's going on.
multiSingularity said:
Prepare to be stunned.
mmcblk0p1 is 524288 in size.
Unsurprisingly, formatting and reflashing KK then gapps still failed. I've attached the gapps installation log for some light reading.
(Scratches head) Soooo... something is screwy with my system partition size. I've never resized it (if that's even possible) so I don't know what's going on.
Click to expand...
Click to collapse
I am stunned and scratching my head. This is after running a format in TWRP???
It's late here and I'm going to sleep on this. c u later
berndblb said:
I am stunned and scratching my head. This is after running a format in TWRP???
It's late here and I'm going to sleep on this. c u later
Click to expand...
Click to collapse
Hey, thanks for all your help so far. I really appreciate the time you've put in answering my questions! Sleep tight.
Had to downgrade to KK 5.1.1 to get it all to fit. Worked OK, but noticably slower than Nougat. I did a little jiggerypokery with KK 7.1 in the TWRP terminal window and moved the /system/app directory to my sdcard (set up as Adoptable Storage) with a symlink to it under /system. Hoping this should work OK... it certainly gave me enough space to install gapps. Time to test.
Yeah well that was a bit of a flop. Got stuck on the boot animation. Tried moving some different directories out of system to sdcard or to /data and symlinking but no dice any which way. Tried leaving directories in situ but moving large files and symlinking those (eg foreign font files) but still no joy.
Unless there's a way to delete and recreate the system and data partitions I think I'm stuck on 5.1 till the end of time.
multiSingularity said:
Yeah well that was a bit of a flop. Got stuck on the boot animation. Tried moving some different directories out of system to sdcard or to /data and symlinking but no dice any which way. Tried leaving directories in situ but moving large files and symlinking those (eg foreign font files) but still no joy.
Unless there's a way to delete and recreate the system and data partitions I think I'm stuck on 5.1 till the end of time.
Click to expand...
Click to collapse
You really think the tablet will last that long?? :silly:
How about flashing the thing back to stock. AFAIK flashing the stock blob in fastboot puts everything back to stock. I have no idea if it also recreates the partition table though... Worth a shot if you ask me.
It's called a buster99 and typically used if you're stuck with an 'unrecoverable bootloader error'. Google those terms and you'll find the steps easy enough.
berndblb said:
You really think the tablet will last that long?? :silly:
How about flashing the thing back to stock. AFAIK flashing the stock blob in fastboot puts everything back to stock. I have no idea if it also recreates the partition table though... Worth a shot if you ask me.
It's called a buster99 and typically used if you're stuck with an 'unrecoverable bootloader error'. Google those terms and you'll find the steps easy enough.
Click to expand...
Click to collapse
Yeah, I used buster99's approach to recover from my soft brick. It's worth a go, for sure. Will let you know how it goes.
OK, here's the latest.
Flashing the stock ASUS ROM via fastboot failed because the staging partition is too small - it can't even get off first base.
HOWEVER... the lightbulb went on as to why my partitions are all out of whack - a while ago when I started experimenting with resurrecting my Infinity I accidentally flashed a stock TF201 ROM onto it, and this has clearly recreated TF201-sized partitions for me. So, this is an ecouraging sign that doing the same with the right ROM will fix the issue - if only we can get it to complete.
I'm thinking if I could delete all partitions except system and recovery, or even recreate a properly sized staging, and then flash the stock ROM it would likely create the missing partitions as it goes. Thoughts?
Now that explains a lot!
I seem to remember that _that posted a flashable partition table somewhere quite a while ago.... pt.blob I think it was.... I'll dig for it later today...
---------- Post added at 06:00 AM ---------- Previous post was at 05:52 AM ----------
Or you say wth and just flash the TF201 Katkiss to it
Which bootloader do you have on there now? The 700 or 201?