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.
Related
UPDATE - Do not bother with these instructions. They do not work as intended. Too many different results.
Unlocked R800X - run Sony ICS stock beta as a daily driver on your R800X - the easy way
This is purposed for the stock R800i rom to run on the R800X. Since the information is somewhat scattered in the threads I thought I would bundle it with instructions to help other R800X owners that want to use a completely stock rom with root. This assumes you have an unlocked R800x and know how to get fastboot working. Everything seems to work except MMS.
First a disclaimer...
-I did not create anything here so credit truly goes to Doomlord, Chevyowner, Sony, Google and anyone that contributes to XDA
-This is intended for informational purposes only. Although I hope it works for you, I really dont care if your phone goes up in smoke so use at your own risk.
Now lets have fun!
1) I gathered all the files you will need from XDA and Sony for this:
2) Extract the contents of the above file to c:\ICS using winrar
3) Copy all the *.zip files from the above folder to your phone's SD card
4) Boot device into fastboot mode. With the device off, hold the magnify glass button while connecting the usb cord. If all goes well you see a blue led. If not search forum about your fastboot problems.
5) Flash doomlord's ics beta kernel via fastboot. (this is so we can install from zip and also roots the new rom)
fastboot flash boot c:\ics\doom-ics.img
6) Boot to CWM - keep pressing the magnify glass button right after powering on the device
7) Wipe cache, data, dalvik cache and reboot
8) Boot device to fastboot again
9) Flash sony beta rom files (takes a while so be patient)
fastboot flash system c:\ics\system.img
fastboot flash userdata c:\ics\userdata.img
10) Boot to CWM - keep pressing the magnify glass button right after powering on the device
11) 'Install from zip' all the zip files you copied to your device earlier. Including gapps, doomlords ics boot animation, and cdma
12) Flash stock kernal (fix wifi without loading modules)
fastboot flash boot c:\ics\boot.img
13) To get cell data working - go to settings, xperia, internet settings and click accept
Hope this helps someone. Good luck!
Followed the steps on my R800x, boots, wifi works and runs pretty smooth. Phone crashes after I hit the call button. SMS appears to work, MMS doesn't, even after adding the Verzion APN in settings.
Going to Settings>Xperia>Internet Settings doesn't appear to do anything after hitting apply, mobile data isn't working and calls crash. Haven't tested any games yet though. Are there any steps I might have missed?
Edit: Even though the phone force closes, the call connects and the other party can hear my voice, but there's no way to hang up or any indication that there's a call going on. The Wifi indicator flashes on and off until the phone is rebooted or the call is dropped.
Wallrunner said:
Followed the steps on my R800x, boots, wifi works and runs pretty smooth. Phone crashes after I hit the call button. SMS appears to work, MMS doesn't, even after adding the Verzion APN in settings.
Going to Settings>Xperia>Internet Settings doesn't appear to do anything after hitting apply, mobile data isn't working and calls crash. Haven't tested any games yet though. Are there any steps I might have missed?
Click to expand...
Click to collapse
Nope. This is all we have working right now.
Sent from R800x
Leraeniesh said:
Nope. This is all we have working right now.
Sent from R800x
Click to expand...
Click to collapse
Thanks, but were you aware that calls were going through and the microphone works? you just can't hear the other party or see anything indicating the phone was on, but the other party can hear you and they get a call notification.
Wallrunner said:
Thanks, but were you aware that calls were going through and the microphone works? you just can't hear the other party or see anything indicating the phone was on, but the other party can hear you and they get a call notification.
Click to expand...
Click to collapse
Don't forget that only the other party can hang up or do anything else in the phone call. Works great for leaving voicemail!
Wallrunner said:
Followed the steps on my R800x, boots, wifi works and runs pretty smooth. Phone crashes after I hit the call button. SMS appears to work, MMS doesn't, even after adding the Verzion APN in settings.
Going to Settings>Xperia>Internet Settings doesn't appear to do anything after hitting apply, mobile data isn't working and calls crash. Haven't tested any games yet though. Are there any steps I might have missed?
Edit: Even though the phone force closes, the call connects and the other party can hear my voice, but there's no way to hang up or any indication that there's a call going on. The Wifi indicator flashes on and off until the phone is rebooted or the call is dropped.
Click to expand...
Click to collapse
Was the CDMA for Verizon "patch" in this .rar. tested on the doomlord kernel? (vs. stock)
zipeee2 said:
Was the CDMA for Verizon "patch" in this .rar. tested on the doomlord kernel? (vs. stock)
Click to expand...
Click to collapse
My patch is only to receive a CDMA signal. Its been tested on DooM and stock, with similar results.
Sent from R800x
Leraeniesh said:
My patch is only to receive a CDMA signal. Its been tested on DooM and stock, with similar results.
Sent from R800x
Click to expand...
Click to collapse
Sorry there is trouble.
Again all I did here was attempt to bundle everything that's already available to make it easier. I assumed what I did would work for everyone.
Since I wrote the instructions from memory I should go through them again to see if I missed a step.
My data works fine as well as 3g notification.
My phone app does occasionally get that error but calls and hangs up ok.
Personally I prefer the stock kernel and stock wifi modules because I get way better battery life in standby. Other roms/kernels I was only getting 5 hours and with ics beta with stock kernel I get over 24 hours.
Do you think baseband versions matter here causing different device behavior for data and phone issues?
Please help me, i'm on step 6 and having an impossible time booting to CWM, and am now stuck in a bootloop since flashing doomkernal
GlacialFlames said:
Please help me, i'm on step 6 and having an impossible time booting to CWM, and am now stuck in a bootloop since flashing doomkernal
Click to expand...
Click to collapse
Instead of flashing DooMLorD's ICS kernel in step 5, try flashing the three .img files from the official beta, then try this in fastboot mode. It will boot you to recovery instead of flashing it, where you can flash all the .zip files in step 11 onwards. No need to do step 12.
One2many said:
Unlocked R800X - run Sony ICS stock beta as a daily driver on your R800X - the easy way
This is purposed for the stock R800i rom to run on the R800X. Since the information is somewhat scattered in the threads I thought I would bundle it with instructions to help other R800X owners that want to use a completely stock rom with root. This assumes you have an unlocked R800x and know how to get fastboot working. Everything seems to work except MMS.
First a disclaimer...
-I did not create anything here so credit truly goes to Doomlord, Chevyowner, Sony, Google and anyone that contributes to XDA
-This is intended for informational purposes only. Although I hope it works for you, I really dont care if your phone goes up in smoke so use at your own risk.
Now lets have fun!
1) I gathered all the files you will need from XDA and Sony for this:
http://www.mediafire.com/?29fiyj22bt8lzlg
2) Extract the contents of the above file to c:\ICS using winrar
3) Copy all the *.zip files from the above folder to your phone's SD card
4) Boot device into fastboot mode. With the device off, hold the magnify glass button while connecting the usb cord. If all goes well you see a blue led. If not search forum about your fastboot problems.
5) Flash doomlord's ics beta kernel via fastboot. (this is so we can install from zip and also roots the new rom)
fastboot flash boot c:\ics\doom-ics.img
6) Boot to CWM - keep pressing the magnify glass button right after powering on the device
7) Wipe cache, data, dalvik cache and reboot
8) Boot device to fastboot again
9) Flash sony beta rom files (takes a while so be patient)
fastboot flash system c:\ics\system.img
fastboot flash userdata c:\ics\userdata.img
10) Boot to CWM - keep pressing the magnify glass button right after powering on the device
11) 'Install from zip' all the zip files you copied to your device earlier. Including gapps, doomlords ics boot animation, and cdma
12) Flash stock kernal (fix wifi without loading modules)
fastboot flash boot c:\ics\boot.img
13) To get cell data working - go to settings, xperia, internet settings and click accept
Hope this helps someone. Good luck!
Click to expand...
Click to collapse
I clicked Thanks, not because this works - it doesn't - but because you at least made the attempt to be helpful in gathering everything together in one place. Step 13 in particular has never seemed to work for me on Verizon.
The facts about the Sony ICS Beta and the R800x are simply these:
Sometimes, some people, for some UNKNOWN reason, will manage to get everything working almost perfectly. At one point, I had working calls and data, downloaded and installed apps over 3G, the works. Then I booted into recovery and made a backup, thinking to share a working Nandroid...
Well, guess what? Not only did it not work for anyone else, it stopped working for me too. I have tried everything to recreate my former success, with -ZERO- success.
At this point, to my knowledge, NO ONE has found a way to make calls AND 3g data work at the same time, as one would expect it to, in any repeatable manner. Maybe calls, sort of; maybe 3G data for browsing, but not for downloading from the market; rarely both at the same time, and never what one would call a daily driver.
In short, right now, the closest thing we R800x users have to a usable ICS is CyanogenMod 9 by FXP and further modified by paxChristos, AGraceful and others. It's something to bide our time with until one of these genius kids on here finally figures it out. As for Verizon and Sony go, it will probably be a long time coming, if ever, regardless of projected release dates to the contrary.
Having said all that... I think I might wipe my phone and try it all again today!
netizenmt... I agree. I have tried going back & forth between GB and ICS and as much as I love the look and feel of ICS at this point I cant use it beyond just playing around with it as CDMA and 3G are not working. For me I have to have this. I dont mind testing a ROM and or a CDMA patch but for me to have no calls at minimum I cant go without. I watch this threa daily and hope that a Super Genius will find a solution. Becuase I know 2 things. When Sony releases the ICS rom for our PLAYS it will NOT be for Verizon users as Verizon would need to release the ICS version or at least a CDMA but the chances of that happening.. I have a better chance of being the next leader of Middle Earth (yes L of the Rings pun) before Verizon gives a monley butt about our phone. I do work next to a corporate office for Verizon and I do have friends that work there but they are not high enough on the food chain to make a mouse squeek. All in all we R800x users are at the whims of the awesome devs here. And for their efforts I salute you..... the CDMA patch may have us at the moment but I know given time something will happen. Keep positive peeps.
netizenmt said:
I clicked Thanks, not because this works - it doesn't - but because you at least made the attempt to be helpful in gathering everything together in one place. Step 13 in particular has never seemed to work for me on Verizon.
The facts about the Sony ICS Beta and the R800x are simply these:
Sometimes, some people, for some UNKNOWN reason, will manage to get everything working almost perfectly. At one point, I had working calls and data, downloaded and installed apps over 3G, the works. Then I booted into recovery and made a backup, thinking to share a working Nandroid...
Well, guess what? Not only did it not work for anyone else, it stopped working for me too. I have tried everything to recreate my former success, with -ZERO- success.
At this point, to my knowledge, NO ONE has found a way to make calls AND 3g data work at the same time, as one would expect it to, in any repeatable manner. Maybe calls, sort of; maybe 3G data for browsing, but not for downloading from the market; rarely both at the same time, and never what one would call a daily driver.
In short, right now, the closest thing we R800x users have to a usable ICS is CyanogenMod 9 by FXP and further modified by paxChristos, AGraceful and others. It's something to bide our time with until one of these genius kids on here finally figures it out. As for Verizon and Sony go, it will probably be a long time coming, if ever, regardless of projected release dates to the contrary.
Having said all that... I think I might wipe my phone and try it all again today!
Click to expand...
Click to collapse
Don't waste your time on this any longer. Although I swear I had 3g at one time I have been unable to replicate. I get too many different results. Updated first post to discontinue this thread. Thanks!
One2many said:
Don't waste your time on this any longer. Although I swear I had 3g at one time I have been unable to replicate. I get too many different results. Updated first post to discontinue this thread. Thanks!
Click to expand...
Click to collapse
Yes, it is both extremely puzzling and annoying how it works for one person one way, another way for someone else, then it quits working... it's like something "intelligent" is in there messing it up for us... That sounds so paranoid, but I don't know how to explain it otherwise.
netizenmt said:
Yes, it is both extremely puzzling and annoying how it works for one person one way, another way for someone else, then it quits working... it's like something "intelligent" is in there messing it up for us... That sounds so paranoid, but I don't know how to explain it otherwise.
Click to expand...
Click to collapse
Its like Verizon is physically ****ing with us.
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
Hello
I ported the JoyOS from ZTE to the SGP4.
I used the lastet beta of cm7.2.
Known issues of CM7:
Reboot into recovery does not work yet
Setup wizard doesn't run properly, just skip it
Bluetooth won't scan properly
Deep sleep is still disabled
Installation:
Originally Posted by tdmcode
When you install the ROM, the first thing it will do is flash the kernel and backup your data (efs, dbdata, data, cache). Then it will reboot.
Note I don't have it set to automatically reboot into recovery yet, so you'll have to hold VOL+UP to get back into recovery in the new kernel. Note the strange looking initlogo -- I haven't figured out why the framebuffer format isn't correct. Just ignore it for now.
Aot this point, the system doesn't know whether the device is US or INTL because efs has not been restored. So the home key won't work on US devices. Use the menu key to select.
Now install the ROM again. This time it will restore the data directly on MTD/yaffs2 and do the actual install. When it's done, reboot. You should have a functional system and the home key should work on US devices again, since the efs data is now available again.
Finally, wipe data and cache.
Click to expand...
Click to collapse
Download
Nice to see yet another ported ROM from you! One more, and you will have surpassed all the 4.0 Roms combined (sgs ports excluded). Keep up the good work chaoschris!
Awesome rom you have there. I don't have a SGP4 but keep up with the good work. I like your Google Doc/Drive storage.
Dude, your spitting out roms left and right! Keep it up!
Sent using Tapatalk
I don't know what happened. Or why it won't work.
When Safestrap was originally finished, I installed Hyperdrive without a problem. An update came, I downloaded and installed. It made it so I couldn't use HotSpot anymore. So, I figured it was the Rom, and I installed Jellybean Rom. I didn't like it. I tried to install the original Hyperdrive I had, and once its installed and reboots, the lights come on for one second and shut off. Downloaded the newest Hyperdrive, same issue.
The instructions say wait for 10 minutes. I did, and longer. (Range usually 20-40 minutes)
Last night I wanted to try again, (downloaded newest hyperdrive. I have sloooooow internet. Took 5 hours to finish). So, I tried installing today following the instructions, same issue. It installs and says everything is fine, reboot, safestrap pops up, loads normally through that, and the lights are on after like it starts with Stock, lights shut off, phone stops working.
When this happens, the phone does not respond to anything. Power does nothing. I waited 45 minutes the 3rd time trying to reboot after install. The phone will not turn on, respond, or anything unless I pop the battery out and put it back in. I can get back into Safestrap that way.
I really want to use Hyperdrive, but it just won't reboot for my phone.
I do have the Verizon i545 version, ME7, Safestrap, Rooted, and newest Hyperdrive Rom. Used the Safestrap Kernel, but the phone locks up.
I've tried default settings, different Rom settings, (2gb and 3gb), removing almost everything from install, adding what I want, adding what I like, etc. No combination of settings will let me phone boot into Hyperdrive.
Any thoughts?
Are you completely removing then re-creating the slot when trying all these flashes?
Are you flashing the ME7 kernel module.zip ?
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to re-download the module? Preferably on the computer then transfer to your ExtSDCard with the ROM.
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
While you were trying to install did you notice if zip signature was checked if so uncheck when you install and uncheck when you install module other than that don't know what else to say. When i first started i found that to be my problem.
The zip signatures were not checked. : /
Sent from my SCH-I545 using xda app-developers app
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Excessumcarcer said:
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Click to expand...
Click to collapse
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
!Led*Eyes! said:
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
Click to expand...
Click to collapse
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
!Led*Eyes! said:
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
Click to expand...
Click to collapse
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Excessumcarcer said:
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Click to expand...
Click to collapse
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
!Led*Eyes! said:
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
Click to expand...
Click to collapse
Well...nothing has worked.
Update for everyone, I was using the older SS, 3.60.
I killed everything, put the original Verizon ME7 Rom on the phone, re-rooted, put 3.62 SS on, (Done like it), installed the HDrls10, Installed the module, (both successful), restarted, exact same thing. Right after Safestrap Enabled pops up, the phone goes dark and the battery needs to be removed and put back in for it to turn on again.
So, I tried something crazy and for whatever reason it worked as far as HD is concerned...but...I went outside of the instructions.
I have the HD rls9 Final. I installed it through SS, used the modded Kernel, (non SS), and restarted. It popped right up in about 45 seconds. (Wasnt working before I reset everything and started over)
I tried HD rls10 Final that way, and nothing.
I will be redownloading it tonight to make sure it isn't the download. (I have slow internet, itll take all night likely.) : /
If anyone is looking to actually uninstall SS (which you need to do to roll back a version) you need to use the commands hashcode has provided. Using Terminal Emulator on the stock side will accomplish that. Read up on hashcode's SS OP.
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Excessumcarcer said:
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Click to expand...
Click to collapse
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
lazer9 said:
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
Click to expand...
Click to collapse
I just double checked the MD5. It matches the download. How frustrating. Double checked the build, double checked the MD5, double checked install procedure, etc. It flat doesn't work on my phone, and there is no logical reason to it. I tried from a fresh build twice now, doing the rooting and SS install from stock everything.
It locks up right after SS, still.
Electronics hate me, it has been determined before. This is just further proof.
: /
So, I've done pretty much everything feasible. Guess Ill have to stick with an older HD or different rom. : (
Also, hotspot doesn't work HD 9 for me, (nor Jellybeans). I installed the module when I did the rom, but there is no hotspot for one. And two, when I download and use FoxFi, which I paid for to use on the Stock Rom before SS, it will try to turn it on and then it freezes and crashes.
All I want is a non-Verizon Rom with working Hotspot!!!! AHHHHH!!!! Looks like that aint happening.
Well played Verizon...well played. Perahps I should get an international phone and go to another company. Expensive, but tempting.
So, the final verdict for those following -
Hyperdrive 10 - Does not work on my i545 no matter what I tried.
Hyperdrive 9 - Works but the hotspot is glitched and froze no matter what I tried.
Jellybean - Works the same as HD 9
Synergy - Works. Everything on it works, hotspot, install, etc.
Not sure why the others did not work. But, for whatever reason Synergy works flawlessly for my i545. Installed and downloaded the same ways as the others, yet it worked.
: /
I was planning on trying a few others first, but Synergy claims to block Samsung from logging information from my phone. I realize this doesn't stop every company from doing it, but its the thought that counts. lol. So, Im trying this Rom out now. It's no hyperdrive, but it works.
After a BUNCH of tries I finally got it to work!!
I have a Verizon i545 with ME7. I basically started as if I'd never installed HD 9.1 in the first place.
Here's what I did.
1. Double check that your device is rooted. I used Root Checker Basic. I actually re-rooted my device just to be sure (I venture to guess it might have been unnecessary) and it worked.
2. I used a 4GB SD formatted to ex-fat and put the HD RLS10 AND the ME7 modules .zip file on it (Both on the SD)
3. I then booted into recovery.
4. Make a new ROM slot.
5. Name it whatever you like.
6. When you go to flash HD, hit the add zip button and select the ME7 modules.zip
7. When HD gets done flashing UNCHECK the "Reboot" box up top and then hit the reboot tab at the bottom right.
8. It will automatically flash the ME7 modules next. When it says 'Successful', then reboot.
9. Give it a few seconds and hopefully it will work for you as well. Good luck.
Latest installable version for Me7?
What is the latest installable version of HD for verizon locked Me7 bootloader, i currently have rls10.0 installed and ive tried 10.1, 10.2, and now 12 and none of them boot up.
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.