Related
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.
I recently bought a Nexus S and the phone was already rooted. The phone went crazy and all these errors come up saying all the applications cannot be launched. I am not able to access anything on the phone. Every time I go to Fastboot Mode and try Recovery it just reboots to Fastboot mode.
HW Version- REV 11
Bootloader Version- I9020xx.jk1
Bootloader Build- Nov 4 2010
Baseband - I9020xxjk8
Lock State Unlocked
Android 2.3.4 I do not know what ROM is on it.
Is there any way I can get my phone back to stock?
Thanks in Advanced any links or help would be appreciated. I really need to have a working phone again.
I would check out various threads to guide you through it.
Here's one on returning to stock (by Peter Alfonso -- developer)
http://rootzwiki.com/topic/9995-images-100-stock-fastboot-images-can-be-used-to-unbrickunroot/
I'd also just do some youtube searches, as vids walking you through the process always help if you're new to it all. Most of the guides, however well written, assume the user has some previous knowledge. That's where vid walkthroughs are especially helpful. Good luck there!
EDIT: If the phone boots, you might first try dowloading ROM Manager from the android market. In there, try to flash the latest recovery (an option on the main screen).
Also, you can try just going into settings, .. blanking on the option right now.. but theres a place that gives you the option to 'factory reset' the device
I cannot access the ROM Manager or the Settings. Every time I let it boot up all the way it asks me to force close constantly.
BUMP
I still have no access to the actual phone. I only have access to fastboot. Recovery just takes me back to fastboot. Is there anything I can do?
Is it spamming or am I allowed to do Bumps?
anyway BUMP
zkrizzle said:
Is it spamming or am I allowed to do Bumps?
anyway BUMP
Click to expand...
Click to collapse
its spamming.
you have to flash a recovery via fastboot, wipe data, then flash a rom. you can access usb storage via a custom recovery, to put a rom(and gapps) into your usb storage.
simms22 said:
its spamming.
you have to flash a recovery via fastboot, wipe data, then flash a rom. you can access usb storage via a custom recovery, to put a rom(and gapps) into your usb storage.
Click to expand...
Click to collapse
Oh my bad!
and how exactly do you do that? Ive looked all over for tutorials and youtube videos and I followed all of them but I am still in the position I was yesterday. But thanks for the reply I appreciate it.
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.
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
Okay! (bit of a noob here but I really want help T_T)
I'm on 4.2.1 by the way - build number should be latest available.
So I finally decided to get root on my tablet. I followed the instructions by a youtube user, and succeeded. I downloaded SuperUser and a root checker to make sure everything went right, and proceeded to download PacMan 4.2 Milestone, as well as CyanogenMod 10
I did a factory reset from the settings menu of the tablet, and tried to set up PacMan. It worked alright until the loading screen, where the ghost would bounce indefinitely. When it was clear I wasn't going to get in, I restarted, and factory reset again from the TWRP menu, this time making sure to erase Dalvik, cache, and system (I think that's all?).
I then tried to install CM10, which didn't work either. I found out later it was because CM 10 didn't work with the 4.2 bootloader.
So I factory reset again, erased dalvik, system, and cache, and proceeded to reboot into the recovery I made on external. I don't know if it's normal, but when it reached the step 'restoring data,' it was basically stuck. I let it continue overnight, and found that recovery overall took 1933 seconds (is this a sign of something bad?)
And now I'm back to booting! It's taking a really long time though - at least ~45 minutes on the ASUS screen with the little circle going around.
I guess my question is, (1) what do I do, (2) what is the situation I'm in/how did I get here, (3) how do I avoid it (if possible) in the future?
by the way, I forgot to mention that I can still access the twrp menu. I don't know if that helps though?
Hope this helps!
hobomobile said:
Okay! (bit of a noob here but I really want help T_T)
I'm on 4.2.1 by the way - build number should be latest available.
So I finally decided to get root on my tablet. I followed the instructions by a youtube user, and succeeded. I downloaded SuperUser and a root checker to make sure everything went right, and proceeded to download PacMan 4.2 Milestone, as well as CyanogenMod 10
I did a factory reset from the settings menu of the tablet, and tried to set up PacMan. It worked alright until the loading screen, where the ghost would bounce indefinitely. When it was clear I wasn't going to get in, I restarted, and factory reset again from the TWRP menu, this time making sure to erase Dalvik, cache, and system (I think that's all?).
I then tried to install CM10, which didn't work either. I found out later it was because CM 10 didn't work with the 4.2 bootloader.
So I factory reset again, erased dalvik, system, and cache, and proceeded to reboot into the recovery I made on external. I don't know if it's normal, but when it reached the step 'restoring data,' it was basically stuck. I let it continue overnight, and found that recovery overall took 1933 seconds (is this a sign of something bad?)
And now I'm back to booting! It's taking a really long time though - at least ~45 minutes on the ASUS screen with the little circle going around.
I guess my question is, (1) what do I do, (2) what is the situation I'm in/how did I get here, (3) how do I avoid it (if possible) in the future?
Click to expand...
Click to collapse
hobomobile said:
by the way, I forgot to mention that I can still access the twrp menu. I don't know if that helps though?
Click to expand...
Click to collapse
1. Assuming you know how to do this, try flashing the ASUS stock rom and kernel using TWRP. Before asking more questions, use the search tool in XDA developers first since it is most likely someone may of been in a similar situation to yours.
2. It is probably that the person who you followed on youtube might of been be using a different build of stock. That's just my hypothesis-others may differ to mine. Since you have TWRP, you will be able to recover from this situation. (Pun not intended)
3. You should always research about what you're doing with your android device before you do anything about it, especially if the guide is not moderated by the wonderful people from XDA-Developers, and even more so if you are a noob-even if you consider yourself a novice (like me)
To save you some time:
http://forum.xda-developers.com/showthread.php?t=1697227 The mother of guides, read this first.
http://forum.xda-developers.com/showthread.php?p=42407269 [TOOL]Minimal ADB and Fastboot
http://forum.xda-developers.com/showthread.php?t=2257421 Ask any question here-Noob friendly help thread.
Will update this post with more information if need be. Don't be afraid to ask if you're absolutely confused.
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Thanks a lot! I'll do my best trying to find the info - sorry if I have to bother you again though!
Okay, so I have minimal ADB (I actually used that to get root in the first place), and I downloaded the latest kernel and firmware - I'm pretty sure they're the right versions too (10.6.1.27).
Do I just open TWRP, factory reset, clear dalvik and cache, and install both of the above from an SD card? I did some looking around, but I still don't get what a kernel does, or if it's necessary in this situation.
I'm looking at this right now, by the way (http://forum.xda-developers.com/showthread.php?t=2187982), method three.
Okay, so I downloaded this: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU (Android 4.2) - 2013.07.29 update, unzipped the file, went back into twrp, and wiped system, data, and dalvik. When I tried to install it though, it says 'failed.'
What now?
Potential Solution?
Quote:
hobomobile said:
Okay, so I downloaded this: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU (Android 4.2) - 2013.07.29 update, unzipped the file, went back into twrp, and wiped system, data, and dalvik. When I tried to install it though, it says 'failed.'
What now?
Click to expand...
Click to collapse
hobomobile said:
Okay, so I have minimal ADB (I actually used that to get root in the first place), and I downloaded the latest kernel and firmware - I'm pretty sure they're the right versions too (10.6.1.27).
Do I just open TWRP, factory reset, clear dalvik and cache, and install both of the above from an SD card? I did some looking around, but I still don't get what a kernel does, or if it's necessary in this situation.
I'm looking at this right now, by the way (http://forum.xda-developers.com/showthread.php?t=2187982), method three.
Click to expand...
Click to collapse
Define Kernel:
Google:
Define Kernel:
ker·nel
/ˈkərnl/
Noun
A softer, usually edible part of a nut, seed, or fruit stone contained within its hard shell.
The seed and hard husk of a cereal, esp. wheat.
Synonyms
core - nucleus - pith - grain - heart - seed - essence
So that was useless. :silly:
XDA:
Define Kernel-and ROM, and everything:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel "ROM vs Kernel"
If I was you, I would just flash a custom ROM. From here: http://forum.xda-developers.com/showthread.php?t=1697227
There are plenty of ROMs linked there. Even if you want to use one based on the Stock ROM, you can find the links there.
Flash it in TWRP the same way you flashed the "ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU".
Personally, I prefer custom roms because they provide a lot of customisation options.
Is that what your looking for, or do you really want to use the stock ROM?
Remember to at least have a look at the ROMs before dismissing them.
The kernel needs to be the same type as the ROM. e.g, A stock (based) rom will need a stock (based) kernel. AKOP/ASOP ROMS need ASOP/AKOP Kernels. You get the point. See the link mentioned for more information.
Check the compatibility of the ROM with your bootloader before you flash it to not get into situations like this again. (From when you said that CM10 failed to work with your boot loader.
Hope this helped.
BTW, this did not bother me one bit. Your Welcome!
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
If you are running "10.6.1.27" that might be the issue some roms don't boot if you can access fast boot try downgrading to 10.6.1.15.3
Sent from my HTC Desire C using xda app-developers app
1337 H4X0R said:
XDA:
Define Kernel-and ROM, and everything:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel "ROM vs Kernel"
The kernel needs to be the same type as the ROM. e.g, A stock (based) rom will need a stock (based) kernel. AKOP/ASOP ROMS need ASOP/AKOP Kernels. You get the point. See the link mentioned for more information.
Check the compatibility of the ROM with your bootloader before you flash it to not get into situations like this again. (From when you said that CM10 failed to work with your boot loader.
Click to expand...
Click to collapse
Just to add a *tiny* little tidbit right here: every rom has a kernel. It wouldn't boot without one. Yes, a dev can remove the kernel and force you to find one to flash, but that's utterly pointless. I'm just saying that you really don't have to bother yourself with that as yet.
While it's great to educate yourself, don't get overwhelmed. You have PLENTY time to learn more.
I ran into similar issues. You need to make sure your ROM/kernal matches your bootloader and matches your recovery. If not all three match, you run into this issue.
Sent from my EVO using XDA Premium 4 mobile app
so far no good :/
I gave up on this for a couple days, figuring I'd come back to it later when I wasn't as distressed.
so right now, my goal is to get back to stock, and get everything working again before downgrading to 10.6.1.15.3, and then install a custom ROM
Not sure why, but right now, I can't even install the stock kernel flashed onto the device - twrp still tells me 'failed.'
I'm sure that I got the right stock kernel/rom for my build number, so what is going on?