Hi guys,
I am new to the XDA forums so forgive me if this is really stupid or if someone has posted the same problems. I searched for an answer but couldn't seem to find someone with my problem. Forgive me if this is long. I just want to make sure you guys know all the details so we can figure out what went wrong.
I recently flashed the Evil Fascination 3.6 Rom from a modified stock version of ED04 (debloated/debinged). I believe that my version of CWM recovery was 2.5.1 or something like that (w/ voodoo lagfix). I am pretty new to the Android world but I do believe I did everything correctly. I wiped Cache and Dalvik Cache and Data multiple times and made nandroid backups etc.
I flashed the Rom with no problems and everything worked just fine. I was trying out Regina 3D launcher at the time (I regularly use Launcher Pro), and for some reason it seemed a little slow to load up (I figured it had to do with it being the first time with the new rom). I kept having loadup problems with the launcher so I uninstalled it and went back to Launcher Pro. Launcher Pro even seemed like it was acting weird but I didn't take much notice to it.
Now yesterday I downloaded the OTB 1.6 Touchwiz kernel. Everything I've read said it was compatable with Evil Fascination. I tried to flash it from CWM recovery and it didn't work. My phone stayed stuck on the Evil Fascination boot up screen and finally I just popped the battery out. I went back into CWM and just wiped everything and reflashed Evil Fascination. It seemed to work fine with Launcher Pro (again a little glitchy at times, but I took no notice really).
I again tried to flash the OTB 1.6 kernel. This time instead of doing it from the recovery I downloaded an app called SGS kernel flasher. I did what it said and it flashed the kernel for me with no boot up problems like CWM did. I rebooted and then booted into CWM to check it and it was changed from version 2.5.1 (voodoo) to 3.2.0.0.otb. I figured this meant that the kernel flash was sucessful. I went to reboot my phone and when the home screen came on it was a froyo style launcher with only 2 or three icons on the page. I pressed the app drawer and none of my apps showed up that were on my sd card. finally i pressed the home button and it asked for which launcher to choose : LauncherPro or the default and I chose LauncherPro. My regular setup appeared and my apps were in the app drawer. I found it weird that my apps showed in LauncherPro but not in the default launcher.
Now with doing phone reboots my phone always goes to the default launcher with no apps from my sd card and I have to wait to press the home button for LauncherPro to appear. I set it as my default launcher but it never loads when my phone is rebooted.
I was just recently (within the last hour) doing regular things on my phone (texting, internet , email etc) ad all of a sudden I got the shut down boot animation from my rom and my phone turned off. I went to turn it back on and my phone stayed stuck on the boot screen again. Now you can figure what I did again. I went through and did everything over and reloaded the rom and kernel. I am still having the same problems with the launcher as I did before and I have no idea whats going on. I just want to avoid going through this again. Anyone have any idea what the heck is going on???
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
I'm also no expert but after running into constant force closes and random problems with launcherpro I decided to go with go launcher and its been a great switch for me.
Sent from my SCH-I500 using XDA Premium App
Hey guys, still no luck. I don't know what it is. I wish I knew more about hacking and doing all this kind of stuff
Try flashing a PBJ kernel!
can you get into CWM with the three finger salute?
[hold down the two volume buttons and the power until your phone reboots and you see samsung then let go]
See if you can mount as usb to get the kernel on there, if that doesnt work go to staples get a microsd card reader [under $15] and toss the pbj on your card then flash that.
When i was on EF and Comm Rom my phone didnt like the OTB kernels
Good Luck!
My recovery menu works fine and I can boot into it from the ROM without problem. My problem is that when I reboot the phone the ROM's default launcher is setup (and it is missing all of my apps) even though I set Launcher Pro as my default. I have to reset all my defaults in Launcher Pro every time my phone is turned off or rebooted. I would be on PB&J but I like to overclock my phone and PB&J doesn't support voltage control and I don't want to pay for and overclocking app.
efan450 said:
If I were to guess I would say your problems comes from trying to flash the otb kernel with a 2.x.x.x recovery..i don't believe that recovery supports edify scripting.....i would odin a 3.x.x.x recovery and re flash the otb kernel...and I don't know much about that app you are referring to, but I wouldn't use a market app to try to install a kernel unless specifically directed to in the author's o.p.
I'm not a dev..just a flash-a-holic! but I think that should help your problem
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
From what I've read many people have disagreements on whether 2.5 supports Edify or not....because a lot of people have success with it while others don't so I really don't know. Its never given me problems in the past. I actually had more problems with 3.X recoveries (It wouldn't allow me to make nandroid backups and other things that were essential) so I flashed 2.5 and it worked perfect (again I've read about people having the same problems with 3.0 versions of CWM).
Okay what I've found is that this has nothing to do with Launcher Pro. I downloaded He Launcher and when I reboot my phone everytime it asks me to pick a default launcher. And when I'm using He Launcher, none of the apps on my SD card show up in the app drawer (they don't show up in the default ROM launcher either, they only show up in launcher pro)
Efan450 I tried what you said and it worked! I odined a 3.X recovery and wiped everything oof my phone then flashed the ROM and kernel and everything is working perfectly now. Thank you very much!!!
Related
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
First off, wrong section... should be in Q&A.
One way to fix it was to get SetCPU, and make sure the minimum CPU speed is 200MHz
You should also give more information. Have you flashed eb01 with odin before installing SC? How often do these sod's happen? Do you use the clock app?
Sent from my SCH-I500 using XDA App
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
GizmoDroid said:
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
If you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package ROM from this post
While reinserting your battery, hold both the volume keys and the power button down until a second after you see the Samsung boot logo
You should see CWM recovery now
Flash the SuperClean ROM from this post, Wipe Cache/Dalvik Cache only.
Reboot. If you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot, enter CWM and flash theme, Wipe Cache/Dalvik Cache only.
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
Click to expand...
Click to collapse
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
str8havoc said:
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Are you running setcpu ? And if u are and u have a profile for when the screen is off, disable it. That should to the trick
Sent From My Samsung Galaxy S Fascinate Using XDA Premium App - Running Superclean 2.9.1 - 2.2 Froyo
sneakysolidbake said:
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Thacallmehess said:
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Click to expand...
Click to collapse
Your post isn't helpful to the forum at all, at least there's some community members who like to help keep our forums organized and clean so our Mods aren't overwhelmed. (See how easy that was)
@ OP, there is definitely a SOD patch somewhere in the Fascinate forums that Adrynalyne put out a bit back. I apply it along with the Camera mod every time I flash any new version of Superclean based on EB01/EB16. I'll see if I can post a mirror later when I get back home and you still haven't found it.
The SOD patch is already incorporated in to the latest SC. Gizmodroid's process (based on Adryn's solution to problems with SC2.7 iirc) is your best bet at this stage and worked for me. I would also recommend avoiding TiB as much as possible based on Adryn's comments in the SC2.9.2 thread. If you use Gizmodroid's process, please post your results in the relevant thread. I'd be interested in finding out the degree to which that process solves the issues generally.
I had the same problem. Follow the directions above flashing the stock and then upgrading and avoiding the apps noted above (I think youmail was a big part of my problem) and you should be good to go.
GizmoDroid said:
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
Click to expand...
Click to collapse
Thanks everyone for the fast replies even the one telling me i was in the wrong section. Sorry about that
I use both Youmail and the clock app all the time, so thats probbealy why i'm getting the SOD. I also install my apps from my SD card using Astro File Manager and it sounds like that could be causing my problem to.
I installed SetCPU and set the min. to 200mhz, hope that will fix my problems if not
Q1: can I download another clock app and be ok or will it do the same thing
Q2: is there any way of fixing the Youmail app or should I use another voice mail app.
Just want to thank everyone that keeps XDA up and running you guys rock. Love this Forum!
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
mrjake1970 said:
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Click to expand...
Click to collapse
Are you using the voodoo lag fix?
I think the majority of the incompatibility people are seeing with the fixed cwm is might be some broken compatibility with rfs. It's supposed to be able to handle both, but I think changes in jt's initramfs or changes in the project voodoo files in the kernel that CWM is put into are the root of the problem.
Maybe I'll get some time this weekend to look at it.
In the meantime, everyone should go voodoo/lagfix
yeah giz, im using the superclean "stock" voodoo...
r
tonight im going to go flash happy with the original odin file i used to bump to froyo, and the other old cwm with the broken fixpms and the non fixed superclean 2.9.2 and see if that helps.
i cant be late for work again tomorrow with no alarm from a frozen phone lol
Samsung Fascinate
SuperClean 2.9.2 Voodoo
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
What is the sleep of death?
Update...
I reflashed the original EB01 tar file, modem and the 3/30 red CWM, along with the original copy of the non-fixed superclean 2.9.2 ROM and i am running fine so far with no SOD issues.
As long as this holds true for the remainder of the day I'm going to flash the updated CWM tonight to try and narrow down which of the 3 things i suspect in my previous post is causing it.
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
I downloaded setcpu and put it to 200mhz and been running fine since yesterday. I hope it will last the rest of the day.
Sent from my SCH-I500 using Tapatalk
created a sleep of death..
so, guess what? i created the sleep of death on my phone, and i know exactly what caused it.. not only that, but remembering back to my last sleep of death experience - it was the same exact scenerio..
i was running EC10 debloated, jt's 4/8 voodoo.. i flashed a theme to check it out.. didnt like it, so i re-flashed EC10 over it, with wiping dalvik and reg cache..
booted fine, however i started to notice clock lag almost immediately.. screen went off, and next time i tried to open the phone, i had to hit the power key 4 times before it would light up.. sounded familiar to me from last time, so i let it go about 1.5 hours.. sure enough, would not wake up.. had to pull battery to get it to boot..
i did a nandroid back to prior to the theme flash, and seem to be running ok.. however i am going to do the "clean" flash again tomorrow back to EB01 again just to be sure..
im convinced that is what caused mine both times..i will also be doing that every time i get tired of a theme instead of just flashing a new ROM..im guessing themes are leaving pieces parts behind somewhere that don't play nice with a ROM reflash over it..
I have been having SOD issues ever since I rooted and got set up on SC 2.9.2. However today, I decided to leave my GPS on and since I did that I have not had any SOD. Granted today is not a perfect example because not 45 minutes went by without using my phone, but it seems to have made things better for now, except my battery drains because of it.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/foru...21-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I'm running
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
I did TiB but have since uninstalled and used My Backup (free). I'm using GoLauncher and related apps. I do use YouMail and will not stop. I know its redundant but I installed the SOD patch too.
I'm going to try all the bandaid fixes first before re-flashing everything.
Search adrenalyne's threads. He had one with a sod patch.
Sent from my SCH-I500 using XDA App
Ok, so I flashed JT's Vanilla gingerbread rom using CWR 4 and everything seemed fine. I then flashed B Boy Blizzard theme and everthing ran fine for about twenty mintes, then I got what I thought was the sleep of death (only when I pressed the sleep button). I pulled the battery and powered the phone back on. The phone booted into recovery and I got and error 7 cache recovery unable to mount message. I really like what little of the rom I saw and the theme. I sure at this point I'll have to Odin back to stock as I can't do a recovery either (same error message). What I'd like to know is this just a problem I'm having or is there something wrong with the rom or theme? Please advise. Thx in advance.
I have had alot of problems with that rom aswell...not really sure whats going on. Sometimes the rom will install with cwm 4 other times it just boot loops. I have tried every install method for that rom and nothing yet seems reliable. I have no problems flashing other roms, so idk... just chillin with powerwash right now until the bugs get worked out w/ VGB(hopefully).
All of his themes (at this moment) are based on 080211 v2 VGB. And between v2 and v3 there were framework and other apk changes i.e. settings. So flashing that theme on top of v3 will surely lead to issues. Just reflash rom. And make sure the theme you try only says for v3.
good day.
Also, you wont boot into the right recovery using the 3 finger method. you need to use adb or the reboot options
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
lexx210 said:
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
Click to expand...
Click to collapse
Fix permissions with Rom Manager, or in CWM under advanced, then set up your widgets again. You shouldn't have problems after doing that.
I Also noticed in ADW if I installed a backup configuration within ADW I ran into this problem. If I loaded my widgets after re-loading ADW I did not run into this problem. Caelan's post is also spot on!
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
lexx210 said:
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
Click to expand...
Click to collapse
Fix permissions, reboot, then set up widgets again if you lose them. You shouldn't have any more problems unless you flash another ROM, and possibly another kernel.
Then just do the same thing again if you happen to do that.
This is probably stupid, but you don't have the Widgets installed on the sdcard do ya?
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
lexx210 said:
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
Click to expand...
Click to collapse
Same problem here and only after faux's kernel...I tried all the fixes (fix permissions, wipe cache first before flashing kernel) and the only the thing that worked is to go back to the stock kernel.
Oh man, you may be on to something because EVERYTHING was working fine before last night when I flashed faux123's OC kernel. I'm gonna try and go back to stock and see. Thanks man!
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Swiftks said:
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ok perfect then I'll just wait for his next version and hope that fixes the problem. I need his kernel to flash ROM's since I'm on a international phone. It's weird saying that since I'm just in Canada...
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
No problem man....yeah I've made some comments on the the kernel thread about the issue. Hopefully it gets fixed in an updated version.
in the kernel thread (dev) faux is asking INTL users about this issue, for INTL users on his 1.6 unified kernel. some report the widget issue, others do not. its the kernel causing. I am using unified OC 1.6 kernel and am lucky enough to have no issues, and WAY better batter life then stock kernel.
I also encountered this issue, however I don't have an international version of the Atrix.
Using 2.3.4 (pudding version for AT&T) with Alien ROM #4 and faux123's 1.6unified kernel.
Also using Launcher Pro.... I just reinstalled everything after doing a hard reset to try and isolate the problem, and it did occur after the kernel flash.
Same problem here, luckily I just reboot my phone few time a month..(why do I need a reboot, anyways?)
The widget is left blank white with Problem loading widget warning..
I'm not using an INT Atrix, only AT&T (I don't know if there's any other Atrix version) using faux123 1.6, piecrust, romracer cwm ..
any luck, guys?
would there be an update of 1.8 of faux?
I think I'm going partially nuts over this problem. I have tried every thing mentioned in any post. Fix permissions with different CWM's.
I thought was going to win today today when I formatted everything, installed gobstopper 2.3.4 w/ deodex update then setting up my screens with ADW it glitched and would go to the screen preview whenever I touched the screen. a reboot and those damn black boxes are all over the place.
Order of operations:
- format internal/external
- factory reset
- fastboot flashed tenfars CWM which wouldn't mount the internal sd so I couldn't flash
- fastboot erase/flash romracers CWM
- installed Gobstopper 2.3.4
- reboot and used it for an hour or so to let it level out
- installed the deodex update
- reboot and another hour of use with a bunch of reboots to make sure everything was cool (it was)
- used Diviances EXT4 User Journal script
- used it for a few more hours without issue
- installed ADW Ex and while setting up my screens it glitches and goes to the screen preview with every touch.
- reboot... no widgets with a string of expletives
so now what...
Same problem here. I am using latest Aura Rom with latest faux Kernel for International users.
I did everything: Wiped cache, reseted factory, installed rom again, changed kernel to older versions, stock versions, fixed permissions and always lose my widgets configs after a reboot.
Hello,
I recently decided to put the Unnamed ROM on my GS2 and everything went fine and works great, this is my first Android phone and I'm love it! I've been using it a while and just noticed a bit ago that my lock code to open my phone stayed through the flash, is this normal for Android devices? Sorry if this is a noob qestion, i tried google searches and nothing came up.
To install my ROM I rooted my phone with the one click return/unbrick .exe. Then i installed Entropy's 11/3/11 daily driver kernal via adb. transferred unnamed v 1.1.0 over to SD card. Rebooted into CWM and did a "wipe data/factory reset" and then installed from SD card. installation went fine and everything has been working great, just a bit confused about the lock code thing .
Thanks,
as long as you aren't forced to use that code (i.e., you can change it to a different code), then i wouldn't worry about it. sometimes, when you do a factory reset/wipe data, some settings will still stick. for example, every time i do it, i still get a CM7 wallpaper that i was using the first time i flashed anything on this phone as the default wallpaper for the new flash. not sure why it happens, but i am always able to change the wallpaper, so i don't see it as a big deal.
OK cool beans . I just wasn't sure if it was a security measure in place on androids to prevent thieves from stealing a phone and just flashing it or something. Everything else has been working great and I'm able to change the code so I wont worry myself . Thanks much!
Sent from my SAMSUNG-SGH-I777 using XDA App
I NEED HELP!
Backstory: I was on Abberation rom 1.2 and it had worked perfectly. When I installed version 1.0 it used the AROMA installer and allowed me to pick a launcher. I chose Apex launcher but I didn't install any other launchers. Superuser worked fine and it had run buttery smooth. Aberration runs Siyah kernel.
The issue: Alright, so today I was listening to music and suddenly my phone turns off. I literally was listening to music and that's it. I rebooted it and it told said "please wait android is updating" and that only happens when I flash a new kernel...which is impossible since I don't even have mobile odin installed. Then, Then it said "unfortunately, apex launcher has closed" and it would keep repeating that message, meaning I had no actual launcher to run anything from. I installed launcher pro over the air via the play store desktop version from my computer. It downloaded but wouldn't run. I got a text from my friend and the messaging app worked fine, I could text him and everything so there was nothing wrong there. Then I get home and let it charge (since it was dead). I return later and see that the battery icon that pops up when its charging and the phone is off has a loading icon on it, but it doesn't actually show the battery level. I tried to boot up, but it wouldn't. It would show a blank screen and then go back to the battery icon with a loading symbol on it. Eventually I tried to go to CWM via the three button combo and I ended up with the stock 3E recovery. I am utterly confused and need some serious help from you guys. I didn't do anything so is it the ROM's fault?
Note: I have had experience in flashing ROMs and I have done extensive research on trying to fix this. I've never seen this happen before. Did it somehow revert back to the stock kernel while it ran Aberration?
Thanks for any support or instructions you can give me. I was thinking about using creepyncrawly's instruction to unroot to stock, but it only works for gingerbread and I'm on ice cream sandwich.
shadowskorch said:
I NEED HELP!
Backstory: I was on Abberation rom 1.2 and it had worked perfectly. When I installed version 1.0 it used the AROMA installer and allowed me to pick a launcher. I chose Apex launcher but I didn't install any other launchers. Superuser worked fine and it had run buttery smooth. Aberration runs Siyah kernel.
The issue: Alright, so today I was listening to music and suddenly my phone turns off. I literally was listening to music and that's it. I rebooted it and it told said "please wait android is updating" and that only happens when I flash a new kernel...which is impossible since I don't even have mobile odin installed. Then, Then it said "unfortunately, apex launcher has closed" and it would keep repeating that message, meaning I had no actual launcher to run anything from. I installed launcher pro over the air via the play store desktop version from my computer. It downloaded but wouldn't run. I got a text from my friend and the messaging app worked fine, I could text him and everything so there was nothing wrong there. Then I get home and let it charge (since it was dead). I return later and see that the battery icon that pops up when its charging and the phone is off has a loading icon on it, but it doesn't actually show the battery level. I tried to boot up, but it wouldn't. It would show a blank screen and then go back to the battery icon with a loading symbol on it. Eventually I tried to go to CWM via the three button combo and I ended up with the stock 3E recovery. I am utterly confused and need some serious help from you guys. I didn't do anything so is it the ROM's fault?
Note: I have had experience in flashing ROMs and I have done extensive research on trying to fix this. I've never seen this happen before. Did it somehow revert back to the stock kernel while it ran Aberration?
Thanks for any support or instructions you can give me. I was thinking about using creepyncrawly's instruction to unroot to stock, but it only works for gingerbread and I'm on ice cream sandwich.
Click to expand...
Click to collapse
If you have 3e recovery, then I suppose you have the stock kernel. I have no clue how you would have 3e recovery any other way.
I would suggest you flash back to stock and start over. It doesn't matter that you flash back to Gingerbread, because you will install a custom Gingerbread kernel and then flash whatever you want. I would suggest that you use UCKH7 plus root, and then put a Gingerbread kernel on it. Oh, and just in case, do the wipe data/factory reset in 3e recovery after you flash UCKH7, just in case, you know.