[Q] Rooted with RazorClaw - Eee Pad Transformer Q&A, Help & Troubleshooting

Quick a few questions that hopefully someone can answer.
I have just rooted my TF using Razorclaw. So where do I go from there. I'm pretty sure I need to back something up. I don't think I need a custom rom at this stage as all I really want to do is overclock it at this point so I'm happy to stick with the stock rom if it can be done on that.
I have installed RecoveryInstaller using Asus Sync, but I don't want to flash anything further until I know what I need to backup (and is a 2GB Micro SD card big enough to do it). I'm not particularly bothered about losing any apps I've got from the Market as they are all free ones anyway. I'm more concerned about system files so I can do a recovery.
What does being rooted mean for future OTA updates from Asus. Will I now need to wait for a "modded" version of the the update and where will I stand when ICS arrives. I'm reasonably competent and have searched, but most threads seem to pertain to TF's before B70.

hello, i too have rooted and flashed today, i rooted then used gnfabio recovery installer app, then flashed revolver rom, pure class, as for updates, i so far cant understand what the fuss is, the custom roms get updated aswell, so to me it doesnt matter.
Sent from my Transformer TF101 using Tapatalk

Search the forums!
Sent from my HTC Inspire 4G using XDA App

Well I installed CWM and did a backup, so I now have a backup on my MicroSD card with cache, data, system img files, and a nandroid MD5. Is it ok to copy those files from the MSD card to my PC and wipe the card or is it best to just leave it alone.
I also have a file called recoveryblob on my internal SD. Is this something I need to backup, I only ask because I don't recall seeing it there before, although I don't often go into the file system.

cavsoldier19d said:
Search the forums!
Sent from my HTC Inspire 4G using XDA App
Click to expand...
Click to collapse
I have searched the forums, but as I had said, most of the threads appeared to be about methods prior to Razorclaw which used nvflash which all said not to be used with B70's, etc.

Cmdrx3 said:
I have searched the forums, but as I had said, most of the threads appeared to be about methods prior to Razorclaw which used nvflash which all said not to be used with B70's, etc.
Click to expand...
Click to collapse
I suggest you read some of the pages of the RazorClaw thread. There's a lot of similar questions in there. Even though I have a B60, I read the thread anyways just to see what it's about and what problems/questions people have with it. http://forum.xda-developers.com/showthread.php?t=1345049
As for updates, if you decide to go to a custom ROM, it seems most of the developers stay on top of the updates. All "custom" roms are taken from ASUS updates, so don't expect to see an update until ASUS releases an update. If you want to stay relatively stock but keep root and CWM, check out daoist's releases. He's been releasing a repackaged stock room which removes the recovery flash from the stock ROM and also makes it so you keep root. Usually he seems to have this released either the same day as the ASUS Rom or within a day or two. Here's the most recent release. http://forum.xda-developers.com/showthread.php?t=1341533

Related

Kernel/ota questions

