[Q] Bricked friends TF - Eee Pad Transformer Q&A, Help & Troubleshooting

Just bricked a friends TF. Is it possible to unbrick it to stock rom ?
He just updated to latest 3.2WW ROM prior to this.

How exactly did you brick it? What were you doing at the time?

I managed to wipe all partitions .. for various reasons I ran download.sh which apparently formatted the whole TF and reformated it.
At this point I'm downloading the latest tf_rootkit_31 to get the cwm recovery image from it.. but I have my douts that this will work.
I have downloaded the last release from ASUS website and tried to nvflash on the blob files.. but it stays in APX mode..
I have PRIME 1.6r2 but I have no clue how to get this on the device .. without CWM ..

As i thought... didnt work.. but the download.sh wants system.img which I don't have.. :|

think I managed to get it unbricked.
I dumped recovery and system from my working TF101 .. seems to be booting now at least..

This thread can be locked or deleted... as mod see fit
Basically I managed to run the wrong script as I were about to root the TF. Instead of root.sh (self made) that run the needed commands to download, patch and send in the patched boot image back to the TF.
Download.sh is from someone else, don't really who.. but it does wipe the device and flash in boot.img, system.img and recovery.img ..
After fetching the needed files from a working TF101 and flashed it back to the device it is now up and running, but all apps need to be re-installed and setup again.. thankfully he made a mybackup pro backup prior to updating the device.. so I hope he'll managed to restore most of the device back to its original again.

What I love about the TF is that it seems impossible to permabrick. Glad to hear you got it going again.

Glad to hear it. I bricked mine not more than 5 hours ago, and sorted that too.

It's not very nice but you learn as you go I suppose..
(mmh I hate the new mouse-pointer )
Sent from my Transformer TF101 using Tapatalk

Need to pick this up again.. for some reason he doesn't have the 8.4.4.11/8.6.5.7 boot screen.. the one before the boot animation comes into play.. the one he has is the same as 8.4.4.5 .. any1 know the reason and/or a possible fix for this ?
Sent from my Transformer TF101 using Tapatalk

paddy01 said:
Need to pick this up again.. for some reason he doesn't have the 8.4.4.11/8.6.5.7 boot screen.. the one before the boot animation comes into play.. the one he has is the same as 8.4.4.5 .. any1 know the reason and/or a possible fix for this ?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You have to update the bootloader too. It's the EBT partition in the flash.cfg. add something like filename=blob.EBT
You can extract the EBT/bootloader partition from the blob in the 8656 update. Rayman has put out some blob tools for extraction.
sent from my cyanogen(mod) vision

gee one said:
You have to update the bootloader too. It's the EBT partition in the flash.cfg. add something like filename=blob.EBT
You can extract the EBT/bootloader partition from the blob in the 8656 update. Rayman has put out some blob tools for extraction.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Aha perfect, thanks!
Sent from my Transformer TF101 using Tapatalk

paddy01 said:
Aha perfect, thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You might want to update the bootloader flag in the command line too "-bl blob.EBT" I'm not positive but I think this prevents bootloops since the images are flashed with the same bootloader that it is writing.
sent from my cyanogen(mod) vision

gee one said:
You might want to update the bootloader flag in the command line too "-bl blob.EBT" I'm not positive but I think this prevents bootloops since the images are flashed with the same bootloader that it is writing.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thanks a lot for the answers. I haven't got around to do this yet so I have some further questions.. is there a way to do this without wiping the device ?
Also it seems like his Transformer think it's a mobile phone.. eh yea it has like EMEI column and stuff in the information tab.. will the bootloader fix that too ?
the update to 8.6.5.9 didn't appear automatically so we are currently manually updating it to that release.. might fix things.. we'll see..
Edit1: NM! the update to 8.6.5.9 fixed all the issues that were previously

Related

Firmware update Teamwin Issues...?

