Database Info

what to do now?

Hey,
got a problem here, just freaked out cause i thought i bricked, but huray seems we are ok.
Today I went from seans JB 3.0 to 3.6A, after that im stuck at asus logo. So i downloaded
ASUS Transformer Pad TF300T Firmware: V10.4.2.9 Only for WW SKU (Android 4.1) ( I flashed the unzipped file )
then some mismatch poped out and i thought im done . But CWM is still in place so I can still help it somehow :highfive:.
Any suggestions ?
edit: aaaaw i just came up to that I may be flashing different base! Ill try US
edit 2: no, US 10_4_2_9 signature mismatch... :/ so can someone lend me a hand here ? please
pleease some great mind here help me . Im doin it exactly how should i be doing it. Ill talked with guys in seanz topic and im sure im doin it right, I really dont know what could be wrong. I re-downloaded the file from asus, extracted it so i could flash US_epaduser_10_4_2_9.zip, after a minute or two it says its complete but when i reboot it says signature mismatch. There must be someone who knows what could be wrong, because im stuck here, i dont really know what to do.
CONCLUSION: okay i just made it. The problem was CWM Recovery. It just couldnt flash the zip. I just tried to flash TWRP over CWM and I got signature match and right now im on stock rom. hurray TWRP!

[Q] Need help, bad! Greatly Appreciated!

Okay, I rooted my TF101 B90 model and all was good. I installed rom manager and flashed its custom recovery and had that whole issue that the sd card wasn't read and such. After much frustration I finally tried Wheelie (Nvflash) and it keeps failing and now I have nothing on my tablet. I can get into APX mode and flashing the stock rom using many custom utilites always fails (Usually says something like command failure :go failure or could not load bootloader to device) I'm sure it's probably fixable, I just need someone to type it out for me (I'm pretty smart when it comes to Android but I'm honestly stumped right now) Or please redirect me to a post that could help, However I have read a lot of the posts about this and everyone is getting there's to work and I can't get mine. Thank you!!!
Andrew

[Q] Stuck @ Boot Screen

Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!

xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.

OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.

I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.

ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.

I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!

opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:

Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?

opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.

Help updating TF300t to 10.4.2.20

Hello,
I just got my transformer tf300t (US) yesterday. It came with 10.4.2.18 on it. It tried to update to 10.4.2.18 right away, but i had heard so much about problems unlocking the bootloader, i went ahead and an postponed the updated, and unlocked immediately. The unlock went without a hitch! I thought, great! However now I don't know how to update the firmware to 10.4.2.20, as when I tell it to check for udpates, it says that it is up to date(and from what i read this is because its unlocked).
I thought about just installing a customer recovery, and flashing a customer rom based on 10.4.2.20, but they all say in the instructions to update to the newest rom before flashing(i assume this is because the bootloader needs to be up to date?)
Any help or guidance would be appreciated, thanks!

urushiol said:
Hello,
I just got my transformer tf300t (US) yesterday. It came with 10.4.2.18 on it. It tried to update to 10.4.2.18 right away, but i had heard so much about problems unlocking the bootloader, i went ahead and an postponed the updated, and unlocked immediately. The unlock went without a hitch! I thought, great! However now I don't know how to update the firmware to 10.4.2.20, as when I tell it to check for udpates, it says that it is up to date(and from what i read this is because its unlocked).
I thought about just installing a customer recovery, and flashing a customer rom based on 10.4.2.20, but they all say in the instructions to update to the newest rom before flashing(i assume this is because the bootloader needs to be up to date?)
Any help or guidance would be appreciated, thanks!
Click to expand...
Click to collapse
You have an Index for the TF300T/TG here, and you will find all you need for your TF :good:
and try this : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !

philos64 said:
You have an Index for the TF300T/TG here, and you will find all you need for your TF :good:
and try this : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !
Click to expand...
Click to collapse
I went through a few hours of heartache to be able to update my tab to stock jb 4.1 about a month back, and to be honest I don't really remember how I did it, though I think it involved adb/fastboot...
I am currently running cm 10.1 off of the asus 4.1 bootloader, and I will be attempting to update to asus stock 4.2 in about 20 minutes and I will let you know my findings... but sofar, you are off in the right direction, though I might recommend the NVflash tutorial in the dev area to make sure you cant f up your tab...

