So I've searched thru the thread...but I don't know what to search for. Let me explain my problem:
I had Unlocked the device, had TWRP as recovery and was running cleanROM 1.2. So I downloaded cleanROM 2.5 (JB) and put that on my SD card. I also read that I needed TWRP 2.2.2.0 to load it.
So I downloaded and fastbooted TWRP 2.2.2.0 ICS.blob, recovery flashed ok and was able to install cleanROM. Upon reboot, it just bootlooped.
So I figured I needed TWRP 2.2.2.0 JB.blob. I fastboot installed that with no problem but when I rebooted to fastboot mode, I stupidly selected to wipe data from there and now the tablet bootloops with no option for the fastboot. when I try to hold down the power and volume down key the device states "Android cardhu-user bootloader (2.10 e) released by "US_ePad-9.4.3.30-20120604" A03 checking for Android ota revovery" then goes to Booting recovery kernal image.
Did I kill it?
I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.
I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.
tobdaryl said:
I'm going to assume from your post that you were running ICS bootloader and had never updated to stock JB, if so you were ICS.
I read your post last night but didn't have an answer to your problem so I decided to sleep on it.
If I surmised correctly in my previous statements you had an ICS bootloader and flashed a JB rom, then you flashed a JB recovery while you still had an ICS bootloader. I don't think the data wipe is a factor here. You can't mix and match ICS and JB recoveries and roms the bootloader must match.
I know; how does this help me. We need to establish your situation absolutely if there is any chance of recovery.
I'm still thinking about your situation and your reply will give myself and many others reading your post enough info to consider your options.
Click to expand...
Click to collapse
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.
mikaole said:
I fastboot is not working and you were still on ICS bootloader, try if ADB works.
If yes type this:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
then press enter
Then type this
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
and press enter.
Now try if you get fastboot back. If yes fastboot the ICS recovery and then you should be good to go.
1st flash the ICS Stock Rom and then fastboot the ICS recovery again. Now you should be back to normal.
If this doesn´t work dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
unpack it
run WSGFlasher batch
choose 2 as selection and press enter
in the new window choose 1 to fully unbrick and press enter
in the new window choose 1 to Full recovery and press enter
let it run. Needs about 5 to 15 minutes
When everything is done reboot.
Click to expand...
Click to collapse
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.
SO if I read you guys correctly, I would manually have to flash a JB bootloader? It's not something that happens automagically when you flash a ROM? I never flashed a bootloader, just the two recoveries, then once in recovery, the ROM.
Xsoldier2000 said:
So I'm new to the TF300 as you can probably guess. I flash roms constantly with my S-off Rezound and my prior OG Droid. I'm not new to the game, just new to the TF300t.
I did finally grab the right keywords and found pretty similar posts to what happened to me, and it looks like I bricked it. (though I sure hope not.)
I think you are right that the data wipe isn't the factor. I just thought I needed a JB recovery to flash the JB rom. You know how a certain boot.img will just send your phone into a bootloop, but you flash the correct boot.img, and it'll boot straight into the rom? That was my thinking going into this. (guess I should have taken MORE time to read instead of bullishly charging in...
I also believe you are right in your first statement, I received the tablet with ICS. I rooted it and flashed CleanRom 1.2 immediately, and haven't flashed again. I saw jellybean (Cleanrom 2.5) out and thought, why not? Flashed TWRP 2.2.2.0 ICS and proceeded to install CleanROM 2.5. I did not know I needed to be on a JB bootloader. You are correct in that. BUT....after flashing the TWRP 2.2.2.0 JB recovery, I WAS able to go back into fastboot mode and could switch between Android/USB/Wipe Data... if only I had chosen the USB option.....
I await any help you can offer.
Thanks so much.
Click to expand...
Click to collapse
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!
tobdaryl said:
Please see the post directly below mine. mikaole has already provided an excellent path to recover your unit.
Good Luck!
Click to expand...
Click to collapse
Thanks all, but I can't get ADB working on it. It's just a constant reboot - loop.
I guess I need to contact ASUS and try to get it repaired... cheaply, I hope.
Xsoldier2000 said:
Thanks so much, I just returned home from a trip and will try this first thing in the morning.
Though I feel like the bootloop it's stuck in doesn't give me enough time for ADB to work. If ADB doesn't work, I think I'm bjorked.
Click to expand...
Click to collapse
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!
tobdaryl said:
Time for adb; interesting statement. It brings to mind something I have used on another unit with bootloop and on several other units to get boot logs.
I'll try to describe. In terminal you use a command and afterwards if you wish to use the same command you use up arrow and the last command is typed for you and just hit return. I think this also works in windows cmd but can't verify.
Why do we care? Get in terminal and type the first adb command given above and hit return. Now we can send this command twice in one second. Up arrow ( command typed for you ) power on unit, hit return, up arrow hit return, etc. You could verify if there is an adb window of time available by typing adb devices and look at the output. Anything other than devices and blank means there is an adb window.
Sorry; easy to do but hard to describe. Worth a try if you are ready to ship off. This is the only other thing I can think of for your situation.
Good Luck!
Click to expand...
Click to collapse
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......
Xsoldier2000 said:
I will def. try that. I have only usually tried the adb once it's in the loop, not from cold start.
I am aware of the command line trick, I've been using Linux for about 7 years, and was surprised to see it in windows.
Great idea to get it running before hand though, enter > up Arrow . enter > up arrow......
Click to expand...
Click to collapse
No go. I drained the battery, then plugged it in for like 20 minutes to charge. I got ADB ready with adb devices and began trying.
No devices. for the heck of it I plugged in my phone during the up arrow enter marathon, and adb picked up the phone right away.
Sucks, but thanks so much for all your help. Looking for a refurb or a repair place now.
I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.
tobdaryl said:
I'm sorry but I don't know anything else to try.
There is a manual reset on the side below the sdcard.
Click to expand...
Click to collapse
No Worries, I appreciate all your help.
My problem was more or less similar and i managed to fix mine
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
In my case I installed the wrong recovery (TWRP-JB) with the wrong bootloader 4.2 and bricked, I also did the mistake to wipe everything. but after several tries I fixed mine, go to my thread on the link above for details.
Hope it helps.
Related
Hey guys! Been playing around with the transformer pad 300. unlocked it. rooted it. all while on 9.4.3.29. but then the update 9.4.3.30 came out so i installed the update. lost root. tried the same process to root via these links. could never get the recovery.img to load this time around. i uninstalled drivers and reinstalled drivers. always got stuck on "booting recovery kernel image". eventually i pissed it off. now when i try to go into fastboot mode, i dont get the 3 options "wipe date" "usb" "android cold-boot". all i get is booting recovery kernel image" and it sits there. if i dont hold down the volume down button during reboot. it sits on "the device is unlocked".
Is there an adb way to push files and get this puppy running again?
h*t*t*p://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
h*t*t*p://theunlockr.com/2012/05/25/how-to-root-asus-transformer-tf300t/
Please help!
Exactly what happened?
-i tried to install CWM on 9.4.3.30 from link above.
-it showed successful in cmd window on pc
-tried to boot into recovery, that sat there on "booting recovery kernel image". sat there for at least 20 minutes.
-held pwr button to reboot. it did and tablet started up fine.
-reboot with vol+dwn to go into fastboot. choose usb for fastboot.
-fastboot recovery img, which failed with error "Too many links".
-rebooted tab normal just fine.
-turned off tablet.
-tried fastboot erase recovery
-sat on "waiting for devices"
-rebooted just fine.
-checked drivers, all installed just fine. uninstalled, reinstalled to be sure. no problem.
-went through attempt to install twrp.blob. was successful on pc.
-but got stuck on booting recovery kernel image again.
-reboot normal just fine.
-decided to pwr + vol dwn, then choose wipe data.
-gave normal "data wipe complete". then boot recovery kernel image message i keep getting stuck on.
-stayed there for hours.
-finally i pressed and held power to attempt normal reboot. and get stuck on ASUS screen with "device unlocked" message.
-try pwr + vol dwn and get stuck on
"the device is unlocked."
"android cardhu-user bootloader <2.10 e> released by 'us_epad-9.4.3.30-20120604' A03"
"Checking for android ota recovery"
"Booting recovery kernel image"
-cannot adb devices at this point or fastboot devices at this point
HELP!?
http://forum.xda-developers.com/showthread.php?t=1680570
Try this thread.
MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Try this thread.
Click to expand...
Click to collapse
Thanks. i reviewed the whole thread. tried the external SD card idea with firmware update and with recovery.img just for kicks even though it didnt suggest it. no dice on either.
what os u using? I saw a few thread about booting into unbuntu off a live cd and being able to push to the sd card
paedz718 said:
what os u using? I saw a few thread about booting into unbuntu off a live cd and being able to push to the sd card
Click to expand...
Click to collapse
it's running 4.0.3 Asus build firmware 9.4.3.30. unlocked but not rooter (anymore). Could you sahre link to steps about the ubuntu and CD idea you have?
baldypal said:
it's running 4.0.3 Asus build firmware 9.4.3.30. unlocked but not rooter (anymore). Could you sahre link to steps about the ubuntu and CD idea you have?
Click to expand...
Click to collapse
here's the link to the posts that i saw about using Ubuntu. not sure its applicable to your situation, but hey give it a whirl as a last resort
http://forum.xda-developers.com/showpost.php?p=28407803&postcount=253
http://forum.xda-developers.com/showpost.php?p=28477279&postcount=204
Hey I wrote a tutorial for this, it happened to me and its real easy to fix! hope this helps FIX
Seems to me that something went wrong while flashing CWM or maybe you flashed a CWM that is for the Prime.
Had something similar going on with my Pad: This video helped:
http://www.youtube.com/watch?v=Iy-Sbq4JmdQ&feature=player_embedded
If you can´t get ADB to work, try this unbrick tool:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
Just execute the bat in there. Than choose option 5 for ADB shell.
Then use this comand:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
If it runs through this command:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Enter
Then turn off your Pad. Now you should be able with - and Power to get to the screen were you can change to fastboot and then you can fastboot your Recovery again. Try to download it from here for CWM:
http://forum.xda-developers.com/showthread.php?t=1668173
or from here for twrp:
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps. Got mine unbricked like this.
d_crossfader said:
Hey I wrote a tutorial for this, it happened to me and its real easy to fix! hope this helps FIX
Click to expand...
Click to collapse
Thanks! but in my situation i cannot get into ClockworkMod. Also, i can't get into fastboot either. Screen is stuck on first screen with message "Booting recovery kernel image" but just sits there until the battery dies.
mikaole said:
If you can´t get ADB to work, try this unbrick tool:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html
Just execute the bat in there. Than choose option 5 for ADB shell.
Then use this comand:
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
If it runs through this command:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Enter
Then turn off your Pad. Now you should be able with - and Power to get to the screen were you can change to fastboot and then you can fastboot your Recovery again. Try to download it from here for CWM:
http://forum.xda-developers.com/showthread.php?t=1668173
or from here for twrp:
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps. Got mine unbricked like this.
Click to expand...
Click to collapse
This looks to be the most promising so far. i'll give it w whirl when i get the tablet back.
I sent it to ASUS on Friday to see what their charge is going to be to fix it for me.
Well well well!
Got a notification back from ASUS today that they are sending my tablet back to me fixed and good as new. Funny thing is, they never charged me for any work? Unlocked bootloader tablet fixed under warranty? How often does that happen?
baldypal said:
This looks to be the most promising so far. i'll give it w whirl when i get the tablet back.
I sent it to ASUS on Friday to see what their charge is going to be to fix it for me.
Click to expand...
Click to collapse
baldypal, how did you send it to them it turns out, that same thing happened to me, and I think I would have to send it to Asus Also
osiris5180 said:
baldypal, how did you send it to them it turns out, that same thing happened to me, and I think I would have to send it to Asus Also
Click to expand...
Click to collapse
I called them to get tech support over phone. they couldn't assist. I asked if they could RMA it for fix (even though unlocked). They did. I just got lucky and they didn't charge me even though they should have since i unlocked it. WARNING: when i got it back, it was locked again.
I had some probs with mine as well and it seems asus just put up that legalese for its legal dept. I've talked to a guy there wheni asked for my pad and they basically repair all atm. Dunno if that will continue when their new line is out but so far they don't care much and focus on repairing their flagship and making their customers happy.
Cheers
Sent from my A700 using xda app-developers app
baldypal said:
I called them to get tech support over phone. they couldn't assist. I asked if they could RMA it for fix (even though unlocked). They did. I just got lucky and they didn't charge me even though they should have since i unlocked it. WARNING: when i got it back, it was locked again.
Click to expand...
Click to collapse
Guys I think I'm on the same boat as you now... did you have any progress on this?
JohnerH said:
Guys I think I'm on the same boat as you now... did you have any progress on this?
Click to expand...
Click to collapse
The process you quoted in your reply got my tablet fixed and returned but locked. i wasn't out any money, just about 1 weeks time without a tablet.
Hi, I've been experiencing this problem for a while now. Once the screen comes off, the tablet will never wake up. I've clean flashed, with/without gapps, and even right after flashing (EOS, CM, RaymanFX's & Gierdo's, ARHD...) once I turn the screen off (with either the lockpad button in the keyboard, the button on the screen, or after a display timeout) it will never light up again.
I also have trouble switching off the tablet, i.e. I hit shut down and it will never do (I had to go into recovery by power vol-) and hit shut down from there.
Buttons work, so I am thinking it might be firmware problem? Since all roms and different recoveries dont make a difference... I am currently downloading the latest ASUS official firmware from their website, but it'll take some hours since my internet connection here is rubbish.
thanks for any advice and help!
When you flash the different ROMs, are you wiping all the following:
Cache
Davlik Cache
System
Factory Reset (from recovery)
If you are skipping any of these, it can cause issues. The most important one is the Factory Reset to erase the system settings and can cause huge issues when jumping from one ROM to another ROM.
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
TheKaser said:
Yes thanks, of course I am. Full wipes between flashes, cache and dalvik, when changing kernel, etc.
TWRP recovery doesn't install (nor with EasyFlash or GooManager) I currently have CM recovery flashable with EasyFlash. Twrp stalls on a splashscreen and nothing else...
Click to expand...
Click to collapse
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
TheKaser said:
thanks for your help, it still didn't work. It stays stuck in the recovery splash screen and it won't even boot into the rom. I have to fix it using EasyFlasher.
I am thinking that all my problems are due to a corrupt firmware or something like that. The tablet never reboots by software or shuts down, with no matter which ROM.
I will perform an internal storage backup and use EasyFlasher to install the official Asus firmware. Hopefully that will make the trick.
Click to expand...
Click to collapse
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
frederuco said:
I found a little mixup with my code, it should be just a REBOOT command at the end and not a REBOOT RECOVERY.
If you do the reboot recovery, it does not complete the flash of the firmware on boot.
Give that a shot and see if it works if you want.
Click to expand...
Click to collapse
Nothing worked. I indeed followed the insturctions you gave me but reading them in the TWRP site so I did it correctly. Still didn't work. I flashed using EasyFlasher the official ASUS firmware, and the tablet still behaves in the same way: Will never shutdown or reboot by software command, will not wake up when screen is switched off... this is frustrating, but it needs to be software, right? It can't be hardware, since the power button does work...
I dont know what else to do... I wiped my tablet clean and flashed the official firmware and the issue is still present...
the thing is that the tablet is working (PC reacts to usb) and it makes noises when I plug the keyboard dock... but the power button will just not turn the screen on...
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
TheKaser said:
Hi, a little bump just to see if someone could help me out. I flashed the latest Team EOS nightly 4.2.2, and it runs like a charm, but as soon as I turn off the screen, it wont come back. I need to do a reboot by holding the power button to be able to use it again. Could it be hardware?
It happens likewise with all roms...
Sent from my Transformer TF101 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Go to the android development tab of this forum and use the katkernel. Works with EOS roms. I still had a screen freeze but better than the stock kernel. This may help you. Follow the flashing instructions.
Sent from my SGH-T999 using Tapatalk 2
Thanks Tom, I have already tried katkernel in the past, with the same result.
the tablet cant power off either, it stays with the powering down box for ever. I need to hard reboot it into the recovery and power it down from there...
It's all very strange, it happens like that with every rom i've tried, from 4.0 to 4.2.2, and every kernel.
Sent from my Transformer TF101 using Tapatalk 4 Beta
I have followed all the threads I have seen, flashed from roaches Prime 3.0 rom, to EOS 4.2.2, stock Asus/unbrick with easyflash, and using tubuntu installer.
I always find the same issue, cant reboot (it stays stuck), cant tunr screen on after turning it off, and TWRP recovery doesn't work (only the two others provided by easy flasher).
Might it be there is something partially bricked?
I once bricked my USB in my old nexus. I am desperate, the tablet works fine when turned on but can't reboot, power down, or turn the screen back on... it has to be some kind of bricking...
ps: from here: http://forum.xda-developers.com/showthread.php?p=42046184#post42046184
TomTcom said:
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
Click to expand...
Click to collapse
I can corroborate that your commands work.
TomTcom said:
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
Let me know what happens.
Click to expand...
Click to collapse
Is there a way that some part of the hardware is bricked?
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
TomTcom said:
That's always possible it's bricked but I wouldn't give up. Dig deep into wheelie and nvflash and how they work. I'm sure you can get it running right again.
Wish I knew more, sorry!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
TheKaser said:
no worries, thanks for your effort. Is there a way to completely start from scratch? like format and wipe everything, install fresh bootloader, firmware, etc? like wipe everything wipeable and installable in the hardware?
Click to expand...
Click to collapse
My commands from the previous postings were to do just that. Format_all and use the configuration file to load from but I could've edited it wrong.
You can try manually pulling all the files from fresh stock software. I don't use any of the tools out there so it's back to research on it.
Sent from my SGH-T999 using Tapatalk 2
once I do a format all, do you know what will I end up with? no OS, no SDCard files, no internal memory, but also no recovery? If so, I guess I have to do flash recovery via Easy Flasher on APX mode.
edit 1:
i couldnt make the --format_partition --format_all work, it gave an error on partition 0.
So, I run --format_partition 1 and its taking too long it seems, cant tell if it's hung up or what...
edit2.
from the config file you provided in the other thread, I can see the partitions are named 3-16. I manually formatted them with your androidpartition.cfg file. I will proceed to installing the stuff and report back. Thanks!
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Good for you! Glad you got it!
Sent from my SGH-T999 using Tapatalk 2
TheKaser said:
I DID IT!!!
I formatted each partition separately with the configuration file.
Once that was done, there was no OS, no recovery, nothing.
In APX mode, flashed the official firmware using EasyFlasher and booted.
There, the screen can be switched on and off and it works!!!! I also could power it down normally.
Back to APX mode, flashed Team Rogue's recovery (TWRP still didn't work), and flashed EOS latest nightly. It all works like it should, I am very very happy.
Thank you sir TomTcom, you are the man!
edit. Also, I removed a dead SD card, that might have helped to not reboot the tablet, since it might have waited for ever to securely stop it while it was dead and non-responsive. I dont want to verify what happens if I plug it back in, I am happy with my brand new TF101, which didnt work properly since December
Click to expand...
Click to collapse
Hi!
I have similar problem to you.
My tablet is not booting corectly. Stuck on the logo (look at the picture).
I have tried: Easy flash (a few soft), and when i click on the "unbric" my tablet is disconecting from PC.
I can't go into TWRP. I only boot into APX mode.
I can turn on my tablet by recovery mode, and chose there "android" option, but this is annoying.
I dont konw what to do ;(
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 :-/
Hi all I've been an idiot and am hoping I haven't done any permanent damage to my unlocked/rooted tf300 so before I continued doing anymore I wanted to make a post here asking for any help possible.
I hadn't updated to the 4.2.1 build yet and finally decided to bite the bullet an hour or two ago since I wanted to try out the newest version of cromi. I was using the patched 2.4 twrp and initially updated to the 10.6.1.8 update using fastboot, then decided I might as well do the 10.6.1.15.3 using the fastboot again and finally updated to the 2.5 twrp using fastboot. As the jb updates were happening I would get the message that the tablet wasn't rooted and to install SuperSU, and because I'm a dumb creature of habit both times I just instinctively swiped to install, only realizing what I had done after the fact.
After all of this I was still able to at least turn on my tablet and get to the home screen, but unable to do a factory reset in recovery (the log would say "unable to" on every task, but the final message would still say successful?) or have any options to install a rom within it. I had also noticed that I wasn't rooted anymore. I used motochopper and was rooted again for the time being and used a couple apps that required root just to make sure that was the case. At this point I rebooted the tablet and holding down the power button/volume down, I think this is the point where my tablet would just boot straight into recovery, unable to boot into anything except recovery since even if I hold down the power button/volume down.
I've tried to do a factory reset and get the same response as earlier and I get a "failed" message when I try to do a data format. I know there will be at least a couple glaring red flags within this message to anybody who knows much more than I do, but I'm hoping this isn't the end of my tablet and would greatly appreciate any assistance provided. If you need any extra information please let me know I'll do the best I can with providing whatever would be useful, thank you in advance for your time and help.
did you install the 4.2 recovery version?
if you have TF300T (not TG or TL), you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob which you can download from the TWRP official website.
On 10.6.1.15.3, to enter fastboot mode, you need to reboot your tablet and hold volume down button until you see 3 icons (RCK, Android logo, and Wipe). At this point, release the volume down, but do not select any option and do not press volume up. Without doing anything, you are now in fastboot mode.
Do the usual thing you did... connect your tablet to PC via your USB cable, run cmd.exe and change your path to where you have fastboot and the "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" file. Type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
wait until you see a blue progress bar on your tablet. When that completes without error, type:
fastboot reboot
Enter TWRP recovery, Wipe dalvik and cache, try flashing the official ASUS 10.6.1.15.3 stock ROM again. Do not swipe to install SuperSU to root at this point. Just tap "Do not install." If installation goes well, reboot, and re-flash "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob", as installing the official stock ROM may have overwritten your TWRP recovery.
To root, use motochopper like you did. Or alternatively, flash a custom 10.6.1.15.3 stock-compatible kernel and let TWRP install SuperSU (Swipe to install) when prompted before you reboot system. You will get a SuperSU installer app on your launcher. Run that app and choose "Play" or "install from recovery" option. I can confirm that both method works without apparent issues. Choosing Play would be easier and faster than having to go to recovery to flash SuperSU binaries.
I hope this works for you.
matt95 said:
did you install the 4.2 recovery version?
Click to expand...
Click to collapse
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.
peerpressure said:
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.
Click to expand...
Click to collapse
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time
matt95 said:
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time
Click to expand...
Click to collapse
That's too bad I'm leaving for a month and was hoping to be able to use it while I was gone, oh well nobody to blame but myself looks like I'll be without a tablet for a while. Thank you guys for your time and help I really appreciate it, hopefully the fix will come at some point soon in the near future.
I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?
peerpressure said:
I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?
Click to expand...
Click to collapse
probably this will be fixed, i don't know why but we are working onto it... i won't sell it just for few dollars.... it's not worth it
One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.
c0ded said:
One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.
Click to expand...
Click to collapse
Thank you so much for the response, would there be a way to go about getting the 4.2 version onto my tablet though if it only boots into recovery, even when you hold down the power button/volume down? When I plug the tablet into my computer it isn't able to be recognized (I'm assuming just because it only gets to the recovery screen).
Try running "fastboot devices" on your computer while in the bootloader. Does it show anything?
Correct me if I'm wrong, but I remember reading somewhere the when in the bootloader, fastboot automatically launches on 4.2.
---------- Post added at 08:48 PM ---------- Previous post was at 08:31 PM ----------
It IS possible to flash recovery while you're in recovery. Here's how (from tobdaryl; twrp can be gotten from here: techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob):
adb push openrecovery-twrp-2.4.4.0-tf300t-4.2.blob /sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
adb shell
su
dd if=/sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob of=/dev/block/mmcblk0p4
adb reboot
An then to flash stock (once again, from tobdaryl; roms can be gotten from here: forum.xda-developers.com/showthread.php?t=1697227):
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot
Oh, well it hasn't been letting me go into the bootloader on the tablet, just boots into recovery regardless, but for what it's worth the options/commands still show up as shown in the attachment. I don't know if that's something they do anyways though.
What about "adb devices"?
c0ded said:
What about "adb devices"?
Click to expand...
Click to collapse
The list of devices attached doesn't show any it looks like it can't find it
Have you tried flashing 4.2 within TWRP?
How would I be able to go about doing that? (sorry for the inexperience and delays in response, have to wait five minutes between posts)
Download the 4.2 rom (http://www.androidfilehost.com/?fid=22926241640219416), extract it, and put the extracted zip file on to a MicroSD card. Boot into TWRP and install it from the external MicroSD (I don't know how to go about that since I don't have TWRP).
Also, you shouldn't be waiting 5 minutes between each response. You are over 10 posts.
---------- Post added at 09:12 PM ---------- Previous post was at 09:06 PM ----------
Oops. I just read the statement carefully and realized that you have to be verified by a moderator, not have over 10 posts.
I tried it out but sadly it looks like the external microsd is unable to mount so I can't pull anything off of it
edit: It gives me the option to mount a system when the ext. microsd is in but not when it is out, I don't know if that is of any help? Every other option isn't possible though.
What type of MicroSD card are you using?
A sandisk 32gb class 4 microsdhc, it's the same one I had been using with the tablet previously before this all happened
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.