Related
****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary
Hi! I'm a placeholder.
garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.
Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.
Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary
link posted for testing.
thanks again gary loving it.
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.
chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary
thank you. Gary tried not to get Banned OK? we need you buddy. lol
chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary
not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.
chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.
it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary
worked like a charm...backup and restore works perfectly...
thanks gary !!!
Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk
jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).
Maniacs Arrival based off of .26 ota Firmware
I am not responsible for any bricks, crashes, or warrenty replacements. However, if the Joker takes your city hostage, please let me know so I can use my Batman Halloween costume and fight evil.
Realize that there many be bugs with this build, although minimal as this is basically stock but i will get around to fixing them. thats a promise
Based off of System Dump of .26 Firmware
Deodexed, Zipaligned, and rooted with provided superuser.zip
Debloated of many Asus apps, more to come in future updates
Awesomeness put in, find out for yourself
Requirements:
1. Rooted TF700
2. Unlocked bootloader provided by Asus Unlock apk
3. TWRP installed (easiest way is to flash through goomanager)
4. A general idea of what you are getting into
Procedure:
1. Download Rom provided at end of post
2. Download superuser.zip provided at end of post
3. Copy both Rom and superuser.zip to the root of your MicroSD/Internal Storage (personally prefer MicroSD)
4. Boot into TWRP recovery
5. Make a full backup in TWRP
6. Factory reset in wipe options
6.5. If wiling wipe both cache and dalvik cache, as it provides a possible cleaner install
7. Flash Maniacs Arrival ROM
8. Flash superuser.zip to ensure proper root access
9. Reboot. Please be patient as the initial boot could take up to 5 minutes, this is not the fault of the ROM
10. Profit!
Credits go out to the following for their support and help:
1. eoh7678 for his updater-script which caused me multiple problems and his permission to use certain files
2. zeus34 for his support as we have been working days trying to make this all happen for you guys
3. KilerG for his look ins and his general support (plus his willingness to actually "learn something new")
4. Google for the continued ability to let us do as we want with our Android Devices
5. Asus for giving us the Unlock apk to flash custom roms and make the device how we truely want it
I have no issues with anyone who wants to use this ROM as a base for their themes or own custom roms, as long as credit is given where credit is due
Downloads:
ROM: http://www.4shared.com/zip/V_PIuSLS/Maniacs_Arrival.html MD5: fcc91b4e9b6e7429ee47d4719de60e26
Superuser: https://dl.dropbox.com/u/43420190/Superuser-3.1.3-arm-signed.zip
CHANGELOG:
1.0: Initial Release
mein mein mein!
just what i was waiting on!
Nice!
Yes, it's true. I have a weakness for learning about technology. And I certainly did learn a bit.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Just downloaded! Where's the MD5 checksum? I see the file was deleted? I will hold off until MD5 checksum is posted.
rsbuffalo said:
Just downloaded! Where's the MD5 checksum? I see the file was deleted? I will hold off until MD5 checksum is posted.
Click to expand...
Click to collapse
Might want to re download, had to fix a bug not allowing us to update certain apps. But the md5 is fcc91b4e9b6e7429ee47d4719de60e26
Sent from my SCH-I535 using xda premium
Congratulations! I did successfully install your ROM and rebuilt about 400 installed apps with TB. Everything worked great!
Issues were in TWRP:
1.) Used SanDisk 64GB Mobile Ultra MicroSDXC Class 10 UHS-1 - works with 26 firmware in Android ICS OS.
2.) TWRP will not mount this MicroSD in Recovery - I did Factory Reset and wiped caches now TWRP can't find zips on the MicroSD. (TWRP worked this weekend with a 16GB MicroSDHC Restoring Backups and seeing ROM zips).
3.) Did a TWRP Restore (worked) - Moved ROM & SU zips to internal storage.
4.) Found zips internal storage and flashed successfully with SU in apps. About Tablet shows "Maniacs Arrival".
5.) I did not see busybox after ROM installed?
6.) Only 1-app in TB backup did NOT restore - "Unlock Device Tool 7.0" just uncheck in Restore missing apps with data. Otherwise, TB will hang.
7.) Still unlocked so probably don't need the "Unlock Device Tool 7.0" app installed any more (have a TWRP backup though).
8.) I backedup Nova launcher and restored that successfully as well.
Hope this testing helps!
I will run this ROM for now and report if I find any issues. Not much different from what I had before flashing. However, a good start.
Good Job!
That's exactly what it is. A start. Appreciate the feedback and there will be more to come in the future
Sent from my SCH-I535 using xda premium
Thanks
Great job.
still waiting on tf700, but thanks for the rom!
Language
Hi,
does this ROM support German language?
Thanks
My lock button doesn't lock the tab or pop up the shutdown menu.
Alphaform said:
Hi,
does this ROM support German language?
Thanks
Click to expand...
Click to collapse
I did not take out any language support, so if it was in stock it should be in here.
jbdub1771 said:
My lock button doesn't lock the tab or pop up the shutdown menu.
Click to expand...
Click to collapse
I'm sorry, but what do you mean by lock button? Do you mean the power off button?
Sent from my SCH-I535 using xda premium
Was this based off the WW or the US OTA? (and with that.. does it even matter if we're running US version on our WW version? Any differences?). I'll give it a try later on once I've get my new microSD today (apparently it's not wise to let my cat chew it and spit it out again .. seriously /fail).
rsbuffalo said:
Congratulations! I did successfully install your ROM and rebuilt about 400 installed apps with TB. Everything worked great!
Issues were in TWRP:
1.) Used SanDisk 64GB Mobile Ultra MicroSDXC Class 10 UHS-1 - works with 26 firmware in Android ICS OS.
2.) TWRP will not mount this MicroSD in Recovery - I did Factory Reset and wiped caches now TWRP can't find zips on the MicroSD. (TWRP worked this weekend with a 16GB MicroSDHC Restoring Backups and seeing ROM zips).
3.) Did a TWRP Restore (worked) - Moved ROM & SU zips to internal storage.
4.) Found zips internal storage and flashed successfully with SU in apps. About Tablet shows "Maniacs Arrival".
5.) I did not see busybox after ROM installed?
6.) Only 1-app in TB backup did NOT restore - "Unlock Device Tool 7.0" just uncheck in Restore missing apps with data. Otherwise, TB will hang.
7.) Still unlocked so probably don't need the "Unlock Device Tool 7.0" app installed any more (have a TWRP backup though).
8.) I backedup Nova launcher and restored that successfully as well.
Hope this testing helps!
I will run this ROM for now and report if I find any issues. Not much different from what I had before flashing. However, a good start.
Good Job!
Click to expand...
Click to collapse
Many 64GB sdcards are formatted as exFAT instead of regular FAT. If you reformat the card to regular FAT then it should work in TWRP.
Dees_Troy:
Reformatted 64gb card using GParted to FAT32 still no go in TWRP with this card. Android ICS finds all formats in MicroSD slot with firmware 26.
Seems the thread has died a biy, maybe time to update things a bit?
Sent from my Galaxy Nexus using xda premium
ftmaniac948 said:
Seems the thread has died a biy, maybe time to update things a bit?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This is a base ROM...not going to be a ton of excitement about it.
Hey guys, I got the Transformer Infinity yesterday and I am just in love with it. I was on the fence about rooting and unlocking it because it just seemed so great already but I am a flashoholic for I have an Inspire 4g that I mess around with a lot, so I had to do it. BUT ANYWAYS, I was wondering, does this rom remove any of the preinstalled apps? I really got accustomed to the widgets and app backup. I had flashed the ROM Zeus_TF700T_series_v4.0 but it had removed most everything that was preinstalled and I missed it. Does this ROM remove anything or even does it add anything?? ALSO, when the Jelly Bean Update comes out, would I be able to update from this ROM? Any feedback would be much appreciated, and sorry for writing a whole novel, I just have a lot of questions.
Hi young grasshoppers
I'm an aging PC hacker (down to disassembling viruses with Softice and the works, I'm THAT old!) with a splendid TF101 and I could use an upgrade to my brain and my TF101. I looked for a thorough FAQ to get a clue, but clue I didn't get.
Long story short, one year ago I rooted my TF101 in a rush with success, but didn't have enough time to do the homework and RTFM as I am used to (damn crisis!).
Presently the TF101 has Prime! 1.4 (Android 3.1), Kernel 2.6.36.3-00001-gf377a2b, CWM Recovery 3.1.0.1 Solarnz-R3-230511
My goals are two:
1. trying the new 4.x roms on my TF101;
2. get a clue;
My mental framework comes from PC: mobo holds flashable ROMs and BIOS, hd holds Operating System(s), Apps and Bootloader. As I don't know how the TF101 and Android's structureI'm a little bit lost and I don't want to brick it or upgrading without understanding how to restore it to its present state.
As far as I understood, the TF101 has: Internal SD (holding apps and kernel ? ), external SD aka MicroSD holding media and apps movable to SD, some flashable memory for ROM (?).
As I was cosidering trying Android Revolution HD 3.5.1, I noticed that it requires: CWM v3.2.0.1 and a Super Wipe Full which scared the hell out of me...what is it going to Wipe??? ...and rooting made by RazorClaw
What I would like to understand is:
1. How do I backup the present Kernel and Apps and eventually restore it ? Under CWM 3.1.0.1 I just did a (I believe it's called) Nandroid System Backup that was stored to the MicroSD (external SD) ... what did I just back up ? Kernel,apps,both?
1.1 CWM also offers the Factory Wipe/ Reset function: what does it do? Does it restore the OLD (original as bought) Rom and wipes the Kernelt (and deletes the apps) so that it basically reverts to my original unrooted TF101 as-bought?
1.2 Upgrading the CMW would need: copying the new CWM zip into the external SD card, launcing CWM and using the upgrade procedure?
2. As apparently I need to root throught RazorClaw, I think the present rooting might interfere w/ ARevolution installation. So what would the correct unrootin procedure would be, considered my situation? I'm aware that some apps are able to unroot, but not being sure I'd rather ask.
Finally, I would absolutely love to know if there's a post generally addressing my doubts, giving me an overview of a. what's get modded by rooting b. and where c. and what ROM, Kernel, Bootloaders are in a TF101 or (more generally) in the Android world.
Thanks a lot for your help and for giving me some clues! :laugh:
Ill try to answer your questions as best i can
1.0 Nandroid backs up your rom, apps and appdata not the kernel
1.1 Factory reset wipes apps, data and internal sd it does not change your rom or kernel
1.2 Yup just copy over the new cwm (rouge or twrp are my favorites) and navigate to the file in cwm and hit install
2. If you already on prime you are already rooted so thats not a problem
Rooting just allows you elevated privileges like read/write in the system and things like that. Its like su is essentially sudo
All rooting is is putting the su.sh and busybox.sh into the system using an exploit
You really should not restore a kernel from android 3.1 on anything but 3.1 or your going to have a bad time
Before you update make sure to back up your apps. Titanium Backup is a good choice
Most the roms that are currently active are Jelly bean betas which are a little unstable so i would go with a nice stable ICS rom like megatron or revolver
There is a lot of info in the android general form that you might want to read through but a most development seems to be device specific
elpapacito said:
Hi young grasshoppers
I'm an aging PC hacker (down to disassembling viruses with Softice and the works, I'm THAT old!) with a splendid TF101 and I could use an upgrade to my brain and my TF101. I looked for a thorough FAQ to get a clue, but clue I didn't get.
Long story short, one year ago I rooted my TF101 in a rush with success, but didn't have enough time to do the homework and RTFM as I am used to (damn crisis!).
Presently the TF101 has Prime! 1.4 (Android 3.1), Kernel 2.6.36.3-00001-gf377a2b, CWM Recovery 3.1.0.1 Solarnz-R3-230511
My goals are two:
1. trying the new 4.x roms on my TF101;
2. get a clue;
My mental framework comes from PC: mobo holds flashable ROMs and BIOS, hd holds Operating System(s), Apps and Bootloader. As I don't know how the TF101 and Android's structureI'm a little bit lost and I don't want to brick it or upgrading without understanding how to restore it to its present state.
As far as I understood, the TF101 has: Internal SD (holding apps and kernel ? ), external SD aka MicroSD holding media and apps movable to SD, some flashable memory for ROM (?).
As I was cosidering trying Android Revolution HD 3.5.1, I noticed that it requires: CWM v3.2.0.1 and a Super Wipe Full which scared the hell out of me...what is it going to Wipe??? ...and rooting made by RazorClaw
What I would like to understand is:
1. How do I backup the present Kernel and Apps and eventually restore it ? Under CWM 3.1.0.1 I just did a (I believe it's called) Nandroid System Backup that was stored to the MicroSD (external SD) ... what did I just back up ? Kernel,apps,both?
1.1 CWM also offers the Factory Wipe/ Reset function: what does it do? Does it restore the OLD (original as bought) Rom and wipes the Kernelt (and deletes the apps) so that it basically reverts to my original unrooted TF101 as-bought?
1.2 Upgrading the CMW would need: copying the new CWM zip into the external SD card, launcing CWM and using the upgrade procedure?
2. As apparently I need to root throught RazorClaw, I think the present rooting might interfere w/ ARevolution installation. So what would the correct unrootin procedure would be, considered my situation? I'm aware that some apps are able to unroot, but not being sure I'd rather ask.
Finally, I would absolutely love to know if there's a post generally addressing my doubts, giving me an overview of a. what's get modded by rooting b. and where c. and what ROM, Kernel, Bootloaders are in a TF101 or (more generally) in the Android world.
Thanks a lot for your help and for giving me some clues! :laugh:
Click to expand...
Click to collapse
OK here goes:
You have a custom recovery (CWM) which will allow you to flash whatever you like. There are other versions of recoveries out there CWM, rougue, etc. They all do the similar things, but some have more features than others. The nice part is that you can use one recovery to flash another. My personal preference is for the simpler versions.
1) The nandroid backup backs up system and data, but not the kernel (aka boot.img). This is typical for TFs- I think it's because the kernel is usually flashed through the staging partition and not directly in recovery, like many other android devices. The issue with not having a kernel backup when you restore a backup to "go back" but you have an incompatible kernel. This could happen if you flash a jelly bean rom and then decide to restore a backup to go back to prime (honeycomb). You'll get boot loops and hangs, but you will be able to go back to recovery and flash a compatible kernel.
1.1) Factory wipe will wipe the data partition, which is where all your info is kept. Other roms, this is called userspace. The system partition is untouched, so it will still boot, but you will have to reconfigure wifi, email, bookmarks, etc.
1.2) Essentially, yes. If you can get a CWM flashable version of a recovery, you can flash it in CWM or any other custom recovery. It will be a zip file. Be warned, some versions of recovery don't see or use the external SD card, so be sure your files are somewhere you can get to them. If only I had a $1 for every time someone flashed CWM 5.x and then did a superwipe- it uses the internal SD card and the superwipe erases all the roms and backups they had.
2) You are already rooted because you have Prime 1.4. You can use CWM to flash any rom you like, including stock, as long as you don't overwrite the recovery.
Most android users are obsessed with wiping and super-wiping. It's usually only necessary when going from a custom (a la ASUS) rom to an AOSP rom or vice-versa, and even then it will probably be fine.
---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------
As far as rooting goes, it's usually an exploit that allows root level access to the file system.
I think technically, all that is needed is the su binary installed in the system folder so that it is persistent and executable. Of course, the system folder on stock roms is usually read only, which makes the exploit necessary. On custom roms, su is usually pre-installed in system/bin or system/xbin.
Follow these steps... download TWRP (its a recovery), download either ICS jelly bean ROM... place both of them in your SD card ( internal and external). Place it both because I don't know what version of CWM you are using... now restart you tablet into recovery ( press both power and volume down buttons together and as soon as tablet turns on press volume up button)... now go to the folder where you placed your recovery (TWRP.ZIP) flash/install it and reboot into recovery... now wipe (factory data, cache wipe, dalvik wipe, system, internal memory)... after these steps install the required kernel and flash the ROM... wipe dalvik cache and cache again and restart... you are good to go...
If you want to back up your old OS.. select backup and recovery option in recovery and do a backup..
Link for twrp
http://forum.xda-developers.com/showthread.php?p=28454456
Link to kernel
http://forum.xda-developers.com/showthread.php?p=29010487
Link to jelly bean ROM
AOSP ROM
http://forum.xda-developers.com/showthread.php?p=28915296
Team eos ROM
http://forum.xda-developers.com/showthread.php?p=28992514
Coming to your questions
Root access..... it gives you administrator access called superuser by which you can remove/modify/change system apps or configurations. Since you already have cwm access i assume you have superuser/root privileges. So don't worry about it... all you need to do is download the latest recovery from above link and install it through recovery. To install choose "install from SD card" and not "update from SD card"
I wouldn't advice you to back up anything because there is no use and sometimes backed apps with data give problems like random restarts/force close etc... if you still want then you can backup from recovery but it won't back up the kernel... it backs up all your system but not kernel.
Your tablet is already rooted because you have recovery access. So don't worry about rooting... if you want to unroot anytime then search for easy flash/nvflash method..
Ask questions if you have more doubts
GOOD LUCK
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
Follow these steps... [...]. now wipe (factory data, cache wipe, dalvik wipe, system, internal memory)... [...]
If you want to back up your old OS.. select backup and recovery option in recovery and do a backup..
Click to expand...
Click to collapse
First socks, then shoes!
WOW thank guys, many answers and many very detailed options! You rock!
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Udupa82: wow thanks for the very detailed instructions. For the time being, I guess I'll go with Ice Cream
as I gather that Jelly Beans are still not stable...unfortunately I can't really afford the luxury of having TF101 misbehaving or
behaving weirdly (that's why I staid one year with a stable rom, I already have enough issues to address in work life, so I have
to have the Transformer running and upgraded within the week..so that if problems arises, I still have time to fix it).
Anyhow I succesfully installed CWM v3.2.0.1 - but your detailed indications made me wonder one thing: is it safer to
always place the ROM/other zip packages ALSO in the root of the internal SD (assuming having SU privileges allows me to write
in the root dir of the internal SD) ?
I also gather that restoring an Apps Backup may not be the brightest idea when doing such a jump from a 3.1 to 4.0.3 or higher,
so I guess the Titanium Backup at this point may generate more problems than It would solve.
All: as for the Kernel, I figured by the very few modded kernels (fewer people know how to mess with it properly) I've found
on XDA and by their description that kernels indeed manage the core functions of the machine, which had me wondering if any
of you guys had issues with Kernel 2.6.36.3-00001-gf377a2b in combination with some ICS or Jelly Bean Rom.
Thanks a lot for your precious directions!
elpapacito said:
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Click to expand...
Click to collapse
The ASUS rom is just the stock firmware that comes with the TF. It has whatever bloatware they ASUS decided to put on there. The AOSP is built from the google code and usually contains little or no bloatware. The AOSP roms are usually cooked up by devs here on XDA. CyanogenMod is a AOSP based rom, for example.
The recovery is located on the SOS partition. I don't think you can erase it by wiping or even super wiping. Wheelie or nvflash (which is the nvidia bootloader) can wipe the partition.
elpapacito said:
WOW thank guys, many answers and many very detailed options! You rock!
Gee One: oh I see, so Superwise indeed does delete and format, so bye bye to any Titanium Backup on the internal SD.
Brilliant, so I guess I have to move the backup directory to the external (microsd).
Two more fast questions : what's the difference (roughly) between a "custom (a la ASUS)" ROM and an AOSP rom?
And the second one: you state that "You can use CWM to flash any rom you like, including stock, as long as
you don't overwrite the recovery." Oh wow, makes sense..without recovery it's pretty darn difficult to flash anything...but
where does Recovery reside? On the internal SD? I wouldn't like to accidentaly Wipe it out the machine.
Udupa82: wow thanks for the very detailed instructions. For the time being, I guess I'll go with Ice Cream
as I gather that Jelly Beans are still not stable...unfortunately I can't really afford the luxury of having TF101 misbehaving or
behaving weirdly (that's why I staid one year with a stable rom, I already have enough issues to address in work life, so I have
to have the Transformer running and upgraded within the week..so that if problems arises, I still have time to fix it).
Anyhow I succesfully installed CWM v3.2.0.1 - but your detailed indications made me wonder one thing: is it safer to
always place the ROM/other zip packages ALSO in the root of the internal SD (assuming having SU privileges allows me to write
in the root dir of the internal SD) ?
I also gather that restoring an Apps Backup may not be the brightest idea when doing such a jump from a 3.1 to 4.0.3 or higher,
so I guess the Titanium Backup at this point may generate more problems than It would solve.
All: as for the Kernel, I figured by the very few modded kernels (fewer people know how to mess with it properly) I've found
on XDA and by their description that kernels indeed manage the core functions of the machine, which had me wondering if any
of you guys had issues with Kernel 2.6.36.3-00001-gf377a2b in combination with some ICS or Jelly Bean Rom.
Thanks a lot for your precious directions!
Click to expand...
Click to collapse
As far as I remember CWM 3.2.0.1 will give you access to external SD card so no need to place the zip file in internal memory... but creating a copy in internal is always better... remember CWM 5.x.x.x version doesn't allow external SD access so never install it...
Do not use restore apps from backup as I always faced problem of force closing. If you still want to then back up any app which is important to you using titanium backup..
Asus stock ROM= its the ROM from Asus with some added softwares from Asus..
AOSP= Android Open Source Project is a OS usually written from scratch using Google's / android's source codes as android is a open software, it comes without any added software(plus point) and more setting/ tweak options(plus point)
There are some good and stable ROMs... but if you don't want much issues then I advice to go for rooted/detoxed stock ROMs because they dont need any custom kernels
Revolver ICS
http://forum.xda-developers.com/showthread.php?p=23000467
Android Revolution HD
http://forum.xda-developers.com/showthread.php?p=17202357
Good luck
Sent from my Transformer TF101 using xda app-developers app
Android Revolution HD
http://forum.xda-developers.com/showthread.php?p=17202357
Good luck
Thanks guys, the upgrade was succesfull! Indeed there's a world of a difference in speed from 3.1 to ARevolution HD..smooth as silk so far Thanks a lot for the help!
Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
lotherius said:
...on my 2012 Nexus 7 I was having a lot of lag issues using stock/Faux123. It was painfully slow at times, even just waking the screen. I converted to F2FS (data only, not system), and the problems evaporated. [...] It was slow before, then it was fast. I had tried multiple other solutions prior to F2FS that didn't work. Many other users on the N7 2012 have also reported the same experience.
Click to expand...
Click to collapse
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]
Narciso Neto said:
Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]
Click to expand...
Click to collapse
Have you find solution?
I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.
Will it delete all the files in internal storage?
shsagnik said:
Will it delete all the files in internal storage?
Click to expand...
Click to collapse
Yes, it'll as we'll format the partition as F2FS. Make a backup if you have important data on there.
willianalberto said:
I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.
Click to expand...
Click to collapse
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.
jcooler said:
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.
Click to expand...
Click to collapse
Have you tried converting AFTER CM boots the first time? Also, are you using the latest build? It can be TWRP's fault too (just read on a thread on ASUS) or maybe our device don't support F2FS yet.
I have managed 2 convert many ROMs for the tab 2. I've spent hours reading about it in the past. As far as I'm aware no lollipop ROMs can convert yet as u also need a custom kernel that supports f2fs. U should be able 2 convert most KitKat ROM s with the right tools. Its only about 4 lines of the updater script 2 edit then find a kernel that supports ur ROM and f2fs like agni,dhollmen or blackhawk. Youll also need custom recovery thats f2fs ready, theres a twrp and philz download around. pitty easy once you do it ab couple of times. Hope that helps u......
Are there performance improvements?
There was quite a bit improvement, first sign of any custom kernel for lollipop that support's f2fs I'll be trying 2 convert the ROM to see the comparison's. Think that might be a little time away yet tho........
I've opo and like to migrate on CM12 nightly with F2Fs but stopped on boot logo with AK kernel any suggestion??
-cm-12-20150312-NIGHTLY-bacon.zip
-AK.128.OPO.SKULL.CM12.zip
-formatted cache, data, system, sdcard as f2fs by philz_touch_6.59.1
what's wrong?
I've TWRP 2.7 and Crombi-KK. V11.0-20140402-Crombi-kk4.4.2.tf700t. All my apps are "not responding". Would like to clear everything out and reboot in a raw Crombi (don't want to reflash it if possible). Also heard that formatting to fs2f is a screamer, which WOULD mean a reflash, but THAT would be alright if the bennies out-weigh me doing it.
What do I wipe (I HAVE read many other posts, but if I don't ask, I'll **** it up - I have)?
Thanks.
I'm assuming that I factory wipe, wipe cache, then flash cm-11.0-20140921-tf700t-crombi-kk-R1_signed - which will start me over.
Your reluctance to reflash the rom doesn't really make sense to me. All your apps are not responding, you want to "clear everything out" but not reflash? Why?
You could try to just wipe cache and Dalvik and see if that clears out whatever is going on (assuming you are not that well versed in reading a logcat which would be the analytic way to go about this....). That would not touch anything of your current setup.
If that doesn't do it you would have to at least wipe data and then all your apps are gone anyway - why not reflash the rom at the same time????
But you are on a rom that is no longer supported, no further development will happen here, so I would recommend you grab this chance to give your tablet a facelift and switch to where the action is
To do that do these steps in order:
1. Copy anything worth a damn off the tablet
2. fastboot flash lj50036's Kang TWRP 2.8.6 from the Development section (or use his flashable zip in your current recovery). Reboot
3. download ZOMBi-POP and put it onto a fat32 formatted microSD
4. boot into TWRP, go to Wipe > Advanced and format data. This will take up to 90 minutes - do not interrupt it, deep cleaning is going on.
5. Under the Wipe menu find the change/repair file system option and change data (and only data) to f2fs (I have a guide on how to do it in the General section)
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
6. Flash ZOMBI-POP
7. go through basic setup, then leave it alone for 30 minutes to settle in
8. prepare to be amazed
berndblb said:
Your reluctance to reflash the rom doesn't really make sense to me. All your apps are not responding, you want to "clear everything out" but not reflash? Why?
You could try to just wipe cache and Dalvik and see if that clears out whatever is going on (assuming you are not that well versed in reading a logcat which would be the analytic way to go about this....). That would not touch anything of your current setup.
If that doesn't do it you would have to at least wipe data and then all your apps are gone anyway - why not reflash the rom at the same time????
But you are on a rom that is no longer supported, no further development will happen here, so I would recommend you grab this chance to give your tablet a facelift and switch to where the action is
To do that do these steps in order:
1. Copy anything worth a damn off the tablet
2. fastboot flash lj50036's Kang TWRP 2.8.6 from the Development section (or use his flashable zip in your current recovery). Reboot
3. download ZOMBi-POP and put it onto a fat32 formatted microSD
4. boot into TWRP, go to Wipe > Advanced and format data. This will take up to 90 minutes - do not interrupt it, deep cleaning is going on.
5. Under the Wipe menu find the change/repair file system option and change data (and only data) to f2fs (I have a guide on how to do it in the General section)
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
6. Flash ZOMBI-POP
7. go through basic setup, then leave it alone for 30 minutes to settle in
8. prepare to be amazed
Click to expand...
Click to collapse
Thank for your extensive reply. I had already (after re-reading what I had posted) decided to do as you have described. Am installing TWRP today, tomorrow the rest.
I'm using the TWRP Manager having informed it that this is a tf700t, and I'd like to "flash" 2.8.6, it is asking me if /dev/block/mmcblk0p4 && reboot is correct to write to. As I DO NOT profess to be anything other then a 2* newbie with android - I ask, on a T700 is this correct?
AND may I ask a few more questions should I need to? Although the rest is straight forward.
I would not use TWRP manager for anything - even if it happens to identify the correct partition in this case. p4 is the staging partition and that is ok, but still - I have seen TWRP manager do bad stuff - don't use it.
And you don't have to. lj's kang twrp comes in a flashable zip. Just download it, enter your current recovery, flash it and reboot. Bingo - you are now on TWRP 2.8.6
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Post 2, second link
Ask as much as you like. I don't HAVE to answer, right?
Except for that itch I seem to have to keep scratching :silly:
berndblb said:
I would not use TWRP manager for anything - even if it happens to identify the correct partition in this case. p4 is the staging partition and that is ok, but still - I have seen TWRP manager do bad stuff - don't use it.
And you don't have to. lj's kang twrp comes in a flashable zip. Just download it, enter your current recovery, flash it and reboot. Bingo - you are now on TWRP 2.8.6
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Post 2, second link
Ask as much as you like. I don't HAVE to answer, right?
Except for that itch I seem to have to keep scratching :silly:
Click to expand...
Click to collapse
The more I read the more I was disinclined to use the Manager, but couldn't find - and I DID look, the blob, or flashable zip to use!?!?!
So I'm formatting extfs4, THEN changing to f2fs? I changed it to f2fs, which took 10 seconds, then realized I had reversed it. No harm no foul I assume as it is formatting now - and finished in about 30 minutes?
Is this th eversion you suggest: ZOMBi-POP-5.1_B6_omni_tf700t-KANG_signed.zip
Well, I do not have any hard data on this and my knowledge of block devices is more than rudimentary, but the background is this:
Since about TWRP 2.7.x this recovery does a "secure erase" if you format your data partition ext4. All the blocks get wiped before the new file system is created. Just changing the file system to f2fs does not do that and my thinking is: Can't hurt to really, totally wipe your data partition after a couple of years of use, so why not do it once in a while.
Here's what the master said about that:
http://forum.xda-developers.com/showpost.php?p=60189650&postcount=1806
Is it necessary to format ext4, then switch to f2fs? I doubt it. Is it better? I have no idea, but that's what I did
Yes, the b6 is the latest version of ZOMBi-POP. Flash it
berndblb said:
Well, I do not have any hard data on this and my knowledge of block devices is more than rudimentary, but the background is this:
Since about TWRP 2.7.x this recovery does a "secure erase" if you format your data partition ext4. All the blocks get wiped before the new file system is created. Just changing the file system to f2fs does not do that and my thinking is: Can't hurt to really, totally wipe your data partition after a couple of years of use, so why not do it once in a while.
Here's what the master said about that:
http://forum.xda-developers.com/showpost.php?p=60189650&postcount=1806
Is it necessary to format ext4, then switch to f2fs? I doubt it. Is it better? I have no idea, but that's what I did
Yes, the b6 is the latest version of ZOMBi-POP. Flash it
Click to expand...
Click to collapse
I agree, wiping -I assume the format "checks the disc" is not a bad idea. What I'm a little confused about is that everything I've read - including your thread (which started this whole thing - see what you did?) - states it's a 90 minute or so process. When I change the data partition to f2fs, it's a coupla seconds, and when I format it (which defaults to ext4) it only took 30 minutes or so for the 32 gig.
AND I don't see anywhere where I can "check" the disc for stats and condition, so I'd know what it was/is before I install - unless of course it's staring me in the face - I have problems with things that stare at me.
RBraverman said:
I agree, wiping -I assume the format "checks the disc" is not a bad idea. What I'm a little confused about is that everything I've read - including your thread (which started this whole thing - see what you did?) - states it's a 90 minute or so process. When I change the data partition to f2fs, it's a coupla seconds, and when I format it (which defaults to ext4) it only took 30 minutes or so for the 32 gig.
AND I don't see anywhere where I can "check" the disc for stats and condition, so I'd know what it was/is before I install - unless of course it's staring me in the face - I have problems with things that stare at me.
Click to expand...
Click to collapse
I - and others - say 90 minutes so that people leave it alone, I guess. A few months back, when TWRP first implemented the secure erase, we had lots of people who thought the tablet was stuck and they interrupted the format which led to lots of "help - can't mount anything" posts...
90 minutes is on the extreme outside, but better safe than sorry....
berndblb said:
I - and others - say 90 minutes so that people leave it alone, I guess. A few months back, when TWRP first implemented the secure erase, we had lots of people who thought the tablet was stuck and they interrupted the format which led to lots of "help - can't mount anything" posts...
90 minutes is on the extreme outside, but better safe than sorry....
Click to expand...
Click to collapse
Understood. Been a week of amazement . . . . . . .
It was a WHOLE lot faster when first installed, but slowed a bit now BUT still now actually useable.
MANY MANY thanks for "walking" me through this - I've been in IT since large building, that were VERY cold, but now-a-days need to bounce stuff off someone to know I'm thinking correctly.
I've a coupla questions about the setup, but I'll run them through in the correct thread.