Database Info

[GUIDE]How to load CM9 on GSIII

**this was a very early guide and most of the files and methods referenced in it are long outdated, sounds crazy I know as the phone has barely been out, but i recommend finding more recent guides at this point. I wanted to leave this up for archival reasons though. As of 7-22 I am running dhackers CM10 build with great results. Just don't forget to set max cpu clock back down to 1500 mhz if you don't want it over locked out of the box **
As per the usual disclaimer....at your own risk, be aware of IMEI loss issues and whatnot...basically cover your own butt.....and enjoy.....
7-15 2:46pm **As of right now voice and SMS are not working on my phone while other people report they are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
7-29 this guide is very old, it pre-dates kexec and is only here for historical purposes
For clarification: The question was asked if one is supposed to follow the original Team Epic Kexec kernel instructions or these steps and the answer is two fold. If your goal is to install the UNOFFICIAL CM9 built by Invisiblek (which is the purpose of this thread), then you follow the steps in THIS THREAD ONLY. There are a couple steps and a couple files linked to in the original Kexec page that will not allow you to install CM9. That page was made for those wanting to try out their Kexec Proof of Concept KERNEL, not install a ROM of any kind.
This thread makes some assumptions, such as you already have a working install of the Android SDK and ADB, you already have the drivers installed, you are using the original USB cable that came with your phone, you know how to move around DOS to get to the directory where you downloaded the files, etc.......those lower level tasks are for another thread.
To Try Our Proof-of-Concept Kernel <<<The base of these instructions was the Team Epic Kexec Kernel page seen at this link, Many Thanks to them
Thanks to Invisiblek for clarifying and helping me get steps just right.
The following is an adaptation of the CM Kexec kernel proof of concept with the changes in files and steps necessary to load the latest CM9 work in progress. Be advised I take no credit at all. This is the work of Team Epic and Invisiblek. I just put this together for myself and for others who would like to try it with one caveat. DATA doesn't work! Voice and SMS only....and maybe 1xRtt data.....so you will be relying on WiFi for data! You've been warned!
Also, I highly suggest you use a free MD5 Hash checking utility to verify the integrity of the files you are downloading. That is why the MD5 hash is provided, so you can be sure you didn't get the wrong file or a corrupt download that could cause a BRICK!
If you don't follow the directions carefully you can end up with a brick! Ask questions after reading the OP if you still aren't sure. I probably won't know the right answer for sure. You may have to wait on someone with more experience in this to answer your question.
DO NOT ACCEPT AN OTA UPDATE WHILE RUNNING THIS SETUP
1. Download the recovery.img (MD5: f1c01ad20e02751a73188f173eb412ca), which combines our source-based kernel with our previously released CWM v4.
2. Flash the recovery.img following these instructions, that is:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 bs=256k
sync
3. Reboot into recovery (using volume up, home power buttons), wipe data, install one of invisibleks CM9 roms>click here for all of his CM9 roms< which do not have boot.img integrated, then continue with the steps below:
4. Download these additional files:
(required download)boot.img (MD5: db058f4b15df0fa1b9ee04a5c17cf103), which is invisibleks custom boot.img
It would be good at this point to read ahead and determine where you will be loading the next file. Keep in mind if you are in stock recovery and choose to wipe data, this will wipe the internal memory.
if you plan to load onto internal memory download this file boot_emmc_boot_img.zip (MD5: 84a3f98c194f6dedc583dbc75ccc34c2)
or
if you plan to load onto sdcard (ext) memory download this file boot_sdcard_boot_img.zip (MD5: 88904d7e69d455ff88756b4d1ad79aac), which are applied in recovery to kexec (boot) the custom boot.img.
5. Place boot.img either on the internal SD card (the /sdcard/ folder), or on the external SD card (the /mnt/extSdCard/ folder).
The boot.img kernel boots directly out of one of these folders, it will not (and should not) be flashed to the device.
6. If you're using the internal SD card, place boot_emmc_boot_img.zip in /sdcard/ as well. If you're using the external SD card, place boot_sdcard_boot_img.zip in /mnt/extSdCard/.
7. Reboot into recovery.
8. If using the internal SD card, select "Install zip from sd card" and then "choose zip from internal sdcard", then "boot_emmc_boot_img.zip". Alternatively, if using the external SD card, select "choose zip from sdcard", then "boot_sdcard_boot_img.zip".
At this point, the device should reboot "in the middle" of applying the update, temporarily booting boot.img. If the update "completes" and returns to the CWM menu, kexec has failed or the wrong recovery was loaded in the beginning. Please check the locations of boot.img, and boot_emmc_boot_img.zip or boot_sdcard_boot_img.zip and verify recovery.img file used was the correct one, verify using an MD5 hash checker.
9. Once booted, the custom kernel can be confirmed by checking "Kernel version" in "Settings", "About device". It should report:
3.0.8-gdefeb6f
[email protected] #1
SMP PREEMPT Sun Jul 8 04:27:58 EDT
2012
10. To reboot into the stock kernel, select "Restart" from the Power menu, which will actually reboot into CWM recovery. Press the Power button to select "reboot system now" and leave recovery.
11. You cannot simply power on your phone with this setup! In order to power on your phone you will have to hold volume up, home and power to boot into recovery and load the zip file you chose at step 4 where you chose either internal or external memory, so either "boot_emmc_boot_img.zip" or "boot_sdcard_boot_img.zip". If you do accidentally boot up by just hitting power, no big deal, it will give you all sorts of force closes, simply pull battery and boot back up using the Vol up, Home, power method.
If anyone would like to suggest further clarification, please do. To get the stock Google apps such as Play Store get the package HERE and install in recovery
Alternatively a more condensed version of this install procedure has been posted by nbsdx and can be found HERE.
7-15 2:46pm **As of right now voice and SMS are not working on my phone while others are working fine. While you can still play around and see just how amazingly fast CM is on this phone, YMMV. If it doesn't work you need to know how to go back to stock before trying this.
If you want to return to bone stock, simply go to THIS THREAD to get STOCK ROM IMAGE and then put your phone into Odin Download mode by following THIS THREAD and be sure to flash it using the PDA button. It will take a while, probably 20 minutes or so, it will take forever to boot up the first time but you will be on bone stock like new.

