Database Info

[Q] Trying to Root Infuse, odd problem.

Alright, this is just odd.
Generally, I want to get rid of the bloatware and make it so my phone doesn't run so much crap in the background, so I have turned to rooting it. However, this is more of a pain than anything.
I followed the Odin guide in order to get CWM, bloat removal, root, stock kernel, stock rom, etc, and its odd whats going on.
When I connect my phone to my computer, outside of download mode, and have it in USB debug, then it detects my phone in odin just fine. However, when I put it in download mode, it decides my phone is in a different dimension. Why is this?
When I unbricked it, I had to use heimdall. Odin detected it then, but couldn't fix, which turns out because I was using a crappy cord. I'm using the new cord now, and still getting problems with it detecting it in Odin.
Other info: I have the drivers installed from Kies Mini, I am currently trying to root with superoneclick, I have already cleared data via recovery mode, and oppan gangnam style.
Anyone able to help me understand why odin doesn't wanna detect my phone?

Spectre370 said:
Alright, this is just odd.
Generally, I want to get rid of the bloatware and make it so my phone doesn't run so much crap in the background, so I have turned to rooting it. However, this is more of a pain than anything.
I followed the Odin guide in order to get CWM, bloat removal, root, stock kernel, stock rom, etc, and its odd whats going on.
When I connect my phone to my computer, outside of download mode, and have it in USB debug, then it detects my phone in odin just fine. However, when I put it in download mode, it decides my phone is in a different dimension. Why is this?
When I unbricked it, I had to use heimdall. Odin detected it then, but couldn't fix, which turns out because I was using a crappy cord. I'm using the new cord now, and still getting problems with it detecting it in Odin.
Other info: I have the drivers installed from Kies Mini, I am currently trying to root with superoneclick, I have already cleared data via recovery mode, and oppan gangnam style.
Anyone able to help me understand why odin doesn't wanna detect my phone?
Click to expand...
Click to collapse
bleh windows and odin problems. it might be a usb controller problem. or a driver problem... the usb chord should always be plugged directly into the back of the computer into the ports on the motherboard preferably. no hubs or anything. also the heimdall driver might be messing with the samsung download mode driver. there is actually different drivers for download mode and normal connections from samsung. it looks to the computer like different devices. for odin to work you need to connect in download mode and wait for windows to install the drivers or download the drivers from the samsung support website and install them manually. this might require removing all existing samsung drivers and the heimdall driver and starting over.
i have to ask though, if you unbricked the phone with heimdall why not use heimdall to flash the cwm kernel? all you have to do is extract the zImage from the .tar and flash it to the kernel partition.
also fyi super one click can not work on official gingerbread. the att official gingerbread is apparently very secure. or the real hackers never paid it any mind because it is so easy to work around that limitation with odin or heimdall.

Well, I can try digging through and see if the heimdall driver might still be there, idk if it is or not. Also, when I plug it in in download mode, it installs a driver, but when I look through device manager, it says the device isn't there.
Also, I read somewhere you couldn't root the phone with heimdall using the same method I was trying to get ahold of, so thats why I didnt use heimdall. But in that case, any chance you could link me to a guide on how to do that? The main thing I want is to get rid of this bloatware and crap.

Spectre370 said:
Well, I can try digging through and see if the heimdall driver might still be there, idk if it is or not. Also, when I plug it in in download mode, it installs a driver, but when I look through device manager, it says the device isn't there.
Also, I read somewhere you couldn't root the phone with heimdall using the same method I was trying to get ahold of, so thats why I didnt use heimdall. But in that case, any chance you could link me to a guide on how to do that? The main thing I want is to get rid of this bloatware and crap.
Click to expand...
Click to collapse
what link were you following? so i can see what you are working with..
the only ways to root is to flash a pre-rooted /system image(but i haven't seen one, i've been too lazy to make one myself) or flash a cwm kernel and use it to flash an su and superuser package. some of the older kernels had a rooting script but it sometimes borks su if you update it and will downgrade su when you reboot so the devs took the rooting feature out of the kernels. both the /system image and the kernel method need heimdall or odin. anything that odin does heimdall does but heimdall uses different packages or no "package" at all.
heimdall can be done in command line and it's easier to explain that way than the ui. are you comfortable with command line?

THis is the link to the guide i was using. http://forum.xda-developers.com/showthread.php?t=1613523
And I'm not too great with command lines. I have next to no experience with linux os, and though I've tried to learn some, it just doesn't seem to stick.
Hell, most of what you said doesn't entirely make sense to me.

