[Q] Rebooting into recovery -- dead Andy ;) - Asus Transformer TF700

I tried rebooting into recovery to perform a factory reset because the update from .21 to .22 doesn't get through, but after POWER+VOL_DOWN and subsequently VOL_UP, I am confronted with a dead Andy -- with a hatch open and a red warning triangle. The unit reboots itself after while and gets into Android itself OK.
This is a damaged recovery, right? How do I go about fixing this? Fastboot (seen some threads in the G1 forum).... Amon's recovery (not available for the T700 yet, I think). I've never had this before, so I am at a loss on how to progress.
Is there CWM available yet, or is that not an option if your recovery is unbootable in the first place?
Andy is dying! Help me help him!
.....
Uhhh....... thanks!

MartyHulskemper said:
I tried rebooting into recovery to perform a factory reset because the update from .21 to .22 doesn't get through, but after POWER+VOL_DOWN and subsequently VOL_UP, I am confronted with a dead Andy -- with a hatch open and a red warning triangle. The unit reboots itself after while and gets into Android itself OK.
This is a damaged recovery, right? How do I go about fixing this? Fastboot (seen some threads in the G1 forum).... Amon's recovery (not available for the T700 yet, I think). I've never had this before, so I am at a loss on how to progress.
Is there CWM available yet, or is that not an option if your recovery is unbootable in the first place?
Andy is dying! Help me help him!
.....
Uhhh....... thanks!
Click to expand...
Click to collapse
Not sure about recovering the stock recovery, but installing a non-stock one requires an unlocked bootloader which we dont have yet.

Jotokun said:
Not sure about recovering the stock recovery, but installing a non-stock one requires an unlocked bootloader which we dont have yet.
Click to expand...
Click to collapse
Thanks for the reply -- indeed, all the guides I've read to get to CWM or Amon Ra's recovery all revolve around getting that bootloader unlocked. I sure hope development in the TF700 picks up soon, and fast, and we can get some luvin' on this baby. This obviously is not that critical an issue, but I would like to flash a custom recovery and at least have a nandroid backup when the proverbial excrement hits the ditto ventilator.

MartyHulskemper said:
I tried rebooting into recovery to perform a factory reset because the update from .21 to .22 doesn't get through, but after POWER+VOL_DOWN and subsequently VOL_UP, I am confronted with a dead Andy -- with a hatch open and a red warning triangle. The unit reboots itself after while and gets into Android itself OK.
This is a damaged recovery, right? How do I go about fixing this? Fastboot (seen some threads in the G1 forum).... Amon's recovery (not available for the T700 yet, I think). I've never had this before, so I am at a loss on how to progress.
Is there CWM available yet, or is that not an option if your recovery is unbootable in the first place?
Andy is dying! Help me help him!
.....
Uhhh....... thanks!
Click to expand...
Click to collapse
It's normal, take out your SDcard.

Buggyroach said:
It's normal, take out your SDcard.
Click to expand...
Click to collapse
Thanks for the suggestion, but when I have the SD card removed, recovery boots as it should with the report that the "signature has matched" -- in that sense removing the SD card doesn't make a difference, as far as I can tell -- but then cuts off and Andy dies again with the open-heart surgery image.
And then, while I typed this response, I tried to turn off the TF700 by pressing the power button, and voilá, the recovery is there. So I just had to push the power button to not harass you people with n00bie posts... Lesson learned, thank you!

MartyHulskemper said:
And then, while I typed this response, I tried to turn off the TF700 by pressing the power button, and voilá, the recovery is there.
Click to expand...
Click to collapse
How did you do that? Just power down? I still have the dead Andy image after installing TWRP with GooManager...
Any help is more then welcome!

MartyHulskemper said:
I tried rebooting into recovery to perform a factory reset because the update from .21 to .22 doesn't get through, but after POWER+VOL_DOWN and subsequently VOL_UP, I am confronted with a dead Andy -- with a hatch open and a red warning triangle. The unit reboots itself after while and gets into Android itself OK.
This is a damaged recovery, right? How do I go about fixing this? Fastboot (seen some threads in the G1 forum).... Amon's recovery (not available for the T700 yet, I think). I've never had this before, so I am at a loss on how to progress.
Is there CWM available yet, or is that not an option if your recovery is unbootable in the first place?
Andy is dying! Help me help him!
.....
Uhhh....... thanks!
Click to expand...
Click to collapse
If you are completely stock, then that IS your recovery. It is telling you there is nothing to flash/install. It does not mean its broke or damaged.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
ROM: CleanRom Xenogenesis 4.4 DeOdex
Kernel: Hundsbuah's V3.0.5 OC Kernel
Theme: Timberwolf's Blues and Jazz Theme

