Database Info

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

Rooting and unlocking after JB Update

Is there any way to root or unlock the Infinity after updating to Jellybean. The current methods do not work. Will i have to wait for someone to come up with a new tool or what

Downgrade back to .30
http://forum.xda-developers.com/showthread.php?t=1915598
Install SuperSU and OTARootKeeper
Use OTARootKeeper to protect root
Update to JB
Use OTARootKeeper to restore root

macaumen said:
Downgrade back to .30
http://forum.xda-developers.com/showthread.php?t=1915598
Install SuperSU and OTARootKeeper
Use OTARootKeeper to protect root
Update to JB
Use OTARootKeeper to restore root
Click to expand...
Click to collapse
It looks like there is different versions of .30 does it matter what one. Thank you so much

Just follow the SKU of your infinity and download the file from ASUS.

macaumen said:
Just follow the SKU of your infinity and download the file from ASUS.
Click to expand...
Click to collapse
Man i am so confused right now. I have hacked many phones including my S3 and flashed many times. I am just confused coming to Asus. I have never had a asus device before and down want to screw anything up. Any extra help would be greatly liked thanks man

aldude345 said:
Man i am so confused right now. I have hacked many phones including my S3 and flashed many times. I am just confused coming to Asus. I have never had a asus device before and down want to screw anything up. Any extra help would be greatly liked thanks man
Click to expand...
Click to collapse
Settings --> About tablet --> Build number
There you will find something like "XX_epad" in the middle of that very long string. In which XX = your tablet's SKU. It can be US, WW, TW, etc.
Sorry, I don't have my tablet in my hands. Cannot get you a screenshot. I am sure there's some around the forum.
Let me know if you can find it

macaumen said:
Settings --> About tablet --> Build number
There you will find something like "XX_epad" in the middle of that very long string. In which XX = your tablet's SKU. It can be US, WW, TW, etc.
Sorry, I don't have my tablet in my hands. Cannot get you a screenshot. I am sure there's some around the forum.
Let me know if you can find it
Click to expand...
Click to collapse
Awesome i see its the US version. I have found it on Asus website. Now one more thing and this may sound stupid. I see it says put it in adb/fastboot. where is that exactly haha thanks again

Oh wait, I guess you haven't unlocked the infinity yet. Fastboot is available only after unlocking. I haven't unlocked mine, so I am not very familiar with that.
Using adb connecting to your tablet through command prompt is essentially the same as running terminal emulator on the tablet. I guess you should be familiar with adb as you hacked many phones already.
You know what. I heard that the unlock tool also works in JB for TF300T. I guess it should be working on TF700T with JB also. You can try it first before downgrading.
You can try this guide to downgrade to .30. Just download the .30 file instead of .22 stated in the post.
http://forum.xda-developers.com/showthread.php?t=1803343

Can someone post the JB OTA for users that have an unlocked bootloader?

Or suggest how else can I get JB for my unlocked TF700?

letmeupgradeya said:
Or suggest how else can I get JB for my unlocked TF700?
Click to expand...
Click to collapse
Which SKU (US/WorldWide)?

HeartWare42 said:
Which SKU (US/WorldWide)?
Click to expand...
Click to collapse
US please.

letmeupgradeya said:
US please.
Click to expand...
Click to collapse
Refer to this http://forum.xda-developers.com/showthread.php?t=1915079

Malkaridae said:
Refer to this http://forum.xda-developers.com/showthread.php?t=1915079
Click to expand...
Click to collapse
You have to be rooted to use that solution. I don't want to root at this time.
I think I'm a little naive in this situation. I assumed that someone would post the OTA file for users to download. Or will Asus post the JB OTA on their website?

letmeupgradeya said:
You have to be rooted to use that solution. I don't want to root at this time.
I think I'm a little naive in this situation. I assumed that someone would post the OTA file for users to download. Or will Asus post the JB OTA on their website?
Click to expand...
Click to collapse
Err, I'd thought if your unlocked you would be rooted also. Anyway you'll probably have to wait until ASUS post this at their website.

