Database Info

HTC One S (S3 )No SD Card Version Help.

Hi Trev here,I am a New member and hope this is posted in the correct place,I have a HTC ONE S S3 Version chip,No SD card version,has OPTUS AU Firmware on it with CID OPTUS_001,My system stopped booting when i tried to get Nova 3 game working,at the moment its not compatible for my device,but i read on the forums if i edited my Build prop I could get it working again,but sadly enough,it stopped booting the OS and i can sometimes get into the boot loader,Now the only way i can see to fix this is to get the original optus ruu and flash it but i cant find it any where,and i cannot install any of the other stock s3 roms because i don't have super CID,do you guys have any ideas,cheers Trev.

Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.

+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?

adb shell
qzem said:
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
Click to expand...
Click to collapse
Thanks for your reply,how do i change the build prop through adb shell,cheers.

build prop from one s s3 ruu
frdd said:
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
Click to expand...
Click to collapse
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.

trevor3737 said:
Thanks for your reply,how do i change the build prop through adb shell,cheers.
Click to expand...
Click to collapse
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
trevor3737 said:
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
Click to expand...
Click to collapse
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop

re build prop
frdd said:
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
Click to expand...
Click to collapse
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.

trevor3737 said:
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
Click to expand...
Click to collapse
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.

re adb pull
qzem said:
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
Click to expand...
Click to collapse
is where ever the place i send the build prop to,and when i run adb it say device not found,cheers.

Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff

re
frdd said:
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
Click to expand...
Click to collapse
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.

trevor3737 said:
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
Click to expand...
Click to collapse
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...

re recovery
frdd said:
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
Click to expand...
Click to collapse
I have uploaded a pic of the boot loader,i have root access via pauls super boot,boot loader is unlocked and i know how to re lock if i have to ,cheers.

trevor3737 said:
When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers
Click to expand...
Click to collapse
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?

re recovery
[/ATTACH]
frdd said:
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
Click to expand...
Click to collapse
thats what happens when i hit recovery from the bootloader screen.

that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.

re flash recovery
qzem said:
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
Click to expand...
Click to collapse
it says remote not allowed

re
trevor3737 said:
it says remote not allowed
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.188s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.188s

Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it

re flash recovery
frdd said:
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.172s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.188s
C:\Android>fastboot flash recovery recovery-signed.img
error: cannot load 'recovery-signed.img'
the fastboot boot recovery_signed.img way and the fastboot flash recovery recovery-signed.img way