I've successfully recovered my tablet using this method. I was trying to update my TF using the batch script method and somehow managed to flash an outdated kernel. I know this because Asus tech support told me that was the reason my TF wasn't receiving the ota to 3.2. However, Asus tech support also told me that I could flash a new kernel by downloading the source code onto my tablet, then the TF would automatically recognize the [.rar] file and install my new kernel; which didn't work out as you might imagine.
I am now on official 3.1 8.4.4.11.and my kernel is v 2.6.36.3-00011-g3eb19ex And I can't get the OTA update. At one time I had official 3.2 [after previously flashing stock 3.1] but decided to try to root when I found out Netflix wasn't officially supported like the EEE pad site says it does.
Every time I try the batch script method, I end up stuck on the eee pad logo screen. Adb is working as well as apx drivers. Ultimate goal here is stock 3.2 rooted with netflix, but at this point I'd settle for stock official 3.2.
Any ideas? Tia
You may get help if you post your QUESTIONS in the correct forum.
This is the development forum....not Q&A.
Sent from my Jailbroken iPhone 4 using Tapatalk.
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
you could try the zip file from the thread titled [OTA]Stock 3.2 zip file
And +1 on wrong section. This is not related to developing a new ROM or features for the Eee Pad.
I'm trying to avoid flashing CWM, that's where I end up bricking it.
jdmnash said:
I'm trying to avoid flashing CWM, that's where I end up bricking it.
Click to expand...
Click to collapse
I would suggest you to try Nvflash. it is the easiest way to root that tf.
I think the relationship between nvflash and the TF is complicated.
There are a few bootloaders out there, including the one used by custom roms, as well as the 4 stock ones.
My theory is that the kernel images in the boot and recovery images have to match the bootloader that is on the TF.
Throw in the fact that the bootloader is only written using the nvflash --create command or during the OTA update, and we have TFs with all kinds of different bootloaders going around that won't match what people are flashing. I think this is why CWM breaks whenever there is a stock OTA that rewrites the bootloader. I think most people brick trying to go back to stock from a custom rom. Going from stock to custom usually isn't a problem because the compatible bootloader is flashed in the rooting process.
Is this the first time we've seen an completely unlocked bootloader on Android?
sent from my cyanogen(mod) vision
jdmnash said:
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
Click to expand...
Click to collapse
No. Android Development is for "DEVELOPMENT" does this thread have any kind of release? No.
That's why there's a sticky thread that says,
[REF] SEARCH BEFORE POSTING!! All Questions Go In The Q&A FORUM!!
Originally Posted By: mskip
Click to expand...
Click to collapse
ok folks i get it. I'm sorry. Is there anything I can do right now about accidently posting this in the wrong forum? Please forgive me. Mods feel free to move the thread or ban me or both. Whatever the normal punishment is.
Use the NVFlash unroot method here:
http://tabletroms.com/forums/showthread.php?1071-Asus-Transformer-NVFlash-Stock-3.1-Recovery-Roms
That will get it back to stock everything with 8.4.4.5. Then, you can manually install 8.4.4.11 with the download on the Asus website. After that it will recognize the OTA update to 8.6.5.6. Once you've done all that, use the Batch Script for a quick root, and you're done. I did this today. As long as you follow all the steps, it's a breeze.
I don't think it will recognize the OTA update to 8656. Roach's update will work, but not the stock update.
sent from my cyanogen(mod) vision
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
My OP is not very clear, but that is exactly the steps I've followed to get to where I am today. I've given it 2 days to detect the new update and i've got nothing. I'm currently sitting on stock 8.4.4.11 waiting for the OTA.
kingwp1 said:
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
Click to expand...
Click to collapse
How did you root before and what were you running before you went back to stock 8445?
sent from my cyanogen(mod) vision
stock 3.2. I was trying to get rooted 3.2 to get netflix
jdmnash said:
stock 3.2. I was trying to get rooted 3.2 to get netflix
Click to expand...
Click to collapse
Did you ever make a backup with CWM when you had 3.2?
no it was stock 3.2 firmware/recovery
I'm making progress. I'm now on rooted 8.4.4.11... still trying to get to 3.2

Root question before I start

I have a B60 transformer with 3.2.1 HTK75_US_epad-8.6.5.13 on it.
From the reading I have done I should be able to use the 7.1 universal root kit.
My questions are
Where can I get the stock ROM to unroot it and set back to stock if I need to?
Other than updating CWM after using the root kit is there anything else I need to do.
I have rooted my EVO 4g phone and swapped out the rom many times so I'm hoping it is a lot like that but I'm new to this and just do not want to make any mistakes. I have tried to search and read as much as I can but there is tons of info on the forum and lots of it does not match or is very old.
Sorry if this is a newbee questions but I have to learn somewhere.
If you have links please post them and I will read that info.
Thanks
Brandon
ASUS has the stock roms on their website, but the 8.6.5.13 probably isn't available yet as a full rom, just an OTA. There are older versions available, such as 8.6.5.9, but I'm not sure if you can flash to an older version with the built in updater. Once the full rom is released, chances are better you can update back to stock. With nvflash and your B60, you can flash anything you want.
I haven't tried it, but I think that that root tool will let you back up before you flash.
gee one said:
I haven't tried it, but I think that that root tool will let you back up before you flash.
Click to expand...
Click to collapse
Yes, it will ask you if you want to backup before you root but it tells you it could take 4 to 5 hours.
I have rooted and unrooted with this below method many times. I don't need to go looking for a stock rom...it simply reverses the procedure as far as I know...look into it...now if you go for a custom rom your on your own.
http://forum.xda-developers.com/showthread.php?t=1198303
Thank you everyone for your answers, I did the full backup which did not take long as I had done a reset before I started and wiped everything.
The root was painless and is done.
For now I think I will stay with the stock ROM but I'm now going to look for a Kernel to OC it to 1.2-1.4 if I can.
Thanks again
Brandon

[Q] Questions: Upgraded my MZ604 UK WiFi Xoom to US 3.1-ICS 4.0.4

