Related
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.
Hi there xda-community!
I'm a little bit shocked - It seems I managed to break my Asus TF300t while trying to install Cyanogenmod (latest version).
I followed the guide in the wiki "Asus_Transformer_Pad_TF300T:_Full_Update_Guide"
And I'm already at the last step where you should reboot your tablet but I'm stuck on the Asus-Booting Screen. I can't even turn the tablet off. (Automatically reboots)
It says in the top left corner "The Device is UnLocked." followed by a large ASUS-Logo in the middle and a small NVIDIA TEGRA logo in the lower right corner.
I'm still able to go into the recovery and already tried to install the ROM again. But I'm still stuck at the loading screen.
I'm not an expert on this topic but still thought I would be able to install CM - but right now I have no idea what to do next. I don't even know how to turn my pad off.
I would greatly appreciate any help!
Nijin said:
Hi there xda-community!
I'm a little bit shocked - It seems I managed to break my Asus TF300t while trying to install Cyanogenmod (latest version).
I followed the guide in the wiki "Asus_Transformer_Pad_TF300T:_Full_Update_Guide"
And I'm already at the last step where you should reboot your tablet but I'm stuck on the Asus-Booting Screen. I can't even turn the tablet off. (Automatically reboots)
It says in the top left corner "The Device is UnLocked." followed by a large ASUS-Logo in the middle and a small NVIDIA TEGRA logo in the lower right corner.
I'm still able to go into the recovery and already tried to install the ROM again. But I'm still stuck at the loading screen.
I'm not an expert on this topic but still thought I would be able to install CM - but right now I have no idea what to do next. I don't even know how to turn my pad off.
I would greatly appreciate any help!
Click to expand...
Click to collapse
More info needed. What version of recovery are you using? The last time you successfully booted, were you on ICS or jb? What version of cm are you trying to flash?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
More info needed. What version of recovery are you using? The last time you successfully booted, were you on ICS or jb? What version of cm are you trying to flash?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
My guess, as many went before him: Official JB update, adepted bootloader and then... A wipe.
The end! All you can do now is ship it to ASUS to have it fixed. I had mine back yesterday, they fixed it under warranty within one week. But this is Europe, I've read different (horror ) stories here, ranging from tablet in RMA for more than 1.5 month, up to replacing the mainboard (charging a total of 200 dollar).
If you are in Europe, ship it back, lie, say it's stuck after JB upgrade, they will fix it (fast!).
Good luck!
funnel71 said:
More info needed. What version of recovery are you using? The last time you successfully booted, were you on ICS or jb? What version of cm are you trying to flash?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Hi funnel, thanks for your help - sorry for missing the Infos.
I'm using "CWM-based Recovery v6.0.1.3" (showthread.php?t=1668173). Last time I booted the stock JellyBean Firmware. I'm trying to flash "cm-10-20120920-NIGHTLY-tf300t.zip"
Sphinix said:
My guess, as many went before him: Official JB update, adepted bootloader and then... A wipe.
The end! All you can do now is ship it to ASUS to have it fixed. I had mine back yesterday, they fixed it under warranty within one week. But this is Europe, I've read different (horror ) stories here, ranging from tablet in RMA for more than 1.5 month, up to replacing the mainboard (charging a total of 200 dollar).
If you are in Europe, ship it back, lie, say it's stuck after JB upgrade, they will fix it (fast!).
Good luck!
Click to expand...
Click to collapse
Oh.. this doesn't sound good. What would be the way I should have taken?
I did now flash (after a full wipe + cache wipe) the official firmware (from ASUS Website).
THIS DID WORK!!!
I am now back with my pad on the official ROM. (With an unlocked bootloader - but otherwise like it was when I bought it.)
This fixed my problem but I'm still wondering where I went wrong... Could someone explain me what I did wrong and how do prevent it next time?
Thanks for your help!
Nijin said:
Hi funnel, thanks for your help - sorry for missing the Infos.
I'm using "CWM-based Recovery v6.0.1.3" (showthread.php?t=1668173). Last time I booted the stock JellyBean Firmware. I'm trying to flash "cm-10-20120920-NIGHTLY-tf300t.zip"
Oh.. this doesn't sound good. What would be the way I should have taken?
I did now flash (after a full wipe + cache wipe) the official firmware (from ASUS Website).
THIS DID WORK!!!
I am now back with my pad on the official ROM. (With an unlocked bootloader - but otherwise like it was when I bought it.)
This fixed my problem but I'm still wondering where I went wrong... Could someone explain me what I did wrong and how do prevent it next time?
Thanks for your help!
Click to expand...
Click to collapse
CM10 currently doesn't work with the JB bootloader (which you have since updating) as far as I'm aware, which would probably explain why it went wrong.
Check out Hydro or CleanROM perhaps, both have been updated for new JB bootloader.
mozyman said:
CM10 currently doesn't work with the JB bootloader (which you have since updating) as far as I'm aware, which would probably explain why it went wrong.
Check out Hydro or CleanROM perhaps, both have been updated for new JB bootloader.
Click to expand...
Click to collapse
Ah okay - thanks for the info. I'm now running Hydro ROM and I am very happy with it!
In case someone finds this topic and would like to know which firmware I used to get it back again - it was "ASUS Transformer Pad TF300T Firmware: V10.4.2.13 "
Nijin said:
Ah okay - thanks for the info. I'm now running Hydro ROM and I am very happy with it!
In case someone finds this topic and would like to know which firmware I used to get it back again - it was "ASUS Transformer Pad TF300T Firmware: V10.4.2.13 "
Click to expand...
Click to collapse
Any chance you could give me the steps? My stock TF300T is stuck on the boot-logo now.
I never had a chance to even put a single app on it, just turned it on and let it download JB when I went to work, came home tried to install and BRICK. Can I follow your steps if my bootloader is not unlocked?
Sorry for noob questions but I was so excited for my first tablet and now it's dead, I feel like a kid again when I found out Santa wasn't real
TF300T said:
Any chance you could give me the steps? My stock TF300T is stuck on the boot-logo now.
I never had a chance to even put a single app on it, just turned it on and let it download JB when I went to work, came home tried to install and BRICK. Can I follow your steps if my bootloader is not unlocked?
Sorry for noob questions but I was so excited for my first tablet and now it's dead, I feel like a kid again when I found out Santa wasn't real
Click to expand...
Click to collapse
I'm afraid that you will not be able to follow my steps because I used the CW Recovery. (This can only be installed with an unlocked bootloader (as far as I know)).
But since your bootloader is not unlocked you still have your warranty. I'd suggest to call the ASUS Support Hotline / Mail them and ask if they can help you. In worst case scenario you will have to send them your tablet but should get in repaired for free.
Yeah, ASUS will RMA but I have to pay shipping >.<
Trying to get supplier to just send me a new one, heres to hoping!
TF300T said:
Yeah, ASUS will RMA but I have to pay shipping >.<
Trying to get supplier to just send me a new one, heres to hoping!
Click to expand...
Click to collapse
I don't know if this was mentioned but have you tried to wipe data first? Just a though
T.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I don't know if this was mentioned but have you tried to wipe data first? Just a though
T.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
1. Hold the Power button in for about 5-7 seconds to get it to reboot. (Seems stupid for the device to auto restart, wish I could change that.)
2. After the screen goes black, hold the Power and the Volume Down buttons until you get the words in the upper left corner to say something about hitting the Volume Up to load Recovery (don't hit the volume up, there's no recovery on an locked bootloader).
3. Hit the Volume Down button unless the "Wipe Data" icon is highlighted and then hit the Volume Up to confirm. This will go through the factory reset option and should bring your tablet back to working condition if it's possible.
* if you get the android laying on his back you tried to boot the recovery partition after step 2, just start over and hold the power button down to reset the device and remember do NOT hit the Volume Up button after it restarts until you have hit the Volume Down button to highlight the Wipe Data icon.
Let us know if this works.
-Nate
herschwolf said:
1. Hold the Power button in for about 5-7 seconds to get it to reboot. (Seems stupid for the device to auto restart, wish I could change that.)
2. After the screen goes black, hold the Power and the Volume Down buttons until you get the words in the upper left corner to say something about hitting the Volume Up to load Recovery (don't hit the volume up, there's no recovery on an locked bootloader).
3. Hit the Volume Down button unless the "Wipe Data" icon is highlighted and then hit the Volume Up to confirm. This will go through the factory reset option and should bring your tablet back to working condition if it's possible.
* if you get the android laying on his back you tried to boot the recovery partition after step 2, just start over and hold the power button down to reset the device and remember do NOT hit the Volume Up button after it restarts until you have hit the Volume Down button to highlight the Wipe Data icon.
Let us know if this works.
-Nate
Click to expand...
Click to collapse
I had the same problem trying to install CM10 with the JB bootloader. As soon as you restart after its installed it hangs at the ASUS logo.
I tried wiping everything but my backup and still had no luck. Thanks for this procedure though. I was really scared I bricked it for a bit there. Was especially scared at the thought that I live in the US and would never get lucky enough to have mine replaced under warranty.
So yes I can confirm your procedure will correct the issue.
k4killer said:
I had the same problem trying to install CM10 with the JB bootloader. As soon as you restart after its installed it hangs at the ASUS logo.
I tried wiping everything but my backup and still had no luck. Thanks for this procedure though. I was really scared I bricked it for a bit there. Was especially scared at the thought that I live in the US and would never get lucky enough to have mine replaced under warranty.
So yes I can confirm your procedure will correct the issue.
Click to expand...
Click to collapse
im using CleanROM 2.1 at scottsroms .com
with TWiRP 2.2 ( advice to all CWM users, i was one too, uninstall, install TWRP, TEAM WIN RECOVERY PARTITION)
RUNS smooth..
launcher choice: apex or asus stock
its great...
k4killer said:
I had the same problem trying to install CM10 with the JB bootloader. As soon as you restart after its installed it hangs at the ASUS logo.
I tried wiping everything but my backup and still had no luck. Thanks for this procedure though. I was really scared I bricked it for a bit there. Was especially scared at the thought that I live in the US and would never get lucky enough to have mine replaced under warranty.
So yes I can confirm your procedure will correct the issue.
Click to expand...
Click to collapse
CM10 will not work with the JB Bootloader unfortunately. The bootloader will hang at the ASUS logo because of it. Hopefully there will be some development to correct this issue or a CM10 port into the JB bootloader soon, but until then you have the Stock (which has been rooted), Hydro's ROM, and Scott's CleanROM - which I use and love. It's very minimalistic and easy to install.
-Nate
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:
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.
ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.
kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.
I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app
As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.
Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.
Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:
I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app
I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.
I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app