Related
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
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.
OK so let me start off with, great site. I have read a ton of information.
First: Siyah 4.3.3 (Latest) Kernel which now has been put to AJK v1.48s
ROM; SHOstock3 v2.5.9
PreMod Settings: SGS2 AT&T SGH-i777. Started with GB > AT&T OTA (KIES) 4.0.3 > AT&T OTA WIFI 4.0.4 (caused huge freaking headaches with battery, charging, turn off the phone loop, battery draining, etc.)
Issues:
Original Issue posted in this thread (viewing Single Post) http://forum.xda-developers.com/showpost.php?p=39350619&postcount=18
Creepy offered something to try. That never worked as all I was able to do was download mode or stare at the Samsung Galaxy S2 Splash Screen. Well, I took to his download repository and other links and used his One-Click Recovery to stock GB Rom to make part of my phone usable, using this link here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
While it is Gingerbread at least my phone is usable. I want to try his STOCK ICS method but that mentions the eMMC super-brick bug.
So this is what I have tried so far. I have tried installing Siyah 4.3.3 nomswap for my kernel using Mobil-Odin Lite. That works but it never reboots or actually says finished. What it does do is stay at the wicked purple splash with the yin yang symbol. I left it like that last night until I woke up this morning and it never changed. So I rebooted the phone and the Kernel is on there. I reboot into recovery so that I can install SHOstock3 v2.5.9. That goes off flawlessly except here the last few times it won't reboot when I go to the GO BACK. It sticks and doesn't do anything. Rebooting shows the SHOstock3 Engine Boot Animation. Once it stops it goes to ask me for the encryption password. Well I put in my password (was the same one to the unlock screen) and it reboots and you see the nifty Samsung animation logo and then goes to the Samsung Galaxy S2 Animation Logo and then just stays there. It really pisses me off.
So after all that I finally put a new Kernel on there,AJK 1,48s. Pretty cool it loads up and then reboots. Well AJK shows up after the light-blue bar fills up and then goes black and the 4 touch sensitive row keys are lit up for a bit before going dark but the phone is still on. So I rebooted to recovery (CWM now with the Kernel) fixed tweaks, went to advanced and saw all sorts of options. Tried clearing caches for ROM 2 and restarting,no effect. I removed ROM 2 and went through reboot and nothing. Restored ROM 2 and nothing. Re installed SHOstock3 v2.5.9. Did the same thing after install and not backing out when I hit GO BACK. Rebooted, same scenario that happened before with requiring password. Entering password does the same thing with a reboot and then staying on Samsung Splash Screen. If I Don't enter the password and reboot,same thing happens. So after being irritated and pissed off I ran Creepy's One-Click Fix again and paid attention to the phone and noticed it mentioned not being able to access the AT&T section or partition or something like that. So while part of my phone works under normal circumstances I want to figure out how to remove that encryption part of the phone and get full access (even though full memory and space are shown under Windows 7 and the files on the phone). The password I put on there isn't taking and I don't know if using PC methods for removing encryption (which could take awhile I know) needs to be employed (and if so which methods) or if that part is just screwed and I can't put on any other kernels or custom ROMs. Perhaps tell me where I messed up. Should I try swapping the ROMs from Advanced setting in CWM Recovery? Can I try a different ROM (kernel didn't seem to help)? I have done several factory resets dalvik cache wipes cache wipes formats,etc. and it is still there. I can say that before the whole encryption debacle (even though I was encrypted I did get in my phone after encrypting it) my pin unlock for my SIM wouldn't work and I actually SIM locked my phone. Had to go to AT&T and get a new SIM and was up and running. I put a 4 digit pin lock for the SIM (it let me do it) and when I went to unlock it after a reboot, it wanted an 8 pin for the PUK and wouldn't take what I put. I tried to change the PIN but to no avail. Once that happened I guess it snowballed. Any help is appreciated. I have searched and tried some things that looked to match my issue but none have totally helped. I do have ADB set up on my wife's laptop which I use to restore my phone to GB Stock ROM. I haven't been able to reboot the phone into Bootloader to do any fastboot commands as when I tried to do it the commands just sent the phone into normal reboot (though adb reboot recovery does boot to recovery). I Haven't tried booting to the bootloader using the new Kernel though so I will wait for confirmation or additional information before I try. Thanks guys.
Eagle
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Thank you so much creepy. I will give that a try later and see how it goes. I hope the information I gave actually gives enough info. I know folks usually want enough. Ill post back my findings.
Eagle
quick follow up and what I tried
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
WarEagleUS said:
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
Click to expand...
Click to collapse
Should I try TWRP instead of CWM and if so where should I grab it from?
Status Update
So this is what I have tried so far as of this moment.
I reflashed using your Stock + Root Gingerbread ROM.
Wiped DATA and everything in recovery menu several times.
Used Kernel Wipe and ROM Nuke for extra cleaning power.
Reinstalled the Kernel AJK and SHOstock3 ROM
Haven't installed any themes though I had Johns Blue and Villians Poison Base Theme (I believe that is what it is) on there when this all went down. Should I put them back on there?
Password still pops up. So what it looks like is that unless I stick with the unencrypted portion of the phone, I am screwed with any custom ROMs as the correct password has the phone restart and then stick at the Samsung Galaxy S2 Splash Screen. Apparently I still cannot access that area of the phones memory to wipe it at all no matter what I do. I need to access it somehow. Really driving me crazy and thinking I may need to talk with AT&T(as Samsung told me to earlier this morning lol) and see what they can do.
One thing I do notice is when I use your stock root program it actually removes the encryption or decrypts the section of the phone for the stock ROM to go on the phone which is cool.
Eagle
Any other things to try from anyone is greatly appreciated.
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
WarEagleUS said:
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
Click to expand...
Click to collapse
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
creepyncrawly said:
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
Click to expand...
Click to collapse
Thx bro. yeah I need to run some forensic tools and see if I can mount the whole phone system on my PC and run the tools.
creepyncrawly said:
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
Click to expand...
Click to collapse
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
WarEagleUS said:
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
Click to expand...
Click to collapse
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
creepyncrawly said:
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
Click to expand...
Click to collapse
Yeah I should have used ADB to do that from the get go. I should have used the wife's laptop like I started to instead of my WIN 8 machine has it seems to be finicky with Android SDK (the portion at least needed to run ADB). Linux commands really aren't much different than terminal and I have done both. I was actually trying to get fastboot commands to work but my bootloader wasn't cooperating and for the life of me I couldn't find how to unlock it. I may try restoring that EFS. If nothing else I would love to be able to format that EFS and replace it with my original copy though as you said a damaged EFS may actually cause issues (who knows if it is damaged). I do know that I am fixing to chat with AT&T support. I hope I don't have to drive down to Hoover, AL to the repair facility. I would rather them send me a phone and send this one back. I am on stock 4.0.4 ICS from AT&T and any root that may be on there (though I doubt there is now) I can remove and what not
Thanks for the advice and insight Creepy. I know you tried like hell to get me an answer but in doing research on here with other problems I found out some useful information going forward my friend.
Eagle
Well, looks like I will be getting a special early upgrade and the wife will as well. I will be keeping this phone, however, to mess with this and see if I cannot get this problem fixed. Thanks Creepy so much. I appreciate your research and help more than you know. If possible I would love to keep this thread open for a while just in case I figure this out and fix the issue. It may take me a week or so but I will get back to messing with it again.
A side note. You don't need the whole sdk to get adb. You can download just the files you need from my signature.
Sent from my SGH-I777 using xda premium
Hey guys, had a Note for a little while now and was running stock AT&T GB. I tried upgrading to ICS a couple of times using other threads in this forum, but I'd keep getting stuck in a boot loop and had to revert back to stock AT&T GB to recover my device per Da_G's method here: http://forum.xda-developers.com/showthread.php?t=1506330, and it worked fine.
However, I recently tried one more time to upgrade to ICS, failed and reverted back to stock AT&T GB per Da_G's method, and while my phone turns on, it has become sluggish to the point of being absolutely unusable. Screen touches work fine in some cases, and then take forever to register in the same spot later. The on screen keyboard cannot be invoked - it almost always hangs the phone. And the phone randomly reboots.
I did forget to wipe cache and dalvik cache the last time around while doing the install, and that probably caused this problem. But sine then I've wiped both caches and retried flashing, and also reinstalled a stock AT&T radio in case that was the problem, and also reset the flash counter per braway's methode here: http://forum.xda-developers.com/showthread.php?t=1569206, but to no avail...
My Note is pretty much useless at this time, so any light you guys can shed or any other tack you can suggest is going to help me immensely!
Thanks for the help!
Sid.
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
http://www.samsdroid.com/2012/07/i717uclf6-android-404-usa-at-stock-rom.html
This will fully wipe your phone and install the UCLF6 ICS ROM with matching radio.
Agoattamer said:
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
Click to expand...
Click to collapse
Sorry, I didn't mention - I DID do a factory wipe/data reset and I've been flashing the stock GB ROM via ODIN itself. But thanks for the link to the ICS ROM - I'll try installing this and report back.
Okay, I downloaded the UCLF6 ROM from the samsdroid site (took like 3 hours to download!), performed several factory data resets, cache wipes and dalvik cache wipes on my phone, and then flashed the ICS ROM via Odin. Odin showed "Passed", but the phone rebooted into recovery with a message "failed to mount /system" and "failed to mount /data". I then hit "reboot system now" and am stuck at boot loop. Booted back into recovery, got the same message about not being able to mount system and data. Hit "reboot system" again and back to boot loop...
What the heck am I doing wrong???
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You do have an ATT i717 and not a canadian version? But I think your phone has other issues.
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
If the odin flashing did not straighten things out then I have to believe that there are other issues.
sid.asu said:
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
Click to expand...
Click to collapse
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
i have had the same issues as well, i am unsure if its me or what but everytime i have tried to flash a tmobile rom on my note which should work it slows down to a crawl i cannot even go through the setup process. I have tried via odin and through cwm touch. the next thing i flashed was t879uvlg3 modem and i was wondering if that was the issue and if so what modem should i flash that way i dont have to use kies for recovery cause man..........thats slow. I even made a nandroid backup and it was slow as well so if anyone has had this issue or any ideas please help me
oort cloud said:
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
Click to expand...
Click to collapse
My problem is that the phone does not stay on long enough for Kies to detect it - it keeps rebooting on GB. Well, guess it's cooked! Thanks for the help!
I've looked all over for answers on this. I hope I didn't miss something, but here is my issue:
After being fed up with Touchwiz, I tried flashing AOSP ROMs instead. Ever since then, every AOSP ROM I flash will freeze during boot (usually it freezes after 15-20 seconds), I'll see a glitched image for 10 seconds, and then reboot. This bootloop has happened with AICP, Resurrection Remix, and a few others. I'm about to try CyanogenMod, but I assume that will fail as well since the others were mostly based off CM. I always wipe data, cache, and dalvik before flashing (sometimes system too, and now internal storage to try to fix this issue).
Can anyone figure this out?
I have very limited access to a PC and my Mac refuses to recognize this phone in download mode, so Odin isn't readily available and Heimdall has been no good so far.
G900TUVS1FOL1
EDIT: Apparently EVERYTHING is bootlooping this phone. I flashed other Touchwiz-based ROM's and those aren't working. Finally I returned to stock firmware using Kies, and I'm STILL stuck in an endless loop.
I NEED HELP. SERIOUSLY.
This is probably a bad idea, but I'm headed to T-Mobile to try and get help. I can't afford to wait.
t3st4m3nt said:
This is probably a bad idea, but I'm headed to T-Mobile to try and get help. I can't afford to wait.
Click to expand...
Click to collapse
in twrp you need to format data partion and wipe internal storage cache,data, and davilk cache
then use kies for emergency restore
malbert16442 said:
in twrp you need to format data partion and wipe internal storage cache,data, and davilk cache
then use kies for emergency restore
Click to expand...
Click to collapse
Honestly, I feel like I should've just stuck with your ROMs
I've done all of the above, and I do so every time I flash a ROM. I tried re-flashing after wiping system, no good. And the restore from Kies failed to fix the issue.
Kies removed twrp, so I was able to take it to a Samsung Center at Best Buy without the device drawing suspicion of having been rooted (they ignore Knox at this one), and they failed to solve the issue with a home reset. Right now they have no idea what is happening, and neither do I.