Ok, so I was flashing a rom with TWRP.... somehow I deleted my whole internal storage...... So I can access TWRP and fastboot it shows up on my pc win7 but it will not adb. My nexus works just fine. I tried pdanet and naked drivers but no dice. What am I doing wrong?
Thanks,
Danny
i am also have the same problem, please help!
Danny80y said:
Ok, so I was flashing a rom with TWRP.... somehow I deleted my whole internal storage...... So I can access TWRP and fastboot it shows up on my pc win7 but it will not adb. My nexus works just fine. I tried pdanet and naked drivers but no dice. What am I doing wrong?
Thanks,
Danny
Click to expand...
Click to collapse
got to the folder you have adb.exe in, press and hold shift, rightclick and select open command prompt here, then type adb devices if your tab shows up you have adb. Put rom in same directory (folder) as adb.exe. do adb push /name of rom/ sdcard after that you "should" be able to install rom alternately, if you have an external sd card, load rom on card, latest twrp can use external sdcards....
Ok, can't get adb to pickup the tablet in recovery or fastboot. If its just trying to boot it shows up in adb... but when I try to push anything it fails. I think I am on the latest twrp but its not seeing the external sd.
Danny80y said:
Ok, can't get adb to pickup the tablet in recovery or fastboot. If its just trying to boot it shows up in adb... but when I try to push anything it fails. I think I am on the latest twrp but its not seeing the external sd.
Click to expand...
Click to collapse
So when the tab is connected to the pc and it is in recovery, does it show up correctly in device manager?
Gage_Hero said:
So when the tab is connected to the pc and it is in recovery, does it show up correctly in device manager?
Click to expand...
Click to collapse
Yes, It says transformer prime in device manager when its in bootloader and twrp but I cant get adb to see it unless its trying to boot.
Danny80y said:
Yes, It says transformer prime in device manager when its in bootloader and twrp but I cant get adb to see it unless its trying to boot.
Click to expand...
Click to collapse
You have to be running twrp when you are trying to adb... I don't think you can adb while android is running though I have never tried it.
Ok, so adb would not work in recovery at all with twrp 2.0. I could acess fastboot so i just flashed the latest twrp recovery. Once that was done I just mounted the sd card and tada..... I don't know whats up with adb but its a problem if your not running the latest twrp. Just scraped by this time...thank god recovery can now mount sd cards......
Related
fairly new to rooting, so sorry if the fix is simple (hoping it is). i have a evo 4g lte, rooted it, been having issues flashing cm10, so i would reflash a previously saved working rom, no problems. i have been using twrp for recovery. so i switched to cwmr (HUGE MISTAKE)to try and see if that would somehow fix why everytime i was flashing cm10 my phone would never load past the loading screen ( android in middle of revolving circle). basically my problem is, in recovery i cant mount ext-sd or the internal sd, i can "see" my saved backups, but cant flash them, when i try it says" no files found" i played with things for a while, somehow got some old downloaded cm10 version to work, so i atleast have a working phone, but cant mount my sdcard under storage which i need done to flash twrp back into my phone. ive been reading on how to use termianl emulator to mount sd card, but cant figuer that out, any help would be muchly appreciated, sorry for long description of my issue, i just want to be able to flash twrp, reboot into recovery and restore back to a previously working rom!!! PLEASE HELP!!!!!!!!
also... cm update is constantly running, cant stop it, my pc doesnt recognize my phone, cant mount in recovery or in settings. tried copy and pasting the saved zip files using a root browser app to relocate them and trying to reboot into recovery and flashing them, that does work... please help!!!!
If you can get into terminal emulator, then just flash twrp using that. The directions are on their website.
toolmod francis,
{ParanoiA} said:
If you can get into terminal emulator, then just flash twrp using that. The directions are on their website.
Click to expand...
Click to collapse
too late, i kept playing around with everything in recovery mode, and apprently made things worse, now the phone will recognize my ext sd and not the internal sd, which is what u need to use terminal emulator to reflash twrp, any other suggestions???
You can update recovery image through fastboot or place the twrp update zip (rename PJ75IMG.zip) on external and boot to bootloader. As for internal being corrupt, boot into twrp and mount as USB storage and format through pc
om4 said:
You can update recovery image through fastboot or place the twrp update zip (rename PJ75IMG.zip) on external and boot to bootloader. As for internal being corrupt, boot into twrp and mount as USB storage and format through pc
Click to expand...
Click to collapse
can u give me the detailed instructions on how to do that please
om4 said:
You can update recovery image through fastboot or place the twrp update zip (rename PJ75IMG.zip) on external and boot to bootloader. As for internal being corrupt, boot into twrp and mount as USB storage and format through pc
Click to expand...
Click to collapse
when trying to upload pj75img.zip in recovery from ext sd it says install aborted, it wont take, how do u update recovery image in fastboot
update... cant flash anything, lol. cant access the vfolk folder or whatever under system/etc... to try and make my ext sd my primary source of memory, cant flash twrp in terminal emulator, cant flash anything while in recovery with clockworkmod, cant flash twrp thru goomanager or any other app, cant mount internal sd while in recovery, ANY SUGGESSTIONS people, ive spent literally all weekend researching and still nothing, if someone could call me and walk me thru **** thatd help alot, hell... im to the point to where id mail my phone to someone to let them fix it, haha, please help!!!!!!!
run the ruu and start over again
i had sd card reading issues couple months ago and the ruu fixed it
Miahjera04 said:
when trying to upload pj75img.zip in recovery from ext sd it says install aborted, it wont take, how do u update recovery image in fastboot
Click to expand...
Click to collapse
ADB Tools Mini SDK
Extract this and then open the folder and hold shift+select and right click. In the menu select open command window here. Put your phone in fastboot and connect to pc. Type fastboot devices to make sure its connected. Then type fastboot flash recovery "filename.img" filename being what ever the name of the recovery file is. It should write recovery and then you can boot into twrp
flex360 said:
run the ruu and start over again
i had sd card reading issues couple months ago and the ruu fixed it
Click to expand...
Click to collapse
to run ruu, dont u have to be able to connect to pc? when i do, the pc doesnt recognize, since the internal sd isnt mounted, i cant "mount" my phone to the pc....
Boot to fastboot and run ruu
om4 said:
Boot to fastboot and run ruu
Click to expand...
Click to collapse
so that's plugged into PC to do that right, shouldn't the phone say fastboot usb or something
Boot to bootloader and select fastboot, when you connect to the pc it should say fastboot usb
om4 said:
Boot to bootloader and select fastboot, when you connect to the pc it should say fastboot usb
Click to expand...
Click to collapse
while in fastboot i cant get it to say fastboot usb sometimes, but when i run ruu, it says it cant detect my phone, so no luck there... it says usb connection error: 170
om4 said:
ADB Tools Mini SDK
Extract this and then open the folder and hold shift+select and right click. In the menu select open command window here. Put your phone in fastboot and connect to pc. Type fastboot devices to make sure its connected. Then type fastboot flash recovery "filename.img" filename being what ever the name of the recovery file is. It should write recovery and then you can boot into twrp
Click to expand...
Click to collapse
after unziping the folder and trying to run that program i get system error saying its missing a .dll file
You probably need to reinstall HTC drivers
om4 said:
Boot to fastboot and run ruu
Click to expand...
Click to collapse
ok, i atleast got ruu to take, then phoen reboots the bootloader, erases user data, then just stays on sending for about 30-45 secs, then the program stops and says unknown error and to find rom compatible with phone, im using ruu 2.13 which looks to be the newest one... : (
om4 said:
You probably need to reinstall HTC drivers
Click to expand...
Click to collapse
i reinstalled 1000 times. lol.... im currently working on getting adb prompt to work, downloaded the neccesary java stuff, but cant get the prompt to open, been reading about having to relocate java files, and stuff, but havin dificulty... hoping that if i can get into an emulator on the pc i can force flash twrp or something, anyone know how to help with that?
FINALLY FIXED!!!!!! had to relock bootloader for the ruu to take, smh... such an easy thing to over look, but got back to factory rom.. bot to root again, lol... BIG LESSON LEARNED, thanks for all help
my device is stuck in bootloop with no backup and is not showing up in adb for me to push rom to phone? suggestions????
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
NasaGeek said:
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
Click to expand...
Click to collapse
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
jizang said:
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
1.0.31 and tried both twrp and cwm
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
NasaGeek said:
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
Click to expand...
Click to collapse
yea ridiculous amount times
I had the same problem i could not adb sideload a Rom,in the end i had to flash stock ruu to save my phone
Sent from my HTC One X+ using xda premium
indie12 said:
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
Click to expand...
Click to collapse
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
reaper90 said:
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
Click to expand...
Click to collapse
doesn't work with twrp either,
also forgot to mention is odd that adb doesn't find device since i can flash new recovery / kernal via fastboot?
adb discovering my device in sideload now but not allowing the sideload? how can i push the rom to sdcard via adb?
indie12 said:
doesn't work with twrp either
Click to expand...
Click to collapse
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
reaper90 said:
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
Click to expand...
Click to collapse
its just worked, transfering the rom now, no idea what caused it to work this time but it is so thanks
Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
NinjaKenZen said:
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
Click to expand...
Click to collapse
If you can push files on sd card, use the TWRP back-up from here to restore to stock.
http://forum.xda-developers.com/showthread.php?t=2414238
You'll at least get it working again.
Thanks, somehow when I updated the bootloader, the boot.img restriction got lifted after I just entered the command again when 'unknown failure' came up. I was at this point able to access the sd card under a buggy rom start-up.I used TWRP to flash a new rom.
Fixed.
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
loaybilal said:
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
Click to expand...
Click to collapse
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
imcontreras said:
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
Click to expand...
Click to collapse
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
roshak said:
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
Click to expand...
Click to collapse
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
roshak said:
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
Click to expand...
Click to collapse
Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
Thank you!
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app