I put off the upgrade in the hope the UK stock update would come but eventually changed my mind as all posts seemed to say ICS was alot better.
Have a few things I would like people to comment on.
Used the LAIOT tool which made it relativly straight forward. Few hiccups but got there.
1) Part of the process was to ROOT.
ICS installed Titanium Backup it says its not ROOTED.
2) I'm surprised at how stripped down the US stock ROM is in terms of bloat (which is good).
No stock file manager.
3) I must say I don't see any real benefit on the ICS upgrade and would be happy to be pointed to what they are.
4) Still unable to delete files from memory card.
5) I used Astro to backup my Pre-ICS xoom and hoped to be able to restore APPS but I assume this was just if the upgrade failed and I went back to HONEYCOMB as Astro doesn't see the files.
6) I read that boot-up speed was almost instant, but it seems to be the same albeit with a fancy video splash before screen up.
7) not sure if I need to relock bootloader or if I have already as part of LAIOT process. Too many threads and info.
Hi there. Without doubt. Ics is a lot better.
I am not sure your rooting we t well with custom ics rom. Here is the best rom with procedure for your xoom wifi.
http://forum.xda-developers.com/showthread.php?t=1400958
Sent from my MZ601 using Tapatalk 2
Hi
Sorry don't understand second line of your reply.
That ROM procedure assumes you have knowledge of recovery such as CWM which I don't unless with full instructions.
That thread is way to long to go through but glancing it seems some aspects are still reliant on info that Google hasn't released so the ROMs are incomplete.
My post says that with the stock from I really can't see change from Honey to ICS.
That being said then why would I then go to the TeamEOS ROM, I ask so as to be convinced not to disrespect.
cmorephotos said:
I put off the upgrade in the hope the UK stock update would come but eventually changed my mind as all posts seemed to say ICS was alot better.
Have a few things I would like people to comment on.
Used the LAIOT tool which made it relativly straight forward. Few hiccups but got there.
1) Part of the process was to ROOT.
ICS installed Titanium Backup it says its not ROOTED.
2) I'm surprised at how stripped down the US stock ROM is in terms of bloat (which is good).
No stock file manager.
3) I must say I don't see any real benefit on the ICS upgrade and would be happy to be pointed to what they are.
4) Still unable to delete files from memory card.
5) I used Astro to backup my Pre-ICS xoom and hoped to be able to restore APPS but I assume this was just if the upgrade failed and I went back to HONEYCOMB as Astro doesn't see the files.
6) I read that boot-up speed was almost instant, but it seems to be the same albeit with a fancy video splash before screen up.
7) not sure if I need to relock bootloader or if I have already as part of LAIOT process. Too many threads and info.
Click to expand...
Click to collapse
hey
if your looking for a decent ics experience id suggest flashing official cm9 details found here http://goo.gl/UmT44
also check this link http://goo.gl/yveok its a basic introduction on ics features - might help
p.s you dont need to relock the bootloader either - you dont want to go down that road - leave it unlocked for now

So you are all experts, what about newbies?(Root, Unlock, OTA etc..)

Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder

[Q] A700 rooting question

Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
ianrobbie said:
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
Click to expand...
Click to collapse
No problem. Seeing you are on JB, then you have a JB bootloader.
You need to go here http://forum.xda-developers.com/showthread.php?t=1953917
And download Vorbeths easyroot2.0. It's for the 700.
You have to unlock your bootloader first, which shouldn't be an issue for you. Easy instructions for that.
Then download his package to a folder on your PC. (not sure, but you may have to download each file individually) Open a command window (shift & right mouse click) and type in whatever his instructions say. Should be painless.
Make sure USB Debugging is turned on first in your tablet (Settings/Developer Options/USB Debugging), and make sure you have the Acer Drivers installed on your PC.
Then connect, wait 30 seconds, and run his batch file.
You should be ok.
MD
Oh yes, one more thing, once you unlock your bootloader, chances are you will not be able to get OTA. And the only way to re-lock the bootloader is to install a stock rom.
Thanks!
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
ianrobbie said:
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
Click to expand...
Click to collapse
No problem. I thought I mentioned it timed out in about 5 seconds These days I don't remember much
Yeah, I haven't looked at Vorbeth's script, so I don't know which screen he launches it from. With mine for the 701, you can be when the tab is running normal. No difference in the end result though
Happy Hunting!
MD
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
ianrobbie said:
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Moscow Desire said:
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Click to expand...
Click to collapse
So, just for future reference, how would I go about re-flashing the stock image? I'm assuming it's saved on the tablet in a separate partition?
I've decided to stick with the stock rooted ROM but would like to know how to re-flash for when Key Lime Pie and future updates are released.
And, seeing as how you haven't steered me wrong so far, I though I'd pick your brains one last time.
Hope you don't mind!

Categories

Resources