today i rooted my htc wildfire s....i installed cm 7 rom from rom manager ..and installed gapps ..and rebooted ...but it says "touch the android to begin" when i touch nothing happens .....i cannot skip the steps too very sad pls help me
Don't use rom manager, flash the CM7 rom in the WFS Android Developement section.. CM7 isn't officially supported for WFS so I don't know wich version you installed but that may be the reason why touch isn't working
i installed cyanogenmod 7 7.2.0-rco.....pls tell me which the best supported rom wfs other than cm
juniorwebdevs.co.uk/nightlys/
Flash the latest nightly from above. Boot up. Then reboot and flash gapps and it should be fine.
CM7 works a treat.
Scott
ty very much scoot it worked in g1 and wfs .....i talked with all senior members they didnt give me correct cm7 version ty .....its working like charm
Related
I am a new user to the forums and I couldn't post this to the Development section yet.
I did not first ROM install with the Revolution 7.2 I tried us Bricked 3.0 but I got bootloop.
I switched to the Standard Rom for Revolution HD and now everything is working. However when trying to use a different kernel Bricked I get the Bootloop again.
Is this a problem with 7.2 or with the Kernel? Not sure I would like the Swipe to acess instead having to hit the on button all the time. Is it possible to get this without installing the Bricked Kernel?
Thanks
EdwardLotz said:
I am a new user to the forums and I couldn't post this to the Development section yet.
I did not first ROM install with the Revolution 7.2 I tried us Bricked 3.0 but I got bootloop.
I switched to the Standard Rom for Revolution HD and now everything is working. However when trying to use a different kernel Bricked I get the Bootloop again.
Is this a problem with 7.2 or with the Kernel? Not sure I would like the Swipe to acess instead having to hit the on button all the time. Is it possible to get this without installing the Bricked Kernel?
Thanks
Click to expand...
Click to collapse
have you installed the repacked one? and try fastboot erase cache?
EdwardLotz said:
I am a new user to the forums and I couldn't post this to the Development section yet.
I did not first ROM install with the Revolution 7.2 I tried us Bricked 3.0 but I got bootloop.
I switched to the Standard Rom for Revolution HD and now everything is working. However when trying to use a different kernel Bricked I get the Bootloop again.
Is this a problem with 7.2 or with the Kernel? Not sure I would like the Swipe to acess instead having to hit the on button all the time. Is it possible to get this without installing the Bricked Kernel?
Thanks
Click to expand...
Click to collapse
Search for the "repacked kernel for ARHD Rom" thread in the dev forum. You will find all kernels there... I bet there is one with s2w too. But it's not working well for me... Swipe for 2-3 times till the phone wakes up is annoying...
Gesendet von meinem HTC One X
One-X-master said:
have you installed the repacked one? and try fastboot erase cache?
Click to expand...
Click to collapse
I downloaded v.0.3.
Is this not the correct one?
I got the link form the Revolution HD forum under kernels. There was also abeta v0.35 but I didn't use that one. It said it was repacked.
I did erase cache.
I see a v 0.21 that says repacked should I use that. Since I am on the latest build of android 4.0.4 I didn't want to flash an older core.
Thanks
EdwardLotz said:
I downloaded v.0.3.
Is this not the correct one?
I got the link form the Revolution HD forum under kernels. There was also abeta v0.35 but I didn't use that one. It said it was repacked.
I did erase cache.
I see a v 0.21 that says repacked should I use that. Since I am on the latest build of android 4.0.4 I didn't want to flash an older core.
Thanks
Click to expand...
Click to collapse
try another repacked kernel because bricked is outdated and franco and faux's kernels are better or the stock kernel....
To whom it may concern,
since a view weeks, i am proudly new user of a htc desire (yes the old classic smartphone). So the old android 2.x is not that cool, and I was looking after a good ROM.
First I used the Spazedog ICS ROM [1]. It was "nice", but then i found the ParanoidAndroid ROM [2]. So i installed the version 2.22 and i was happy. There was only a problem with gps, so i installed the "INT2EXT+ GPS Testing Copy" [3] Skript over already installed "INT2EXT4+". But that not solve the Problem. Then the Version 2.50 from PA was released (23OKT).
And now my problem: since i installed this ROM it doesn't boot with the PA ROM (both 2.22 and 2.50).
The SpazeDog ROM and a CyanogenMod are booting without problems.
Can anybody help me please, because i really want to use the ParanoidAndroid.
Thank you
PS: I used this links:
[1] http://forum.xda-developers.com/showthread.php?t=1813745
[2] http://forum.xda-developers.com/showthread.php?t=1912187
[3] http://forum.xda-developers.com/showthread.php?t=1716124
Hello,
since nobody can help me, i fixed it.
i had to format the second and third partition on the sd card and then i reinstalled it and now it boots again.
...
Upon finally achieving s-off on my phone, one of the ROMs I've wanted to run was tge MIUI. well it worked on the first try after rooting but boot looped when i had to reboot it. Reflashed it again and it happened again. Can anyone help?
Sent from my rooted incredible 2
Which version of MIUI is it?
I just had this same problem with ICS] Unofficial Multilang MIUI4 - v 2.12.21 Rom
I realized that i was still using the way outdated radio which my phone bootlooped as soon as MIUI tried to load it.
alot of these newer ICS/JB roms require you to update to the new ICS radio 1.09.01.0320
I installed the new radio and it works great! I can reboot all i want.
I used this one on Team venoms Roms thread
http://forum.xda-developers.com/showthread.php?t=1953899
here is another place to get it with inctructions on how to install it
http://forum.xda-developers.com/showthread.php?t=1134451
hope this helps
Thanks! I'll be trying this soon
Hello, i have rooted wildfire s (im 2012 wildfire s user) with s-on. My phone have cwm 5.0.2.8. I was try to to install this custom roms:
CyanogenMod 10: http://forum.xda-developers.com/showthread.php?t=1861623
[ROM][Unofficial][4.1.2] CyanogenMod 10 Nightlies for the Wildfire S: http://forum.xda-developers.com/showthread.php?t=2022331
and m1ndh4h0rz rom (i couldn´t find link on this forum)
I was try delete dalvik cache and all things in recovery menu with delete attribute
So my problem is that when i was try to install these roms in recovery it will all end with status 7 error. So i try the “updater-script” file trick (this: http://www.androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html). Then the cwm say that rom is installed but when i restart mobile it will show only white htc logo and no boot. Next i was flash this stock rom: (http://forum.xda-developers.com/showthread.php?t=1757585) because phone wont start (htc white logo when start phone and nothing).
Now im on this stock rom and my question is how i can install custom roms with no status 7 error. (cyanogen mod 10 rom)
And sorry for my poor english
Thanks for all answers
I have t same issue
Sent from my HTC Desire using xda app-developers app
adic222 said:
Hello, i have rooted wildfire s (im 2012 wildfire s user) with s-on. My phone have cwm 5.0.2.8. I was try to to install this custom roms:
CyanogenMod 10: http://forum.xda-developers.com/showthread.php?t=1861623
[ROM][Unofficial][4.1.2] CyanogenMod 10 Nightlies for the Wildfire S: http://forum.xda-developers.com/showthread.php?t=2022331
and m1ndh4h0rz rom (i couldn´t find link on this forum)
I was try delete dalvik cache and all things in recovery menu with delete attribute
So my problem is that when i was try to install these roms in recovery it will all end with status 7 error. So i try the “updater-script” file trick (this: http://www.androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html). Then the cwm say that rom is installed but when i restart mobile it will show only white htc logo and no boot. Next i was flash this stock rom: (http://forum.xda-developers.com/showthread.php?t=1757585) because phone wont start (htc white logo when start phone and nothing).
Now im on this stock rom and my question is how i can install custom roms with no status 7 error. (cyanogen mod 10 rom)
And sorry for my poor english
Thanks for all answers
Click to expand...
Click to collapse
Try out Jelly King 2.0, it has a kernel which supports 2012 Wildfire S's. Its based on CM10 and minor bugs have been fixed for a pretty much stable ROM. The only issue is battery life.
Or if you want to try out CM7, there's a kernel for your phone in the any wfs user interested thread. I'll post a link in a minute.
Edit: http://forum.xda-developers.com/showthread.php?t=2094869
Sent from my HTC Wildfire™ S powered by Jelly King®
"My name is Win. And if you are reading this, you have been defeated."
[HELP THREAD] Official Wildfire S Help Thread!
hi all just tried to update my cer iconia a700 with cyanogenmod cm 10.1 anyways download it to tablet installed clockwork recovery as well as downloading gapps clicke on mod file and it opened clockwork and i clicked install to install mod/update and now just boots to cyanogenmod on load screen and just sits ther for hours like its loading but nothing happening how to i get back to old rom or even carry on with update i was on 4.1 jb tried to update to 4.2 and yes its rooted sry i am a noob to this thanks in advance
Hello smedzz.
Your device only has experimental and nightlies for Cyanogenmod, with no RC or stable ROMs available. The problem you are experiencing sounds a lot like the problem I had with Cyanogenmod 9.0 for my Samsung Galaxy S i9000. It was a release Candidate (RC), and slightly unstable, and hung up on the boot graphic occasionally. The only way to fix it was to flash the phone again (my experience).
If that sounds like a pain, you could look for a different ROM in the Developer section of the forums for the a700. The "iconiaN 2.6" ROM, based on Jelly Bean 4.1.1, sounds good. At least it would get your tablet working again.
http://forum.xda-developers.com/showthread.php?t=1952124
Already solved?
Did you wipe?