Related
Hello,
I tried upgrading CWM via ROM Manager...and can confirm: It dont work
If I try to go to CWM, equal how (Software or Hardwarebuttons) he says starting CWM and nothing happens. Only way is to boot with Vol+.
Also failt install CWM via apk.
Only way I can imagine is to flash a old rom with CWM, maybe honecomb, via MicroSD? Any working link to such a old rom? And how to flash?
Thank you in advance.
ArnomaF said:
Hello,
I tried upgrading CWM via ROM Manager...and can confirm: It dont work
If I try to go to CWM, equal how (Software or Hardwarebuttons) he says starting CWM and nothing happens. Only way is to boot with Vol+.
Also failt install CWM via apk.
Only way I can imagine is to flash a old rom with CWM, maybe honecomb, via MicroSD? Any working link to such a old rom? And how to flash?
Thank you in advance.
Click to expand...
Click to collapse
You say you lost cwm, so how are you going to flash an older rom via cwm?
Team Rouge has an nvflash version of their recovery or try RecoveryInstaller
Rom manager is bad news for the tf101, please don't use it in the future.
To fix this (Run in an adb-shell on a computer or terminal emulator on the device, if you can boot, I hope you still have root.)
Download any cwm-flashable recovery. Extract the recoveryblob file out of the zip and place it on your tf, via mass storage or ADB (I recommend rouge)
Then run these commands in term em or adb shell
Code:
su
dd if=/your/blob/here of=/dev/block/mmcblk0p4 (Please note the your/blob/here part, you need to type the path of where you placed your recoveryblob here)
reboot
Should get you backing into a non-borked recovery.
Thing O Doom said:
Should get you backing into a non-borked recovery.
Click to expand...
Click to collapse
****. It dont work.
Have read about it. But you had give me the way to try.
Have tested Rouge and Rouch recoveryblob.
Both the same.
su (Grant)
dd if=/Removable/MicroSD/recoveryblob of=/dev/block/mmcblk0p4
Gives me:
8984+1 records in
8984+1 records out
4599884 bytes transfered in...
[email protected]:/#
Looks all fine in my eyes. (I'm DOS-Windows, not Linux)
Why it dont works??
Booting recovery kernel image-> nothing happens
baseballfanz said:
You say you lost cwm, so how are you going to flash an older rom via cwm?
Click to expand...
Click to collapse
Not via CWM with CWM I wrote...
baseballfanz said:
Team Rouge has an nvflash version of their recoveryr
Click to expand...
Click to collapse
How can I flash what? Only put on MicroSD? And then?
baseballfanz said:
or try RecoveryInstaller
Click to expand...
Click to collapse
Have tried. Dont work
Via and with are the same... xD pointless from here.
Last step is to try to reflash the bootloader EBT partition and see if that's the issue, since your recovery flashed fine.
If not, NvFlash here you come!
Thing O Doom said:
Last step is to try to reflash the bootloader EBT partition
Click to expand...
Click to collapse
Ok. How do I do that?
Blobunpack a stock OTA from asus's site,
then take the .EBT rename it to blob with no extension and use the same command to flash it.
ArnomaF said:
Ok. How do I do that?
Click to expand...
Click to collapse
I think the best way now is to go back to stock.
Same way use NVflash to flash full firmware and start again rooting and installing CWM...
farsight73 said:
I think the best way now is to go back to stock.
Same way use NVflash to flash full firmware and start again rooting and installing CWM...
Click to expand...
Click to collapse
Agree with you. But then I need a link to a easy rootable firmware (up to 8.6.6.19 for Razorclaw) and a short description how to flash.
Try my PERI one-click, it should install recovery and walk you through rooting just fine, if you can boot into android. If not just flash the latest OTA completely (Everything including ebt) should fix any recovery and bootloader problems. Then you can run PERI and it will install recovery and root for sure. If you want
I think I going to be crasy, because 3 days later and no sucsess
to sum up:
1. Gnufabio's RecoveryInstaller.apk
work, reboot, stuck, Power&Vol-, Vol+ stuck at booting recovery kernel image
2. NVFlash
somebody wrote NVFlash is inpossible for B80
seems to be true:
rcm version 0X4
Comand send failed (usb write failed)
3. my last hope: ADB
a) Power&Vol+, adb shell-> device not found (Device Manager: Nvidia USB boot-recovery driver for mobile devices)
b) Power&Vol-, Vol+, adb shell:
List of devices:
0123456789ABCDEF offline
Device Manager: Asus Transformer ADB Interface
c) normal reboot, stuck on EeePad Screen, same as b)
Now I'm on the end of my ideas...
BTW. Tried also this, but dont work.
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 in Terminal on the pad->done, but nothing happens
BTW2 Im on Megatron 1.1.4 - It works but I cant take part of the development on this.
BTW3 @Thing o Doom: Your PERI also dont work. Think it belonges to the ADB Problems.
BTW4 If I try to going into recovery there is written:
Android WW_epad-user bootloader < e> released by WW_epad-8.6.6.23-20111202
Checking for Android ota recovery
Skipping android ota checking
Checking for RCK..press key <VOL_Up> in 5 sec to enter RCK
Booting recovery kernel image
If I understand that right it may possible to flash a OTA-Update with this method?
Which schould i use?
BTW5 Tried to copy Rouges recoveryblob to mmcblk04p. Was sucessful, but nothing happens
EDIT:
I just talked to Rayman and this won't work for you, TF101G devices have another SBK. I'm sorry.
Hi there.
I made this tool for you.
http://www.mediafire.com/?5wi7ga8c7b4wz1p
Unzip and start EasyFlasher.exe
1. Put your tablet in APX mode (Hold down Power and volume up)
2. Install APX drivers if needed
3. In EasyFlasher, click on the "Wheelie" button, this prepares your tablet for nvflash.
4. Click Flash recovery.
This should work if you have a SBK2 device, I have heard that newer TF101Gs have a newer SBK, if you have a newer SBK, this will not work.
EDIT:
This tool will only work with any SBK2 device at the moment.
Credits to AndroidRoot.mobi for Wheelie.
Removed all my Dropbox links because they disabled my account due to too much traffic, if you guys want them back please consider donating a buck or two for a Mediafire Pro account...​I didn't develop this, just getting the word out that's it's officially available for the Nexus 7. You can either install the "normal" version or touch version from ROM Manager
UPDATE 11/16 new version posted by Koush 6.0.1.9
CWM Regular
CWM Touch
Here is the CWM ZIP by osm0sis:
Touch 6.0.1.9
Regualr 6.0.1.9
You NEED an unlocked bootloader in order to flash this check this thread on how-to unlock/root etc Nexus 7 Toolkit
If you just want to apply an OTA update and you haven't got it, you can do so by booting into CWM without installing it or having root.
first download and save OTA files from OTA 4.1.1 files and save to your /sdcard
then use
./adb reboot bootloader
./fastboot boot recovery-clockwork-touch-6.0.1.9-grouper.img
select install zip from sdcard
toggle signature verification and make sure it's disabled
select the file you downloaded earlier and install
reboot and you will be updated
Click to expand...
Click to collapse
If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p
now use
./adb reboot bootloader
./fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
./adb reboot
Click to expand...
Click to collapse
You now have CWM installed.
I'm not responsible if you brick your tablet, it blows up mid flash etc
Make sure you know how to use ADB and have the SDK installed, you need that in order to do all of the above steps
Also make sure you have the recovery files saved to /sdk/platform-tools and also fastboot.exe has to be there also
Any commands that start with ./ are for linux/osx...just remove those when using windows
Click to expand...
Click to collapse
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
** edit 7/21/12**
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf
Feel free to mirror!
Sent from my Nexus 7 using xda app-developers app
Flashing when I get home thanks.
Sent from my Galaxy Nexus using xda app-developers app
I flashed this from rom manager and so far have not had any of the problems I have had in some of the interim CWM's like inability to delete back ups or mounting system.
hey dude it's 6.0.0.6 not 6.0.6
mrich137 said:
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Shano56 said:
hey dude it's 6.0.0.6 not 6.0.6
Click to expand...
Click to collapse
oops, typo...thanks, I will fix it now
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
It works as long as you're connected to a computer, so you can access recovery from bootloader you just need to be hooked to a computer.
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
JoeM01 said:
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
camblue said:
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
Click to expand...
Click to collapse
Flashed fine here also. Works without flaw so far.
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
Did you install the ota after you rooted and installed the recovery? I soft bricked too and I think that was the reason why. Something about the ota overwrote the recovery partition. Best thing to do is download ROM manager and click the first option to flash cwm. Then click the next button to boot into recovery. Then just flash the zip I posted to upgrade to touch.
**edit** just tried to boot into recovery from the boot loader and got stuck at the Google screen too. Holding all three buttons rebooted and started up as normal. Maybe the boot loader boot into recovery is pointing to a different partition for some reason?
Booting into recovery from ROM manager works though. That's how I've been getting in.
Sent from my Galaxy Nexus using xda app-developers app
thanks for the heads up
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
What did you try?
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
BennyJr said:
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
Click to expand...
Click to collapse
camblue said:
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
Click to expand...
Click to collapse
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Bootloader = fastboot. Any adb commands wont work
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
Sent from my Galaxy Nexus using xda app-developers app
Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
Sent from my Nexus 7 using xda premium
Hi everybody
I've been so stupid
I tried to flash Jelly Bean to my nexus s,
I forgot to root, restarted, it didn't start, I went into stock recovery, deleted system by accident, now it won't boot anymore.
Can I do something about it or is it really dead?
Dennis
If the phone turns on and fastboot works then no it is not dead.Follow the instructions below to install CWM on your phone and then you can flash stock/custom rom using CWM.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery
Android-Junky said:
If the phone turns on and fastboot works then no it is not dead.Follow the instructions below to install CWM on your phone and then you can flash stock/custom rom using CWM.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery
Click to expand...
Click to collapse
Thank you for you reply. I have adb installed and it worked, but now my laptop won't recognize my device anymore:S
Denn77 said:
Hi everybody
I've been so stupid
I tried to flash Jelly Bean to my nexus s,
I forgot to root, restarted, it didn't start, I went into stock recovery, deleted system by accident, now it won't boot anymore.
Can I do something about it or is it really dead?
Dennis
Click to expand...
Click to collapse
Lol, forgot to root? That made me literally laugh out loud. Are you the same guy that posted this on Engadget.com? Some guy just explained on there of how he did the exact same thing...
Make sure you are running as admin on your computer. Right click on whatever program you are using and click "run as admin". That can solve most of the problems with your computer not recognizing the device. Good thing you messed up on the nexus. It's a pretty good phone for fixing newb mistakes.
Sent from my Galaxy Nexus using xda app-developers app
nikeman513 said:
Lol, forgot to root? That made me literally laugh out loud. Are you the same guy that posted this on Engadget.com? Some guy just explained on there of how he did the exact same thing...
Make sure you are running as admin on your computer. Right click on whatever program you are using and click "run as admin". That can solve most of the problems with your computer not recognizing the device. Good thing you messed up on the nexus. It's a pretty good phone for fixing newb mistakes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Well, i forgot to flash the root as I first wanted to see if Jelly Bean worked at all.. And it wasn't me on Engadget.com
I really really really hope I can fix it, as I don't want to lose my nexus s, it's a great phone!
If i can fix it, I'll be more carefull in the future
thanks for your replies!
PdaNet hangs on 'installing PdaNet to your phone'
Solved
He's alive again (My phone wasn't dead, I know)
Thank you so much!
Good! We learn from mistakes! Rooting is fun and has many benefits! Hard parts done, flash away!
Sent from my Galaxy Nexus using xda app-developers app
OK, let's start from the beginning. I installed TWRP recovery, EOS 4 and KAT Kernel successfully today and I was quite happy with the results but decided to try Revolution HD. Since I am more used to ROM Manager, I decided to change TWRP to CWM and use it for recovery. After that things got messy. First of all CWM said that it can't find sd card and secondly my TF wouldn't boot up anymore after exiting recovery. I've been messing with it for hours and can't find a solution. It only got worse and for awhile the only way I could access it through ADB was to do a cold boot and it would get stuck at the spinning EOS logo, but atleast it would allow ADB access.
Last thing I tried is this and the tablet reboots, but it's still stuck on spinng EOS logo, but I don't have to do a cold boot to get stuck there anymore
AW: [Q] TF101G stuck on boot,cannot access recovery. Any way to fix via adb maybe?
So, for all those who have the same problem as I had, I found a solution and its a pretty easy one!
In my case, it seemed to be a permission problem concerning /dev/block/mmcblk0p3. So, I went through different threads and found a suitable solution here:
http://forum.xda-developers.com/show...530337&page=20.
All you have to do is to enter terminal emulator on your device (or use adb alternatively) and enter:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
You should see the asus eee pad screen with a blue progression bar and then it should boot normally. Thanks to partio for this hint! :thumbup:
Sent from my Transformer TF101G using xda app-developers app
Click to expand...
Click to collapse
If I select recovery after reboot, it will get stuck at Booting recovery kernel image. So any ideas what to do next ?
Edit: That's what is visible on my tab from QtADB
OK I've tried everything I could find but nothing
Computer recognizes it fine when it's cold booting and as you can see, ADB works on it but can't get fastboot to work. I guess the solution would be to get a working recovery on it again, but I can't figure out how without fastboot.
http://forum.xda-developers.com/showthread.php?t=1671598
Don't use ROM manager.
Get adb access and use it to run that command you quoted, then reboot, run the command again, and run adb push recoveryblob /sdcard/ then dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 to restore a working recovery. Then from there mount and reflash.
Thing O Doom said:
http://forum.xda-developers.com/showthread.php?t=1671598
Don't use ROM manager.
Get adb access and use it to run that command you quoted, then reboot, run the command again, and run adb push recoveryblob /sdcard/ then dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4 to restore a working recovery. Then from there mount and reflash.
Click to expand...
Click to collapse
OK, tried it but I couldn't complete it.
The first part works ok and after reboot I see the blue line filling up and after that the usual EeePad screen and it boots to EOS loading screen and I can get ADB access again.
But after I have to write "adb push recoveryblob /sdcard/" CMD says
Daemon not running starting it nor on port 5038
Daemon started successfully
And after that it just doesn't do a thing and then it reboots and I can't enter the final code. And under directory tree the sdcard is not a folder but it's just a file or smthing like that "sdcard -> /storage/emulated/legacy" is written.
EDIT:
Man, I would kiss you if I could ! Worked, finally it worked !
So the problem was, that it couldn't find sdcard and so it rebooted. Changed the sdcard to another directory, /dev in my case and after that it completed it and booted perfectly into recovery. AWESOME !
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?
lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!
lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?
berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Wow what a difference DATA2SD and ROM2SD make!
lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW
lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?
lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...