Ok so I have the update from Asus, I'm rooted with an unlocked bootloader and TW recovery on .17
Everytime I try and flash the zip, it fails. I have rootkeeper and I also tried flashing the second zip file that's inside the first zip. It fails almost immediately while verifying its size or whatnot.
I think I read that trying to flash CWM over TW could brick. Do I need to or is there a way to relock the bootloader?
Thanks guys!
Sent from my ADR6425LVW using xda premium
dopediculous said:
Ok so I have the update from Asus, I'm rooted with an unlocked bootloader and TW recovery on .17
Everytime I try and flash the zip, it fails. I have rootkeeper and I also tried flashing the second zip file that's inside the first zip. It fails almost immediately while verifying its size or whatnot.
I think I read that trying to flash CWM over TW could brick. Do I need to or is there a way to relock the bootloader?
Thanks guys!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You wont brick you're tablet if you switch recoveries, and you also don't flash them . Either way if your flashing stock Asus firmware in CWM read up and make sure you do it right. I bricked my tf300 trying to install the us .29 update. Haha
Sent from my ADR6300 using Tapatalk 2
Since you went through the trouble to help out the OP, I'll help you a bit. Technically, you do flash recoveries. How else would they get on the flash memory chips? Just because you don't flash recoveries through a recovery doesn't mean the process of installing them gets a new name.
Flashing = writing images/files to flash memory. How you do it doesn't matter.
I'm so sorry for my wording. guess I should have made it so a complete retard could follow what I was asking... I had zero time to write this question and just dumped it out there. Either way, I think you knew what I was saying. So yeah... thanks for the help! ← sarcasm? Naaaah....
Also, its kinda interesting how when you root devices using methods like ADB, to get a recovery.img on the system, the command is usually something like " fastboot FLASH recovery recovery.img "
Don't ya think...?
Sent from my ASUS Transformer Pad TF300T using xda premium
dopediculous said:
I'm so sorry for my wording. guess I should have made it so a complete retard could follow what I was asking... I had zero time to write this question and just dumped it out there. Either way, I think you knew what I was saying. So yeah... thanks for the help! ← sarcasm? Naaaah....
Also, its kinda interesting how when you root devices using methods like ADB, to get a recovery.img on the system, the command is usually something like " fastboot FLASH recovery recovery.img "
Don't ya think...?
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
I'm not sure how what I said was insulting, but I am quite sorry you took offense to what I said, and felt it was enough to call me a retard for. I do know that the file is flashed, but, like you I was short on time, and meant that you dont flash in in recovery. generally, unless its made to be a temp flash done in recovery.
At least EndlessDissent politely corrected me on my lack of abilty to communicate normally. and informed while doing it!
enomele said:
I'm not sure how what I said was insulting, but I am quite sorry you took offense to what I said, and felt it was enough to call me a retard for. I do know that the file is flashed, but, like you I was short on time, and meant that you dont flash in in recovery. generally, unless its made to be a temp flash done in recovery.
At least EndlessDissent politely corrected me on my lack of abilty to communicate normally. and informed while doing it!
Click to expand...
Click to collapse
All good man. Its not what ya say, its how ya say it and unfortunately via plain text, one can't really tell how ya meant to come off sounding. My apologies. Now can someone give me some guidance on how to get .29 on this thing? Lol
Sent from my ASUS Transformer Pad TF300T using xda premium
Have you checked the md5sum to make sure it matches the correct value? It could be a bad download.
EndlessDissent said:
Have you checked the md5sum to make sure it matches the correct value? It could be a bad download.
Click to expand...
Click to collapse
I haven't, just because I've downloaded it twice already. Just figured it had to be good by the second try :/
Are the md5's posted on the Asus site that ya know? Sorry. Still mad busy and can't check for myself just yet. I work for vzw corporate and we all know how slammed the retail locations can be. Ugh. Lmk if ya can. I appreciate everything you guys!
Sent from my ASUS Transformer Pad TF300T using xda premium

Need people to run adb commands for twrp 4.2

