Related
I have seen a lot of unfinished info on UNROOTING so rather than see a bunch of people stuck like I was last night I thought I would toss a little guide together for everyone.
I take no credit for any guides I post just pitching in, if I help you CLICK me a THANKS!
download the asus firmware from here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
extract the blob from the zip file and put it in your adb folder located at something like:
AndroidSDK/platform-tools/
as you did to root the device.
open cmd promt window type the following and return after each.
\cd
\cd AndroidSDK\platform-tools\
adb devices
*adb your device make sure it is hooked up and id'ing your transformer.*
adb push blob /data/local
adb shell
*at the # type the following*
dd if=/data/local/blob of=/dev/block/mmcblk0p4
*wait a few mins to be safe*
now reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob” file. this will remove the clockwork recovery and put your tablet into BOOTLOOP this is ok.
----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Now that your tablet is stuck in a boot loop, put on the root of the micro sd card on your computer-> the update normally found in the asus/update/ folder from the firmware zip you download from asus. I used the .9 US update and it worked fine, you must then rename it to EP101_SDUPDATE.zip make sure you leave it a zip dont change the extension AND->make sure it is on the root of the card.
Now put your card in your transformer, hold the down volume and power till it prompts you in the upper left about wiping or booting to recovery**> let go and push up on the volume, which will load the factory recovery android with a box and a loading bar *** IF IT IS STILL CLOCKWORK RECOVERY THEN YOU MISSED SOMETHING START OVER DO NOT CONTINUE***> it will begin to flash the update do not bother it turn it off or anything else will take up to 10 mins to complete. it will restart and you will see the bar load again on boot up then it will boot to the asus logo and then to the homescreen and your good.
-Ian
Faved for later use when INeed to RMA
Sent from my Transformer TF101
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Thanks for this. I have been holding off trying to root my Tablet until I had some clear indication that there would be a "way back".
I will PM you a link to V8.2.3.9 US Firmware as soon as it's done uploading to MegaUpload (Aborted as someone beat me to it)
I haven't found a need to root my TF yet as all I need for it is running pretty smoothly.
My phone on the other hand gets flashed with a new ROM every few days.
Great to know that I can go back if I do root one day. Thx
I get to this point...
ianandamy said:
...let go and push up on the volume, which will load the factory recovery android with a box and a loading bar...
Click to expand...
Click to collapse
See the box with a loading bar for about three seconds then the screen switches to the image of the android robot logo and an exclamation point within a triangle. I think its because I accidentally wiped my data last night when I was trying to fix the boot loop issue. I'm about to give up on this one...
Edit: Hey it works great, just make sure you don't add a .zip extension to the E101_SDUPDATE rename.
Big Thanks to ianandamy this works great! Got it up and running. The only problem is that I am being prompted to enter a password in order to get it to the homescreen...The second problem is that I never had a security password in order to access the tablet. I have a feeling this has to do with it being rooted by the previous owner before I purchased the tablet. Would the settings return to how he customized it pre-root? If so the password the tablet is asking for would be the one he set before I ever owned the tablet. How do I get around this?!
worked great, and like the profile pic
Added to ultimate thread. Nice job.
isdnmatt said:
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Click to expand...
Click to collapse
Can someone host it and pm me a link to post
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
isdnmatt said:
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
Click to expand...
Click to collapse
GREAT!
I've extrapolated the WW version with that http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
I'd do it, but I'm lame and don't have a linux box or VM setup .. that and I sold my eeePad to pay for vet bills... something about 'daddy save the puppy' is haunting me now.
P.S. Thanks for the info, just trying to save time if this is possible
sirmx said:
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
Click to expand...
Click to collapse
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Segnaro said:
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Click to expand...
Click to collapse
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
StirCwazy said:
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
Click to expand...
Click to collapse
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Segnaro said:
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Click to expand...
Click to collapse
Sorry to be a bit pesky here, but just want to be real sure: Based on ROM work I've done on my Android phone, unrooting is not the same as going back to a stock ROM. Actually the reverse is true: you can apply a stock ROM< and it will effectively unroot the phone.
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
ewingr said:
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
Click to expand...
Click to collapse
Yes, and after a factory reset it would be like when you just took it out of the box.
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
b1ackplague said:
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
Click to expand...
Click to collapse
Yes, I went from 3.1 direct to .9 without any issue.
I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.
You can get the update in the "Just got an OTA update" thread.
Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk
...................
martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...
for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.
TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk
Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...
Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.
None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116
Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.
Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.
OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.
OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably
ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)
Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.
Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.
mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now
OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?
still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?
turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.
Did you manage to get this working?
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.
redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)
MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.
Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2
Hey sorry i am new to the forums not new to rooting phones but i guess a tablet is all new ballgame i just received the asus transformer tf700t on ebay and tried to root it and it wont root as after i click into RCK it goes to installing system upate and then the red triangle android guy shows up saying error (i guess i cannot recovery mode the device either)
ok i was able to root my device but i am unable to install custom roms as my recovery boot im assuming is corrupt
Please note as i received it this way
Try this:
Boot Loop/No Boot Version (Can also be used to downgrade but always backup all apps and data.)
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
ASUS - Tablet & Mobile
The zips are under Tablet(your model), Downloads/Support. then under Android.
Also, they removed the 4.2.1 zips from their website. Here are Mirrors.
TF700 Zips (10.6.1.14.4)
Stock 4.2.1 US
Stock 4.2.1 US Mirror
Stock 4.2.1 WW
Stock 4.2.1 WW Mirror
Stock 4.2.1 TW
Stock 4.2.1 TW Mirror
I'll explain what your seeing a little bit more. The android guy on your back IS the stock recovery, it is not an interface. 10.6.1.14.4 is your your android version. 4.2.1 is the base, 10.6.1.14.4 is the package that ASUS creates and names it, so nothing is incorrect. Just try this method and it should get the tablet up and running.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Try this:
Boot Loop/No Boot Version (Can also be used to downgrade but always backup all apps and data.)
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Also, they removed the 4.2.1 zips from their website. Here are Mirrors.
I'll explain what your seeing a little bit more. The android guy on your back IS the stock recovery, it is not an interface. 10.6.1.14.4 is your your android version. 4.2.1 is the base, 10.6.1.14.4 is the package that ASUS creates and names it, so nothing is incorrect. Just try this method and it should get the tablet up and running.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
i didnt everything but as soon as i select RCK it says installing update and then it says error the tablet is working fine other than the recovery mode not working
darkcroc said:
i didnt everything but as soon as i select RCK it says installing update and then it says error the tablet is working fine other than the recovery mode not working
Click to expand...
Click to collapse
Error how? The android guy laying of his back? That is not an error. The stock recovery has NO interface, so you CANNOT go INTO the stock recovery. All the stock recovery can do is update if you have a ROM on your sdcard.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Error how? The android guy laying of his back? That is not an error. The stock recovery has NO interface, so you CANNOT go INTO the stock recovery. All the stock recovery can do is update if you have a ROM on your sdcard.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I dont know bro it shows the android guy on his back with the red triangle and underneath him it says "Error!" i don't understand why
darkcroc said:
I dont know bro it shows the android guy on his back with the red triangle and underneath him it says "Error!" i don't understand why
Click to expand...
Click to collapse
Then you didnt follow the instructions/naming properly. Try renaming it on a PC first then put it on the MicroSD card and doing the process. Also make sure you have the correct SKU and name down.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Then you didnt follow the instructions/naming properly. Try renaming it on a PC first then put it on the MicroSD card and doing the process. After make sure you have the correct SKU and name down.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
A common error is to download the file and rename it without extracting it first. Its a zip in a zip. The one inside is the one you need to rename, not the one you downloaded.
The other common error is not having FAT32 format for your MicroSD card, which is the Removable one, not the internal sdcard. When you get a MicroSD card out of the box, the standard format is exFAT which does not work for recovery (flashing ROMs or firmware).
The dead android means that your recovery cannot find the update.zip file in the root directory of your MicroSD card.
Tylorw1 said:
Then you didnt follow the instructions/naming properly. Try renaming it on a PC first then put it on the MicroSD card and doing the process. Also make sure you have the correct SKU and name down.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
well im sorry to say this method is not working i did everything u said to do and its not getting fixed bro and my micro is a fat32 just checked
darkcroc said:
well im sorry to say this method is not working i did everything u said to do and its not getting fixed bro and my micro is a fat32 just checked
Click to expand...
Click to collapse
well i did everything manually for the recovery and got twrp to work and rooted with motochopper so alls well that ends well thanks guys but i got it done on my own
darkcroc said:
well i did everything manually for the recovery and got twrp to work and rooted with motochopper so alls well that ends well thanks guys but i got it done on my own
Click to expand...
Click to collapse
That's great! Can you briefly outline what you did differently to make it work for you? It may be helpful for the "next guy".
elfaure said:
That's great! Can you briefly outline what you did differently to make it work for you? It may be helpful for the "next guy".
Click to expand...
Click to collapse
Looks to be he installed a custom recovery. However in the OP, he never mentioned of being unlocked. I thought he was fully stock, so it is an entirely different situation. So my answer to him was for people who were purely stock.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Looks to be he installed a custom recovery. However in the OP, he never mentioned of being unlocked. I thought he was fully stock, so it is an entirely different situation. So my answer to him was for people who were purely stock.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Gotcha. But he did mention in the OP that he was trying to install a custom rom, and that can only be done if unlocked. But it also looks like he added that statement as an edit after the OP. Weather or not he knew that is unclear. Makes it hard to help someone when you only get partial info from the user about their problem I agree.
elfaure said:
That's great! Can you briefly outline what you did differently to make it work for you? It may be helpful for the "next guy".
Click to expand...
Click to collapse
well i rooted the tablet with motochopper then downloaded goo manager into it after word i downloaded the Twrp Blob file (most recent) and then downloaded terminal emulator and typed su for super user and installed the blobs file threw it and rebooted and flashed cw rom onto it to verify it worked and wah la and yes i did unlock the device sorry for not inputing it (it wasnt working after i unlocked it either so thats when i decided to install custom recovery)
darkcroc said:
wah la
Click to expand...
Click to collapse
You mean "voilà"? </grammar nazi mode>
Your summary makes it look easy, which it would have been if you had supplied full information timely and upfront. Meh.
darkcroc said:
well i rooted the tablet with motochopper then downloaded goo manager into it after word i downloaded the Twrp Blob file (most recent) and then downloaded terminal emulator and typed su for super user and installed the blobs file threw it and rebooted and flashed cw rom onto it to verify it worked and wah la and yes i did unlock the device sorry for not inputing it (it wasnt working after i unlocked it either so thats when i decided to install custom recovery)
Click to expand...
Click to collapse
Sorry i hav the same problem. But can you tell me more specificity what code you typed in?
ivansong said:
Sorry i hav the same problem. But can you tell me more specificity what code you typed in?
Click to expand...
Click to collapse
Can you be a lot more specific please?
You have what problem? You did what and want to accomplish....??
And always mention what bootloader/recovery/rom you are currently running.