My friend and I both have Fascinates. I got mine first, and just rooted the Gingerbread that came with it. I use it for medical purposes, and really needed something stable and reliable.
When my friend got hers, we decided to go for a more recent ROM, and chose GeeWiz 4.4.2 (Jellybean). It was real easy to install and didn't require anything special. It worked great for a little while, but as she added apps to it, it got real laggy and hard-crashed a fair amount.
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Since it's a blank canvas, and her experience with GeeWiz wasn't all that great, I figure it's a good time to try something else.
What do YOU recommend?
Here's her priorities:
1. Must be super stable.
2. Everything must work. Speakerphone, bluetooth, camera, video, microSD, you name it.
3. Not laggy.
4. Good battery life.
She really likes the Jellybean notifications, so she would prefer Jellybean or later.
I'm very interested in what the community recommends. :highfive:
the newest cm10.1 nightly was rock solid for me. helly bean 4.2.2 was good too. don't go beyond 4.2 if you want good stability, i don't think some basic things work in the cm11 builds yet (GPS and MMS are flaky)
oh also don't feel bad for running stock GB. i'm actually running it right now (rooted, lean kernel, and i gutted out the majority of samsung things)
---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------
also, for future reference, any thread you post of similar connotation to this will probably get locked by a moderator and he'll say "oh try roms out for yourself blah blah blah"
so if that happens, don't say i jinxed it. also, i've had my fassy for around 6 months and i've tried literally everything under the sun for it.
I agree with sceptic on these ROM selections
rockpaperlizard said:
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Click to expand...
Click to collapse
I thought Geewiz was only made for the Fascinate? I have been trying the Geewiz rom, and so far the only time it became laggy was when I set the cpu Govenor to a power saving option. Otherwise it has actually been much faster booting up than the kitkat roms.
Sent from my GT-N5110 using xda premium
Okay, trying to get Hellybean working... but am stuck!
Thank you to everyone providing a reply so far. Please keep the suggestions coming. :highfive:
I am trying to install the recommended Hellybean 4.2, and am stuck.
The phone was stock Gingerbread, and then I installed the GeeWiz 4.4 ROM on it. Had some lagging and crashing, so now I'm trying to get Hellybean 4.2 on it, per recommendations of others.
So I downloaded the latest Hellybean 4.2 from the hellybean website. I then booted into recovery, and selected Update from Zip and and tried to install the Hellybean zip. I get a Status 7 error. Some sites said to try it 3 times. I tried it 5 times. No dice.
I can't find a Hellybean 4.2 Fascinate thread on XDA, so details are sparse. Am I blind?
Am I correct in understanding that Hellybean 4.2 includes the devil kernel? Or do I need to ODIN a different kernel first?
I installed ROM Manager to get the latest CWM Recovery, but it says the Fascinate is an "unknown device". There is no CWM Recovery installation file for the Fascinate listed on the Clockworkmod website. UGH! :crying:
Can anyone help? I can follow step by step instructions real well. :good:
Progress Update
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
rockpaperlizard said:
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
Click to expand...
Click to collapse
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
if any of my guide didn't help, just follow the thread i linked in step 2. it's a good comprehensive guide.
also never flash anything with ROM Manager, it's useless for this phone because the version of CWM on ROM Manager is really old. i've bricked my phone when trying it.
Getting closer!
skepticmisfit said:
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
Click to expand...
Click to collapse
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
rockpaperlizard said:
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
Click to expand...
Click to collapse
wipe data before installing helly. also i've never bothered with build.prop in Hellybean. it only references to EI20 for Voodoo Sound drivers. EI20 is the stock build for.. i believe the US Cellular Mezmerize (aka not the Verizon Fascinate). so don't screw with it
yes stock radio is good. EH03 is a good radio but if you want you can flash EC09, based off of a leak of GB. some people have good luck with it, i used to but i like EH03.
so.. i'm not sure if you can boot the phone into helly bean. it sounds like you were getting a lot of "status 7" errors, which i didn't ever get while trying to use helly. this may or may not be caused by the sd card. try a different card if possible. if you're bricked at this point just start over from EH03.
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Good advice!
skepticmisfit said:
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Click to expand...
Click to collapse
Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
rockpaperlizard said:
Hey, it's the girlfriend here. BF is out, so I was trying to get the right files gathered. Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
Click to expand...
Click to collapse
here you go: http://andromirror.com/file/1386
good luck!
Sooooo close...
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
rockpaperlizard said:
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
Click to expand...
Click to collapse
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
for windows
or an android one
like this one
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
its what you need to start with,, and then after you sign in to your account,, it will check to see what needs to be updated.
.
I tried the cm10 mentioned here. It does seem very nice. It appears to have more features than Geewiz also, along with a lot more ringtones.
Sent from my GT-N5110 using xda premium
Information
hhp_211 said:
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
.
Click to expand...
Click to collapse
Thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
hhp_211 said:
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
.
Click to expand...
Click to collapse
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
It's the blue CWM, forgot to mention that...
rockpaperlizard said:
Hi, GF here again. I'm new to all this, thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
Click to expand...
Click to collapse
whoa you're not supposed to have blue recovery after flashing a 4.x ROM (or MTD as we call it).
go to step 4 in this guide: http://forum.xda-developers.com/showthread.php?t=1238070
you're going to have to reflash EH03 in Odin before doing anything because your recovery is borked.
Got it!!
Finally got helly onto a phone! Ended up starting all over, and then just flashing to helly since had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
rockpaperlizard said:
GF here. We finally got helly onto the my phone! We ended up starting all over, and then just flashing to helly since we had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
Click to expand...
Click to collapse
that's weird that 3-finger into recovery is broken for you.. it wasn't for me. but whatever, as long as it works
Related
Hello, at the start i wanted to install some new ICS rom for my Vibrant..i try to root it with one click and i couldn't do that coz i had froyo(2.2update)..so i read some forums and found solution in odin...i used that to turn back to stock eclair where i rooted the phone ...but the problem is that now i can't install any application on the device(i need ROM manager)..i get to android market and ,click on application but nothing is happening, no download at all...than i try to use android injection with apks that i found on the net , but nothing, i always get INSTALL_FAILED_OLDER_SDK...so now i am stuck i have: fimware version-2.1 update 1,baseband T959UVJFD, kernel 2.6.29 can you tall me should i do?? thx
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Download the clockwork mod recovery file (update.zip) and save it to the internal storage on the phone. Then reboot into recovery and install packages. Might have to do it twice. Then you'll be in CWM recovery. Install from from there.
Sent from my SGH-T959 using XDA
The AIO Vibrant toolbox might be something you need to look at. you can find it here http://forum.xda-developers.com/showthread.php?t=954509
guide
i followed your guide...flashed CM7, than i try to flash Euphoria RM2.1(ICS) and flashing is starting all ok , than after 30 secs i see message 'Random offset 0x302' and it's not going forward with flashing,i pulled out battery and try 2 more times,and there is always the same problem, i'm on CM7 now(and i don't have google play what should i do? can you recoommand me some good and stable gingerbread ROM for Vibrant(if i goona be unable to install ICS Rom) thx
Woodrube said:
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Click to expand...
Click to collapse
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
Click to expand...
Click to collapse
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
stack
man, now i am completly stack, i try to flash slim ics, found the file for vibrant, but it culdn't flash , in the middle it just stoped..and phone is just rebooting it self when i enter cw mod i can't install any other ROM from internal sd, it says no files found ffs now i can't even use phone, i need help emergently
Woodrube said:
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
Click to expand...
Click to collapse
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
odin
ok i get into odin , marked repartiton but is sais fail ??? what should i do now?
Woodrube said:
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
Click to expand...
Click to collapse
If you do get past all of these, but this is unlikely for a normal flash, get either Iczen or chimera.
Sent from my SGH-T959 using xda app-developers app
Hi I am new to the whole modding scene.
My girlfriend is tired of having her phone freeze and lock up, so I decided to load a nice Jelly Bean rom on it for her. She has a Verizon Samsung Fascinate.
I followed this tutorial here:
http://www.youtube.com/watch?v=mDH8NWyikJM
That I found on this roms site www.hellybean.com
I downloaded the 9/25 build.
I followed the tutorial, got it rooted, installed the teacmhacksung.... rom. rebooted and installed the hellybean rom. rebooted, reflashed hellybean again as it says to do. then installed the latest gapps 20120706 signed.zip
rebooted then it went all haywire. It shows the boot logo for hellybean for a split second then keeps booting to the devil recovery menu,:crying: no matter what i do.
I found a tutorial (http://forum.xda-developers.com/showthread.php?t=1238070) section 9.
I followed it until the second time I had to install the cm7 rom. after the second flash it keeps showing the boot menu for cm7 then 2 secs later it reboots constantly.
Good news is that I can get into CWM recovery with no problems (so glad I dont see devil recovery anymore lol )
I dont know what to do from here. I do have a backup but it is at the time of the infinate devil recovery situation, so that wont help me.
Any help at all would be greatly appricated, hell i would be ahppy with going back to stock if possible but I really want to see jelly bean on this thing
Thanks in advance!!
Chris
Not sure what could have happened there, you seem to be on the right track with following directions. I would Odin back to stock and try a different JB rom, such as AOKP or CM10, just follow droidstyle's guide on how to do that step by step.
Crawshayi said:
Not sure what could have happened there, you seem to be on the right track with following directions. I would Odin back to stock and try a different JB rom, such as AOKP or CM10, just follow droidstyle's guide on how to do that step by step.
Click to expand...
Click to collapse
I got it working no problems now. I used odin to go back to stock, re-rooted, and used AOKP 9/25 rom. It runs great, but the pink swagger unicorn has to go. What are some good sites to find boot animations? also are theme packs avaliable for this rom? I see the default 1/1 in the rom manager but nothing else is installed yet.
Thanks for the help
You can disable the boot animation in the rom settings...
As for themes, CM10 themes should work the same. Go here: http://forum.xda-developers.com/showthread.php?p=29455970#post29455970
Also, upgrade to 9/27 because it has the new partition layout with much more internal storage. It runs great with Devil Kernel 1.6.0. That's what I'm on now and it's fast as hell
AOKP milestone 1 seems a lot better than the current build of cm10 on the Fascinate, so I would like to give AOKP a shot. However, the guides say to flash from a cm7 enabled CWM. If I'm on the latest nightly of CM10, would it be ok to just download the latest AOKP and flash it, or should i downgrade to cm7 then back to AOKP
No need to go back to CM7, but you should do a data wipe before switching for sure
I have read up and am quite experienced, especially with samsung flashing and Odin.
I will be flashing a coworkers verizon fascinate which is bone stock 2.3.5
to keep on subject with this thread I would like to go straight to a Jellybean ROM.
can I just... Odin the CWM recovery fixed for CM7, wipe data/cache/dalvik,etc. flash JB ROM & gapps?
Do I need GB bootloaders? shouldnt they already be there? Im not sure of his ext sd card speed class, but it is the stock 16gb ext sd. Will a low class(class 2) really cause so many problems I've read about?
Since I wont have a ton of time I would like to get to JB as quick as possible.
I will be backing up via GoBackup, will we run into trouble restoring? going from GB-->JB ?
also, just to be safe.. factory reset should not wipe the ext. removeable sd correct?
Thanks so much guys..
GT-P6200 user here .. Galaxy Tab Plus 7.0 3G Malaysia... waiting for Note 7! yeah baby!
chrisrotolo said:
I have read up and am quite experienced, especially with samsung flashing and Odin.
I will be flashing a coworkers verizon fascinate which is bone stock 2.3.5
to keep on subject with this thread I would like to go straight to a Jellybean ROM.
can I just... Odin the CWM recovery fixed for CM7, wipe data/cache/dalvik,etc. flash JB ROM & gapps?
Click to expand...
Click to collapse
Yep, although you should still flash the stock EH03 first just to be safe before flashing CWM
chrisrotolo said:
Do I need GB bootloaders? shouldnt they already be there?
Click to expand...
Click to collapse
You don't need them, and no, they won't necessarily be there. You can flash the bootloaders at a different time, but I think if you check 'bootloader update' in Odin while flashing EH03 it should do it (I have not tested this. I flashed them separately).
chrisrotolo said:
Im not sure of his ext sd card speed class, but it is the stock 16gb ext sd. Will a low class(class 2) really cause so many problems I've read about?
Click to expand...
Click to collapse
I don't know. I never had a problem with my stock sd card until I started flashing custom roms, and boom, all of a sudden it had problems mounting in CWM. If you want to play it safe, get a new sd card, because sometimes there aren't any warning signs (I got a 32GB class 10 for $30).
chrisrotolo said:
Since I wont have a ton of time I would like to get to JB as quick as possible.
I will be backing up via GoBackup, will we run into trouble restoring? going from GB-->JB ?
Click to expand...
Click to collapse
You shouldn't have a problem, but then again I've always used Titanium Backup. Never had an issue using TiBu, it's very fast and has a ton of options. Personally, I always do a full data wipe on almost every rom I flash and restore using TiBu and I'm good to go within 15 minutes.
chrisrotolo said:
also, just to be safe.. factory reset should not wipe the ext. removeable sd correct?
Click to expand...
Click to collapse
If you mean photos, music, etc. then no, it won't. One time when I did a reset it did wipe my music, but I think that was when I had my old sd card. My photos were never touched, though.
*USE DROIDSTYLE'S GUIDE*
big thanks @Crawshayi, I should probably use the alpha 2.2 .pit to Odin back stock right?
I thought I also saw a 2.2.2 pit and a v2.3 pit are these any better?
chrisrotolo said:
big thanks @Crawshayi, I should probably use the alpha 2.2 .pit to Odin back stock right?
I thought I also saw a 2.2.2 pit and a v2.3 pit are these any better?
Click to expand...
Click to collapse
Honestly I didn't even know there were different versions of that file, I've always used the 2.2 one from section 4 of droidstyle's guide and never run into any problems. The only purpose of that file (from my understanding) is just to re-partition so I don't think it matters all that much
From my understanding you don't need cwm 4 fixed for cm 7 to flash straight from stock to jb. Only when flashing ics roms. I have had to go back to stock a few times flashing aokp jb builds. And I always step up to jb like this. Odin cwm 4 fixed for cm 7-flash ths build 2- reboot -reboot into recovery vis power menu -flash aokp milestone 6(ics)- flash aokp jb build of choice. (me stone 1 just released). And then devil kernel of choice. Currently running devil 1.6.1. Never had any problems. Going this way. And I prefer to use go back up when restoring. It's slways done me right. Is this all necessary? Idk... But it works. Just sayin...
The devil rode a unicorn named jelly bean
forsakenone said:
From my understanding you don't need cwm 4 fixed for cm 7 to flash straight from stock to jb. Only when flashing ics roms. I have had to go back to stock a few times flashing aokp jb builds. And I always step up to jb like this. Odin cwm 4 fixed for cm 7-flash ths build 2- reboot -reboot into recovery vis power menu -flash aokp milestone 6(ics)- flash aokp jb build of choice. (me stone 1 just released). And then devil kernel of choice. Currently running devil 1.6.1. Never had any problems. Going this way. And I prefer to use go back up when restoring. It's slways done me right. Is this all necessary? Idk... But it works. Just sayin...
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
This has been proven unnecessary, basically the new roms have scripts built in that will re-partition as needed thus removing any need to flash 'over' another rom first. I was the one who actually verified this in droidstyle's guide (check the last few pages) and he has updated the thread to reflect it. If it still makes you feel better to do so... well... rock on because I don't think it hurts anything, but I thought you should know it isn't required.
Let me start off by saying Im far from new to the rooting and roming game. Been through several phones. Never run into this issue.
Note 2 - i605
Team Win Recovery - Up to date
Clockwork Recovery - Up to date
MJ9 Radio from Zif
I am able to install CleanROM and Sophisticated. But when I attempt to install CM11, MeanBean, or Gummy the install fails. It attempts to unzip but always ends with failed. This occurs on both recoveries. I have even tried an alternative recovery. Nothing seems to get it done. Please someone help. Like to note I checked my external SD card for errors. It passed.
Sent from my SCH-I605 using XDA Premium 4 mobile app
General consensus seems to be that philz recovery is currently the recovery of choice for 4.3, id say give that a try
Note2.5
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Jiggabitties said:
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Click to expand...
Click to collapse
Im going to give that a shot. I think it may actually be the thing that sorts this all out. Not hat Phillz is not a good option. But that's the other recovery I already tried. Thinking that maybe the Casual I did was not smooth. As it did hang a couple times and was not as smooth as I would have liked. I am going to reply back when I do it to let everyone know how it turned out. Just in case someone else has the same issues.
:good:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Crotty.Josh said:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Click to expand...
Click to collapse
Hmmmm. Somewhere there's a step that's failing you (obviously). Maybe break down your process, from download to flash, and try to pinpoint where it's going wrong. In my experience the things that have caused an install to fail have been either an incompatible or outdated recovery, bad download (check the MD5), or borked system partition (which is when I Odin'd and re-casualed).
Had issues with CM11 until I ODIN'd back to stock LJB, unlocked bootloader/rooted, updated to latest TWRP 2.6.3.1 via ODIN, wiped all partitions included cache, data, dalvik, system, internal sdcard, external sdcard then adb push CM11 plus gapps and installed. Just make sure you can adb push before wiping everything along with checking file CRC and temporarily disable antivirus.
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Crotty.Josh said:
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Click to expand...
Click to collapse
It's always something small it seems. Good practice is to download the ROM, get it to it's final destination then check the MD5. I always wait until I've moved it to the SD to check the MD5 just in case there was a bad transfer.
I am about at my wits end...Rewind to two days ago...
Order of events:
1. Received my new S4 in the mail a few days ago to replace my old S3. I received the S4 fully updated with the NC5 OTA (yeah, I know, bad juju).
2. So I followed Surge's downgrade thread HERE and am now downgraded to the MK2 build, but with no sound and the telephone/calls app does not work.
3. I then downloaded GooManager and installed the OpenRecovery from TWRP, and it said it installed correctly. However, now I CANNOT GET INTO RECOVERY no matter how I try (via VolUp+Home+Power or via "Reboot into recovery" from the GooManager app). It just goes into Download mode with an error at the top in re that says "Could not do normal boot"
4. At this point the phone just boot loops into Download mode. Cannot go into recovery or the MK2 Rom. I then have to reflash the MK2 downgrade files in order (downgrade, system, cache) in order to get a working phone again and I have now probably done this at least 8 times. It is getting old.
So, I am curious what I need to do now. I have gone through the MK2 downgrade process multiple times and tried again to no avail. I also tried flashing the TWRP .Tar file (directly via Odin) but no luck also --- Is there like a super/clean ODIN file I can use that will also reset the recovery image on the phone? I feel that is my main problem, then I can fix the sound/phone problems after that.
This thing is 10x harder to get on CM than the S3 which I had running CM within 2 hours of ownership. I'd appreciate any help to get me back on path.
FYI - I can install Safestrap 3.71/3.72 and get into those fine, but if I want a chance of running CM I will need a Loki recovery right? If so, I just do not see how I am going to get there.
My ultimate goal is a clean rom, and I was so used to CM on my S3 that I'd hate to part with that, but if there is a Safestrap-friendly ROM that is very clean/similar, then I will take that any day. Ready to be done with this - easiest way out.
--edit--
Found this...can I just follow these steps or is that only for people still on MDK?? http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
There's absolutely no way to get cm, aosp, or twrp on your device .
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
crobs808 said:
Yeah, pretty sure I am convinced of that now. :crying:
So, should I upgrade to the rooted-NC5 (Surge's method), and THEN put a Safestrap-custom-ROM on, or just do it now running rooted-MK2?
Click to expand...
Click to collapse
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Well it depends. If you stay on mk2 you can only run 4.3 roms but there's a lot of them. If you upgrade then you can run 4.4 roms but there's only a couple right now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
crobs808 said:
I definitely want 4.4.x. I found THIS one called PurifieD (port by gogolie) which is supposed to be clean-ish. We'll see: http://www.androidfilehost.com/?fid=23487008491966540
-edit-
^ hmm, no mirrors may try Fox and Hound instead:
http://www.androidfilehost.com/?fid=23487008491966537
^ and again...no mirrors.
Is there a consolidated link list of SS-compatible ROMs for the S4, or do I have to hunt and peck through the forum?
n/m - found a list of 4.3 roms, but it looks like I will have to hunt for 4.4 roms individually.
Conclusion: Going to try this rom: http://forum.xda-developers.com/showthread.php?t=2596654
I think I will sleep well tonight (crosses fingers)
Click to expand...
Click to collapse
only a handful, so not that hard to locate in dev forum. Until hashcode comes out with a safestrap for verizon that enables rom slot creation for custom rom installs on 4.4 base phones I know many of us are staying clear of kitkat.
good luck
So I have not used Safestrap since my Moto X days a few years back, and I am having problems installing a new ROM. Here are my steps, please tell me if things have changed because I got unexpected results.
1. While running stock NC5 (rooted+SS installed), copied custom ROM (SS-friendly FoxHound port by gigili) and SU over to my internal sdcard (do not have an external as I never needed one for the S3)
2. Booted into SS and created a ROM slot in rom-slot1
3. Gave it the nickname FoxHound
4. Selected that rom-slot to be active, then went into advanced Wipe, and did Data, Cache, System, Dalvik
5. Went back to the Install menu so I could install the new ROM but there were no files. Actually, I found out it wiped my StockRom slot even though I have made the rom-slot1 active. Why?
Anyway, now I am back to a wiped stock NC5 and have to do this all over again. Am I supposed to not do step 4 (wipe) after I create the ROM slot? and Am I supposed to just install the custom rom in the Stock slot?
Ugg forget it. I now tried flashing the custom ROM on the safe side without doing the WIPE step and just got a rom that looked identical to the stock except that DATA was broken. Forget this - I guess I just have to live with stock rooted, and modify/freeze apps.