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
Hi all,
Some background information, I was using team eos nightlies and I wanted to change the rom to see whether if others are any better, so i did cleared the cache/delvik cache and as well as did a factory wipe. Then i installed the the that I wanted to try out, the Energy rom, however, after flashing, I couldn't get past the asus spalsh screen, I can still go back to the twrp recovery though.
I tried flashing back my original team eos nightly.. and it booted without any problem.
Anyone knows if i'm missing any step to flashing a new rom?
ZeitiaX said:
Hi all,
Some background information, I was using team eos nightlies and I wanted to change the rom to see whether if others are any better, so i did cleared the cache/delvik cache and as well as did a factory wipe. Then i installed the the that I wanted to try out, the Energy rom, however, after flashing, I couldn't get past the asus spalsh screen, I can still go back to the twrp recovery though.
I tried flashing back my original team eos nightly.. and it booted without any problem.
Anyone knows if i'm missing any step to flashing a new rom?
Click to expand...
Click to collapse
Sounds to me like your on the older ICS bootloader and the other roms you've tried are using the JB bootloader (lucky you havnt bricked your device)
You need to upgrade the Bootloader first in order to install these roms but BEWARE, once you upgrade the bootloader, you cannot go back to the ICS bootloader or roms.
Unless you have backed up NVFlash and you restore your device/bootloader with NVFlash.
Now would be a good time to do your NVFlash backup if you havnt already, then go from there.
Click the link for a guide on upgrading the bootloader by Flumpster in the Androwook thread ... there is also a link for the NVFlash guide
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
Danny-B- said:
Sounds to me like your on the older ICS bootloader and the other roms you've tried are using the JB bootloader (lucky you havnt bricked your device)
You need to upgrade the Bootloader first in order to install these roms but BEWARE, once you upgrade the bootloader, you cannot go back to the ICS bootloader or roms.
Unless you have backed up NVFlash and you restore your device/bootloader with NVFlash.
Now would be a good time to do your NVFlash backup if you havnt already, then go from there.
Click the link for a guide on upgrading the bootloader by Flumpster in the Androwook thread ... there is also a link for the NVFlash guide
http://forum.xda-developers.com/showpost.php?p=34938455&postcount=6212
Click to expand...
Click to collapse
Ohhh is it. I don't remember anything about the bootloader so I just assumed that since I was on TeamEos JB nightlies, then I'm on JB bl.
I went to flash many other roms to tried too. Must've been really lucky then.
Thanks for the help, I'll go try it out.
Howdy all,
I've been out of the loop for a bit with my TFP since the screen/digitizer broke.
When I last had it working I had installed Rooted_CWM_SparkyAsusStock_9.4.2.28-signed.
If I wanted to change the ROM, would I go back to stock with the same Android version, then update? I do have my tablet NVFlashed and the blobs all saved, but I'd like to avoid any possible brick.
Head on over to the androwook thread and search a ways back. Team Androwook had posted a guide to upgrading to the Jelly Bean boot loader that had an easy flashable zip for ya.
Nightpath said:
Howdy all,
I've been out of the loop for a bit with my TFP since the screen/digitizer broke.
When I last had it working I had installed Rooted_CWM_SparkyAsusStock_9.4.2.28-signed.
If I wanted to change the ROM, would I go back to stock with the same Android version, then update? I do have my tablet NVFlashed and the blobs all saved, but I'd like to avoid any possible brick.
Click to expand...
Click to collapse
If you have NVFlash you can never brick.
Go to second post here http://forum.xda-developers.com/showthread.php?t=1674827 and follow "Upgrade instructions for ICS"
So I must be on ICS now, so I'd want to upgrade to JB correct?
I take it I can just jump from whatever I have installed now to one of the modded JB releases? Which one is considered the best so far? Stock, Androwook, Cyanogen?
Only want to watch movies, internet and a few games.
I was on stock ICS when I got nvFlash access and started throwing roms at my prime. I basically had to update to the JB bootloader before I could flash any JB-based rom. As far as I remember, there's no going back from the JB bootloader.
I simply flashed the stock JB firmware which includes the JB bootloader from this thread:
http://forum.xda-developers.com/showthread.php?t=1927494
(this is the WW version, there's another thread for the US version, not that I think it matters)
This updates bootloader/rom/recovery (stock/stock/TWRP) to JB, and from there you can flash anything JB-based. Mismatching rom/bootloader will not work (i.e if one is ICS and the other is JB or visa versa) then you won't boot. I did this, but I already had nvFlash so I wasn't worried.
I have NVFlash already done...waiting for my LCD replacement screen so I can put my TFP back together and use it again.
OK, could I use the stock Asus JB to update, then flash over to Androw00k?
I'm already rooted, nvflashed, etc.
How in the hell do I boot into recovery mode with TWRP?? Any ideas, I'm on ICS
Nightpath said:
How in the hell do I boot into recovery mode with TWRP?? Any ideas, I'm on ICS
Click to expand...
Click to collapse
It's nothing to do with twrp. I'm guessing you have now flashed the jellybean bootloader.
Hold down volume down and power and when the 4 icons appear press volume up on the first one "rck"
Or have you flashed the wrong version of twrp and put the jellybean twrp on ICS?
flumpster said:
It's nothing to do with twrp. I'm guessing you have now flashed the jellybean bootloader.
Hold down volume down and power and when the 4 icons appear press volume up on the first one "rck"
Or have you flashed the wrong version of twrp and put the jellybean twrp on ICS?
Click to expand...
Click to collapse
I flashed twrp but only have 3 icons when I do pwr + vol down. Data Reset / Fastboot / Android.
I'm going to need a How-To for idiots guide. I've been working long hours, not a lot of time off...and I'm tired as hell all the time. I really need assistance.
Nightpath said:
I flashed twrp but only have 3 icons when I do pwr + vol down. Data Reset / Fastboot / Android.
I'm going to need a How-To for idiots guide. I've been working long hours, not a lot of time off...and I'm tired as hell all the time. I really need assistance.
Click to expand...
Click to collapse
Think I have it all figured out...Androwook installing now with JB
TWRP was giving me some massive problems, had to work around it and reinstall a few times before updates would work.
Hi people,
I need your urgent help!
My TF201 was running on hairy rom.
I wanted to update/change to CM10 latest nightly (I really dislike the asus crap).
I tried several times via TWRP and goo manager but it would boot up (only saw the asus logo).
Then I thought it might have been the recovery.
I booted in fastboot mode and flashed CWM (recovery-clockwork-touch-5.8.1.8-tf201.img and md5 was correct).
Looked fine.
Then I wanted to reboot into recovery but it simply did not.
Tried it 5/6 times but nothing.
So I booted up again in fastboot mode and flashed the latest TWRP (2.3.3).
Again I rebooted to recovery but it still failed.
I do not have NVflash because I bought this device 2nd hand and it was allready upgraded to JB bootloader so I could us NV.
Is my device bricked? Is there a way to solve this?
Please help me but keep in mind, I'm a "noob" (do know stuff but not very much).
Thnx in advance!
Ralph aka TwistedNL
Re: [Q] Help! can get in recovery!
I'm not sure but it sounds a little like you flashed rom for ics bl but I'm not sure as ypu can still get to recovery and fastboot. Btw post questions to Q&A!!!
Edit: What version of hairybean were you running? And did you wipe?
Sent from my sgs2
Makrilli said:
I'm not sure but it sounds a little like you flashed rom for ics bl but I'm not sure as ypu can still get to recovery and fastboot. Btw post questions to Q&A!!!
Sent from my sgs2
Click to expand...
Click to collapse
I can get in fastboot mode but can't get in recovery mode. The latest nightlies are JB roms right?
If I can get in recovery, I could restore nandroid I made before starting this journey.
Could the custom build TWRP version from hairy be the reason? As far as I know, the only difference are cosmetics (othe backgropund and buttons, like a theme)
Sorry about the wrong section for my question. Am to pissed atm so I did not look good where I should have asked this.
Can my question be moved by somebody?
Re: [Q] Help! can get in recovery!
Well I don't know about the CM10 nightlies. But most likely that custom twrp didn't do it. I'm not an expeet in any of this stuff. Also what happens when you go to recovery? And only mods can move threads to another section
Also I edited my first post but ypu answered too quickly What version of hairu bean were tou running and did you wipe when you flashed cm10?
Sent from my sgs2
twistednl said:
Hi people,
I need your urgent help!
My TF201 was running on hairy rom.
I wanted to update/change to CM10 latest nightly (I really dislike the asus crap).
I tried several times via TWRP and goo manager but it would boot up (only saw the asus logo).
Then I thought it might have been the recovery.
I booted in fastboot mode and flashed CWM (recovery-clockwork-touch-5.8.1.8-tf201.img and md5 was correct).
Looked fine.
Then I wanted to reboot into recovery but it simply did not.
Tried it 5/6 times but nothing.
So I booted up again in fastboot mode and flashed the latest TWRP (2.3.3).
Again I rebooted to recovery but it still failed.
I do not have NVflash because I bought this device 2nd hand and it was allready upgraded to JB bootloader so I could us NV.
Is my device bricked? Is there a way to solve this?
Please help me but keep in mind, I'm a "noob" (do know stuff but not very much).
Thnx in advance!
Ralph aka TwistedNL
Click to expand...
Click to collapse
There is not a version of CWM that is for the Jellybean bootloader. The quickest way to hard brick your device is to install a recovery meant for ICS onto Jellybean bootloader.
If you can still access fastboot then you have a chance, if you cannot still access fastboot then I'm sorry but flashing CWM has hard bricked you.
Then I'm a lucky bastard!
Managed to reflash stock TWRP (without the theme).
After 2 times flashing, I could boot in recovery again. The nandroid was copied to external SD which I could restore and the Prime is running again!
I think I'll keep it on Hairy (which runs fine on 1.7 kernel) and will wait to the promised update (around november 2012) of Asus to 4.2 cause I really like the multi user option
Thnx all for helping me out!
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