used Flash Image GUI to flash Viper rom and when it boot into boot loader my custom TWRP Recovery is gone. so now im stuck in HBOOT screen..so i tried to ADB CMD and it says (no device detected) tried multi times and nothing.. is my 3D bricked or is there something that im over looking during this frustration..thanks for any help.
im Hboot 1.5
and did a search and nothing with this situation
Your phone would be brick if it doesnt turn on . Try to do a backup
Sent from my PG86100 using XDA Premium App
First flashing again recovery.
Sent from my PG86100 using XDA Premium App
Efrencalvario said:
First flashing again recovery.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
i tried to fastboot useing ADB cmd but i cant get it to recognize the phone, it keeps saying device not detect or found... thats what got me going crazy
if i could get it to recognize the phone i was thinking of trying to reflas recovery
bricked phone?
If you can still get your phone to boot up into HBOOT then your device is not bricked to say the least. The next thing I would try is to remove all the drivers on your, WIN/MAC/LINUX?? computer and reload those to see if the device can be noticed again through your computer. ALL HOPE IS NOT LOST, hang in there!
malignant098 said:
If you can still get your phone to boot up into HBOOT then your device is not bricked to say the least. The next thing I would try is to remove all the drivers on your, WIN/MAC/LINUX?? computer and reload those to see if the device can be noticed again through your computer. ALL HOPE IS NOT LOST, hang in there!
Click to expand...
Click to collapse
i uninstalled SDK and HTC Drivers restarted comp then installed HTC Drivers and SDK Tool and restarted comp then i opened up CMD Window and tried again and same thing.. (device not found) windows detects the phone when in Fastboot usb mode b/c windows make that sound when connecting a device..
im trying to keep faith..this is what the CMD window says
C:\Android new\android-sdk\platform-tools>adb push recovery.img /sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
If worst comes to worse you may need to wipe and relock use the a RUU exe 2.17 If your CDMA..
Then make sure debug is on and unlock and flash a recovery fasboot boot recovery.img and wipe and flash rom...
Debug isn't on that is why ADB isn't finding your phone man..
ok i got it going..lol.. what a relief i did these 2 steps from a diff thread and it worked once it booted the recovery i knew what to do from that point
6. Open the command prompt on your PC (press START and type cmd) In the command window, type: \cd\rootevo3dnew to get to C:\rootevo3dnew).
7. Type the following command in the command prompt: fastboot boot cwm-4.0.1.4-shooter.img and press enter.
just wanted to thank everyone for their help
now i can call Sprint and cancel my replacement
Related
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
I don't know for sure so I'll just tell you what I have in my folder where I have my fastboot.exe. I also have the adb files which include:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Not sure if that means anything though. Have you updated your drivers recently? What OS does your laptop use? I know if you have the wrong drivers it can cause problems like using 32 bit drivers on a 64 bit system.
As far as wiping, it is recommended especially if you go from a different ROM to another. I usually use this which was suggested by a user named @CaelanT:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
jonnyboyC13 said:
Ok so I wanted to try out some new Tom's besides the cm7 weeklies and figured I should do a deeper wipe than just the normal cwm wipe but I can't seem to figure put how to get fastboot working I set it up on my phone and navigated to the file ln my laptop and just issued a reboot so I knew how it worked before I started wiping but it just sat there and never rebooted I have is there additional files I need besides the fastboot exe to do a wipe. And is it advised to erase all the partitions before flashing a new rom or is it not needed
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well just updated motohelper and no luck still no response in fastboot maybe my procedure is wrong in what way do you wipe
Sent from my MB860 using XDA App
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Do you have "USB Debugging" checked when using adb?
How did you unlock the bootloader? It seems weird that it's not working since you need an unlocked bootloader to run CM7 (which you said you had) and you need fastboot to unlock the bootloader. I don't understand what could have changed since then. Are you using a different computer now?
Just to make sure we're on the same page, are you putting the phone into fastboot before you issue the fastboot commands?
[Turn off phone->Hold Vol down and press power->Keep holding Vol down until it says "Fastboot" at the top of the screen->Release Vol down and then press Vol up]
jonnyboyC13 said:
ok learning process. didn't even realize you needed adb to use fastboot. so i got that on my laptop.
adb isn't recognizing my phone either so i think i'm still missing something
Right now i know i have the motohelper install adb and and the fastboot files. I may have some other files when i first got my phone that just installed with it was still blurred but i don't know
Click to expand...
Click to collapse
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
There are only 2 things I can think of after the details you have given me:
1. Are you making sure it says "Starting fastboot protocol" at the top of the screen before you issue the commands?
and
2. Have you rechecked your drivers? To me this sounds like the issue if everything else is in place. Try plugging the phone into your computer while it's turned on and switching the "USB Connection" from "None" to "Windows Media" then to "Mass Storage" and finally "Phone Portal", making sure you allow it to install any proper drivers on each connection (takes a few seconds). It's also important to select OK each time you change the connection.
Also, did you get the correct adb files in the same folder as fastboot.exe?
Other than these 2 suggestions I don't know what could be causing the issue. At this point I would be seeking help myself.
jonnyboyC13 said:
Yep usb debugging is on
honestly i don't know why it's not working it just says waiting for device, all i need to do is just put into fastboot on my phone, navigate to the fastboot.exe on the command promt. Then plug in in the phone and issues the command correct. are there any other things that need to be running to get it working. is there another step before this for the computer to recognize my phone
Click to expand...
Click to collapse
ok did some more searching it is the driver just have to figure out what i need to get on my computer now
Ok haven't wiped yet but i got the right driver on my computer now adb now can discover my device and a did a fastboot reboot and it worked cool beans.
just in case anyone else is having a similar problem i had to download the MOTODEV usb driver here http://developer.motorola.com/docstools/USB_Drivers/ and yes had to sign up for MOTODEV to do it but whatever got it working and i'm pumped
Well, I have a problem, my EVO doesn't boot, I was first on meanrom and made a nandroid backup(system and boot), after that I wanted to install MIUI, so I flashed with flash GUI, all worked fine in the ROM, but after I wanted go back to meanrom I went to recovery, nandroid menu, cleared caches and restore partitions(I always do the same if the ROM I have don't like me), but for my surprise, phone doesn't boot, it shows the HTC white screen and after that just shows a black screen, the phone isn't turned off, it seems like a dimmed black screen. I tried to run adb to flash the boot.img but the pc doesn't recognize the device, I tried to restore only the boot partition in recovery and install meanrom again(ROM i had before) with no luck. I don't know what to do, any suggestions? Oh, I'm on hboot 1.5
You need to also wipe data when flashing a rom with a different base or boot.img. What I would do is boot recovery through adb and flash ROM/kernel from there.
Edit: also check out this thread for flashing boot.img on hboot 1.5
http://www.forums.infectedrom.com/showthread.php?p=10100
ssojyeti2 said:
You need to also wipe data when flashing a rom with a different base or boot.img. What I would do is boot recovery through adb and flash ROM/kernel from there.
Edit: also check out this thread for flashing boot.img on hboot 1.5
http://www.forums.infectedrom.com/showthread.php?p=10100
Click to expand...
Click to collapse
Yes, i wiped data and system too. And the first i tried was to flash ROM through adb but it says phone not found, is there a way to make the pc recognizes the phone?
luis4ever said:
Yes, i wiped data and system too. And the first i tried was to flash ROM through adb but it says phone not found, is there a way to make the pc recognizes the phone?
Click to expand...
Click to collapse
Yes install HTC sync for our phone and after it installs you need to uninstall it. This will install the drivers for our phone. You need to make sure usb debugging is enabled and plug your into your pc. It should work now.
Sent from my PG86100 using xda premium
ssojyeti2 said:
Yes install HTC sync for our phone and after it installs you need to uninstall it. This will install the drivers for our phone. You need to make sure usb debugging is enabled and plug your into your pc. It should work now.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Mmmmm, and how can i enable usb debugging if the phone doesn't boot to select that option?
luis4ever said:
Mmmmm, and how can i enable usb debugging if the phone doesn't boot to select that option?
Click to expand...
Click to collapse
Didn't think of that, but it should still work. Try getting into recovery by holding volume and power to turn phone on.
Sent from my PG86100 using xda premium
Well, i tried another pc and adb reboot bootloader works but when i write fastboot flash boot boot.img just says <waiting for device> and nothing happens. What should i do?
luis4ever said:
Mmmmm, and how can i enable usb debugging if the phone doesn't boot to select that option?
Click to expand...
Click to collapse
you dont try and do it from adb then... go to your bootloader screen by holding volume down and then the power button.....select fastboot and then hook your phone up to your data cable an use this command
fastboot flash boot boot.img
boot.img being the file that was saved in your backup flash that and that may fix your problem
wloftus said:
you dont try and do it from adb then... go to your bootloader screen by holding volume down and then the power button.....select fastboot and then hook your phone up to your data cable an use this command
fastboot flash boot boot.img
boot.img being the file that was saved in your backup flash that and that may fix your problem
Click to expand...
Click to collapse
In the message above i said adb worked in other pc but when i write fastboot flash boot boot.img just says waiting for device and nothing happens.
luis4ever said:
In the message above i said adb worked in other pc but when i write fastboot flash boot boot.img just says waiting for device and nothing happens.
Click to expand...
Click to collapse
fastboot and adb work at different times....adb is for when youre booted into the android
OSwith debugging turned on.... if you can run any adb commands then you can push any file you want.... but if no adb commands work you have to be in the bootloader area for fastboot to work....fast boot doesnt work when your at any htc boot screen it says its waiting for device bc its not set into fastboot usb modeagain.... turn the device off then hold the volume down buttonand press power.... friom there a screen will pop up and go through a file list and then come to a screen where the first option selected is "fastboot" press the power button from there and then hook up the data cable....you should see it say "fastboot usb" nowand from there you run
fastboot flash boot boot.img
fastboot commands only work in one spot in the set up just like adb commands only work when youre fully booted into the android os
wloftus said:
fastboot and adb work at different times....adb is for when youre booted into the android
OSwith debugging turned on.... if you can run any adb commands then you can push any file you want.... but if no adb commands work you have to be in the bootloader area for fastboot to work....fast boot doesnt work when your at any htc boot screen it says its waiting for device bc its not set into fastboot usb modeagain.... turn the device off then hold the volume down buttonand press power.... friom there a screen will pop up and go through a file list and then come to a screen where the first option selected is "fastboot" press the power button from there and then hook up the data cable....you should see it say "fastboot usb" nowand from there you run
fastboot flash boot boot.img
fastboot commands only work in one spot in the set up just like adb commands only work when youre fully booted into the android os
Click to expand...
Click to collapse
Yes i do that but cmd just says waiting for device
luis4ever said:
Yes i do that but cmd just says waiting for device
Click to expand...
Click to collapse
Are you able to boot into recovery holding volume down?
Sent from my PG86100 using xda premium
Idk if windows matters but i tried on a tablet with windows 8 with no luck, after I tried on a 64 bits windows 7 pc witness no luck but on a 32 bits windows 7 worked in the first try.
Your stuck in a bootloop and also you have lost you boot.IMG and you will have to exract from the zip folder of the Rom you have flashed and when that's done you will go to that folder and scroll down and you will see boot.IMG now copy and past it in the same folder that you have your adb and fastboot now open cmd and type fastboot flash boot boot.IMG and press enter and your EVO should reboot enjoy
Sent from my HTC EVO 3D X515m using xda premium
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I have HTC Desire X and I've been facing some problems lately. I rebooted my device into bootloader through command "adb reboot bootloader", then I checked my device as "fastboot device" and it was showing device connected, so later i tried fastboot flashing a "boot.img" file but it showed an error as"error: cannot open `desire` ". I have attached the screenshot..
My usb debugging mode was on and I use win8 os.
Plz help me.
AdilKhan694 said:
I have HTC Desire X and I've been facing some problems lately. I rebooted my device into bootloader through command "adb reboot bootloader", then I checked my device as "fastboot device" and it was showing device connected, so later i tried fastboot flashing a "boot.img" file but it showed an error as"error: cannot open `desire` ". I have attached the screenshot..
My usb debugging mode was on and I use win8 os.
Plz help me.
Click to expand...
Click to collapse
The command prompt reads a space as a second argument. Just enclose all your file names with quotation marks or start the command prompt session in the folder where the file is. Using Windows 8 may also cause problems afaik.
Yea my boot.img is in the same directory as platform tools, the one I'm working in. And I did not understood that space thing, I mean I directly copied the file path from explorer, so I don't think that can be wrong, can u plz explain it. Thanks a lott:thumbup:
Sent from my HTC Desire X using xda app-developers app
Ok so once again I tried flashing and this is what happened.
Is it possible that as I'm trying to flash the image file 1st and then flash the zip file from bootloader that I'm having this problem?? Jus for the info m trying to install CM 10.2, but flashing the rom.zip file from recovery mode leaves me with a black screen and it aint moving ahead. So after a bit of research, I tried doing it backwards, as in ROM MYOneDX+, but that aint helping too.
fastboot flash boot "c:\path to boot image\boot.img"
Or use Flashify from Google play.