New info. Computer detects it in download mode, but odin doesnt. Grr to this stuff.

I think I found the main problem.
When I unbricked my phone, I upgraded to GB. Now I'm at GB, and according to what I read, thats where all the problems are stemming from. Is there a way to root when you are on GB? Or do I need to downgrade to Froyo, root, then go back to GB?
If I have to do the latter, then I'll just skip GB and figure out the CM9 stuff.

you should still be able to use heimdall, and i think it can work with the samsung drivers, the open source driver heimdall uses may help in some situations but i dont think it's needed. odin can be weird. i never use it.
you have 2 options asuming heimdall works(i think it will). you can use option a from that thread but flash it through heimdall, or you can go to the thread for entropy's kernel and download the zImage and flash that through heimdall.
for heimdall download this and extract it to a folder somewhere. https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
you may also need this but it may already be on your system http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en
download the rom .tar file (or kernel zImage if you want cwm) that you choose and extract the contents to the folder that contains the heimdall files.
if you are using the rooted rom, stock kernel no cwm package it is in .rar and there is a .tar or .tar.md5 inside of that. remember to extract the .tar and not just the .rar.
now if you are already on the att release if gingerbread uclb3 you will only need the factoryfs.rfs remeber that it should be in the same folder as the heimdall.exe file
put the phone in download mode and connect the usb cable then open a command prompt and navigate to the folder with heimdall and the factoryfs.rfs (c:\users\<login name>\<whatever folder you made or chose>\ ) and type
Code:
heimdall flash --factoryfs factoryfs.rfs
if you chose to use a kernel with cwm instead then you will use the zImage file. download the kernel you want and extract the zImage file into the heimdall folder or what ever you called it. go into a command prompt and type
Code:
heimdall flash --kernel zImage
after you have cwm you can download this http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip for root, move it to the sdcard and reboot to recovery and flash it in cwm
if you are not comfortable with command line you can use the frontend but it requires the pit file which you need to get from the unbrick packages.

[Q] Black screen after Heimdall One-click with bootloader, Download mode works

First, I tried searching for hours, and I haven't been able to find this same issue anywhere on the forums yet. If I missed it, sorry, and thanks.
I downloaded the stock 2.3.6 firmware from the Hiemdall One-touch thread here, and ran it on my phone (SGH-T959V Galaxy S 4G, and I made sure the firmware was for that specific model and not the Vibrant). It ran through the first time just fine, and then I went to do the bootloader (which I gather I probably shouldn't have done and didn't need to do maybe). Heimdall One-Click started running, then gave me this message and restarted the phone to a black screen:
Code:
Uploading PIT
PIT upload failed!
Ending session...
Rebooting device...
Now, I can pull the battery and get the phone into Download Mode just fine, and I've tried running the same firmware as well as several others (AntonX-Basic_with_a_twist, Stock KJ6 + root-One-Click, hampsterblade-Basic_MIUI_Kernel_r2_OC_UV, at least), but while they all do the first restore fine, none will load the bootloader and I get the same results every time. The phone is obviously not 100% bricked since I can get into Download Mode, but all I get is a black screen, no lights under the buttons and nothing on screen, not even the rainbow pattern or the Samsung logo. It's as if the phone isn't doing anything at all, and it doesn't change if I just pull the battery and leave it (tried for 15-20 minutes a little while ago). The only thing I can do is put it back into Download Mode, but none of the firmwares I've found have worked to restore the bootloader.
I am using a Mac with 10.8 and Java 1.7, and if it's necessary I can get access to Windows, but that will take me some time and effort, so if there's any way to resolve it using just the Mac that'd be best.
jW

When you flash the Heimdall package, does the phone boot fine?

