Related
Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....
It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good
timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now
so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA
topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App
Nevermind I got the Su command to work
Sent from my PC36100 using XDA App
you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.
Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!
hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?
Build number 1.47.651.1 CL195459 release-keys
yea same here......and what is it that your trying to do...go back to stock ROM?
I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.
OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!
I may have bricked my phone and it would be nice to know:
First off if I have.
Second Can i fix it, and how?
I installed the cyanogenmod 6.whatever the newest one is which I can't seem to locate right now. An I found that I liked sense quite a bit so I went to restore from a backup of the Fresh v3.etc rom I was running previously. Halfway through the restore, it failed saying that it was "unable to flash the boot image" Now when I try to boot my EVO I get stuck at the white "htcEVO4G" loading screen and I cant get passed it.
I've tried to flash a new rom (multiple times with the same and different roms), wipe and flash a new rom, at some point I guess i deleted my all my nandroid backups except the one of Fresh which continues to fail.
I CAN boot into recovery and access all of those features properly however (if that helps). I am using the ClockWorkMod recovery as well. (Hboot 2.10.0001)
I was thinking that this didn't look too good for me and I couldn't find anything similar on the forums so I decided to ask here.
If I need to supply any more info on the situation please ask but I think I covered all my bases.
Thanks in advance for any help,
Cheers,
IGC_BlasIAN
what version of clockwork did you use
It says v2.5.0.1 in recovery mode, it was whatever is the latest in ROM Manager as I made sure I was up to date before flashing the new ROM (cyanogen).
All of this occurred yesterday (January 14)
Download Calkulin's wipe all zip and flash it from recovery. Then download Fresh Rom and flash it. There should be an option in Clockwork to be able to transfer files to your sdcard. Start new since the nandroid is failing. You are not bricked if you can access hboot and recovery. If my previous suggestion fails download the latest shipped OTA PC36IMG.zip and make sure it is named PC36IMG. Place it on the root of your sdcard and boot into hboot by holding volume down and power at the same time and it should recognize the PC36IMG.zip and automatically load it. Then choose yes when it asks if you want to update by pressing volume up. If your phone reboots during the process let it detect the image again and it will automatically continue the update. DO NOT PULL THE BATTERY AT ANY TIME DURING THE UPDATE. This could really get you a brick. Good luck.
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?
sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo
Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help
erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X
encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?
Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what
Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?
oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!
whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.
HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App
I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App
Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App
Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!
I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance
You're in the wrong forum, this is the HTC One XL/at&t One X forum. I'll ask for this to be moved to the correct device forum for you.
Sent from my Evita
your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904
nogotaclue said:
your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
omg, i feel so stupid that i did this.. thank you very much! i now flashed TWRP and it worked, I'm waiting till the battery charges and i'll install CM again, but looks like it gonna work this time.
thanks again, that link was really helpful.:good:
Ok, don't forget to use the right cm, not the version you used previously
Sent from my HTC One X using XDA Premium 4 mobile app
xulube said:
I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance
Click to expand...
Click to collapse
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.
okhughes said:
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.
Click to expand...
Click to collapse
he doesn't need to start from scratch, he knows how to do it. the problem was he was in the wrong forum. did you even read the thread?