Related
Hello all.
I have a t-mobile g2, currently S-OFF, which is sitting in hboot/fastboot right now. I will not boot past the HTC screen.
I attained root last night using this method, and it worked without problems. I then gave a few apps (terminal and shark, to be precise) superuser access. Went to sleep.
This morning, I wanted to delete some apps and change some system fonts around (wanted to use the ubuntu font instead of droidsans). deleted photobucket at amazon mp3. while trying to change the fonts, I changed permissions on the /system/ folder to 777 (chmod 777 /system/). Changing the fonts wasn't working out, so i decided to leave it alone and just reboot my device. upon reboot, it would no longer boot past the htc boot screen. It will, however, go into hboot/fastboot mode without a problem. I tried going into recovery mode and using the update.zip (e4aaacea73af.OTA_Vision_TMUS_1.22.531.8-1.1.19.531.1_release_signed.zip renamed). No luck. Also, i tried researching on the forums and using adb to try to unbrick, but adb doesn't recognize any device being plugged in. fastboot did work, though, and i wrote the original recovery.img file into the phone (although I don't know where it goes when this is done...) and now I don't know where to go next. any help?
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Vandale said:
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I had stock android that came with the phone, I just got it about a week ago. Is there any way to find the standard/stock android rom for the g2? if anyone could link it and let me know how to flash it, that would be amazing.
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
consciousdawn said:
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
Click to expand...
Click to collapse
Which one did you download? The first few on there were pre-release ROMs. The 1.19.531.1 ROM was the release ROM originally. Most recent G2's come with 1.22 (the OTA update) pre-installed, which we do not currently have a PC10IMG.zip for. If your G2 had 1.22 (e.g., you already had wifi-calling and tethering), you won't be able to use the 1.19 PC10IMG unless you used gfree to obtain S-OFF. If you did not (i.e., you only flashed the engineering HBOOT), you should not try to flash this file (it will replace your HBOOT with the shipping version and then quit mid-flash because it sees you already have a higher version installed). Even if you did obtain S-OFF with gfree, flashing this file will cause you to lose your engineering HBOOT and root (though you will still have S-OFF, so it's easy to re-root).
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
ianmcquinn said:
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
Click to expand...
Click to collapse
Do you mean this thread? I have been trying to follow along and it's a bit confusing (although I feel that's due largely in part to grammatical/usage errors). what you are saying does help a lot though. I just need to learn how to install Clockworkmod Recovery through fastboot. *googles away* in the meantime, feel free to link me to another thread which helps me do this. Thanks a million.
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
consciousdawn said:
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
Click to expand...
Click to collapse
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
That's exactly what happened, and no, not at all. It said it flashed successfully. Maybe I don't have the correct version of Clockworkmod? If you could please link me to a good one, that would be great.
UPDATE!!
So I found an official clockworkmod 2.5.1.2, and now when I boot into recovery, it shows the HTC logo and then goes to clockworkmod. This is amazing. Thank you guys for all your help, I have learned something new today.
Now, can someone explain the difference between odexed and deodexed? please? lol.
ianmcquinn said:
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
Click to expand...
Click to collapse
Looks like I cried victory too quickly. While I do get the menu for clockworkmod (every time I boot, for that matter), every time I issue a command, such as reboot now, or install from SDcard, and even advanced, the screen goes black. GRRR, WHAT AM I DOING WRONG? I've been at this since about 1 today T_T
Just wanted to say that I'm the biggest noob on the planet. While I did upgrade to cwm 3.0.0.5, i didn't know it allowed the use of the main controls. I got my phone up and running now. Thank you for all the help. Good night :]
Unlocked my bootloader...check
Rooted my Arc...check
Downloaded the latest CM7 from Cyanogenmod...check
Fastboot boot.img...check
Wiped cache, user data...check
Install update.zip from SDcard...check
Boot, and I'm stuck. The CM7 loader shows up, I see the unlock screen for about 2 seconds and then the CM7 loader comes back. Over and over and over again. I've tried completely wiping and starting from scratch but that's not working. I've tried both the latest stable release and the latest nightly. I read elsewhere on an EVO 4G thread that someone had a similar issue but the fixes they suggested aren't flying.
I am relatively new so please don't make too many assumptions as to my understanding. Speak slowly and use little words. Hand gestures help.
What kernel are you using and which firmware were you on before you flashed cm7?
sinkster©
The kernel was something.something.56, I believe. (or was that the firmware?)
I'm sort of stuck in this place and I can't get out. I suppose if push came to shove I could find those posts about putting my phone back into its stock state. But I'd rather not. The stock Sony experience was terrible.
Firmwares ok then, did you use the kernel in the cm7 zip or from DoomLord (i.e. fastboot flash boot boot.img)?
sinkster©
I first tried the boot.img from Doomlord (v15). But that wouldn't even get to the home screen so then I tried boot.img from the cm7 zip.
i have same problem
Best idea is to start from scratch. Check fxp thread for anyone else having issues too.
sinkster©
freicook said:
I first tried the boot.img from Doomlord (v15). But that wouldn't even get to the home screen so then I tried boot.img from the cm7 zip.
Click to expand...
Click to collapse
You have to use Doom's CM7 kernel on CM7, not the one for SE's ROM.
Sent from my iPad 2 using Tapatalk
keep getting random reboots anyone know why?
Resolved
OK, this has been quite a journey but I was able to get CM7 working.
1st, I had to put the phone back into a stock state, like I just got it from Sony. My phone was unbranded and not from a carrier so this wasn't too hard. But I can't even sort of retrace the steps I took to get it back to the stock version of the SE Xperia Arc software. I never strayed from XDA so all of the answers are here, but what a rabbit hole that was.
2nd, the "latest stable release" on the CM7 site that I linked to in my original post is, in fact, completely unstable. Random reboots, stuck at the loading animation, etc. You need to use version 7.1.0.1 instead. Download that version, flash the boot.img that's contained within that zip and then update in fastboot to the 7.1.0.1 update.zip
This took far too long to figure out but I was able to get the thing running. And it looks so much better than Sony's terrible UI. What on Earth were they thinking?
If you downloaded CM7 on Cyanogenmod websites, I think you have to delete anthalservice.apk or something. It is located in /system/app/ or /data/, can't remember correctly.
OK, here it goes.
I have a R800x CDMA Verizon Xperia Play
I had bootloader unlocked successfully by alejandrissimo.
I am rooted.
Today I decided to try the MIUI rom for CDMA.
It required custom kernel, and recommended Kieren's darkforest kernel.
I installed that kernel via fastboot with no problems.
Upon turning on phone, i get a page that says Sony, then I get ANDROID page.
Then it just stays on ANDROID. I can tell that it is not frozen because I can see the waving lines going across.
SO, I decided to just go back to stock kernel then try again.
BUT, I cannot get into fastboot!!
I hold search while connecting usb, and the led blinks blue once, then continues with boot.
I am at a loss.
I Can get into CWM.
Please Help!
Edit: I just noticed that after holding search then plugging in USB, the light blinks blue once. Then about 25 seconds later, the light turns solid blue for about 3 seconds. Then just to orange for charging. During this time, I can not get fastboot to recognize device, nor does my computer recognize any devices.
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
netizenmt said:
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
Click to expand...
Click to collapse
ok, small problem with that.
when I click to install flashtool, it tells me that it is not available for my region (Central USA).
I do have a nandroid and titanium backups made just before flashing.
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
still stuck
netizenmt said:
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
Click to expand...
Click to collapse
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
zeeky120 said:
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
Click to expand...
Click to collapse
Yeah, that seems to be the wrong boot.img. It should be called boot-v2.img.
EDIT: WOW - I just reread your post after posting mine and realized I pointed you to the same spot!
Try this ROM which is a version of CM9 that Chevyowner got working for our R800x. I know it works because I'm using it. http://www.mediafire.com/?1xnh54i6lvnnh73
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
zeeky120 said:
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
Click to expand...
Click to collapse
just an fyi, you can name kernels whatever you feel like (I'm not sure about spaces, I use linux, so I never have spaces in names anyways )
Sent from my R800x using Tapatalk
Flashing now
OK, I just downloaded and flashed the ROM about 3 minutes ago.
I cleared everything just like you told me to.
It installed with no errors.
You may be right about long boot times for first boot, otherwise I have a really bad kernel.
It has just sat on Sony screen for the past 10 minutes.
It hasn't even went on to the android page that I got before.
Hoping that it will Work.
Assuming that it doesn't, what would be my best next move?
Can I flash a kernel (Such as doom_lord's CDMA Kernel) via clockwork?
I think I saw a video about it for the Samsung fascinate, however I seem to recall something about needing an s2 file or something??
I will update as soon as I get something. (hopefully good news)
Update: It has been about 20 minutes now and still on Sony screen.
Now it has been 30, im starting to get worried. Should I plug in? Should I just let it be? Should I let it die? Should I battery pull?
Major Edit: I got impatient and just battery pulled. I then tried to get into CWM, but failed. THen I got a bright Idea, why not try fastboot with the new rom. IT WORKED. I WILL NOW TRY TO FLASH A NEW KERNEL AND SEE IF THAT HELPS.
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
chevyowner said:
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
Click to expand...
Click to collapse
is this your kernel, or someone else's? If it's yours/you have a working copy, could you post an md5 so the op can double check it?
Sent from my R800x using Tapatalk
nope not my kernel, and i doubt i have an original working copy as i added 2 lines so i could mount my sdext partition.
Finally!
OK, I am now back up and running.
I went through every kernel and rom for CDMA play, and got nowhere.
I ended up getting Doom's kernel to run. It worked, and booted to android... Then stayed at android.
Then I decided to flash my nandroid i made, and am now working on stock rom W/ DoomKernel.
The ROM seems to be lagging a lot.
Since everything is *working* now, what kernel/ROM combo can anyone verify working for the Play R800x CDMA.
I would really like CM9 or ICS based roms.
Thanks for your help getting me out of this mess!!
EDIT: Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
If you're using keiran (darkforest) cm9 kernel the md5sum for it should be: 74a5be2bf95322b8c45780d9daeda4fa
Sent from my R800x using Tapatalk
zeeky120 said:
Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
Click to expand...
Click to collapse
This site has some of the stock FTFs, just extract the kernel.sin from the R800x one http://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html
kernel.sin: http://www.mediafire.com/?e29j13d9wpgdvoj
md5sum: 45116201967408d70895ef63c500ed1e
@zeeky120 - I'm sorry you're having so many problems. For me when everything seemed hosed, I started over by using Flashtool and flashing the ftf file I gave you links for. Then once it came back up as stock, I started again from scratch. Depending on what your goals are, you need to flash the proper kernel for that. Then get into CWM. Clear DATA, CACHE, DALVIK CACHE before you do anything else. Then load via zip file the rom you want to install, making sure it matches the kernel you loaded. And, whether necessary or not, I always wipe the big 3 again, just in case. (Call me paranoid, but it helps! )
Ok now up and running on stock everything working great just like out of box. The only thing I have done so far is to root. I want to do it right this time. I would like to flash cm9 based miui for r 800x. Could anyone provide detailed step by step instructions and links for download. Thanks in advance.
Sent from my R800x using xda premium
Closing Notes
This thread has reached its end, because my problem has been fully solved. Advice to future users, always clear the big three, and when in doubt: use flashtool to reboot the ftf. Right now I am up and running on CM9 (use the link in Chevy's signature to download. I can verify that it works great on CDMA. (faster download speeds than stock!!!) Thanks for everyone for all of their help, and I hope to be contributing to development in the near future.
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Did you do a full wipe ???
ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).
Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.
ok guys i have htc one x and my nephew just got a wildfire s and tried to root and rom it.
so heres where im at. ive flashed this rom but im stuck at the htc logo.
he installed the latest CWM for this phone 5.0.2.8. then full wipe and installed a few roms but none worked and then i got here.
with my one x i have to flash boot.img but as far as i can see thats not the issue here??
can anyone help?
It's a gsm wfs with a sim slot. I'm assuming the next step is to install the correct RUU for the phone right?
the phone is stuck at the htc logo
Can someone possibly point me to the correct RUU? Its a UK phone that was on Tesco/o2 mobile and I cant find the right RUU.
Any help is greatly appreciated
Nothing??
Sent from my HTC One X using Tapatalk 4
Seriously no help at all????
Sent from my HTC One X using Tapatalk 4
Oh well
Sent from my HTC One X using Tapatalk 4
So I get told of four posting in a rom thread and get told to post here and I get zero help. Ffs
Sent from my HTC One X using Tapatalk 4
Usually when you're stuck on the HTC logo it's because the ROM you are trying to flash also needs the kernel flashed, which you have to be S-off to do and the developer you got the ROM(s) from should have provided it. You were very general, but I presume a full wipe was cache, dalvik-cache, data/factory reset, and (optional), battery stats? Are you just plain stuck, can't do a factory reset and/or didn't make a backup before trying the ROMs? I was going to flash this ROM at one time and he gives some pretty good instructions to follow...sounds like it might work for you. Better than staring at the HTC logo, eh?!
http://forum.xda-developers.com/sho...ht=what+files+can+i+remove+from+my+wildfire+s
Thanks for the reply. I can get to recovery but I can't install anything as recovery can't seem to find the internal storage.
Sent from my HTC One X using Tapatalk 4
Most recoveries are going to look on the external storage, the actual sd card. Can you move your ROM to that and give it a try? Just to save time, I'll say I'm figurin' the sd card is formatted (FAT 32) and if there's a problem seeing that you might have to go into, "Mounts and Storage" and mount the sd card. I'm in the middle of a movie and will get back after, if you have another question I can help with. Hope it works.
ok so i finally got CWM to see the sdcard and i installed a rom and flashed the boot.img.
now the phone just reboots into recovery. what the hell is wrong with this dam phone????!?!?!
So far we've been successful with the, "One step back and two steps forward" approach so:
You extracted the boot.img file from the ROM zip to your PC for use after and then installed the ROM, rebooted the phone into recovery>>fastboot, hooked up to the PC in a command prompt and changed directory to where you have the boot.img and the adb/fastboot command files and at the command prompt typed: fastboot flash boot boot.img
Typically you would then type: fastboot erase cache, or back in recovery wipe the cache and reboot to find the ROM (slowly) booting for the 1st time.
I'm a one step at a time person (so I know what worked). So if all that's true, and it's still stuck in a recovery loop then I'd try wiping cache again and dalvik-cache and rebooting.
If that doesn't work I'd suggest one of two things:
1. Start over and I don't mean at htcdev, but wiping cache, dalvik, and data...install ROM, flash boot.img, wipe cache reboot...or
2. We can go over all the steps (as briefly as possible for both our sakes) and I'll say why: one time I was writing a macro and it just wouldn't work, after 3 days of spending too much time on it each day I asked someone else to look at it and he found I had missed a slash or used a comma instead of a semi-colon or some one simple thing. So it wouldn't hurt to see if there was one little thing skipped.
Lastly for now - if you post again, whatever you post, just for my curiosity tell me which (compatible with the Wildfire S) ROM your wanting to use.
First of all I just want to thank you for trying to help.
I did those steps perfectly and they've always worked with my HTC one x but no dice with this wildfire.
http://forum.xda-developers.com/showthread.php?t=2206780
That's the ROM I'm trying to get to boot.
I really want to fix this phone for my nephew but its not looking good.
Sent from my Nexus 7 using Tapatalk 2
I know how it is...we all get fixed on wanting one thing and then intent on making it work.
I did a quick look at the page for your intended ROM and first thought, aha...in the instructions to install, the wipe file he provides seems to indicate for a marvelc in the name, so does it wipe all it should on a gsm WFS; but, then he's got that link to the ROM for a marvel c(dma); anyway I did a quick search of the thread (there are 119 pages!) for, "Reboots into recovery" and found this (among others):
http://forum.xda-developers.com/showthread.php?t=2206780&highlight=reboots+into+recovery&page=102
I do see where there was a rebooting into recovery problem with this ROM and a fix was applied in July 2013. I think the link above is to the, "fixed" ROM (hopefully for GSM WFS) but I'm not going to claim that as fact; again, I just took a quick look between my morning news readings and did not read around the problem or, about Lizards patch.
We could go deeper like formatting partitions, but since he has provided a wipe script and there's so much info there...well, I'm not dumping you, but I am thinking researching there might get you more specific results since we've pretty much been going through the generic version of flashing ROMS. What do you think?
ok i read the entire thread and flashed all the fixes etc but no dice. however i did flash a different rom altogether and now everything seems to be working fine!!!!!
dont know why that never occurred to me before!
i must say thank you for all your help. it is very much appreciated
now for some strange reason the original rom now works !!!!!!!!!
For as long as I"ve been fooling around with electronic devices, it often still just seems like, "PFM" sometimes; and, I don't know how many times I've done the right thing over and over and over and then just given up and set it aside only to pick it up again a day or two later and then everything goes like it should...and not doing anything different!
I'm glad you got everything going again, and I'm sure you just want to get back to enjoying it, but I'm curious to know (along with anyone else that might be following) what ROM finally worked, and then you ended up going back to which, "Original" ROM, stock?
I hear you on that. So many times I've had to work on systems for hours then magically I'll do something and it works.
What I did was flash another custom ROM which was unofficial cm10.2 it's on the main page made by owl. That booted up fine but I wasn't happy with that ROM so I flashed the one that I've been trying to flash, marvellous cm10, the one you helped me with.
The only thing I did differently was flash the boot. IMG after I flashed the ROM , I usually flash the boot image first on my one x.
And that's about it.
Sent from my Nexus 7 using Tapatalk 4
I clicked a thanks (and thank you for yours). I enjoyed the exchange and glad you've got it going. The Wildfire S is a great phone, especially for me (although I have my SIM in another phone now) and hopefully your nephew, because it needs to be managed, tuned, tweaked, etc. which is what I love to do and hopefully your nephew will too and keep at it now that you got him off to a good start.
good start yes, but i have to fix the mistakes!! lol
Do you know where u can get int2ext?
Sent from my HTC One X using Tapatalk 4
You caught me right at the end of a movie I was watching!
I've always been happy with Link2SD, but you can't beat moving all of data to SD.
Try this:
http://forum.xda-developers.com/showthread.php?t=1716124
also, this is an easy way to get init.d if you don't have that...I think it's needed for int2ext:
http://forum.xda-developers.com/showthread.php?t=1710980
Have fun!