Very informative. Would read again.
Sent from my Transformer Prime TF201

dual boot
Being that we have to use kexec anyhow, it would be nice (especially with the state of current cm9 rom) if we could fully dual boot so as to keep stock system and data for stock kernel.
Like here,
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html

I just installed successfully using the instructions in the OP so I can confirm it works correctly. Holy crap it's fast.

Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium

dakalter said:
Anybody want to put up a video of how well it runs for us that aren't brave enough to put it on our own phones?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'll leave that part to someone who doesn't sound like a retarded redneck on video.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
If you follow the steps in this thread, including using these links for your files, it will work without a problem.
I can't comment on why other guides on other sites using other files don't work.....and not really sure how it applies to this thread. Lets try to keep it on topic. If you have issues with the dual booting instructions, you might start a new thread to address that or jump in irc.freednode.net/verizons3 and graciously ask the people for help
When you flash the the CM9 rom built by Invisiblek it will come back out to CWR menu. At that point in the process I realized I hadn't copied the boot.img file into the root of my sd card, so i left it on the CWR menu, popped out the sdcard, copied the boot.img file over (already had the boot_sdcard_boot.img file on the root of sdcard), and popped the sdcard back in, chose advanced->reboot recovery, then followed the steps in this guide, worked perfectly.

silasrye said:
I tried to install the vzw cm9 (with with invisiblek's boot.img put back into the zip) via this method exactly.
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
fake cwr works, and everything went fine, but when i try to flash boot_cm9.zip i stay in cwr.
I am using the cwr from this post
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
So, I don't see why this shouldn't be a doable thing. But something probably needs to be redirected somewhere.
The good news is, I boot into my normal rom without problem.
Click to expand...
Click to collapse
You need to add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder. Check out the sprint cm9 install for the line to add.
I have tested dual booting to work perfectly.

is the data not working due to the ril??

suzook said:
is the data not working due to the ril??
Click to expand...
Click to collapse
yes, will update OP once we have working 3G/4G data
as of right now my voice and SMS isn't working while others is.....trying to figure it out

I flashed back to stock, simply because I need to have voice and SMS working. I could deal without 3G/4G data for a little bit and use WiFi, but no SMS/Voice was a deal breaker on my phone. I have to be easily gotten in touch with for work and such. It was fun while it lasted.

Will these same instructions work for the CM10 build that is in the server list?

17akota said:
Will these same instructions work for the CM10 build that is in the server list?
Click to expand...
Click to collapse
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium

neyenlives said:
No. Different files used, probably a different step or two also. I plan to edit this once CM10 builds are ready for public consumption. These instructions also don't include the automated kexec scripting work done recently that allows your device to cold boot into CM9.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.

17akota said:
I figured that.
Could you point me in the direction of the new Kexec? I read about it somewhere and would like to try it out.
Click to expand...
Click to collapse
irc.freenode.net #verizons3
Sent from my SCH-I535 using xda premium

i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?

seang said:
i came from a thunderbolt, and know how different a RIL can be from phone to phone, so i ask this quite seriously...
How different is the RIL from the Gnex to the SGIII?
Click to expand...
Click to collapse
Completely different processors.

Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.

17akota said:
Is there anyway to get the TouchWiz Camera on CM9? I really like that camera app.
I tried just putting it in /system/app and changing the permissions to rw-r--r-- and rebooting and nothing
Then i tried just installing it like a normal apk and it failed.
I would love CM9 if i could just get the stock camera app too work.
BTW im using DHacker29's CM9 and its amazing. So much easier to install.
Click to expand...
Click to collapse
It probably requires touchwiz frame work. It will take significantly more work than just dropping in an apk
Sent from my SCH-I535 using xda premium

DHacker's CM10 is awesome!! I've been running it all day and Jelly Bean is really smooth on the S3.
http://www.droidhive.com/forums/index.php?/files/category/26-sgs3/
Check it out guys.

Help an aging PC hacker upgrade his brain and his TF101

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!

[ROM][23-08-2012]NVFlash ICS 9.2.1.27 US/WW/TW Restore[FULLY STOCK!!NOT ROOTED!!]

Hi
Here are the nvflash versions for the .27 update. For those that wanna go back to stock for warrenty or have a dual boot this can come in handy.
I've tested the WW version on my on transformer and it worked (got a B70 with SBK1) created the US and TW version the same way with the same con-fig files so it should work! LET ME KNOW IF IT WORKS FOR YOU
But remember I'm not responsible for any bricks flashing my causes and you do this on your own risk.
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
I'm hosting them on my own website with a 1gbit connection:
http://www.xdafileserver.nl/
a direct link to the folder containing the files: http://goo.gl/OsTbW
PS: these are a bit late i know been very busy! but perhaps somebody can benefit from these! Older versions still are available on the site itself

It's fantastic, thanks man.

Thank's a lot!!!

Hi, Korumera,
I would like to use your NVFLASH to reinstall ww9.2.1.27 on my ASUS TF101, which currently has ww9.2.1.27 with damaged google play store and gmail. Would you please help me with the following questions:
1. Does the nvflash delete the old ROM before flash new ROM.
2. Does it wipe out user app and data?
3. Does it delete files on plug-in sdcard?
Regards

e154037 said:
Hi, Korumera,
I would like to use your NVFLASH to reinstall ww9.2.1.27 on my ASUS TF101, which currently has ww9.2.1.27 with damaged google play store and gmail. Would you please help me with the following questions:
1. Does the nvflash delete the old ROM before flash new ROM.
2. Does it wipe out user app and data?
3. Does it delete files on plug-in sdcard?
Regards
Click to expand...
Click to collapse
NVFlash is one of the lowest-level parts of the firmware. It completely wipes out everything on your internal storage to reset you back to a clean state. (The *external* MicroSD Card shouldn't be wiped, but I would remove it anyway, just to be safe.)

XBIRDIE98 said:
NVFlash is one of the lowest-level parts of the firmware. It completely wipes out everything on your internal storage to reset you back to a clean state. (The *external* MicroSD Card shouldn't be wiped, but I would remove it anyway, just to be safe.)
Click to expand...
Click to collapse
I've nvflashed many times. The MicroSD is safe, it doesn't get touched. As said, everything on internal gets wiped, repartitioned and reformatted.

Anyone have a mirror please? Bricked my TF101 pretty badly (stuck in APX).

How do I get this driver to work in windows 10?
Sent from my SM-T800 using Tapatalk

[GUIDE] From stock GB to Custom JB (Noob-friendly)

STOCK GB ALL THE WAY TO JB CUSTOM ROM
If you run Gingerbread, start from A directly
If you run un-rooted Jellybean, start from B
If you run rooted Jellybean with a custom kernel, start from C.
If you run rooted Jelly Bean without a custom kernel, start from B, but skip number 1 and 6.
You might want to read this before starting, it is optional though, but will give you a better idea of what you're doing.
GUIDE
This guide shall guide you through turning your suckish GB i9070 (not i9070p) to Custom ROM JB Awesomeness.
Unless your phone shipped from Russia, it probably has Gingerbread preinstalled... so, let's first Jellybeanize it.
A) JELLYBEANIZATION:
Download Odin3 from here. http://forum.xda-developers.com/atta...1&d=1341114315. Extract it into a folder.
Download Stock JB firmware from here. http://hotfile.com/dl/222710569/1f2...m-GT-I9070-TSR-I9070XXLQE-1365486223.zip.html . Extract it into a separate folder, you will get a .tar.md5 file.
Make sure you have Kies installed, but not running.
Turn your phone off, and boot into Download mode, this can be done by holding the Vol.Down+Home+Power buttons together at the same time, till it boots.
Press Volume up to continue. Plug in your phone (make sure it's at least 60% charged) . Wait till Odin recognizes (It should say something like COMORT... to the left).
Click on PDA and choose the firmware (.tar.md5) that you extracted in step 2. Click start.
Right now, a virus which will fry your phone's internals is being installed... Calm down, joke.
When your phone boots into JB, and Odin says "PASS". Unplug.
NOTE: There is a chance that you will get a bootloop ( i.e. Android won't boot ). No, no, no... your phone isn't broken! Simply reboot to stock recovery by powering off, then pressing Vol.Up+Home+Power buttons together and wipe data/factory reset. It'll boot nicely
Now, you are currently on a stock Samsung Jellybean firmware, which is not rooted. This basically means that you do not have access to modifying the system files in your ROM, which means that you cannot install any custom kernel, custom recovery or a custom ROM... In section B, you will learn how to gain root access, install a custom kernel with a custom recovery.
B) ROOTING, KERNEL & TWRP/CWM:
Download Shaan's root from here http://d-h.st/ook
Download Temporary cwm from here http://forum.xda-developers.com/show....php?t=1987313
Download CoCore + TWRP (TWRP is one of the two recoveries available, we will use it in this guide because it looks less intimidating, and it's touch-enabled ) from here http://forum.xda-developers.com/atta...8&d=1363518705
Place all 3(or 2 if you're rooted) zip files in your external SD card
Power off. Boot into recovery by holding Vol.Up+Home+Power.
By navigating via volume buttons, choose install zip from external sd card, and install root.zip... shouldn't take long.
In the same way install update.zip. Now in a few seconds, you will get a different screen, this is Clockworkmod recovery, albeit a temporary one..
In this recovery, go to install zip, then install zip from external sd, and choose CoCore+TWRP. After installation, keep going back until the main cwm screen, and hit reboot.
NOW, Everytime you boot into recovery (which is the way to backing up and installing custom ROMs) you will get TWRP.
Now, you are rooted, with a custom kernel, and TWRP ( a custom recovery). You can either stay on stock Samsung firmware, or continue through section C, and get yourself a custom ROM.
C) INSTALLING A CUSTOM ROM:
Download any custom ROM (Recommendations at the end of the thread) zip and place it in the root of your external (or internal, but i prefer ext.) sd.
Boot into recovery.
Navigate by touch, press backup, and slide as instructed to make a backup.
Go back to the main screen and choose install. If the zip has been placed in ext. sd. then press on external sd and choose the appropriate zip and slide to install. If placed in internal sd, then choose internal sd from the top and go to /emmc folder, and choose zip and install.
When finished, navigate to the recovery home, and press reboot sytem.
Frequently Asked Questions
Q- Which of the above will increase my binary counter?
A- None! Let me clarify how the binary counter is tipped. The only way the binary counter can be increased is if you flash anything that is non-official Samsung signed, via Odin.
Q- How do I unroot?
A- You can unroot simply by following the steps in section A and not continuing with the rest of the guide.
Q- I encountered a problem, what now?
A- If the problem is related to this guide and the steps followed in this guide, then post it here, I'll try to help when possible. If you encountered a general problem not related to this guide, please post a thread in the Q&A/Troubleshooting section.
ROM Recommendations
If you want a fully stable ROM, with everything working, Cyanogenmod or Cyanogenmod based ROMs currently do not fit the cirteria, as they some bugs still remain in these. So, you may try one of the stock based ROMs.
[AOSP Themed] - JellyMod - by martin_carpio17 Link here
[S4 Themed] - Light JB - by petraru1 Link here
[AOSP Themed] - Pure Vanilla - by ikaster17 Link here
[Xperia UI Themed] Galaxperia - by Achyut Link here
However, if you'd still like to go for most change, and don't mind the small bugs, then you may try Cyanogenmod or the Cyanogenmod based ROMs below.
Cyanogenmod 10 - by diego-ch and other contributing developers Link here
MIUI v4 - by fedevd Link here
Paranoid Android Port - by nlygamz Link here
Cyanilla - by ikaster17 Link here
This is basically it for this tutorial! Finally eh? But really now, all the above is very very easy once you get used to it, I mean, all the sections in the guide, A, B and C can all be done in 5 minutes, but I've simplified everything as to suite everyone's experience.
Hopefully this guide was useful for you...

If I made any mistakes with this, please correct me

Odp: [GUIDE] From stock GB to Custom JB (Noob-friendly)
That would be very usefull
If only tons of familiar topics wasn't already created ...
tapatalked

rajman said:
That would be very usefull
If only tons of familiar topics wasn't already created ...
tapatalked
Click to expand...
Click to collapse
Excuse me for trying to contribute.

panda00 said:
Excuse me for trying to contribute.
Click to expand...
Click to collapse
You have done a good job. Remember, haters gonna hate
Sent from my GT-I9070 using xda premium

Plus, I provided this for newbies who have little to no idea about rooting and the works...

Odp: [GUIDE] From stock GB to Custom JB (Noob-friendly)
Brainiac.shri said:
You have done a good job. Remember, haters gonna hate
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
Yup, thanks button is to mainstream.
Hating is way more vintage
tapatalked

Added and corrected some things... Thanks R_a_z_v_a_n for the corrections.

Your welcome!

there is anyway to add brazilian portuguese language?

fromanbr said:
there is anyway to add brazilian portuguese language?
Click to expand...
Click to collapse
I don't think so... until a official JB firmware with the language is released.

Up.. since people are still asking how to root and etc.

Up

A million thanks for the guide .. I've installed Jetmod 4.0 and it's running fine. My only concern is that I created a backup of my previous ROM in the internal storage and now just 33MB space is available for installation of apps. Can you please tell me how to 1. Remove the backup, or 2. Move it to the external storage ?
Thanks !

Go to "my files" - internal (sdcard0 I suppose) select what file u want to move an move to external memory (sdcardExt).

R_a_z_v_a_n said:
Go to "my files" - internal (sdcard0 I suppose) select what file u want to move an move to external memory (sdcardExt).
Click to expand...
Click to collapse
I have already tried that, but I am not able to identify the backup. I had used to TWRP to backup and then flash JellyMod. I had looked up on some threads that the backup will be in SD -> TWRP -> Backups (or something similar to this), but there is no such folder in my phone.
:crying:

ttrublu said:
I have already tried that, but I am not able to identify the backup. I had used to TWRP to backup and then flash JellyMod. I had looked up on some threads that the backup will be in SD -> TWRP -> Backups (or something similar to this), but there is no such folder in my phone.
:crying:
Click to expand...
Click to collapse
Look for it using Root Explorer (download the app from the play store).

ttrublu said:
I have already tried that, but I am not able to identify the backup. I had used to TWRP to backup and then flash JellyMod. I had looked up on some threads that the backup will be in SD -> TWRP -> Backups (or something similar to this), but there is no such folder in my phone.
:crying:
Click to expand...
Click to collapse
in your file manager browse to ext_sd. from within ext_sd you should have a folder labeled nandroid..
also, by default, the backups should be labeled/dated accordingly..
you could also get details on each file from within file manager that will give you more specific info. date created, etc..
hope this helps..

Thanks guys, but I think I didn't make myself clear. The backup is present in the 2GB memory reserved for installing apps. How do I access that storage and remove the backup? I'm an android beginner, so pls have patience with me.

ttrublu said:
Thanks guys, but I think I didn't make myself clear. The backup is present in the 2GB memory reserved for installing apps. How do I access that storage and remove the backup? I'm an android beginner, so pls have patience with me.
Click to expand...
Click to collapse
in the "My Files" folder on your phone..
you will see All Files.. select it and youll see extSdCard and sdcard..
go to sdcard to navigate to your back up files after that move them to your memory card extsdcard..
voila.. free space..

[Q] Incredibly slow to start but runs OK after that

Hello all,
I'm a bit of a newbie at this stuff, but I hope this is enough information:
I recently installed CROMBi-KK on my TF700T. I don't think I've done any other relevant "mods" and certainly none after changing the ROM.
The tablet is connected to the optional keyboard.
I think the hard drive is about 2/3 full. Not sure about SD card. (I haven't tried starting system without SD card installed.)
It typically takes 15 minutes to start up!!!!
But once it starts, in part thanks to using Cleaner Master to block automatic startup of many programs, it typically runs fairly well. If it gets laggy, I can use the "phone boost" part of Cleaner Master (or of similar functioning programs) to get it running fairly well again.
Can anyone please offer me advice on what to do in order to get to a reasonable startup time?
Thanks very much for any help!

That sounds as if you did not install CROMBi-KK clean or clean enough. Or you are on the wrong bootloader...
So post your bootloader version and recovery version, which rom you came from and how and what you wiped before installing the rom.
Start backing up all your data off the tablet, 'cause no matter what your answer is, I'm going to recommend you move to ZOMBi-POP anyway. And that takes a full format of data and a change of /data to f2fs.
CROMBi-KK is no longer supported for a good reason: ZOMBi-POP is much better - especially better over time where CROMBi tended to really bog down.
You should not use (and need) CleanMaster on this rom. That app is for stock roms loaded with bloatware.
Post the info I asked for and I can help you to get this tablet flying again
This may be some helpful reading: http://forum.xda-developers.com/showthread.php?t=2688891
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471

Info you request
Thanks for your help...how do I find the bootloader and recovery versions? I don't remember which ROM I came from. I want to say 4.2 but I don't know for sure.
What's the best way to back up data?
Thanks again!
berndblb said:
That sounds as if you did not install CROMBi-KK clean or clean enough. Or you are on the wrong bootloader...
So post your bootloader version and recovery version, which rom you came from and how and what you wiped before installing the rom.
Start backing up all your data off the tablet, 'cause no matter what your answer is, I'm going to recommend you move to ZOMBi-POP anyway. And that takes a full format of data and a change of /data to f2fs.
CROMBi-KK is no longer supported for a good reason: ZOMBi-POP is much better - especially better over time where CROMBi tended to really bog down.
You should not use (and need) CleanMaster on this rom. That app is for stock roms loaded with bloatware.
Post the info I asked for and I can help you to get this tablet flying again
This may be some helpful reading: http://forum.xda-developers.com/showthread.php?t=2688891
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Click to expand...
Click to collapse

Read the threads I linked to.
Bootloader: post 3 under the first link
Recovery: fire it up, read he header
Data: copy it to a microSD or PC
Sent from my TF700T using Tapatalk

Is this the info you asked for?
Sorry, was away for a couple of days...please let me know if this is the information you said I should get to you:
[UPDATE: Did Titanium Backup to SD card]
Bootloader (very tiny and hard to read): "US_epad-10.6.1.14.10-20130801" A03
TWRP 2.8.5.0 (found by using RCP boot option)
briefly on screen at restart, under 4 funny looking little birds:
[ 4.134409] preinit: ######### starting ###########
(and then more stuff, then a few lines of stuff, then)
mmcblk0p8: ext4
mmcblk1p2
mmcblk1p3
ro.cm.version=11.0-20140921-crombi-kk-tf700t
berndblb said:
Read the threads I linked to.
Bootloader: post 3 under the first link
Recovery: fire it up, read he header
Data: copy it to a microSD or PC
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse

You're good to go on the bootloader side. But TWRP 2.8.5 has a bug with the f2fs conversion, so if you want to go for ZOMBi-POP on f2fs you have to update your recovery.
Instructions are all in my f2fs conversion guide (3rd link I posted earlier).
But first make a nandroid of your CROMBi-KK installation - just in case you should not like ZOMBi.
Get the recovery and rom files together on your microSD, then
Flash the Kang TWRP by lj
reboot
format data in TWRP
convert file system on /data to f2fs
flash ZOMBi-POP
enjoy
Sent from my K00C using Tapatalk

So since I don't know what nandroid means and don't want to figure it out, I'm going to take your word for it that ZOMBi is better than CROMBi!
I'll work through this with your instructions and let you know how it goes.
Thanks very much!
berndblb said:
You're good to go on the bootloader side. But TWRP 2.8.5 has a bug with the f2fs conversion, so if you want to go for ZOMBi-POP on f2fs you have to update your recovery.
Instructions are all in my f2fs conversion guide (3rd link I posted earlier).
But first make a nandroid of your CROMBi-KK installation - just in case you should not like ZOMBi.
Get the recovery and rom files together on your microSD, then
Flash the Kang TWRP by lj
reboot
format data in TWRP
convert file system on /data to f2fs
flash ZOMBi-POP
enjoy
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse

Rossputin said:
So since I don't know what nandroid means and don't want to figure it out, I'm going to take your word for it that ZOMBi is better than CROMBi!
I'll work through this with your instructions and let you know how it goes.
Thanks very much!
Click to expand...
Click to collapse
A nandroid is a full system backup. In TWRP touch 'Backup", choose your microSD as destination (remember you will totally format your internal storage) and swipe the button. That's it.

It worked!
Still figuring out Zombi but it sure does boot up a lot faster.
Thanks so much for your help!
berndblb said:
A nandroid is a full system backup. In TWRP touch 'Backup", choose your microSD as destination (remember you will totally format your internal storage) and swipe the button. That's it.
Click to expand...
Click to collapse