Related
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
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
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Well u do have APX mode... is there a day to do something with that?
I7
darthvince said:
Hi guys,
So I think I f^&*ed up royally. I got the official jellybean update, but of course, not to be content with what I had, I tried to flash CWM recovery on it using fastboot.
It didn't work. I tried to reboot to recovery and it would just freeze, so I would have to force a hard reboot.
No big deal, right? I'll just flash TWRP. I tried to initiate fastboot again and it would just freeze again...
So I rebooted once again (holding vol down) and tried the factory reset option... surely that would fix my problem, right? WRONG! It tried to boot recovery (which is now a non-working CWM) and it totally sh*t the bed. I cannot boot the tablet now nor will it do anything when I try to hold vol down. It just sits at the boot screen no matter what I do.
If there anything I can do, or am I totally screwed? My bootloader is unlocked, so I believe the warranty is void.
Help, please?
Click to expand...
Click to collapse
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
krhainos said:
Join the club, I think you're victim #4 or 5 at this point.
Check out the last couple posts here : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
As your bootloader is unlocked, like mine -- Asus doesn't have an obligation to help per the "Revised" warranty the Unlocking process warned you about.
Asus does have representatives that hang around here, so give them a holler and see if they'll help. I've e-mailed both Gary Key and Asus_USA about my/our situation.
Click to expand...
Click to collapse
the bold part is where I can really use some help!!!!
have a tf300t, neither unlocked nor rooted atm.... I never got an OTA after purchase, always had to manually download zip and update, i cannot even unlock the damn device!!!! some unknown network error issue, even tough m fully connected ! its begining to irritate me to the core that anyone asking me advice on what to buy , i say straight up that if its asus it will be crap don't buy it!
i can really use some help regarding this.... it looks like some serial number issue..... :'(
ASUS Rep HELP me please!
Paschalis said:
I7
You were locked, got OTA, and then flashed custom recovery?
Or you were unlocked, returned to stock, flashed jb and then custom recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
I've been trying to figure this out. But so far nothing. I've tried flashing cm10 images in fastboot. I built a recovery and used it to try and go back to stock but it give me a mismatch error. I tried flashing cm10 in recovery and everything takes me back to asus screen. Any other ideas I could try?
I would love to be able to use my tablet again.
darthvince said:
You hit the nail on the head with the second guess. I was unlocked, returned to stock, got the OTA update, then tried to install recovery with fast boot. Now bricked. Can't boot, can't get into fast boot or anything. Vol down doesn't do anything. I can get into apx mode, if only I knew what to do with it.
Click to expand...
Click to collapse
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Paschalis said:
Okay.
I am so lucky for now!!!
Same situation but, flashed twice recovery with goo app(twrp), didnt worh, flashed twice again twrp with fastboot, and then flashed cwm with fastboot!
And still bootable!
But recovery dont work!!
Also another user who managed to get cwm to work, had a non working recovery first, but not bricked device!
Why installing custom recovery bricks some users and others dont?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
krhainos said:
Perhaps it has something to do with how the recoveries were flashed. This only happens if you tried to REflash the recovery AFTER applying JB.
I did fastboot -i 0x0B05 flash recovery recovery.img
Some people noticed they didn't have a recovery working, and didn't try reflashing. Those that did, seemed to have bricked.
There seems to be a test recovery floating around in the other thread : http://forum.xda-developers.com/showthread.php?t=1841211&page=2
It seems all the recoveries need to be updated to the new kernel.
Click to expand...
Click to collapse
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Drgravy said:
I tried to flash my recovery the exact same way except it took me about 8 tries before I finally bricked
for those wanting to flash a recovery to the jb OTA it looks like TWRP is going to be updated soon so I would wait till then
Click to expand...
Click to collapse
I have a TWRP version for someone to test here: http://forum.xda-developers.com/showthread.php?t=1843694
Flash with fastboot.
I created an RMA request with Asus, the fellow on the phone says it's bewteen $87 to $100 to repair the OS on a device with an unlocked bootloader. This excludes the cost of you shipping Asus the tablet. However, it includes the cost of labor, diagnostic, and shipping back to you.
For those of you weighing your options, there's one answer.
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Rompf said:
:/ If only i lived in the states i would send it to Asus for 100 bucks if its necessary. Im going to have to check with the Asus representative here in Colombia...
If you do get your tablet fixed please tell us, that would be awesome.
Click to expand...
Click to collapse
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
TF300T in repair in Texas as well...
krhainos said:
If anyone is curious -- I've sent my tablet to Asus but I haven't heard anything other then that they've started to work on it.
Click to expand...
Click to collapse
My TF300T is in Grapevine TX having the same exact thing done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
bjanice44 said:
My TF300T is in Grapevine TX having the same exact hting done as I am bricked at the moment. Can you please let me know what they end up charging you? Have they contacted you at all at this point? Please post updates as I am interested if we both end up with the same charges and repairs. Mine is stuck on the boot screen with no fastboot or adb access.. just like yours.
Click to expand...
Click to collapse
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
krhainos said:
They have not charged me yet, and it's still in Grapevine, TX as well. I'll keep this thread updated too -- a couple people have been posting their experiences over here though : http://forum.xda-developers.com/showthread.php?t=1825265&page=3
Click to expand...
Click to collapse
Thanks
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I'm just curious where the problems are truly coming from. I got the jb update ota, unlocked after and installed cwm recovery with no issues at all. Is it possible the wrong recovery was installed? Ii think v6 cwm is the only one that works with jb.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What I understood is that's a partitioning difference on JB... Bricked mine too, more and more showing up on these boards... I guess the more issues will show up, the bigger the chance we can have someone fix them (Not me, that's for sure )
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
So here is the long story.. Over the summer I had unlocked my bootloader and rooted my tablet. I did have a rom on it but i decided to go back to stock because my family and I were going to go on vacation and I wouldn't have access to a computer if something were to mess up. I then returned home and was going to root it again and install a custom recovery. I tried to plug it in to my laptop and it said that the device had an error and could not be read and that it malfunctioned. I had never seen this before. I could charge it and use it on my keyboard dock correctly but my computer would not recognize it at all. I then contacted ASUS support and they just fed me with bull****. I played their game and reinstalled drivers, factory reset it, tried a different computer, all of that and NOTHING would work. I then sent it to them just to see if they could fix it. They had it for almost 2 months and sent it back because I had unlocked the bootloader. Ever since I had gotten it back, it has been the absolute slowest tablet in the world. It lags 24/7 and it is almost boiled down to a piece of ****. I cannot connect it to a laptop of computer in hopes of putting CM on it to fix it. Can anyone please offer me any advice!!! Is there a way to use an app to somehow root it, should I buy a new usb cord if that could be the case, something??!??!!! FYI my bootloader is still unlocked and I am running stock (US version) 10.4.2.17. Thank you.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Even if you flash stock JB on your tablet, after having CWM or TWRP on it, that shouldn't replace your custom recovery. You should still be able to get into recovery by shutting off the tablet and then booting up holding vol/d and power and then selecting RCK. From there you can flash any ROM you want even if you are no longer rooted.
I'm not 100% about this but i'm pretty sure.
Ramrod421 said:
Even if you flash stock JB on your tablet, after having CWM or TWRP on it, that shouldn't replace your custom recovery. You should still be able to get into recovery by shutting off the tablet and then booting up holding vol/d and power and then selecting RCK. From there you can flash any ROM you want even if you are no longer rooted.
I'm not 100% about this but i'm pretty sure.
Click to expand...
Click to collapse
Actually I think if you flash a stock ROM, your recovery is wiped, but you can put it back easily since you're unlocked. If you made any backups to internal storage, those will stay if you don't wipe the data partition. Flashing stock ROM doesn't erase data, just the system partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Actually I think if you flash a stock ROM, your recovery is wiped, but you can put it back easily since you're unlocked. If you made any backups to internal storage, those will stay if you don't wipe the data partition. Flashing stock ROM doesn't erase data, just the system partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Well I honestly dont care about keeping data or not, its all cloud for me. I got into the recovery and I wasnt able to get past the screen where there is the android logo with the red triangle and a "!" in it. I thought there was some key combination with the power and volume key but i couldnt get to the recovery menu. If i were able to navigate that could I somehow add CWM or TWRP???
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Ramrod421 said:
Even if you flash stock JB on your tablet, after having CWM or TWRP on it, that shouldn't replace your custom recovery. You should still be able to get into recovery by shutting off the tablet and then booting up holding vol/d and power and then selecting RCK. From there you can flash any ROM you want even if you are no longer rooted.
I'm not 100% about this but i'm pretty sure.
Click to expand...
Click to collapse
How would I go about doing that with the stock recovery?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
OK so stock out of the box, you have no recovery. That's why you get the droid with the red triangle when you try to access it. You have none. You must download recovery and flash it in. I recommend twrp. You can find links and instructions in the Dev section.
If you have recovery and flash a stock ROM, you lose it because where recovery is gets written over during flash, but you can easily reload it. That's what I have to do every time Asus releases an update - no sweat.
You must have your bootloader unlocked before you can do anything I just said.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
If you are getting the android with the red triangle then you need to flash recovery again. Sorry about that, I thought it stayed when you flashed stock roms but obviously not.
So yeah, just flash TWRP again and you can flash the ROM of your choice.
funnel71 said:
OK so stock out of the box, you have no recovery. That's why you get the droid with the red triangle when you try to access it. You have none. You must download recovery and flash it in. I recommend twrp. You can find links and instructions in the Dev section.
If you have recovery and flash a stock ROM, you lose it because where recovery is gets written over during flash, but you can easily reload it. That's what I have to do every time Asus releases an update - no sweat.
You must have your bootloader unlocked before you can do anything I just said.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Ramrod421 said:
If you are getting the android with the red triangle then you need to flash recovery again. Sorry about that, I thought it stayed when you flashed stock roms but obviously not.
So yeah, just flash TWRP again and you can flash the ROM of your choice.
Click to expand...
Click to collapse
Ok I understand what you guys are saying and all and I have looked up ways to root and recovery my tablet. But I cannot connect this to a computer! I cannot make a stable connection for some reason, therefore I cannot access ADB to somehow flash the recovery to my tablet. I am stuck with the stock recovery with an unlocked bootloader and can't connect to a computer at all.
dtraini7 said:
Ok I understand what you guys are saying and all and I have looked up ways to root and recovery my tablet. But I cannot connect this to a computer! I cannot make a stable connection for some reason, therefore I cannot access ADB to somehow flash the recovery to my tablet. I am stuck with the stock recovery with an unlocked bootloader and can't connect to a computer at all.
Click to expand...
Click to collapse
Then do it right on the tablet. Instructions to do that are on game same site where you get twrp.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Then do it right on the tablet. Instructions to do that are on game same site where you get twrp.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I cannot do it right on my tablet because I am not rooted.
This is what I used. http://www.teamw.in/project/twrp2/97
ADB can also be done over wifi. I've never used it but know quite a few who have.
wetbiker7 said:
ADB can also be done over wifi. I've never used it but know quite a few who have.
Click to expand...
Click to collapse
Really? I will have to look into that. Thanks.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
No problem. It's available on the Market.
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2
wetbiker7 said:
No problem. It's available on the Market.
Sent from my Transformer Pad TF300T using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
Unfortunately you need root to attempt that method
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
dtraini7 said:
Unfortunately you need root to attempt that method
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I just did a quick search on Google and there looks to be a way to use wireless adb on non rooted devices. You may be able to get it done if you do a little reading. Not sure if it'll work on our tablet. It's worth checking into though.
Well I just got a new USB connector for the TF300 and it now works!!! I rooted and installed cm10.1 and all is well Mods can delete
Sent from my Nexus 7 using xda app-developers app
So I pretty much bricked my tablet and can't get into the recovery or fastboot menus and now I'm stuck at the Asus logo screen.
I've searched high and low for a way to un-brick my tablet and get it back in working order but no dice...
My question is.... Do you think/know if there will be a way to un-brick these tablets (without NVflash) in the future? I would send it in to ASUS but I literally just received it back from them due to a screen manufacturing defect.
I just wonder if someone out there has managed to do it and hasn't shared their knowledge or if someone is working on something right now.
Hopeful as ever,
Kordman916
What did you do that you bricked your tablet?
I unlocked the tablet and tried installing Twrp recovery on it. It froze every time I tried booting into recovery so I opened the fastboot menu and hit "Wipe Data" now it just sits at the boot screen with "The device is unlocked" in the corner
Kordman916 said:
I unlocked the tablet and tried installing Twrp recovery on it. It froze every time I tried booting into recovery so I opened the fastboot menu and hit "Wipe Data" now it just sits at the boot screen with "The device is unlocked" in the corner
Click to expand...
Click to collapse
i guess you wiped entire your tablet so there is no system to boot.
You are unrecoverable bricked! I'm sorry.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Hazard17 said:
You are unrecoverable bricked! I'm sorry.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Are you serious??? I feel like someone would've come up with a solution by now...
Kordman916 said:
Are you serious??? I feel like someone would've come up with a solution by now...
Click to expand...
Click to collapse
Yeah, I think we are screwed. I have fastboot and recovery, but my recovery is the TWRP that doesn't support 4.2.1. Fastboot says is flashes, but it doesn't. It just hangs.
Without the ability to flash a working recovery, I'm afraid we can't fix it. It sucks, I bought my tablet 11 months ago. Waiting for the warranty to be almost over before i flash it. If I would have waited 2 days, I would be fine.
From what I read, Asus wants between $80 and $200.
i thought this was well know by now but by using that wipe data button you brick, completely. you cannot recover. DO NOT EVER USE "WIPE DATA" in bootloader menu. there needs to be a massive banner or something that says this when you enter the tf300 forums IMO.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Possible Fix?
sevenalive said:
Yeah, I think we are screwed. I have fastboot and recovery, but my recovery is the TWRP that doesn't support 4.2.1. Fastboot says is flashes, but it doesn't. It just hangs.
Without the ability to flash a working recovery, I'm afraid we can't fix it. It sucks, I bought my tablet 11 months ago. Waiting for the warranty to be almost over before i flash it. If I would have waited 2 days, I would be fine.
From what I read, Asus wants between $80 and $200.
Click to expand...
Click to collapse
Have you tried fastboot flashing the latest version of TWRP?
If you haven't tried it yet, I would recommend you follow the instruction in this thread:
http://forum.xda-developers.com/showthread.php?t=2187982
to install a patched TWRP recovery image (2.4.4.0). This should then let you reinstall a copy of the downloadable ROM from the Aus website.
Once you have installed the update you must re-install the same TWRP 2.4.4.0 again because the Asus ROM update over writes the TWRP recovery files.
Good luck!
:good:
Good luck.
markymark567 said:
i thought this was well know by now but by using that wipe data button you brick, completely. You cannot recover. Do not ever use "wipe data" in bootloader menu. There needs to be a massive banner or something that says this when you enter the tf300 forums imo.
Sent from my asus transformer pad tf300t using xda app-developers app
Click to expand...
Click to collapse
why the f*** did asus put that option there if that's all it does??? It should say "click here if you wanna brick your tablet"
Kordman916 said:
why the f*** did asus put that option there if that's all it does??? It should say "click here if you wanna brick your tablet"
Click to expand...
Click to collapse
lol - but who would hit something without knowing what will happen? I wouldn't dare choose this "wipe data" without knowing, what it means
You can enter wipe data from bootloader menu, when your twrp is working. When your TWRP doesn't exist, wipe data will brick your tablet. So maybe in the future we will be able to install mod which will change icon from Wipe Data to picture with Brick
Kordman916 said:
why the f*** did asus put that option there if that's all it does??? It should say "click here if you wanna brick your tablet"
Click to expand...
Click to collapse
Because it works if your on all stock. and apparently it can work if your twrp is working right, although i say dont even risk it. But im sure it was not known by asus when they put it in there. These tabs are just finiky like that... especially when it comes to recovery
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Because it's fine with their stock firmware. They don't want you to root it and change it, because they didn't take the proper precautions to prevent bricks. I'm sure they also don't mind the free $$$ for fixing bad flashes. There is a reason why unlocking voids their warranty. They want to charge you to fix it.
I honestly can't imagine ASUS replacing the motherboard of the tablet just to fix it they must be doing something software wise.... I just wonder what it is to fix my damn tablet
Kordman916 said:
I honestly can't imagine ASUS replacing the motherboard of the tablet just to fix it they must be doing something software wise.... I just wonder what it is to fix my damn tablet
Click to expand...
Click to collapse
im sure they have the files and knowledge to restore the tablet through apx mode. they probably use something like nvflash actually..
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I think that they shouldn't replace motherboard, they only need replace nand memory. They do this for money!
I imagine it must be easier to train employees how to change the motherboard then to flash. Then just have 1 or 2 guys flash motherboards and sort them.
Or they could just be lying and just hook it up to a computer that sends the special stuff needed to flash unrestricted. Then charge you an insane amount for at most 20-30 minutes.
I'm mailing mine off today, won't get to TX until Tuesday since the weekend is here. But I think I'll get mine back before March is out. I'm not happy about the money. I waited for my warranty to be over before I decided to unlock. I killed it by being stupid. i just hope it's not more then the $87 quoted.
This tablet felt slow, never fast. App switching and soft keyboard lag was a big one. I attributed that to the crap flash memory they put in. IO is just as important as CPU/RAM. I think all owners will agree with that. I believed those that they custom firmware is so much better and the tablet speed is improved. I still do. Just sucks I have to pay quite a bit of money to get it fixed and not having a tablet for a few weeks.