Related
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
want a droid said:
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
Click to expand...
Click to collapse
Odin the proper clockwork,reboot straight to it, wipe data and then flash CM7 from the SD card.
Please give me step by step instructions with links. I'm an HTC Thunderbolt guy myself so I am having a hard time finding all the right links and stuff. I really appreciate your help!
First sticky in this forum has all the links and steps.
Sent from my SCH-I500 using Tapatalk
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
want a droid said:
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
Click to expand...
Click to collapse
Really? did you look at the sticky?
Code:
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. All of the files, I cant guarantee links to other OP's, will still be available, I wont take them down. Your recovery methods have not changed, nor have the PIT files, so this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1026746
odin...
atlas_v2.2.pit
CI500_VZW_ED05_FROYO_REL.tar.md5
check repartition
then follow the CM wiki
I don't understand why I'm getting this: http://imgur.com/WkDsK
Sorry for rotated picture.
I'm in the process of flashing the verizon firmware but it's taking forever to download. I thought I could just odin the CWM?
You better do some research before u brick ur ****...there are guides all over the place on how to get back to stock/flash roms. And last but not least all questions should be posted in the q&a section...that's what its there for...seriously use it!
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
When I try to connect it to my mac it says it can't read what I'm trying to connect. When I connected it to windows laptop it says its a CD drive that is write protected.
I can't move any files in or out. Also when I try to flash a rom zip in recovery it doesn't work.
I'm in the process of trying to restore her MIUI backup. Here's to hoping that works.
EDIT: Supposedly the restore worked, but here is part of the error that showed when trying to flash a zip (top text): http://imgur.com/X1RQL
Oh and I'm stuck on the Samsung screen now...what do I do?
want a droid said:
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
Click to expand...
Click to collapse
fail.
if you did CM Wiki, you have CWM 4.X, not 2 or 3
you need to flash back to stock like i said
I did flash back to stock. Anyways in the broken clockwork recovery I decided to try and install MIUI again and when I clicked it it took me to an orange recovery.
Then I flashed her backup and it loaded up fine. Hopefully everything is back to the way it was. I'm not sure what ever went wrong in the first place.Thanks for your help.
Dude...sounds like you just made it hard. Its actually quite simple.
Pull battery, put in download mode.
Odin the Verizon firmware with atlas.pit and repartition checked.
let it boot, then shut it back down and go back into download mode and Odin the fixed recovery for CM7. Then flash MIUI and profit.
It shouldn't take but about 15 minutes out so for the whole process
Swyped via Tapatalk
Well I wish you had been here last night. I was told to do the heimdall thing and then after all that the phone wouldn't be recognized in odin.
It was a frustrating 3 hour long process (granted ~1h was waiting for the 441MB file to download).
so I found this thread searching through the fascinate forums and i gotta say, it saved my ass. I used heimdall 1.3.1 and it wasn't working right for the flash. IDK why but when I tried 1.1.1 it worked first try to flash back to stock after brick. I used the eh03_full_odin.zip file in heimdall and it quick and easy to get back to stock =] this forum rox!!
Hi all, I'm running a rooted A500 (Android 3.1 build number Acer_A500_4.010.13_COM_GEN2) using the 2.6.36 Honeyvillian 1.0 kernel (so I could OC) and would like to upgrade to a rooted ICS. But since I changed from the stock kernel I get a little confused trying to follow other threads on what to do. The threads seem to start out on topic but tend to drift and for somebody like me, that can make it very hard to understand. I'd like to stay away from a custom ROM, no insult to the hard working dev's intended. You guys have saved alot of my devices from ending up on the top shelf of the closet. I'd like to upgrade to a "stock" rooted ICS with proper bootloader, kernel, etc. If I decide later to try a dev's ROM then I'll always have that option, but since I've never messed with ICS...stock may do all I need. I'd like to root for OC because some of the things I do seem to run better if the device is OC'd. So, what I need are a clear set of instructions on what to do. OTA's dont work, I'm guessing thats because of the root and kernel. Any help would be appreciated. Thanks.
There are 2 threads with Stock rooted ICS roms in the developer section. Read each and choose the one that suits you. Also, you may need to separately update the bootloader. To do this there is a new tool in the developer section called afterota 1.02. This will help automate the process for you.
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
realityrat said:
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
Click to expand...
Click to collapse
If you want to go completely stock (stock kernel, non-rooted), then you need only to install one of the Stock ICS Roms. This set's your bootloader back to a stock condition. So that's simple enough. You can do this through CWM
You said you're on Honeyomb right now. So my suggestion, is to follow these steps to upgrade your a500 to ICS.Go Here and read the steps;
http://forum.xda-developers.com/showthread.php?t=1622425
Pay attention to step 4. You have a choice. Stock Rom with Full Root, or (in small print (stock rom no root).
If you decide to install Stock Rom No Root, then skip steps 5 and 6. Just copy the file to your EXT SD Card, boot to your recovery (pwr & Vol-) and install Zip From SD. It'll be a done deal. Recovery gone, ICS Stock bootloader and rom.
I have you do steps 1-3 because I want you to write down your UID!!!!!! It's the only thing that will save you if something messes up.
Then you can decide if you want to root and install some custom stuff later.
MD
MD, can you run setCPU w/o Root? I didn't think so. Since this OP requests the ability to OC specifically I think that the steps listed would all need to be followed in Civato's post.
RR, Here are the steps I recommend, it's an opinion, and I think the best route to take as a fairly novice rooter, I've done my A500 many times and BN Nooks, but nothing else and am not a DEV, but have professionally been in IT for 20 years...so I use novice loosely here...
First, know why you're getting your CPUID:
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
Don't forget to BACKUP!!
Second, select which ROM you want on your tab, I recommend putting a couple on the MicroSD card so that you can test them. DON'T INSTALL ANYTHING, JUST PICK A COUPLE OF ROMS AND PUT THE ZIPS ON THE SD.
Don't forget to BACKUP!!
Third, follow the steps in the post that MD listed, read twice, run once...
http://forum.xda-developers.com/showthread.php?t=1622425
Don't forget to BACKUP!!
Fourth, flash one of the ROMs you chose previously while in recovery. Can't give you steps on this because they are all different unless you're just using the option in step 4 of the above post (stock w/ root)
Don't forget to BACKUP!!
Fifth, not sure if you can OC the stock w/ root or not, but if not pick a custom ROM and test several, they're all great, and see what fits your needs best. I use Flexreaper Extreme and love it, posted below, but look at ALL of them and find the one you like best, they're all GREAT! We have great DEVs here.
http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1
Don't forget to BACKUP!!
Good Luck, Have fun, and did I mention to make sure you Backup before each step so that you can get back to that point if you run into issues, and make sure you write down or put in a text file on a different device your CPUID...both very important.
Good luck again!
-DB
Thanks everybody for the info but I think I'll be staying on HC for now. The linked threads are the problem I mentioned in the OP. If you look at those threads with novice eyes they are incredibly hard to follow. Not sure why I cant find simple instructions but I do appreciate everyone's help. Maybe somebody will come up with a guide for dummies. Until then I guess I'm stuck with HC. Thanks again for the info.
Mate, it can be daunting even to experienced flashers...
My advice, go to this thread - http://forum.xda-developers.com/showthread.php?t=1622425
This has been cleaned up to make it easy to understand...
I use the manual method to go to apx mode but each to their own...
Now, follow each step. Make sure each step has been followed EXACTLY. Don't skip ahead or you will regret it, sooner than later...
If you have a doubt, go back a step.
Good idea to read through to the end first, especially the bit about checking you sdk...
Good luck....
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
realityrat said:
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
Click to expand...
Click to collapse
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Moscow Desire said:
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Click to expand...
Click to collapse
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
realityrat said:
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
Click to expand...
Click to collapse
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Moscow Desire said:
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Click to expand...
Click to collapse
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
realityrat said:
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
Click to expand...
Click to collapse
I zipped 4 apx packages for your 500. They have the ICS Booltoader and different recoveries. Unzip them to the same folder as your installation package.
http://www.4shared.com/zip/9TE6rTH-/500Bootloader_package.html
Yes, after you finish the bootloader/recovery installation process, turn tablet off. Press and hold Vol- and PWR till you see 2 lines of text in upper left corner, then release both. This will be your recovery menu. From here, you need to follow the instructions from the Rom page where you got your new Rom for the installation. Pretty simple really.
Also, I can't advise you on which recovery to use. I haven't tried the public recovery or TWRP yet.
MD
Thanks MD. Got the files downloaded. I'm gonna read over the threads a few times and make sure I havent missed anything and I also want to research some of the ROM's available. I'll probably give it a try in the next few days. Thanks again for all your help.
**UPDATE**
After reading the threads multiple times and following the instructions carefully I am now running ICS 4.0.3 with updated bootloader!! Everything went fine with only a couple problems that I was easily able to overcome. I'd like to address those problems so if anybody else has problems, 1: when entering the sbk its important to note that the spaces between the sets of numbers ARE needed, and the 0x at the beginning of each set has to be typed with a lowercase "x". 2: I used ezterry ICS 1.031.00stock- full root with busybox, and more tweaks and a500 public recovery. Following the instructions for this ROM I used the "clean up tablet" option in recovery. This DOES NOT do a full data wipe. So first boot had my custom boot animation and all my other apps and settings still there. ICS didnt like this and kept forcing reboots. I had to do a full data wipe and all is good now. I'm on ICS rooted stock and OC'd and loving it. Thank you all for your help, without your input I dont know if I would've tried this but I'm glad I did and I really appreciate everyone taking time out of their busy schedules to help some guy in NY get some ICS love. Thank you all again!
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.