Related
WELCOME
to the WINDOWS Bell Atrix 0.37.4 update guide on how to go from 2.2.1 to 2.2.2! (without problems )
===================================================================================================================================================
WARNING
Do not attempt any of these steps if you are on an international firmware. You will probably brick your phone. This guide was made to help people who are having trouble updating from 0.37.4 to the new bell 2.2.2.
Bell users:
Please note that flashing files to your phone and modifying system contents can brick your phone. However, the method I am sharing worked flawlessly for myself and others.
Before beginning:
You need root access on your phone. If you are not sure what root access is, you shouldn't be having problems updating, because you wouldn't have modified system files. Regardless, here is a thread on how to root a bell atrix.
Guide:
Step 1:
Download Titanium Backup from android marketplace, and back up all of your apps and games. This is necessary only if you want to have an easy reinstall of most of your apps and games, as we will be wiping data off of the phone. (if you have another backup program, it should work just fine. Make sure it saves the backup to a folder that you can copy onto your computer)
Step 2:
Remove the external microsd card from your phone (if you have one). This is simply for safety purposes, as we don't want any data being wiped off of this (we don't need the microsd any time during the process).
Now, copy (or cut) all of the data from your internal storage to your computer, just in case, and we are about to wipe data off of your phone.
Step 3:
Format your phone. This can be done two different ways.
The first method is the simplest:
Menu -> Settings -> Privacy -> Factory Data Reset.
The second method (if for some reason you can't do the first) is:
Turn off your phone. Turn it back on while holding the volume down key. It will show the word FastBoot. Keep pressing the volume down key until you reach android recovery. Press the volume up key. Wait patiently. Once a little man appears, there should be a menu. If there isn't, press both the bottom left and bottom right corners of the screen simultaneously. That should bring up the menu. (give it a few tries, it takes me 8-10 lol). From this menu, press volume down until you get to wipe data, then press ok on the bottom left corner (give this a few tries too).
Step 4:
Your phone should now be acting like you just bought it. It should, upon reboot, prompt you to enter your country.. etc. Make sure you either use your existing motoblur account, or create a new one. It is just important for you to have a blur account for the update process (my phone gave me hell when I didn't have one). Do what is necessary to get your phone up and running again.
Step 5:
This is where the fun begins. Reroot your phone usinggladroot(or any other root method you know how to use). Download Superuser, install it, then download Root Checker from android marketplace to confirm root access. Whenever a Superuser popup comes up, confirm / say yes (and make sure the remember box is checked).
Once you have confirmed root access, proceed to the next step.
Step 6:
Download Tenfar's CWM recovery, and install the apk on your phone. Follow the instructions inside of the app to install recovery and enable recovery mode.
Step 7:
Download these two files, and put them in the root of your internal storage. (By root, I mean in the very first directory, ie. F:/put file here)
http://dl.dropbox.com/u/23800522/Blur_Version.0.37.4.MB860.BellMobility.en.CA.zip
http://dl.dropbox.com/u/23800522/Blur_Version.0.37.4.MB860.BellMobility.en.CA.crc
Step 8:
We are now ready to start fixing up the phone, and preparing it for the update.
First of all, we need to make sure ADB (the program we will be using on our computer) has root access on our atrix when it is plugged into our computer via usb.
Before plugging in your atrix via usb, enable USB debugging via:
Menu-> Settings-> Applications -> Development -> Check USB Debugging.
Now plug the atrix into your computer, and set the USB connection to: None. Check to make sure USB Debugging is in your notification bar.
Download these files onto your computer if you do not have the adb files yet. Extract the files preferably into the root of your hard drive (ie C:/ ) is just makes things easier this way.
Now open up command prompt.
If it is not in the directory where the adb.exe file is, you will need to type:
cd C:/
into command prompt. This says "change directory to C:/" (or wherever you put the files, could be cd C:/Program Files/ could be anywhere. wherever you extracted them to.)
Once in this new directory, type this into command prompt and press enter:
adb devices
If a device pops up (mine said TY290380 or something like that) that means that it recognizes your atrix. That is great news. We now have to enable ADB root access on the phone.
If nothing pops up, or it says some sort of error, you are not in the directory where adb.exe is located. Navigate to the proper directory.
Now, type the following command:
adb shell
One of two things can happen here. It will either create a new line with a $, or a new like with a #.
blah blah C:/ adb shell
$
or
blah blah C:/ adb shell
#
If a $ came up, you need to prepare a command BUT DONT PRESS ENTER YET. Type in "su", but dont hit enter. Now go to your phone and unlock your screen. After you unlock your screen and can see your homepages, press enter on your keyboard doing the "su" command. Now look at your phone. A superuser request should appear. Hit yes, and make sure that "remember" is checked. If not, it is ok, as long as the su command went through on your screen. it should now show a # on your command line.
For those of you who had a # on your command line, type in shsu and hit enter, then type in su and hit enter (just to play it safe ).
We are now ready to flash the first files to our device. You can close the command window.
Step 9:
Download this file. It is the original unmodified system partitions and files (thank you NFHimself). Extract the file using winrar or 7zip.
Change your USB connection on your phone to: Mass Storage, wait a minute or so, and then put the extracted file "mmcblk0p12.bin" in your internal storage on your phone. (ie. F:/ )
Step 10:
Dismount the phone from your usb devices via windows hardware manager. Unplug your atrix from your usb. Reconnect it, and choose connection type: none. Make sure usb debugging is in your notification bar.
Now, re-open command prompt. Renavigate to the directory where your adb files are located using the "cd C:/" command (or wherever your files are). Once there, perform "adb devices". Make sure a device is there. Next, perform the command "adb shell". You should have a #. Type in shsu, hit enter, now su, hit enter (just to be sure).
Now copy this command and hit enter (you have to right click paste into cmd prompt):
dd if=/sdcard/mmcblk0p12.bin of=/dev/block/mmcblk0p12
This will begin the flashing process, which will restore all stock system partitions allowing us to update properly. However, it's not over yet .
Mine took a few mins, do not panic. Simply wait for it to say "Complete" in x amount of seconds or whatever. Your phone may crash, but it should boot up fine (if not, that is why we have installed Tenfar's CWM )
After it is complete, turn off your phone. Keep it connected to the computer.
Step 11:
Boot up your phone holding volume down. Navigate to android recovery using volume down. Volume up. Open up the menu with the bottom left bottom right press. Go to clear cache. Press OK. Now reboot your phone.
You can now update through settings and it should work properly. If not, respond in here and I will guide you a few more codes, but it should work.
The phone should now boot up, and it should be running android version 2.2.2.
Regard this thread for how to root the new bell update. Just a heads up, it wiped my internal storage and SD card, so remove and backup that stuff. Lol. But it did root.
Now reinstall your backup program, and get your phone going again!
If you have any questions or problems please post them here and I will reply ASAP, personal messages are hard to keep track of. Thanks again to NFHimself for supplying files and code.
Cheers!
PS: I just finished exams, yay!?
Please say if you notice anything misspelled, etc. Gratzi
You are the f***in man for posting this. Thumbs up to NFHimself for his contribution too!
Links
Crud, your links for the files in dropbox aren't working.
Silvercloak5098 said:
Crud, your links for the files in dropbox aren't working.
Click to expand...
Click to collapse
You sure? I clicked them both myself to make sure they work.
How don't they work?
FYI: I'm reuploading them to megaupload as we speak anyways
IrshaadH said:
You are the f***in man for posting this. Thumbs up to NFHimself for his contribution too!
Click to expand...
Click to collapse
When I got my phone to update to 2.2.2 it felt amazing.
I just wanted to spread the love
Thank you so much!! You don't know how frustrated I've been all day! The only problem I had was that my root was gone after I flashed it, but I just updated through settings and it worked flawlessly
tyrkk said:
Thank you so much!! You don't know how frustrated I've been all day! The only problem I had was that my root was gone after I flashed it, but I just updated through settings and it worked flawlessly
Click to expand...
Click to collapse
NP! Just glad you got your update.
I changed the steps so that the last step is simply updating via settings. If that doesn't work for people I will help them out in this thread with the more complicated coding way.
Cheers!
Couldn't step ten be used to revert to stock from an international sbf?
Sent from my MB860 using XDA App
Ok..quick question. You said not to install for those using any international version. I have run the Telstra sbf at one point..as well as had the Greyblur rom on. Before installing the Telstra I had made a backup using CWM, and a few days ago I had to revert to my old backup due to a rogue app. In my About phone, it tells me my System version is Blur_Vision.0.37.4MB860.BellMobility.en.CA with a Build number of OLYA_U4_0.37.4.
Would this be still safe for me to do seeing's how it seems i'm back to my "Bell sbf" or is there still going to be some Telstra files in there that could cause me some problems?
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Rickroller said:
Ok..quick question. You said not to install for those using any international version. I have run the Telstra sbf at one point..as well as had the Greyblur rom on. Before installing the Telstra I had made a backup using CWM, and a few days ago I had to revert to my old backup due to a rogue app. In my About phone, it tells me my System version is Blur_Vision.0.37.4MB860.BellMobility.en.CA with a Build number of OLYA_U4_0.37.4.
Would this be still safe for me to do seeing's how it seems i'm back to my "Bell sbf" or is there still going to be some Telstra files in there that could cause me some problems?
Click to expand...
Click to collapse
Depends on whether or not you're still on the telestra framework. If you're confident with your ability to recover from a potential brick via early usb enumeration id go for it.
bdking2 said:
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Click to expand...
Click to collapse
Edit: See my lower post first, then this one
Open up the menu in android recovery by tapping both the bottom left corner and bottom right corner of the screen at the same time.
It should show you an error if there was one.
Does the phone boot fine?
You should lose root access. When you flash the .bin it restores your bell to stock like you got it from the store. That allows you to update.
Most importantly open up the recovery menu when you see the triangle by tapping the bottom left and right corners simultaneously. Itll take a few tries.
IrshaadH said:
Couldn't step ten be used to revert to stock from an international sbf?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
No, since you are on an international framework it will probably brick your phone.
That .bin file contains the system partitions from the stock bell framework.
If you want to try go ahead but I think the odds are against you
bdking2 said:
I made it through to the end of step 10 and the phone was looking good. Then when I shut off the phone and tried to go into Android Recovery, it keeps going to the triangle symbol and I have to reboot.
After a couple times of that I decided to check Android Recovery from inside the app list and it said I no longer have root access.
Any ideas what to do now??
Click to expand...
Click to collapse
Bdking I have another idea. if you can boot up your phone, re-root it using any normal methods, then install CWM. Boot into CWM recovery mode and clear the cache from there. Then do step 11.
Chances are the update file is hanging out in your cache so when the android recovery sees that it immediately tries to install the messed up package.
Thats why you should clear cache on CWm because it wont try to install anything automatically from the cache. Then do step 11.
Hope it helps, Mag.
No my phone boots fine. And now I can get into android recovery to clear cache and have done so. But before I read your response I rooted my phone again.
Should I just restart everything?
bdking2 said:
No my phone boots fine. And now I can get into android recovery to clear cache and have done so. But before I read your response I rooted my phone again.
Should I just restart everything?
Click to expand...
Click to collapse
No you should be good to go try to update via settings.
You flashed the bin right?
If so you're good to go
I flashed the bin for sure. But wasn't sure about the process because I rooted again.
bdking2 said:
I flashed the bin for sure. But wasn't sure about the process because I rooted again.
Click to expand...
Click to collapse
Root shouldnt change anything only deodexing/webtop mod/ theming should mess it up.
If you flashed the bin go for it. Worst thing that can happen is that the update fails.
In that case, redo step 10, then do step 11.
Magnetox said:
No, since you are on an international framework it will probably brick your phone.
That .bin file contains the system partitions from the stock bell framework.
If you want to try go ahead but I think the odds are against you
Click to expand...
Click to collapse
So, there is absolutely NO WAY I can get back to the Bell framework from 2.1.1 without an actual Bell sbf?
IrshaadH said:
So, there is absolutely NO WAY I can get back to the Bell framework from 2.1.1 without an actual Bell sbf?
Click to expand...
Click to collapse
NFHimself knows a way.
But hes a master of code.
Pm him, he might be able to help you.
He was happy he got his bell 2.2.2 thoough. so im assuming it wasnt easy.
I am stuck at a blue screen, and I was told here that I need some linux backup that someone might have made so I can restore it to my phone and everything would be ok and back to normal again!
I really need as soon as possible because my phone is bricked and I need it!
The last thing I flashed to my mobile, was the official 2.3.5! for x5
Ok, here's what you should do:
Download this.
Connect phone to USB.
Copy the zip contents onto the phone (partition with size about 252mb).
Remember to keep the folder structure partition/image/boot.img etc.
Restart - if system is not corrupted, it should boot.
Blefish said:
Ok, here's what you should do:
Download this.
Connect phone to USB.
Copy the zip contents onto the phone (partition with size about 252mb).
Remember to keep the folder structure partition/image/boot.img etc.
Restart - if system is not corrupted, it should boot.
Click to expand...
Click to collapse
There is a problem, when I connect to USB and press Volume Up + Volume Down buttons to get to the purple screen it aint reading my phone as a device or sth I can put files into it!
Something with the drivers!
That was occurred even before that blue screen happened, when I installed the 2.3.5 official and the the drivers with SuperOneClick!
Ok, do you have a external SD card? If you do, check this.
After applying that, try to do the steps I posted earlier.
thanks I will this night, because I got lessons to attend at the moment!
Thanks a lot, you offered a great relieve!
I did it! I am back at official 2.3.5!
But I cant root :/ SuperOneClick Crashes when i press ROOT! Drivers and everything are installed!
It just wont root!
And I also tryed to first install SuperUser first!
See this thread for other rooting methods. I've used Doomlords method and it worked great
I have an Acer 500a I just bought off carigslist. Initially I thought it would be fine but then I realized I was inheriting someone elses problems. I hope someone may be able to help.
Within the first few hours I was noticing google Play crashed a number of times and struggled to update from Market. Somehow the update went through but now there is a system update that won't go through. I'm able to down load it and when i restart the computer to complete installation the screen goes black and says: booting recovery kernel in the corner. I then see a picture of an android and a load bar which after 2-4 seconds the android is on his back and an exclaimation mark is coming out of his belly.
My android version is 3.2
Kernel version
2.6.36.3+
Build number
Acer_a500_7.006.01_COM_GEN2
I'm pretty sure its rooted and i think that might be why its not playing nice with google market and system updates. I called the old owner and explained the problem and he just said he had it rooted and he thought he unrooted it. There is an ap called superuser in aps. (although if it were rooted would'nt I be able to uninstal some of thecrap software it comes with like GOLF HD? -- it won't let me).
The system update is for Acer_a500_7.014.01_COM_GEN2 8.88mb
My problem is all of the force closes I'm getting and the inability to update the system. Any thoughts? I don't have a usb cord to connect it to a desktop either =(
I am a bit out of practice, but...
Should be pretty simple to fix. From what I am seeing, you are running a stock rom. Just because the superuser.apk is installed on the system does not mean it is rooted, but it probably is.
Hit the market, grab "Root Checker" - simple tiny program to let you know for sure if your tab is rooted or not.
https://play.google.com/store/apps/details?id=burrows.apps.rootchecker&hl=en
From what I understand - automatic system updates will fail when trying to apply them to a rooted or modded system. Probably why you cannot auto-update.
My advice at this point would be to:
1) Since you just bought it, just do a factory wipe on it. That will remove all the stuff the prior owner had running on it and will result in a unrooted tab that should be able to get auto updates without a problem.
2) Un-Root it. Once the tablet is unrooted, the system should update without any issue.
As for your Play Store issues - I have never heard of or personally seen any issues caused with installing apps from the store on a rooted device. I have seen a few apps that will refuse to run on a rooted device - but that does not sound like your problem.
I would go with option 1 - just factory wipe the thing. Prior owner may have made tons of changes to the OS that we will never know about, and may have handed you a unstable system. Start fresh. Wipe it out.
Hope this helps you out! Let me know if I can answer any questions.
k thank you so much for the quick reply! I downloaded the root checker and it Is rooted. I did a factory wipe as found in the settings privacy tab when I bought it. That factory reset did not unroot and only cleaned out some of the aps on the device. Is there a better or more surefire way to unroot it? If I reset with the volume down key will it hard reset it?
Thank you for you help!
Draight
Okay.
I am about a year out of practice with my a500 - but from what I am think, if a factory reset still results in a rooted device - the prior user installed a stock ROM that comes pre-rooted.
I highly doubt being rooted is causing the issues you are running into.
At this point if you just want to get back to stock you can probably just install the Acer Recovery Manager from the market and use it to reflash a stock unrooted ROM. Or I see a few guides about how to manually restore back to stock over in the dev section for the a500.
Others will correct me if I am wrong, but I think Acer Recovery Manager should take care of your problem.
Hope this helps!
(Edit: Or you can just download the official stock 4.x rom (ICS) from the dev section and flash that. 3.2 is pretty slow and wonky in my experience, you should be able to just download a 4.x ROM and flash, since you are rooted. Again, I am way out of practice. Don't do anything before reading up!)
(Edit again: I think I was making this harder then needs be. Just flash any stock 3.2 unrooted ROM, done. After you do that the automatic on the air update should kick in for you and update you to ICS)
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
draight said:
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
Click to expand...
Click to collapse
Hmmm..
Try the thread I linked two in my second edit of my last post. You just need to grab the stock and unrooted 3.2 - put it on a MicroSD card as update.zip - then reboot with vol rocker and power switch to get the system to flash the update.
That *should* work just fine.
(Edit: Forgot the link! http://forum.xda-developers.com/showthread.php?t=1839313 - there you go)
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
draight said:
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
Click to expand...
Click to collapse
Nope. Just snag the stock unrooted 3.2 ROM - place it in the root of the MicroSD card as update.zip
Power down.
Power up with VOL + and POWER key held at the same time (you can let the vol rocker go when you see text appear in the upper left corner)
Should be all you need to do. Worst case; it does not work and returns you back to where you are now. Worth a shot.
If that does not work, let me know so I can do a few mins of homework and help you further. Been a long time since I have changed ROMS or had any issues with my a500.
I have bricked it twice by not following directions all the way or just making simple mistakes, but from what I have found there is always a way to recover.
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
draight said:
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
Click to expand...
Click to collapse
Hmmm. Odd.
Like I said, I am rather out of practice.
Someone more experienced them me: please help me point Draight in the right direction here?
Thanks for trying to help. =(
I wish that my tablet wasn't having such issues. I;m going to try to scramble around the forums and see if I can find some advice...If anyone has a suggestion please let me know.
Thanks again entropy,
Draight
Update:
So I've been tinkering around with it a bit more and I found a usb cord that plugs it into my computer. I keep finding boken links on this site so Im struggling to find an update I can use to flash to. I downloaded a different super user program which allowed me to temporarily unroot my device. I then restarted it and no root checker says its no rooted and I cannot find the superuser program. I think I have somewhat unrooted it -- but I think the real issue now is the recovery tool. I keep reseting it - hard reset, or factory reset and it wipes everything away but when i try to update it gets about 1/3 of the way up the bar then it stops with an '!' Mark above the droid. Im kind of annoyed at this point and hoping for some new links or some ideas on how to repair the recovery piece.
Draight
Go to the Dev section, and grad a couple of the ICS Update roms. You will see them listed for the a500. Make sure they are the FULL update roms. Should be about 3-400mb. These contain a FULL ICS Update Rom, and not a patch file.
http://forum.xda-developers.com/showthread.php?t=1816560
Then, go to the Themes and apps forum. You'll see a sticky that has the Acer Update Decrypter.
http://forum.xda-developers.com/showthread.php?t=1869505
Now, unpack the decrypter, and select one of the ICS Updates. Then hit Start. Take a couple minutes, but you will have a duplicate file with the word "decrypted" added to it.
Wait, you are not done yet.
Using a program like 7zip, or even Winzip, open the decrypted file. DO NOT EXTRACT, just open it and pull the update.zip to your PC's desktop.
Copy that update.zip file to your Ext SD Card of the tablet. Don't be putting it in any folder, just copy it to the root of the card.
Now, you still ain't done.
With the tablet off. Press and hold Vol+ and then PWR. Hold them both untill you start to see text about installing blah blah blah, then release the buttons.
If it completes, and you can reboot into ICS, then you are good to go.
If something fails during installation, then decrypt the other update Rom file you downloaded, and do the same procedure. Usually one of the 2 or three should work for you.
Note these are for the a500, and not the a501.
One more thing. It's advisable you get your UID number before doing these things. You probably won't need it, but it's nice to have written down in case you need it in the future. Inf to get it is at;
http://forum.xda-developers.com/showthread.php?t=1624645
MD
Thanks! I am downloading a few of the FULL ICS roms:
*Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy
Acer_A500_1.031.00_PA_CUS1: http://d-h.st/idO
Acer_A500_1.041.00_WW_CUS1: http://d-h.st/Yt5
*Acer_AV041_1.054.00_WW_GEN1: http://www.theandroidcollective.org/...00_WW_GEN1.zip
*Acer_A500_7.014.16_041.206.01_COM_GEN1: https://docs.google.com/file/d/0B_bk...hVc1RVcHc/edit
The I downloaded the ones ending with Gen1. Once they are downloaded I will continue with the instructions. Thank you so much for your help! I will post how it goes later tonight.
Draight
I just decrypted both:
*Acer_AV041_1.054.00_WW_GEN1:
*Acer_A500_1.031.00_WW_GEN1
Both get get to the third bullet quickly and the bottom says DONE! It takes like 4 seconds. I don't think the Decryption key of $12 is working
[*] Opening file: Acer_A500_1.031.00_WW_GEN1.zip
[*] Decrypting using key $12
[*] Writing decrypted file: Acer_A500_1.031.00_WW_GEN1_decrypted.zip
I try to extract something from the decrypted file and it says the file was not downloaded properly and I should try redownload it...it says its not a proper archive
wahoo!
So that worked! I down loaded the file Acer_AV041_A500_1.033.00_PA_CUS1 and extracted the update. I palced the update on the sd card and booted with the power and sound volume pressed down. it went through the installation procedure and restarted twice before saying it was upgrading my aps and BOOM its got ICS and everything looks great. Thank you so much for your help and I hope that this paper trail is able to help someone in the future
My problem is that I'm on ICS and I'm rooted, but I just can't download a custom recovery. I've tried, and I haven't gotten anywhere
Sent from my SPH-L710 using Tapatalk 2
Having recently purchased a TF300T with intent to customize the hell out of it, I ran into a big problem. There wasn't one definitive guide for my general case, some of the steps I read weren't completely clear, and I often had to put pieces together from multiple guides to get where I wanted. Halfway through the process it occurred to me that sharing my experience in form of a guide could give the community something I wish that I had when I began. So enough with the intro, let's visualize the process before we begin.
This guide is for new owners of TF300T devices that have Jelly Bean 4.1.X preflashed from the factory.
joelalmeidaptg said:
If your tablet has 4.2.1 Android version from Asus, DO NOT FLASH A RECOVERY THAT WAS ACTUALLY MADE FOR 4.1 TABLETS! You will end up on a PERMANENT BRICK with no solution until now. You won't be able to use fastboot ever again. You won't be able to flash anything ever again. You will be stuck with a bricked tablet!
If you are looking for a Recovery for a 4.2.1 bootloader (and a complete guide for updating), read this thread: http://forum.xda-developers.com/showthread.php?t=2187982 Don't do it with any other tutorial: they are for 4.1 bootloaders!
Click to expand...
Click to collapse
For those curious...
My TF300T was one of the Champagne Gold models purchased from Groupon with a serial that begins with C9. I recall seeing a user with a Champagne Gold from Amazon that still had ICS. If you're still on ICS, this guide isn't for you-- Read up on NVflash and decide if you want to take advantage of it BEFORE you upgrade to JB.
Here's an overview of what we will be doing:
Click to expand...
Click to collapse
Unlock the TF300T
Backup apps, app data and files (Recommended, Optional)
Install ClockworkMod Recovery (soon to be replaced with TWRP; I gave in)
Root the TF300T (Optional)
Backup your stock Asus ROM (Recommended, Optional)
Flash a Custom ROM
Backup your working Custom ROM (Optional)
Additional information you should know:
Click to expand...
Click to collapse
This guide has been made with the total android noob in mind. Having only owned an android tablet for a week, I too am an android noob. On the flipside, I'm no noob to hardware and software exploits and modifications. I've tried to make this friendly for any type of noob, but there are a few instances where I expect basic menu and Windows 7 navigation skills.
ClockworkMod Recovery doesn't appear to have a "Shutdown" function, nor does it display current battery level-- for this reason, the recommendation and warning to have a battery charged to at least 60% is extremely heavy. The worst thing that can happen to any device is usually an incomplete flash. Don't let it happen to you-- start charging your TF300T NOW.
I have seen reports that "Fastboot" doesn't work properly on Windows 7 64-bit. This guide addresses that issue, as I also encountered it. If you don't know what "Fastboot" is, in the words of an admirable comedian, "You gonna learn today". Don't worry about it for now!
Your device came with JB-- you didn't miss the bus for NVflash. In your case, the bus never came.
I am not responsible for any damages caused to (but not limited to) yourself or your device.
Even if you think you're pretty good at figuring this stuff out, stick to the directions as close as possible.
If you love tweaks, you're going to love your custom ROMs.
Let's get started!
Unlocking Your TF300T
Click to expand...
Click to collapse
WARNING: Unlocking your TF300T will void your warranty. If your device breaks or fails under normal use, don't expect Asus to pick up the tab! Be aware that once unlocked, it cannot be relocked.
There are two ways you can go about this-- Either download the official Asus unlock utility for Windows or download the .apk and install from your tablet (Asus utility still working! I successfully unlocked mine on JB 4.1.1). I chose to download the .apk and install directly on my tablet, therefore this is the method I will cover.
To download the .apk file, scan the QR Code below with Barcode Scanner (free; on Play store) and open the URL to the Asus Support page for the TF300T. Alternatively, if you are viewing this thread on your TF300T, you may simply tap the code below.
On the Asus Support page, select "Android" as your OS. The page will reload and present you with a list. Click on "Utilities", then after it has loaded, download the Unlock Device App. When it is done downloading, a notification will pop up in the lower right corner. Click on it to install the Unlock tool. You'll also be able to open the app immediately after the install completes-- open it now.
After scrolling to the bottom of the End User Licence Agreement, select the checkbox indicating that you agree to those terms. You should now have access to the slider that will unlock your tablet. Stay connected to your wifi and unlock when ready. The unlock will not work without access to the internet.
If I recall correctly, your tablet should reboot. Just let it do what it wants. After it's done doing it's thing, take this opportunity to make backups! when you and your tablet are ready, we'll continue on to the next step.
Setting Up The Android SDK and Installing ClockworkMod Recovery
Click to expand...
Click to collapse
Perhaps this was the most frustrating part of my experience-- Installing the Android SDK went fine when I could actually find the .exe download. After that it was a matter of getting the drivers for Fastboot working properly. I was able to narrow it down to a problem for users of Windows 7 64-bit.
From your PC, go HERE, scroll down and click on "Download For Other Platforms". Scroll down more and under the "SDK Tools Only" downloads, you should find a download that looks like: "installer_r##-windows.exe" where "##" is the revision number. Download this .exe and assuming Windows is installed on C:\, install it to either "C:\tools\android-sdk" or "C:\android-sdk". If Windows is not installed to drive letter C, replace the drive letter with the correct letter for your system. Do the same when following the command prompt examples that follow.
Open the Android SDK Manager. Search for "SDK Manager" in the start menu and you should find a result with the same name and a little android icon. Once it's open, you'll be presented with a list. Check the box next to the "Tools" folder, then expand the "Extras" folder and check the box next to "Google USB Driver". In the lower right corner, click "Install packages...", agree to all when ready and begin your downloads.
In the settings application of your tablet, go to the "Developer options" tab near the bottom. Ensure that the switch in the top right corner is in the "ON" position, then under the "Debugging" header, enable "Android debugging". Read the following carefully before you continue: Shut down your tablet and connect your USB cable. Hold the power and volume down buttons at the same time. Keep holding until you see a menu. The menu will consist of a few items, among them there is "RCK", a USB icon, an Android icon, and a "Wipe Data" icon. Tap volume down until the USB icon is selected, then press volume up. Cross your fingers and hope drivers install automatically.
They probably won't, so have windows look in the \android-sdk\extras\ folder. It should say the drivers installed successfully. Either way, open the start menu, and right click on "Computer". Click "Manage", then in the left hand pane of the new window, click "Device Manager". The "Other Devices" section may be already expanded in the center pane. If it is, look to see if "Fastboot" appears in that section with a yellow exclamation mark.
If it isn't there, you shouldn't be worried-- check for a section called "Android Phone" or "Portable Devices". Look for a device called "Android ADB Interface" or "Fastboot". It shouldn't have a yellow exclamation mark next to it.
In the event you have the device appearing with a yellow exclamation mark next to it, go HERE and download PdaNet. This was my remedy for this error. Unplug your TF300T from your computer and install PdaNet following instructions. During the install a warning will appear to install unsigned drivers. Install the driver anyway, and let the installation finish. You can now plug your TF300T back in, and it should be recognized automatically. Just in case, hold the volume down and power buttons again until your tablet restarts and you see your hidden menu again. Once again, tap volume down until the USB icon is selected, then press volume up again to select it. Check the Device Manager again and you should find the "Android Phone" section at the top. Within it, you'll find a device called "Android ADB Interface".
Now that we have your tablet and computer set up nicely, we can finally install ClockworkMod (CWM) Recovery. Go to THIS thread and download the attachment called "recovery-jb.img" (thanks XpLoDWilD!). It is VERY important that you download "recovery-jb.img" as this is the version for users with Jelly Bean bootloader!
Rename the file you just downloaded to "recovery.img" and place it in \android-sdk\platform-tools . In Windows 7, open the Start Menu and search for "cmd". You should see a result called "cmd.exe". Right click that result and click "Run as Administrator". Now type the following commands into the new command prompt window in order to flash CWM Recovery:
Code:
cd C:\tools\android-sdk\platform-tools\
fastboot -i 0x0B05 flash recovery recovery.img
DON'T unplug your tablet!! Don't close the window either! Wait for the command prompt to finish what it's doing, then you can type the final command:
Code:
fastboot -i 0x0B05 reboot
Your tablet will reboot. Once it has fully rebooted, shut it down and hold volume down and power again to access our tablet's hidden menu. This time, instead of selecting the USB icon, select "RCK" and press volume up. If I'm not mistaken, "RCK" stands for "ReCovery Kernel". ClockworkMod Recovery should load up. If it doesn't, then you were not successful in flashing CWM. If it does, then you can go to the Backup and Restore menu and create a backup.
I was overconfident when I went through all this, and I didn't make a backup-- for me, I wasn't able to get my SD card detected (64GB fat32), but even in this case you should be able to make a backup to your "Internal SD card". Unfortunately, you are on your own for this step. Make sure that you transfer this backup to your PC after creating it. You may need to disable Developer options in your TF300T's settings before you can transfer files over again.
In THIS post, XpLoDWilD gives instructions on how to Root your tablet. If I'm not mistaken, this applies to users who are using a ROM that does not already have root. If you care about Root right now, you can go ahead and flash his attached .zip file using CWM to your TF300T.
When I did this, I selected the .zip file with CWM and then went back to the main menu to select reboot. CWM then prompted me that it needed to fix permissions in order to keep Root. I tried it both ways-- first I let it fix permissions, then used a Play store app to check for root. Test came up negative, so I tried again without allowing it to fix permissions. Negative again. I tried again, allowing it to fix permissions again and then left it alone. If you are successful in rooting your TF300T, you can use Titanium Backup to backup your device later. However I used an app that did not require root that worked fine. The choice is yours.
Flashing a custom ROM
Click to expand...
Click to collapse
Now it's time to find a custom ROM to flash. For my guide I will cover Baked TF300T Blackbean #6-- Based on CyanogenMod10, and quite a nice upgrade from the stock ROM. The only downside I found is the Asus App Backup application is not included and cannot be installed. I'm unsure why this is the case-- I have even attempted to install it via CWM with no success. If you need this app or the App Locker app, I suggest you choose a non-CM10 ROM. You are on your own in deciding an alternative, but I have heard great things about CleanROM and I seem to recall reading that these incompatible Asus apps work on it. Don't take my word for it-- do your own research to make sure!
It should also be noted that ROMs like Blackbean #6 have some potentially dangerous settings that can make a power user salivate profusely.
Spiderman's Dad said:
With great power comes great responsibility
Click to expand...
Click to collapse
Okay, so it was his uncle, whatever. But either way, if you're going to install this ROM (or any other with overclock tweaks), BE CAREFUL when selecting different settings for CPU speed and overclocking. I used to overclock my PC as a hobby and pushed a 1.8GHz CPU to 2.77GHz on air cooling.. The thing I learned in the process is if you don't have the proper settings, your computer becomes unstable and weird things start happening. Data corruption, clicking the Start Menu does something crazy and unusual, PC crashes randomly, etc... Some of these errors are due to insufficient cooling-- a problem you cannot remedy when working with a portable device.
Assuming you are new to this tablet like I am, use this rule of thumb when dealing with foreign and potentially dangerous things: DON'T TOUCH IT until you understand it. Then when you understand it, understand it again. Then when you feel you've understood it twice, take baby steps. It's like jumping up a cement set of stairs-- you're definitely not going to try to jump five steps in your first attempt, unless you want to risk smashing your face and bloodying yourself up. Take it one step at a time-- make sure you can land on your feet before deciding to go further.
There's a lot of other options Blackbean #6 has that the average user can still appreciate, so ignore those overclocking/CPU stuff and focus on the other tweaks. Nova Launcher is included and is pretty sweet. I upgraded to Nova Launcher Prime and feel it's worth the extra $4, but I'll leave that for you to decide. There are more options than merely Nova Launcher alone, and not all of them have a price tag.
Without further adieu, let's download the Blackbean #6 ROM and Gapps. Head over to THIS official release thread for the downloads. The names of the files you want are:
baked_tf300t_blackbean-6_jb-bl_b6.zip
gappsinverted-jb-20121029-signed.zip
Put them into a folder called "bb6" and copy the folder over to your TF300T. If your SD card is working in CWM (from CWM, go to the "mount" menu and try to mount SD card), copy the folder to your SD card.
NOW is the time to do any final backups before your fresh ROM install! I recommend "App Backup & Restore" on the Play store. If your tablet is rooted, you can also use Titanium Backup. Both will work fine, though generally speaking people seem to prefer Titanium Backup. People also seem to prefer TWRP over CWM, but I personally find the design unappealing. More importantly, I could only find a proper guide on installing CWM on a factory flashed JB TF300T.
Once you've made your backups, don't do anything until these backups are safely transferred to your PC! Don't forget to backup your music, movies and photos...
Now that you're 100% confident you've made all the backups you need and your battery is well charged and ready to go, let's flash your custom ROM! Shutdown and enter our hidden menu you should be very familiar with by now. Boot into CWM (with RCK icon from hidden menu selected, press volume up), then press volume up/down to navigate.
READ THE FOLLOWING SECTION BEFORE DOING ANYTHING ELSE:
Select "install zip from sdcard" and tap power. If you placed your "bb6" folder on your SD card, tap the power button once more. If it says "Can't mount /sdcard/" in the bottom left corner, then select "choose zip from internal sdcard" and tap power. Earlier you should have put your ROM and Gapps in a folder called "bb6". If you can't find this folder in either the SD card or internal SD card locations, GO BACK, reboot, and make sure you put the folder on your TF300T or your SD card. You should also make sure that the ROM and the Gapps file are inside that folder as well. Do NOT unzip them! They are just fine as they are. We are NOT flashing the ROM and Gapps yet, we are merely making sure they are there before you wipe your tablet. If the files are there, go back to CWM's main menu.
Select "wipe data/factory reset" and tap the power button. Confirm that you want to wipe, wait for it to finish.
Now select "wipe cache partition" and press the power button. Confirm that you want to wipe, wait for it to finish.
Go back to the main menu and select "advanced" and tap power, then select "wipe dalvik cache" and tap power. Confirm that you want to wipe, wait for it to finish.
Don't worry! Your ROM and Gapps should still be in your bb6 folder. Navigate to "install zip from sdcard" again, and let's make the magic happen. We are going to install the ROM first, then install Gapps. Only after both the ROM and Gapps are installed will we reboot our tablet.
So select the ROM first, confirm that you want to install, wait for it to finish. This one will take a long time compared to the Gapps. Just be patient and wait, even though it looks like it's not doing anything.
Then select the Gapps, confirm that you want to install, wait for it to finish.
Finally, reboot your tablet and cross your fingers. You should be greeted with the sweet victory of the startup animation. Go through the first time setup routine, and make sure the tablet works. From here you can optionally backup your custom ROM, but I recommend getting your settings the way you like them before you backup.
Give yourself a pat on the back--you survived! Hope this guide helped someone out-- I was able to sort through my problems fine, but I felt it important to share my experience. I know I couldn't have been the first to hop through these hoops anyway.
Congrats on your custom ROM Transformer Pad. Enjoy your tablet.
P.S. Questions? Comments? Suggestions? If you have any of the three, feel free to share! If it's a suggestion, please PM me and I'll see about making edits to my guide. All are appreciated, and especially anything that clears up any uncertainties I've expressed.
Special thanks (individuals and groups I owe credit for my process):
Drgravy, Team Baked, and everyone who wrote code that was used in the Blackbean ROMs. Blackbean #6 is my first custom ROM, and so far it's been great!! Keep up the awesome work!
XpLoDWilD, for CWM Recovery + Root on TF300T. These files and instructions were the major keys in making my endeavor a success
I also want to send out a big thank you to every other individual and team who has released a custom ROM for the TF300T-- admirable work, and far more than I could ever do. Thanks for giving us options and making us excited to have a customized tablet!
(....And many more! Currently in finals week (yikes) and can't recall everything right now-- will add more as I remember)
It's a shame that such a well written guide has so little thanks. Have mine.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Very nice. hopefully this helps people just getting the tf300.
note, if you want to install TWRP recovery instead, your command will change accordingly, just make sure you type in the exact file name you want to flash. so if your recovery file is named twrp.blob:
fastboot -i 0x0B05 flash recovery twrp.blob
Thanks!
Your guide helped me a lot. I had problems only with root. Flashed 4 times, but always got "no root acces". Finally, I downloaded root package from here http://forum.xda-developers.com/showthread.php?t=1845377 and it works well
is there any way around that "unknown error..." when i try to use the unlock app yet?
I keep trying but the same error message keeps coming up
sq1ne said:
is there any way around that "unknown error..." when i try to use the unlock app yet?
I keep trying but the same error message keeps coming up
Click to expand...
Click to collapse
Is your tf300 new? first hand? or have u ever sent it to asus for repair before?
Well written, well thought out instructions. Many, many thanks!! I'm still having some trouble though. I get stuck once I download the unlock app, open it, agree to the EULA, then another warning appears that is a black screen white text and a yellow triangle. Nothing happens after that. There are no buttons to agree, no checkboxes, nothing happens. Any advice?
*UPDATE* Figured it out. Be sure to sent the font in settings->display->font size to small, then you will see it. The large font pushes the agree button off the bottom of the screen.
It would be great if CWM in this OP were replaced with TWRP. Many are having issues with CWM. Me being one of them. I flashed TWRP with fastboot and no more problems!
I agree with the post above. Sad that such a well written post has so little thanks. :good:
thnx for this amazing guide, but I am still unsure of this guide will work for me.
I am from Holland (Europe)
specs from my ASUS Transformer TF300T:
Android 4.1.1
Kernel 3.1.10 ([email protected])
Buildnr JR003C.WW_epad-10.4.2.18-20121122
Pad EC Version PAD-EC20T-0216
My question is...will this guide also work for me? ...since I have JB 4.1.1 & build 10.4.2.18
I am also worried about the fact that this guide in for an american(?) transformer I gues...so do I need other files then the files mentioned?
I would love to have ROOT and install a custom rom and remove bloatware etc.
thnx for the help in advance!
Thank you so much, perfect for so many people here.
Can you edit it with TWRP? I would use this right now but as above poster said there have been issues with CWM so don't want to try it.
P.s. i got mine from groupon too
Tamaskan said:
Is your tf300 new? first hand? or have u ever sent it to asus for repair before?
Click to expand...
Click to collapse
bought mine brand new just this past Black Friday.
updated to .18 firmware
I don't want to have to send it in.
GodfleshNL said:
thnx for this amazing guide, but I am still unsure of this guide will work for me.
I am from Holland (Europe)
specs from my ASUS Transformer TF300T:
Android 4.1.1
Kernel 3.1.10 ([email protected])
Buildnr JR003C.WW_epad-10.4.2.18-20121122
Pad EC Version PAD-EC20T-0216
My question is...will this guide also work for me? ...since I have JB 4.1.1 & build 10.4.2.18
I am also worried about the fact that this guide in for an american(?) transformer I gues...so do I need other files then the files mentioned?
I would love to have ROOT and install a custom rom and remove bloatware etc.
thnx for the help in advance!
Click to expand...
Click to collapse
Yes, it will work, I've tried it. But i suggest you use TWRP custom recovery though. CWM has high chances of getting bricked.
Tamaskan said:
Yes, it will work, I've tried it. But i suggest you use TWRP custom recovery though. CWM has high chances of getting bricked.
Click to expand...
Click to collapse
Could you also please add a NOOB tutorial for installing TWRP Recovery (this forum is very confusing in getting the right tutorials / avoiding outdated tutorials which would brick my TF300T etc)?
Example:
quote from XDA forum in TWRP topic: "The fastest and easiest way to install TWRP is to use the GooManager app" <--- GooMnager needs ROOT so I can't use this method?
My ASUS TF300T is completely untouched & unrooted still and don't won't to mess it up.
GodfleshNL said:
Could you also please add a NOOB tutorial for installing TWRP Recovery (this forum is very confusing in getting the right tutorials / avoiding outdated tutorials which would brick my TF300T etc)?
Example:
quote from XDA forum in TWRP topic: "The fastest and easiest way to install TWRP is to use the GooManager app" <--- GooMnager needs ROOT so I can't use this method?
My ASUS TF300T is completely untouched & unrooted still and don't won't to mess it up.
Click to expand...
Click to collapse
www.mediafire.com/?7v1gwbbzqzvzto7 <- fastboot and twrp, the twrp is out dated so if you want you can download new one from twrp website.
2)Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (you must click the fastboot and adb when extracred and i suggest you put your extracted fastboot and recovery zip in C:\(foldername) and then open cmd)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Credits to krabappel2548.
Tamaskan said:
www.mediafire.com/?7v1gwbbzqzvzto7 <- fastboot and twrp, the twrp is out dated so if you want you can download new one from twrp website.
2)Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (you must click the fastboot and adb when extracred and i suggest you put your extracted fastboot and recovery zip in C:\(foldername) and then open cmd)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Credits to krabappel2548.
Click to expand...
Click to collapse
Here is a little update on my progress...
- I unlocked the bootloader of my TF300T
- I managed to install latest TWRP
- Made a (COMPLETE) backup of the untouchedl system with TWRP <--- DO THIS BEFORE ANYTHING ELSE!
- Rooted the TF300T with the WW file in this topic: http://forum.xda-developers.com/showthread.php?t=2033205 <----works awesome!
- Made a second (COMPLETE) backup of the now ROOTED system with TWRP
- Tried installing the latest "Cleanrom 3.01 Inheritance", but got the infamous "bootloop" too...the rom has been pulled down from the forum till that is fixed ( I thought I had done something wtong flashing a custom rom, but actually a lot of others had the same problem)
- Waiting for a "bootloop fixed" Cleanrom Inheritance 3.02....and gonna try flashing it again.
first of all thanks a lot ive been going crazy looking for this!! my question is will it work for me?
i bought my tf300t in sept with ics and upgraded to jb....
also i tried this not to long ago and ran into a problem after i unlocked
so right now its just unlocked but not rooted do i need to reverse that or what?
my apologies im extremely noob haha
GodfleshNL said:
Here is a little update on my progress...
- I unlocked the bootloader of my TF300T
- I managed to install latest TWRP
- Made a (COMPLETE) backup of the untouchedl system with TWRP <--- DO THIS BEFORE ANYTHING ELSE!
- Rooted the TF300T with the WW file in this topic: http://forum.xda-developers.com/showthread.php?t=2033205 <----works awesome!
- Made a second (COMPLETE) backup of the now ROOTED system with TWRP
- Tried installing the latest "Cleanrom 3.01 Inheritance", but got the infamous "bootloop" too...the rom has been pulled down from the forum till that is fixed ( I thought I had done something wtong flashing a custom rom, but actually a lot of others had the same problem)
- Waiting for a "bootloop fixed" Cleanrom Inheritance 3.02....and gonna try flashing it again.
Click to expand...
Click to collapse
i never backup.... I only backup app using titanium backuo, if something on the rom goes wrong i just reflash latest firmware from asus website. If you like custom roms, i suggest you use Energy Rom if you want OC or Hydro rom if you want just modified stock rom with better performance.
I have a problem while I try to run the flash recovery command. I have done all steps prior to this.The only difference I see is in device manager I get "ASUS Android Devices". Now, the error I am getting comes after trying to run the command, I get "error: cannot load 'recovery.img' No error" . I have also tried the pdanet solution. Thank you for your help in advance.
Stupid question... but I am going to ask it. Having never rooted my TF300 it is on latest firmware will this guide still apply to be even though I bought my device running ICS but have updated to latest firmware? Have never rooted tablets before so all new to this.
Agera said:
Stupid question... but I am going to ask it. Having never rooted my TF300 it is on latest firmware will this guide still apply to be even though I bought my device running ICS but have updated to latest firmware? Have never rooted tablets before so all new to this.
Click to expand...
Click to collapse
It will work as long as you are using Jelly Bean
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
I've just made a simple batch file with adb, and the recovery file all in one zip for y'all.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to Your Internal SD card on your tablet
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Make sure your tablet is powered on, and connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
6) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Enjoy!
BIG thanks to Chainfire for his root, and team win recovery project for their fast work on the recovery!
07/30/13 Updated SuperSu link to latest revision (ver 1.51).
07/29/13 Updated SuperSu link to latest revision (ver 1.50).
For those that couldn't find their azzes if a target was painted on it, here's a link to the video.
http://www.youtube.com/watch?feature=player_embedded&v=UpcTMTu-5Qc
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Ravynmagi said:
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Click to expand...
Click to collapse
ADB reboot recovery
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to SD card
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Power off your device.
6) Once powered down, hold Volume Down and Power. (this will boot you into fasboot)
7) Make sure your tablet is connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
8) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
9) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
10) when you reboot Superuser will be updated automatically by the Play Store
Click to expand...
Click to collapse
Umm thanks, but the bat file boots you into fastboot...watch the video
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, you may want to create a folder in there for organizing all your flashable zips
greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, your INTERNAL SD CARD
Thanks guys, I haven't done much rooting / flashing with devices without SD cards before. I used the Nexus 7 toolkit to root the old Nexus 7. Everything I rooted before that had a real SD card to dump zips on - wanted to make sure where TWRP could access.
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
Click to expand...
Click to collapse
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
What error message are you getting at the end of the flash, or does it say success...watch the screen as it's flashing.
I just ammended the video, follow along
Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
ATGAdmin said:
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Click to expand...
Click to collapse
Cool, glad I could be of some small assistance.
Rooted just fine, thanks! Saved me typing some adb commands and such.
evodon84 said:
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
Click to expand...
Click to collapse
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Ravynmagi said:
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Click to expand...
Click to collapse
I dont know what happened but this did not work, I can still boot my device, but now I have no recovery installed. If I attempt to boot into recovery, i get the red triangle underneath it says *No command* I have tried to research the problem here but no luck in getting TWRP to flash.
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
samg77 said:
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
Click to expand...
Click to collapse
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
ATGAdmin said:
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
Click to expand...
Click to collapse
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
samg77 said:
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
Click to expand...
Click to collapse
You're preaching to the choir bro, I'm with ya.
Sent using XDA premium on my Nexus 7 (2) tablet.