Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
What is your recovery?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Danny Samuel said:
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Click to expand...
Click to collapse
Also, let us know the OS you are using.. Win 8 x64 is a tricky BS.. sometimes the drivers work, some times they don't...
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
I'm on Windows 7 and had the same problem the other night when I needed to sideload a rom, it just would not find my device. Even though I had previously flashed kernels without any issues.
I ended up removing the drivers, re-installing them using Hassoons toolkit and rebooting both PC and phone. It will work, just can be a bit finnicky. I used his toolkit to sideload a rom through twrp.
cortem said:
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
Click to expand...
Click to collapse
I hope you are giving enough time for the device to be recognized.
BTW TWRP has been updated to 2.6
Sent from my GT-I9300 using xda premium
Related
guys I have a weird problem, I installed honeycomb foliomod then I switched to 1.4 and I lost so I went back to the recovery cmw classic, now when I go to install cmw (cmw compatible for any folio) I get the droid with the signal of danger so I'm obliged to restart the tablet, and now I can not install the recovery, now someone can give me a little hand to understand how do I install cmw?
The fastest way is to install it via fastbooot.
you have a guide to install via fastboot? I honestly do not even know what this is fastboot, excuse my ignorance.
Just find my guide in General and then look into my HC thread for tutorial of using fastboot and then type:
fastboot erase recovery
fastboot flash recovery recovery.img reboot
Sent from my IDEOS S7 Slim using XDA App
I have a small problem with the fastboot, I wrote out the cmd <waiting device> for ... I do not understand what's the problem
I noticed that the drivers will not install, you have a method to install drivers Folio 100?
Are you using W7 or Linux?
follow this guide
http://forum.xda-developers.com/showthread.php?t=1119507
you need @windows every single step. Deinstall the old Drivers
best regards
I have windows 7, any suggestions?
however, I want to thank you for the answers you are giving me.
mauri90 said:
I have windows 7, any suggestions?
however, I want to thank you for the answers you are giving me.
Click to expand...
Click to collapse
Follow what realmausi has posted. That will setup the drivers in Win 7 and allow you to communicate with the folio when it's in fastboot mode...
thanks a lot guys, really do not know how to thank you, finally I made it through Davvi not as stupid as I thought it would pass, the problem was in the drivers, thanks again
So i accidently wiped my phone and i have twerp so i tried to push a new os to my phone threw adb but whern a type adb devices no devices show up and i know i have the drivers installed becsause ive done this before 5 times. and i downloades the android sdk and installed everything from 4.0 to 4.4 in the sdk managers. please help me. the problem was i tried to flash twrp using flashify but it took the place of my os.
SuperAndroidTech said:
So i accidently wiped my phone and i have twerp so i tried to push a new os to my phone threw adb but whern a type adb devices no devices show up and i know i have the drivers installed becsause ive done this before 5 times. and i downloades the android sdk and installed everything from 4.0 to 4.4 in the sdk managers. please help me. the problem was i tried to flash twrp using flashify but it took the place of my os.
Click to expand...
Click to collapse
twrp took the place of my OS. and clockwork mod touch is my recovery is there any way i can fix this.
SuperAndroidTech said:
twrp took the place of my OS. and clockwork mod touch is my recovery is there any way i can fix this.
Click to expand...
Click to collapse
you can RUU back to stock
do you have an AT&T Phone
Alright, i had the system update downloaded and it went to twrp. I realized this wouldn't work. So i was going to sideload the update but for some reason ADB doesn't see my watch in sideload mode. Is this a driver thing or something else?
I had trouble with that in win 8.1. I just uninstalled drives while in twrp. Then reinstall should fix u up.
dude1981 said:
I had trouble with that in win 8.1. I just uninstalled drives while in twrp. Then reinstall should fix u up.
Click to expand...
Click to collapse
Thanks!
So I was trying CM12 and it flashed the crappy Cyanogen Recovery over TWRP. I was trying to flash it again through Flashify and other similar apps but it just won't work. I'm now trying to flash TWRP again through Fastboot...but i can't get to install the proper drivers for Windows 10. I tried flashboot drivers and many others I've found online with no success.
How can I get my tablet recognized by Windows 10 ?
Thanks !
DannyBiker said:
So I was trying CM12 and it flashed the crappy Cyanogen Recovery over TWRP. I was trying to flash it again through Flashify and other similar apps but it just won't work. I'm now trying to flash TWRP again through Fastboot...but i can't get to install the proper drivers for Windows 10. I tried flashboot drivers and many others I've found online with no success.
How can I get my tablet recognized by Windows 10 ?
Thanks !
Click to expand...
Click to collapse
I believe you have to disable driver signing in Windows 10.
BladeRunner said:
I believe you have to disable driver signing in Windows 10.
Click to expand...
Click to collapse
Not good enough solution.
We want drivers test signed so we can use them without exposing our production machine to a huge security risk.
Therefore, Test sign procedure or alredy signed Sony Xperia Z2 Tablet Family is desirable as a proper solution here.
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
zsajak said:
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
sanke1 said:
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
Click to expand...
Click to collapse
How can I follow your guide If I cannot flash the recovery?
zsajak said:
How can I follow your guide If I cannot flash the recovery?
Click to expand...
Click to collapse
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
For some reason it was not working, it is now.
I still get a bootloop when I try to flash the resurrection remix rom.
cm13 by teamspain worked fine though
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
I followed your guide and installed twrp correctly and it worked.
I cannot install any rom besides cm13 unofficial though, i always get a bootloop if I install resurrection remix for example.
Its really very annoying, I wiped everything including data and system, only the official 16s roms works and cm13 unofficial, all other roms result in a bootloop.
something is not right here.
twrp not mounting storage data
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
twrp flased but its not mounting storage data, also sideload command to install supersu.zip didnt worked tried several times
its just stopping exactly at 73% everytime