It should have work with Mac, can you double check things?
If possible can you try re-downloading the .jar package.
And in the terminal run the .jar package (sorry I don't know OS X commands).

Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW

jondesu said:
Thanks for the responses. It does not work after I run the Heimdall package, before or after I check the Flash bootloader checkbox. I have tried redownloading the packages several times, and I always run them with "java -jar [path to file].jar", which should be the proper command structure (and they do open and run and report success up until the point of that error, which is after the first time through but before any other steps complete in the Flash bootloader process).
Is there another method instead of the Heimdall One-Click .jar's that I can use? I have the full Heimdall installed of course, but I can't seem to find a stock PIT file for this phone that it will recognize.
jW
Click to expand...
Click to collapse
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.

th3controller said:
As far as I know don't be desperate, that happened to me and I ended up with a bricked device.
Either boot into a free Linux distro. or use a Windows computer.
Click to expand...
Click to collapse
Thanks, I've got a Linux distro downloading and I'm looking into whether I could get a copy of Windows or borrow a PC easily.
jW

You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.

FBis251 said:
You've verified the md5 of the .jar file? I'm not sure which one you're using, please specify.
If the package file is fine and got downloaded correctly though, the next thing I'd try is a different USB cable. I have two cables, both work fine with my own phone, but I was flashing my friend's phone the other day and only one of them worked. This has happened to others too and it very likely might be the issue.
At this point though stop trying to flash the bootloaders. We're not sure whether your phone will flash successfully. You'll need to try flashing without the bootloaders and if the gingerbread package got flashed correctly you'll wind up getting the rainbow screen (assuming your phone still has the froyo bootloaders) which will be a good sign, and from there it'll be safer to flash the bootloaders.
Click to expand...
Click to collapse
Thanks, I'll give that a try (still trying to get Linux installed here to try that as well). The first one I tried, and the one I think I'd prefer to use is the T959VUVKJ6 Stock UVKJ6 from the Heimdall One-Click thread in the forums here. I tried some of the others when that one failed. It downloaded fine, and I tried downloading it again with no change in the results.
I should clarify, btw, that I have been trying flashing it without the bootloader, but when I do that, it still sits on the black screen. The very first time I did it and one other time later, I did get the rainbow screen (and the first time, but never again, it did boot up to the stock OS and home screen), but now if I flash with or without the bootloader, I get nothing, probably because the bootloader got screwed up by the first bad flash.
My first step today will be using another cable (there's one handy, I just didn't think about it), and then I'll move on to trying Linux/Windows.
jW

No operating system found.

Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.

There's a cool tool kit called wugs nexus toolkit that will help some http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 5 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------
Also, here's mostly all the roms stock & custom here: http://forum.xda-developers.com/goo...dex-google-nexus-5-roms-kernels-mods-t2475401
Did you say you can still get into recovery? Because there's an unroot rom thats flashable somewhere... Itd take you to stock everything.....
Sent from my Nexus 5 using Tapatalk

I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.

In fastboot, but can't flash operating system
dahawthorne said:
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
Click to expand...
Click to collapse
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.

" I've followed every rabbit trail"
Have you followed this one?
"Wugfresh's Nexus Root Toolkit"

kakid56 said:
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
Click to expand...
Click to collapse
Yup use wugfresh toolkit ... download the factory image https://developers.google.com/android/nexus/images#hammerhead
and boot into bootloader.. then u knw what to do

kakid56 said:
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
Click to expand...
Click to collapse
I don't disagree with the NRT suggestion but am confused. Sorry if I'm missing something obvious. When you are in the bootloader, do you get a cmd response from "fastboot devices" (no quotes in the command)? ADB doesn't work from the bootloader as you probably know, but since you identify as a noob, thought I'd throw it out there. You can flash the system using fastboot commands if your PC recognizes (part of the confusion) the device in fastboot. If not, then you do need to get the drivers set up. If you just need adb/fastboot drivers, I recommend this which I used recently when NRT didn't seem to have the SDK version I needed for my N9 to sideload the latest OTA. Since it installs at the system level, you can place flashable files at the root of C rather than in a specific platform-tools folder. I'm on Windows 10; don't know if that makes any difference for this minimal install. As far as the flash-all. bat not working, that's not uncommon; the files can be extracted and flashed separately.
Sent from my Nexus 9 using Tapatalk

Odin or Heimdall ?

Hello there ! I'm probably going to flash a new rom or at least recovery.
I'm first time flasher and have one question:
should I use Odin or Heimdall (I've got Windows 7 x64) ?
I've read that Heimdall is more reliable but Odin is best for flashing more things at once.
I want to know what do you think is the best.
Edit: Drivers don't work on Windows (error 10, adb ones are ok), so maybe I'll try Heimdall on linux.
Edit 2: I've booted into bootloader, then connected the phone and it worked.

Hello!
While I prefer Heimdall (which is free software, has native Linux support and supports both command-line and graphical interfaces), both apps were reliably flashing my S6310. I think that it’s not a problem to flash many partitions at once using Heimdall, but AFAIK it doesn’t support Odin’s .tar.md5 files.

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