Internation HOX+ bricked problem - HTC One X+

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!

Related

[SOLVED] help! phone won't boot into system or recovery!

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

Biggest regret trying to Root & Flash! (PLEASE HELP REVIVAL)

Sigh...
Sorry to rant here. hoping i can get answers, to common problems obviously but even though i researched & tried many stuff that i'm unfamiliar with, after 15hours trying, i decided to post.
Certain issues came up while flashing, some fixed(accidentally), but now my HTC one x+ (Asia), which was perfect, is stuck with a non-working ROM which does't get any Radio (no network/sim), also the SD card (internal) is not detected.
I JUST WISH TO GO BACK TO STOCK ROM NOW...
I know how to UNLOCK it using ALL IN ONE TOOLKIT.
I'm now dowloading (on a slow internet in Philippines) an (OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_0.23a.32.09.29_10.128.32.34a_release_299070u0mcx8aiaku8jgn4.zip),
hoping i will be able to go to Bootloader, fastboot & just click the RUU?
(honestly i dont even know if it will be an EXE, & the correct way)
I'm just hoping if i can re-lock the device, and run a RUU exe, i will have my phone again.
What i did to end up like this below (if anyone bothers to read)
first it was stuck at boot, then i flashed more stuff im aware of, trying to fix anything. i think i shall skip mentioning what i tried as i myself not sure what i did.
bottom line, now the htc one x+ turns on, charges, gets wifi (but no data network & no sd storage)
SD card (while detected, was wiped clean) - no ROMS there now.
I cannot go into RECOVERY BOOT, and pc sometimes recognises the ONE X+ device, but not as a storage card!!??
I have no backup in the Sd anyway..
someone please help me...
i think my post above doesnt make sense, as im so tired trying to fix it by researching.
if there is a simple STEP BY STEP guide to going back to stock ROM please help.
(i'm guessing what i can find for HTC one x can also be used for HTC one x+???)
i saved up many months for this phone.
i loved it so much, & it was perfect, but i wanted to try tweaking & trying the 4.2.1...
i regret it so much as im stuck..my brain is not working anymore after reading so much..
hi
to anyone who can give me a quick reply..
at this point, i have no ROM in my HTC One X+
I am trying my hardest to get back the stock ROM
so now im downloading the RUU exe.
RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.14.707.16_Radio_3.1204.167.31_release_290413_signed.exe
I really think thats the right one for my CID
NOW, after it completes download, (in about 3more hours!)
I intend to RE-LOCK my phone.
Go into FASTBOOT, connect to PC & simply RUN the RUU exe file..
MY QUESTION
Is this the right way? i tried with another RUU exe whih was for Cingular,USA, obviously it said WRONG RUU! but it was starting to TRY TO FLASH/INSTALL etc..so it seems like if i get the right RUU it will work??
(i found some links to use the COMMAND PROMPT but i tried & i still cannot get it fixed..)
please..i know this is all a common problem.. but i really just want my phone back.. at least to working condition..
im now thinking of bringing it to some repair shop, but i don't know anywhere here that can fix android or HTC.. i'm in Cebu, philippines by the way...
Sideload
You can try adb sideload option with TWRP recovery and a custom ROM. That should solve your problem. Finding correct RUU and installing them does not work easily most of the times.
To revert back to your original RUU, you need to
- relock your bootloader
- go to USB fastboot (connecting the the phone to your PC)
- run your Asian RUU from PC and follow instructions and wait
Thank you Steve0007 (I like your Avatar!)
Yes, i'm hoping it will be simple...
(Is it correct after i relock the device, the bootloader shows RE-LOCKED!?? , just curious as i don't know what it says before.. shouldn't it say.. LOCKED??).. oh well..
Sadly i'm using super slow internet to download whatever i can...
now i'm waiting for the Asian RUU (executable) to be downloaded, so i can try this method!
In the meantime..i'm gonna keep reading up about other methods.
thnks so much!
Steve0007 said:
To revert back to your original RUU, you need to
- relock your bootloader
- go to USB fastboot (connecting the the phone to your PC)
- run your Asian RUU from PC and follow instructions and wait
Click to expand...
Click to collapse
Abhishek.chaurasia said:
You can try adb sideload option with TWRP recovery and a custom ROM. That should solve your problem. Finding correct RUU and installing them does not work easily most of the times.
Click to expand...
Click to collapse
Hi Abhishek... thank you for all the Messages in inbox... relieved to get some help..at least..this phone is my baby..
I see, ... while waiting for the RUU to be downloaded, i think i shall try to find out how to do TWRP recovery!
I have One_X+_All-In-One_Kit_v2.3 (by Hasoon2000)
somehow it doesnt show TWRP...
it shows CWM (ATT),
and CWM International
and Your Own Recovery
i'm sorry i ask so many newbie questions.. but its really helpful for people who are in panic..
(on a sidenote, .. my wife thinks im crazy trying to (HACK-her words.. JAILBREAK-her understanding.. -SPOILING-her verdict) a perfectly fine phone!..)
I've been flashing ROMS and customising stuff on WINDOWS MOBILE since 2005/6 since the O2 Mini days.. but now i decided to 'ply' around with my device and find out i know NUTS!
I feel for you mate I did same after a week of trial and error I managed to adb sideload a Rom hope u get it fixed
Sent from my HTC One X+ using xda app-developers app
Abhishek.chaurasia said:
You can try adb sideload option with TWRP recovery and a custom ROM. That should solve your problem. Finding correct RUU and installing them does not work easily most of the times.
Click to expand...
Click to collapse
Oh..by Custom ROM, you mean one of those suitable ROMS found here right?
Which means i should ensure its UNLOCKED..
i now have in my hard drive...these ROMs downloaded..will these do??
OTA_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9-1.26.401.2_release_257085oc51j7moynlstgb9
Slim-4.2.1.stable.1.0-enrc2b-20130216-1511-UNOFFICIAL
flashing regrets... maybe just temporary
andy1969 said:
I feel for you mate I did same after a week of trial and error I managed to adb sideload a Rom hope u get it fixed
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Yes Andy1969, thanks.
I've been trying for about 17hours total now... (i realise i must be not as 'techie' as i thought!)
i have refrained from flashing ever since i got HTC touch, Touch Dual, Diamond, HD, Sensation, One X and now finally got my dream phone One X+.. which is almost perfect.. But i had an itch to start fiddling with it after owning it for just about 2 months...
even though i regret it, at this moment.. i feel that somehow after i learn more..my addiction to flashing may come back just like in those Windows Mobile days!
TWRP2
DELETED
TWRP
First try the RUU you have downloaded. If not, then unlock again and install TWRP from this link http://teamw.in/project/twrp2/130 and try sideloading Slim Rom you have downloaded.
Abhishek.chaurasia said:
First try the RUU you have downloaded. If not, then unlock again and install TWRP from this link http://teamw.in/project/twrp2/130 and try sideloading Slim Rom you have downloaded.
Click to expand...
Click to collapse
I managed to install TWRP!
now when i choose RECOVERY it goes straight to the TWRP...
i dont really know why the SLIM ROM sideloading did not work... as in SD card (as stated in TWRP) shows only the TWRP folder...
but at least im seeing progress...
i will keep trying sideloading some ROMS... maybe need to change name of file etc??
anyway..when i got into TWRP..1st thing i did was back up... at least for now..its better than being totally bricked...
i am back into the non-fully-working AOKP Jelly Bean 4.2.1 Custom ROM which doesnt recognise my sim or my sd card...
I DID IT! (i think..i hope)
WELL...
by some fluke.i managed to use TWRP to sideload the SlimBean ROM.. wow... 1st it was all error..so since its in the SD partition, i used TWRP recovery to reflash...still many buggy errors... network was found but no calls can be made.. now i did a factory reset from the phone settings itself.. (not the TWRP) and wala... all seems to be fine..
wifi, text, calls all ok..
yet to test others.. its 12.45am now!
so i spent 2 full days for my silly trial... but its ok.. i learnt stuff anyway..
BUT the SD card problem still exists... no detected..will work on it tomorrow or try new roms etc..
but the SlimBean interface & 4.2.1 is really cool & different..
im pretty sure there will be some errors tomorrow.. (just have a feeling)..if not.. then it will be best..
for now.. HOME button doesnt get me back to HOME! (will try settings etc)..now checking out other settings before i get some rest!
cheers.. will update again tomorrow..
Good progress. Now you know how to bring your phone back to life
c2nitz said:
WELL...
by some fluke.i managed to use TWRP to sideload the SlimBean ROM.. wow... 1st it was all error..so since its in the SD partition, i used TWRP recovery to reflash...still many buggy errors... network was found but no calls can be made.. now i did a factory reset from the phone settings itself.. (not the TWRP) and wala... all seems to be fine..
wifi, text, calls all ok..
yet to test others.. its 12.45am now!
so i spent 2 full days for my silly trial... but its ok.. i learnt stuff anyway..
BUT the SD card problem still exists... no detected..will work on it tomorrow or try new roms etc..
but the SlimBean interface & 4.2.1 is really cool & different..
im pretty sure there will be some errors tomorrow.. (just have a feeling)..if not.. then it will be best..
for now.. HOME button doesnt get me back to HOME! (will try settings etc)..now checking out other settings before i get some rest!
cheers.. will update again tomorrow..
Click to expand...
Click to collapse
You keep saying "SD Card" problem. What do you mean by that? You do understand our phone has no SD Card or SD Card partition. What you think of as the SD Card is nothing but a folder called "media" on the /data/ partition. That means we can't do things like mount our device as mass storage on PC's or mount SD Card in recovery.
Sent from my HTC One X+ using Tapatalk 2
Nvm
Sd storage
AndroHero said:
You keep saying "SD Card" problem. What do you mean by that? You do understand our phone has no SD Card or SD Card partition. What you think of as the SD Card is nothing but a folder called "media" on the /data/ partition. That means we can't do things like mount our device as mass storage on PC's or mount SD Card in recovery.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Yes i understand it doesn't have a 'physical' SD Card, but in Stock Rom, in File Explorer, it is recognised as SD Card.
Also, when plugged into PC, it is recognised as External Storage... from PC, it was possible to access the Internal Storage, and within that, the SD Card, which inluded DCIM, and whatever folders it had..
BUT now all tht 'SD' portion is gone.. Gallery cannot be viewed as there is no 'SD Card' (system prompt)
Camera doesn't work too as there is no 'SD Card' (system prompts again)
Help pls! Rom is gone! Usb unrecognized!
NOW its worse!! pls help!
I woke up this morning, turned the HOX+ on...
I found that most functions not working! (example-FILE MANAGER/CAMERA/BROWSER HAS STOPPED WORKING PROMPT,etc)
I knew that i will try re-flash today, so i went into TWRP recovery again & re-flashed the same SLIMbean rom.
still didnt work, so i wiped data etc...
I didnt realise I ALSO WIPED AWAY EVERYTHING!
SO NOW THERE IS NO ROM AGAIN..
if i boot it's STUCK AT HTC QUIETLY BRILLIANT screen, and worst, if i go into FASTBOOT, when i plug the usb into my Windows 8 PC, it DOESN'T say FASTBOOT USB anymore!!
so the pc doesnt recognise the device and i cannot use the all-in-one toolkit!
HOPELESS
c2nitz said:
when i plug the usb into my Windows 8 PC, it DOESN'T say FASTBOOT USB anymore!!
so the pc doesnt recognise the device and i cannot use the all-in-one toolkit!
Click to expand...
Click to collapse
I HAVE NO IDEA WHAT TO DO NOW...
USB CANNOT DETECT HOX+ NOW..
COMMAND PROMPT CANNOT FIND DEVICE..
TOOLKIT CANNOT FIND..
I have a new custom ROM downloaded finally (viper), but unable to sideload now..
The custom RUU failed to download halfway Twice, even if it succeeded, it won't detect device.
been doing more research... PdaNetA4013 downloaded but not able to install on this Windows 8..
i'm trying to re-download the AndroidSDK, just in case..
some kind expert pls help!
to me, this is all hell breaking loose.. its been almost 3 days now... big REGRET!
c2nitz said:
I HAVE NO IDEA WHAT TO DO NOW...
USB CANNOT DETECT HOX+ NOW..
COMMAND PROMPT CANNOT FIND DEVICE..
TOOLKIT CANNOT FIND..
I have a new custom ROM downloaded finally (viper), but unable to sideload now..
The custom RUU failed to download halfway Twice, even if it succeeded, it won't detect device.
been doing more research... PdaNetA4013 downloaded but not able to install on this Windows 8..
i'm trying to re-download the AndroidSDK, just in case..
some kind expert pls help!
to me, this is all hell breaking loose.. its been almost 3 days now... big REGRET!
Click to expand...
Click to collapse
well maybe go back try the basic things maybe ur pc isnt up to it recheck drivers mine was wiped all out and got it back

[Q] Formatted, I think I broke it

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

ADB freezes my computer, can't flash ROM

So I made the terrible mistake of wiping my data / system partitions and internal SD without putting a ROM on the phone. I was trying to revert the phone to a stock build via the RUU utility (I need to flash the phone to another carrier and I can't do that without the stock phone app) but it failed so now I'm just stuck with a phone with nothing to boot into. I tried to run the RUU again but it freezes my whole computer after clicking "Upgrade" (there's some serious disk activity going on but nothing happens, unlike the first time when it proceeded after that.
I can't mount the internal SD on my computer as Windows 7 won't recognize it (a new disk shows up but I can't go into it). I've tried to use ADB sideload in TWRP but my computer hangs when I issue the command and I have to hard reset it. Trying to flash the zip via fastboot also requires a hard reset.
I am moonshine S-Offed and I'm using the latest TWRP recovery. I am pretty sure I have all the drivers installed (HTC Sync is installed and I also updated them with the drivers from PDaNet). Help?! I just want to get it back up and running, I'm just going to flash a non-RUU stock rooted ROM.
J D A said:
I am moonshine S-Offed and I'm using the latest TWRP recovery. I am pretty sure I have all the drivers installed (HTC Sync is installed and I also updated them with the drivers from PDaNet). Help?! I just want to get it back up and running, I'm just going to flash a non-RUU stock rooted ROM.
Click to expand...
Click to collapse
If you have a recovery you can just use a USB OTG cable, a thumbdrive with your rom images on it and install a rom from external SD.
twelfth said:
If you have a recovery you can just use a USB OTG cable, a thumbdrive with your rom images on it and install a rom from external SD.
Click to expand...
Click to collapse
I don't have one. Is there any other way?
J D A said:
I don't have one. Is there any other way?
Click to expand...
Click to collapse
Not really. USB OTG cables are $3 on eBay. Buy one.
Thanks for your help! I actually got it working jut now after a full day and night of frustration haha. I used this thread: http://forum.xda-developers.com/showthread.php?t=2060858. I thought I couldn't issue adb push but I was wrong! Everything works now!
J D A said:
Thanks for your help! I actually got it working jut now after a full day and night of frustration haha. I used this thread: http://forum.xda-developers.com/showthread.php?t=2060858. I thought I couldn't issue adb push but I was wrong! Everything works now!
Click to expand...
Click to collapse
You got lucky. The way it sounded in your original post was that even ADB was broken. By that point, if you have a working recovery, the only thing you CAN do is flash an image... and without an SDCard to pull out of the phone, you can only do it through USB OTG on the DNA.
So I'd still pick up a USB OTG cable in case you need it in the future.
twelfth said:
You got lucky. The way it sounded in your original post was that even ADB was broken. By that point, if you have a working recovery, the only thing you CAN do is flash an image... and without an SDCard to pull out of the phone, you can only do it through USB OTG on the DNA.
So I'd still pick up a USB OTG cable in case you need it in the future.
Click to expand...
Click to collapse
I know. Way too lucky. ADB has always been a pain for me, even with my Rezound. I will definitely be buying an OTG cable or that OTG-like sd card plugin asap!
boot into recovery and push the file to the /sdcard
no need to mount anything just make sure it says adb device: **device_id##**
when you have twrp booted and plug it in to your pc it will act as if the system is already mounted if you type adb shell it will bring up the shell of the phones storage then exit and just adb push rom.zip /sdcard/rom.zip and its there...
You can use this tool kit to help you out. I have used it and its very simple. The creator did a wonderful job with it. Best of luck to you!
http://forum.xda-developers.com/showthread.php?t=2219175&highlight=toolkit

[Q] Buggerit!

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.

Categories

Resources