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
Related
I've been stuck in a weird place for some time with my phone. After I installed clockwork mod, backed up, installed some flavour of FroYo, and made the mistake of trying to flash back my old back up without properly wiping things have been getting weird. I can use ODIN to flash fresh ROMs, but I always get a bunch of FCs at startup, and most apps don't work. I tried to do all kinds of tricks to completely wipe the internal SD, but there is always some remnants of old fun hanging about causing cascading errors and FCs. No matter what I try to do, MyBackupPro and Rommanager is always present, but not working.
How I can completely rid myself of anything not stock ROM?
I've finally gotten back to root ADB, after a long and hard battle. I believe this may hold the key to salvation for my Vibrant.
Any and all suggestions are much appreciated!
Things I've already tried:
EUGENE373_SamsungS_Froyo_PDA -> Stock 2.1 T959UVJFD
EUGENE373_SamsungS_Froyo_PDA -> battery pull -> Stock 2.1 T959UVJFD
Stock 2.1 T959UVJFD -> EUGENE373_SamsungS_Froyo_PDA
Bionix1.9.zip - would not install due to some error I can't recall right now. Will update.
Factory wipe - from Settings menu
Wipe in Clockworkmod menu
Wipe all in adb shell
The weird *2767*3855#* factory wipe
UPDATE:
Strangest thing happened: I flashed an old ROM back onto the phone with Odin 1.52, then the Updated Stock 2.1 also via Odin the usual FC-ing was still there. Then I rebooted into recovery, reinstalled the Clockworkmod recovery menu, installed the root-update.zip in order to have root shell access. Then I pushed VibrantDeodexed1_2.zip and Vibrantfroyo_R3.zip on to the sd card. I tried to apply the VibrantDeodexed1_2.zip, but it aborted due to some catalog not present. However, I did notice that the installation erased /system and deleted some files, and I had the notion to try and install the VibrantFroyo_R3.zip. The installation succeeded, and Lo and Behold!
the phone has returned to the land of the living! Wohoo!!
I do not fully understand how this can be, but there is no Force Closing of programs any longer. What a relief!
Thanks to everybody who contributed ideas!
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Yea, when in doubt I thank the deities for Eugene and flash his "Froyo that doesn't brick" followed by the stock JFD firmware.
Sent from my SGH-T959 using XDA App
brnagndan said:
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Click to expand...
Click to collapse
Sorry to say, that trying this solved nothing. Just the same as before.
ullrotta said:
Sorry to say, that trying this solved nothing. Just the same as before.
Click to expand...
Click to collapse
You clicked the "repartition" option? That should format your internal sd...
I7oobie said:
You clicked the "repartition" option? That should format your internal sd...
Click to expand...
Click to collapse
Yeah, that's the weird part.. It doesn't really delete anything. Files are still there, and so are the un-wanted system files, too.
Does anyone know if I can manually partition the sdcard?
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
same thing happened to me >.> I just formatted the SD card on the phone. then flashed whatever rom I wanted.
Br1cK'd said:
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
When I boot into recovery, I always have to reinstall packages to get to the CWM recovery menu. I tried to clear everything from the mounts and storage submenu; I cleared system, cache and data, then flashed stock eclair. STILL the same applications and files sit on the internal SD.
When performing the wiping, all looks normal. It does take a little time, and the system reports that all is going according to plan, yet no files are deleted.
What can possibly make the phone act this way? Are there no super secret samsung-technician codes that allow me to completely wipe clean the face of the sdcard?
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
this has to be one of the most useful threads. just last night i was messing with rom manager and enabled advanced settings, BEEFORE reading this thread. I've done so much monkeying, but didn't keep a journal or log, so ive got **** from so many hacks and tweaks (mods and themes)...
thanks, im gonna wipe this ****er clean.
Good Info..but moved to Q&A
Br1cK'd said:
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
ullrotta said:
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
Click to expand...
Click to collapse
I was hoping that would help you friend, that process wiped mine clean of all remnants. Good luck in getting her back into a functional state.
After reading som more, contacting Samsung Service, I've decided to send the phone in for service. [sigh]
I've learnt a lot about ADB, pushing and pulling files, rooting, unrooting, swapping ROMS and whatnot. Still, the phone is stuck in that weird place where I cannot delete files.
Hopefully the service team can fix this poor, misguided phone
No matter how many times I wipe my phone I still can't flash any pic the newer roms. I have root explorer an have been able to see that nothing changes. The weird thing is I'm not getting any errors after installing a Rom. Usually if there is a media folder on my SD card but never get passed the three skateboards. I can flash tazz14 an it boots just like I never took it off my phone. An no it wasn't flashed from a nand. Need help.
Sent from my Eris using XDA App
cpole17 said:
Usually if there is a media folder on my SD card but never get passed the three skateboards.
Click to expand...
Click to collapse
I intend no disrespect, and perhaps I am alone in this, but I'm having difficulty understanding, other than in a general sense, what this sentence means.
I agree. Don't really understand what you are saying. What are you trying to flash?
I've checked some of your previous post discussing the problem. It is unlikely but possible that your recovery image has been corrupted. I would suggest that you recover from a nandroid then run jcase's one click root app, don't worry about flashing rootme.zip, but do ensure that you reboot twice after running the app. And when you flash the ROM do both Dalvik wipe and factory/data wipe. Hope this works.
http://dl.dropbox.com/u/8699733/erisone010.apk
ok sorry for the broken sentences. I let my frustration get the best of me.
I use to be able to flash any rom. One day I decided to try some of Tazz and shed's roms. I had no problem flashing up to Tazz v14 and shed's v2. I tried to flash Tazz V15 and this is when I first noticed my problems.
When I would flash v15 or higher i would get the e: error in line 238 e:wasn't able to write boot image and installation aborted.
Shed's roms don't give me the error it just says installed from sdcard. On a re-boot I just get the skateboards and it never boots. just sits there. At first I thought I didn't wait log enough so I waited 20 minutes. Never booted.
I always do a factory/data and dalvik at least 3 times before trying to load a new rom
I don't believe it has anything to do with their roms. I went all the way back to 2.1 stock and started over. then one click eris root. It seems as if i flash a new rom the new stuff doesn't overwrite over the old system files.
sounds like it could be a couple of issues.
not sure what recovery you are using... but i'd read this thread here:
http://forum.xda-developers.com/showthread.php?t=827718
could be some very useful tips for clearing space on your phone.
reason i say that... if you are getting all the way to the boot image, then it's failing... then i'd say you either have a bad DL (check the md5's), a bad recovery image (already mentioned), or you are running out of space in /system/ block (maybe the reason some ROMs are successful in flashing, and not others... as the "heavier" ROMs maybe too big to fit on whatever amount of space you have left in /system/).
if you could, load/flash a ROM that works... then, from a command line, do the following and post it:
adb remount
adb shell
busybox df -h
copy/paste the results so we can have a look
Filesystem Size Used Available Use% Mounted on
tmpfs 95.4M 12.0K 95.4M 0% /dev
tmpfs 95.4M 0 95.4M 0% /mnt/asec
/dev/block/mtdblock3 170.0M 105.8M 64.2M 62% /system
/dev/block/mtdblock5 159.5M 37.0M 122.5M 23% /data
/dev/block/mtdblock4 130.0M 47.8M 82.2M 37% /cache
not sure if this is what you mean. never ran adb before.
I'm having a similar issue where I can't get past the skating androids when flashing new ROMs. KaosFroyo v37 is the only stable ROM I can flash. I've tried numerous things to fix with no luck. I hope we can find a fix.
P.S. - My mem usage breakdown looks very similar to yours. Within a few %.
There has to be away to clear alot of that data. Just don't know enough yet to do that.
Sent from my VANILLA TAZZ using XDA App
cpole17 said:
There has to be away to clear alot of that data. Just don't know enough yet to do that.
Sent from my VANILLA TAZZ using XDA App
Click to expand...
Click to collapse
hmmm... if I correctly recall there is a delete partition command associated with fastboot. I have no idea what would come of this. Perhaps as a last resort.
I haven't given up just have had no time to work on this.
Sent from my VANILLA TAZZ using XDA App
I'm still stuck with the same prob too. Here are a few things I have tried in the past week.
1. Repartition SD Card to 1 partition.
2. Format SD Card FAT32.
3. After flashing, booting w/o SD Card.
4. Completely unrooted back to 2.1, rerooted.
All of these were followed by a fully wipe, dav wipe, flashing new ROM and reboot and all resulted in endless skating androids.
I'm just stumped.
I have a feeling that the OP has one of those Erises that cannot be overclocked to 710 MHz; all of the latest ones seem to default to that. I'd say that it would be proved if you can flash Plain Jane and it works, as that defaults to stock 528 MHz.
I did find a way to alter the xtrROMs to allow a flash and then, before restarting the phone, using ADB commands to change the default maximum clock speed to something other than 710000. See http://androidforums.com/eris-all-things-root/212791-kernel-overclock-custom-rom-s.html#post1841188
It's worth a try, anyway. I'm not sure that I'd try it with anything other than xtrROM or xtrSENSE for now; I haven't checked any other ROMs to see if that would be the proper procedure.
I have been working with Conap who writes the kernel for many of the new roms out there for the past week and we finally resolved the issue. Apparently with CFSv6+ he added CIFS support to the kernel which was causing the boot problem for me. Try flashing his rom CELB v3.8 and see if it works for you.
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.
I was wondering if anyone could point me in the right direction for moving apps to my sd card. I'm currently rooted but on the stock 2.1. Have done some searching but haven't had much luck. I'm a newbie and haven't jumped in to the rom realm yet. Guess, I don't want to run the risk of screwing anything up. Any help would be greatly appreciated!
mattamous said:
I was wondering if anyone could point me in the right direction for moving apps to my sd card. I'm currently rooted but on the stock 2.1. Have done some searching but haven't had much luck. I'm a newbie and haven't jumped in to the rom realm yet. Guess, I don't want to run the risk of screwing anything up. Any help would be greatly appreciated!
Click to expand...
Click to collapse
It would probably be easiest to flash [ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense. It is extremely close to stock but has all the advantages including having Apps2SD built in. You can read zach.xtr's instructions for using Apps2SD under AndroidOS 2.1 in that first post in a section that's titled "Apps2sd and Cache2sd:".
roirraW "edor" ehT said:
It would probably be easiest to flash [ROM][GPL][3/15/2011] xtrSENSE5.0.1 [cache2cache,apps2sd,oc,jit]-HTC Sense. It is extremely close to stock but has all the advantages including having Apps2SD built in. You can read zach.xtr's instructions for using Apps2SD under AndroidOS 2.1 in that first post in a section that's titled "Apps2sd and Cache2sd:".
Click to expand...
Click to collapse
Are you currently running this rom? If so, have you come across an problems with it yet?
mattamous said:
Are you currently running this rom? If so, have you come across an problems with it yet?
Click to expand...
Click to collapse
The last version of this I used was v4.6.5, just less than a couple months ago. Before that I had run many versions of it and xtrROM. At the moment I'm using GSB v2.7.
I don't recall any problems with xtrSENSE at all, it's the ROM I recommend the most to people who ask for a recommendation.
roirraW "edor" ehT said:
The last version of this I used was v4.6.5, just less than a couple months ago. Before that I had run many versions of it and xtrROM. At the moment I'm using GSB v2.7.
I don't recall any problems with xtrSENSE at all, it's the ROM I recommend the most to people who ask for a recommendation.
Click to expand...
Click to collapse
I appreciate that. I'll continue to research it and take your recommendation into consideration. Just a little hesitant to roms still but if I want to better my eris, looks like I need to jump the gun a little.
xtrSENSE is a fantastic ROM and I also recommend it to anybody new to rooting, unless they are specific in wanting to get away from Sense at all costs, or needs something like Google Voice Search/Actions (which requires Froyo or better).
I have one issue with xtrSENSE, but it seems to be unique to me: after running the ROM for a while, the phone becomes erratic about reminders for items in my calendar. For example, if I have a meeting at 4:30 pm and have a reminder set to 15 minutes, after running these ROMs (xtrSENSE, xtrROM and stock, actually) for a while, they may or may not sound the reminder at 4:15 pm, as desired. Sometimes they do, often they don't - often, they will fire off at some random time hours later, and even rarely never remind me at all until I restart the phone, and then they all start pouring in.
This was the major reason why I finally rooted a few weeks after 2.1 finally came to the Eris last year.
I have never seen anybody else report this issue with xtrSENSE, though, so I continue to recommend it to others. It's great advantage is that if you have been running stock, it will look and feel just the same, except faster, with better battery life, without the lag that happens with stock as your text message and call log grows.
doogald said:
xtrSENSE is a fantastic ROM and I also recommend it to anybody new to rooting, unless they are specific in wanting to get away from Sense at all costs, or needs something like Google Voice Search/Actions (which requires Froyo or better).
I have one issue with xtrSENSE, but it seems to be unique to me: after running the ROM for a while, the phone becomes erratic about reminders for items in my calendar. For example, if I have a meeting at 4:30 pm and have a reminder set to 15 minutes, after running these ROMs (xtrSENSE, xtrROM and stock, actually) for a while, they may or may not sound the reminder at 4:15 pm, as desired. Sometimes they do, often they don't - often, they will fire off at some random time hours later, and even rarely never remind me at all until I restart the phone, and then they all start pouring in.
This was the major reason why I finally rooted a few weeks after 2.1 finally came to the Eris last year.
I have never seen anybody else report this issue with xtrSENSE, though, so I continue to recommend it to others. It's great advantage is that if you have been running stock, it will look and feel just the same, except faster, with better battery life, without the lag that happens with stock as your text message and call log grows.
Click to expand...
Click to collapse
That's because your Eris runs outside the normal space-time continuum.
So, after looking into both xtrROM and xtrSense, I'm not sure which would be the better idea. I don't have to have sense but both sound like they would be great roms. Also, should I stick with 2.1 or jump higher to 2.2 or even 2.3??
mattamous said:
So, after looking into both xtrROM and xtrSense, I'm not sure which would be the better idea. I don't have to have sense but both sound like they would be great roms. Also, should I stick with 2.1 or jump higher to 2.2 or even 2.3??
Click to expand...
Click to collapse
It would probably be best if you just start flashing some of them to see for yourself. Keep in mind that without the Sense home, the phone will feel a little different, plus not be able to use the Sense widgets. Since you already have experience with Sense, flash xtrROM and see how you like it. Then I would personally just skip right over 2.2 and go to 2.3 since it's essentially fully developed now.
I'm personally using GSB (soon to flash v2.8) and Tazz's Gingerbread ROM get's rave reviews, too.
Try a few ROMs and find out what you like best.
What's the best back up app? Or, with Astro and a nandroid, would that be good enough?
mattamous said:
What's the best back up app? Or, with Astro and a nandroid, would that be good enough?
Click to expand...
Click to collapse
As far as backing up your apps and/or their settings, I swore by My Backup Pro for quite a long time but since going to Gingerbread, I've taken advantage of Titanium Backup's ability to restore apps to where they were backed up from (not applicable to the stock ROM), which is handy for me because using Gingerbread's (or Froyo's) native Apps2SD, I have a total of 190 user and system apps.
I don't know if they've added any feature like that in My Backup. If they have, then it would have been very recently.
mattamous said:
What's the best back up app? Or, with Astro and a nandroid, would that be good enough?
Click to expand...
Click to collapse
Personally, I use cyanogen as my rom and nandroid to backup the phone...you know in case the rom fubars the phone.
Sent from my Eris ADR6200 using XDA App
I use titanium back up and copy my sdcard to my computer before doing a wipe also make a nandroid copy there as well.
I went with My Backup Pro and made a copy of my sd card to my laptop. I was trying this technique last night but it had an error at the end of the command prompt.
http://www.askstudent.com/how-to/resolve-phone-storage-space-is-getting-low-on-android-phones/
mattamous said:
I went with My Backup Pro and made a copy of my sd card to my laptop. I was trying this technique last night but it had an error at the end of the command prompt.
http://www.askstudent.com/how-to/resolve-phone-storage-space-is-getting-low-on-android-phones/
Click to expand...
Click to collapse
I see this at that link:
However, Google listened and with Froyo or Android 2.2 release, they included the App2SD functionality.
Click to expand...
Click to collapse
You said you're on rooted stock, and those instructions are for 2.2+ ROMs only so it won't help you unless you since flashed another ROM. Have you? If so, which one?
Also, those instructions are purely to help move apps which normally wouldn't allow you to move them, which as I might've said Titanium Backup (paid version) will allow you to do by the Batch, and the free "Install Manager" may allow you to do so in batch, too, I've just read.
roirraW "edor" ehT said:
I see this at that link:
You said you're on rooted stock, and those instructions are for 2.2+ ROMs only so it won't help you unless you since flashed another ROM. Have you? If so, which one?
Also, those instructions are purely to help move apps which normally wouldn't allow you to move them, which as I might've said Titanium Backup (paid version) will allow you to do by the Batch, and the free "Install Manager" may allow you to do so in batch, too, I've just read.
Click to expand...
Click to collapse
Somehow, I must have missed that. I haven't flashed anything just yet; I was hoping that would do the trick before I went to flashing a rom. I downloaded the free version of titanium last night but it wouldn't backup, saying that I didn't have busybox. I downloaded busybox afterwards but it had a few warnings right at the beginning that I wasn't sure about so that's why I went with backup pro. I just checked into install manager but it isn't in the market.
With the help you have already given, is there a set of instructions for the nandroid backup process? I'm kinda interested in xtrROM but want to get all my ducks in a row before I flash it. Thanks for the help! Appreciate it!
mattamous said:
Somehow, I must have missed that. I haven't flashed anything just yet; I was hoping that would do the trick before I went to flashing a rom. I downloaded the free version of titanium last night but it wouldn't backup, saying that I didn't have busybox. I downloaded busybox afterwards but it had a few warnings right at the beginning that I wasn't sure about so that's why I went with backup pro. I just checked into install manager but it isn't in the market.
With the help you have already given, is there a set of instructions for the nandroid backup process? I'm kinda interested in xtrROM but want to get all my ducks in a row before I flash it. Thanks for the help! Appreciate it!
Click to expand...
Click to collapse
BusyBox is included with any custom ROM, another reason it's just easier to flash a ROM like xtrSENSE or xtrROM as you mentioned, although with Apps2SD under Android 2.1, you need to backup the entire contents of your SD card, repartition it to include an Ext2 partition and 0 (zero) Swap, and the rest FAT32 as normal. All can be done from Recovery.
What method did you use to root? I'm assuming that whatever method you used installed a custom recovery. To make sure you do have a custom recovery, turn the phone off, press and HOLD the volume up button and press the End button long enough to turn the phone on. Keep holding the volume up button for a few seconds longer. When it goes into recovery if you have Amon RA recovery it should say something like amon-ra-eris-1.6.2 at the bottom.
In Amon RA recovery, reference http://forum.xda-developers.com/showthread.php?t=648025 there are these menu options:
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a Nand backup, the following partitions are NOT included :
Recovery (to avoid restoring old version)
Cache (no need to backup imo)
Misc (no need to backup imo + restore issues on some phones)
Splash1+2 (no need to backup imo + restore issues on some phones)
Nand + ext backup :: Make a Nand + ext backup
Nand restore :: Restore a Nand backup
BART backup :: Make a BART backup (Nand + ext)
BART restore :: Restore latest BART backup
Flash zip from sdcard :: Flash a zip update file from your sdcard
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Other
Fix apk uid mismatches :: Does extacly that
Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Click to expand...
Click to collapse
To make a nandroid, just choose the "Backup/Restore" menu with your trackball, then choose "Nand backup".
The Market search is quirky. Here's a link to Install Manager on the market: https://market.android.com/details?id=com.beidl.chooseloc.
Install Manager or anything else having to do with Apps2SD won't do you any good without either flashing the Apps2SD script from recovery, or flashing a custom ROM that includes Apps2SD.
You can find the most important information via links from the Eris Roll-up Thread.
Thank you very much! A huge help! I used the 1 click Eris root.
Flashed xtrROM based on your recommendation and so far its pretty rad. Really smooth and quick too.
im looking for some info working with a droid eris used 1click method to root ive got the 2.2 froshedyo 11 rom the kernel is 2.6.29 DECAFUCTCFS-dirty the person im doing this for really wants the HTC widgets back so im looking and getting a good feel about the xtrsense5.0.1 rom but the only thing im not sure of is wiping sd ext partition is that something i need to do or is that only if im planning on using the app2sd im alil lost about that part and the whole partition process id ask there but not enough posting yet to do so the recovery is the RA-eris-v1.6.2 so there i should b good to go thanks for any and all info out there
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.