Database Info

[Q] Will this restore a CM7 i9020A back to 100% stock?

Hi,
- This is my first post on XDA forum.
- Before I ask this, I swear I've read 20+ pages on this forum.
- Before I read those 20+ pages, I know absolutely nothing about modding Android Phone.
- I saw some thread asking the same question as me, but I can't find a thread that sum this issue up in a 1 page step-by-step guide.
- I did my best, just need experts like you guys to confirm that I understand it right (before I brick my phone T_T...).
- I believe many people are also looking for answer to this question as well.
--- Situation ---
I bought a White Nexus S (it's i9020A) from ebay. It's modded with CM7. Actually it's not arrived yet. But I'm doing research while waiting for it.
--- My goal ---
Restore everything back to 100% stock. Be it 2.3.3 or 2.3.4 is fine, as long as it's official. (Well if it's 2.3.3 it'll get official OTA to 2.3.4 anyway)
I want the phone to be like it has never been modded at all.
I want to restore everything: the OS, the recovery image, the root access, ...
If I'm still missing something, please let me know.
--- Main Question ---
Does the following steps enough to achieve my goal?
1.Restore the recovery image to stock first. From what I read, the 'stock recovery' will not allow flashing of custom OS. So this will help confirm that the OS we're going to flash is also a 100% stock OS.
1.1 Find the stock recovery image for i9020A(still don't know where to download it)
1.2 "fastboot flash recovery my_finally_found_i9020a_stock_recovery.img"
2. Flash the stock Android 2.3.4 OS for i9020A downloaded from the first page of this thread:
http://forum.xda-developers.com/showthread.php?t=1056062
(the link that says Model: i9020A - GRI54 -> GRJ22: Released)
The flashing tutorial is also in that thread:
How to apply the update:
I will cover stock only, as those running Clockworkmod should already know how to apply an update zip.
Copy the update file appropriate for your model/build/modem to your Internal storage of your phone. Do not place in any sub-directory.
Turn off your phone.
While holding the volume up, press the power to turn on the phone
use the up/down volume to select recovery
press power to make the selection.
Your phone will now reboot into recovery.
When you see the little droid, while holding the power, press the volume up to bring up a menu.
Select "Apply update from /sdcard"
scroll down to the update file you downloaded it, make sure it's highlighted then press power to select
The update should go through
Click to expand...
Click to collapse
Is this all I need to do? Am I 100% stock now? (almost forgot to ask where to find the stock recovery image for i9020A? I can't find it in this forum)
Thank you in advance!

The link for the stock ROM is only update, not a full rom. You need a full rom in size about 80 MB.
In the stock rom there gonna be recovery.img - that is stock recovery. Extract it and flash with fastboot, then do the rest as you described.
Ask free if you need help.

Thank you for the info.
I found the stock rom(around 90mb in size) in this thread:
http://forum.xda-developers.com/showthread.php?t=1033269
but it doesn't contain the recovery.img
however, in page 4 of that thread, there's a stock recovery.img
So let me re-arrange the to-do list again:
1. use fastboot to install the stockrecovery.img
2. use stock recovery to flash the Full stock rom
well this should get me 100% stock, right?
(BTW, I wonder why people keep saying flash stock rom with CWM first, then fastboot recovery.img)
Thanks again!

You would need to do step 2 and then step one. You need Clockwork Recovery to flash the stock zip file and then flash the stock recovery using fastboot, if you do it the other way around the stock recovery won't let you flash the zip....not sure if it would cause any other problems though.
So it's
1. Flash stock zip using Clockwork Recovery
2. Use fastboot to flash stockrecovery.img
3. Then lock the bootloader using fastboot oem lock

hi
you can find all the samsung related stock firmware on samfirmware
please add www and com in the addres. i am not allowed to put the web address.
please check the website
cheers

zuvoke said:
hi
you can find all the samsung related stock firmware on samfirmware
please add www and com in the addres. i am not allowed to put the web address.
please check the website
cheers
Click to expand...
Click to collapse
That is for Odin which is might be more difficult than necessary.
EDIT: OP, have you seen this thread? http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
I'm not sure if the radio is right for you. But maybe you can use it with another radio.

hey I am in the sort of in the same boat as lgmcben. I just purchased a nexus s and its on 2.3.4 rooted already. Not knowing anything about android and wanting learn the whole thing from scratch, i also want to reset my phone to factory setting. Now, not knowing how it was rooted orignially, i am having difficulty following a particular guide because they all at some point end mentioning about how the phone was originally rooted so i get confused whether i should follow that guide. Would i be able to follow same steps suggested by lgmcben. Also, my phone is unlocked for to be used with any carriers. would resetting it to factory setting lock it to the original carrier again? Any help is appreciated.

matt2053 said:
That is for Odin which is might be more difficult than necessary.
EDIT: OP, have you seen this thread? http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
I'm not sure if the radio is right for you. But maybe you can use it with another radio.
Click to expand...
Click to collapse
Hi,
This should work. However, it's still an unofficial/unsigned rom. But it should work. Thank you. =)

forpulse said:
hey I am in the sort of in the same boat as lgmcben. I just purchased a nexus s and its on 2.3.4 rooted already. Not knowing anything about android and wanting learn the whole thing from scratch, i also want to reset my phone to factory setting. Now, not knowing how it was rooted orignially, i am having difficulty following a particular guide because they all at some point end mentioning about how the phone was originally rooted so i get confused whether i should follow that guide. Would i be able to follow same steps suggested by lgmcben. Also, my phone is unlocked for to be used with any carriers. would resetting it to factory setting lock it to the original carrier again? Any help is appreciated.
Click to expand...
Click to collapse
May be you can use the rom provided in this thread =)
http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
About the step-by-step guide on how to use the ClockWorkMod, go here:
http://forum.xda-developers.com/showthread.php?t=1007782

lgmcben said:
May be you can use the rom provided in this thread =)
http://forum.xda-developers.com/showthread.php?t=1033269&highlight=stock
About the step-by-step guide on how to use the ClockWorkMod, go here:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
I am kind of not sure if I can use that ROM since its 2.3.3. I am on 2.3.4 at the moment so that would mean downgrading. If thats allowed then great, but i don't know if it is allowed. As for the clockworkmod guide, I am not going to be needing it now since for now I just want a normal factory resetted unrooted phone. Once I get to that stage I will look into that. But thanks for that guide. For now, I just want to unroot. I found this guide here on XDA, which I am not sure if I can use. would you be able to tell.
UNROOTING.........
Get files (can't post the link since i am new user but its 4shared links found in this forum)
-download and extract files, we will be using odin, the 3 tar files.
-extract tar files to desktop along with odin.
-run odin and in the files section select the boxes bootloader, pda, phone.
-click the buttons next to each and direct it to the .tar files we extracted to desktop, so....
click the bootloader box, direct it to sph-d720-bootloader.tar ...then..
click the pda button direct it toward the sph-d720-pda.tar....then..
click the phone button and direct it toward sph-d720-phone.tar....
-now turn off your phone, when off hold volume up and volume down buttons simultaneously, then quickly press the power button....a huge yellow triangle will pop up and say "downloading'.......
plug your phone via usb to computer....odin should automatically see it.....click the start button in odin and let it do its thing and bam...all set.
If you want stock recovery too place the recovery.img in tools folder, open command prompt..type the following command..
fastboot flash recovery recovery.img
Done.

[Q] I think I killed my Nexus S! Please help! (unlocking process/rooting stuff)

So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!

I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.

nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.

OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?

nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!

Edit: nvm. >_<

kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!

nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..

OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?

http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.

skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness

mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?

Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?

skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img

kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!

skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.

nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.

Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.

nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.

[Q] Newbie Confusion About Rooting, Unlocking, Installing Custom Rom

Hello great people of XDA,
I am a newbie to Android and XDA ecosystem. I am trying to summarize my situation below. Sorry if it is too long.
Goal for using tablet: My main purpose for using tablet is having a mobile device I can use both form my studies and my work. I will take notes via smthng like supernote, open word and excel documents and track my mails. All files will be kept in microsd, I just load apps and movies and music to internal storage.
I won’t use my tablet as a gaming machine. Of course I can play some games like chess or small games but not big ones.All I want is performance and smooth usage. A laggy device while surfing or taking notes makes me crazy.
My tablet is a 15 days old tablet but I want to root it, unlock it and install a custom rom. The device is running Android 4.1.1 (JB) with WW…….10.4.4.18_20121012 firmware. Here is my plan.
Phase 0 : Downgrade it
1. Download Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for WW SKU (Android 4.0.3)
2. Unzip it
3. Rename it to EP201_768_SDUPDATE.zip
4. Copy it to microsd card
5. Insert microsd
6. Power off
7. Press power on + volume down
8. See some small lines at left top
9. Press (only) volume up in 5 seconds
10. Hope the machine sees the file in the SD card and downgrade your device
Result : you have a machine with android 4.0.3
Phase 1 : Root it
1. Mark USB Debugging and Unknown sources
2. Load the drivers to computer
3. Connect the device
4. Run the rootdebugfs
5. Follow the instructions
6. Hope to be root
Result : you have a rooted machine with android 4.0.3
Phase 2 : Unlock it
1. Install GooManagerBeta via GooglePlay
2. Run GooManagerBeta
3. Install open recovery script
4. Machine reboots itself
5. Power off
6. Press power on + volume down
7. See some small lines at left top
8. Press (only) volume up in 5 seconds
9. TWRP (I dont know which version is installed via GooManagerBeta) should be opened
10. Backup your data to your external sd card if necessary
11. Wipe all data/cache
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty
Phase 3 : Install custom rom
1. Copy custom rom and gapps file to microSD
2. While TWRP is infron of us, choose install
3. Find your custom rom files
4. Flash to install
5. Find your gapps files
6. Flash to install
7. Hope to boot again
8. Hope to get enough performance
Result : you have a rooted/unlocked machine with custom rom with no warranty
Here are my questions
1. Is my flow correct?
2. Where is the real risk for hard or soft bricking? (I have no idea what is the difference)
3. I have not decided yet what to choose clearrom 2.3 or CM10? All I want is performance and smoothness
4. Does it worth to make all these things? Will I get a real performance and smoothness boost?
Thanks for your help…

Almost correct. Your phase 2 is missing the actual action of unlocking the tablet. What you're doing in the second phase, is actually installing a custom recovery. Before you can do that, you need to be unlocked.
You need to download the unlocking utility from Asus' website to unlock it. You can do this just before you start phase 2. Besides that, it's almost exactly what I did.

In my point of view you could forget about Phase 0
The things that you want to do are possible on JB

jokapo said:
In my point of view you could forget about Phase 0
The things that you want to do are possible on JB
Click to expand...
Click to collapse
I'm worried about this too. I'm about to unlock, but my tab is currently on 4.1. Are you saying that the unlock tool from ASUS will still work with android 4.1?

People have reported it working, yes.

rikkoko said:
I'm worried about this too. I'm about to unlock, but my tab is currently on 4.1. Are you saying that the unlock tool from ASUS will still work with android 4.1?
Click to expand...
Click to collapse
Firebrazer said:
People have reported it working, yes.
Click to expand...
Click to collapse
It works without any problem.
I also unlocked when on JB

ingenihero said:
3.I have not decided yet what to choose clearrom 2.3 or CM10? All I want is performance and smoothness
Click to expand...
Click to collapse
I would highly recommend CleanROM 2.3 - it's the fastest, smoothest ROM that I have ever used on the TF700 (and I've tried them all!). Plus, the developer is simply amazing in terms of support, etc. Being that it is a stock-based ROM, you will get to keep some very useful stuff, such as the keyboard dock battery level on the status bar and some useful apps that are only available in stock-based ROM's.
Then again,once you are unlocked, it's very easy to install different ROMs and try them for yourself - that's half of the fun of unlocking - getting to try different ROMs!
Good luck and have fun!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
I would highly recommend CleanROM 2.3 - it's the fastest, smoothest ROM that I have ever used on the TF700 (and I've tried them all!). Plus, the developer is simply amazing in terms of support, etc. Being that it is a stock-based ROM, you will get to keep some very useful stuff, such as the keyboard dock battery level on the status bar and some useful apps that are only available in stock-based ROM's.
Then again,once you are unlocked, it's very easy to install different ROMs and try them for yourself - that's half of the fun of unlocking - getting to try different ROMs!
Good luck and have fun!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
How can I be sure that GooManager is using TWRP not CWM? As I heard CMW is problematic with managers.

