So I should not be doing this on so little sleep, obviously. I have a Verizon HTC Droid DNA, Moonshine S-off, TWRP, and I had CarbonROM on it, but I was having issues so after some fumbling around and trying different things, I was at a loss. So I wiped all data and formatted. Well, before this, for some damn reason, I think I turned USB Debug off. Now I can't get into Fastboot USB. Am I totally screwed? My PC won't communicate with the phone.
HELP!
Actually its difficult to be "totally screwed" you can always hold the power + volume down until the phone boots into HBoot. Once your in HBoot again fastboot should work if it doesn't then that generally a driver issue. Once your back in HBoot you can select fastboot and that will give you the option to boot back into recovery. Once you get into recovery again I would select sideload and flash the ROM using "adb sideload <rom name>" making sure your in the adb directory and so is the ROM. Hope this helps.
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Kevin5377 said:
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Click to expand...
Click to collapse
PC driver issue, go into device manager and load new driver
I'll take a look
Sent from my Nexus 7 - Carbon Rom
Yeah, I'm not even getting the Windows sound like I connected anything. Usually it'll tell you no drivers or unsuccessful installation or something!
Holy crap... well you were right... it was a driver issue. I reinstalled the HTC drivers and I got FASTBOOT USB now... thank goodness!
I feel like my brain isn't working. How do I now get my .zip on my device using fastboot so I can then get into recovery and flash it?
Nevermind... booted to recovery, used adb to push my .zip to device
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
trickster2369 said:
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
Click to expand...
Click to collapse
Even more fun when they answer themselves
hawkstwelve said:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
Click to expand...
Click to collapse
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Enjoy
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Thanks that worked! Back to loving viper.
I Have a similar problem
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Hey i'm new to this and i also formated my phone when installing a new rom i can still get into twrp and when i plug in the phone to the computer fastboot usb shows up and it makes the sound on the computer however when i type adb devices in the cmd its blank could someone please walk me through the adb stuff sorry for being a noob
I also have a OTG cable but i tried to plug in a 16GB FAT32 flash drive but twrp didnt recognize it. it says unable to mount
Thanks a bunch
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Kevin5377 said:
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Click to expand...
Click to collapse
Thanks a bunch but i plugged in a bunch of flash drives until one was recognized and then was able to restore my old ROM... WHEW
Related
SOLVED, see post #6
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
=JKT= said:
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
Click to expand...
Click to collapse
okay, I just found out that I can access adb in the state that recovery is in.
Is it possible to reflash either the rom or the recovery from a shell in here? or would that be "bootstrapping" since I'm already in recovery?
perhaps I can adb push a backup to /system?
of course the ./adb reboot bootloader doesn't work
I'm using a mac and I've had trouble getting fastboot to recognize my device in the past...I think last time I just borrowed someone's pc to do it.
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Can't test it right now, but I think the process would go something like this (recovery means on the phone, computer means on the computer):
Code:
[I]recovery>[/I] mount /sdcard
[I]computer>[/I] adb push recovery.img /sdcard/
[I]recovery>[/I] flash_image recovery /sdcard/recovery.img
[I]recovery>[/I] umount /sdcard
[I]recovery>[/I] reboot recovery
Note once again that this is untested, it's straight from my head, so it might need adjustments.
ravilov said:
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Click to expand...
Click to collapse
thanks for the idea. I can't access any of the functions of the recovery. it's just a splash screen. ADB recognizes the device on my computer though. I can adb push files...I'm wondering if I can push something from a backup to my phone through adb. I guess I'd need to push the /system and /boot to it. I can't seem to get mmcblk0p12 to mount though...
edit: I didn't see the code you added.
I tried it and got this message:
error scanning partitionsfailed with error: -1
I can't seem to get any partitions to mount (ie mmcblk0p12 etc)
I'm nervous about totally borking recovery since it's my only access to the phone right now. I might have to borrow a pc to get fastboot to work.
=JKT= said:
I might have to borrow a pc to get fastboot to work.
Click to expand...
Click to collapse
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
[SOLVED]
ravilov said:
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
Click to expand...
Click to collapse
SOLVED!!
First I found out that if I type fastboot -i 0x22b8 before every command, they worked fine.
then I stumbled across moto-fastboot, which is apparently a special fastboot for moto devices.
I used that to flash a new recovery the standard way and it worked out just fine.
Thanks so much for your help, ravilov!!
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
ravilov said:
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
Click to expand...
Click to collapse
I've only had the Atrix for about a week. Still learning the ropes: coming from an HTC device, so I'm used to doing things a certain way and relearning some basics lol
Cheers!
Sent from my MB860 using xda app-developers app
Hello everyone,
I have been searching in vain for a while now to find a solution to my problem and I fear that I may have done something daft to my phone.
I am using a HTC One X+ that was unlocked, s-off and rooted for about a year, i had TWRP and stock android 4.1.1. For ages I have been getting an update alert saying a software update is ready and i think it was some Vodafone update (1.17.161.7). Whenever i accepted and tried to install this it would obviously reboot into TWRP and then the update would fail. This was fine until last night when I decided to install it through TWRP, it said it failed again and i rebooted to find that WiFi wouldnt turn on, my phone was no longer rooted or s-off and that I get no signal. I tried to re-root it but command prompt on the computer or HTC Sync wouldnt recognise my device however it was appearing as HTC One X+ in My Computer and i could access the internal storage.
I restarted into recovery and managed to flash a new root using twrp and the root file using the unlockr.com - how to root the htc one x
Then thinking it was a ROM issue i downloaded and installed InsertCoin Evolution ONE X+ 5.0-6 Sense 5 Android 4.2.2.
This all went through ok however when i reboot from this install it just sticks at the HTC Quietly Brilliant screen. I wiped everything using twrp beforehand.
When i restart into bootloader, it says unlocked, S-On and HBOOT -1.30.0000
Not sure what else to do as now i have no ROM, i read that you have to partition the SD card for InsertCoin to work but the option to partition SD card isnt there in my TWRP (ver. 2.3.3.0)
Any help to even reset my phone back to basic stock everything would be amazing, i have a Titanium Backup of most of my stuff saved btw.
Thanks to anyone who can help.
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
AndroHero said:
Did you flash the insert coin boot.img?
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
EDIT - Now seen the instruction to flash the boot.img - what a fool i am. Now i need to get it recognised by USB again so i can transfer the zip file to it and go again.
maxwell689 said:
No I just copied the whole zip file to the SD card section and installed it from there - ive encountered a new problem now in the fact that my computer no longer can recognise the phone via USB - it still appears in device manager but cant access the sd card and the sd card got wiped by twrp so now i dont have any way of getting things onto the phone that i know of. It just says - failed to open usb master mode in the bootloader. How could i get the computer to recognise the phone again so i can transfer it back onto it and try installing insertcoin again? Really hoping i havent managed to make my phone useless as ive had to dig out the old Nokia 6230 from the drawer haha!
Thanks.
Click to expand...
Click to collapse
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Without a rom installed you're not able to acces the internal memory of your phone directly. You have to use "adb sideload" command to transfer a rom onto your phone. Look in the General and/or Q&A forum of this device, there are enough guides or topics on how to solve this "problem".
maxwell689 said:
Now seen the instruction to flash the boot.img - what a fool i am. All I need now is to get it recognised by USB again so i can transfer the zip file back and go again.
Click to expand...
Click to collapse
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Optimus said:
Hi use this link..may be useful (http://forum.xda-developers.com/showthread.php?t=2066390) by the way reaper90 is right you need to sideload the rom..
In TWRP:
1-wipe everything
2-goto advance in twrp
3-select sideload
4-navigate to the folder where you have adb.exe, adbwinapi.dll, adbwinusbapi.dll and fastboot.exe. and make sure to keep the rom and its image; bootimg there.
5-then in command prompt write (adb sideload *name of the rom*.zip) make sure the name is a letter.
6- also make sure to keep the screen alive and not let it goto sleep while adb sideload is working.
7- rom will start setup once sideload is 100%.
Hope this helps. Goodluck.
Click to expand...
Click to collapse
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
maxwell689 said:
Hi, thanks very much for the responses - its much appreciated.
Nothing happens when i type that command, a load of text appears in cmd prompt showing all the adb commands and thats it, i have searched for this problem and found this on twrp website as a possible solution "You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line" My version says 1.0.26 I have tried to update this but cant seem to find a way to do it, would that be an issue?
I think once ive managed to sideload the zip i should be good to go its just getting to that point that seems to be stumping me at the moment.
Click to expand...
Click to collapse
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Ghand0ur said:
Dont sweat it. They understood you wrong.
Guys what he wants to do is copy the file FROM the SDCARD TO the PC.
First you will need to know where the location of your rom then type in the following commands:
Code:
adb devices
If you device is not detected then try to run the CMD as an administrator and try again
then:
Code:
adb pull {location without the curly brackets}
For example if its on the SDCard then:
Code:
adb pull /sdcard/rom.zip
It will paste the file to the folder where the adb is found
Then just open the zip file and get out the boot.img and flash it using fastboot
Hope this helps you out.
Click to expand...
Click to collapse
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
maxwell689 said:
Hey, thanks.
No they got me correctly, there is absolutely nothing on my phone at all and I need to get my new ROM zip file from the PC to the phone so that I can install it. I am currently downloading SDK manager to try and update my adb to 1.0.29 or higher and will see if that works.
Click to expand...
Click to collapse
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Lol.. Well, as i said try to run the Toolkit/cmd as administrator and try different usb ports.. It took me 5 minutes on windows 8 for the adb to properly read the device , had to try different usb ports, unplug , replug, and so on..
maxwell689 said:
Ok, i downloaded the hasoon toolkit and select ADB Sideload a ROM and it says "error device not found" in the command prompt. I am in ADB Sideload mode in TWRP with it plugged in via USB so dont know what to try next.
Click to expand...
Click to collapse
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Optimus said:
Hi goto htcdev n download the latest sdk
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 09:08 PM ---------- Previous post was at 09:07 PM ----------
I will try to send I over the files for command prompt tomorrow.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
maxwell689 said:
Right ive manged to download the latest sdk and then after much unplugging and plugging and right clicking things in device manager its recognised my phone enough to sideload and install the ROM. I have also managed to fastboot the boot.img file as well after 3 attempts but it finally worked so i have a phone back again!! Thanks everyone here!!! Now to upload my titanium backup of apps, sadly i think ive lost all my photos thou
But thanks again to all. Sorry if ive been a bit noob but its been a good learning curve for me as i never had these issues with my HTC desire
Click to expand...
Click to collapse
Thats great news that all is well now..feel free to post.. and dont forget to press the Thanks button
So I clearly screwed something up. Was running Viper 2.0.3 but went to reset/wipe and think i accidnetly formatted the sdcard then system also in CWM. Now i can't get anything to boot. I can get into CWM but am struggling to figure out how to flash something so a ROM will load. I'm clearly a newby with this. Pretty sure I have adb setup right,as it apprears to recognize the device with adb devices, but this was my first foray into adb so i'm struggling with this. Any help from the community would be more than appreciated, as I'm trying to set this up for my mother's first smart phone.
davescarp said:
So I clearly screwed something up. Was running Viper 2.0.3 but went to reset/wipe and think i accidnetly formatted the sdcard then system also in CWM. Now i can't get anything to boot. I can get into CWM but am struggling to figure out how to flash something so a ROM will load. I'm clearly a newby with this. Pretty sure I have adb setup right,as it apprears to recognize the device with adb devices, but this was my first foray into adb so i'm struggling with this. Any help from the community would be more than appreciated, as I'm trying to set this up for my mother's first smart phone.
Click to expand...
Click to collapse
In CWM select sideload, use the sideload command from the command prompt on your PC to get a rom on the DNA
RLGL said:
In CWM select sideload, use the sideload command from the command prompt on your PC to get a rom on the DNA
Click to expand...
Click to collapse
ok, i was messing with that... so "adb sideload ViperDNA_2.0.3.zip" where the viper zip is in the adb folder? just tried that and is says it * can not read ViperDNA_2.0.3.zip * ?? Appreciate the resonse, i think this is easily solveable since i can boot to recovery and still have CWM.. just need a nudge to get over the top...
EDIT: figured it out... thanks to xda and all for providing a resource so useful.
Adb push Rom.zip /sdcard/Rom.zip
Sent from my dlx using XDA Premium 4 mobile app
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Sorry, also, I have checked through xda and I cant seem to find anything that would explain why I am stuck!
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Fastboot
Lloir said:
flash the boot.img
from a welsh person who can't understand why people cannot flash rom's correctly
Click to expand...
Click to collapse
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
ryutnm said:
I used "fastboot flash boot boot.img" in my cmd, like i always have done, and this time it doesn't want to work...at all
Click to expand...
Click to collapse
you tried fulling wiping? then just flashing the rom + bootimage after
thanks
Lloir said:
you tried fulling wiping? then just flashing the rom + bootimage after
Click to expand...
Click to collapse
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
ryutnm said:
No, does that require different fastboot commands?
i have cwm touch recovery installed. Would that make a difference?
Also, could I just say thank you in advance for your help sir!
Click to expand...
Click to collapse
Unless you mean the user data and cache wipe.
Then yeah i did that
ryutnm said:
Unless you mean the user data and cache wipe.
Then yeah i did that
Click to expand...
Click to collapse
Data/system/cache
Sent from my Nexus 5 using Tapatalk
ryutnm said:
Good evening Ladies & Gents.
Firstly can I say, this site has been my bible, and I am so very very grateful for all the work that everyone has put in to making this site what it is.
Now down to business.
I have an HOX+ and have been flashing for about a year now but still consider myself to be a complete nub! first with hox then i broke it and now hox+. Im in a bit of a predicament.
I flashed a version of aosp 4.4 onto the phone, installed from the zip file, cleared the cache, user data and dalvik.
rebooted, and got stuck in a boot loop.
So i went to my backup and restored from there...
boot loop again.
So i went back into bootloader, then fastboot, and reflashed the viper+ 2.0.1 that I had on before.
But when I got stuck on sending boot
Now im stuck in a boot loop, none of my backups will restore properly.
I fear I am hardbricked as I cant get anything to work...
Any help before I have to be back at work tomorrow would be very helpful! and even more appreciated!
Yours
A very frustrated and stressed British nub
Click to expand...
Click to collapse
Well the bootlooping has something to do with not flashing the boot.img stated by yourself and lloir. About that bug of "Sending boot.img", it happens to me but I fix it by running CMD as administrator , If that doesnt work, try using a different usb port. Preferably one directly to pc/laptop rather than using a hub. Try a 3.0usb port first, if that doesnt work then 2.0usb port.
P.S Without S-Off you can't become hardbricked. Till now I didn't see a single person who bricked their HOX+ unless he received an S-Off developer phone..
Lloir said:
Data/system/cache
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
ryutnm said:
Im now only getting "waiting for device"
which I can only assume means my pc now doesnt even recognise the phone when its booted in bootloader/fastboot usb mode?
Click to expand...
Click to collapse
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Lloir said:
stop....Hammer time...
have you got a rom on the sdcard (in cwm) if yes
wipe data/system/cache
then
reboot into bootloader
fastboot flash boot boot.img
if not ----------
full wipe (as above)
adb sideload romname.zip
then reboot into bootloader as above
Click to expand...
Click to collapse
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Edt - just tried the sideload using the cmd, and i had error: device not found
so windows isnt recognising my phone...it was working this morning
ryutnm said:
I have the zip on the internal storage as i dont have "sd/ext" or what ever the extention is. When I bought the phone I never had the sd card. Never was able to save anything onto an sd card.
so should i try installing from the zip? even though the fastboot commands arent working?
or would a sideload skip the fastboot commands?
or am i just being completely retarded
Click to expand...
Click to collapse
Why am i being ignored you guys lol. Did you try my solution ?
Terribly Sorry
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
dude, im so sorry - i didnt even see the post!
i will try now!
sorry again
edt - still no joy as for some reason my phone is no longer being recognised by my pc =[
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
*edit the above is assuming you are in recovery
IF NOT in recovery, but fastboot_usb mode
then fastboot devices (but you cannot do jack apart from flash boot image)
IF in recovery, you got a few choices
wait 5-10minutes (don't ask, it's a common issue with the X+ and CWM\TWRP)
put the device in adb sideload for a minute or so (^ see above reason)
i have adb issues in CWM\TWRP myself, especially when i have no rom and so on, so i know your frustration, patience young padwan
looking good so far
Ghand0ur said:
Why am i being ignored you guys lol. Did you try my solution ?
Click to expand...
Click to collapse
Lloir said:
HTC sync uninstalled ?
you have killed adb (if on windows just kick open taskman and kill adb)
or in cmd\terminal adb kill-server
then do adb devices
reboot pc?
try a different usb cable (maybe the one from your charger if you are not using that one)
Click to expand...
Click to collapse
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
ryutnm said:
So I tried starting cmd in administrator mode [never had to before]
- Didnt work
- Plugged into a different usb slot as lloir suggested, didnt get the "windows does not recognise this device" this time
restarted cmd as admin like Ghandour suggested.
Just managed to install the viperx+ 2.0.1 rom and i am now setting it up!
THANK YOU SO FREAKING MUCH GUYS [and gals if either of you are female]!
do you know why I had to start using cmd as an administrator?
Click to expand...
Click to collapse
might be because of where you have the adb tools. and i'am 100% male
thanks
Lloir said:
might be because of where you have the adb tools. and i'am 100% male
Click to expand...
Click to collapse
well dude, thank you for your help!
I dont understand why though, ive been using this pc the whole time to flash recovery images and boot images and never had to use admin
Thank you
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
ryutnm said:
Also a thank you to Ghand0ur for your help as well!
So very much appreciated
Click to expand...
Click to collapse
Glad you got it working. Just always try those common solutions:
-Restart PC
-Run as admin
-unplug replug
-reboot phone
-try different usb port
-try different usb cable.
My international HTC One X+ is now bricked. I've flashed different roms on it without any problems, so this time I was headstrong and flashed a new rom with no back ups available at all...
I flashed it and accidentally erased everything... so now I don't have any OS installed on the phone. The HBOOT is 1.72.0000 so all of the RUUs that I've tried don't work because apparently it they only work on if the HBOOT is 1.35 or less...
Computer doesn't show me the phone's internal storage when I plug it in so I can't put any OS on the internal storage to flash it (it does go into recovery, I have TWRP recovery).
ADB Sideload doesn't seem to work... ADB doesn't see my device (though fastboot does see it... I can flash boot and recovery as many times as I want) but I can't manage to flash a rom to my phone... fastboot says "FAILED: (remote: not allowed)"
I've tried the commands " fastboot flash rom rom.zip" and "fastboot flash zip rom.zip" and they both fail after taking about 2 minutes.
And this phone doesn't have SD Card... I've tried using an adapter cable to connect my external memory disk (for my PC) to my phone but the phone simply doesn't read it...
I would like to try to downgrade my HBOOT firmware to 1.35 so I could get the RUU to work... or if there is a better solution I would be glad to try.
Please, help me here... thank you
you know TWRP has MTP support now....Sooo you can just drag the file from pc to the internal directory of the phone....
Yeah, I've noticed that, but for some reason my computer doesn't see the phone... it did once but then it stopped for some reason.
elitezenithweb said:
Yeah, I've noticed that, but for some reason my computer doesn't see the phone... it did once but then it stopped for some reason.
Click to expand...
Click to collapse
Adb also works in TWRP, it's just super slow. Rule of thumb. Once you see the battery % with a + at the end, adb will work as should sideload. Yes It's a pain in the ass, I know. I have to do this really often while building CM.
Lloir said:
Adb also works in TWRP, it's just super slow. Rule of thumb. Once you see the battery % with a + at the end, adb will work as should sideload. Yes It's a pain in the ass, I know. I have to do this really often while building CM.
Click to expand...
Click to collapse
Wow! Thanks for developing :good:
Well, I got my problem fixed... my drivers on my PC were out of date or something... they weren't working properly. I got them updated and MTP started working! Now I got my phone flashed. Thank you!