Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc
To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks
Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.
I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/
Related
Reading through different forums I have read problems similar to mine but nothing exactly the same. I followed each fix anyway but I have not been successful.
The last thing I remember I did before the brick, I flashed CWM touch then CyanogenMod 9. I am unsure what occurred but I tried to flash back to my JB backup and the problem started.
Now my tablet comes on and just hangs on the Asus splash screen. If I turn the tablet off, it automatically comes back on.
I have tried to turn the tablet off and boot into recovery but it just boots back up to the splash screen and hangs; I have no option to go into recovery, android or fastboot.
I can get into what I think may be USB mode by pressing power and volume up through a couple of cycles; my computer detects a device but I cannot load drivers.
I have downloaded the Android USBPCdrivers but each time I try to navigate to the folder to install the device manager fails.
If anyone has any thoughts I would appreciate any assistance, thanks for your time!
UPDATE TO ORIGINAL POST
I as able to finally get my computer to recognize the tf300t in device manager by wiping all the usb drivers and installing "Universal Naked Driver 0.7" posted by 1wayjonny from XDA's website http://forum.xda-developers.com/show....php?t=1766220, not sure if it matters my computer "sees it" as a ASUS transformer prime rather than tf300t.
Now I am reviewing an ASUS unbrick called Wheelie http://forum.xda-developers.com/show....php?t=1687285, I believe this is geared towards the tf101. Anyone have any thoughts based on my status at this point? Thanks
If you are on JB stock, there is no way to flash a booting Cyanogen 9 ot 10 Rom.
Only Hydro JB is running!!!! And JB Stock.
1st of all you have to download a special Recovery. I highly recommend TWRP. You have to dl the JB version!!!!!
Flash it through fastboot. Then flash the Stock JB via TWRP recovery
Then flash TWRP again via fastboot.
Than flash The Hydro JB rom
Then reboot
Then go back to recovery
Then flash the latest Hydro update and reboot
You are like me stuck on the f...... new JB Bootloader and Kernel. All other roms are for the ICS Bootloader and Kernel, so no way of getting them running until the Cyanogen devs finding a solution.
Fastboot not an option
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
mfsmith said:
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
Click to expand...
Click to collapse
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
喔喔兒 said:
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
Click to expand...
Click to collapse
Waiting for nvflash won't do you any good since you needed to have it BEFORE bricking your tablet. If your tablet is already bricked, APX/nvflash will not help you.
krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
He could still try sending it for RMA. Mine got repaired for free for some reason.
An unusual Asus TF300T brick
Yeah, I'm having problems with my TF300T, too. I had CWM installed, but when I tried to flash a new ROM, I bricked it. No problem, I had figured it out before. But when I was in the bootloader, I inadvertantly erased instead of selecting the USB. Now, All I get when I try to boot up is the white ASUS screen with;
The Device is Unlocked
Android cardhu-user bootloader <2.0 e> released by "ww_epad-9.4.3.26-20120416" A03
Checking for android ota recovery
Booting recovery kernel image
My computer sees the tablet. The Device Manager shows: Asus Transformer Prime APX Interface
But it only shows up when I reset. As soon as I try to boot the tablet, it no longer sees it. I can't access the bootloader and Fastboot doesn't do anything except "waiting for device".
SO! If anyone can give me some help, I'd appreciate it. It's a puzzle for ya, anyway.
Thanx
As your last resort, this worked for me
Link to my thread---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, feel free to ask anything.
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
I think to only solution is to replace the main board OR buy a new tablet :'(
Sent from my ASUS Transformer Pad TF300T
jay-roc said:
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
Click to expand...
Click to collapse
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
For future reference here is the way I see the recovery and rom matching issue.
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
tobdaryl said:
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
Click to expand...
Click to collapse
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
jay-roc said:
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
Click to expand...
Click to collapse
I'm sorry, I hoped the guide would give you a chance of recovery.
I definitely appreciate the help, and the guide's a great resource.
tobdaryl said:
I'm sorry, I hoped the guide would give you a chance of recovery.
Click to expand...
Click to collapse
jay-roc said:
I definitely appreciate the help, and the guide's a great resource.
Click to expand...
Click to collapse
You are welcome!
I had wished for better results.
Good Luck!
noahvt said:
I think to only solution is to replace the main board OR buy a new tablet :'(
Click to expand...
Click to collapse
Is there any tips for buying mainboard? Should it be exactly the same as in my tablet (I mean the same region and, therefore, version of ROM installed), maybe serials.
I have a bricked TF300T, and the only way I have to resurrect it - MB replacement. So, please, ANY info will be useful. Thanks in advance.
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Buster99 said:
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Click to expand...
Click to collapse
I'm so damn appreciated! Thank you so much)) I'd add this way to get to fastboot - adb reboot fastboot - just from faulty CWM. Other way it didn't worked.
I got mine working this way
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
ozkrtech said:
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
Click to expand...
Click to collapse
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
martyzzz said:
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
Click to expand...
Click to collapse
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
ozkrtech said:
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
Click to expand...
Click to collapse
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
martyzzz said:
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
Click to expand...
Click to collapse
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
ozkrtech said:
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
Click to expand...
Click to collapse
When i press vol down+power i get the asus boot screen for a minute or 2, the tab switches off and on again to the same boot screen.
I cant boot into recovery
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
Buster99 said:
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
I dont have fastboot in any way.
I can only power on the device with volume up + power to enter APX mode, than only my pc sees a USB device.
I tried a lot of differtent drivers but for nome of them i can ADB of Fastboot to the device.
It would help if someone that has managed to unbrick through APX mode posted the right driver for a TF300T
Cheers
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Buster99 said:
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
martyzzz said:
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
Click to expand...
Click to collapse
don't just point at the folder
manually select the driver for the device from android-sdk\extras\google\usb_driver
gl
So I want to install the latest 4.4.4 Kit Kat on my Transformer Infinity because the latest Jelly Bean on it is extremely slow. Through research and google I found that the only way to root it was go back to an earlier version of Jelly Bean. Otherwise the motochopper program was denied access so I was unable to root it. So I found the right Jelly Bean update and stuck it on my SD card and it showed up in the notifications as an update to fall back to. Installed it and the motochopper app worked and rooted the tablet. I tried to use the Asus unlocker tool but it always says to try back later as it is trying to unlock it. Some info on the internet says that app doesn't work with jelly bean some says it does. So I thought i would roll back to Ice Cream Sandwich. In order to do that the info. on the internet says to hold the down volume button along with the power button and you can go to some menu that will allow you to install earlier version of android. Which I have an ICS for the infinity on the SD card. Problem is the volume down button plus power button does nothing. It has no effect. I'm at my wits end here. Everything I have found on the internet doesn't work. I'm fairly new to rooting, unlocking, and installing a custom android. I have done this once for a Kindle Fire tablet and it was MUCH easier then this Infinity tablet.
You do not need to downgrade to ICS (and you can't - at least not with stock firmware) The unlock tool version 8 works fine on JB roms - if it works at all. You really have to keep trying. For some people it literally took 50 tries or more and all the sudden it worked... And for some it never worked. There's no rhyme or reason for this except that Asus is not trying very hard to make this work for us. They enable it, but do not support it.
Google "unable to unlock TF700" and you will get a dozen threads discussing this and a few more strategies you can try.
Sent from my DROID4 using Tapatalk
That was kind of how the root tool worked I had to try it over and over I think about the 5th or 6th time it worked.
Well that was relatively painless then - happy flashing
I'm not quite to 50 times yet but I still get "an unknown error has occured. The network may be down please try again later" error.
So i'm all rooted and unlocked now. I have a snapshot version of 4.4.4 for transformer infinity. The cyanogen mod program says the TF700T isn't supported and aborts. I've tried the Clockwork Rom recovery program and it says the TF700T isn't supported either only the TF200 is it says. What is the best way to install this ROM?
So I tried Rom Toolbox. When the tablet reboots to boot into the recovery where you can install the rom it just sits at the asus logo screen forever. I don't think I have a recovery boot anymore. When I hold the power button and volume down button which is supposed to allow you to boot into recover nothing ever happens.
It's probably a little late, but to install a custom rom you have to install a recovery compatible with your bootloader and the rom you intend to flash.
You flash this recovery (TWRP or CWM) in fastboot, then you can boot into it to install a rom.
If you can't boot into the bootloader with Power and Volume Down and you did not generate nvflash blobs prior to all this, I'm afraid it's a brick.
Try every combination you can think of: Holding the buttons a very long time, use the reset pin hole on the side in conjunction with Volume Down, let it sit for hours and hope it sorts something out.
You need some magic to give you access to the bootloader menu and fastboot - that's your last hope.... Sorry
I can still boot into the version of jelly bean I have on the tablet fine. I did manage to get it to finally boot into a recovery console. it might have been a fluke I tried like 20 times and it finally just booted into it from the Rom Manager program. I tried installing my rom image but it would fail every time. I just rebooted and it went back into jelly bean. No idea what to do from here. The power button and volume down still don't do anything. And I haven't been able to reproduce getting it to boot back into the recovery again. At least it isn't bricked but I hate this tablet so much I might just take a hammer to it and give up.
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
kahless1979 said:
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
I know when I'm upset with this thing I start doing things wrong....make sure you are actually using the vol down button and not the Up button. It's an easy thing to do when you're in PO'ed mode.
You're lucky to be unlocked! I bet I have run that unlock tool a million times to no avail.....
kahless1979 said:
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
You cannot use ROM Manager on the TF700!!! That is the fastest way to a hard brick I know on this tablet. Forget ROM Toolbox, ROM manager and all the other tools! You have to get ADB and fastboot working on your computer and my guide you linked to is a good start.
I have no idea why you cannot boot into the bootloader if your rom boots fine????
You are pushing Power and Volume Down until you feel the tablet vibrate TWICE?
Get the ADB drivers installed on your PC and with the tablet booted into your rom type this in a command prompt:
Code:
adb devices
What do you get?
berndblb said:
You cannot use ROM Manager on the TF700!!! That is the fastest way to a hard brick I know on this tablet. Forget ROM Toolbox, ROM manager and all the other tools! You have to get ADB and fastboot working on your computer and my guide you linked to is a good start.
I have no idea why you cannot boot into the bootloader if your rom boots fine????
You are pushing Power and Volume Down until you feel the tablet vibrate TWICE?
Get the ADB drivers installed on your PC and with the tablet booted into your rom type this in a command prompt:
Code:
adb devices
What do you get?
Click to expand...
Click to collapse
Volume Down and Power yields one vibration and nothing happens after that. I have tried holding them down longer to no avail and released them after one vibration and nothing still.
I would use ADB to push the rom to the tablet and that is what I did with a Kindle Fire a couple years ago and worked great. But your guide still calls for being able to use the volume down and power button. I guess I got a real lemon of a tablet here.
I get List of devices attached
C7OKAS090001 device
kahless1979 said:
Volume Down and Power yields one vibration and nothing happens after that. I have tried holding them down longer to no avail and released them after one vibration and nothing still.
I would use ADB to push the rom to the tablet and that is what I did with a Kindle Fire a couple years ago and worked great. But your guide still calls for being able to use the volume down and power button. I guess I got a real lemon of a tablet here.
I get List of devices attached
C7OKAS090001 device
Click to expand...
Click to collapse
Well that's good. You seem to have ADB access. Try this command:
Code:
adb reboot - bootloader
That should reboot your tablet into fastboot mode. If it does, use this command:
Code:
fastboot devices
That should return a (different) alpha-numeric string and you would be in business to flash. But let's not get ahead of ourselves...
adb reboot - bootloader
That command restarted my tablet.
So just type "adb fastboot devices" at the command prompt?
kahless1979 said:
adb reboot - bootloader
That command restarted my tablet.
Click to expand...
Click to collapse
The correct command is:
Code:
adb reboot-bootloader
_that said:
The correct command is:
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
I took out the spaces between the hyphen. Same thing, it rebooted the tablet right back to the android desktop.
kahless1979 said:
I took out the spaces between the hyphen. Same thing, it rebooted the tablet right back to the android desktop.
Click to expand...
Click to collapse
I'm stumped... @_that you have an idea why it doesn't boot into the bootloader? I thought maybe the Volume button is bust - but now...IDK
berndblb said:
I'm stumped... @_that you have an idea why it doesn't boot into the bootloader? I thought maybe the Volume button is bust - but now...IDK
Click to expand...
Click to collapse
Is it possible I messed something up when I downgraded from Jelly Bean 4.2.1 to 4.03? The reason I had did that was a guide somewhere for this tablet said the ADB motochopper program wouldn't root 4.2.1. Which I could never get it to work. But did fine once I went to 4.03. I did that by downloading that update from asus's website and putting it on my SD card and it found the update and asked me if I wanted to fallback to an older one.
kahless1979 said:
I can still boot into the version of jelly bean I have on the tablet fine.
Click to expand...
Click to collapse
kahless1979 said:
Is it possible I messed something up when I downgraded from Jelly Bean 4.2.1 to 4.03?
Click to expand...
Click to collapse
So what version of Android is now actually running on your device? 4.2.1 or 4.0.3 (which is ICS)?
You also speak repeatedly of some version 4.4.4 you are trying to install - the latest version of Android as of today is 4.4.2.
Note that there are multiple ways to hard brick your tablet if it is unlocked - don't do anything you don't understand.
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Hmm i installed the latest verison of twrp with my mac via fastboot ( followed directions from twrp site for the commands). I would try to get adb/fastboot to work on your mac first and maybe try to fastboot flash twrp again? and if that does not work i would just do a RUU honestly, but i'm sure someone smarter than me can chime in and get it resolved . For instructions to install adb/fastboot on a mac i followed this http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/ If it does not recognize your device try installing htc sync manager.
darthnix said:
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Click to expand...
Click to collapse
You could go find the ruumode-flashable recovery that I think is in one of dottat's ruu threads (5.0.1 one I think). Then change the name of the file to 0p6bimg.zip and flash it in bootloader. That should flash twrp to a phone without adb/fastboot.
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Shinobi_warrior said:
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Shinobi_warrior said:
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Click to expand...
Click to collapse
Are you able to boot into twrp? If yes,then flash this firmware.It should solve any firmware corrupt issues,i.e. you should be able to boot into fastboot again.
Thank you, YES this is exactly what I needed/looking for.
.
You have fixed/saved the Day confirmed now.