Once you open GooManager and press the "Install OpenRecoveryScript" button, it will tell you which recovery it will install, before it starts downloading and installing it. It is always TWRP.

jtrosky said:
I would highly recommend CleanROM 2.3 - it's the fastest, smoothest ROM that I have ever used on the TF700 (and I've tried them all!). Plus, the developer is simply amazing in terms of support, etc. Being that it is a stock-based ROM, you will get to keep some very useful stuff, such as the keyboard dock battery level on the status bar and some useful apps that are only available in stock-based ROM's.
Then again,once you are unlocked, it's very easy to install different ROMs and try them for yourself - that's half of the fun of unlocking - getting to try different ROMs!
Good luck and have fun!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
AMEN to that
ingenihero said:
How can I be sure that GooManager is using TWRP not CWM? As I heard CMW is problematic with managers.
Click to expand...
Click to collapse
I have used both TWRP and CWM and never had any problems with both.
I just like the simplicity of CWM though.
Maybe because thats the one that i encountered using first when i stepped into the wonderful world called ANDROID

Looking for better understanding
I too could use a better understanding of this. I am about 70% happy with my TF700. About 70% of the time it is fast enough and smooth enough. The other 30 it kind of crawls. This is especially noticeable when trying to navigate Netflix.
What exactly is CleanROM replacing? Do you get to keep all the built in apps? What about upgrading as new versions of Android are released or minor updates come out?
Is there a CleanROM info page or guide that explains it all?
Thanks for the information.
Scott

