Related
Well....I think I might have done something really stupid. It should be obvious at the moment that I didn't understand completely what I was doing.
I just picked up my SGSII today from AT&T. In reading around I had hopes of a new ROM as I was very happy with CM on my captivate....unfortunately while in the process I followed instructions from an (obviously) european version of the phone and installed the KG6 modem....now I have no data connection.
I'm feeling really foolish...is there any way that I can get the stock modem for the AT&T U.S. Galaxy S2? Any help would be greatly appreciated.
Anybody? My phone is completely non-functional at the moment.
I've learned my lesson; I'll leave the modding to the more adept, I just need to get my phone back.
Try the stock plus root rom for odin/heimdall and that should over write the modem you flashed
Sent from my SAMSUNG-SGH-I777 using xda premium
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Entropy512 said:
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Click to expand...
Click to collapse
What would be the easiest way, If possible, to install european ROMS on the ATT version? Maybe, install the ROM without their kernel and modem and replace them AT&T's ?
Entropy512 said:
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Click to expand...
Click to collapse
Thank you! Thank you! Thank you!
Donation coming your way.
Thank you!
daraj said:
What would be the easiest way, If possible, to install european ROMS on the ATT version? Maybe, install the ROM without their kernel and modem and replace them AT&T's ?
Click to expand...
Click to collapse
I believe that alone should work - I haven't had time to test yet.
cgrums said:
Well....I think I might have done something really stupid. It should be obvious at the moment that I didn't understand completely what I was doing.
I just picked up my SGSII today from AT&T. In reading around I had hopes of a new ROM as I was very happy with CM on my captivate....unfortunately while in the process I followed instructions from an (obviously) european version of the phone and installed the KG6 modem....now I have no data connection.
I'm feeling really foolish...is there any way that I can get the stock modem for the AT&T U.S. Galaxy S2? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Feeling kinda foolish... I did the same thing yesterday AFTER I flashed the wrong kernel. (european kernel without proper button support) then everything went to hell, now I am back to the proper kernel, and the deoxed att firmware from the guide here on the forum... i just need the modem up and running with the right firmware and Ill have a working phone again
jdip1978 said:
Feeling kinda foolish... I did the same thing yesterday AFTER I flashed the wrong kernel. (european kernel without proper button support) then everything went to hell, now I am back to the proper kernel, and the deoxed att firmware from the guide here on the forum... i just need the modem up and running with the right firmware and Ill have a working phone again
Click to expand...
Click to collapse
I got all excited when my brother got his gs2 and I flashed a euro rom before I realized what I had done. I used entropy's stock package to get him fixed. Then he calls me from home and starts *****ing about how he can't use data unless he's on wireless. I put 2+2 together.
I am, like the others here, super eager to get that modem file when you post it. It would be a huge help. If it's not too much work on your part entropy, could you post a cwm version of the modem as well? I'd rather not have to flash him back to stock again just to fix the modem.
He's an iphone expat so I'm trying to make his android life smooth as possible.
I'm going to get home around 6 PM Eastern.
Initially I'm going to post up a Heimdall (and hopefully also Odin) flashable image of just the modem binary for those in a hurry, then I'll work on a CWM zip (need to find a reference one to pick apart in case it's different from the Infuse), then I'll upload a new more complete "unbrick".
Thanks for the donation cgrums.
OK, here's an emergency flash package for modem recovery - http://www.multiupload.com/JTFK1K1FOA
It's just a little too large to be an XDA attachment, sorry if multiupload is a problem for you.
It contains both a raw modem.bin, and a .tar file containing modem.bin (yes, redundant!)
It is NOT a CWM-flashable ZIP. Repeat, do NOT try to flash this ZIP in CWM. Seriously, it won't work!
The following method for flashing the modem IS tested:
Unzip the attached package
Use Heimdall to flash from the command line
Code:
heimdall flash --modem modem.bin
The following method for flashing the modem should work but is NOT tested:
Use Odin to flash the contained .tar file, using the Phone slot for the .tar
Man, before I even leave work! Awesome! Thanks again!
I made an error above - I believe in Odin, modem has to be in the Phone slot not PDA.
As I said in the post above - Heimdall is tested, Odin is not.
As to CWM - the maintainer of the I9100 modem collection frowns upon CWM for modem flashing - http://forum.xda-developers.com/showthread.php?t=1131950&page=2 . It sounds like CWM-flashing of modems might have issues on our device, I haven't had time to investigate but right now I'm going to trust pulser_g2's judgement for until I have more time to figure out GS2-isms of modem flashing. I've got a ton of stuff to do and I'm going to drop CWM-flashing of modems in priority for now since it should rarely be needed.
Entropy512 said:
I made an error above - I believe in Odin, modem has to be in the Phone slot not PDA.
As I said in the post above - Heimdall is tested, Odin is not.
As to CWM - the maintainer of the I9100 modem collection frowns upon CWM for modem flashing - http://forum.xda-developers.com/showthread.php?t=1131950&page=2 . It sounds like CWM-flashing of modems might have issues on our device, I haven't had time to investigate but right now I'm going to trust pulser_g2's judgement for until I have more time to figure out GS2-isms of modem flashing. I've got a ton of stuff to do and I'm going to drop CWM-flashing of modems in priority for now since it should rarely be needed.
Click to expand...
Click to collapse
I flashed the tar in odin using phone, the phone rebooted, but it will only make calls. The phone cannot use the internet when the wifi is off. Do you have any suggestions? I am going to try flashing your entire recovery image when you update it tonight.
What does your baseband version say now? If it flashed properly it should say UCKH7.
If it doesn't, it didn't flash for some reason. I know it flashes properly with heimdall, odin is kind of untested.
Entropy512 said:
What does your baseband version say now? If it flashed properly it should say UCKH7.
If it doesn't, it didn't flash for some reason. I know it flashes properly with heimdall, odin is kind of untested.
Click to expand...
Click to collapse
I had my brother do the factory reset, wiping the user data. That seemed to fix it (although we did flash your modem prior). Thanks so much!
I am happy to report that I am on my way back to functionality!
I've noticed a difference in connectivity though. At times, typically out-of-doors, I get decent signal strength and HSPA+ connection. Call service is a bit spottier than I remember it before the hijinks.
Inisde buildings is a completely different story...I can't seem to maintain a data connection of any type.
My baseband shows I777UCKH7 so I believe the flash went well. I'm planning to flash back to stock to get a good starting point going forward.
Anybody else experiencing similar issues? Thoughts?
This community is awesome!
I think someone did indicate that things were funky until they wiped - not sure though.
One click + CWM ICScrewed = in call audio problem
Hi I used your on click root kernel and then used CWM to flash the ICScrewed ROM .zip file.
Now I am having a problem where when I make or receive a call there is no audio. I still have data and wifi connectivity though it seems.
Could it be a problem with my modem? If so how do I flash another and where can I find the appropriate one?
Thanks, and sorry I cannot post on the ICScrewed page as I do not have permission to post in development yet.
jgordo32 said:
Hi I used your on click root kernel and then used CWM to flash the ICScrewed ROM .zip file.
Now I am having a problem where when I make or receive a call there is no audio. I still have data and wifi connectivity though it seems.
Could it be a problem with my modem? If so how do I flash another and where can I find the appropriate one?
Thanks, and sorry I cannot post on the ICScrewed page as I do not have permission to post in development yet.
Click to expand...
Click to collapse
I have no "one click" kernel. Any "one clicks" are repackaged by someone else and I have no idea what they contain in many cases.
My apologies if this has been asked before, but I've spent hours searching and think I've done a better job of confusing myself, than answering my question.
I've rooted my wife's Samsung Fascinate, using Super One Click and removed all annoyances such as the Verizon bloat ware and got add blocker installed, etc. The point on doing so, was also to improve battery life, backup the ROM and some of the other associated advantages with rooting. One of my main goals was to also install a custom ROM on her phone, as the factory ROM is very flaky. It receives emails, then doesn't. It sends a text, then can't minutes later. It's been a great phone HW wise, but just junk as far as the OS.
Thus far, all attempts to backup the factory (modified) ROM has failed, which evidently is part of the limitation with the stock ROM. At this point, she's so frustrated (me too) with her phone, that it's time to get serious.
So, my confusion stems from varying reports regarding what the proper steps are to install a new ROM. On my Thunderbolt, I simply used CWM to install and backup/restore my ROMs as needed. This doesn't seem to be the case with the Fascinate and there's varying reports of whether this can even be done if Super One Click was used.
Has anyone had experience with flashing new ROMs after the phone was rooted and if so, by what method?
Her current ROM details are:
Firmware
2.2.2
Baseband
S:i500.04 V.ED05
Kernel
2.6.32.9
Build
SCH-I500.ED05
Thanks in advance.
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cm7 zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
droidstyle said:
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cwm zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
Click to expand...
Click to collapse
Okay, that makes a lot more sense now. Thanks for the quick reply.
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
ibsk8 said:
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
Click to expand...
Click to collapse
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
droidstyle said:
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
Click to expand...
Click to collapse
I never could get to the ROM flashing part. Every time I tried I got the same set of errors as when trying to backup the original ROM. I did manage to get the CWM 4 fix applied through ODIN and it said successful, but nothing really changed and my attempts to flash the new ROM still failed.
I searched around this forum and others and found another file to flash and things went very badly. The flash was moving super slow and I left the phone, so I wouldn't be tempted to do anything stupid and after an hour, it was at the same point. When I rebooted the phone, I got a sad face icon only. No Samsung logo or anything.
Luckily, I was able to re flash the stock rom, but after messing with it for 4 hours and getting nowhere, I decided the stock ROM was good enough for now. I have no idea why this phone is so pesky and read how some folks had to ref lash the stock ROM, before being able to flash a new ROM. I made one final attempt to do so and got the same error as the first time, so that was enough for that day. I don't recall exactly what the error said at this point, but I had blue text, followed by orange, which I think said something to the fact that is was unable to verify the package, followed by red text showing the failures.
Sorry there's no more detail than that for now. I may try this again in the future, but as mentioned this is the wife's phone, so I can't take nearly the liberties with it as I could my own.
If anyone has any ideas on what I may be able to try next, that would be great. If not, I may keep digging on this forum (a very helpful place indeed) and see what the options may be.
Thanks everyone for your help.
refer to section 3 of my guide and follow those steps. for some reason certain fascinates have trouble flashing mtd roms when starting from ed05. I have to start with dl09 eclair then flash cm7. look in page 2 of this section for my guide. all files needed can be found there aswell. good luck!
Hi all,
I need help with my wife's Note i717.
I was on a custom ICS ROM, and I tried to flash CM10 ROM.
I've been flashing ROMs for a few years now on various phone, so this is no different ... flashing went smooth, but after flash CM10 I discovered the phone would freeze on certain screen ... like when I go to Task Manager, or when I hit certain menu's.
After a bit of searching, seems like a few others have the same problem ... I figure maybe ROM isn't very stable, so I did a NANDOID restore to my ICS ROM, and all is good.
Tried to flash again, this time I also wiped my internal SD, and flashed a new UCLF6 radio when I flashed a newer version of CM10.
This is when all hell breaks loose. I run into even more severe problems of freezing after flashing CM10, and I can't even make phone calls anymore as the phone I call would ring, but the Note would freeze to a point the other side can't hear me.
So again I did a NANDOID restore of my ICS ROM, but this time I'm not so lucky. After restore, my Note is VERY SLOW ... it'd take seconds going from one menu to the other, hitting "OK" buttons and the phone freezes for a few seconds before it goes to the next menu.
So I did a clean wipe, starting with a ODIN flashed the stock AT&T image. But rightaway after flashing the AT&T stock ODIN image, after the phone boots up again I knew I got the same problem. Even on the setup wizard by AT&T the phone reacts VERY SLOW like before, or downright freezes.
I followed up with rooting it, flashing CWM, then TWRP recovery, and tried to flash different ROMs ... all give me the same problem. I also tried NANDROID restore again, but same thing!
Any suggestion on what I can do next? I thought flashing AT&T ODIN is already the cleanest wipe I can do to restore my phone ... any help is appreciated!!!
did you make sure you wiped cache, davilik cache and did a factory reset? if you didnt do all 3 then flash again sounds like a dirty flash is what you have been doing
Yes always wipe cache, dalvik and factory reset 3 times before flashing any rom, not to mention I thought ODIN flashing stock rom would get me back to square 1 regardless of previous flashing?
Try using Kies recovery through your computer.
-Once you go NOTE, you'd say 4 inches a Joke
[Lady]: "How do you carry that huge phone in your pocket?"
[Note User]: "I'm used to having huge stuff in my pants"
Kies recovery eh? I can give it a try but how is that different from ODIN?
I had similar issues this past summer...I would try various roms and get crashing and instability, calling issues, etc.
Make absolutely sure that your modem is flashed...I had to do it via Odin. Get a stock one for your carrier. I assumed that when I flashed a new rom that the modem got updated as well but I was wrong. I went from FJs rom to CM10 and got the same issues as you. Went back to FJs rom and the issues persisted. Did a nandroid restore to stock GB and still had the same issues. Then I used the 'muglf4' version for my carrier (Bell), flashed the modem separately and all went well since.
Might not be your issue of course but its something to verify (that the modem and kernel are being flashed).
chriskwarren said:
I had similar issues this past summer...I would try various roms and get crashing and instability, calling issues, etc.
Make absolutely sure that your modem is flashed...I had to do it via Odin. Get a stock one for your carrier. I assumed that when I flashed a new rom that the modem got updated as well but I was wrong. I went from FJs rom to CM10 and got the same issues as you. Went back to FJs rom and the issues persisted. Did a nandroid restore to stock GB and still had the same issues. Then I used the 'muglf4' version for my carrier (Bell), flashed the modem separately and all went well since.
Might not be your issue of course but its something to verify (that the modem and kernel are being flashed).
Click to expand...
Click to collapse
Can you point me to where I can find the tar file for MGLF4 radio? mine is also a Bell unit and I want to ODIN flash the radio to see if it would fix my problems.
Thanks!
chriskwarren has the answer. Your LF6 radio download was corrupted. This happens frequently, so just redownload it and flash it again either with odin or CWM.
If the phone is at&t use LF6, if Bell use the Bell radio.
chriskwarren said:
I had similar issues this past summer...I would try various roms and get crashing and instability, calling issues, etc.
Make absolutely sure that your modem is flashed...I had to do it via Odin. Get a stock one for your carrier. I assumed that when I flashed a new rom that the modem got updated as well but I was wrong. I went from FJs rom to CM10 and got the same issues as you. Went back to FJs rom and the issues persisted. Did a nandroid restore to stock GB and still had the same issues. Then I used the 'muglf4' version for my carrier (Bell), flashed the modem separately and all went well since.
Might not be your issue of course but its something to verify (that the modem and kernel are being flashed).
Click to expand...
Click to collapse
It could be, but I can't seem to find the Bell radio for ODIN flashing, even with a lot of searching ... if someone can point me to it it'll be greatly appreciated.
BTW, having done some more tests I think the problems are caused by either a corrupted radio and/or corrupted kernel.
- If I run the phone in airplane mode, without turning on the radio, the phone works fine, for the most part
- What guarantees the phone to freeze and have all kinds of problems is if I try to make a phone call. The phone will either give me "Call cannot be sent" error message, or it will dial, the other number will ring, but can't hear a word at all, and the Note will freeze.
I have tried flashing different radio's I find, but most radios I find are CWM ZIPs, not ODIN TARs. I don't know if CWM can't do a 'complete overwrite' or something, but flashing different radio's don't help. I want to try to flash radio via ODIN, but can only find 1 appropriate ODIN file, and that tar file might be corrupted in itself because it fails trying to flash it through ODIN.
I suspect it may also be a corrupted kernel, because in trying to make CM10 work I flashed both a different radio and a different kernel, which causes all the problems I have.
I have a Bell Note i717M ... what is the safest radio and kernel I can use with ICS ROM? If someone can point me or send me the ODIN tar's it will be greatly appreciated. I searched and searched but can't find much for ODIN on xda!
Check the "note super everything thread "....
At the top of the general section ...
About half way down the page you will see the modem section .....and bell is there ....g
Try a stock kernel. If else fails, try a bell modem.
-Once you go NOTE, you'd say 4 inches a Joke
[Lady]: "How do you carry that huge phone in your pocket?"
[Note User]: "I'm used to having huge stuff in my pants"
SKyRocKeting727 said:
Try a stock kernel. If else fails, try a bell modem.
-Once you go NOTE, you'd say 4 inches a Joke
[Lady]: "How do you carry that huge phone in your pocket?"
[Note User]: "I'm used to having huge stuff in my pants"
Click to expand...
Click to collapse
Thanks for all the advices guys.
I have tried different radio's, all of them CWM zips. None of them seems to work ... the supposedly "stock" kernel makes it worse actually.
I wonder if ODIN would flash 'cleaner' ... but so far, can't find any ODIN modem.
As stated earlier, your modem you flashed was corrupted and you need the Bell modem.
If it is in CWM zip format, unzip the file on your pc, and use the mdm.bin or modem.bin file in the unzipped folder. That goes in the Phone slot of Odin3.
rangercaptain said:
As stated earlier, your modem you flashed was corrupted and you need the Bell modem.
If it is in CWM zip format, unzip the file on your pc, and use the mdm.bin or modem.bin file in the unzipped folder. That goes in the Phone slot of Odin3.
Click to expand...
Click to collapse
Ahhhh I see ... thanks a lot. I'll try that tonight.
Thanks a lot that did the trick!! As soon as I flashed modem.bin everything works.
How about amss.bin? Do I need to flash it too?
Noooo.
Similar issue - Note very sluggish
Hey guys, I'm having a similar issue as the OP. I've tried updating my Note to ICS without success and was working fine on stock ATT GB. I tried again today to update to ICS and failed, reverted to stock ATT GB from here: http://forum.xda-developers.com/showthread.php?t=1506330, and now my Note is sluggish as heck!
Right at the ATT setup flow, the touchscreen seems very unresponsive and screen taps take a few seconds to register. The soft keys are pretty much unusable - if I hit back or home, the whole thing freezes and randomly resets.
I made sure I wiped cache, wiped Dalvik cache and factory reset and then flashed the stock ROM again, but same thing. I found the stock ATT modem and flashed that as well by putting mdm.bin in the Phone field in Odin, but no luck...
Any idea what else could be wrong here?
Appreciate any help guys! I'm close to having a large ungainly paperweight here...
I am at my wits end and hopefully one of you can help.
The phone in question is is the AT&T Galaxy S2 SGH i777. It was running a jellybean ROM and there were problems with the GPS and google maps not working at all about four months ago. Not sure what happened. I went through the usual process of putting a ROM on the SD card, wiping cache/davlik and installing, then installing the gapp.apk for that rom. Everything was fine. Except wireless. Wireless would not connect. Just wouldn't do it. Googled forever, found no real solution. Thinking it was the rom I reinstalled. Wash rinse repeat. Same issue. Thinking it was a bad rom I proceeded to go through about six more roms. Same issue. Four hours later I resolved to unroot, take it back to stock. Took it back to stop with no issues. Wireless worked just fine. Everything was great. Rooted it again with the stock gingerbread. Wireless worked fine. Made a backup of the rom and was feeling lucky so I installed the Carbon ROM from the Sept 29th post on galaxys2root.com (I don't know if you guys allow linking here) and the gapps from that post. I boot. Everything is looking fine....yet the wireless doesn't work. This has been consistent across every rom I installed. I am quitting for the night.
It is currently running android 4.3, kernel version 3.064-CM-gbc8f4c9 (if that helps). The phone service is fine and makes/receives calls/texts just fine. No other blaring issues. Worth pointing out: all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect.
I had this phone for years (girlfriend has it now) and Rom'd it many times with next to no issues, especially not with wireless. I don't understand why it was working fine on a JB rom and trying to change rom suddenly screwed the wireless.
I am literally at my wits end and it's probably the result of me being an idiot somehow and missing something. Can anyone suggest a fix?
God bless in advance.
fifthmanstanding said:
[...]all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect. [...]Can anyone suggest a fix?
God bless in advance.
Click to expand...
Click to collapse
My advice is to avoid downloading ROMS from galaxys2root.com
If you want the insider scoop, keep up at xda or at each group's G+ community.
if you want:
-Carbon; get it from: http://download.carbon-rom.com/?dir=./i777/nightly
-Cyanogenmod; get it from http://download.cyanogenmod.org/?device=i777
-Omni; get it from http://dl.omnirom.org/i777/
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
cyril279 said:
My advice is to avoid downloading ROMS from galaxys2root
If you want the insider scoop, keep up at xda or at each group's G+ community.
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
Click to expand...
Click to collapse
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
fifthmanstanding said:
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
Click to expand...
Click to collapse
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
creepyncrawly said:
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
Click to expand...
Click to collapse
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
fifthmanstanding said:
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
Click to expand...
Click to collapse
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
creepyncrawly said:
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
Click to expand...
Click to collapse
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
fifthmanstanding said:
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
Click to expand...
Click to collapse
hint: http://forum.xda-developers.com/member.php?u=2916435
cyril279 said:
hint: http://forum.xda-developers.com/member.php?u=2916435
Click to expand...
Click to collapse
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
fifthmanstanding said:
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
cyril279 said:
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
Click to expand...
Click to collapse
I agree.
Which links?
I read through the notes on the repository:
There is always some risk involved when flashing bootloaders and Param.lfs. Please don't flash this unless you absolutely need to.
"This is the complete stock UCMD8 Binaries downloaded from samfirmware at sammobile.com. Please note, this package contains boot.bin, sbl.bin and param.lfs, plus cache.img, factoryfs.img, hidden.img, modem.bin and zImage.I777UCMD8 Full Odin Flashable tar: I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z 427.02 MB (Contains I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5)
(MD5: 307cc8fcbb8f220d3ae75d387569da40)"
And I'm downloading the file now. I've used odin before so I assume that goes by the standard process ( download mode, open, pda, select file, hit start, wait, finish) and then I went here http://forum.xda-developers.com/showthread.php?t=2130276 and he says "Version 1.3: Add Aragorn and Legolas exploits" so I assume based on Creepy's previous statement that's the one I need. I would download the apk and run it.
What am I missing?
Yeah I just installed the tar file using odin and before I even get to rooting process, wireless isn't working. This time it sees the network, password goes in as usual, it attempts to obtain IP address and says that forever. Never connects. Then goes back to scanning. Then attempts to connect again. No dice. No other device in the home has this issue. I'm out of ideas.
Edit:
Yeah I just tried again, using odin, took it back to stock, wireless works, using odin took it to stock with root, wireless works, using the tar file located here http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 took it to I777UCMD8 Stock Binary. Wireless is not working.
Does anyone have any insight? I've got a pissed off girlfriend an a perment dent in my desk from my head.
update: took it back to i777 UCMD8 with odin, just for kicks I tethered it to my nexus 4. Works fine. Turned off data, disconnected the wireless just to be sure. Turned it back on. Working fine. Still will not connect to my router. This would imply there is a router issue and I have less knowledge of how/why that would work. Thoughts?
fifthmanstanding said:
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Edit: Failed to click on the latest page of the thread before I posted this. Yes, it sounds like an issue with your router, perhaps. So find other routers and test the wifi. If that's the issue, then the other roms will probably also work on a different router.
creepyncrawly said:
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Click to expand...
Click to collapse
Yeah I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
EDITosted before I saw your edit
fifthmanstanding said:
Yeah as stated, I'm familiar with odin. I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
Click to expand...
Click to collapse
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
creepyncrawly said:
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
Click to expand...
Click to collapse
Fair enough.
I've downloaded the AJK no swap from here http://forum.xda-developers.com/showthread.php?t=2110542
I've downloaded Mobile Odin lite and am going to work on that.
Assuming it all works out and I get to make a backup. Where to next? This rom is terrible. What do you recommend for a jellybean experience as stock nexus 4 as possible.
Yeah the ajk no swap 4.9 is giving me a consistent java error that kills the download. I attempted to move it to the sd card and open in odin lite but am not seeing it on the card. Am I doing something wrong?
Edit. I tried connecting the phone to the computer and opening in explorer, following directions from here http://forum.xda-developers.com/showthread.php?t=2197157 , created a folder and attempted to drop the zip in there and it's not letting me drop files to the phone. nor to the sd card.
Edit 2: suddenly file xfer is working again. I dropped the .zip to the new folder on the internal and also created a new folder with the boot, METAINF folder and system folder that shows when you unzip. It's not detecting the zip file so I assume you're supposed to select the Boot file. I select it. Nothing happens.
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
fifthmanstanding said:
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
Click to expand...
Click to collapse
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
creepyncrawly said:
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
Click to expand...
Click to collapse
Ok by the looks of it that worked. Thanks for that.
In terms of roms I'm looking for something stable, jelly bean and non-touchwiz. As close to possible as nexus 4's jelly bean. Nothing comes to mind?
Edit: apparently the home key now no longer works properly, hitt it brings up a selection box and selects whatever is the left most side whether it's 'apps' tab or an icon on the home screen. Also the search magnifying glass soft key doesn't work, same function as the home key it seems.
Edit 2: And the wireless is no longer working. Was working fine before flashing the kernel. Put the phone directly on top of the router. It shows the network, allows for password input, says 'connecting' and never ever connects. Then it drops and goes to 'out of range'...sitting directly on the router. Just for kicks, like last time, I enabled the hotspot on my N4 and it connected fine. I attempted to connect to the router again and it does the same...connecting and drops to out of range. Sigh.
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