Database Info

Need help rooting and/or flashing twrp

Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.

Shad0w32 said:
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Click to expand...
Click to collapse
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.

cmendonc2 said:
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
Click to expand...
Click to collapse
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance

Shad0w32 said:
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Click to expand...
Click to collapse
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.

graphdarnell said:
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
Click to expand...
Click to collapse
For first, I downgraded my device, so I could root it with motochopper. Then I flashed recovery with the way explained here:http://forum.xda-developers.com/showthread.php?t=1845377
Now twrp seems to be working, i can start it, but it cant mount anything, so i cant flash anything from the device. Both 2.5 and 2.4.4 does this. Goo manager cant find a recovery for this device, so i cant use that either. Fastboot still cant see my tab. Im on windows 7, with proper drivers

Nevermind my stupidity, I installed the wrong recovery, not the one for the 4.2 bootloader. By now I'm a proud owner of a tf300t with cyanogenmod on it Thank you both though, for trying to help

[Q] gooManager and twrp

I was toying with unlocking my tf700t to install cromi-x and installed gooManager, i kind of accidentally installed the openScript recovery BEFORE unlocking my device (it is rooted), now that my warranty has expired, i have unlocked the device, but when i try to use twrp i get the dead android, when i try to reinstall it from gooManager, by telling it to install the openScript recovery, it tells me "no recoveries were found for your device" how can i solve this so i can go ahead and flash cromi-x??

basarix said:
I was toying with unlocking my tf700t to install cromi-x and installed gooManager, i kind of accidentally installed the openScript recovery BEFORE unlocking my device (it is rooted), now that my warranty has expired, i have unlocked the device, but when i try to use twrp i get the dead android, when i try to reinstall it from gooManager, by telling it to install the openScript recovery, it tells me "no recoveries were found for your device" how can i solve this so i can go ahead and flash cromi-x??
Click to expand...
Click to collapse
To use GooManager you need to have root. When you tried to use it to install TWRP before unlocking it silently failed. Unfortunately GooManager never reports a failed install.
Use the fastboot method to install TWRP - it's worth it to get fastboot working for trouble shooting purposes.
A shortcut or slightly easier way would be to use the "Minimal ADB Fastboot Tool" here from XDA. Just google it.
Edit: Sorry, overlooked that you were rooted. For some reason GooManager doesn't seem to work on our tablets right now - have read several posts about it....

berndblb said:
To use GooManager you need to have root. When you tried to use it to install TWRP before unlocking it silently failed. Unfortunately GooManager never reports a failed install.
Use the fastboot method to install TWRP - it's worth it to get fastboot working for trouble shooting purposes.
A shortcut or slightly easier way would be to use the "Minimal ADB Fastboot Tool" here from XDA. Just google it.
Edit: Sorry, overlooked that you were rooted. For some reason GooManager doesn't seem to work on our tablets right now - have read several posts about it....
Click to expand...
Click to collapse
thx for the input, i was working on going the adb/fastboot way, but didn't wanna go ahead before hearing from someone from here just in case, you know, just trying not to brick the thingy.
fastboot worked like a charm
had to do it on windows though as for some reason, woudlnt wanna work on linux.....(my soul died a lil booting 3 times in a month into windows )
weird thing is that gooManager did seem to work the first time.....before i was unlocked but not afterwards.
anyways, thanks for the help.

[Q]Stuck in bootloop with deleted OS, abd not working.