The CleanROM thread can be found in the Development part of the TF700T forum. It explains a lot of it.
You have the option of installing all the stock Asus apps, none of them, or whichever ones you want.
You can always go back to stock, should you wish it, but once you're unlocked you won't receive OTA updates anymore, you'll have to install them manually. The developer will most likely update the ROM as new versions of the stock becomes available, assuming it's a stock-based ROM (CleanROM is stock-based).

Firebrazer said:
The CleanROM thread can be found in the Development part of the TF700T forum. It explains a lot of it.
You have the option of installing all the stock Asus apps, none of them, or whichever ones you want.
You can always go back to stock, should you wish it, but once you're unlocked you won't receive OTA updates anymore, you'll have to install them manually. The developer will most likely update the ROM as new versions of the stock becomes available, assuming it's a stock-based ROM (CleanROM is stock-based).
Click to expand...
Click to collapse
Hi again,
I downgraded to 4.0.3 ICS but rooting tool is working for 20 minutes is that normal? SHould I interrupt the process?

It shouldn't take that long. Have you followed the on-screen instructions? Maybe you forgot to press a key after the tablet rebooted?

Firebrazer said:
It shouldn't take that long. Have you followed the on-screen instructions? Maybe you forgot to press a key after the tablet rebooted?
Click to expand...
Click to collapse
I have succeed to install CleanRom 2.3 at the end. First impression, there is a performance and stability increase but not a dramatic one. I will continue with trying Clemsyn Kernel. If this does not bring expected perfromance, I will try Data2sd Mod.
Here is my actualized flow.
Phase 0 : Downgrade it
1. Download Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for WW SKU (Android 4.0.3)
2. Unzip it
3. Format micro SD to FAT32 format (not a quick format) if it is not FAT32 already
4. Copy needed downgrade firmware to microSD without renaming
5. Insert micro SD to tablet
6. Tablet recognizes the downgrade update and ask for continue
7. Continue with the process
8. Tablet reboots
9. Tablet downgrades its OS to 4.0.3
Result : you have a machine with android 4.0.3
Phase 1 : Root it
1. Mark USB Debugging and Unknown sources
2. Load the drivers to computer
3. Connect the device
4. Run the rootdebugfs
5. Follow the instructions
6. It takes too much time to complete the action, but after 20 minutes or a little more I kill the process via CTRL+C and process interestingly continued and rooted my device.
Result : you have a rooted machine with android 4.0.3
Phase 2 : Unlock it
1. Install Asus Offical Unlocker
2. Follow the instructions
3. You have easily unlocked your device.
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty
Phase 3 : Install Custom Recovery
1. Install GooManager via GooglePlay
2. Run GooManager
3. Give root permisson
4. Install open recovery script
5. Machine reboots itself
6. Power off
7. Press power on + volume down
8. See some small lines at left top
9. Press (only) volume up in 5 seconds
10. TWRP (I dont know which version is installed via GooManagerBeta) should be opened
11. Backup your data to your external sd card if necessary
12. Wipe all data/cache (In TWRP Factory Reset Under Wipe Menu)
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty and custom recovery installed
Phase 4 : Install custom rom
1. Copy custom rom and gapps file to microSD
2. While TWRP is infron of us, choose install
3. Find your custom rom files
4. Flash to install
5. Find your gapps files
6. Flash to install
7. Hope to boot again
Result : you have a rooted/unlocked machine with android 4.0.3 with no warranty and custom recovery / custom rom installed
That worked for me.

