Lifesaver needed - Screwed my Infinity? - Asus Transformer TF700

Hi all,
Firstly apologies if this is posted in the wrong place......
I think I might have messed up my Transformer infinity but hoping to see some light at the tunnel.
When I got my tablet I rooted it and unlocked the bootloader (wish I hadn't done that). All of that went fine and I got it all set-up perfectly. I then tried to use CWM to make a back-up of the ROM which didn't work. I read a little online and got the impression that CWM doesn't work as it does with most android devices and then read about being able to get to recovery mode (where I assumed I could make a back-up) using an app called Transformer Pad Recovery Tool so I ran this......BOOM!!!!
My Infinity will now not boot and I have the following....
Normal Boot
Sticks at the first Asus Logo with the white 'Device is Unlocked' text
Powering on with Power & Vol DOWN pressed.
Hangs on the Asus logo with.......
'Android cardu-user bootloader <2.10e> released by "US_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernal image
but it doesn't do anything further
Powering on with Power & Vol UP pressed
Tablet goes black screen but windows picks it up as an APX device whereas before it wouldn't pick it up at all. I also have it listed in device manager as 'Asus Transformer TF700 APX interface'
I'm guessing that the APX connection is my only potential route to salvation but I don't know where to go from here. I can't seem access fastboot on the tablet itself and am I right in thinking I can't push anything to it through the PC without this?
- I've read about NVflash but apparently this only works if already on the device before it's KO'd? (I wish I'd have read this article before the recovery app one)
- I've also read somewhere that I can copy the stock blob file to an sd card and then reboot the tablet it will recover from there but it doesn't seem to work (I've tried it with both the blob & meta inf folder and with the zip file)
I'm really worried becuase I can't return it now and I may have messed up big time. I've been reading loads online but can't find a specific answer for my dilema and I'm trying to avoid experimenting too much in case I make things worse.
Can anyone help point me in the right direction?
Thanks

I am sorry mate but it looks like your device it's stuck in the so called "recovery boot loop" and this happened mostly because you have used that app, wich btw was already known for causing bricks and you can find more than one thread warning about it. AFAIK there's no fix for that yet, at least not without NvFlash so it seems that the only way to fix it is sending the device to Asus and pay for the repairs (some users said they paid 250$ for this).

ahh crap. Getting a warranty repair could be fun as well because I'm in the UK using a US model and they haven't even released here. Is it the sort of thing where a solution might come out in the near future or would that just be wishful thinking?
BTW - Edit: The app was called 'Transformer reboot to recovery so everyone steer clear of that as well

It's strange how that app works for some (I can use it without problem) and causes others to get in this "recovery bootloop"... I just don't understand that...
Man, it really sucks that you didn't install NVFlash.
So there is nothing that he can do even though APX mode is working? When I last read of this problem, I thought that the person couldn't even get APX mode working.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
It's strange how that app works for some (I can use it without problem) and causes others to get in this "recovery bootloop"... I just don't understand that...
Man, it really sucks that you didn't install NVFlash.
So there is nothing that he can do even though APX mode is working? When I last read of this problem, I thought that the person couldn't even get APX mode working.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Sadly the APX mode is useless for users without working NvFlash,so considering that OP is on .30 bootloader and didn't used the nvflash tool to backup the needed files, then for him Asus is the only solution, at least for now.

cwm works fine on the infinity. my guess is you were using rom manager which does NOT work on the infinity.
there are several guides posted here to walk people through the recovery/backup process.
I would suggest reading through all of them to see if there is anything you can try.
did you even install cwm through fastboot before running these apps?

DNO1978 said:
ahh crap. Getting a warranty repair could be fun as well because I'm in the UK using a US model and they haven't even released here. Is it the sort of thing where a solution might come out in the near future or would that just be wishful thinking?
BTW - Edit: The app was called 'Transformer reboot to recovery so everyone steer clear of that as well
Click to expand...
Click to collapse
Of course they have been released here... they were released around 3 weeks ago.

hshah said:
Of course they have been released here... they were released around 3 weeks ago.
Click to expand...
Click to collapse
oops....of course. I remember seeing the gold ones for sale but not the Grey
Well I've submitted my return form now and will be waiting to take the hit from Asus. I'm sure it will be an expensive lesson to learn!!
"Kiddies to avoid bricking your brand new Asus Infinity in two seconds - Make sure you read EVERYTHING before doing ANYTHING!"
<walks away with his head down in shame> :crying:

DNO1978 said:
oops....of course. I remember seeing the gold ones for sale but not the Grey
Well I've submitted my return form now and will be waiting to take the hit from Asus. I'm sure it will be an expensive lesson to learn!!
"Kiddies to avoid bricking your brand new Asus Infinity in two seconds - Make sure you read EVERYTHING before doing ANYTHING!"
<walks away with his head down in shame> :crying:
Click to expand...
Click to collapse
Id hate to have to see you do that. Have you tried to flash something from recovery, or reinstall recovery from fastboot (e.g. fastboot flash staging twrp.blob), or reflashing the firmware?

petavium
rightonred said:
Id hate to have to see you do that. Have you tried to flash something from recovery, or reinstall recovery from fastboot (e.g. fastboot flash staging twrp.blob), or reflashing the firmware?
Click to expand...
Click to collapse
Yep, fastboot wont pick the device up attached to the computer. It just hangs at waiting for device. I decided just to send it off as I needed it fixed quick.....pretty sure a solution will turn up the day I get it back
At least it's a chance to test out the customer services in turning it around and how much they charge......

DNO1978 said:
Yep, fastboot wont pick the device up attached to the computer. It just hangs at waiting for device. I decided just to send it off as I needed it fixed quick.....pretty sure a solution will turn up the day I get it back
At least it's a chance to test out the customer services in turning it around and how much they charge......
Click to expand...
Click to collapse
Did Asus repair your table? I have to repair mine because the same brick and I would know how much cost :fingers-crossed:

They repaired it and they didn't charge me!

DNO1978 said:
They repaired it and they didn't charge me!
Click to expand...
Click to collapse
They reflashed your bootloader?
I hope to have your luck
Congrats! :good:

Related

Bricked trying to flash CWM recovery with official JB Firmware.. Help?

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.

[Q] Definitely bricked asus tf300t

Hello all, I just recently bought a tf300t, unlocked it, installed cwm 5.5.0.4 for ics, and then updated to jellybean hydro, then installed cwm 6.
Afterwards, just recently noticed that CM 10 nightlies came out, so i updated to it. I went through step by step, and DID NOT USE rom manager. I went into straight recovery mode. It installed perfectly fine, but when i reboot, it would get stuck at the initial asus splash screen. At first I was able to get into RCK. I became extremely upset, fell asleep and the device eventually died, because it wouldn't turn off, it would constantly boot loop. The next morning, I plugged it in, and it would not even get into RCK, but it would show the options for fastboot, RCK, and cold boot. So, just to restate. Was able to get into RCK, device died, then would not boot into RCK. So then I ran fastboot, and that completely stopped the device from showing ANY options when holding power + volume down. I can not get to RCK or fastboot.
So all in all my device is legitimately stuck at the initial asus boot screen, and NOTHING happens when I hold power + volume down.
Anybody got some ideas? I'm going to japan soon, i'll try and stay in touch. Someone on the forums named Neroga will keep this updated for me while I'm in transit, i'm military and ridiculously busy.
thanks all
just flash stock ROM with fastboot. this should work.
I've tried multiple times. No menu pops up with power + volume down. Literally just hangs on the unlocked screen. I can put it in APX mode or whatever it's called but I heard that nvflash isn't working for the tf300, yet.
Sent from my Motorola Atrix 4G
Blubberor said:
just flash stock ROM with fastboot. this should work.
Click to expand...
Click to collapse
Neroga said:
I've tried multiple times. No menu pops up with power + volume down. Literally just hangs on the unlocked screen. I can put it in APX mode or whatever it's called but I heard that nvflash isn't working for the tf300, yet.
Sent from my Motorola Atrix 4G
Click to expand...
Click to collapse
What neroga said, we can't get to the menu to choose fastboot.
Velict said:
What neroga said, we can't get to the menu to choose fastboot.
Click to expand...
Click to collapse
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
‏@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck! (and PLEASE don't come up with a solution while mine is in repair :laugh:
Sphinix said:
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
‏@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck! (and PLEASE don't come up with a solution while mine is in repair :laugh:
Click to expand...
Click to collapse
I think it really depends on where the tablet is shipped for RMA because mine got reflashed for free I didn't even have to pay shipping or diagnostic costs.
sparky28000 said:
I think it really depends on where the tablet is shipped for RMA because mine got reflashed for free I didn't even have to pay shipping or diagnostic costs.
Click to expand...
Click to collapse
Wow, that's great. I think they might notice the "bootloader unlocked" in the top right corner though... Anyway: I don't really mind paying, it's like paying for a lesson learned
Mine is going to the Czech Republic. Where did yours go to?
Sphinix said:
Wow, that's great. I think they might notice the "bootloader unlocked" in the top right corner though... Anyway: I don't really mind paying, it's like paying for a lesson learned
Mine is going to the Czech Republic. Where did yours go to?
Click to expand...
Click to collapse
Czech Republic also and mine was obviously unlocked. With some luck they will just perform a "BIOS upgrade" and repair it for free. Did take them about 3 weeks though. And if it makes any difference I did lie about bricking it myself. I told them that the official update went wrong and bricked my device.
I'm stucked at Asus logo but I can go into recovery and fastbood. There is something that I can do to repair my tablet?
Sphinix said:
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
‏@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck! (and PLEASE don't come up with a solution while mine is in repair :laugh:
Click to expand...
Click to collapse
I knew NVFLASH wasn't going to work, since you basically need to backup your device with it, then you'll be unbrickable. The whole point of NVFLASH is BEFORE you decide to mess with your tablet, you make sure you have a failsafe, which is NVFLASH. Since the whole tablet is completely locked out, it won't work. Idont understand why asus would make a device that completely locks itself out. Even on a normal everyday computer, the bios can be completely reinstalled.
Why can't firmware?
I just sent the tf300t in for RMA. UPS $27 USD for shipping. I"ll keep everyone updated along with whoever else probably has threads like this open, especially for theTF300t
For anyone who comes across this thread, let me recap on what you should do if you have a TF300t, or tf700. DO NOT go to jellybean yet. I honestly suggest waiting for CM10 nightly to become more stable. Also, wait for nvflash for these devices. With that tool you'll become unbrickable.
Velict said:
I just sent the tf300t in for RMA. UPS $27 USD for shipping. I"ll keep everyone updated along with whoever else probably has threads like this open, especially for theTF300t
For anyone who comes across this thread, let me recap on what you should do if you have a TF300t, or tf700. DO NOT go to jellybean yet. I honestly suggest waiting for CM10 nightly to become more stable. Also, wait for nvflash for these devices. With that tool you'll become unbrickable.
Click to expand...
Click to collapse
Is there any way to stop the JB update notification? I set the postpone to one day but it keeps popping up all the time!
Velict said:
I just sent the tf300t in for RMA. UPS $27 USD for shipping. I"ll keep everyone updated along with whoever else probably has threads like this open, especially for theTF300t
For anyone who comes across this thread, let me recap on what you should do if you have a TF300t, or tf700. DO NOT go to jellybean yet. I honestly suggest waiting for CM10 nightly to become more stable. Also, wait for nvflash for these devices. With that tool you'll become unbrickable.
Click to expand...
Click to collapse
That's a good advice/warning , considering that the Jelly Bean bootloader is completely incompatible with CM9/CM10/AOKP and all derivatives that are designed around the ICS kernel. Hope they find a solution for those who already jumped on the Asus JB train.
Skickat från min Transformer Pad TF300T
solefero69 said:
I'm stucked at Asus logo but I can go into recovery and fastbood. There is something that I can do to repair my tablet?
Click to expand...
Click to collapse
I am having the same problem and the whole thing is so confusing that I am loosing hope to get my Transformer tf300gt working again, Did you managed to have yours sorted out.
Regards,
Yves
I had this happen once, but continuously pressing Vol- & Power got me into bootloader eventualy. It took "forever" for my feeling, may be 20-30 seconds, but it booted to the bootloader.
Ti2 said:
I had this happen once, but continuously pressing Vol- & Power got me into bootloader eventualy. It took "forever" for my feeling, may be 20-30 seconds, but it booted to the bootloader.
Click to expand...
Click to collapse
I just went through a brick scenario when trying to get data2sd working with cleanrom 3.3 after many bootloops i was able to install the stock rom. I am going to unlock and reinstall cleanrombut first going to back it with nvflash. I hate the feeling ofnot knowing if the tablet will stay a brick or not.

Bricked my TF300T

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.

TWRP ecrypted after CROMI update HELP!

Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
cubaniche1 said:
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
Click to expand...
Click to collapse
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
jimpmc said:
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
Click to expand...
Click to collapse
Hey thanks for the reply! Actually, no I was not installing 4.2. I would like to install a newer version of twrp but I cant do anything in twrp because it says its encrypted. I did read that other thread but all the options given are not available to me. I cant get to fastboot.
BUT heres an update:
I got the PC to recognize my device as a Transformer. But I couldn't get the naked drivers nor the newer Asus drivers to work. So I modified the .ini file for both the MTP install and USB driver install to include the Hardware ID shown in windows under device manager properties for the device. Basically I modded the .ini so that it also looks for the device ID, then saved and had windows look at the folder I gain to install the driver and this time is installed. So now I am going to try to use a fastboot command....Ill update if this works. Otherwise I may need to try adb and Im a total newb at adb...
UPDATE:
Got the driver installed but 2 issues:
1: Device manager says Device Cannot Start
2: I cant get recovery menu to show. Tablet goes right into TWRP recovery after looping through the ASUS boot screen twice.
I am stumped. I don't want to give up but I think I may have to
UPDATE
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
cubaniche1 said:
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
Click to expand...
Click to collapse
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Nexus 10 has it's drawbacks too, I love my TF300T.
UPDATE:
Installed new mainboard and got her back up and running quickly. Already updated to 4.2.1. I like it. Well done ASUS!
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Lol. I love my TF300T. Sure, i can buy a better tablet but I would also have to spend a lot more money. I've only got $299 invested in my 32gb tablet plus $49 in my dock. I'm a happy camper. My tablet , when connected to the dock, will last almost twice as long as the Nexus on one charge. I can also keep using the tablet while the dock is charging. I really never even need to put the tablet itself into the charger. You can't do that with the more expensive Nexus 10.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Have you added the patch yet? This will allow TWRP to pick up your sd card.
I tried flashing the patched one via fastboot but it did not seem to take. Its still encrypted. I'm thinking its not flashing properly. I'm not the only one having this issue. Hopefully I can just wait it out till a fix is found. I'm afriad of screwing it up to where its completely unuseable.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] Bootloader error / Soft brick

So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Try writing in smaller paragraphs - that is really hard to read
From what I can tell you appear to have flashed something form a nexus into your bootloader partition?
If so I think you can say goodbye to the device unless you previously did the flatline nvflash backups to make it unbrickable?
ah wait! you said you have fastboot? Can you fastboot devices from a cmd prompt and get a device id back?
NobleXperiment said:
So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Click to expand...
Click to collapse
Wow, you beat me on the unlock your new device within one day of usage...
You can see the post above to see if you still can use your fastboot. If your fastboot is still working, you can download the full latest firmware from Asus website and install it with fastboot command...good luck....:fingers-crossed:
Yeah sorry bout the length, i know a lot of times everyone asks for more details so i figured id get that out of the way, honestly didnt even know if i would get a response so much appreciated, i will be home shortly to try the download, def a huge failblog learning experience at best. when you do that what exactly is the point of making two blops. ?
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
NobleXperiment said:
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
Click to expand...
Click to collapse
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
sbdags said:
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
Click to expand...
Click to collapse
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
NobleXperiment said:
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
Click to expand...
Click to collapse
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
berndblb said:
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
NobleXperiment said:
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
Click to expand...
Click to collapse
You tried all the links? I use Global and it works.
Which SKU are you? I think I have the US .10 firmware lying around somewhere - can upload it to Dropbox.
Sent from my K00C using Tapatalk
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
NobleXperiment said:
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
Click to expand...
Click to collapse
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
berndblb said:
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
It makes it unbrickable. You can recover from any brick with the nvflash blob files.
NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
Entirely up to you. You were a half-step away from hard bricking your tablet. If this is a typical pattern for you (try first - ask/read later) it may be a very good idea to get those blobs squared away
You have to flash a modded bootloader and modded recovery just for generating the blobs (and flash back afterwards), so it may be a good idea to get this done before you get everything set up.
Sent from my K00C using Tapatalk
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
NobleXperiment said:
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
Click to expand...
Click to collapse
Follow these instructions to the letter.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
I anything is unclear, ask in this thread:
http://forum.xda-developers.com/showthread.php?t=1901479
Sent from my K00C using Tapatalk
So yeah while i thought the upgrade to 4.2.1 was a lucky mistake but now i cant use kingo to root my phone, any suggestions without having to go back to an earlier firmware?
or would getting the nvflash unroot the device again anyway?

Categories

Resources