Hey all,
I have a big problem with my TF700.
I wanted to root my device after unlocking the bootloader through the app, but by being dumb I managed to delete the OS in TWRP (thought it was factory reset) and now I'm in big trouble.
The only thing the tablet loads now is the TWRP 2.2.1 recovery. (TWRP came with a root-package, I didn't install it myself.)
Since I can't load an OS that is apparently deleted, I'm stuck with using the (latest) SDK to get the stock rom back on the tablet.
The problem is, it doesn't work, at all. The device is recognised by my (Win7) PC and the 'adb devices' command gives me the ID and 'recovery'.
If I try to push the ROM to the Sdcard folder (or any folder, for that matter) It gives me a "protocol error" with no other explanation.
If I try to sideload it it is stuck on "Waiting for device".
I tried the 'shell' command, just to see what that does, but it also gives me an error.
Other commands can also give the the "error: closed" message.
Since both of those commands don't work, I can't get anything on this tablet, since I can't get this version of TWRP to mount an external (micro) SDcard, the option simply isn't there.
Can anyone help me with this, of has my tablet been reduced to an expensive paperweight?

That's the problem with packages - you don't really know what's in it...
What root package did you use?
You have a very outdated recovery installed. I'm guessing here, since you didn't post your bootloader version and that's the first thing we need to know!
Can you still get into the bootloader?
Boot with Power and Volume Down buttons until you see the tiny script and post your bootloader version. Should be something like 10.6.1.....
Do NOT do anything else in recovery at this point!!!! If it is incompatible with your bootloader you could hard brick!
Once we know if you have fastboot access and what your bootloader version is, we can help you to flash the correct recovery in fastboot. With that installed it's a piece of cake to get you up and running.
But be patient! Don't do anything else you're not quite sure of!

*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?

FooYoungHi said:
*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?
Click to expand...
Click to collapse
Ok, good - you got adb working. The adb command to boot into the bootloader is
Code:
adb reboot-bootloader
Note the hyphen
Also I wonder if you pushed Power and Volume Down long enough. You should feel the tablet vibrate twice, then see some tiny script and 3 icons appear. That would be the bootloader menu and in it, you are in fastboot mode by default.
The next step would be to check if you have a fastboot connection.
The command for that is
Code:
fastboot devices
Read my guide on flashing a custom recovery and rom very carefully and follow the steps outlined to get TWRP 2.8.0.1 on your tablet.
Ask any questions you may have in that thread.
http://forum.xda-developers.com/showthread.php?t=2688891
Edit: Sorry, forgot that we have to determine your bootloader version first. So use the button combination or the adb command to boot into it and post it. Don't worry. I don't think you did anything to the bootloader - it's not that easy to mess it up...

Unfortunately, the adb code doesn't work, with or without the hyphen. The device will reboot, but will return to TWRP.
I've held down the Volume down+power button for more than a minute witout result. The device will just reboot after a while for as long as I'm holding it. I do see the screen flicker for a second.
I've also noticed, that after I push a file to the tablet, that after a reboot it loses the data I just moved.
After booting TWRP, when I look in the command line of TWRP, it tells me that it can't mount the 'system' , 'data' and 'cache' forders. (tw_mount)
And it specifically mentions (multiple times) that the /data folder failed to mount, giving the message "No such file or directory"
It seems I really managed to F'ed it up good...

My "force-boot-to-bootloader" kernel module might help you unbrick. Read this guide very carefully before you do anything:
http://forum.xda-developers.com/transformer-tf700/help/guide-t2853546

You people are my new heroes!
The last guide did the trick. The stock firmware is installed and I'm currently updating and installing all the apps.
Thank you all só much, you really saved me a ton of frustration.

Can't boot into recovery. any idea if this can be fixed?

I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!

@nickizm, when you boot to fastboot and enter the command "fastboot devices", can you see your device listed on the screen?

Thanks for the reply.. The fastboot work fines apart from when I try to unlock the devices and it reboots into recovery, it crashes and doesn't unlock.. the rest of the phone works fine apart from the recovery... my bootloader is also locked and I can't unlock it due to crashing
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screem enabled: false

I can't be certain but I'm pretty sure I read a similar issue to this a few days ago that was caused by not having the latest fastboot software, the user resolved it by downloading the latest android sdk and trying again.
Worth a shot.
Hope it helps.
Powered by Bacon

I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.

I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again

nickizm said:
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
Click to expand...
Click to collapse
Did you try with the latest android sdk?
Powered by Bacon

I'm sure I did.. It wasn't that old.. I can try again, but the problem is I won't be able to unlock my phone??
is this the right link? http://developer.android.com/sdk/installing/index.html?pkg=studio

New drivers, exactly the same

Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here

Rkr87 said:
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Click to expand...
Click to collapse
Yea i have also tried the tool kit V2
My problem is that the recovery is damaged in some way and my device is locked. i can't "fastboot oem unlock" as it just crashes when it goes to reboot.. is there a way to unlock my device with another method or can the recovery be repaired some how? i'm such noob

patstar5 said:
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
Click to expand...
Click to collapse
Ye i tried that as well.. can't unlock the device as it just crashes when it goes to reboot into recovery

I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.

Rkr87 said:
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Click to expand...
Click to collapse
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways

nickizm said:
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
Click to expand...
Click to collapse
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here

Rkr87 said:
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Click to expand...
Click to collapse
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help

nickizm said:
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
Click to expand...
Click to collapse
No worries! Let me know how it goes good luck!

Rkr87 said:
No worries! Let me know how it goes good luck!
Click to expand...
Click to collapse
Definitely! cheers again

nickizm said:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
Click to expand...
Click to collapse
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
adb reboot recovery
Click to expand...
Click to collapse
there you can got into recovery.

Gh05tShie1d said:
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
there you can got into recovery.
Click to expand...
Click to collapse
That doesn't work as my device crashes when it goes into recovery..
eg: "fastboot oem unlock", factory reset, or a boot recovery all crash as my recovery isn't working. When my device goes to reboot in recovery the 1+ logo comes up, fades out to like a blueish from the white 1+ logo and crashes.. so basically it's looked and I can't get into recovery.. thanks for trying

[Q] First timer Rooter having problems

Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.

Terry_Tsang said:
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Ok I was dumb and figured out the first half of my problem. I thought it had to boot into recovery mode to get the fast loader to work. Anyways now it lists my device when I type fastload device but when I try to flash twrp it gives me an error saying
Sending 'Recovery" <6800 KB> ...
Failed (command write failed(No such device or address))
Can someone please help? thanks

I guess you forgot "-i 0x0b05" in the command
it should look like this:
fastboot -i 0x0b05 flash recovery twrp.blob
if fastboot devices detects tablet then this should work.
AFAIK Asus is the only one brand that needs "-i [hex_ID]" even when it is the only fastboot device detected by "fastboot devices" command
Sent from my TF300T using XDA Free mobile app

th3cr0w said:
I guess you forgot "-i 0x0b05" in the command
it should look like this:
fastboot -i 0x0b05 flash recovery twrp.blob
if fastboot devices detects tablet then this should work.
AFAIK Asus is the only one brand that needs "-i [hex_ID]" even when it is the only fastboot device detected by "fastboot devices" command
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
That id string is a vendor code and all android vendors have one ....
It is not need to flash from fastboot, it is only for safety that you need to use the vendor id ....
Thx Josh

I remembered reading about that while performing nvflash backup - https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
and then I remembered it didn't work for me without that vendor ID specified manually,
later on I rooted my cousin's Sony phone and that one did fastboot without -i option, so I concluded it must be asus specific "issue" - not to detect ID automatically or sth ....
Anyway @Terry_Tsang - If you have not tried like that, it is always worth a shot ;]