[Q] Help needed, Stuck in bootloop :(

Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig

craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
same issue here!!! can someone please tell me how to restore my nexus 5 without the toolkits? would appreciate it alot!!

Hoping someone has a quick fix to this! I can get into bootloader so there must still be hope? :')

here
craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
i used Kwonggers toolkit and found several errors and bugs annoying which of them either critical or not.

Have you done a factory/data reset in recovery? That'll usually get you past a boot loop

jd1639 said:
Have you done a factory/data reset in recovery? That'll usually get you past a boot loop
Click to expand...
Click to collapse
When i try and factory reset in recovery it says it cant mount to anything!

fastboot flash userdata
if you unlock your phone, you should let the system boot up once before you flash twrp/cwm. it rebuilds the directory structure.

craig14 said:
When i try and factory reset in recovery it says it cant mount to anything!
Click to expand...
Click to collapse
If it were me, I'd flash the factory image and start over. Never did like tool kits that do every thing for you.

craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
Flash a stock image to take phone back to stock.
Then fastboot oem unlock for bootloader
let the phone load up once, then do fastboot flash recovery xxxx.img
As for right now when you're in bootloader, try flashing stock recovery or FDR like another user said.

craig14 said:
Hi guys, after some helpppp
I unlocked my phone and installed TWRP, then i went to copy Superuser files to my phone, The internal memory had no folders in it whatsoever...
I rebooted the phone and still nothing so i used the "out of box restore" function from the Kwonggers toolkit, now im just stuck in bootloop
any ideas?
Thanks Craig
Click to expand...
Click to collapse
Download the factory image from here https://developers.google.com/android/nexus/images#hammerhead and flash it.

I cant flash anything because i cant copy any files to the phone, nothing will mount! :'(

craig14 said:
I cant flash anything because i cant copy any files to the phone, nothing will mount! :'(
Click to expand...
Click to collapse
You don't have to copy anything to your phone. Google how to set up adb / fastboot on your computer. Once set up run the fastboot flash userdata from a command prompt that the other user suggested, sorry on don't remember his name (edit, Zepius). Do you have usb debugging on?

Still bootlooping after flash
Hi,
I have the same issue so I downloaded the factory image on the website then I tried to do these steps :
Code:
- fastboot erase boot
- fastboot erase cache
- fastboot erase recovery
- fastboot erase system
- fastboot erase userdata
- fastboot flash bootloader bootloader-hammerhead.img
- fastboot reboot-bootloader
[ Wait ]
- fastboot -w update rom-hammerhead.zip
(File names might be differents)
But now I still have a bootloop then I tried to acces to recovery mode but I can't mount /sdcard :crying:

Don't just erase. Flash relevant partitions, you phone will return to stock and boot loop will be gone.

Thank's but I don't know which command I have to type
I think it's this one but I'm not sure
Code:
flash <partition> [ <filename> ] write a file to a flash partition
Could you write the command please
---------- Post added at 10:42 PM ---------- Previous post was at 10:33 PM ----------
Petrovski80 said:
Don't just erase. Flash relevant partitions, you phone will return to stock and boot loop will be gone.
Click to expand...
Click to collapse
Thank's but I don't know what I have to type exactly :/
Could you tell me ?

Alex01723 said:
Thank's but I don't know which command I have to type
I think it's this one but I'm not sure
Code:
flash <partition> [ <filename> ] write a file to a flash partition
Could you write the command please
---------- Post added at 10:42 PM ---------- Previous post was at 10:33 PM ----------
Thank's but I don't know what I have to type exactly :/
Could you tell me ?
Click to expand...
Click to collapse
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.

Petrovski80 said:
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.
Click to expand...
Click to collapse
I LOVE YOU, i am forever in your debt

Problem Solved
Petrovski80 said:
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.
Click to expand...
Click to collapse
Love you too you solved the problem thank's a lot

Petrovski80 said:
You need to read this: http://forum.xda-developers.com/showthread.php?t=2513701
Use method 2. I'm not sure about the scrips, haven't used those.
Click to expand...
Click to collapse
Heyy man, half a year later and Ill still thank you for this.. Totally saved my bricked Nexus 5.. Thank you Thank you... I can now sleep well tonight. :good:

[Q] boot loop cannot get PC to read device

Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?

sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?

sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:

tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?

sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.

tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks

sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard

tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere

sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.

tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111

sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img

tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip

sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.

Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:

[Q] Can't mount partitions after installing WTRP.

Hi everyone,
I was hoping someone might have some advise for me to try. I did the following and now I can't seem to boot the ROM I installed and/or load the partitions to wipe them. TWRP is asking for a password (which I just cancel) and then it can't mount the partitions. Here is what I did.
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Any advise would be appreciated. Thank you. The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file. Thanks so much for your time. Someone is helping me on the side via PM, if I get anywhere with that, I'll post the resolution here.
-Tony

qzmicro said:
The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file.
Click to expand...
Click to collapse
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias

Any suggestions?
manhart said:
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Click to expand...
Click to collapse
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony

qzmicro said:
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
Click to expand...
Click to collapse
That is a rom based on CM11 kitkat. Did you read the requirements (which the cmb creators unfortunately just touch upon in their op) before you flashed it?
The CM11 OP states that you have to be on 10.16.1.14.x bootloader and CWM 6.0.4.4 as a recovery.
It also clearly states that TWRP has problems with KitKat. Supposedly the latest TWRP version works, but to my knowledge that is not confirmed. Don't know what TWRP version you initially flashed, but then you flashed one that's totally outdated and possibly not even compatible with your bootloader.....
I hope you still have access to fastboot.... download CWM 6.0.4.4. and flash it. Then try to flash the rom again.
But check your bootloader version first!
Read this: http://forum.xda-developers.com/showthread.php?t=1957660

Now I can't seem to erase certain partitions or write to system...
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony

qzmicro said:
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
Click to expand...
Click to collapse
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2

It's been a single ? since I started using fastboot.
berndblb said:
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q

qzmicro said:
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
Click to expand...
Click to collapse
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip

Drivers are installed now and stilll ? for fastboot devices.
berndblb said:
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Click to expand...
Click to collapse
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony

qzmicro said:
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
Click to expand...
Click to collapse
I have never heard of this issue.....
Please post the fastboot commands you are using.

Liunx Mint 32 bit
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036

I will document what I have done so far, step by step.
berndblb said:
I have never heard of this issue.....
Please post the fastboot commands you are using.
Click to expand...
Click to collapse
I'll post shortly what I have done and how it went down. Specifically the commands used in fastboot as that is the ONLY tool I've used so far besides the ASUS Unlock Tool. Standbye...
-Tony

I'll be installing linux mint 32 on a VM....
lj50036 said:
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
Click to expand...
Click to collapse
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
UPDATE: Here is all the commands I've tried on my Tablet...
Originally I did this:
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Since then I've tried this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob (blob was in same directory as fastboot and I got it form the latest asus firmware zip file) <-- Failed It sends the data okay but fails to write to the disc. Error on ASUS tablet in red also confirms the command write:system failed and gives a memory address.
fastboot -i 0x0B05 reboot
Please note that some of the erase commands simply hung. I had to restart the tablet to go back into fastboot mode. When I restart it sometimes they erase successfully. Not sure why. I know I couldn't erase userdata at all, and recently tried again and it worked.
I now have a copy of Mint Linux 32-bit ready to go. What should I try?
-Tony

VM Mint
qzmicro said:
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
Click to expand...
Click to collapse
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]