You are unlocked but refuse to root? Interesting.
Regardless you can root and use the method posted. Once JB installs you can continue to live root-free and be happy.
oh and the ota file is posted all over the forum. you just can't flash it if you are unlocked.
--edit-- looking at the instructions I don't think you really have to root in order to flash. you will need cwm though.

letmeupgradeya said:
You have to be rooted to use that solution. I don't want to root at this time.
I think I'm a little naive in this situation. I assumed that someone would post the OTA file for users to download. Or will Asus post the JB OTA on their website?
Click to expand...
Click to collapse
Actually, you don't have to be rooted. If you're still on the stock rom, all you have to do is flash the provided zip from a custom recovery.
---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------
lafester said:
oh and the ota file is posted all over the forum. you just can't flash it if you are unlocked.
Click to expand...
Click to collapse
sure you can, but in that case the easiest method needs root access, as you have to copy things into /cache.

urrlyx said:
sure you can, but in that case the easiest method needs root access, as you have to copy things into /cache.
Click to expand...
Click to collapse
No, that did not work for myself and many others.

lafester said:
No, that did not work for myself and many others.
Click to expand...
Click to collapse
well i don't know what to tell you. it DID work for me a couple of times. both from .22 -> .26 and .26 -> .30.

urrlyx said:
well i don't know what to tell you. it DID work for me a couple of times. both from .22 -> .26 and .26 -> .30.
Click to expand...
Click to collapse
Didn't work for me for .30 or JB... got update failed every time.
Mind sharing your technique?

lafester said:
Didn't work for me for .30 or JB... got update failed every time.
Mind sharing your technique?
Click to expand...
Click to collapse
how did you end up upgrading then? did you just go with the full firmware?
the zip files pretoriano linked contain the same blobs / patch files as those in the OTA dlpkgfile. if any part of /system fails to look exactly like what the updater expects, it will fail.
when i do an upgrade i take a backup, wipe everything, install the latest full stock firmware, and then apply the update. that way i don't have to waste time hunting down missing apks or other original files.
i only used pretroriano's zips this time around because flashing a zip is way easier than reverting to stock recovery, copying the ota file into /cache, creating the /cache/command file and then rebooting to stock recovery to watch it do its thing. plus he hadn't provided them for the previous updates at the time i did those.

yeah that's exactly the same method i used with no luck.
for .30 i just used the full update file from asus. i had just about given up and should have since nvflash came out a week later.
really just wanted the hardware updates at the time.

yeah i hear ya. wankers, sneakin in a signature check on us like that!

djrbliss releases AT&T S4 bootloader vuln.

I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki

this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.

spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom

its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...

shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.

Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with

fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have

alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.

just means soon we will have bootloader unlocked.... patience

lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.

Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET

TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.

fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.

fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:

Incoming update from Samsung in 3....2....1.....

I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!

mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.

fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.

mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.

Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Shield Tablet OTA

Can anyone upload the official Shield TABLET' OTA's somewhere? I can't download it because I don't have a developers acount
https://developer.nvidia.com/gameworksdownload

djricekcn said:
Can anyone upload the official Shield TABLET' OTA's somewhere? I can't download it because I don't have a developers acount
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116
links in that thread.

kossiewossie said:
http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116
links in that thread.
Click to expand...
Click to collapse
sorry for late reply, those links dont' work...it keeps taking me to a log in page or make a dev account. neither of which I can. I just need someone to upload the factory one on dropbox or something cause anything recovery / ota related on Nvidia, I can't access it without a Dev Crudential

djricekcn said:
sorry for late reply, those links dont' work...it keeps taking me to a log in page or make a dev account. neither of which I can. I just need someone to upload the factory one on dropbox or something cause anything recovery / ota related on Nvidia, I can't access it without a Dev Crudential
Click to expand...
Click to collapse
https://www.dropbox.com/s/ul95yle4ostpdtb/nv-recovery-image-shield-tablet-update1.zip?dl=0
I uploaded it to my dropbox. hope that helps its recovery image with update 1