I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
xdatester11 said:
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
Click to expand...
Click to collapse
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Pretoriano80 said:
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
AFAIK the nvflash method doesn't work for TF700 and is possible that you really bricked your device... The only solutionn i can see is to flash a recovery in fastboot mod and flash the Asus stock from there,but if you can't even boot in fastboot then i don't see any other way to recover the device.
xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
attachment
NVFlash works with the TF700??? That's news to me!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
Sorry mate,but according to this --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/ <-- i don't think you will be able to use nvflash for recovery and it clearly states that you need to get fastboot working in order to use that method. (to get in fastboot mode press Volume down + Power and release the buttons when the message about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" wich means boot in fastboot mode).
P.S : Can you tell us why you had to mess with nvflash?That is the most advanced way to recover/backup the Transformer 101/201 series and you have really high chances to brick your device for good.
EDIT: I don't think someone here will be able to make a backup for you with nvflash...it will only lead to more bricks.
EDIT 2: Can you please tell us the name of the app that bricked your device so we can avoid other people bricking their device?
The app was transformer reboot recovery I think.
I only used nvflash because it was the only option left as the tab wouldn't work with adb or fastboot.
I guess I'll keep it as a paper weight.
xdatester11 said:
The app was transformer reboot recovery I think.
Click to expand...
Click to collapse
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
henbone11 said:
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
Click to expand...
Click to collapse
Yes,i also used that app with no issue,but one of the developers behind TWRP advised to not use it at all,because if for some reason your recovery gets corrupted (that app send a custom command to boot into recovery) the device will boot loop trying to get in recovery and without nvflash we don't have many options to recover from that.
"
KEEP AWAY from that app for the moment,just stick with the old good " Volume Down + Power and then Volume UP " method to get into recovery.
Same issues here as well
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
shasan2 said:
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
Click to expand...
Click to collapse
1The first step is to get your recovery back and working...here's a how-to:
1) Download the recovery from here
2) Follow the instruction on how to flash the recovery in fastboot mode
If the flash went good and you can get in recovery mode follow this steps:
1)Download the 9.4.5.26 firmware from Asus site (the SKU for your region)
2)Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3)Put the extracted zip to a MicroSD card
4)Insert the MicroSD card in your tablet and boot into recovery
5)Install the zip from recovery and restard when done
If all goes well your tablet will be again up and running
Ray of Teamwin
:good::good::good:Thanks a million, seeing the team win screen relieved me. The only problem is i cant boot into recovery (teamwin screen is visible)through the wipe data mode, wherein everything is wiped and it reboots automatically. I cant seem to force the table into recovery without this is there any fastboot command which i can use to force the tablet into recovery.
Need Stock Boot, Recovery, System img
Still no luck with the recovery mode. Every time i wipe the device it automatically reboots. I was wondering if i could get hold of stock recovery, boot and system .img files so that i can push them or flash them through fastboot.
i tried using the blob pack and unpack but i cant seem to get around the blob header thing.
Anyone to spare me stock .img files
End of Infinity
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
shasan2 said:
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
Click to expand...
Click to collapse
There's a thread (I can't find it again) that talks about this "Reboot into Recovery" app and how it might be bricking TF700T's. This guy wrote in, because he could not get to the recovery menu at all any more and could not do the "PWR+VOL-DOWN" combo. Nothing would happen. Maybe this was the thread, I don't know.
An XDA Mod in another thread said the app *might* be bricking them, but was waiting for confirmation before posting that it does.
I wish to confirm that IT DOES BRICK TF700T's! IT DOES!!!
And there is NOT A DAMN THING you can do! Your PC will not even recognize that the device is connected! You cannot get to the little icons to pick USB Mode, or whatever it's called.
This is the free app, not the other pay one in the Market. I don't know about that one, but this one is called, "Reboot into Recovery" and if you can somehow find that thread if I don't and just copy my post there, I would really appreciate it! I just want to warn people, ya know?
Also, using ANY of the "ROM Managers", whether it's CWM's, or GooMgr's, will take away all ability to get to a recovery menu at boot, at all! The device will still work and everything and boot to your Home Screen and everything. It won't be bricked like the app listed above does to it, but it will take away your recovery menu altogether and the PWR+VOLDOWN thing won't work any more either.
You can Unlock the TF700T, you can Root it. But you cannot use ANY ROM Mgr and you cannot use that Reboot into Recovery app.
But the app I listed above WILL BRICK YOUR DEVICE BEYOND ANY RECOVERY METHOD!
Please pass this on, I am confirming the experience. It doesn't matter if others say it worked for them. It is bricking them at random and even one of the guys who reviewed the app (diff guy than the one who posted here) said it bricked his. It is happening! It is not the user messing up! I did do it right!
Thanks!
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No offense, but I think a huge problem in forums, is that people don't read carefully.
1) I think you are referring to the paid app. Read what I said about that.
2) You're saying what you're saying, in a thread started by a guy who had a running device and who didn't after using the app.
3) I said that it bricks them AT RANDOM.
4) Another problem with forums, is that whenever someone has a problem, A LOT of users want to post responses that ignore the users' experience and they want to act like the problem doesn't "really" exist. If multiple people are posting the same problem, then IT DOES EXIST. It just doesn't exist for YOU! But something working for you, does not mean it works for everybody and it does not mean there is a problem with their device, nor that they did something wrong.
5) And yet another problem with forums, is that when someone like me points things like this out, many users will respond by jumping on me, instead of those who try to make the guy feel like he's hallucinating and who, instead of trying to help him out, or just keep their mouths shut if they have nothing helpful to offer, think the right thing to do is to argue with the person having the problem.
These forums are for help and information. If someone has neither to offer the person, or at least warn others, then why are they responding at all? And why would anyone defend someone doing that?! It's ridiculous! But that's what typically happens, especially in XDA doe some reason (lots of snobs here, who like to prove they are, by doing as I just described).
The bottom line is, you do not run the app I talked about and even if you did, that does not take away from the experience that some have had and the best thing, is to avoid the app, because there's a risk involved and there is no recovery from it. I decided to warn people. You decided to tell us that we're hallucinating and that people should use the app. You did not carefully read what I wrote, or you would have checked the Market to see what the name of the app that does not have a pay version is. The one I am talking about does not.
I will tell you this. I am posting this from my laptop, because I had to return my Tablet and have a replacement shipped and now I have to spend a few days getting it all set up again the way I had it.
Avoid the ROM Mgr apps on the TF700T. And avoid the free app called "Reboot into Recovery". A user told me about it for my device, who had seen it used successfully. However, if you look at the reviews in the Market, you'll see that one of them says it bricked his *WORKING* *FINE* tablet and this thread right here has told you about two more. So just believe it and don't criticize, huh?
Okay Mods, feel free to jump on me again, just like last time.
I agree with many of your points, Zeuszoos, and thanks for pointing that out, but I believe there are many senior members at XDA willing to help if they have knowledge/abilities to do so, that's been my experience so far and hopefully it can be yours too. Of course, a little SEARCH won't hurt before posting one's problem, as you reasonably mentioned yourself
"reboot to recovery" has been in my apps STICKY thread in the sections "apps to avoid" (RED) for quite some time now after first reports of bricking users' devices started popping up and I believe it has helped some users who did a little reading before clicking...
I have rooted on other devices and done this in the past. This time it seemed to be going very well. I hit a snag and was hoping you guys could help.
I followed this thread http://forum.xda-developers.com/showthread.php?t=1762709
I got the the device unlocked.
I then ran ez unlock and it unlocked.
I then ran ez recovery and had it load CWM 6.0.1 and it worked.
I then opened up EZ recovery and hit the reboot recovery, and nothing happened.
Thank you for the help!
Did you click the flash button in ez recovery for cwm6.0.1 before hitting the reboot recovery? Just checking since you didn't clarify in post.
Did ez recovery ask to allow root when you started the app?
dark_system said:
Did you click the flash button in ez recovery for cwm6.0.1 before hitting the reboot recovery? Just checking since you didn't clarify in post.
Did ez recovery ask to allow root when you started the app?
Click to expand...
Click to collapse
I did click the flash button first, and I got recovery flash successful. \\
I dont remember if it asked me to allow root when i first started the app.
EDITED
I re installed it and it did not ask for Root
You could try to power off your phone and try to get into recovery via volume up + home key + power button hold.
Might need to run the root script again.
I'm new to this phone so don't have many ideas. Hopefully someone else will come along and offer more help.
Rooted, Unlocked, Flashed, Overclocked Galaxy S III
dark_system said:
You could try to power off your phone and try to get into recovery via volume up + home key + power button hold.
Might need to run the root script again.
I'm new to this phone so don't have many ideas. Hopefully someone else will come along and offer more help.
Rooted, Unlocked, Flashed, Overclocked Galaxy S III
Click to expand...
Click to collapse
I tried that but cant seem to get it to work. I know in an older CWM I would see update from zip option and be able to find the zip and then use that to load ROM. This time its not an option.
OK....
So I had the gapps and rom on my device and not the SD card. I moved both to the SD card, turned the phone off and then used the 3 buttons to turn it on.
1. I got a message using a custom rom can hurt your phone etc... continue
2. Then it said downloading and do not turn off target.
I never even made it to CWM screen. Umm is this a good thing? Sorry my last device was the original EPIC and this is very different from the CWM and rooting etc.
With my limited experience with this device, this is what I would do.
Use odin to flash phone back to factory stock, there are guides on this.
Then start again.
There might be other ways to deal with your issues, but it doesn't sound like something is right. Sorry if this isn't what you wanted to hear, but since no one else has chimed in, I would start fresh.
Sorry I can't be of any real help.
Hey Dark thanks for the help, I did it all and now CWM is working.. normally. Thanks again!
Hey everyone, sorry if this has been asked already, I wasn't able to find what I was looking for with the search. I've been trying to unlock and root my Motorola Xoom (WiFi Canadian model, should be the same as the American MZ604, yes?) and haven't had any luck flashing a recovery that works. Unlocking the bootloader went fine as far as I can tell, but when I try and flash a recovery (tried CWM and TWRP) it comes up with a line of text in red saying something about a partition recovery, then 2 lines about flashing recovery and being successful. When I try and boot into recovery though to continue rooting the Xoom, I get the android laying on its back with the caution triangle over its chest. Any suggestions or ideas as to where/what I'm going/doing wrong?
Anyone? No one has had a similar problem to what I have been experiencing?
After you flash the new recovery and reboot the Xoom, it is very important to not allow it to boot into Android. If it does, Android will detect the foreign recovery and remove it.
When the Xoom reboots, press (don't hold) the volume down key to get a line of text about entering recovery, and press volume up to confirm.
This time you should see your shiny new recovery.
Sent from my GT-I9300 using xda app-developers app
As far as I know, this is what I have been doing, but I will give it another go around and see what happens. Thanks for the reply
EDIT: That worked! Thanks very much for the tip, I was using the AIO tool and it would automatically reboot on its own without trying to take it to recovery. This would be where I was going wrong.
Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!
Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.
1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app
Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]
I am trying to root my TF700T as it has become unbearably slow and I am sure that a rooted tablet and lagfix would do wonders. Can't understand why such a great tablet and powerful processor would take so long to perform very average tasks.
I am having massive dramas getting root. I have looked at the web and most sites recommend running Motochopper, which I have done, however it fails and I am left with Super Su that fails saying that the binaries are not available.
Does anyone know where a root file for the TF 700T running Android 4.2.1 that has the drives included and the files necessary to obtain root.
Sorry if this is the millionth user asking for the same thing. Please have patience with me, I am apologise for the repetitious request.
Thank you ...
rosse912003 said:
I am trying to root my TF700T as it has become unbearably slow and I am sure that a rooted tablet and lagfix would do wonders. Can't understand why such a great tablet and powerful processor would take so long to perform very average tasks.
I am having massive dramas getting root. I have looked at the web and most sites recommend running Motochopper, which I have done, however it fails and I am left with Super Su that fails saying that the binaries are not available.
Does anyone know where a root file for the TF 700T running Android 4.2.1 that has the drives included and the files necessary to obtain root.
Sorry if this is the millionth user asking for the same thing. Please have patience with me, I am apologise for the repetitious request.
Thank you ...
Click to expand...
Click to collapse
Why don't you unlock and install a custom rom to get the full benefit? Rooting won't do that much to give you back speed.
If you want to get some performance back on pure stock. Do this:
1. Boot into the boot loader by holding down volume down and power
2. On rck icon hit vol up
3. Hit volume up down and power until a menu pops up
4. choose wipe cache
5. reboot
I don't know why it works but it will buy you back about a week until it slows down again. Then just do it again.
Groan ...
sbdags said:
Why don't you unlock and install a custom rom to get the full benefit? Rooting won't do that much to give you back speed.
If you want to get some performance back on pure stock. Do this:
1. Boot into the boot loader by holding down volume down and power
2. On rck icon hit vol up
3. Hit volume up down and power until a menu pops up
4. choose wipe cache
5. reboot
I don't know why it works but it will buy you back about a week until it slows down again. Then just do it again.
Click to expand...
Click to collapse
There must be something wrong with my tablet or maybe it is me??
I have tried to follow your instructions here and I can get the where the RCK icon is on the screen, but when I hit the volume up key, the tablet starts installing something and ends in a green android fallen over on his back with ERROR written underneath him.
I would love to be able to unlock, or root or install a new rom, but so far everything I do fails to work on this device.
Can someone please direct me to a location that is suited for a TF700T running 4.2.1 where I might try these procedures and actually has the relevant zip files to enable these installations.
I really like this tablet, however it is a great disappointment the way things are and if possible I would like to unleash the power under the hood.
Thank you
Ross
Have a read of the sticky topics in the TF700 general forum. And ask questions if you get stuck.
It's not that hard really.
Make sure you are on latest Asus stock rom
Unlock using Asus tool on tablet
Install twrp from PC
Flash ROM
Hardest part is getting correct drivers for PC but there are guides out there.
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Thanks
sbdags said:
Why don't you unlock and install a custom rom to get the full benefit? Rooting won't do that much to give you back speed.
If you want to get some performance back on pure stock. Do this:
1. Boot into the boot loader by holding down volume down and power
2. On rck icon hit vol up
3. Hit volume up down and power until a menu pops up
4. choose wipe cache
5. reboot
I don't know why it works but it will buy you back about a week until it slows down again. Then just do it again.
Click to expand...
Click to collapse
sbdags said:
Have a read of the sticky topics in the TF700 general forum. And ask questions if you get stuck.
It's not that hard really.
Make sure you are on latest Asus stock rom
Unlock using Asus tool on tablet
Install twrp from PC
Flash ROM
Hardest part is getting correct drivers for PC but there are guides out there.
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
OK Thanks for your reply.
I will continue to see if I can get my head around this stuff.
Thanks again for your time.
Ross