lj50036 said:
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
Click to expand...
Click to collapse
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
P.s. I do not believe I have NVFLASH. I had firmware that didn't alow for it, so I just did the Asus Unlock Tool. Please refer to my previous message about anything/everything I've done so far. Cheers.

qzmicro said:
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
Click to expand...
Click to collapse
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices

lj50036 said:
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
Click to expand...
Click to collapse
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony

Great
qzmicro said:
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Click to expand...
Click to collapse
Sounds great!!! No worries on a time.. Just let me know... Thx lj

Linux Mint still shows ?????? as my serial.
lj50036 said:
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Click to expand...
Click to collapse
So, I installed fastboot and ADB and installed all updates on the OS for kicks. Then tried the fastboot devices command and I recieved:
Code:
[email protected] ~ $ fastboot devices
no permissions fastboot
[email protected] ~ $ sudo fastboot devices
[sudo] password for amascolo:
???????????? fastboot
[email protected] ~ $
...? Still no serial number. I've seen this since I took it out of the box. Not sure what that is all about, I have found no one else with this issue. I'm going to try to flsh and I'll let you know what happens.
-Tony
UPDATE: I have tried to re-flash the damn thing and it still fails. Here is what I see...
Code:
[email protected] / $ sudo fastboot -i 0x0B05 flash staging /home/amascolo/Desktop/blob
sending 'staging' (800927 KB)...
OKAY [135.763s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 136.934s
[email protected] / $
Any ideas fellas? Seems I simply am not able to write to the system partition again.
-Tony

* SIGH *
Anyone have any ideas as to why I can't write to my device? Any ideas as to what I may try? Please advise, I'm not looking forward to throwing this thing away. Cheers.
-Tony

Screwed [Solved]

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 ...