Alright brother, so here is what I have got figured out since I last posted about, oh, say 8 hours ago...
Now, assuming you took my advice and did the whole lovely NVFlash Tutorial, then what I would do is go to Asus.com, pick your region, go to support, firmware, then select the 10.4.2.20 update that matches your tab's region (mine is in the US, so I picked US). Then download that sucker, go smoke a cig or two (however long it takes) or do whatever you do that will take THAT time to download the ~500mb file...
FROM THERE, assuming you are using windows (like I am, Windows 7 to be exact) use your favorite unzipping prog. to open the file, then extract the .zip within (called US_epad-user-10.4.2.20.zip) to somewhere on your interal (or I prefer external) sd card.
NOW, if you haven't done so already, you need a Custom Recovery, and I HIGHLY recommend TWRP because in my experience, it is simply more versatile that CWM (clockword mod). Again, you can find this in the Developement section of this forum...
Once you have both TWRP, and your official update file on an sd card, you are almost home free here... Alls you have to do is boot up into recovery from, say... device turned off... by first holding Volume Down then pressing and holding (at the same time) The power button until device comes on. You will then be met with a small message in the upper left hand screen saying "press Volume up to enter RCK" (or recovery) and TWRP should load from here.
Once it does, then it's easy here, first, for grins, create a backup, simply by hitting the backup button (you'll know it when you see it) that way you have a dyed-in-the-wool backup of your actual stock rom (THIS CAN BE VERY HELPFUL should you need to return or repair the tab, which Asus will no longer cover since it's unlocked, but if you got it from, say Amazon or Best Buy, you should have almost NO problems being able to do that... jejejeje) once backup is complete (should take about 3-5 minutes or so) then hit the Home softkey in the upper right corner, go to "install" then find where you put that update file that I had you extract earlier (hopefully on your external sd card for simplicity)... You are given a some-what easy to navigate file system that should help you locate it where your folder tree will be on the left window and your files within the active folder are in the right, select the file, then install...
WHEEEEE! Now let that bad boy go, when it says Success! and displays the buttons again at the bottom, then you are good to return home to the main screen (of TWRP) or to just Reboot the tab. Upon rebooting, you will first see your Asus splash screen with the device unlocked text in the upper left, following some new text saying something silly like official update ok, then the next screen will have a slightly different Asus splash with a progress bar that fills up blue as it updates/installs the system. THIS WILL TAKE A LITTLE WHILE, and when done it will reboot again ( I believe) and then show the Asus logo with a dotted rotating "loading" circle, and this too, will take a while to finish doing what it's doing...
From here, it's just the waiting game....until you are prompted to set it up like you did the first time out of the box.
Congrats! Now you are fully up to date until Asus posts the NEW 4.2 update on the site, which is currently only available in the US via OTA update (which would require you NOT be unlocked, but who cares)
You can find info on THAT update below...
http://www.androidcentral.com/android-42-roll-out-asus-transformer-pad-tf300-begins-today-us
Other than that, once you are where you wanted to be (which was on the official JB 4.1.1 update, things will go smoothly for you, it ran real nice for me, but I don't know if it's just my Wi-Fi setup or what, but I seemed to lose Wi-Fi stability after a month or so... Asus has been known for that I hear, but then again, you might not have that issue...
At any rate, you are now able to safely flash your brains out on this tab... I was on CM 10.1 (which gives you the bleeding edge Android 4.2.2) and it works nicely, but I experienced some seriously noticeable lag on screen rotation when using the nightlies that simply just weren't there on the stock rom. Not only that but the stock rom gives you a cute feature at the bottom of the screen, in the middle of the notification/nav bar... a navigation locker (great for games, especially if you have kids or just hit the nav buttons accidently when using media).
I am currently running the newest AOKP, and it does everything that CM10.1 does (as far as I can tell) and isn't short of any features (again, as far as I can tell after about an hour of toying) that CM10.1 has...
*finally exhales* Hope this has been helpful to you... God, I know it would have been helpful to me back when I did this.

VERY IMPORTANT: as it is almost 7 am, I just realised that after you flash the official 4.1.1 update, you will need to reinstall TWRP in order to use other ROMs...too easy, doesn't take hardly any time, I just forgot to mention it... Wish you well on your new tab!

Help!

I recently acquired an asus tf101 that was rooted running katkiss and twrp. I changed it to cm10 and now it wont boot on its own or load twrp it just hangs on "Booting recovery kernal image" i have tried everything i could find online such as EasyFlasher and the twrp app but the app wont let me flash the image for some reason (it does havce rooting permitions btw). If anyone could help find out whats going on it would be helpful. I atached some images if that helps.
Thanks in advance.
William

HI SuperUserWilliam
I have the exact same problem you are having and also my tf101 was rooted with katkiss and since I changed it to cm, I cannot boot into recovery or bootloader. Please let me know if you find a way out of this because I am going to have to trash my tf101 otherwise. Thanks.
VA3JLF

I wish I could help you guys but I can't even get my TF101 rooted since the batteries won't hold a charge.