I changed my build prop like the other thread said so I could play Nova 2. Now my TP wont reboot. I had to hold power and home down otherwise it just hangs after cyangenmod loading screen. I can boot in webos but not cm. What gives?
thegameksk said:
I changed my build prop like the other thread said so I could play Nova 2. Now my TP wont reboot. I had to hold power and home down otherwise it just hangs after cyangenmod loading screen. I can boot in webos but not cm. What gives?
Click to expand...
Click to collapse
Happened to me too. I think it is a bug with alpha 2. I had to restore a back up of alpha 1 in recovery to get back to cm7. It would not simply let me install an alpha zip cause it would also boot loop. Restoring alpha 1 was only thing that worked and then I could update to alpha 2.
Sent from my HP Touchpad using xda premium
That's why you always keep a nandroid....
Sent from my Android powered Tenderloin
I have a backup and I fixed the problem. Just trying to see if there is anyway to play games that need a change in build prop or do I have to wait for the next update?
Had the same issue which I fixed via the Clockwork Mod recovery console fix permissions option. Eventually re-installed alpha 2.1 due to some other issues but this time editted the build.prop file without deleting the build.prop.bak file and am having much better results getting some of the 3d games working which so far are Modern Combat 2, NOVA2, Quake3Droid, found this thread quite helpful:
http://rootzwiki.com/topic/7709-gameloft-compatibility-thread-with-working-version-s/
Related
Hi guys,
I am new to the XDA forums so forgive me if this is really stupid or if someone has posted the same problems. I searched for an answer but couldn't seem to find someone with my problem. Forgive me if this is long. I just want to make sure you guys know all the details so we can figure out what went wrong.
I recently flashed the Evil Fascination 3.6 Rom from a modified stock version of ED04 (debloated/debinged). I believe that my version of CWM recovery was 2.5.1 or something like that (w/ voodoo lagfix). I am pretty new to the Android world but I do believe I did everything correctly. I wiped Cache and Dalvik Cache and Data multiple times and made nandroid backups etc.
I flashed the Rom with no problems and everything worked just fine. I was trying out Regina 3D launcher at the time (I regularly use Launcher Pro), and for some reason it seemed a little slow to load up (I figured it had to do with it being the first time with the new rom). I kept having loadup problems with the launcher so I uninstalled it and went back to Launcher Pro. Launcher Pro even seemed like it was acting weird but I didn't take much notice to it.
Now yesterday I downloaded the OTB 1.6 Touchwiz kernel. Everything I've read said it was compatable with Evil Fascination. I tried to flash it from CWM recovery and it didn't work. My phone stayed stuck on the Evil Fascination boot up screen and finally I just popped the battery out. I went back into CWM and just wiped everything and reflashed Evil Fascination. It seemed to work fine with Launcher Pro (again a little glitchy at times, but I took no notice really).
I again tried to flash the OTB 1.6 kernel. This time instead of doing it from the recovery I downloaded an app called SGS kernel flasher. I did what it said and it flashed the kernel for me with no boot up problems like CWM did. I rebooted and then booted into CWM to check it and it was changed from version 2.5.1 (voodoo) to 3.2.0.0.otb. I figured this meant that the kernel flash was sucessful. I went to reboot my phone and when the home screen came on it was a froyo style launcher with only 2 or three icons on the page. I pressed the app drawer and none of my apps showed up that were on my sd card. finally i pressed the home button and it asked for which launcher to choose : LauncherPro or the default and I chose LauncherPro. My regular setup appeared and my apps were in the app drawer. I found it weird that my apps showed in LauncherPro but not in the default launcher.
Now with doing phone reboots my phone always goes to the default launcher with no apps from my sd card and I have to wait to press the home button for LauncherPro to appear. I set it as my default launcher but it never loads when my phone is rebooted.
I was just recently (within the last hour) doing regular things on my phone (texting, internet , email etc) ad all of a sudden I got the shut down boot animation from my rom and my phone turned off. I went to turn it back on and my phone stayed stuck on the boot screen again. Now you can figure what I did again. I went through and did everything over and reloaded the rom and kernel. I am still having the same problems with the launcher as I did before and I have no idea whats going on. I just want to avoid going through this again. Anyone have any idea what the heck is going on???
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
I'm also no expert but after running into constant force closes and random problems with launcherpro I decided to go with go launcher and its been a great switch for me.
Sent from my SCH-I500 using XDA Premium App
Hey guys, still no luck. I don't know what it is. I wish I knew more about hacking and doing all this kind of stuff
Try flashing a PBJ kernel!
can you get into CWM with the three finger salute?
[hold down the two volume buttons and the power until your phone reboots and you see samsung then let go]
See if you can mount as usb to get the kernel on there, if that doesnt work go to staples get a microsd card reader [under $15] and toss the pbj on your card then flash that.
When i was on EF and Comm Rom my phone didnt like the OTB kernels
Good Luck!
My recovery menu works fine and I can boot into it from the ROM without problem. My problem is that when I reboot the phone the ROM's default launcher is setup (and it is missing all of my apps) even though I set Launcher Pro as my default. I have to reset all my defaults in Launcher Pro every time my phone is turned off or rebooted. I would be on PB&J but I like to overclock my phone and PB&J doesn't support voltage control and I don't want to pay for and overclocking app.
efan450 said:
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
From what I've read many people have disagreements on whether 2.5 supports Edify or not....because a lot of people have success with it while others don't so I really don't know. Its never given me problems in the past. I actually had more problems with 3.X recoveries (It wouldn't allow me to make nandroid backups and other things that were essential) so I flashed 2.5 and it worked perfect (again I've read about people having the same problems with 3.0 versions of CWM).
Okay what I've found is that this has nothing to do with Launcher Pro. I downloaded He Launcher and when I reboot my phone everytime it asks me to pick a default launcher. And when I'm using He Launcher, none of the apps on my SD card show up in the app drawer (they don't show up in the default ROM launcher either, they only show up in launcher pro)
Efan450 I tried what you said and it worked! I odined a 3.X recovery and wiped everything oof my phone then flashed the ROM and kernel and everything is working perfectly now. Thank you very much!!!
Forgive me if missed this, but I'm finally getting mine from HP tomorrow, and I think I'll hold off on CM until some of the major bugs are worked out, but I still want to play with WebOS.
--
Sent from my Droid Bionic.
You can still install the cyanogen mod alpha with the update, it doesn't change anything as far as that goes. If you have the alpha installed already, you'll have to rerun the command to install it again, but it still works with the update.
You will have to install only moboot not everything.
Update first and then install CM7. I did this and can confirm that it works.
rootnik said:
Update first and then install CM7. I did this and can confirm that it works.
Click to expand...
Click to collapse
+1 ... Just did a co-workers TouchPad today and CM7 installed smoothly.
Side note: 3.0.4 is in fact really "snappy", I like the updated camera app and no lag on the stock kernal.
Woke up this morning, unplugged my touchpad, and turned it on. And it's stuck in a bootloop. I've been using it daily since release and updated to the latest alpha at its release.
It's stuck on the cm7 boot animation.
I've rebooted it multiple times. No luck.
Swifted from my Atrix.
Have the same problem right now again, last time I got this I had to reinstall the system and it was so frustrating....
I'm on the same situation today for no reason ..It was working fine for over a month. Any way to solve this without reinstall ... I know alpha 3 is out so just want to update... if I'm on webos how can I get to "sd card" folder to put alpha 3 file for upgrade ?
Never mind, fixed it... transfer alpha 3 file in to root of touchpad from webos and reboot to cwm , wiped cache and dalvik cache, install zip file from sd card ..choose the latest alpha 3 zip file .. then install and reboot.. that took care of cm7 endless bootloop and got alpha 3 installed as well....
Mentioning you have a bootloop and not giving the output of logcat helps no one.
Total wipe/reinstalled to fix it, right before alpha3 got released, kinda pissed at the timing.
Swifted from my Atrix.
Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.
UPDATE This is the MX2-Beta1 Done by DKZ. I am pasting the post Lrs121 did later in the forum (P.13) I am just posting it here to stay Current!
-below Lrs121 post their is my original post to help with flashing if you need it. Flashing should be the same. Included in Lrs121 post their is a wifi patch that DKZ applied.
Enjoy!
Lrs121
Here it is! CM9 Beta1 Download links.
THANK YOU AND ALL CREDIT GOES TO DragonzKiller For all the work hes put forth
Read entire post before flashing. Its long i know but worth reading.
Known issues for mx2 cm9beta1 without data wipe (comes from my experience with it)
Includes same issues for dx2
constant super user request (see fixes/info)
always says updating android durring startup (see fixes/info)
reboot/shutdown hangs (see fixes/info)
restart doesnt work properly (see fixes/Info)
WIFI does not start (SEE FIXES/INFO)
NOTE!!! IF UPDATING FROM ALPHA 4 Wipe DATA CACHE AND FACTORY RESET!!! DATA WIPE FOR ALPHA 5 IS NOT REQUIRED BUT RECOMMENDED!!!
How to install(credit to DZK)
Installation:
Install the BSR (patched if on CM7/CM9)
Reboot into the BSR
NANDROID <--- you'll probably want to go back to this
Install the CM9 zip from the SD Card MX2 Users Go to the MX2 Thread for the Patched CM9 zip once it has been updated to Beta 1
MX2 ONLY! Install the WiFi Driver zip from the SD Card
Install the GAPPS from the SD Card
Wipe both DATA and CACHE (no need to wipe Dalvik if you wipe both of these)
Reboot your phone
Enjoy CM9 Beta 1
Fixes/Info-for flash with out data wipe
Constant superuser requests - Fixed
when it happens - when you open an app that requires su access
Theory - su updated but the app list didnt causing request loops
how to fix - enter play market; go to my apps and uninstall updates for superuser; reinstall updates; open superuser and manually update binaries
Always shows Updating Android - Info
Info - No fix known, however it does not prevent your device from starting. Itll add on a couple seconds to the start time the first few times the phone is turned on after the first startup after flashing. After a few restarts it only takes a split second and it jumps right to the lock screen.
Reboot/Shutdown hangs (note this is occasional) - Info
Info - When rebooting or shutting down the phone will seem to hang with the rebooting/shutting down notification and the spinner is still spinning. The phone will become unresponsive to button input; that is normal for the shutdown and restart routiens.
Fix - None however the phone should reslove it fairly quickly the longest ive seen it hang is a minute or two then it shuts down or restarts properly. if it lasts longer than that i recomend a battery pull.
Restart doesnt work properly - Info
Info - this usually happens when the restart hangs. the phone will determine that the restart is taking too long and will force shutdown the device. The device will not start back up AUTOMATICALLY. Just turn on the the phone normally as if you had told it to shutdown instead of restart.
WIFI Does not start - info/fix hybrid
Info/Fix - after flashing the rom and the wifi fix, the wifi may or may not turn on/connect durring the first start up, restart the phone. After the first restart the wifi should turn on but be delayed in connecting, wait for it to connect or say its connecting and then restart the phone. afterward there should be no problem with the wifi. if you are still having problems you may need to reflash everything.
Will Update post as soon as the second mirror is up
Mirror 1
Cm9_Beta1
http://www.mediafire.com/?u320dbohymdxl0v
Gapps (note recomend finding current gapps and installing those. these are the ones i used)
http://www.mediafire.com/?aa37q7r985afoqj
MX2 WIFI Patch
http://www.mediafire.com/?e7cbyc9lmdj3p7g
-------------------------------------------------------------------------------------------------------------------------------------------
DKZ Came out with CM9 for the Droid X2. I tried to flash it and it did not work.
I did some modifying on his file, which he created, to see if I could get it to load in the Milestone X2. We are running a different kernel then the Droid X2.
I wanted to let everyone know that it was a success! With Several hours in trying to locate certain files and modifying them we have
CM9 FOR THE MILESTONE X2
I am in no means taking credit for DKZ's work. He did a fantastic job!
Problems I have seen so far are:
WIFI (working with DKZ to work)
Camcorder
Have not tested
HDMI
Radio
MMS
What works
Data
Text
Call
Touch screen
GPS
Camera*New
Theme's are suppose to work.
The transitions are smooth and I have not had any issues with freezing or anything yet.
When I loaded I came from stock 2.3.6 Rooted
Instructions.
1. Root phone on (how to do that Click Here)
2. Place BSR on memory card
3. Install BSR
4. Load BSR
5. Hit install Button
6. Click Recovery Mode
7. Do a backup
8. Wipe Factory Settings
9 Wipe Cache Settings
10. Go to Advance Settings
11. Go Wipe Devlik Cache
12. Select Go Back
13. Select Install from SD Card
14. Go to the place you put the ROM zip and choose install
15. GO back and install GAPP apps.
16. Wipe Factory and Cache one more time
17. Reboot phone
18. Install BSR Patch (link Below)
19. Enjoy Goodness!
To go back to backup copy.
1. Install Patched BSR
2. Select install
3. Select REcovery Mode
4. Select "Back up and Restore
5. Select Restore
6. GO to area restore was saved
7. watch load
8. Then when done then select to reboot phone
9. You are done!
Just keep in mind. If you are on stock use the normal BSR if you are on CM9 then use the Patched BSR! THIS IS VERY IMPORTANT!
CM9 ALPHA 5 (Thank you 754boy)
Link: http://www.mediafire.com/?rx1x4lz95mzau3k
G-apps
Link: https://www.dropbox.com/s/yw9088ehdqi4nfy/gapps-ics-20120429-signed.zip
MD5: 7C524E1E078164F681E0AA6753180B2C
He said that he is going to help with creating a wifi patch!
Sweet man! I'm going to try this tonight as soon as I get home from work
Did it work for you?
We're not going to have any wifi as long as we're using ics from the 2.3.4 kernel...well at least those of us who don't have a working sbf
Sent from my DROID X2 using Xparent ICS Blue Tapatalk 2
Sippi4x4man said:
We're not going to have any wifi as long as we're using ics from the 2.3.4 kernel...well at least those of us who don't have a working sbf
Sent from my DROID X2 using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
So us Cspire users don't have a working sbf? Have you tried this yet? I was just about to do it before I read what you wrote lol
If you guys want WIFI working. All you have to do is ask. I know how to make it work for you guys if the ROMs are actually running.
EDIT: I am going to need a few things from you guys first. And I am going to need one of you guys to get me the SBF for your phone so I can get them. If I have it, I can make one that works (at least for that specific SBF, maybe the others).
Sent from my MB870 using XDA
is this essentially for x2 owners that are not with verizon?
Below is the SBF for ntelos wireless running 2.3.6. That is the current sbf for that network and phone.
I did want to say that the firmware of 418 that was just recently released is the same as the Milestone X2. Eclipse made his new rom,2.2, based on this update and the wifi works. I do not know if this helps.
(from skwoodwiva post)
http://www.mediafire.com/download.php?qds5l2lp3s4c3st
MD5: 3915A1C1756EB5585FB1C7E4115F1B0E
MD5 Checker
http://forum.xda-developers.com/atta...4&d=1331628615
Outside of that the rom boots up, Runs great for an alpha. For everyday use it satisfies me.
Are you going to use my version I posted up their? I just took out the kernel checks.
Thank you DKZ!
HitMyKush said:
is this essentially for x2 owners that are not with verizon?
Click to expand...
Click to collapse
This is for Milestone X2 owners. We had issues isntalling CM7, MIUI, and CM9 with their release because we have a different kernel. So I modified DKZ original file so we can enjoy this one as well! They will not flash unless a few things are modified. This has been modified so MX2 customers can still enjoy the same things as DX2 customers.
I'll just make a patch that you guys can use.
Sent from my MB870 using XDA
Awesome!
Here is the patch the *should* work to get wifi working. I have NOT tested it and I don't even guarantee that it'll even flash. It also doesn't have a kernel check. With that being said, if it does work, I can only guarantee that it'll work with the MilestoneX2 version that was given to me in the SBF. As I know there a few versions out there, I doubt the kernel is the same for all of them. I don't have a MilestoneX2, so I wouldn't be able to check these things.
Wifi patch for the NTELOS MilestoneX2:
REMOVED CUZ IT WAS BAD
Also note that this patch (if working) should work with CM7 as well.
I am flashing it now. I will let you know.
EDIT; It did not work. Gave me a (code 6) error.
twobrare said:
I am flashing it now. I will let you know.
EDIT; It did not work. Gave me a (code 6) error.
Click to expand...
Click to collapse
probably a typo. like i always do. also forgot to tell the script to delete the older drivers.
Try this one:
http://www.mediafire.com/?1v5d6921zxczc10
It did not work. It booted this time but the wifi just says turning on. It stayed like that for 5 minutes.
754boy said:
Sweet man! I'm going to try this tonight as soon as I get home from work
Click to expand...
Click to collapse
Did you try Flashing this?
One thing I can recommend is if you are on stock use regular recovery. If you are in CM9 then use The Batched Recovery for CM7. As long as you do that you are going to be alright. Also look at the rerecovery.
Thank you,
Twobrare
dragonzkiller said:
Try this one:
http://www.mediafire.com/?1v5d6921zxczc10
Click to expand...
Click to collapse
This one it did not work either. I also had issues where the phone randomly frooze. It did it twice in less then a 30 second window...
Thank you for trying though.
this is awesome im downloading right now, feedback shortly
twobrare said:
It did not work. It booted this time but the wifi just says turning on. It stayed like that for 5 minutes.
Click to expand...
Click to collapse
i'm going to have to look at the firmware needed for it and how it interacts with your drivers. it might take a bit more for me to work out, but I'll try to get it working for you guys.