Root Twrp

[scary alien]

I'm using the clockworkmod recovery can i see the error from there? else i would have to install the twrp recovery all over again

By the way, your first image (in the first post) is clearly TWRP custom recovery...I'm guessing you're using two different ones?

Perhaps your issues are because you're using one that is not specific to your device?

 

[Jeezy1]

how do i grab /cache/recovery/last_log and/cache/recovery/last_log.1???

 

[Jeezy1]

I changed it to Cwm as u can see in the photo

 

[scary alien]

how do i grab /cache/recovery/last_log and/cache/recovery/last_log.1???

You're rooted, right?

Use a rooted file explorer like Root Explorer or ES File Manager and make a copy of those file to your SD card and then post them up here.

Or you can use an adb shell and copy them to your SD card and them post them up here:

c:\> adb shell
$ su
# cat /cache/recovery/last_log > /sdcard/last_log.txt
# cat /cache/recovery/last_log.1 > /sdcard/last_log1.txt​

and then post-up the last_log.txt and last_log1.txt files to here.

 

[scary alien]

I changed it to Cwm as u can see in the photo

Is that version of CWM built specifically for your villec2 device?

 

[Jeezy1]

do you mean this? i have no idea where to find it or how sorry i'm not an expect

 

[Jeezy1]

yes it is

 

[scary alien]

Well, that's close enough (it looks like you copied more than just the files, but I think I got what I needed).

So, this is really odd...it looks like you've got two different device information fields listed below that disagree what you posted previously for the Device Info app's output:

ro.build.description=full_VilleC-eng 4.0.4 IMM76L eng.root.20120704.222400 test-keys
ro.build.display.id=full_VilleC-eng 4.0.4 IMM76L eng.root.20120704.222400 test-keys
ro.build.fingerprint=Android/full_VilleC/VilleC:4.0.4/IMM76L/eng.root.20120704.222400:eng/test-keys
ro.build.product=VilleC
ro.cm.device=VilleC
ro.hardware=villec2
ro.product.board=VilleC
ro.product.device=VilleC
ro.product.name=full_VilleC​

I'm guessing that the values above are because the version of ClockworkMod recovery you're using is built for the VilleC version and you actually have the villec2 version (the values above would be what the kernel that CWM uses / was built for). That would explain why you're getting the flashing errors because the ro.build.product and ro.product.device values don't match the ROM you're trying to install).

So, it looks like you don't have a version of CWM that is built specifically for your villec2 device.

So, you need to make sure you definitely have a villec2 version of your custom recovery.

This page, http://forum.xda-developers.com/showthread.php?t=1927165, looks like it references this download for a version of TWRP built for your device:

http://techerrata.com/file/twrp2/villec/openrecovery-twrp-2.2.1-villec2.img​

So, try installing and using that custom recovery instead of the one you currently have.

 

[Jeezy1]

ok i just did that now....so what next?

 

[scary alien]

ok i just did that now....so what next?

Try to flash the ROM that you were wanting to install...

I'd advise you to take a Nandroid backup first, of course...and read and follow all of the installation instructions from the ROM dev's thread for how to flash the ROM.

 

[Jeezy1]

Ok so i flashed a Rom i'llput up and it stuck on the lod screen!!

 

[scary alien]

Some ROMs take 5 - 10 - 15 minutes to do their initial setup, etc...so don't be too hasty.

Also, make sure you did all of the wipes suggested by the ROM dev in the thread where you got the ROM from.

It sounds like you're past the initial flashing issue and now it's just a matter to fine-tuning your flashing process (i.e., again from the ROM dev's thread's instructions).

 

[Jeezy1]

it is past the 15 minute mark now and is still stuck in the boot screen...

 

[scary alien]

1. Did you make a Nandroid backup before you began?

2. Did you do any of the wipes instructed by the installation page?

I kind of feel like we're having a one-sided conversation where I'm having to guess at all of the things you might or might not have done...

edit: also, I believe you have to install / flash the gapps (Google apps) package separately when you install CyanogenMod...

 

[Jeezy1]

sorry about that. i went through all the procedures and flashed everything but the gapps was not installing which i think is not much of a big deal right? (maybe i downloaded a wrong one and can easily replace it). I have just restored back to my old rom. its hard to find any new rom to flash for my phone now...

 

[scary alien]

You should only need the gapps package if you're doing to download apps from the Play Store.

Bear in mind that the following link is the page for the ville device and not specifically your villec2 device, so this is just for guideline purposes only--you'll have to identify the places where things are device-dependent:

https://wiki.cyanogenmod.org/w/Install_CM_for_ville​

At the bottom of the page is the Installing CyanogenMod from recovery instructions where step #7 says "Select Wipe and then Factory Reset." so have a careful read through and make sure you don't skip this step.

Otherwise, I think you might want to make a new thread here in the root area (now that your past the issue with actually flashing from custom recovery) so that the folks familiar with your HTC One S can guide you best.

 

[Jeezy1]

Man i messed up i used fastboot to flash the boot img into the phone and forgot to backup. Now i have flashed the ROM successfully onto my phone but can't use my usb and can't you wifi and since the backup went bad i can't go back to my old ROM. :'(

 

[DaisFlaque]

All hope is not lost my friend. If you still have a recovery installed you can save the device and come out on top.
Check this modified stock with root and see if flashing it will solve problems. I have ran into same problems on my device.. flashing a modded stock seems to fix loads of issues like these.
Link...http://forum.xda-developers.com/showthread.php?t=2374476

 

[Jeezy1]

@scary alien Thank you so much for your help you are heaven sent! android forums is definitely the best! although i had problems i managed to flash back my stock ROM i think i should get a new phone. A less sophisticated one which will be easy to flash a custom ROM onto. @DaisFlaque managed to flash 'firm.zip' in flashboot now i'm back to my stock ROM i think i'll keep that...for now. Thanks guys!!

 

[DaisFlaque]

Happiness is making others happy to me. :')