Hey guys!!
We may have a solution to the recovery issue found after updating to the 4.2 build!!
However, someone needs to run some commands in ADB for the TeamWin team.
I am NOT on the 4.2 update or i would do it myself.
But if there is someone on the 4.2 update who isnt very familiar with ADB, i am more than happy to run a TeamViewer remote desktop session to figure this out.
I cannot wait to solve this!
Thanks for reading guys!
elesbb said:
Hey guys!!
We may have a solution to the recovery issue found after updating to the 4.2 build!!
However, someone needs to run some commands in ADB for the TeamWin team.
I am NOT on the 4.2 update or i would do it myself.
But if there is someone on the 4.2 update who isnt very familiar with ADB, i am more than happy to run a TeamViewer remote desktop session to figure this out.
I cannot wait to solve this!
Thanks for reading guys!
Click to expand...
Click to collapse
You don't say what they wanted run.
I will be doing this myself in the next few hours but if someone would like to do it now can they please install terminal emulator from market if you are already on 4.2.1 update and run the following 2 commands and paste the output here.
ls /dev/block
mount
Deleted
flumpster said:
You don't say what they wanted run.
I will be doing this myself in the next few hours but if someone would like to do it now can they please install terminal emulator from market if you are already on 4.2.1 update and run the following 2 commands and paste the output here.
ls /dev/block
mount
Click to expand...
Click to collapse
It's because you need to be on the freenode chat with them while doing it. I don't think it's simply those two commands because they want some commands ran while inside TWRP
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
It's because you need to be on the freenode chat with them while doing it. I don't think it's simply those two commands because they want some commands ran while inside TWRP
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Yea figured that out but can't do it right now. Would help otherwise. The read out from those commands was too long to post. Better to have some who can go freenode to help.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Lol. I give up.
I am one of the devs from the prime forums and was just trying to help you out because I was the person that edited twrp to work on data2sd installs.
I will head back to the prime forums and try to get it to work there instead
flumpster said:
Lol. I give up.
I am one of the devs from the prime forums and was just trying to help you out because I was the person that edited twrp to work on data2sd installs.
I will head back to the prime forums and try to get it to work there instead
Click to expand...
Click to collapse
I'm confused lol. I can't do anything lol. You gotta talk to the guys over at TWRP I was just merely getting volunteers to help out.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ok I have re-updated to 4.2.1 and seem to have a successful way to now to go back and forth between 4.1.1 & 4.2.1
Here is a screenshot of those two commands "ls /dev/block" & "mount" which shows the partitions still in ext4, which I think blows my theory out the door
I have also been contacted by eyeballer to jump into the twrp on freenode chat but just waiting till were both online
pjc21 said:
Ok I have re-updated to 4.2.1 and seem to have a successful way to now to go back and forth between 4.1.1 & 4.2.1
Here is a screenshot of those two commands "ls /dev/block" & "mount" which shows the partitions still in ext4, which I think blows my theory out the door
I have also been contacted by eyeballer to jump into the twrp on freenode chat but just waiting till were both online
Click to expand...
Click to collapse
Awesome paul!! How do you go back and forth between 4.2 and 4.1? Just flash the different .blob files?
Oh also look for Dees_Troy on freenode. He can help as well. Its who i was talking to.
elesbb said:
Awesome paul!! How do you go back and forth between 4.2 and 4.1? Just flash the different .blob files?
Click to expand...
Click to collapse
First I did a clean wipe from twrp then installed WW_epad-user-10.4.2.20.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed that zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification. I clicked and installed and once the system had rebooted into new android 4.2.1 system I get a triangle notification with a downgrade option to 10.4.2.20
---------- Post added at 12:41 PM ---------- Previous post was at 11:45 AM ----------
Hi,
Have just been talking to Dees_Troy and this is what he had to say
<Dees_Troy> We are going to have to update the kernel
<Dees_Troy> The new bootloader changed something about the partition scheme
<Dees_Troy> I will post a test build tomorrow in the 300 twrp thread
<Dees_Troy> Without the new kernel the entire internal emmc chip doesn't show up at all
<Dees_Troy> Having the new kernel will fix it but I won't be able to patch it to allow backup and restore of boot / kernel until we get source
<Dees_Troy> If you hang around another hour I might have time to make a test build
So where getting somewhere now :good:
Hopefully only a matter of hours or days now till we should have a working recovery with 4.2.1
pjc21 said:
First I did a clean wipe from twrp then installed WW_epad-user-10.4.2.20.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed that zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification. I clicked and installed and once the system had rebooted into new android 4.2.1 system I get a triangle notification with a downgrade option to 10.4.2.20
---------- Post added at 12:41 PM ---------- Previous post was at 11:45 AM ----------
Hi,
Have just been talking to Dees_Troy and this is what he had to say
<Dees_Troy> We are going to have to update the kernel
<Dees_Troy> The new bootloader changed something about the partition scheme
<Dees_Troy> I will post a test build tomorrow in the 300 twrp thread
<Dees_Troy> Without the new kernel the entire internal emmc chip doesn't show up at all
<Dees_Troy> Having the new kernel will fix it but I won't be able to patch it to allow backup and restore of boot / kernel until we get source
<Dees_Troy> If you hang around another hour I might have time to make a test build
So where getting somewhere now :good:
Hopefully only a matter of hours or days now till we should have a working recovery with 4.2.1
Click to expand...
Click to collapse
That is some sexy news! At least we will get root again! omg i think i have a hard on now xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Well I've got a long night ahead of me so I'm thinking about flashing the stock recovery and doing the update
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 09:56 PM ---------- Previous post was at 09:44 PM ----------
elesbb said:
That is some sexy news! At least we will get root again! omg i think i have a hard on now xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
+1 x10
Sent from my SAMSUNG-SGH-I747 using xda premium
keep us updated paul!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
keep us updated paul!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Will do, just waiting to hear back about test build :good:
Here is slightly more detailed method of what I did:
What I did is from running CROMI, I booted into twrp and first I did a clean wipe then installed WW_epad-user-10.4.2.20.zip which can be extracted from the WW_epaduser_10_4_2_20_UpdateLauncher.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed EP201_768_SDUPDATE.zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification in the notification menu of loaded android os.
I clicked and installed and once the system had rebooted into new android 4.2.1 system I get another triangle notification in notification menu with a downgrade option to 10.4.2.20.
If you do not get the notification to downgrade back to 4.1.1 you can try copying the WW_epad-user-10.4.2.20.zip to you internal sd card and you should then get notification after a few seconds.
There is no need to boot into stock recovery, just click on the notification in the notification menu that pop up from loaded android os.
You can boot into fastboot and flash twrp if you want but it will be encrypted/unusable so best to wait for the new build of recovery.
Feel like hugging you man... (no homo) appreciate all your doing... and everyone trying to get this thing working.. was wondering. I have only the new bootloader with the weird fastboot... would this be beneficial to me at all? And im willing to try a fastboot of recovery for testing, lol cause ill be able to tell you fairly quickly whether its working for my type of scenario. .
Lemme know
:thumbup:
Sent from my SPH-D710 using Tapatalk 2
Hmmm... I dont know whats going on man... maybe my bootloader is screwed up. It says it writes it. But again. It seems like the tablet just locks up.. that green box over the rck doesnt flash after writing. No download bar or anything.. there any way to reflash the bootloader as writeable? Or maybe an older version as writeable? Damn this sux..
Sent from my SPH-D710 using Tapatalk 2
Goddly said:
Hmmm... I dont know whats going on man... maybe my bootloader is screwed up. It says it writes it. But again. It seems like the tablet just locks up.. that green box over the rck doesnt flash after writing. No download bar or anything.. there any way to reflash the bootloader as writeable? Or maybe an older version as writeable? Damn this sux..
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
After you are flashing that new twrp.blob are you restarting the tablet before trying to go into recovery ?
The flashing just places it to staging area ready to flash on next restart.
As in .. reboot regular? Power button.. after writing completes I cant reboot from command
Sent from my SPH-D710 using Tapatalk 2
---------- Post added at 01:14 AM ---------- Previous post was at 01:12 AM ----------
It just seems like my bootloader is locking up.... im about to throw this thing against the wall.... I cant do anything with it...
Sent from my SPH-D710 using Tapatalk 2
I'm sorry I'm late, but for the future a little trick. If anyone will run commands in terminal emulator, at the end of command like: ls /dev/block type >/sdcard/lsoutput.txt and then you can post or attach this txt file.
Just to make it a little easier.
If you will do logcat with this txt output don't break it because it runs a little longer until it finishes.

