Just installed Kitchen Sink by Jokersax and Team. Looks great but have one BIG problem - the telephone has not service: During boot I'm getting the error message: Unfortunately, the process com android phone (I took the dots out!) has stopped
That leaves me without phone and data service!
As Th3Bill recommended, in CWM did Choose Advanced, Choose Report Error, Choose Show Log, Choose Reboot Recovery. Then did a Backup. THEN flash Kitchen Sink v2.11 with following options: CM9, Default stock install, full wipe.
Please help! Thank you for any help! C
Did you wipe before install? If you did restore your backup and flash again without wiling from within CWM. You need a working base to start from.
Before going that route boot into CWM, wipe davlik cache, fix permissiins, then reboot.
My MoPho's in the kitchen sink!!
More details about my installs
Thanks for the reply!
I did not wipe within CWM, just the Error-Report-Log thingy that Th3Bill recommended, even though I'm not sure what the reporting changes. I'm just starting out on CWM!
One thing I failed to mention was that a few days ago I was trying to flash CWM recovery as shown here http://forum.xda-developers.com/showpost.php?p=20331623&postcount=6. After erasing the recovery (step 2) I was unable to flash the img file (step 3). I got a bit freaked out, but then installed CWM with the MOTODX2_Bootstrap_signed.apk. Based on that I "upgraded" to CWM 5.5.0.4 with the joker-recoveryv3.zip file.
It all worked flawlessly until I flashed KS 2.11. The first install (AOKP; non-wipe; 1300 oc; all nos and Cyanogenmod animation; select all launchers; font default; keyboard Cyan9; GPS N.Amer; TTS Google; Music CM9; Gapps yes; network CDMA; RIL forced roaming; Alt 2d libs No; Beats Audio Yes; Bravia No) seemed to have installed well, but the boot animation went on for a while, so I left it running while plugged into the wall. Four hours later the phone was out of power (even though it was plugged in), and really hot to the touch. After charging I restored the previous installation.
The next night I tried it again (as Th3Bill suggested, in CWM did Choose Advanced, Choose Report Error, Choose Show Log, Choose Reboot Recovery, Backup, THEN flash Kitchen Sink: CM9, Default stock install, full wipe). This one worked fine except for loosing the phone function. However, again I left the phone turned on and plugged in, and after 5 hours it was dead. After charging restored to the previous install (198-7).
In summary:
1. I deleted recovery a while ago but have CWM. Concerns?
2. with KS installed the phone doesn't seem to be charging
3. lost phone function.
How do I deal with these problems. I'd really like to run KS!! I have the recovery.log file I created before the last flash. However, xda doesn't let me copy it into this Reply as I haven't posted much here.
Thanks for your help!
As far as your phone fc is concerned, try flashing cm9 0.3.something in bills fixes thread, then flash kitchen sink with no wipe option. Boot into 0.3.x first to make sure you have service, then go back to recovery and flash sink.
Sent from my MB855 using XDA
Do not understand the term 'kitchen sink'
We used the term 'kitchen' in the WinMo days to discuss 'cooking' a ROM. Makes sense since kitchens are for cooking.
'Kitchen sink' to me indicates garbage down the drain. What am I missing? Not a big deal, but I am obviously missing what you'all are intending "kitchen sink' to mean.
tia
Kitchen Sink ROM installer. http://goo.gl/aMqiM
Kitchen sink rom is actually anbjnstaller with 5 roms in it. Jokersax th3bill and spleef has busted there ass for this community and you degrade their work by sayigbits trash. Do some research jokers cm9. Miui. Aokp aokpcb gummy and all the options included in each ROM where you can basically mix and match them to create one suitable for each individuals needs/wants . Please show support and thank them! You are doing a great job with this ROM!
Sent from my MB855 using XDA
willysp said:
Do not understand the term 'kitchen sink'
We used the term 'kitchen' in the WinMo days to discuss 'cooking' a ROM. Makes sense since kitchens are for cooking.
'Kitchen sink' to me indicates garbage down the drain. What am I missing? Not a big deal, but I am obviously missing what you'all are intending "kitchen sink' to mean.
tia
Click to expand...
Click to collapse
Kitchen sink ROM = has everything but the kitchen sink
Sent from my MB855 using XDA
Related
Didn't want to clutter any other thread but wanted to know about the package and the script in the newest 7/1/11 build.
Does a wipe need to be done?
I installed through the orange CWM and it just recovery looped so I did the 3 finger to recovery and flashed from RED CWM and now it boots to CM7 just fine. Didn't do a wipe.
Should this package be able to be flashed from previous versions and maintain settings or does it require that a wipe be done beforehand?
Can the update script be modified to not convert if it has already been done?
Could the new packages be setup in more of a Delta apply?
Sent from my SCH-I500 using XDA App
The bootloops appears to be an issue with the 7/1 (Build 6) release of CM7 (also an issue with MIUI 1.7.1.3 which is based upon 7/1 CM7).
7/4 (Build 7) CM7 did not do this for me.
So, I wouldn't worry about the bootloop issue anymore.
As for wiping, it is good practice to wipe before installing any rom unless the dev explicitly says it is unnecessary. However, if you did not and you are not having force close issues, then I wouldn't worry about it.
It is my understanding that the filesystem is converted to MTD once and then everytime you reinstall the ROM (or update to a new version), it only checks to see if you are properly converted. JT would be able to answer this question better, this is only what I have observed.
Jp
Well I am happy for a response and will take it at face value since I spent some time setting myself up again.
While I agree with wiping g before an update there really isn't a reason you can't try it first and see if it works or not.
I know that I had to edit a file to get the 7/1 version to install so I was thinking there might be something else in there that could keep from wiping.
Sent from my SCH-I500 using XDA App
this is a long story, so bear with me, please:
i used to be on JPKH1 (this was the rom that came out of the box)
i was on XXKI3 when i decided to flash nightly #116 of CM7. i followed the instructions, got it working and had no real issues. however, i felt like CM7 made my phone old-ish (loved it otherwise), so i decided to return to a custom rom. prior to all this, i was on VillainROM 3.0
i flashed XWKJ3, business as usual, and then Batista70 rom. when i did that, something...strange, happened. none of the system functions worked (SNS sync, android system ringtones, etc.). i was overall dissatisfied with it, so i switched to Omega rom 6 XT.
i did that, and installed the relevant version of ICS domination theme by vertumus, and that's when it first happened - both the camera AND android system ringtones were force closing. also, when a system notification came on the unfortunate moment my phone was asleep, there would be a moving pixel on the screen and nothing else until i woke the phone up. nothing i did would fix it, and believe me, i tried EVERYTHING (restore nandroid, fix permissions, reflash rom). at last, i factory reset it, which did the trick but took some of the 'omega' out of 'omega rom'
i flashed stock XWKJ3, factory reset, flashed Omega 7 XT, and the problem persisted. it starts whenever i reboot the phone, for any reason, even if it doesn't change anything on the phone (just a simple power on/power off)
now i was pissed, and went back KI3 and VillainRom 3 and all SEEMED good. there were VRTweaks i wanted to use, but the above DID happen, after all. i rebooted into CWM recovery, took a nandroid, booted up again and sure enough, 'it' happened AGAIN!!!
this has me driving myself crazy, and no one on the Omega thread seems to believe in the existence of my post there (that's how well they're ignoring it). WHAT SHOULD I DO?!!!
by the way, i have NEVER flashed a .PIT file (since i've read in so many places not to touch that thing on the S2) and my binary counter is at a service-center-scaring 7. and for the love of god, don't just read this and go away (that's happened to me before), GIVE ME A HAND!!!
Stock rom via odin, and reroot.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
tried that already
flashed KJ3, then omega 6
flashed KJ3, then omega 6
flashed KJ3, then omega 7
flashed KI3, then villainrom 3.0
or were you implying something else?
Try wiping dalvik/partition/cache before and after installing the custom ROM
I do that out of habit when installing custom roms, as in the above cases
Sent from my GT-I9100 using Tapatalk
Have you tried fixing permissions? Might be worth a try
Sent from my GT-I9100 using Tapatalk
the pixel on the screen is because of app called noLED or something like that just uninstall it like any other apk and your that problem will be solved it automatically installs when you flash OMEGA ROM
@thefaixy: well, solved i guess
@macdam: nope
Sent from my GT-I9100 using Tapatalk
Random but I had an issue on my phone that followed me through different ROMs and kernels like some sort of ghost.
Turned out to be a corrupted video file in my ext SD card which was basically crashing the phone constantly and causing all sorts of strange issues.
Sent from my Optimus 2X using Tapatalk
thanks for the suggestion, mungulz, but i suppose we don't have the same problem. i went through all my internal AND external data and saw nothing out of the ordinary
on that note, introducing another twist in this ridiculous predicament, NO app (and with the exception of root explorer, NO app) can see my songs (external sd). if i use root explorer to force an app to use it, the app force closes
and just a thought, but i keep fixating on the .PIT file. your thoughts?
Have you done a full wipe including user data? Might be something left over that us causing issues, take a titanium backup first though
Sent from my GT-I9100 using xda premium
if you mean the CWM one, then yes, plenty of times. basically, each time i flashed something on the phone in this period, i factory reset. if i do it now, that will temporarily solve the problem and i'm pretty sure of it. one reboot later, i'll be back in hot water
i'm aware, of course, that there are other ways of factory resetting...
1) Flash Stock KI3, with pit file and re-partition
2) Back up everything including the int. SD to my PC.
3) press *2767*3855# it will completely wipe your device.
4) Once phone reboots, place custom rom and pictures + titanium backup onto the int. SD
5) Flash a custom Kernel
6) Reboot recovery, wipe data, wipe system, Flash Rom.
7) Reboot and restore the DATA only
or without pit file and uncheck re-partition
i had to go for tuition, so i couldn't do all the things gasmias said; just factory reset with *2767*3855# and then restored the apps ONLY with TB. and...my phone is back!
huge thanks to all of you for trying to help (lol, too many thanks buttons to press) . i guess it was just corrupt left overs. but dammit, now i'm scared of putting VRTweaks back in . eh, i'll take a nandroid back up
in light of these events, anything i should keep in mind for my future flashing endeavors?
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.
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.
Okay, so I've tried a ton of different JB ROMs and have come to the conclusion it's not meant for the Fascinate. Between slowdowns, memory issues, missed calls, bluetooth crashes and app incompatibilies it just isn't worth it on our phone.
So, this is how you can join me in moving back to a fully working and FAR more responsive ICS (Gummy ROM). Not only is my phone zippy fast again, all apps work as intended (including Samba Filesharing, Pandora, Snapchat and LBE Privacy Guard!). No more weird errors, no more 'such and such stopped responding', no more missed calls! It's just like a working phone.. because now it is!
I ended up:
- Doing an Odin of CI500_VZW_EH03_GB_CM.tar.md5 and atlas_v2.2.pit (re-partition option checked, battery installed)
- booted it
- back to odin again (battery in)
- odined cwm4_fixed_for_cm7-ODIN.tar
- booted into recovery directly (3 finger after battery pull)
- flashed teamhacksung-ota-eng.BUILD2.zip
- booted it
- rebooted to recovery via power menu
- flashed Gummy_fascinatemtd-Release-2012-06-15-03_38.zip
- booted it
- rebooted to recovery via power menu
- flashed gapps-ics-20120317-signed.zip, Glitch-fascinatemtd-SkunkWorks-20120510.1733.zip and TitaniumBackup.zip
- booted
- restored my apps + data (not system data, just app data)
- profit!
If you don't have any of these files, the ones I haven't linked are likely linked elsewhere in this section, but if you want to find them faster, just search for the exact filenames in google. If anyone has links to the missing ones, please post them below and I'll update this.
DON'T SKIP ANY STEPS! THEY ARE ALL LISTED FOR A REASON. IF YOU HAVE A PROBLEM AND SKIPPED ANY STEPS, I WILL KNOW AND YOU WILL BE IGNORED.
Cheers, and welcome back a working phone!
Links to stuff
Here are some links for stuff:
TeamHacksung ICS Build 2: http://www.enderszone.com/ics/teamhacksung-ota-eng.BUILD2.zip
ClockWorkMod for CM7: http://forum.xda-developers.com/attachment.php?attachmentid=669652&d=1311907538
you can find the other stuff at Droidstyle's excellent guide: http://forum.xda-developers.com/showthread.php?t=1238070
scroll down to the section about ICS/JB ROMs.
also, i wanted to add some things to the guide.
1. if you don't have the samsung drivers and odin, go to Droidstyle's thread, or browse around the Fascinate subforums for info.
2. transfer the zip files to your phone before you odin stock firmware for convenience
Dude, you just saved my ass. I was effin' around with my GF old Fascinate, which I've used basically as a learning device for my kids, and I thought I'd flash a new 4.2.2 ROM (I was on another that I can't remember). Well, it didn't go well and of course I didn't have a nandroid. All of my nandroids were ICS and earlier and simply restoring wasn't gonna work. Thanks so much for this! Took me a while, but I got it done.
After using gummy rom for a while, I've found I've had some pretty irritating lag issues. I'm now running avatar ics rom and recommend flashing that instead of gummy. Also, avatar rom doesn't need a custom kernel as its plenty fast without the need to overclock.
Otherwise the flash directions are the same as gummy rom
Note, I'm speaking of avatar ics, not avatar jb. Cheers!