Related
Hi everybody!
(Sorry for my english )
I up rom cook for HOX+ but failed. It can't boot to room cook. I can boot to recovery, fastboot. All things in sdcard are lost.(backup rom ship). How can I restore my phone? Please.
When I run rom guu RUU_ENRC2B_U_JB_45_Vodafone_UK_1.14.161.13.....exe it failed because my phone is x.17.161.x.
My phone: HBoot: 1.40, version x.17.161.x.
Thanks all!
macarong35 said:
Hi everybody!
(Sorry for my english )
I up rom cook for HOX+ but failed. It can't boot to room cook. I can boot to recovery, fastboot. All things in sdcard are lost.(backup rom ship). How can I restore my phone? Please.
When I run rom guu RUU_ENRC2B_U_JB_45_Vodafone_UK_1.14.161.13.....exe it failed because my phone is x.17.161.x.
My phone: HBoot: 1.40, version x.17.161.x.
Thanks all!
Click to expand...
Click to collapse
Did you install TWRP or are you on stock recovery?
When you enter bootloader, does it show unlocked or locked at top of the screen?
Addicted2xda said:
Did you install TWRP or are you on stock recovery?
When you enter bootloader, does it show unlocked or locked at top of the screen?
Click to expand...
Click to collapse
I installed CWM-base Recovery v6.0.2.7 and bootloader unlocked.
macarong35 said:
I installed CWM-base Recovery v6.0.2.7 and bootloader unlocked.
Click to expand...
Click to collapse
Install TWRP 2.5 and get a ROM sideloaded ...
( adb sideload blahblahblah.zip )
Of course you need to flash the kernel too
AFAIK CWM does not support ADB Sideload and is practically dead.. or at least in hibernation...
Addicted2xda said:
Install TWRP 2.5 and get a ROM sideloaded ...
( adb sideload blahblahblah.zip )
Of course you need to flash the kernel too
AFAIK CWM does not support ADB Sideload and is practically dead.. or at least in hibernation...
Click to expand...
Click to collapse
Could you please detail step by step to sideload zip file. I installed TWRP2.5. I goto recovery and select ABD sideload, them run command on PC but error:
D:\IDE\AndroidSDK\sdk\platform-tools>adb sideload d:\Elegancia_6.1.0.zip
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
D:\IDE\AndroidSDK\sdk\platform-tools>
macarong35 said:
Could you please detail step by step to sideload zip file. I installed TWRP2.5. I goto recovery and select ABD sideload, them run command on PC but error:
D:\IDE\AndroidSDK\sdk\platform-tools>adb sideload d:\Elegancia_6.1.0.zip
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
D:\IDE\AndroidSDK\sdk\platform-tools>
Click to expand...
Click to collapse
Try this command a few times...
Copy the rom to same folder as adb tools
rename the ROM file to .. say ROM.zip
The ADB sideload needs some time to detect...
yrgeryi Bosher
Addicted2xda said:
Try this command a few times...
Copy the rom to same folder as adb tools
rename the ROM file to .. say ROM.zip
The ADB sideload needs some time to detect...
Click to expand...
Click to collapse
Hi, I send file successfull. But after my phone don't display anything. Black screen. What must I do next?
Update: uprom success. Thank so much.
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
NinjaKenZen said:
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
Click to expand...
Click to collapse
If you can push files on sd card, use the TWRP back-up from here to restore to stock.
http://forum.xda-developers.com/showthread.php?t=2414238
You'll at least get it working again.
Thanks, somehow when I updated the bootloader, the boot.img restriction got lifted after I just entered the command again when 'unknown failure' came up. I was at this point able to access the sd card under a buggy rom start-up.I used TWRP to flash a new rom.
Fixed.
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
loaybilal said:
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
Click to expand...
Click to collapse
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
imcontreras said:
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
Click to expand...
Click to collapse
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
roshak said:
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
Click to expand...
Click to collapse
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
roshak said:
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
Click to expand...
Click to collapse
Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
Thank you!
Ohh.... Help please!!
I was flashing rom but I skipped a step and end does not pass the white HTC screen.
The fact is that it was installing the rom and Gapps but I miss the boot.img I have it on PC, the problem is that as the phone will not start, i can enter to bootloader but does not recognize the pc, I get the normal bootloader but how i do to pass the boot.img again if the phone does not recognize it??
And sorry for my bad english---- Help please!
rikrdoVe said:
Ohh.... Help please!!
I was flashing rom but I skipped a step and end does not pass the white HTC screen.
The fact is that it was installing the rom and Gapps but I miss the boot.img I have it on PC, the problem is that as the phone will not start, i can enter to bootloader but does not recognize the pc, I get the normal bootloader but how i do to pass the boot.img again if the phone does not recognize it??
And sorry for my bad english---- Help please!
Click to expand...
Click to collapse
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
ethanon said:
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
adb reboot bootloader
ethanon said:
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
rikrdoVe said:
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
Click to expand...
Click to collapse
rikrdoVe said:
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
Click to expand...
Click to collapse
Well you do need to have the Android SDK tools download but if you select the "Platform Tools" at the SDK manager , that will only install the platform tools on your hard disk. and yes the device drivers needs to installed , to work with ADB ,
Any ways this tutorial by LUCKY_THIRTEEN just might help you
http://forum.xda-developers.com/showthread.php?t=2213910
ethanon said:
Well you do need to have the Android SDK tools download but if you select the "Platform Tools" at the SDK manager , that will only install the platform tools on your hard disk. and yes the device drivers needs to installed , to work with ADB ,
Any ways this tutorial by LUCKY_THIRTEEN just might help you
http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
I cant install sdk and use adb... I resume: Dowloaded sdk from the page, and when i start sdk manager "Platform Tools" cant update i got this error: Stopping adb server succeeded. Failed to rename directory C:\adt.bundle.windows-x86-20131030\sdk\platform-tools to C:\adt.bundle.windows-x86-20131030\sdk\temp\PlatformToolPackage.old01. Nothing was installed"
I dont know if sdk was installed or what. only have the folder in C:
I put the boot.img file in platform-tools and tried to flash the image using the command fastboot flash boot boot.img but tells me the boot.img arrchivo not be found.
The phone does not recognize the pc, the bootloader is relocked.
Thanks for your support bro, I would like resolve this as soon as possible.
rikrdoVe said:
I cant install sdk and use adb... I resume: Dowloaded sdk from the page, and when i start sdk manager "Platform Tools" cant update i got this error: Stopping adb server succeeded. Failed to rename directory C:\adt.bundle.windows-x86-20131030\sdk\platform-tools to C:\adt.bundle.windows-x86-20131030\sdk\temp\PlatformToolPackage.old01. Nothing was installed"
I dont know if sdk was installed or what. only have the folder in C:
I put the boot.img file in platform-tools and tried to flash the image using the command fastboot flash boot boot.img but tells me the boot.img arrchivo not be found.
The phone does not recognize the pc, the bootloader is relocked.
Thanks for your support bro, I would like resolve this as soon as possible.
Click to expand...
Click to collapse
Well it seems you have installed the Android SDK all right. and make sure you put the file in the platform tools folder, and also make sure you have installed the HTC drivers for your PC to detect your phone , you can also try uninstall the driver and re install
ethanon said:
Well it seems you have installed the Android SDK all right. and make sure you put the file in the platform tools folder, and also make sure you have installed the HTC drivers for your PC to detect your phone , you can also try uninstall the driver and re install
Click to expand...
Click to collapse
Ok, i updated Platform-Tools to rev. 19.0.1, I had to start windows in safe mode.
But, yestarday Android sdk tools appeared in the list of installed programs in windows, i uninstalled and install today again but now i dont see sdk in list. Anyway, i open cdm and type "adb reboot-bootloader" and it says "error: device not found".
Then y type: fastboot flash boot boot.img and it says "error: cannot load boot.img"
I put the boot.img in C:\adt-bundle-windows-x86-20131030\sdk\platform-tools
And now... I dont know what to do
rikrdoVe said:
Ok, i updated Platform-Tools to rev. 19.0.1, I had to start windows in safe mode.
But, yestarday Android sdk tools appeared in the list of installed programs in windows, i uninstalled and install today again but now i dont see sdk in list. Anyway, i open cdm and type "adb reboot-bootloader" and it says "error: device not found".
Then y type: fastboot flash boot boot.img and it says "error: cannot load boot.img"
I put the boot.img in C:\adt-bundle-windows-x86-20131030\sdk\platform-tools
And now... I dont know what to do
Click to expand...
Click to collapse
Install the windows drivers , better try installing the the HTC sync manager. that way your device will be detected.
ethanon said:
Install the windows drivers , better try installing the the HTC sync manager. that way your device will be detected.
Click to expand...
Click to collapse
Ready, installed the HTC Sync Manager, and same result. "Device not Found"
if only I could get the phone to be recognized by the pc, I think it could solve the problem.
rikrdoVe said:
Ready, installed the HTC Sync Manager, and same result. "Device not Found"
if only I could get the phone to be recognized by the pc, I think it could solve the problem.
Click to expand...
Click to collapse
From where are u trying the commands.............
u must put ur phone in recovery mode.......
Connect ur phone to PC......
from the platform-tools folder try "adb devices"........
The adb commands will work in recovery only........
in bootloader the fastboot commands will work..........
[email protected] said:
From where are u trying the commands.............
u must put ur phone in recovery mode.......
Connect ur phone to PC......
from the platform-tools folder try "adb devices"........
The adb commands will work in recovery only........
in bootloader the fastboot commands will work..........
Click to expand...
Click to collapse
The phone is not recognized by the pc.
I can not get into recovery because the bootloader is relocked. I can only enter fastboot, but when executing commands, either with adb, All in One Toolkit, Flasher Venom or the phone is not recognized "Error: Device not found"
I have the drivers installed, htc sync manager, and I'm afraid that this phone unusable ... Also I did have a backup but on PC, but if the phone is not recognized I can not run any command ...
Also, I was trying to run teh Stock RUU:
RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed
But When I run the. Exe signature throws an error (132) "find the correct signature and try again" and which is not correct. had sense 5 and 4.2.2 HTC One X + International.
Help please ... : (
same issue, cannot access recovery fastboot only
I hope this adds to this post if I miss speak I apologize in advance but I do not have the time or knowledge to post 10 times before strating my own thread so if this doesn't add value to this post, I have been reading and researching all week and now that I cannot use my phone I must intensely focus on this until it is fixed
Fed up with 4.3 and lower limitations and looking to get my monies worth on my phone, I look to upgrade to 4.3.1 or higher just started this week so I am a total newb, and if it means anything to anyone I would be happy to donate to contributors via papal once a solution is found I am a working professional and I am happy to pay you to save my time/phone
with that said here is what I have done
HTC One X+ (AT&T US) Quad Core Tegra 3
OTA upgraded 4.2.2 Android Firmware 2.15
Unlocked BL via HTCDev
Was using;
Recovery-clockwork-6.0.3.7-enrc2b.img
With intent to upgrade to 4.3.1
Used the following Rom and GAPPS to load .zips via CWM
cm-10.2.1-enrc2b (stable)
gapps-jb-20130813-signed.zip
Did not work
Tried more recent gapps
Did not work got stuck on Circling Cyanogenmod screen
//goo.gl/YzZ75o
THEN
I realized I was not flashing boot.img taken from the CM 10.2.1 zip so I followed directions to use the boot.img then load the zip files, since doing this I can no longer use my recovery
Erase Cache (from fastboot)
COMMANDs:
./fastboot erase cache
./fastboot reboot-bootloader
Results:
White HTC “Quietly Brilliant” Screen for a few seconds then turns off
Plug in charger and Red light turns on grey empty battery symbol appears with a lightning bolt inside then disappears
red light turns off :-/
//goo.gl/JrBJph
Current state: I can fastboot, but I cannot load recovery
//goo.gl/43F6XT
Also, if I can get back into recovery
The last time I was in it, last night I believe I reformatted my internal SD, because when I was looking for my backup, and my zips they were all gone...I was very tired and should haven't pushed it.
I don't care about loss of data I just need to get my phone working again, thanks for your time and careful considerations
UPDATE+++
Used WinDroid HTC One X+ Toolkit 3 to flash custom recovery CWM 6.0.3.7 back in recovery again, now I think I need to side load a ROM because I deleted what I had internally
cclifford81 said:
I hope this adds to this post if I miss speak I apologize in advance but I do not have the time or knowledge to post 10 times before strating my own thread so if this doesn't add value to this post, I have been reading and researching all week and now that I cannot use my phone I must intensely focus on this until it is fixed
Fed up with 4.3 and lower limitations and looking to get my monies worth on my phone, I look to upgrade to 4.3.1 or higher just started this week so I am a total newb, and if it means anything to anyone I would be happy to donate to contributors via papal once a solution is found I am a working professional and I am happy to pay you to save my time/phone
with that said here is what I have done
HTC One X+ (AT&T US) Quad Core Tegra 3
OTA upgraded 4.2.2 Android Firmware 2.15
Unlocked BL via HTCDev
Was using;
Recovery-clockwork-6.0.3.7-enrc2b.img
With intent to upgrade to 4.3.1
Used the following Rom and GAPPS to load .zips via CWM
cm-10.2.1-enrc2b (stable)
gapps-jb-20130813-signed.zip
Did not work
Tried more recent gapps
Did not work got stuck on Circling Cyanogenmod screen
//goo.gl/YzZ75o
THEN
I realized I was not flashing boot.img taken from the CM 10.2.1 zip so I followed directions to use the boot.img then load the zip files, since doing this I can no longer use my recovery
Erase Cache (from fastboot)
COMMANDs:
./fastboot erase cache
./fastboot reboot-bootloader
Results:
White HTC “Quietly Brilliant” Screen for a few seconds then turns off
Plug in charger and Red light turns on grey empty battery symbol appears with a lightning bolt inside then disappears
red light turns off :-/
//goo.gl/JrBJph
Current state: I can fastboot, but I cannot load recovery
//goo.gl/43F6XT
Also, if I can get back into recovery
The last time I was in it, last night I believe I reformatted my internal SD, because when I was looking for my backup, and my zips they were all gone...I was very tired and should haven't pushed it.
I don't care about loss of data I just need to get my phone working again, thanks for your time and careful considerations
Click to expand...
Click to collapse
ummm your flashing the X+ International CM rom and not the evitareul one, reboot into the bootloader and then enter recovery from there.
Lloir said:
ummm your flashing the X+ International CM rom and not the evitareul one, reboot into the bootloader and then enter recovery from there.
Click to expand...
Click to collapse
Will do, thanks!
evitareul? Does that mean Flash TWRP recovery and then use evita ROM?
cclifford81 said:
Will do, thanks!
evitareul? Does that mean Flash TWRP recovery and then use evita ROM?
Click to expand...
Click to collapse
Evitareul = X+ AT&T
Sent from my Nexus 5 using Tapatalk
Lloir said:
Evitareul = X+ AT&T
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok so I just need the evitareul Rom, I'm looking for it now, I just need something stable at 4.3 or higher with GAPPS anyone have any links
cclifford81 said:
Ok so I just need the evitareul Rom, I'm looking for it now, I just need something stable at 4.3 or higher with GAPPS anyone have any links
Click to expand...
Click to collapse
look in original development
Lloir said:
look in original development
Click to expand...
Click to collapse
Ok, from what I can tell I think I have to go with this?
[ROM][2/18/2014][AT&T X+ S5 eXtreme V1.0.3.3]
I will be very happy if I can get this to work, and I will just "stay tuned" for when I can flash a stable 4.3 or higher for my phone
Under downloads I see the following: (would post picture but still too n00b)
S6 eXtreme RC1
S5 RC2 Patch
Native WiFi
Hotspot Patch
S5 eXtreme
V1.0.3.2
S5 eXtreme
V1.0.3.3
I am not sure what to download here, I will continue reading these directions as I believe this is my best option, please confirm if I am on the right path, thanks guys!
Update+++
Downloaded S5_eXtreme_V1.0.3.3_Signed.zip
about to flash this ROM, is GAPPS included in this?
Update+++
Downloaded S5_eXtreme_V1.0.3.3_Signed.zip Rom
Extracted the boot.img file and followed instructions
Extract boot.img from zip file and place in your sdk platform tools folder, (or wherever your adb tools are located)reboot device to bootloader and connect it to your PC.
From a command prompt type:
1. fastboot flash boot boot.img
2. fastboot erase cache
reboot to recovery and flash ROM.
but I am not sure how I flashed the ROM, I tried sideloading from recovery with WinDroid HTC One X+ Toolkit, before and after and it said no package loaded
Then I tried to load from fastboot, finally I figured "well I might as well reboot" and amazingly enough it booted...not sure what exactly but I am back on 4.2.2 so thank you!
[[ SOLVED ]]
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
rikrdoVe said:
I was trying to flash a rom and I did wrong.
The phone got stuck on the white HTC screen.
I'm trying to get it back, the problem is that when I connect to the pc is not recognized. I installed SDK Tools, adb, drivers and all.
All In One Toolkit run and try to flash the boot.img but it says "error: device not found"
I run adb commands but it says the same thing, "error: device not found"
I tried it with Venom Flasher but I can not solve.
I uninstalled and went back to install the drivers, but I still have the same result, I run out of options.
When I turn the phone enters fastboot, I can access the recovery, but the phone at this time does not rom, dead.
By mistake I went to lock the bootloader but today I unlock it again with the All In One Toolkit and the bin file, so do not understand why if the file could flasher to unlock the bootloader again, but when trying to flash the boot.img or execute commands like: adb devices, adb reboot bootloader throws the error "device not found"
I appreciate it can help me ...
Click to expand...
Click to collapse
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
reaper90 said:
ADB commands are only recognized in recovery or when system is running. re-unlock your bootloader first. you can reboot into bootloader by pressing and holding power & volume-down button. navigate using volume buttons and enter fastboot by pressing power button. Now you can flash boot.img with "fastboot flash boot boot.img" or using any One X+ compatible toolkit. If it doesn't work, try installing latest HTC sync on your computer to get latest drivers. you can uninstall htc sync later again, the drivers will remain installed.
Here's a guide how you can setup adb/fastboot on cour computer, also contains useful information for beginners: http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
rikrdoVe said:
Yeah, try doing that. I locked boot loader again but still had no results. What I did right now was "fastboot flash boot boot.img" says ok, but just gets stuck on the white screen. The phone right now has no information, nothing. I have in my pc folder with the rom that was installed (zip with boot.img) I have the latest version of clockworkmode.
Click to expand...
Click to collapse
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
reaper90 said:
Some more information please. What rom did you flash and what recovery did you use? also do you have international version of this phone or AT&T/Telus version?
Click to expand...
Click to collapse
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
rikrdoVe said:
1. Carbon ROM: http://forum.xda-developers.com/showthread.php?t=2447870&page=33
2. CWM 6.0.4.6
3. Yes, international version.
Click to expand...
Click to collapse
Did you use the right version of CWM for android 4.4+?
reaper90 said:
Did you use the right version of CWM for android 4.4+?
Click to expand...
Click to collapse
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
rikrdoVe said:
Correct, as said in the post "Note: For KK 4.4.x necessary CWM recovery from Lloir's thread."
Click to expand...
Click to collapse
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
reaper90 said:
Did you do a wipe in before flashing the new rom?
Anyway you can copy a new rom.zip onto your phone using "adb sideload rom.zip" or "adb push rom.zip /data/media/0" while you're in recovery. Then do a full wipe first, flash rom and don't forget to flash boot.img.
Click to expand...
Click to collapse
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
rikrdoVe said:
Thanks for your help...
I cant flash zip file, its says "error: device not found".
I put the zip file in adb folder, then "adb sideload filename.zip"
Do not know if I'm doing well, I turn on the phone in recovery mode, then with the volume keys I go to "install zip" option then "install zip from sideload" then run the command I get the error.
Click to expand...
Click to collapse
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
reaper90 said:
ADB may take some time to recognize your device in recovery. Try "adb devices" first and if it isn't listed as in recovery or sideload, wait some minutes and try again. Shouldn't take more than 5 minutes though.
But you have installed latest drivers?
Click to expand...
Click to collapse
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
rikrdoVe said:
Hey, i tried that, and says:
List of devices attached:
FA31ZW100713 recovery
And then, i write "adb sideload filename.zip"
Error: Closed >>
I waited 6 minutes and the same result.....
And yes, i have the latest drivers and HTC Sync Manager.
Click to expand...
Click to collapse
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
reaper90 said:
Your phone needs to be in recognized as in sideload mode in order to use adb sideload. when recognized in recovery, try "adb push rom.zip /data/media/0", this will copy your rom onto your phones internal memory. Depending on rom size, this may take some minutes and there's no progress bar/display, so give it some time, 10 min should be enough.
Click to expand...
Click to collapse
A month without phone and thanks to you it works again!
Thank you so much, I could not pass the zip in any way but with "adb push rom.zip / data/media/0 /" if it happened and I could flash ...
I Repeat .... THANK YOU!
have the same problem with my HTC One X.
Can you gave me an answer?
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img