[Q] screwed something while installing cromi4.0 need some direction

ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.
kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.
I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app
As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.
Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.
Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:
I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app
I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.
I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app

Bricked my TF300t

i screwed up and tried to change roms after unlocking and the flashing of recovery well after flashing recovery after going to install a rom i hit format and lost everything. that led me to a asus boot up screen that was boolean in other words it kept rebooting itself. dont know what i did other then try a couple recovery tools found in our forums for my tablet that got rid of the constant reboot bu now i am stuck on the asus sreen i dont know if that in a better state then it was, or worse, i am despereate to fix my spendy paper weight , i am willing to make a healthy donation to the person or persons that are willing to give me there time and hard effort to fix it. pm me or email me [email protected] ill give my phone number via email cause i dont have a mic for the pc...
Can this be moved to the QA
wrong section, Sir - this is definitely Q&A!
but you could try to set up fastboot and then flash the latest stock ROM for your SKU (in your case probably US) with the command
fastboot -i 0x0b05 flash staging blob
you can get the blob from the asus site, just unzip it until you get a file called blob who should be about some hundred mbs :good:
Sounds like you just have a boot loop. Boot recovery and flash a custom or stock ROM. Above post should also work, so use that if you prefer fast boot.
Also please ask a moderator to move this to Q&A.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
What the guys above say. You wiped data, so there is no operating system on your tablet. Not bricked or anything.
One tip, never use these tools, learn to do it yourself so you understand what's happening and you don't get scared with these things. There's a thread that explains the process.
Sent from my Nexus 4 using xda app-developers app
Yeah I was gonna say... I feel like this could have been solved with a quick search.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
TF300t
Good time of day. Don't know if there I write, but I have a problem with the boot loader. after a failed firmware solid Asus, clicking on + volume down and up nothing. Saved files through NVFlash not. Is there any way to restore the tablet TF300t?
Sorry for the text using google translator .
jokeridze said:
Good time of day. Don't know if there I write, but I have a problem with the boot loader. after a failed firmware solid Asus, clicking on + volume down and up nothing. Saved files through NVFlash not. Is there any way to restore the tablet TF300t?
Sorry for the text using google translator .
Click to expand...
Click to collapse
Try using Buster's recovery method, but I don't think that would work.
tf300t
cmendonc2 said:
Try using Buster's recovery method, but I don't think that would work.
Click to expand...
Click to collapse
Can you give a link to it?

