Hello all! Long-time prowler, 1st time poster.
Finally got my hands on a GS2. Very pleased with it. I've always been interested in custom roms and kernels, as I've spent dozens of hours researching how-to's and don't-do's, but I've been hesitant to take the plunge due to the risk and 1st-time unfamiliarity.
That is, until now. I was following the rooting instructions here: http://forum.xda-developers.com/showthread.php?t=1311081
Specifically, point 2c using Entropy's root method (phone had the OTA UCKK6 update) to revert back to UCKH7 2.3.4. Everything went as expected, root was achieved (2.3.4, kernel 2.6.35.7, superuser, etc.), but wifi is DOA. It appears that everything else is working fine, but when I attempt to turn on wifi, it starts scanning for a few seconds and then shuts itself off.
I've searched both XDA and Google on the topic, and while it seems to be a common occurrence, there is very little information in the way of solutions. The closest I've come to has been this thread: http://forum.xda-developers.com/showthread.php?t=1364039&highlight=wifi+broke
Appears that a full un-root is necessary? I just wanted to double-check that there isn't some silly little thing I'm missing or a more streamlined solution.
Again, noob here. Any advice or input is greatly appreciated. Looking forward to trying out some roms and kernels and learning more from the community!
I've got the same problem ... kinda...I followed the same steps to root, WiFi was fine after that, but when I flashed CWM-recovery, WiFi was borked. This is where I usually shhot myself in the foot ( as I appear to have done again). After more reading and research, I found that the ROM I was planning to flash (UnNamed) did its own kernel update so I figured that it may patch my WiFi problem.
Sadly it did not and now I have NO radio at all. (Cellular, data or WiFi). I get FC's from com.android.phone. (over and over... every 5-7 seconds.)
Hmmmmmm...
Flash stock again just to make sure it got everything
Sent from my páhhōniē
That had crossed my mind, so I went through the root flashing process again, Odin3 gave it a "PASS," but the problem remains.
OK... Should I wipe before flashing stock? Thats the one thing that I didn't do. I wasn't sure which wipe to do so I didn't. (oops???)
Do a wipe data/factory reset now and you should have wi-fi again. I had the same problem and it worked after I did the wipe data/factory reset.
ehhhhh.... somethings up here. I did a wipe/factory reset, then flashed back to my virgin ROM with CWM-recovery on board. My cellular/ data is back but WiFi is still borked.
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
wreckit72 said:
Do a wipe data/factory reset now and you should have wi-fi again. I had the same problem and it worked after I did the wipe data/factory reset.
Click to expand...
Click to collapse
Or did you mean that I should have did the wipe on the UnNamed ROM?
Trying to do a CWM backup through the Rom Manager App so I can do a data wipe/reset (through the factory-reset option, or through CWM, just to clarify?), but every time I try to make a backup CWM gives me this:
E: Failed to verify whole-file signature.
Any idea what would cause this?
McMash said:
Trying to do a CWM backup through the Rom Manager App so I can do a data wipe/reset (through the factory-reset option, or through CWM, just to clarify?), but every time I try to make a backup CWM gives me this:
E: Failed to verify whole-file signature.
Any idea what would cause this?
Click to expand...
Click to collapse
It is posted prominently in several places in the I777 forums, do not use ROM Manager app.
Starting with UCKK6, then flashing UCKH7 plus root package is known to bork wifi. A wipe data/factory reset will clear it if you wish to stay on UCKH7. Doing OTA update to UCKK6 without a wipe also reportedly clears the wifi problem, and will retain root.
To use ClockworkMod Recovery, you must first install a CWM enabled kernel.
ya...
McMash said:
Trying to do a CWM backup through the Rom Manager App so I can do a data wipe/reset (through the factory-reset option, or through CWM, just to clarify?), but every time I try to make a backup CWM gives me this:
E: Failed to verify whole-file signature.
Any idea what would cause this?
Click to expand...
Click to collapse
Yuppers... ROM manager is incompatable with the SGSII. I just learned that yesterday. Its a P.I.T.A.
You gotta delete it then flash the CWM-R kernel to get the nandroid backup. Yes you are now backing up a modded kernel but otherwise you are pulling a raw (and virgin) FS image.
@SeniorGato
I can't interpret from your post. If you restored a previous backup from ClockworkMod Recovery, then you probably reintroduced the wifi problem.
Anyway, you want to be on UnNamed. You should do a wipe data/factory reset before you flash UnNamed. Then for good measure, it couldn't hurt to do another one after.
creepyncrawly said:
@SeniorGato
I can't interpret from your post. If you restored a previous backup from ClockworkMod Recovery, then you probably reintroduced the wifi problem.
Anyway, you want to be on UnNamed. You should do a wipe data/factory reset before you flash UnNamed. Then for good measure, it couldn't hurt to do another one after.
Click to expand...
Click to collapse
I did in fact go back to CWM.
From the recovery screen of UnNamed, I kernel flashed back to CWM, then did the factory wipe, then flashed the backup I made. The WiFi did work when I was on that ROM prior to flashing UnNamed. Now... not so much.
Anyway... Off to look for that stock kernel, then start over.
So do a wipe before each flash then?
Just finished re-installing the OTA update back to UCKK6. Root is still good and the wifi seems to be working. Thank you Creepy and Gato for being so helpful and gracious. There's a huge amount of information on here that I'm trying to sift through and thus a bit of a learning curve, but thanks for helping me through the first hurdles!
Yes, you must wipe before changing from one rom to another, ie stock UCKK6 to UCKH7, or UCKH7 to UnNamed, etc.
You can usually get by without a wipe when flashing the same ROM, ie UnNamed 2.0.0 to 2.0.1
Hmmmm...
So I've wiped, flashed UnNamed then re-wiped. Now I have no modem at all (again).
Looking in the about phone I see some interesting things...
model number: SPH-D710
Baseband: unknown
Kernel version:
2.6.35.7-sph-d710.el13-cl806482
build number: UnNamed v2.0.1
hardware version : unknown
And strange behavior (aside from the no modem thing): when the screen turns off, I have to restart the phone all over again.
I downloaded the ROM through the developement forum under the I-777 so I THINK its the right one, but this descrepancy in the model number has me concerned. Is it normal for custom ROMs to display incorrect data like this or have I completely hosed this?
This is totally *not* normal.
SPH-D710 is Epic 4G Touch.
The kernel belongs to the epic.
It looks like the phone won't even recognise the sprint modem.
I'm surprised your phone will even boot.
Your phone is the AT&T Samsung Galaxy S II I777, right?
If so, you need to re-download the UnNamed install file. The latest version number is 2.2.1 (not 2.0.1) from here. The file you want is update-unnamed-v2.2.1-full.zip.
I don't have enough experience to tell you how to proceed, but here is what I think will work.
If the kernel currently on your phone has ClockworkMod Recovery, and if you can boot into recovery, you might try flashing UnNamed from there. Do a wipe first.
Or, flash back to stock plus root, install a CWM kernel, and then flash UnNamed.
Edit: Yes, gtg released an UnNamed for Epic 4G Touch, which is currently on version 2.0.1. Somehow, you have downloaded and flashed the wrong package, but knowing gtg, it almost certainly does not contain bootloaders or param.lfs, so you should be able to recover. The kernel contains CWM recovery based on 5.0.2.7, the same version we have in Entropy's DD kernel, so you might try flashing the correct UnNamed directly from that recovery. Since you could go SGS II --> Epic 4G, you should be able to go back the other way. If that doesn't work, then flash the stock plus root using Odin or the Odin One-click package.
Well that does explain...
Weird part is that I DID use the I-777 forum's download. Anyway, I'm redownloading now.
*fingers Crossed*
So this begs the question, how are the sprint galaxy s2 roms looking, and how hard would it be to build a 'hellraising' package for them? If a straight flash managed to boot, kernel and all, might open even more possibilities for us.
Sent from my páhhōniē
Siyah Kernel 2.6.6 Troubleshooting
Hello again!
I thought I'd give flashing a kernel a go. I've been following Creepy's guide to installing a kernel via Mobile Odin (bought the pro version; easier and helps out the devs!). Got it installed on the phone and put the zImage for Siyah in the internal SD-card root and flashed from there.
It rebooted and showed that CWM had successfully installed, but the kernel is still the 2.6.35.14 as it was before. Not only that, but wifi is also non-functional again. Tried to flash it again; same result. Cleared the cache/dalvik and also ran the kernel cleaning script, then gave it another go. Still no Siyah kernel, still no wifi.
Great start to my XDA career, I know. Any help would be awesome!
If you're sure you have root and can boot to CWMrecovery, you may try mounting the phones internal USB memory (not the removeable SD card) on your computer, move the entire zip into it and flash thru CWM recovery. Once I had the right ROM *sheepish grin* it worked immediately and perfectly. My wifi is back and everything!
A thousand thanks for all the help!
Edit: I just reread your post. First check what recovery you are booting to. 3e or CWM?
Sent from my SAMSUNG-SGH-I777 using XDA App
Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
I rooted my sgs2 I777 with CWM a few months ago. Now my phone is trying to run updates, but the updates keep getting interrupted. I'm assuming it's because th device is rooted. Is a newer version of cwm available, and should it fix my issues?
Several users have updated successfully with root, and the root stick with the update. However, it appears that a custom kernel will cause the update to fail. You could try flashing the stock kernel, and then doing the update. And once you update successfully and retain root, you can put a CWM kernel back on the phone. Get the stock kernel Odin flashable tar here.
Thanks dude, I appreciate your help =)
I reflashed cwm to my device after updates were complete. Just noticed my wifi isn't working. I flashed the device with cwm 5.0.2.3. Should I have used a newer version of cwm, or is something else causing the wifi to malfunction?
I hear clearing cache/dalvic cache has corrected the wifi problem for some people in the same situation.
how do you clear the cache? Sorry, I'm kinda a noob.
It's one of the options in CWM recovery. From main menu choose Advanced, then clear dalvic cache. It will probably take longer than normal to reboot. Since this didn't happen with mine, I'm not sure if this will fix the wifi, but heard it might. It surely wont hurt your phone, dont worry.
Thanks, trying it now, I'll let you know if it works.
Clearing cache didn't work. Will attempt to flash daily driver mod, by Entropy, next. Th mod has been said to fix the problem.
you might also want to try the wipe data/factory reset from CWM. I would back up anything you don't want to lose, but the more I think about it, this may be the fix I read in a different thread. I'm not sure how much it would wipe though.
Your WIFI issue will be resolved flashing Entropy's DD from 1221. Clearing your cache and/or davlik will not do anything to resolve it.
Thanks, do you know where I can find it in a tar package? I prefer flashing with Odin.
rmw1980 said:
Thanks, do you know where I can find it in a tar package? I prefer flashing with Odin.
Click to expand...
Click to collapse
I have not seen a tar package for it. I could probably put it in a tar, but I prefer loading it with its CWM package or loading it the way I have outlined here. Honestly, the CWM package is your best and safest choice, imo.
Thanks for the information. Will try it tomorrow.
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Gutana said:
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Click to expand...
Click to collapse
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
screamworks said:
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
Click to expand...
Click to collapse
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
DirkTeur Velserbroncx said:
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
Gutana said:
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Click to expand...
Click to collapse
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
screamworks said:
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
Click to expand...
Click to collapse
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Gutana said:
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Click to expand...
Click to collapse
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
screamworks said:
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
Click to expand...
Click to collapse
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Gutana said:
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Click to expand...
Click to collapse
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
screamworks said:
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
Click to expand...
Click to collapse
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Gutana said:
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Click to expand...
Click to collapse
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
screamworks said:
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
Click to expand...
Click to collapse
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Gutana said:
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Click to expand...
Click to collapse
I only just the message 12 hours ago, if that helps?
Usually, your best bet is to go with the latest build, which you can get here. If it's stability you're looking for, go with the stable build, instead of nightlies.
Personally, out of all ROMs I've tried, I could only ever stand MIUI and CyanogenMod - but even then, MIUI started to annoy me with little things here and there. I think I'll be sticking with CyanogenMod for awhile. So, I'm not really the best authority on that. Just try some different ones, and see what appeals to you the most
Hey guys this is where I am with this issue. Kind of new to Android so forgive me if something is obvious and left out.
Bell Galaxy Note, unlocked via unlock code.
Please note that before I ever flash a new rom, I do a factory wipe, wipe cache, wipe dalvik..3 times first, then I redownload and install from Play
1. Noticed that my phone on Flappjaxx's rom was acting flaky. (ie FCs more than usual). This rom worked fine for a few weeks.
2. Tried CM9 via Rom Manager. Phone still a bit flakey.
3. Used CWM Recovery to return to FJ's rom which I made a backup first.
4. Phone even more flakey (ie. noticed some apps could get the internet, others could not. Phone would FC as well every time).
5. Tried clearing cache, dalvik, and fixed permissions. FJs rom still flakey (at this point 2-3 attempts to fully boot). Factory reset and caches cleared again but still the same.
6. Used Odin to flash the Bell stock system, recovery, and boot from this thread: http://forum.xda-developers.com/showthread.php?t=1599127
Did a factory reset using the stock recovery after this was flashed as well.
7. Having the same issues on the stock rom as I had on FJs rom and CM9.
8. I was eventually able to get the phone to allow me to see the baseband version before it rebooted (took a few tries) and I see the baseband is still UCLF6. I thought the baseband would have been reset too but I guess not.
Is there something else I should do? Will popping CWM recovery on there again and flashing another modem fix this?
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
This happens sometimes. You just have to find and flash the stock modem through odin to get it 100 percent out of the box.
As far as the warranty return, no one would allow it because you have no way of proving that the problems with the phone are not directly related to your modifications to the device even if they are not.
However, I would suggest flashing the stock modem and then reformatting your device through kies as a last resort. If this does not still work, I would suggest (although never used) the flash counter reset zip once youre on stock and sending it in for repair.
Hope you get it up and working
welchertc said:
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Understood about warranty of course.
- not restoring anything...as mentioned, everything is always set up from scratch, including all apps from Play store.
- I'm trying to get back to stock, and everything looks stock except that my baseband reads UCLF6, which I assume is not stock GB. I have tried flashing the modems, kernals, and roms found here http://forum.xda-developers.com/showthread.php?t=1506330 and here http://forum.xda-developers.com/showthread.php?t=1599127
This is why I am asking if my hardware seems defective, or if there is something amiss in what I am trying to do (if I am seeing UCLF6 in my baseband, I am assuming I am missing something).
Last attempt to get rid of the UCLF6 baseband I downloaded this modem: http://forum.xda-developers.com/showthread.php?t=1506330 , did a reset, wiped caches, and still showing UCLF6.
Don't know what I did differently, but I tried pterry30's modem and flashed via CWM (I could not find an Odin modem tar) and my phone seems normal now (but very stock) and I got the 'mugla' version of the modem listed in my system settings.
Thanks for the suggestions...hopefully its really fixed. Since I went through all this trouble I'll try Bell's ICS update.
Problems like this are great learning tools...but a bit stressful lol
Happy all is well. Good luck.
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.