Database Info

[HELP NEEDED] Magic Value Mismatch

Started reading the forums a few days ago, already planning on getting a gtab for x-mas. So got one at Sears today and went home confident I would know what I am doing. Well I was wrong !!
First mistake: My assumption that this will be as easy as my SGS with clockworkmod. For one, there are apparently CWM versions floating around that are known to cause issues - hence that is the one I ended up with. It installed the CMW fine and went into recovery just like I am used to. Tried to apply the ZPAD 2.2 rom and as soon as I rebooted got the 'Magic Value Mismatch' error at the top of the screen.
Mistake two: trying to fix it by finding the correct CWM called .8 which seemed to make things worse. I got a screen now right after the power and Vol + key that shows alternating black and white strips.
I had this thing only for 3 hours and I already managed to get way past my expertise on fixing this.
What can I do to get the tab to load a recovery image so I can boot?
On the internal SD card there is the folder called 'recovery' with the command file that points to the update.zip on the external sd card. I imagine that is correct. However it did not matter what ZIP file I place on the SD card. For example I renamed all the exising rom's one by one to update.zip to see if one of them would take and no luck.
I am sure someone with more experience can point me to how to get back to normal. I would appreciate some help.

Try This
I had a similar issue with mine about 30 min after I got it. Use your external SD and but the vanilla tnt update.zip and the recovery folder on it. Edit the command file in the recovery folder to say sdcard2 instead of sdcard. This worked for me , Good luck

Thaks for the info.
I created the recovery folder with the command file this time on the external SD card (preped this on the PC) and made sure the vanilla update.zip was on the root of the SD card.
I got a new error about a kernal having a critical error, but I was so frustrated that I did not write it all down.
Then I tried another rom (gtab lite 2.2) and I get the Magic Value Mismatch error again.
It seems like it does not even attempt going into recovery now, because it does not matter if I press the VOL+ and PWR key together. It has the same effect as if I press PWR alone.
I really don't want to give up just yet. If anyone else has any suggestions I am willing to try, plus this experience might help others in a similar situation down the road to recover instead of having to return the device.
I saw a post about some PC based update, but I also seen comments that that could make things even worse. Any ideas?

In the mean time I followed the NVFlash instructions and there is some success and also some loss.
The success is that I no longer get the "magic value mismatch" error. The loss is that my tablet still does not boot and now I have a Nvidia boot screen which will most likely raise a flag with Sears when I return it for an exchange.
I don't want to give up yet, but I really could use some pointers on what else to try.
Here are the instructions I followed for the NVF...
http://wiki.tegratab.com/index.php/ROMs
and
http://forum.tegratab.com/viewtopic.php?f=6&t=8
and
http://forum.xda-developers.com/showpost.php?p=9575351&postcount=26
All I get is the Nvidia logo. The tab has been on for more than 10 min and there is no change.

anosis said:
In the mean time I followed the NVFlash instructions and there is some success and also some loss.
The success is that I no longer get the "magic value mismatch" error. The loss is that my tablet still does not boot and now I have a Nvidia boot screen which will most likely raise a flag with Sears when I return it for an exchange.
I don't want to give up yet, but I really could use some pointers on what else to try.
Here are the instructions I followed for the NVF...
http://wiki.tegratab.com/index.php/ROMs
and
http://forum.tegratab.com/viewtopic.php?f=6&t=8
and
http://forum.xda-developers.com/showpost.php?p=9575351&postcount=26
All I get is the Nvidia logo. The tab has been on for more than 10 min and there is no change.
Click to expand...
Click to collapse
My nvflash won't help you, at this point. You want bekit's nvflash recovery -- http://forum.tegratab.com/viewtopic.php?f=6&t=8 I know you used mine because you have the Nvidia logo.
The difference between bekit's recovery and mine is that bekit's flashes EVERYTHING, at a low level. Mine isn't that extensive. You definitely want to try Bekit's flash before throwing in the towel.
As for SEARS, I wouldn't worry about it - they probably won't even notice. When I returned my first one, they didn't even open the box. Seriously.

roebeet said:
My nvflash won't help you, at this point. You want bekit's nvflash recovery -- http://forum.tegratab.com/viewtopic.php?f=6&t=8 I know you used mine because you have the Nvidia logo.
The difference between bekit's recovery and mine is that bekit's flashes EVERYTHING, at a low level. Mine isn't that extensive. You definitely want to try Bekit's flash before throwing in the towel.
As for SEARS, I wouldn't worry about it - they probably won't even notice. When I returned my first one, they didn't even open the box. Seriously.
Click to expand...
Click to collapse
The link you provided (I already went there before) had a link inside to download the necessary fiels but all it did is link to the main forum page. I never was able to find the correct files until this morning I believe. I found another post on these forums that had 'dropbox' links to several files that I downloaded.
So now I ended up with 1) the Tegra MSI installation file 2) the g tab image files and 3) the windows script files with the batch file. I will attempt these tonight and report back.
We are in the middle of moving - finally home owners again at last ;-). I have no internet connection at my new house yet however my SGS and tethering are my friend right now, so I can post and download at a lower rate.
Thaks for the help!!