@Tyolorw: although I would have appreciated your help very much back in the day this thread is almost a year old. The TF700 had just gone retail (although I had it before it went retail) -- nobody knew what meant what.
@musicfreak: I obviously cannot remember what I had done to revive it. Sorry.

MartyHulskemper said:
@Tyolorw: although I would have appreciated your help very much back in the day this thread is almost a year old. The TF700 had just gone retail (although I had it before it went retail) -- nobody knew what meant what.
@musicfreak: I obviously cannot remember what I had done to revive it. Sorry.
Click to expand...
Click to collapse
Ahhh my apologies.
musicfreak said:
How did you do that? Just power down? I still have the dead Andy image after installing TWRP with GooManager...
Any help is more then welcome!
Click to expand...
Click to collapse
Are you positive you are unlocked? You must be unlocked, not only rooted, to install TWRP using GooManager. Also, if you still have no success you can always use the fastboot method.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
ROM: CleanRom Xenogenesis 4.4 DeOdex
Kernel: Hundsbuah's V3.0.5 OC Kernel
Theme: Timberwolf's Blues and Jazz Theme

Tylorw1 said:
Are you positive you are unlocked?
Click to expand...
Click to collapse
Ehm sorry, very stupid but I was only unlocked not rooted!
Now I'm both and that is better. And... I've learned how to get into Fastboot.

musicfreak said:
Ehm sorry, very stupid but I was only unlocked not rooted!
Now I'm both and that is better. And... I've learned how to get into Fastboot.
Click to expand...
Click to collapse
Good job! Any custom ROM you flash from here will probably provide root access in the package, so you won't have to think of that again (on this particular device, of course ).

Related

[Q] CWM and boot problems

So I might very well get crap for this since I know this has been brought up in numerous locations, however none of the answers seem to quite fit my direct problem and the information is so entirely scattered around the forums that it's a wee bit hard piecing it all together. I do apologize in advance if there is some post that details this already, it's rather late and I'm at my wits end.
So I decided to root the old Transformer today and toss on CWM to flash Revolver (yeah you guys see where this problem is headed). Upon loading up CWM and flashing the rom, I promptly rebooted, at which point it just hung on the title screen. After figiting with it a bit I got it to the point that it simply boot loops into CWM directly now (not sure if that would be what we call an improvement). Now, most solutions to this problem involve cold booting linux (this seems to work for most people) however for me it just hangs. NVflash (is that it?) doesn't seem to be an option since I'm one of the unlucky ones that it wont work for (b80 serial) and I'm not sure where to go from here.
Windows won't recognize it at any stage (CWM/hung at linux boot) however I can load it into APX mode and can successfully run Root Toolkit (though I'm not sure that will help me much).
Now I promise I have at least a wee bit of intelligence, I'm not asking for a complete walkthrough or anything but at the very least if there is an answer buried on the forums somewhere, could someone point me in the right direction?
First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
farsight73 said:
First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
dotpkmdot said:
Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
Click to expand...
Click to collapse
What version of CWM are you using?
The rogue touch recovery that the PERI installs.
Are you completely wiping your TF before installing the ROM? You MUST wipe before installing anything in CWM generally.
dotpkmdot said:
The rogue touch recovery that the PERI installs.
Click to expand...
Click to collapse
Huh. Did you factory reset and wipe data/cache?
Without looking at the options, wiping data/factory reset option, wipe cache, wipe dalvic cache.
Afterwards installing Revolver and next the update.
Tried the whole process again without doing the update, results the same.
Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.
Will do, downloading Revolution now to try and give it a shot.
Thing O Doom said:
Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.
Click to expand...
Click to collapse
So, different rom, same results. After flashing and rebooting, I simply get stuck at the Eee Pad screen. Is there any where you can point me to so I can read up on what I would need to do to reflash everything? I'd rather not turn the tablet into a nifty paperweight.
Search for
'wheelie NvFlash'
You can use that to reflash everything, or if you can Cold-Boot into Android (Hold volume-down then press power and wait 30 seconds, still holding volume-down)
You can use dd if=/sdcard/blob of=/dev/block/mmcblk0p4 (Staging partition) to reflash a blob.
See blob tools for extracting partitions from stock blobs to reflash, it's probably EBT (bootloader) that is messed up.

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] Tried to install CM - stuck on Asus Boot Logo

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

[Q] How do I use nvFlash to unbrick?

I've found a number of help of how to make the nvFlash files to make my Infinity unbrickable. But I cannot seem to find any concise instructions on what to do with the 8 files I end up with. I've saved them all over my system. But I do know how to use them. Could someone point me in the right direction?
I was unlocked, rooted, ICS, using TWRP 2.3.1. I can get into recovery, and I can get into Fastboot.
My tablet is stuck at the logo with the spinning icon, and shutting it down only starts up again. The tablet is also getting a little warm. The only way to fully shut it off is to use TWRP to power off.
Thanks, in advance. I'm panic-ing. :crying:
Reggie777 said:
I've found a number of help of how to make the nvFlash files to make my Infinity unbrickable. But I cannot seem to find any concise instructions on what to do with the 8 files I end up with. I've saved them all over my system. But I do know how to use them. Could someone point me in the right direction?
I was unlocked, rooted, ICS, using TWRP 2.3.1. I can get into recovery, and I can get into Fastboot.
My tablet is stuck at the logo with the spinning icon, and shutting it down only starts up again. The tablet is also getting a little warm. The only way to fully shut it off is to use TWRP to power off.
Thanks, in advance. I'm panic-ing. :crying:
Click to expand...
Click to collapse
You don't need NvFlash to recover from that, just flash an official Ics or JB rom from recovery. Also try a factory reset from recovery, but i guess it won't work, maybe you tried to install something that is messing with you sytem files or some mod (dpi change, beats audio, chainfire,,etc) ?
Pretoriano80 said:
You don't need NvFlash to recover from that, just flash an official Ics or JB rom from recovery. Also try a factory reset from recovery, but i guess it won't work, maybe you tried to install something that is messing with you sytem files or some mod (dpi change, beats audio, chainfire,,etc) ?
Click to expand...
Click to collapse
Thanks for the reply. I'm just overjoyed you didn't say it was hopeless. :highfive:
Sorry to be such a noob, but how do I flash an official ICS or JB rom from recovery? I was on ICS and wouldn't mind going up to JB. But when I went to the Asus site to download the update, I could not find my SKU [?] among them. I think mine is ILM. So where could I find an official JB rom without the SKU limitation? Also, when you say a "factory reset", I am assuming you mean a clean wipe? I hadn't tried that.
Reggie777 said:
Thanks for the reply. I'm just overjoyed you didn't say it was hopeless. :highfive:
Sorry to be such a noob, but how do I flash an official ICS or JB rom from recovery? I was on ICS and wouldn't mind going up to JB. But when I went to the Asus site to download the update, I could not find my SKU [?] among them. I think mine is ILM. So where could I find an official JB rom without the SKU limitation? Also, when you say a "factory reset", I am assuming you mean a clean wipe? I hadn't tried that.
Click to expand...
Click to collapse
All Asus software download located here:
http://forum.xda-developers.com/showthread.php?t=1734005
All instruction how to do things here:
http://forum.xda-developers.com/showthread.php?t=1834521

[Q] constant reboot after installing roms