I have tried it with and without the -i tag and get the same error. I have a feeling my recovery file is corrupt as I get an error when I try to boot into that mode. I also now have a new error instead of unable to write, it says invalid argument.
Since I was able to root it with kingo, I tried the TWRP app but it also crashes when I try to do an install of TWRP through the app. I have no idea how to proceed.
I have tried, rooting with kingo and the commands. I have tried unrooting it. I have tried rooting then using ROM Manager and TWRP apps. I have no idea how to continue. I definately think something is wrong tho lol.

th3cr0w said:
I remembered reading about that while performing nvflash backup - https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
and then I remembered it didn't work for me without that vendor ID specified manually,
later on I rooted my cousin's Sony phone and that one did fastboot without -i option, so I concluded it must be asus specific "issue" - not to detect ID automatically or sth ....
Anyway @Terry_Tsang - If you have not tried like that, it is always worth a shot ;]
Click to expand...
Click to collapse
Well its all good not a point of being right a point in giving good info ...
Here are the most use vendor codes not just an Asus thing ?
https://gist.github.com/lj50036/3b30ecc420b5838646be
Thx Josh
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
Terry_Tsang said:
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
You do not have to root to flash a recovery anyway ...
If you would like to look into this more shoot me an email at [email protected]
Thx Josh

Terry_Tsang said:
I have a feeling my recovery file is corrupt as I get an error when I try to boot into that mode. I also now have a new error instead of unable to write, it says invalid argument.
Click to expand...
Click to collapse
You did check the checksum of your download right?