I think I corrupted something - HTC Wildfire S

I picked up a Wildfire S Virgin Mobile that cannot be activated. I wanted a small mp3 player with an Android flavor. I unlocked the bootloader via HTCdev.com. I loaded Team BlueRidge Recovery 1.1.0. I made a nandroid backup.
I tried to flash a couple CM roms and on bootup they would get past the HTC splash screen and go blank and that would be it. I tried a GB rom and it flashed fine and booted up. However it turned out it was a marvel rom and not a marvelc rom so wifi and BT didn't work. I decided to try loading a TeamWin recovery. I put the newest one and when I tried to flash a rom it gave me an error. I downgraded it to v2.2.2.0 and had the same error. I put TeamRidge back on and now every rom I try to install errors on me.
I am guessing that I corrupted something when I tried to flash with TeamWin and now I can't flash anything. I reformatted the sdcard but it made no difference.
CAn anyone bail me out. I really want to run a CM9 or CM10 rom.

Anyone?? I am kinda stuck, so any ideas might help. Thanks

Try to install clockwork mod recovery using either fast boot or adb via your PC. I have never had issues flashing ROMs that way
Sent from my Crescent using xda app-developers app

Related

Stuck on boot screen! Help!

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.

[Q] Can't get past boot screen

Hey all,
I was trying to flash CyanogenMod to my phone a couple days ago and I followed the procedures in this guide http://forum.xda-developers.com/showthread.php?t=960323, and this guide http://wiki.cyanogenmod.com/index.php?title=HTC_Incredible:_Full_Update_Guide.
As far as I know I did everything correct up to installing CyanogenMod. I already had done the unrevoked root, as well as install clockwork recovery. I used ROM Manager to update clockwork before trying to install Cyanogen, and then I used ROM manager again to try to install CM. And then it started to do its thing, but when it was done, it had booted straight into what I had before.
What am I doing wrong? I've considered trying to unroot it and start from scratch so to speak but whenever I use recovery or factory reset from the HBOOT it sits at the white "HTC Incredible" screen forever, and then doesn't accomplish anything.
Its bc ur using the newest recovery i assume tge rom u flashed isnt compatible...try going to a 2.x recovery, the new recoveries arent compatible with a lot of roms
Sent from my ADR6300 using XDA App

CDMA VM One V problem flashing custom JB rom

Alright, I've searched and searched and searched and followed several different guides to try to flash a custom Jellybean ROM on my One V (CM10 and AOKP), and three times I've ended up having to run my stock RUU. Unlocking my bootloader wasn't an issue, and after a few tries, flashing a custom recovery and rooting wasn't an issue either. From what I understand, for the primoc One V, the only custom recoveries that are useable CWM Recovery 5.8.x and TWRP2 (CWM Recovery 6 doesn't work for the device). I tried both of these recoveries, CWM with CM10, and TWRP2 with AOKP. Also, each time I booted into recovery, I got the HTC display with the red "this build is for development purposes..." text, but recovery loaded normally.
Here is what I did:
1) Placed rom and gapps zips on root of my sdcard.
2) Backed up
3) Whiped cache and dalvik
4) Whiped data
5) Installed rom zip from sd card
6) Installed gapps zip from sd card
7) Booted into fastboot, and ran "fastboot flash boot boot.img" (where boot.img was either jboot.img in the case of CM, or the boot.img included in the AOKP zip in the case of AOKP)
8) Rebooted
Here's where the problems came. Booting back up the phone just displayed the white HTC screen with the red "this build is for development purposes..." text. Nothing else. So, each time I've had to boot back into fastboot and run my RUU...
I know it's possible for me to flash a custom rom, as the roms exist for my device, but it just isn't working for me . I could really, really use some advice, this is driving me crazy. Thank you.
EDIT: Figured it out, flashed another version of the kernel. Running AOKP Jellybean!! Sorry for the post.
For aokp, go to the thread and download the boot image linked in the op. For CM10, read the whole thread. The are a few issues with flashing and a file you will need to push to the system with adb to get it boot.
Thanks for the reply. I resolved my issue. I just had to flash the correct jelly boot kernel.
Sent from my One V using xda app-developers app
dankstahz said:
Thanks for the reply. I resolved my issue. I just had to flash the correct jelly boot kernel.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I had that issue for a day where i was juggling with three to four different "same" rom/kernel/boot images... you just have to get the right three in a row. Im now trying to remove the ugly red developer text. I loved the CM10 but too many bugs and my texting option on my cell went away I couldnt recieve but i could send. the sd card never mounted right. I found MIUI rom which I am absolutely in love with all features work. But I want to know if you have any success or even attempted hboot editing to remove the red developer text?

Can't get into recovery

Hello,
For some reason lately I cannot boot into recovery. It will boot into the white screen (bootloader?) but keeps loading it when I try to go into recovery. The same thing happens when I try to reboot phone into recovery.
I cannot backup or flash any ROMS now. CWM seems not be be able to backup my current ROM anyway, even when I could boot into recovery a few days ago.
Also, my SD card adapter has failed me and now sometimes when I go to connect with USB to put files onto the card it sometimes does not work and restarts Cyanogenmod. I worked on the last try ok.
I am running Cyanogenmod 7.2.01 and have Rover theme installed.
Please help.
Reflash your recovery. Use 4ext recovery this time. You will find an apk file on 4ext site, just download and install.
Go the application and follow instructions to flash the recovery. It will overwrite the current one.
Sent from my HTC Desire
Ok I flashed recovery from ROM manager again and it's working fine. I still don't know why it didn't work or I needed to flash recovery again, but at least it works now
Centurionmark said:
Ok I flashed recovery from ROM manager again and it's working fine. I still don't know why it didn't work or I needed to flash recovery again, but at least it works now
Click to expand...
Click to collapse
U should use 4ext recovery like dvsk69 suggested, its waay better. And u just flash it using the app, just like u did with rom manager.
Sent from my HTC Desire
RSK Sattelite SuperSense4.1

[Q] Softbrick/bootloop

So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
EgoTrip26 said:
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
Click to expand...
Click to collapse
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
soupysoup said:
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
EgoTrip26 said:
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
Click to expand...
Click to collapse
Just flash recovery then cm rom.
Sent from my SGH-M919 using Tapatalk 2
Thanks a million!
Thanks to both of you for prompt response, Used TWRP and at least got CM to flash and startup, so far so good. hope it works as well on the S2 as it does on my phone!
Thanks again

Categories

Resources