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.
Related
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!!!
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
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
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
Hey all
So after a botched Cyanogenmod install on my AT&T GS3, I am having some issues with the stock ROM. Here's what happened: I tried to install CM using the windows installer, everything went well until the end and then I got a prompt on the phone prior to it rebooting "Root access lost, fix? Yes/No". Regardless of choice, phone would always boot back to stock ROM. Asked for some advice on the CM forum and was told KNOX was the issue. I then rooted the phone using Towelroot, and then installed Super SU. Super SU when opened for the first time said KNOX was installed, did I want to disable it, I chose YES. Re-tried CM installer, same issue, just boots back to stock ROM.
At this point I gave up and just re-installed all my apps and settings, synched my Google account etc. Since then I can no longer download anything from any Google app, it just says "Download failed". So Gmail attachments, links, Chrome etc. nothing downloads. Although stock Internet downloads are fine. Swiftkey now errors saying "Cannot save language pack" then crashes, Swype keyboard keeps on re-enabling itself after I turn it off, and apps that worked fine before are crashing like crazy.
Last night I performed a wipe/factory reset after starting in recovery mode. This did not help. I also noticed that recovery mode boot screen is Cyanogenmod boot screen still, so guessing factory reset is not exactly a full factory reset and it just wipes data/cache etc.
Seems to me like some kind of permissions issue. I downloaded Root Explorer and had a poke around. Permissions look fine (read/write etc.) on Downloads folder. Only thing that looked odd was there are 3 different file system areas so 3 different downloads folders (ie sdcard0/0/Downloads, storage/0/downloads and storage/legacy/downloads). Not sure if that is normal.
Just want to put it back to how it was. Any suggestions what to do next?
Cheers.