Related
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.
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
I was running the Spike Pure ICS on my SGS2, before which I had the ICS version of MIUI. I tried flashing Lite'ning Rom 3.6 through Odin, but was unsuccessful. Also, that's time I noticed the 7.2 version of CM and decided to flash that and that's when the problem occurred.
Although I could flash CM 7.2 properly and could also install the GApps through CWM, on rebboting it through the CWM, my phone got stuck and it wouldn't go into Recovery any more.
Luckily, it would boot into Download Mode and I could flash the stock rom through Odin and get my phone back to stock, thereby losing the Root and CWM.
I wanna know as to what could cause such an issue to arise. so that I can prevent it later!
Your help and time are appreciated!!
Why start a 2nd thread ?
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
And you couldn't make another post to your initial post along the lines of 'Why did this occur in the first place ?' You could even easily change the title of your initial thread to reflect your desire to know the answer to this question.
One of the main rules of XDA is don't spam.
I'm extremely sorry if I've spammed as it wasn't my intention at all!
This thread was and still is a genuine question which I want to know!!
Also, could you please tell me about the occurrence of such a problem on my phone??
gadgyfreak said:
That's because every person who replied told me how to go about the problem, but nobody told me why it occurred in the first place!
I posted this thread so that I can know how to avoid such a problem in the first place, as such a problem seemed very unique to all the people I talked to.
Click to expand...
Click to collapse
I think answer was there but might be not clear......
When you flash gb over ICS you have to wipe, when you mix stuff after that, meaning trying different kernels to fix the issue it might get worse.
Because recovery is somewhat linked to kernel in s2, you won't get recovery in a messed up system.
So when you flash a complete firmware using Odin and then do data cache wipe, it get fixed.
Hope this helps.
But then how is it possible that my phone didn't get all messed up when I flashed CM 9(Nightly) over my pre-existing CM 7.1, while it happened when I tried it vice versa?
already told you, when you go from ICS newer kernel to GB older kernel, wipe is necessary. Going from GB to ICS will work but wipe is better there too.
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Flash a GB rom.
gadgyfreak said:
Thanks a lot for your help.
So what exact procedure do I have to follow if I want to mover from ICS to GB?
Click to expand...
Click to collapse
save data
Wipe dial *2767*3855#
Flash GB Rom, preferably stock using Odin.
Should boot now, if not go into recovery and wipe data cache.
It will boot now.
So I'm very new to android as I came from an iPhone.
I want to flash the liquid Smooth Rom. I'm currently on the viper one Rom that I side loaded when I flashed a bad kernal. I just want tips so I don't soft brick my phone again. Thanks
NM
I can't really help you with your issue but I may be able to get some help from you. please check my post.
http://forum.xda-developers.com/att-htc-one-m8/help/rooted-phone-stuck-boot-screen-plz-halp-t2886980
Tarantulaboy337 said:
So I'm very new to android as I came from an iPhone.
I want to flash the liquid Smooth Rom. I'm currently on the viper one Rom that I side loaded when I flashed a bad kernal. I just want tips so I don't soft brick my phone again. Thanks
Click to expand...
Click to collapse
1) Read read read until you understand the basic concepts of what you are doing, potential pitfalls, how to recover, etc.
2) Read the ROM thread for the one you picked for any potential issues. Read the install instructions on the top post of that ROM thread, etc.
3) I don't know what you mean by "bad kernel" but (going along with Items 1 and 2 above) understand what you are flashing. Only flash mods known to work with this device, don't mismatch kernels with the ROM (try to use a AOSP kernel on a Sense ROM or vice versa), etc.
4) Have adb/fastboot installed and understand how to use them. You know how to sideload, so it seems you already have this one done pretty well.
5) For the love of god, make a nandroid backup of your current setup using your preferred custom recovery (TWRP or CWM). This alone will get you out of most "soft brick" jams; so I have no idea why some many folks skip this step!!!
6) Full wipe (data, cache and Dalvik) when flashing a new ROM. This is the default wipe if using TWRP. Neglecting to do this is a common mistake, and doing so can save some headaches.
7) Some folks have had random issues flashing with TWRP. Be prepared to re-flash TWRP (wipe cache first) or switch to Philz CWM if this happens to you.
8) Consider S-off, as it gives you more recovery options if you run into problems.
9) That's really about it. If you have these items covered, you are pretty well equipped to recover from any issues flashing ROMs. But most likely, if you do a full wipe and just install the ROM, it will boot fine.
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
JudoFreak said:
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
Click to expand...
Click to collapse
Your title seems like bluspark have some kind of problem, but that's not the case. You should change that; the kernel works flawless and the problem is clearly you that doesn't know what you're doing. Read and learn from guides, videos and everything else before going flashing around.
And, of course, search. There are threads out there pointing out how to unbrick your phone and solve this kind of mistake.
(and you may have flashed the kernel for CM13, not the OOS kernel...)
Oedipus Rex said:
Your title seems like bluspark have some kind of problem, but that's not the case. You should change that; the kernel works flawless and the problem is clearly you that doesn't know what you're doing. Read and learn from guides, videos and everything else before going flashing around.
And, of course, search. There are threads out there pointing out how to unbrick your phone and solve this kind of mistake.
(and you may have flashed the kernel for CM13, not the OOS kernel...)
Click to expand...
Click to collapse
My apologizes if it seemed like I was implying or insinuating that something was wrong with the kernel, I was only stating it so that it would provide the necessary information for those at were interested in troubleshooting and saving them the hassle of asking. This is my first Android device, and first time rooting and I don't think it would be inappropriate to ask for a slight bit of patience. Again, I did not mean to imply something was wrong with the kernel, I am fairly certain it is something of my doing that I can (hopefully) repair.
Is there any guide that you would recommend specifically for the BluSpark kernel? I know for certain I donwloaded and installed the OOS version so I know that's not an issue.
I think you have to use an older version of twrp to flash this kernel. The recommended version of twrp is 2.8 I believe maybe this is your problem but I'm not sure since I am using cm13 based rom with this kernel.
Go dig through the Blu_Spark thread, I'm pretty positive he said he will never support using F2FS as no one's shown that it's either better or worse than EXT4 which has been trusted for years.
JudoFreak said:
I'm fairly new to rooting and flashing kernels so sorry if I'm ignorant about all this. I have the latest version of TWRP (3.0.2-0). I would install the latest BluSpark zip (r128), wipe the data and cache and then format them into F2S2 and the phone would reboot fine. However, if I try and reboot the phone or turn it off and turn it back on again I just get stuck at the bootloading animation. Is there any advice or anything I do to prevent this? Did I install something wrong or using the wrong version of something? Thanks in advance for any and all help!
Click to expand...
Click to collapse
You did a couple of things wrong. When you flash the kernel there is no need to wipe data. You basically reset your phone. Also, formating to f2fs after you flash the kernel will also wipe data and therefore reset the phone.
Your best bet is to start over from factory rom and kernel to get the phone to boot right and then do some research and reading before you start changing kernel and partition formats.
Search the question and answer forums for restoring to factory settings.
Good luck.
I have the same issue. after flashing latest build of blu_spark, phone stuck on boot screen .. i tried latest TWRP and Blu_Spark TWRP in his download section, neither worked for me. I did not format f2fs as I would like to keep it the same EXT4 .. any ideas how to solve this issue?