Is there any way to have a full format of EVERYTHING except the APX mode?
I know the Format utility that erases any rom traces that might be in the system, but is there anyway to have a fresh start and erase everything (like sys, system, data, dev, d and other folders in root) and get like a full factory reset?
Conclusion:
The closest formats are:
http://forum.xda-developers.com/showthread.php?t=974422
http://forum.xda-developers.com/showpost.php?p=9603803&postcount=1
http://forum.xda-developers.com/showthread.php?t=842000
The closest thing I think that is available currently can be found here. Listed as a detox for the gtablet.
Read everything very carefully. You will have to use nvflash to restore your tablet if you use this.
http://forum.xda-developers.com/showthread.php?t=974422
but I think this is the format utility you describe?
makto said:
The closest thing I think that is available currently can be found here. Listed as a detox for the gtablet.
Read everything very carefully. You will have to use nvflash to restore your tablet if you use this.
http://forum.xda-developers.com/showthread.php?t=974422
but I think this is the format utility you describe?
Click to expand...
Click to collapse
Yep, it is the format utility; but it specifies that "This fully erases the ROM".
I would like to start again erasing everything except apx.
Pazzu510 said:
Is there any way to have a full format of EVERYTHING except the APX mode?
I know the Format utility that erases any rom traces that might be in the system, but is there anyway to have a fresh start and erase everything (like sys, system, data, dev, d and other folders in root) and get like a full factory reset?
Click to expand...
Click to collapse
To do this simply install a copy of TNT 3991, this is a fairly good reset, we do not have a real stock image from viewsonic yet, partitioning to 2048 and installing a rom is a prety good refresh.
btw APX is not something you can erase... it's a special mode that the tegra support, it read into ram memory a special files and execute low level command.
P00r said:
To do this simply install a copy of TNT 3991, this is a fairly good reset, we do not have a real stock image from viewsonic yet, partitioning to 2048 and installing a rom is a prety good refresh.
btw APX is not something you can erase... it's a special mode that the tegra support, it read into ram memory a special files and execute low level command.
Click to expand...
Click to collapse
Tnx for the comment, but a fresh install is not good enough for my problem.
I have a problem with the battery. I am a noob, but i think that the folders in root such as the sys, system, d ,dev, data and so (not sure if they are part of the kernel or not) are they ones i have corrupted. That is why i am asking for a full format, no rom change or kernel(clemsin or pershoot) update has fixed my problem, i need something much more complete(i think) to solve my problem.
My theory is that, if i manage to replace those files for fresh new ones untouched by anyone else that is not from viewsonic would finally fix my problem because those files are the ones that control the battery meter.
You can see my signature to see what the problem is.
I also thought that it would be good not just for my problem, but for any problem that comes from the base of the pyramid rather than the rom. A good fresh and complete reinstall of the tnt firmware would fix almost any problem that is not related to hardware.
BTW: i thought that APX was something as primitive as bios, if you manage to erase it, it would leave your device as processed plastic + metal. Didnt know that it couldnt be erased.
pazzu510,
What you are looking for doesn't exist here. Android is not well-documented and many
of its function -- like formatting, deleting, etc. -- don't work just like Windows or Linux or ?????.
As I have been told and understood -- even what you call the format programs -- are not
formatting the G-Tablet like you or I would format a hard drive. They are simply
writing a subtitute image into your G-Tablet.
The closest we have been able to put together to a "stock" recovery is:
http://forum.xda-developers.com/showthread.php?t=861950
This thread nvflash installs a bekit stock image 1105 which in fact when
it is installed tells you it is Stock Version 2638. (I got Stock Version 2967
on my first G-Tablet. 3588 is current.)
I would recommend:
1. Follow the thread referenced above and NVFlash your tablet to bekit 1105.
Follow the instructions carefully.
2. Assuming you get a good install, then install ClockWorkMod (CWM). If you
get that installed, then go to the Advanced menu and choose the option to partition
your tablet. It will take a short while, so don't panic. The choose Fix Permissions.
Once that is done go up and Wipe Dalvic Cache. And then go back to the Main
menu and Wipe Cache and Wipe Factory Data.
3. With the above done (to make sure a variety of things may not be affecting your
tablet) re-nvflash to bekit 1105 again.
4. See whether this fixes your file and battery problem.
5. If it does not, you can drain your battery down, plug it in and run CWM and go to
the Advanced menu and Reset Battery Statics.
If that doesn't fix you, then I suggest Prayer -- that's all else I can offer!!!
Hope this gives you answers, ideas and help.
Rev
butchconner said:
pazzu510,
What you are looking for doesn't exist here. Android is not well-documented and many
of its function -- like formatting, deleting, etc. -- don't work just like Windows or Linux or ?????.
As I have been told and understood -- even what you call the format programs -- are not
formatting the G-Tablet like you or I would format a hard drive. They are simply
writing a subtitute image into your G-Tablet.
The closest we have been able to put together to a "stock" recovery is:
http://forum.xda-developers.com/showthread.php?t=861950
This thread nvflash installs a bekit stock image 1105 which in fact when
it is installed tells you it is Stock Version 2638. (I got Stock Version 2967
on my first G-Tablet. 3588 is current.)
I would recommend:
1. Follow the thread referenced above and NVFlash your tablet to bekit 1105.
Follow the instructions carefully.
2. Assuming you get a good install, then install ClockWorkMod (CWM). If you
get that installed, then go to the Advanced menu and choose the option to partition
your tablet. It will take a short while, so don't panic. The choose Fix Permissions.
Once that is done go up and Wipe Dalvic Cache. And then go back to the Main
menu and Wipe Cache and Wipe Factory Data.
3. With the above done (to make sure a variety of things may not be affecting your
tablet) re-nvflash to bekit 1105 again.
4. See whether this fixes your file and battery problem.
5. If it does not, you can drain your battery down, plug it in and run CWM and go to
the Advanced menu and Reset Battery Statics.
If that doesn't fix you, then I suggest Prayer -- that's all else I can offer!!!
Hope this gives you answers, ideas and help.
Rev
Click to expand...
Click to collapse
if you are right YOu´ll clarified what i thought.
Ill try what you say as soon as i finish my homework.
Thanks for the advices.
Edit: Did everything, problem persists.
I am starting to think it is a hardware problem because i tried like 3 diferent factory utilities and none of them made any difference.
Pazzu510,
If that didn't work, then I suggest you go to the thread where you got
the Calkulin Rom and ask there. That Rom is advertised as having
battery-saving stuff in it. (I don't know anything about it, myself).
Maybe that kernal changed something??????
Rev
yeah, thinked so. I will, but i keep leaving my school projects for later and they can not wait any more. XD. i always keep trying to fix the tab and skip what i have to do, so i did the opposite now.
Ill post on calkulins as soon as i can.
Thanks for eveyrthing, it is good to know that someone is trying to help me.
Scripts in root/sys/class/power_supply/battery/uevent (Charger connected) POWER_SUPPLY_NAME=battery POWER_SUPPLY_TYPE=Battery POWER_SUPPLY_PRESENT=0
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_VOLTAGE_NOW=0
POWER_SUPPLY_CURRENT_NOW=0
POWER_SUPPLY_CURRENT_AVG=0
POWER_SUPPLY_TEMP=0
POWER_SUPPLY_CAPACITY=0
POWER_SUPPLY_TIME_TO_EMPTY_AVG=0
POWER_SUPPLY_TIME_TO_EMPTY_NOW=0 POWER_SUPPLY_TIME_TO_FULL_AVG=0
POWER_SUPPLY_TECHNOLOGY=Unknown
Scripts in root/sys/class/power_supply/battery/uevent (Charger NOT connected)
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_PRESENT=0
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_VOLTAGE_NOW=0
POWER_SUPPLY_CURRENT_NOW=0
POWER_SUPPLY_CURRENT_AVG=0
POWER_SUPPLY_TEMP=0
POWER_SUPPLY_CAPACITY=0
POWER_SUPPLY_TIME_TO_EMPTY_AVG=0
POWER_SUPPLY_TIME_TO_EMPTY_NOW=0
POWER_SUPPLY_TIME_TO_FULL_AVG=0
POWER_SUPPLY_TECHNOLOGY=Unknown
From your earlier post.
That is weird. Not only is nothing changing when charging but it doesn't even recognize the Li-ion battery.
A full repartition then rom and clemsyns newest kernel should have fixed that. I assumed that this was part of the base build stuff and gets written over with every flash.
Also assumed repartitioning deleted everything.
Mantara,
Not so. As I said before, what happens with Android doesn't
always jive with what I have seen in other OS!
Maybe the devs can break it out, but some things don't get
changed.
I nvflashed once and it did just fine -- and when I was through
some of the programs were still on the tablet.
Rev
Mantara said:
Scripts in root/sys/class/power_supply/battery/uevent (Charger connected) POWER_SUPPLY_NAME=battery POWER_SUPPLY_TYPE=Battery POWER_SUPPLY_PRESENT=0
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_VOLTAGE_NOW=0
POWER_SUPPLY_CURRENT_NOW=0
POWER_SUPPLY_CURRENT_AVG=0
POWER_SUPPLY_TEMP=0
POWER_SUPPLY_CAPACITY=0
POWER_SUPPLY_TIME_TO_EMPTY_AVG=0
POWER_SUPPLY_TIME_TO_EMPTY_NOW=0 POWER_SUPPLY_TIME_TO_FULL_AVG=0
POWER_SUPPLY_TECHNOLOGY=Unknown
Scripts in root/sys/class/power_supply/battery/uevent (Charger NOT connected)
POWER_SUPPLY_NAME=battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_PRESENT=0
POWER_SUPPLY_STATUS=Unknown
POWER_SUPPLY_VOLTAGE_NOW=0
POWER_SUPPLY_CURRENT_NOW=0
POWER_SUPPLY_CURRENT_AVG=0
POWER_SUPPLY_TEMP=0
POWER_SUPPLY_CAPACITY=0
POWER_SUPPLY_TIME_TO_EMPTY_AVG=0
POWER_SUPPLY_TIME_TO_EMPTY_NOW=0
POWER_SUPPLY_TIME_TO_FULL_AVG=0
POWER_SUPPLY_TECHNOLOGY=Unknown
From your earlier post.
That is weird. Not only is nothing changing when charging but it doesn't even recognize the Li-ion battery.
A full repartition then rom and clemsyns newest kernel should have fixed that. I assumed that this was part of the base build stuff and gets written over with every flash.
Also assumed repartitioning deleted everything.
Click to expand...
Click to collapse
Yep, it is very weird, but the weirdest thing is that i am able to use the tablet with the battery; i get over 7 or 8 hours of use with a full charge(i know it is a full charge because when powered off, the red light works and gets to green eventually).
I already tried repartitioning, full format, nv flash, stock, clemsin, calkulins, but anything of this has worked. As i sad, , i am starting to think it is a hardware problem(even if i think it is improbable because i didn't hit the tablet when it happened, i just flashed vegan 5.11 and came from calkulin.
Thanks for the interest, any suggestions are gratefully accepted.
Related
I did NOT paritition my gTablet after I installed CWM 0.8. My CM7-based ROMs have installed and worked just fine, including the new Market app. Do I need to partition?
The only real error I have had is the inability to transfer files (using Astro) between my internal 16 GB memory (/mnt/emmc/) and my installed 2GB sd card (/mnt/sdcard). Will partitioning help solve this?
TIA!
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Mantara said:
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Click to expand...
Click to collapse
I agree with Mantara. I think it reduces the chances of corrupting the tablet's data. Also, repartitioning is a bigger pain if you decide to do it later when you have a like a ton of files in your internal memory and have to back it up because repartitioning reformats the internal sd card.
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
butchconner said:
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
Click to expand...
Click to collapse
that's the approach i'll take for now. when time comes for officially official CM7 tablet releases, i'll reformat then. until then i'll just enjoy things as they are. thanks for the feedback, all.
How much wiping do you need to do when you are upgrading to a new ROM release? I don't really want to have to go through all of the setup every time a ROM is updated. What does every generally do?
I'm running the G-Harmony ROM.
Use Titanium backup or the like to take a backup of everything if you are upgrading from one version of the rom to a new version. At first I wasn't backing up and spent hours getting everything back to the way it was. Now, in a matter of minutes I'm back running the same way I was before, but on a newer ROM.
Take the backup -> copy the backup folder to your micro sd card or computer -> follow the steps to install the ROM (do what is recommended such as the user data, dalvik, cache) -> once the rom is up and running, copy the backup folder back to your tablet -> download titanium backup, it will see the folder you copied over containing your backup-> restore data, apps, user settings from titanium backup.
I'm not sure how it works if going from ROM to ROM, probably want to search on it.
Cool, that's pretty much what I did. Unfortunately, I hadn't copied off the TitaniumBackup folder, and the new ROM version switched the emmc and SDCard mount locations, so I had to switch them back to be able to get at my backups. I didn't have an external micro SDCard reader with me, so I couldn't easily copy the folder from the internal card to the external. Ah, well. Going through the Titanium restores right now. I really should buy this software to prevent having to approve every restore
chadness,
One of the main things I try to help people here with is boot loops and I spend a
lot of time trying to figure out the cause so we can prevent it.
IT IS MY OPINION that one of the things causing the boot loops and making
people have to re-flash and re-partition -- is the stuff leftover in flash after
flash playing with their tablets.
I'm not sure the Android file system is all that good. I don't believe in tablet formats
because it doesn't work like a hard disk. You can delete a file and go back later and
the file is still there. You can nvflash the tablet and stuff is still let there.
When stuff gets left over it can conflict with the new stuff and BAM -- boot loops.
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid
version -- bekit 1105 (2538) or 3588 -- the repartition to 2048 and 0, Fix Permissions,
Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
I can't prove it yet -- but I bet if people would do that most of the boot loops would stop -- and probably some of the other little stuff too.
This is just my opinion -- but then I have only nvflashed either of my G-Tablets one time in five months now (involuntarily -- because of problems.)
Think about it.
Rev
Interesting! I've been flashing different ROMs this week and haven't run in to any problems as long as I've formatted system and data.
butchconner said:
. . .
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid version -- bekit 1105 (2538) or 3588 -- then repartition to 2048 and 0, Fix Permissions, Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
. . . . Rev
Click to expand...
Click to collapse
Rev, what is your opinion about using 'Calkukin's_Format_All.zip & wiping Dalvik Cache' vs all the above steps ?
VEGAn RC1 Ginger Edition was loaded and working fine for almost two weeks.
Then I powered up and it would get stuck on the G-TABDEVs splash screen.....
Here is what I can do:
I can power up and the tab will go past the viewsonic birds screen to the next splash screen (G-TABDEVS) and will stay there indefinately.
I can power up into Clockworkmod 2.5.1.1. 0.8 (all soft buttons work and I can scroll through the choices with the vol switch just fine)
I can wipe cache partition
I can apply sd card:update.zip (only because I still have VEGAn RC1 GE .zip on my device)
I can mount the USB drive (drive is recognised on my computer running win XP)
I can apply NVflash to the device (did this to get access to CWM by changing part #9)
What I can't do:
I can not transfer large files files from my computer to the tablet (I can make a directory and transfer small files only maybe 100 kb or less) Any time I try to transfer a larger file (a ROM or other) I get an I/O error.
I can not partition the SD card (internal storage),
Wide data/factory reset,
Wipe Delvik cache,
it just hangs indefinately with each of the above.
I have spent counless hours searching through all the great information on XDA and can not find any instance like mine.
I don't think it has been bricked because of what I still can access, although there still seems to be something "limiting" my actions.
Has anyone experienced this? and more importantly.... Can anyone HELP????
you can boot into clockwork but cant use the factory reset option there? if its hanging how long did you let it wait? id try a reset and let it sit for 5-10 mins to see if its really doing something or just mucking around.
you make a restore file (backup of your previously installed rom on your tablet)?
if the rom is still on your tablet try reinstalling it. then after installing try factory reset before rebooting. if you cant reset try reboot then reset.
the G-Tabdevs screen staying there indefinitely is because it needs to be reset. so you just have to figure out how to reset it.
Great! I totally did not realize that it took that long to reset. I will try that later tonight and post my results.
OK, I tried using "wipe data/factory reset" and it just hung. I let it sit for 20 minutes (just in case).
Then tried "partition SD card (2048,0) and let it run, again for 20 minutes and it just hung.
Still very frustrated.
What are my options at this point?
I need to follow this thread b/c I have the same problem. Last night shut down fine and this morning went to power back on and I get the birds and then it gets stuck in the next load screen. I reinstalled update.zip but no dice. Any ideas?
Make sure all the partition are active, wipe dalvik, try reflashing the same rom over and fix permission
For such strange issue you can alway use the nvflash format utility but not before having performed an nvflash backup then use bekit images to bring back the tablet to life. You can also make a clockwork backup
Backup http://forum.xda-developers.com/showthread.php?t=1010659 (if something goes really wrong it can help, the .bct is what you want to keep at least)
Be warned that backup may have issue if you got flash bad block, this is not a critical issue
Format http://forum.xda-developers.com/showthread.php?t=974422
Restore http://forum.xda-developers.com/showthread.php?t=861950
make sure you follow instruction
This thread has link to everything!
http://forum.xda-developers.com/showthread.php?t=1026660
Keep in mind that NVFLASH only restore or erase about 300MB of the 2GB out of the 16GB you can write to.
This is in no way a FULL tablet reset. It is however a dangerous tool above application are tested and proven, some older thread may have nvflash command that can be dangerous.
That is great information.
I have used the format flash, then Nvflash.
flashes work fine, but same issue. Stuck at G-tablet splash screen.
I still can not load update.zip because I can not transfer any large files to the tab when it is mounted.
Any time I try and transfer a file greater than about 100k I get an error that states "can not copy file due to an I/O error"
Really disheartening........
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
Alright, I hope I have this in the right place. I just recently flashed the TerraSilent Kernel for the Galaxy Player 4.0 US version. The Flash went fine, but my device was running extremely slowly. A re-flash didn't solve it either. I figured that wiping the cache partition might solve the problem - I decided to do this before running a backup, since no important data is stored in the cache (...right?), and since I was worried that backing up while I had this problem could make things worse - so I went ahead into CWM and did just that. Then, it reboots, and I nearly get a heart attack. The stock wallpaper is back, it's using the default launcher again (I had LauncherPro installed), and pretty much only system apps work, all the others have an icon with an SD card on it, and when clicked on, it says something like "application not installed". I did some searching, and it seemed like a reboot might help (although I didn't find anyone with a problem like mine anywhere). The reboot didn't do anything, so now I have it shut down, so that nothing can happen. The odd thing is, it doesn't seem to me like the system messed up and did a full wipe instead, either, because a couple of things I have are still there - for example, some of my bookmarks I made on the homescreen while still using the default launcher are still there. I'm really confused because I have wiped the cache partition before, when I was still on an unmodified stock kernel, and everything stayed the same, the way I thought it was supposed to. And now this happens. What do I do now? I exported my absolute most important data (Astrid Tasks and Calendar) before I installed TerraSilent (but I obviously wasn't able to do a full backup because I wasn't rooted, I figured installing TerraSilent would root it), so my absolute most important data is on my computer. I also did a simple file backup of the internal USB storage and external SD card to another computer before flashing TerraSilent. However, there is still a good deal of data still need, and a lot of data that would just be a pain in the rear to recreate, not to mention my (valuable to me) game data. What did I do wrong - or did something in the system mess up? And - what do I do to get back to where I was before?
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
ti-pich said:
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
Click to expand...
Click to collapse
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
trainman261 said:
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
Click to expand...
Click to collapse
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
And the conclusion...
ti-pich said:
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
Click to expand...
Click to collapse
OK, my reply is late, but thanks for your help. I managed to copy the partition with all the deleted contents over to the computer, and I'll have to study the contents some other time, because I've spent about 24+ hours on this problem in total, and need my device for more important purposes - those for which the data I managed to copy before the custom kernel and everything else. For those of you who have a similar issue, this is how I managed to save (or that is I am 95% sure this will have saved at least some, as I said I haven't studied it yet) what I hope is a good chunk of my data.
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I've got huge issue with steve's kernel. You can get into recovery, but once you booted in it will simply bootloop. Then you have to flash back with odin. So if you go with steve's kernel, don't boot into recovery. As for klin's kernel, I've never tried it, and will probably never as we have some really nice jellybean rom that I recommend you.
I never got that issue with steve's kernel.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
trainman261 said:
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
Click to expand...
Click to collapse
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
obscuresword said:
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
Click to expand...
Click to collapse
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
trainman261 said:
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
Click to expand...
Click to collapse
hmmm. I'm about to try Terrasilent with my YP-G1 (US version) running 2.3.6. This is giving me second thoughts. Does this kernel still cause issues with SGP 4.0s running GB 2.3.6?? Maybe I should try the old Steves Kernel? I just want to use voodoo sound - thats really the only reason I want to root and get these kernels.