I wonder what came of this! A feedback would be nice.
Thanks!

i would guess roebeet's suggestion worked, otherwise anosis would've been back on here.

oshea85 said:
i would guess roebeet's suggestion worked, otherwise anosis would've been back on here.
Click to expand...
Click to collapse
No PM's to me, yet. I take that as a good sign?

roebeet said:
No PM's to me, yet. I take that as a good sign?
Click to expand...
Click to collapse
I believe you deserved a big thank you instead!

Thank You!
I don't know about the other guy, but I borked the Tab tonight, and these instructions worked flawlessly. The links to the apps were stale, but the IRC channel pointed me in the right direction.
Now back to to the Tablet to find out what I need to put back on it.
Thanks again!

can you tell me where to find those links? I screwed mine up too.

professor03 said:
can you tell me where to find those links? I screwed mine up too.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=861950

Saved my bacon!
This thread was awesome! Pulled my ace out of the fire when i accidentally wiped out CWM when trying to format to install a new VeganTab. You guys rock!

Hooray!
Sorry to bump an old thread guys, but I just wanted to chime in and say this also worked for me. Someone should add this to the stickied threads...

rogersranch said:
Thank You!
I don't know about the other guy, but I borked the Tab tonight, and these instructions worked flawlessly. The links to the apps were stale, but the IRC channel pointed me in the right direction.
Now back to to the Tablet to find out what I need to put back on it.
Thanks again!
Click to expand...
Click to collapse
Hi,
I am just wondering if you can provide a more detail instruction on how this can be fixed? I am a new android user, I am not very knowledgeable. If you can provide some more information, that would be greatly appreciated!

I beleive what you are looking for is in the link posted.
http://www.slatedroid.com/topic/177...recovery-pack-cwm-standard-recovery-g-tablet/

mismatch is good
I finally did the nuclear option to get my tablet back. I was in the dummies site when panicking as well, read mismatch was to be a welcome...

Bricked? And options?

I think I'm posting to the right place. I have been playing around with the various mods, tnt lite, vegan, cyanogen, and somewhere along the way it got stuck to the point it is giving me an error right when I start the tablet saying "magic value mismatch". First time it happened I was able to get back to recovery. And I tried to restore, and didn't work. Tried clearing cache and it hung there for over thirty minutes. Now I can't even get into recovery and error reads the magic value mismatch. So am I bricked or is there a way out of this? And anyone try returning a bricked tablet to Sears? I'm still within my 30 day window.
Sent from my Droid using XDA App

Here's a nice link:
http://forum.xda-developers.com/showthread.php?t=860493

Thanks for the link. This seems to work, as I did not know the low level capabilities. Hopefully, I'll be mod'ing again soon! And for anyone in my position between these two links I figured it out where to get the files:
forum.tegratab.com/viewtopic.php?f=6&t=8
forum.tegratab.com/viewtopic.php?f=13&t=18&p=170

Did you use a newer version of clockworkmod (.12 or higher) with the device, and attempted a firmeware update? If so, it's a known issue and it's why I'm still using .8, right now.
It's not bricked, btw. This device is virtually unbrickable - you will probably need nvflash to fix it, and I have a post that can point you in the right direction:
http://forum.xda-developers.com/showthread.php?t=861950
Hope this helps!

Thanks, but I'm now getting the issue some others had in the other forums, but I don't see a fix where every boot ends up in APX mode. How do I get out of that?
As a side note, I did try the latest updated Clockwork recovery last night, which I believe is 2.5.1.8, that seemed like they added support from ROM Manager.

Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!

jkpatel79 said:
Sorry, I take it back used, the right zip file and everything is fine. I grabbed the one dated 2010112600 thinking it was a later version. Thanks for the help and the great threads and ROM's!
Click to expand...
Click to collapse
You might one of the newer devices with the swapped partitions (thats the 11/26 one you used). We still don't know why this is - very bizarre as to why VS (or whatever vendor they use) did this.

roebeet said:
This device is virtually unbrickable
Click to expand...
Click to collapse
Virtually is right. I accidentally bricked mine because I hit one of the devkit .bats while trying to reflash to stock

Did I just brick my OPO?

Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.

Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)

Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon

Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.

Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon

timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!

Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon

Updating advice please ! Reroot failure

Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true

I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.

Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again

[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!

So where does one get the latest OTA?
cheers

Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.

Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!

bootloop - question on how to proceed

I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:

monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....

berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.

Nobody has any more expertise to proffer?

monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary

berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!

Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.

New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.

Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience

berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.

Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again

berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?

No, you cannot relocate the bootloader. Flash away

berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.

Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.

I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks

Not enough information. What can you get to?
What's your ROM, bootloader, recovery?

berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks