the title says it all basicky i made simple mistake and deleted davlik cache and all that and i cant acesess cwm and i cannot not do factory reset or anthing is way a way i can reset everything through fastbootusb mode or anythin and i have just had the phone for 4 days so am pissing my pants, any help would be much appreciated!!
mtumnene said:
the title says it all basicky i made simple mistake and deleted davlik cache and all that and i cant acesess cwm and i cannot not do factory reset or anthing is way a way i can reset everything through fastbootusb mode or anythin and i have just had the phone for 4 days so am pissing my pants, any help would be much appreciated!!
Click to expand...
Click to collapse
Boot into fastboot (volume down and power) plug in lead.
In command prompt, navigate to adb folder and type: fastboot erase cache
If this doesn't work then more information as to what you have done will be needed before I can help you.
First, punctuation.
Sent from my HTC One X using XDA
bobsie41 said:
Boot into fastboot (volume down and power) plug in lead.
In command prompt, navigate to adb folder and type: fastboot erase cache
If this doesn't work then more information as to what you have done will be needed before I can help you.
Click to expand...
Click to collapse
Ignore
---------- Post added 25th May 2012 at 12:02 AM ---------- Previous post was 24th May 2012 at 11:59 PM ----------
Fokas. said:
First, punctuation.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
That's really helpful thanks.
reply
i tried that but no luck, (and what imformation do you need) what i did was i used Android_Revolution_HD_Super_Wipe_One_X but i done a stupid mistake instead of flashing Android_Revolution_HD-One_X_6.0.0 after the first thing i did .i rebooted the phone then i lost i cwm and couldnt access it and just stuck on the boot load menu and i cant even do factory reset even from their,
if you need more imfo plz ask cause am so scared lol
Erasing the Dalvik has absolutley no bearing at all on accessing CWM, that wont be the cause of the problem, as suggested you need to boot to fastboot, from there relock ya boot if you unlocked it and run the correct RUU for your phone which will rewrite recovery and everything back to stock.
Make sure in future, especially if flashing custom roms you research the instructions first, failure to do so is what leads to trouble and youre in the best place to get help, Xda community is the best.
reply
(glad to hear that) am not very familiar with the technical jargon, if its not a burden could write a step by step guide on how I can do that please
Don't panic its not a brick.
Hold power 7 seconds to restart phone, when off hold vol down to enter HBOOT.
Once in HBOOT press power to enter fastboot.
First try 'fastboot erase cache' and then 'fastboot reboot-bootloader' this should do the job, if this don't work, reboot into fastboot and try below.
On your pc open cmd and change directory to where your adb and fastboot are. Once there use 'fastboot oem lock' your bootloader should now say Relocked I think.
After that download RUU specific to your handset and run. This should install fine and return you to stock.
After done you may need unlock bootloader again, I did via HTCDEV and then reflashed recovery with 'fastboot flash recovery *recovery name*
Job done, phone restored, panic over
Credits to jdroid of cardiff for this helpful post....
reply
ok i will follow what said(as for unlocking the bootloader would i have to go through htc dev all over again
Not if you still have the bin file they sent you. Just push it bk to the phone as b4
Sent from my HTC One X using xda premium
First, you need to download the rom from htc, find your version in this thread: http://forum.xda-developers.com/showthread.php?t=1543604
then ejecute it, and go to this folder: %temp%, find a folder that contains a ROM.ZIP file, inside you will find boot_signed.img and recovery_signed.img.
Now do this:
-fastboot erase cache
-fastboot reboot-bootloader
-fastboot flash recovery recovery_signed.img
-fastboot reboot-bootloader
-fastboot flash boot boot_signed.img
-fastboot reboot-bootloader
-fastboot oem lock
then go to FASTBOOT SCREEN and run the downloaded RUU.
sorry, what file you talking bout.
cant find the correct ruu for 02 uk have tried file factory but the only have and its the wrong 1, any advice
mtumnene said:
cant find the correct ruu for 02 uk have tried file factory but the only have and its the wrong 1, any advice
Click to expand...
Click to collapse
O2 means an operador or it is your CID? If 02 its your cid you can try the lastest 1.29.401.11 RUU.
http://www.filefactory.com/file/6kvkplch72kf/n/RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
Im not sure about it, but you have nothing to lose. Try it.
Sent from my HTC One X using XDA
Boot to bootloader, enter fastboot mode, use
Fastboot OEM readcid
in cmd window from your fastboot folder. It will show your CID then. Post this here and it might help to determine/find the matching RUU
Sent from my HTC One X using xda premium
ye my network operator is 02 have tried download the RUU its say "Sorry, the server hosting the file you are requesting is currently down for maintenance. Please check back soon" so i will try later, and i have done what you said on the cmd but just gives other options it does not give me the cid directly.
O2 RUU : RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
Download here : http://hoxroms.serveftp.com/RUU_END..._Radio_1.1204.90.13_release_251230_signed.exe
ye i have tried that one but no luck its say its the wrong before i fuc*ed up my phone it was running on 1.29.401.11.
1.29.401.11 stock ?
http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.105.14_release_260491_signed.exe
hello i have download the RUU u suggested but it first said error it didint connect the phone even though when i tried the other wrong RUU it didnt say that and now it say my battery is low than 30% so how can charge so i can try again if i load the "htc quietly brilliant" logo it show the red signal on top does that mean its charging. (as for stock software it wasnt the one told you when i got it,i updated using my phone via ota)
Related
Ok, so basically, I formatted everything on the phone like a douche, and its stuck on the HTC Quite Brilliant screen.
I tried using fastboot and adb, but it shows "device not found" even though the drivers are saved.
Any clue?
Any help would be appreciated. Thanks.
you need to flash a stock RUU. im not sure what development is like for the one X, id assume not alot yet. you need to either flash a fully stock RUU or someones backup. i feel for you bro, ive never fully bricked a phone but i DID format every partition on my intercept once, and i fixed it through a custom recovery flash of a stock rom, samsung is nothing like htc though....
Sent from my PG86100 using XDA
Try this http://forum.xda-developers.com/showpost.php?p=25863603&postcount=11
Or flash official RUU
ckpv5 said:
Try this http://forum.xda-developers.com/showpost.php?p=25863603&postcount=11
Or flash official RUU
Click to expand...
Click to collapse
As soon as i do the "fastboot boot xx-recovery.img" command, on the CMD it shows:
downloading 'boot.img . . .
OKAY [ 0.789s]
booting . . .
OKAY [ 0.006s]
finished. total time: 0.803s
but on the phone, it just stays on the Fastboot USB screen. I cant move it with the volume keys or press power to select a choice like its frozen on that screen.
I need help.
I really need my phone, if anyne could please give me a solution to this.
Been trying all night and day
Thanks for your help though guys, its really appreciated.
Try clearing the cache and then doing that again.
"fastboot erase cache"
then do your recovery.
Just tried that, still no luck.
Same thing happens.
After
downloading 'boot.img . . .
OKAY [ 0.789s]
booting . . .
OKAY [ 0.006s]
finished. total time: 0.803s
Sometimes pull out the USB cable will help
ckpv5 said:
Sometimes pull out the USB cable will help
Click to expand...
Click to collapse
Did that as well bro :/
I'm on a different computer to see if itll work on here.
Have you try flashing RUU when fastboot boot recovery.img seems not working for you ?
Do you have any instructions I can follow?
(Even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
You must have the official RUU for your phone, stock recovery and stock boot.img.
Do you have the RUU ? You need to know which is the right RUU for you. See http://forum.xda-developers.com/showthread.php?t=1543604 to look for one.
I will try this when I get home
Whether this works or not I would love your PayPal email address please.
Just for your effort in trying to help me so much I just HAVE to pay you back.
Thanks so much again.
shawayne21 said:
I will try this when I get home
Whether this works or not I would love your PayPal email address please.
Just for your effort in trying to help me so much I just HAVE to pay you back.
Thanks so much again.
Click to expand...
Click to collapse
Have you manage to solve your problem ?
You don't have to pay me back, I'm always happy when I manage to help others.
And because of some request for my PayPal email address, first time after four years with XDA, I put the "donate to me" box, but you don't have to
EDIT: Are you still on stock ROM before the brick ? If yes, you don't have to do all the step, just flash RUU.
ckpv5 said:
Have you manage to solve your problem ?
You don't have to pay me back, I'm always happy when I manage to help others.
And because of some request for my PayPal email address, first time after four years with XDA, I put the "donate to me" box, but you don't have to
EDIT: Are you still on stock ROM before the brick ? If yes, you don't have to do all the step, just flash RUU.
Click to expand...
Click to collapse
Gotcha, didnt even see the donate box
When I tried RUU'ing, it gave me an error.
Error 131: customer ID error
And I was on a stock rooted ROM before the brick.
Which RUU are you trying to use? And which software version were you on when you bought it?
I was trying to using this one:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe 601.21 MB 1 week, 3 days ago
and see that I dont know, I literally had the phone in my hand for 5 minutes.. Just bought it off of a member here and opened the box to format and wipe data on everything, as I do to every phone, but I didnt know you couldnt mount sd in recovery on this phone yet
Can you go to bootloader and see what is your radio version ? And the hboot too.
Maybe it helps to determine which RUU is the correct one for you
Person I bought it from said he bought it from Expanys USA.
The HBOOT version is 0.43.0000
RADIO: 1.1204.90.13H
BTW, I flashed the stock recovery and relocked the bootloader but i didnt flash the boot.img
I have no idea where to get it from.
hey dude whats your cid for your Phone?
U have to use the correkt ruu matching your cid, or else ruu installation will be abortet!
how to check the cid:
in fastboot whith usb type "fastboot getvar cid"
if this is not working try this:
enter "adb shell"
now enter "getprop ro.cid"
android sdk should be installed to make use of the second option getting the cid.
After that you should search for the correct ruu matching this cid.
If u got it, first thing to do ist installing stock recovery. U cant get the recovery here:
http://forum.xda-developers.com/showpost.php?p=24777223&postcount=163
flash it via fastboot typing "fastboot flash recovery stockrecovery.img"
after that u have to relock your phone using the comand "fastboot oem lock"
now leave your phone in fastboot usb mode and try to start the ruu installer from your desktop pc
now it should work if u have the correct matching ruu
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU (ROM Update Utility) for your device from androidfiles.org. Make sure you download a Primo_C RUU for a CDMA device (no sim card) or a Primo_U RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Hi
Thanks for that perfect decsription exactly when I needed it
I just had a weired effect with my new windows 7 laptop that I want to share.
I installed the USB drivers and "fastboot devices" showed my HTC fine
but even flashing the stock recovery image was not working.
So it was stucking in the "Sending" part and never continued.
I then moved to my old laptop with Vista did exactly the same things
and there it worked without problems.
I disabled virus scanner, checked for htsync and used the original USB cable
without success.
But now I know why I normally never touch Windows and only
work on linux
Regards
max
---------- Post added at 11:19 PM ---------- Previous post was at 10:33 PM ----------
Hi
CafeKampuchia said:
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
I have done that now - compared to my first "try"
Regards
max
hi. thanks for the tips.
however when i do this, i get an error "FAILED <remote: signature verify fail>
Any suggestions?
ur RUU and CID is diff...
ryanlow134 said:
ur RUU and CID is diff...
Click to expand...
Click to collapse
and... how do i make them the same?
lcavada said:
and... how do i make them the same?
Click to expand...
Click to collapse
Use the correct RUU package for your device
regards
max
Another way of saying it is that you downloaded the wrong RUU for your device.
not working
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
I use fastboot flasher for this.. this tool is good .
sush93 said:
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
Click to expand...
Click to collapse
"Waiting for Device" at fastboot usually related to bootloader driver. You need Android USB Driver
See : http://developer.android.com/sdk/win-usb.html
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
run the ruu in hboot..
Sent from my HTC One V
thevilish said:
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
Click to expand...
Click to collapse
Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
NOTE: There is no boot/reboot and enter pin in between.
paarthdesai said:
run the ruu in hboot..
Sent from my HTC One V
Click to expand...
Click to collapse
I've done this before and didn't succeeded, but now it works! Magic
Thanks a lot!
help
CafeKampuchia said:
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
PLEASE HELP!
The 5th point does not work for me. I can not run the code.
What can i do?
what do you mean by navigate to the folder where you installed sdk?
brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
It means that if you installed SDK in c:/android, then u must type.in the command prompt: cd c:/android and hit enter
Cheers
Sent from my HTC One V using xda app-developers app
brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
where the fastboot.exe is located and stock recovery must be in the same folder for the command to work
[ask] Error 155
hey guys, ive been reading all tutorial for reverting to stock RUU.
the first time i tried, it works prefectly.
then after a few weeks, i tried to revert to stock RUU, it failed .
it show error 155.
i already flash the boot , recovery that i found inside the stock RUU, also I've relock the phone.
but when i relock the phone, it show "info Lock successfully , status read failed no such file / directory"
when i enter bootloader, it show that my device already "relocked"
does the relocked proses is successfully ?
iam running PrimoU 2.09.707.1 with stock bootloader, CWM recovery, and rooted ..
I did exactly as it is mentioned but at the end where there is vertical progress bar it gives me an error of customer Id... Failed to update. What shud i do. How do I check what my customer Id is I can't Download it from play store coz can't boot into normal screen... How do I make ruu and cid same.
Sent from my Galaxy Nexus using xda app-developers app
Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(
Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"
Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA
Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly
This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:
Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%
ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.
ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?
i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man
I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app
Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App
You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.
You could also take this opportunity to install a custom Rom, with which I can also help.
Hey guys , am having a problem with my htc one x recovery ,
as i was going with the rooting of my phone i got stack at 1 point where i needed to use recovery so i could access the zipped file in my htc (i have already unlocked the bootloader). So when am getting to the point of using recovery from the fastboot screen with the color letters (using volume up and the power button to navigate as always) the htc message pops up trying to load the recovery and then a black screen pops up with the icon of the mobile and a green cyrcle, and after a few secs of loading theres another icon with a red triangle and a exclamation mark. at that point the phone stacks with that icon and i can do nothing. after a couple of mins the phone just restarts by itself and am back on the normal htc interface...
In the video i saw after he used recovery none of those icons where seen and it loaded up the default directories of the phone, as i was searching in net i saw a prob like that and the solution was to erase the fastboot erase cache, already erased the cahe but the problem is still there, if any solutions for that would be greatly apreciated !
Did u flash a custom recovery ? Latest is cwm 5.8.4.0
The one u are describing is the stock one.
Verstuurd van mijn HTC One X
The recovery you described is HTC's stock recovery ... Go to here - > http://forum.xda-developers.com/showthread.php?t=1594819 < - and download the first link and put it into your phone sdcard then reboot into fastboot and fastboot flash recovery <recovery name>.img and you're good to go for flashing ROMs
chaun1308 said:
The recovery you described is HTC's stock recovery ... Go to here - > http://forum.xda-developers.com/showthread.php?t=1594819 < - and download the first link and put it into your phone sdcard then reboot into fastboot and fastboot flash recovery .img and you're good to go for flashing ROMs
Click to expand...
Click to collapse
Wrong mate....
Download the cwm recovery and put in the fastboot folder on PC.
And also give this command before AND after flashing the recovery.
Fastboot erase cache
And why giving the answer again, i already gave the answer, and get your facts right ! This is the second post i see around with a small error in it
Sent from my ..........
MarcelHofs said:
Wrong mate....
Download the cwm recovery and put in the fastboot folder on PC.
And also give this command before AND after flashing the recovery.
Fastboot erase cache
And why giving the answer again, i already gave the answer, and get your facts right ! This is the second post i see around with a small error in it
Sent from my ..........
Click to expand...
Click to collapse
no need to put the recovery.img in the fastboot folder:
Code:
fastboot flash recovery path/to/recovery.img
Very true .... but to keep it more clear (just like putting the boot.img in the fastboot folder,.like most tut's say) i advice to do it straight from the fastboot folder, so in that way the commands stay the same.......if you get my point
Verstuurd van mijn HTC One X
tyvm guys really helped , the guy in the video i was watching forgot that step ... well either way flashed the recovery and after following the next steps i rooted + tried to load the new maximus v6. and huston we have a problem . when i rebooted after the instalation of the custom rom my phone stack in the white first loading screen of the phone (htc quitely brilliant) any suggestions in that?
Solidarious said:
tyvm guys really helped , the guy in the video i was watching forgot that step ... well either way flashed the recovery and after following the next steps i rooted + tried to load the new maximus v6. and huston we have a problem . when i rebooted after the instalation of the custom rom my phone stack in the white first loading screen of the phone (htc quitely brilliant) any suggestions in that?
Click to expand...
Click to collapse
Have you flashed boot.img?
I think it's better to read more rather then watching half baken video's (what you did not know) it's better to follow the tutorials here ! :thumbup:
And yes like said before flash the boot.img
Extract it from the rom.zip and place it in fastboot folder
Phone in fastboot USB mode and do the following command
Fastboot flash boot boot.img
Fastboot erase cache
Just like you did with the recovery
Reboot !
Verstuurd van mijn HTC One X
ok.. so i just searched a bit in this forum and the tutorials here as u said , and y after i saw in here am not going to trust any videos and just follow the forum.. i missed a couple of steps first i dont know what CID i have , which as i've seen its very important ( any ways to check now that i cant use my htc and am stack in bootloader?) 2nd i ve seen i need to have the hboot 1.31 for it to work and currently i don't. thought that maybe that would fix it and downloaded it and as the steps told me
1.i relocked the bootloader
2.downloaded the firmware.zip from the forum instructions
3.entered succesfully the command "fastboot oem rebootRUU"
4. { (4) In order to flash new hboot write "fastboot flash zip firmware.zip" } and here am stuck cause when am typing the command am getting FAILED <remote : not allowed) and in that step i saw a vid again (i know...but am desperate) which he said if that happens u should use the
adb reboot oem-78. which i did and after it opens deamon it says error : device not found
and also u said:
And yes like said before flash the boot.img
Extract it from the rom.zip and place it in fastboot folder
i know i might be asking for much but plz put some more detail form me as am somewhat new to this and i might not understand some of the ways
for example which one is the boot img? the hboot 1.31 ? and what do u mean extract from rom.zip ( the custom rom maximus v6 i downloaded u mean?) and i really apreciate ur time guys ur helping me much hope i can still use my phone after ur instructions atm i crying over a my dead phone help me bring it back ( if its possible ;/)
boot.img is insite the custom rom zip file open the zip file with totalcommander take out the boot.img an fastboot it
so u mean the boot.img inside the zipped folder from the instuctions named firmware ? the one that has the hboot 1.31? cause if thats the case i tried and i unzipped it put it on the fastboot folder and tried to run the commands like this
fastboot flash boot boot.img
what i got is
sending 'boot' <5260 KB>....
OKAY [ 0.6s ]
writing ' boot'....
FAILED < remote : not allowed>
finished . total time : 0.9s
so that got me curious and i typed adb devices to check on cmd ... but my phone is not listed there o-o
while i was doing this the phone is on fastboot menu with the cable attached and says FASTBOOT USB.
any ideas? also how could i manage to come so far if the phone couldnt be reached in the first place (something changed meanwhile?) any ideas?
Solidarious said:
sending 'boot' <5260 KB>....
OKAY [ 0.6s ]
writing ' boot'....
FAILED < remote : not allowed>
finished . total time : 0.9s
Click to expand...
Click to collapse
that's because you bootloader is locked
EDIT: also install the htc drivers
matt95 said:
that's because you bootloader is locked
EDIT: also install the htc drivers
Click to expand...
Click to collapse
well i relocked the bootloader cause the instructions said i had2 , also the htc drivers are installed and the device in device manager on my pc is running smoothly. So i have to reunlock in order to boot the boot.img? if so how can i reunlock it :? can u type me the exact commands? thought it was fastboot oem unlock but there seems to be an error !
Solidarious said:
well i relocked the bootloader cause the instructions said i had2 , also the htc drivers are installed and the device in device manager on my pc is running smoothly. So i have to reunlock in order to boot the boot.img? if so how can i reunlock it :? can u type me the exact commands? thought it was fastboot oem unlock but there seems to be an error !
Click to expand...
Click to collapse
you have to unlock it in order to upgrade th firmware but when the firmware is flashed you have to unlock it again, because with the bootloader locked you can't use fastboot to flash anything....
matt95 said:
you have to unlock it in order to upgrade th firmware but when the firmware is flashed you have to unlock it again, because with the bootloader locked you can't use fastboot to flash anything....
Click to expand...
Click to collapse
ok i get it i have to reunlock the bootloader but how? ... the last step i remember from the first time i did was till i got in my email the unlock.bin after that? isnt it the fastboot oem unlock? idk ;/ help
and btw i found a way to check my cid fastboot oem readcid lolz was typing random xD. E11 is my cid so 1 less thing to worry about as its supported
Solidarious said:
ok i get it i have to reunlock the bootloader but how? ... the last step i remember from the first time i did was till i got in my email the unlock.bin after that? isnt it the fastboot oem unlock? idk ;/ help
and btw i found a way to check my cid fastboot oem readcid lolz was typing random xD. E11 is my cid so 1 less thing to worry about as its supported
Click to expand...
Click to collapse
unlock the phone via HTCdev.com...
matt95 said:
unlock the phone via HTCdev.com...
Click to expand...
Click to collapse
well actually didnt need to do anything via htcdev but i did the same steps and found the command i needed
which was:
fastboot flash unlocktoken Unlock_code.bin but ty though gave me the idea
just did booted the boot.img and i ll let u guys know what happend next ! great help from all of u
thanks to all
Solidarious said:
well actually didnt need to do anything via htcdev but i did the same steps and found the command i needed
which was:
fastboot flash unlocktoken Unlock_code.bin but ty though gave me the idea
just did booted the boot.img and i ll let u guys know what happend next ! great help from all of u
thanks to all
Click to expand...
Click to collapse
glad to help
Im sorry if this has been answered so many times but ive spent about 4 hours looking around and i couldnt understand half of the solutions that were out there. My problem is that i attempted to root my htc one x and i succeeded. Then i tried to put the new jellybean 4.2.2 cyanogen10.1 mod nightlies or something like that. This failed terribly. I have no back ups or anything what so ever. I dont care about anything i may have lost, i only want to get the phone working again. I know i should have researched this further before trying, but yeah... if anybody has done the same thing and solved there matter i'd be so grateful. it still responds on fastboot. heres some info on the bootloader screen. I tried factory resetting it, clearing the cache...none worked.
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
Radio-5.1204.164.30H
eMMC-bootmode:disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012,13:59:37
Did you flash the boot.img from the CM10.1 rom ?
Mr Hofs said:
Did you flash the boot.img from the CM10.1 rom ?
Click to expand...
Click to collapse
well not sure what you mean but i did put the boot.img in the same folder with the adb stuff and attempted to reboot it on fastboot but the same thing happened.
Phone in the bootloader and flash the boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Did you do that from the command window on the pc ?
Mr Hofs said:
Phone in the bootloader and flash the boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Did you do that from the command window on the pc ?
Click to expand...
Click to collapse
yes however i only did the fastboot erase cache once not after the the second command. Also i wiped all the date on recovery mode. should i try the commands above again? sorry if im being a pain
Best to do is :
Full wipe in the recovery ! Then install the CM10.1 rom and directly the GAPPS. don't reboot but type in the command window
Adb reboot bootloader
Then flash the boot.img and reboot
Mr Hofs said:
Best to do is :
Full wipe in the recovery ! Then install the CM10.1 rom and directly the GAPPS. don't reboot but type in the command window
Adb reboot bootloader
Then flash the boot.img and reboot
Click to expand...
Click to collapse
thanks but how do i install the cm10.1 and gapps when i cant enter my phones mass storage on pc.
Mount is a usb drive in the recovery
Mr Hofs said:
Mount is a usb drive in the recovery
Click to expand...
Click to collapse
okay ive installed the clockwork mod and im trying to enter the phones sotrage on pc, but i cant seem to do it. which option is it. mount/sdcard and mount/usb storage dont work
What recovery do have ? Version number ?
https://www.dropbox.com/s/guvfqd7tp8acxg6/recovery 5.8.4.0.img
Flash this one and go to mounts and storage and tap the last option in the list
Please help me..
Hi, same problem here..
my phone got stuck on the startup screen (HTC quietly brilliant). But my case is different because im a total noob, newly registered here. I bought my htc one x that is already in CM10 jellybean mode. last night i got a notification for cm10 update, I just click it without thinking much (cause im a noob) then after rebooting it just freezes... I hope senior members here can help me, i reallly dont want to lose my data..
You probably updated to CM10.1. You need to take the update's boot.img and flash it in fastboot.
Sent from my One X using xda premium
TToivanen said:
You probably updated to CM10.1. You need to take the update's boot.img and flash it in fastboot.
Sent from my One X using xda premium
Click to expand...
Click to collapse
many thanks for replying me..
sorry but im totally clueless at this point, i spent all night reading posts, watching videos.. i've seen the same advice (flash boot.img in fastboot) in several places, but still dont know how to do it .. I would be very very grateful if someone can guide me step by step to do this
You place the boot.img file from the CM10 rom.zip (its inside) in the fastboot folder on the pc, then you put the phone in the bootloader
Open the command window in the fastboot folder(point in the fastboot folder hold down shift + right mouse button- open command window here) and type
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Mr Hofs said:
You place the boot.img file from the CM10 rom.zip (its inside) in the fastboot folder on the pc, then you put the phone in the bootloader
Open the command window in the fastboot folder(point in the fastboot folder hold down shift + right mouse button- open command window here) and type
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Click to expand...
Click to collapse
Does it usually took a long time for every command to complete? im entering fastboot erase cache and <waiting for device> appear and its still there right now..
just to be sure, the bootloader mode is when the HBOOT is highlighted blue am i right?
oh i hate myself..
It should say
Fastboot usb in red text above that
In bootloader you should highlight fastboot using volume keys and press power. Then fastboot mode should be engaged and FASTBOOT USB text visible.
Sent from my One X using xda premium
Mr Hofs said:
It should say
Fastboot usb in red text above that
Click to expand...
Click to collapse
now i have fastboot usb in red and "<waiting for devices>" still there. any thoughts?? does this mean the PC doesn't recognize my phone or it I should wait longer?
Do you have HTC syncmanager installed on the pc ? Uninstall it but leave the drivers when asked !
Reboot the pc and the bootloader....check again.
And you should have a myhtc in the device manager when the phone is plugged in the pc
Mr Hofs said:
What recovery do have ? Version number ?
https://www.dropbox.com/s/guvfqd7tp8acxg6/recovery 5.8.4.0.img
Flash this one and go to mounts and storage and tap the last option in the list
Click to expand...
Click to collapse
i have version 5.8.4.0, i went to the last option and it still does not come up on the pc