I think actualized is a very groovy word!
May I use it from here forward?

Thats OK said:
I think actualized is a very groovy word!
May I use it from here forward?
Click to expand...
Click to collapse
Sure you can
P.s. : I am not very good at english.

ingenihero said:
Sure you can
P.s. : I am not very good at english.
Click to expand...
Click to collapse
I think you are very good at english!

Make sure to cold boot a couple of times after installing CleanROM. That usually helps a bit. Also, try Browser2Ram.

I thank the OP for this thread as I was also having some questions, even though I don't consider myself an actual newbie. I think this thread will help a lot of people out with an outline process of what to do with the TF700 regarding the root to flashing custom ROM process. I am still left with a few questions that I'm hoping can be answered. [btw, my TF700 is totally stock, no root, locked, on the latest OTA JB release, US version]
1) for the OP, what made you decide to proceed with your Phase 0, rather than going straight to Phase 1?
2) If a person only wanted to root their device, could the simply follow the Phase 1 listed here only? Is there a need to unlock the bootloader if you want to just be Rooted?
3) Does anyone think that there will be a way to go from Rooting to Installing a Custom Recovery, without unlocking the boot loader (similar to the TF101 process)?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

[Q] Rooting, Flashing, Upgrade services needed!

I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....

Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.

Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?

dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.

junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.

dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....

I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.

dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:

If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app

Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!

did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.

what step are you up to?

Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......

i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.

OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!

here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?

Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?

What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?

Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....

Great let us know what happens. I will be around for a while.

Full on Noob, need help if possible.

Okay so, I love my Infuse but getting really tired of not being able to download anything off the play store. Just tired of it's rather less than great performance right now as well. It's is running 2.3.6 GB and want to get this thing up to ICS if possible. Just something running 4.0 so I can use my phone for what I need too. It is not rooted, no cyanogenMod, NOTHING. As the title says, I'm a full on noob here and I apologize if all this is covered in other threads, however I have just gotten to the point where I have found myself even more lost than where I started on what I needed to do/get. If someone can, I will literally need this spelled out to me (no pun intended), in order of the steps I need to take with everything. I'm getting tired of confusing myself even more from all the different stuff I have seen all over the place and I know without some serious guidance, I will just brick my phone. Thanks for any help! :laugh:

I understand this community can be a bit unorganized and confusing so I'll give you my process for rooting and installing custom firmware (there are other ways, but this works for my AT&T Infuse 4G SGH-i997).
First of all, no one uses ICS on the Infuse. There is a ROM, but it's underdeveloped because JB came out so quick. You will need to flash it to get to higher operating systems, but it is by no means a daily driver. Even JB is a little buggy compared to KitKat on the Infuse these days.
The first thing you want to do is root your phone and get a custom recovery.
There are more than a few options for rooting, but I prefer using ODIN (as I understand it, this is the tool Samsung uses to restore soft bricked phones). So this is a good thing to know how to do, in case you ever do soft brick your phone, you'll know exactly what to do.
Read the ODIN instructions in full as I will only briefly explain.
You're going to have to install Samsung drivers.
You'll be using UCLB3_Unbrick_root_1.1.zip. If you used UCLB3_Unbrick_1.1.zip it would just get you back to stock GB with no root added.
To put your phone into download mode, first turn off your phone. Plug a usb cable into your computer. Then with the phone off, hold down both volume buttons and plug the usb cable into your phone. A warning will come up and you push volume up to accept, realizing that you can easily soft brick your phone if you loose power or unplug during a download.
Once downloading is done, the phone will reboot and you'll be disappointed to see that nothing has changed. Except one small thing, you are now rooted and you should have an application called SuperUser that will allow you to do nifty and also dangerous things.
Now follow this step in the ODIN instructions to add the custom recovery (CWM = Clock Work Mod):
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
Click to expand...
Click to collapse
If you follow the link in the second "HERE," you'll get the kernel I prefer since it was most recently updated. Scroll down the downloads section and grab "2013.04.30-CWM-Synthesis-1.2Ghz.zip." (1.2Ghz is stock for our processor, anything higher will be overclocked which I don't recommend).
Extract that and grab the zImage file in the update folder. You're going to copy this to your phone in a second.
But first you need SGS Kernal Flasher, you can get it off the playstore, but I despise having to log in to an OS I'm going to write over in less than a minute so I download the APK from here. Hopefully you know how to install APKs from your SD card and that you'll have to check install from unknown sources.
Now flash the zImage using SGS Kernel Flasher. Your phone will reboot and hang on the Samsung logo and a creepy voice is going to tell you about how she's partitioning your phone and installing Voodoo lag fix. This is normal. Eventually your phone will reboot back into GB and you'll be ready to flash any ROM of your choice by rebooting into recovery.
You reboot into recovery by holding the volume up and volume down button while powering on the phone. This is different than download mode and will take you do a new screen that you control with the volume keys.
You'll be using this to put new software on your phone.
Now you can bassically follow the instructions for getting to CyanogenMod 11 (Kit Kat) from GB.
The first bullet is what I just explained in detail.
Note that I didn't include the links in these instructions, just follow the link above to get to the original post.
Obtain CWM, this can be done using Jscotts Odin back to stock (Follow instructions and use SGS kernal flasher to obtain CWM)
Run Qksters IMEI backup script here
Make certain you are on ICS, this can be done by flashing Entropy's CM9
It is recommended now that you remove your SD Card
CWM: Wipe Cache / Factory Reset
Install ROM: Scroll down for downloads sectoion
... The package will start to install..
... Phone will reboot into the install screen again...
... Continue to install [Automatically] If not manually flash again
... Phone will reboot again and be at the recovery screen...
Install Gapps: Here - Working swipe!
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
To be clear, when you flash a ROM, it won't be like flashing the zImage (that was just to get custom recovery). To flash the CM9 ROM or Qksters IMEI backup script for example, you leave the rom in the .zip file and simply put it on your SD card. Once in the recovery screen, you select "Install Update from ZIP" and navigate to the particular ROM you wish to install.
Also after updating to a higher version of Android, your phone will sometimes hang on the install screen for a long time. If it does for more than five minutes, it's safe to pull the battery and try flashing again (and sometimes necessary).
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Lately I've been using CyanFox and I have to say, it's the most stable ROM I've used in a while.
If you have any questions about this, feel free to ask.
Best of luck and happy flashing,
~bokonon9