Hello everyone and happy new year
I unlocked my asus tf700 using asus unlocker...
Rooted fine, with super user
Installed clockwork mod recovery 6.0.4.4
Tablet stock is 4.1.1
The problem is that no matter which rom I install... when it finally boots up it goes to the setup screen no problems.
I enter timezone etc etc then rom loads then after a minute or so the system freezes for a few seconds then restarts..
I cleared cache , have done a factory reset, and tried different roms listed in the tf700t section of xda.
I rooted countless phones and tablets and never had this problem.
Any help would be greatly appreciated.
Thank you inadvanced!!!!
xxkhbxx said:
Hello everyone and happy new year
I unlocked my asus tf700 using asus unlocker...
Rooted fine, with super user
Installed clockwork mod recovery 6.0.4.4
Tablet stock is 4.1.1
The problem is that no matter which rom I install... when it finally boots up it goes to the setup screen no problems.
I enter timezone etc etc then rom loads then after a minute or so the system freezes for a few seconds then restarts..
I cleared cache , have done a factory reset, and tried different roms listed in the tf700t section of xda.
I rooted countless phones and tablets and never had this problem.
Any help would be greatly appreciated.
Thank you inadvanced!!!!
Click to expand...
Click to collapse
Check your bootloader. You have to be on 10.6.1.14.4 or higher for any of the current roms.
berndblb said:
Check your bootloader. You have to be on 10.6.1.14.4 or higher for any of the current roms.
Click to expand...
Click to collapse
Hmmm i didnt know that, i never had to mess around with that with any of the phones or tablets that ive done in the past.
When i load up android it boots up and says bootloader 10.4.4.5 i guess thats not the correct version. For some reason I'm drawing a blank on how to update the boot loader...
Lol
xxkhbxx said:
Hmmm i didnt know that, i never had to mess around with that with any of the phones or tablets that ive done in the past.
When i load up android it boots up and says bootloader 10.4.4.5 i guess thats not the correct version. For some reason I'm drawing a blank on how to update the boot loader...
Lol
Click to expand...
Click to collapse
You tried different roms from XDA and missed the section in the OP about warnings, requirements and instructions in each one of them???
It's usually the part in red with the huge letters, the part that says: READ ME
To get your bootloader to a current version you can flash the latest firmware from Asus. You would have to reinstall the custom recovery via fastboot afterwards of course.
Or you can download the bootloader/TWRP package in the OP for CROMi-X and flash that. Again: depending on which rom you want to flash, you may have to change to a different recovery afterwards.
berndblb said:
You tried different roms from XDA and missed the section in the OP about warnings, requirements and instructions in each one of them???
It's usually the part in red with the huge letters, the part that says: READ ME
To get your bootloader to a current version you can flash the latest firmware from Asus. You would have to reinstall the custom recovery via fastboot afterwards of course.
Or you can download the bootloader/TWRP package in the OP for CROMi-X and flash that. Again: depending on which rom you want to flash, you may have to change to a different recovery afterwards.
Click to expand...
Click to collapse
The funny part of it all is that I'm color blind lol.
Ok I updated to the correct bootloader and so far so good.
I was honestly surprised that I missed that part as well, but as I read it I thought to myself hmm but you knew that!! Lol
One quick question though, now when I boot into boot loader holding down the power and up there's only 3 icons instead of 4. The USB icon isn't there anymore.. Is that normal
Btw I'm on a cm 11 update.. Fingers crossed
Thank you again for your time
xxkhbxx said:
The funny part of it all is that I'm color blind lol.
Ok I updated to the correct bootloader and so far so good.
I was honestly surprised that I missed that part as well, but as I read it I thought to myself hmm but you knew that!! Lol
One quick question though, now when I boot into boot loader holding down the power and up there's only 3 icons instead of 4. The USB icon isn't there anymore.. Is that normal
Btw I'm on a cm 11 update.. Fingers crossed
Thank you again for your time
Click to expand...
Click to collapse
Good! Glad you worked it out. Maybe wearing green colored glasses while reading forums would help
ICS: 4 icons in bootloader, push Volume Up on flashing USB to get into fastboot
JB: 3 icons and you're in fastboot by default.
Or was that from JB 4.1 to 4.2? Can't remember... My problem is a serious case of CRS...
The glasses would come in handy here again: Read the script: "Starting fastboot protocol" Admittedly the script is tiny, but still: Read man! Read! The stuff is there for a reason!
LMAO
berndblb said:
Good! Glad you worked it out. Maybe wearing green colored glasses while reading forums would help
ICS: 4 icons in bootloader, push Volume Up on flashing USB to get into fastboot
JB: 3 icons and you're in fastboot by default.
Or was that from JB 4.1 to 4.2? Can't remember... My problem is a serious case of CRS...
The glasses would come in handy here again: Read the script: "Starting fastboot protocol" Admittedly the script is tiny, but still: Read man! Read! The stuff is there for a reason!
LMAO
Click to expand...
Click to collapse
Very Good, everything worked out perfect and thank you!
You made me laugh with the green glasses comment lol.
I'm on kitkat nightly .. Seems OK. I notice some lag but nothing crazy.. I was thinking about going to paranoid or another ROM but who knows lol.
I installed cm on two kindle fires last night with the adb... Thank god for development ,damn that kindle skin blows.. No app store just the amazon app store, what a bunch of crapppp...
But thank you again for taking the time out to help.

Categories

Resources