Error Firmware Update

Hello,
i m trying to update the firmware of my asus tf700t and all i get when i use the power and volume down recovery is the droid that wants to install but then falls over with the exclamation mark. dont know why it wont update. any ideas? any tricks?
thanks
Ben
ben9000 said:
Hello,
i m trying to update the firmware of my asus tf700t and all i get when i use the power and volume down recovery is the droid that wants to install but then falls over with the exclamation mark. dont know why it wont update. any ideas? any tricks?
thanks
Ben
Click to expand...
Click to collapse
Did you download updated firmware, unzip it, rename the zip in the zip appropriately as outlined in guides, put it in the root directory of your external sdcard formatted for FAT32, all before you entered recovery?
elfaure said:
Did you download updated firmware, unzip it, rename the zip in the zip appropriately as outlined in guides, put it in the root directory of your external sdcard formatted for FAT32, all before you entered recovery?
Click to expand...
Click to collapse
yep did all of the above. since my device is unlocked I cant do the ota update. and everytime I run the update from the SD card it shows the red exclamation mark. I reset my tablet but that didn't help. I cant update to anything newer. no matter how I do it (when the tablet shows that there is an update or when I do It with the power button and the volume down)
ben9000 said:
yep did all of the above. since my device is unlocked I cant do the ota update. and everytime I run the update from the SD card it shows the red exclamation mark. I reset my tablet but that didn't help. I cant update to anything newer. no matter how I do it (when the tablet shows that there is an update or when I do It with the power button and the volume down)
Click to expand...
Click to collapse
Tell me all about your system. You said you are unlocked. Lets gather some info for the next guy to help you. Do you have a custom ROM or recovery? Have you ever? Are you rooted? Have you ever upgraded after unlocking this way?
As a fallback, you can try to copy the update.zip file to the root directory of your INTERNAL sdcard and repeat the stock recovery process and see if that works. If not you will have to wait for someone else to help you. I have no experience with unlock, just root. I think you can flash with Goo but I am not at all sure. Wait for some who knows for sure. There is no margin for error when flashing!
@Tylorw1 are you around?
ben9000 said:
Hello,
i m trying to update the firmware of my asus tf700t and all i get when i use the power and volume down recovery is the droid that wants to install but then falls over with the exclamation mark. dont know why it wont update. any ideas? any tricks?
thanks
Ben
Click to expand...
Click to collapse
I am guessing the way you speak you never installed a custom recovery? What version are you on(not 4.2.1 or 4.1.1, but the ROM number) and have you ever flashed a custom ROM? Just wanna get this aired a bit.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
My 2 cents worth: Did you uninstall or freeze any system or Asus apps or anything that came with the tablet? If you did you'll have to restore them or the stock update will fail.
Another question: If you're unlocked, why by all means are you on stock????
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
My 2 cents worth: Did you uninstall or freeze any system or Asus apps or anything that came with the tablet? If you did you'll have to restore them or the stock update will fail.
Another question: If you're unlocked, why by all means are you on stock????
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I agree with you there. I was thinking if he cannot get the stock recovery to work correctly, depending on the boot loader he is on, he could install a custom recovery and flash the stock kernel from there, but until there is more specifics given on his tablet's state a definite way cannot really be given.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
I agree with you there. I was thinking if he cannot get the stock recovery to work correctly, depending on the boot loader he is on, he could install a custom recovery and flash the stock kernel from there, but until there is more specifics given on his tablet's state a definite way cannot really be given.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
well i have to admit that i didnt think that rooting would be that complex/complicated and from my old days with the iphone unlocking always seemed like a good idea. (i know better know.)
i will probably end up rooting it.
the update doesnt work in general....i reset my tablet back to (i think it was ) 4.1.1 and download the 2 versions afterwards but both dont work. the first update i made was OTA before i unlocked. afterwards no update possible.
i have to look up my bootloader later and will post the information.
ben9000 said:
well i have to admit that i didnt think that rooting would be that complex/complicated and from my old days with the iphone unlocking always seemed like a good idea. (i know better know.)
i will probably end up rooting it.
the update doesnt work in general....i reset my tablet back to (i think it was ) 4.1.1 and download the 2 versions afterwards but both dont work. the first update i made was OTA before i unlocked. afterwards no update possible.
i have to look up my bootloader later and will post the information.
Click to expand...
Click to collapse
Iphone unlocking is not android boot loader unlocking. Unlocking an iphone is to make it so you can use it on multiple carriers. Jailbreaking the iphone gives root rights to the user, though the hardware is not very detailed and is not as controllable as on android. Rooting gives root rights and is mostly for backup purposes. Unlocking your boot loader on android(talking TF700 here because they just give you access to your recovery partition, not the whole boot loader) gives you access to write whatever you want to your recovery partition. Kinda like your motherboard bios, for nothing can be done if they become corrupted.
You said you downloaded the zip file, unzipped it once, stuck it on a MicroSD card, and stuck in your tablet and the update popped up and clicked it and it still failed?
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Iphone unlocking is not android boot loader unlocking. Unlocking an iphone is to make it so you can use it on multiple carriers. Jailbreaking the iphone gives root rights to the user, though the hardware is not very detailed and is not as controllable as on android. Rooting gives root rights and is mostly for backup purposes. Unlocking your boot loader on android(talking TF700 here because they just give you access to your recovery partition, not the whole boot loader) gives you access to write whatever you want to your recovery partition. Kinda like your motherboard bios, for nothing can be done if they become corrupted.
You said you downloaded the zip file, unzipped it once, stuck it on a MicroSD card, and stuck in your tablet and the update popped up and clicked it and it still failed?
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
ahhh i understand...thank you.
and yes. unzipped it...put it on sd card....then in the lower right corner where the time is and where it tells me that is downloading files it told me that an update is found and ready to be installed and if i want to install it. i clicked yes....it shut down and started up with the droid all happy....and then it fell over with the red exclamation mark.
i guess i will just root it...and hope that i wont brick it.
ben9000 said:
ahhh i understand...thank you.
and yes. unzipped it...put it on sd card....then in the lower right corner where the time is and where it tells me that is downloading files it told me that an update is found and ready to be installed and if i want to install it. i clicked yes....it shut down and started up with the droid all happy....and then it fell over with the red exclamation mark.
i guess i will just root it...and hope that i wont brick it.
Click to expand...
Click to collapse
Rooting wont fix the problem. May I ask, since you mentioned something about is in the op, did you use the unlock tool from ASUS? Meaning when the tablet boots is says "This Device is unlocked" in the upper left hand corner?
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Rooting wont fix the problem. May I ask, since you mentioned something about is in the op, did you use the unlock tool from ASUS? Meaning when the tablet boots is says "This Device is unlocked" in the upper left hand corner?
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Thats what i did. so yes it says the device is unlocked in the upper left hand corner. does that have any influence on things?
ben9000 said:
Thats what i did. so yes it says the device is unlocked in the upper left hand corner. does that have any influence on things?
Click to expand...
Click to collapse
It allows you to access the recovery partition. What version of android are you on?
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
It allows you to access the recovery partition. What version of android are you on?
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
you mean 4.1.1? or the bootloader version?
ben9000 said:
you mean 4.1.1? or the bootloader version?
Click to expand...
Click to collapse
Ok then you need to root, then download GooManager. Using Goomanager, install TWRP, which is a custom recovery. Boot into recovery and flash the stock ROM from there. Then it will wipe out TWRP and you will be 100% stock again with new boot loader and recovery.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Tylorw1 said:
Ok then you need to root, then download GooManager. Using Goomanager, install TWRP, which is a custom recovery. Boot into recovery and flash the stock ROM from there. Then it will wipe out TWRP and you will be 100% stock again with new boot loader and recovery.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Thanks for taking over @Tylorw1.
Ok. so.....magic!
i got it to work. the trick was to copy the file to the internal memory. (i did that before i wiped my system and it didnt work then and now i just tried it again out of desperation and it worked). i was suprised since i expected the red exclamation mark again. so i m officially on 4.2.1
thank you very much.
Ben
ben9000 said:
Ok. so.....magic!
i got it to work. the trick was to copy the file to the internal memory. (i did that before i wiped my system and it didnt work then and now i just tried it again out of desperation and it worked). i was suprised since i expected the red exclamation mark again. so i m officially on 4.2.1
thank you very much.
Ben
Click to expand...
Click to collapse
Awesome! Glad I could help. Please thank my meter (click the thanks button). Its always a good thing to know more than one way to do something. _that 's a trick not well published.
[Edit] If it worked on your internal memory after the wipe but still didn't on your external memory, then something is wrong with the external sdcard. Its either not FAT32 or its corrupt and you should consider reformatting it with GNU GParted (live). On Windows, you'll need to download the iso image and burn that to a CD or DVD, which makes it bootable. Then all you may possibly have to do is reorder your boot devices in your BIOS so the CD/DVD comes before the HDD so if you have a bootable disk in the player at boot it will boot from CD/DVD. Stick it in there and try to boot off it first. Some (most?) newer PCs should already have this BIOS boot order as stock. If not, change it.
Alternately, a better or more convenient option if your PC supports it would be do basically the same thing as above except flash the iso to a flash thumb drive and boot from that. Your choice. I use a free Windows program called Astroburn Lite which can burn or flash iso's to either media. Does files too.
elfaure said:
Awesome! Glad I could help. Please thank my meter (click the thanks button). Its always a good thing to know more than one way to do something. _that 's a trick not well published.
[Edit] If it worked on your internal memory after the wipe but still didn't on your external memory, then something is wrong with the external sdcard. Its either not FAT32 or its corrupt and you should consider reformatting it with GNU GParted (live). On Windows, you'll need to download the iso image and burn that to a CD or DVD, which makes it bootable. Then all you may possibly have to do is reorder your boot devices in your BIOS so the CD/DVD comes before the HDD so if you have a bootable disk in the player at boot it will boot from CD/DVD. Stick it in there and try to boot off it first. Some (most?) newer PCs should already have this BIOS boot order as stock. If not, change it.
Alternately, a better or more convenient option if your PC supports it would be do basically the same thing as above except flash the iso to a flash thumb drive and boot from that. Your choice. I use a free Windows program called Astroburn Lite which can burn or flash iso's to either media. Does files too.
Click to expand...
Click to collapse
alright...i looked and looked but cant find the thank you button...could you give me a little hint on where to find it?
ben9000 said:
alright...i looked and looked but cant find the thank you button...could you give me a little hint on where to find it?
Click to expand...
Click to collapse
LOL Lower left corner of any of my replies

Categories

Resources