Thank you muchness!
Thank you very much for helping me in this mess! I greatly appreciate it. I love my Infuse and do not want to get rid of it quite yet so hopefully this will help! Once I get a new usb cord I will get on this. My toddler decided to get a hold of it and it has to set a certain way now and can't be moved. This, is no bueno! Anyways, THANKS AGAIN!!! :laugh:

Goodluck! :laugh: :good:

I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
After flashing Entropy's CM9, you will be on ICS, you can use if you want but I don't advise it. You should continue with the instructions and update to KitKat after getting to ICS. I recommend Scott's CM11 (what I linked you to) or Scott's BeanStalk (find it in the Android Development Section).
Click to expand...
Click to collapse
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!

wwr said:
I'm new in the android world and I'm using a nexus 7 and an infuse to make experiments just to learn.
bokonon9, thank you! You're guide has been precious to me.
Unfortunately I only succeeded installing ICS, infact I get till here:
I tried to install CM11 and even CM10 at least half a dozen times each, following step by step the instructions that I've found on the thread but all the times I have the same issue:
after the zip rom update and the reboot, the bootloader keeps launching the CWM recovery. I see the logo, the progress bar and then I land in recovery
I don't get any kind of error (and I don't know where to look for to get more information than what's shown on the screen) and I'm just stuck in the recovery and I have to start from scratch every time using Odin all the way down.
I'm not interested in Gapps so, at the beginning I tried without installing them but then I tried also using the appropriate gapps as indicated in the procedure. Either way I didn't get any solution to my problem.
Do you have an idea? Is there a way for me to provide more information or debug?
Thank you!
Click to expand...
Click to collapse
i would say go back to stock gb with odin and basically start over but with ics i always let it reboot to get a "feel" for it then i reboot to recovery and wipe basically everything then flash the next level of android which should be cm 10 then i let that boot then repeat that to get to kitkat 4.4.3 CarbonRom....sometimes you have to flash the same rom twice to get it to flash tho

I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall

wwr said:
I already tried all that and I can't figure out a way out ... I'm really banging my head against the wall
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2091900&page=370
read the last post on that page by scmfxt