Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
JesseBeckett said:
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
Click to expand...
Click to collapse
Could be a long way off here, but are you sure the download wasn't corrupted, a statusbar and black screen sounds to me like the launcher wasn't opening, or wasn't flashed.
Also what version of CWM are you using? I would download rom manager and flash the latest version, then try flashing slim again.
JesseBeckett said:
Hi,
I have a Galaxy S3 i9300 currently running CM10.1. I just tried to flash Slim Bean 2.2 on my S3 as that's the only download available. However after flashing the ROM and G-Apps in CWM, when I boot the phone gets stuck at where the setup menu should be. Like when it should ask for Wi-Fi password etc, it just shows a black screen but the notification bar is there and working. At first nothing would work, but after a cache wipe, it said Android is upgrading (54 apps) but was still a black screen. However I could access settings and change anything I wanted, but the home button wouldn't take me to home screen. I print screened to try get to home through the gallery but the button still doesn't work. I booted without G-Apps to see if that was the cause and same problem. I have wiped everything and reflashed several times, still doesn't work. I have to flash through my external SD because when I put the .zip on my internal they don't show up in CWM. I am back on CM10.1 from a backup however I would much rather Slim Bean as I can tell from my "demo" access to it, it seems far far smoother. How can I fix the issue so I can use it?
Thanks
Click to expand...
Click to collapse
First of all, the newest version of Slim Bean available for the S3 is 3.1, which you can download here:
http://www.slimroms.net/index.php/downloads/all/viewcategory/152-i9300
I would suggest doing a full wipe and installing this (much newer) version... I'm using it and it's awesome. Hope this helps.
Wrong section, post in QA
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
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.
Hello all.
I have a Galaxy S3 (i9300) and changed the stock rom to CyanogenMod 10.1. As I was not satisfied with the camera I decided to go back to stock. I downloaded the foirmware in sammobile.com sock and put the rom with odin. After that I had several problems. I tried other versions of the stock rom, but nothing worked. When I turn on the phone, it takes longer than normal on the first screen (the first screen to turn on, where it appears samsung galaxy s 3). After the android loads, everything works normally, but when you connect the phone to pc it is not recognized, and the worst of the problems, when he gets some time with the screen off (locked) when I click to wake it, it takes too long to turn on the screen, or does not care, having to be restarted. I think he does not shut down, but is frozen with the screen off. When this happens I get the impression that the phone FIVA a little warm.
Can you help?
Thank you!
R: [Q] Problems back to stock
It looks like you mightve flashed the wrong stock version of the rom.
Also under my point of view cyanogenmod is not stable enough for s3, it is intelligible after all since the s3 is not in desperate need of updated roms for now, also there are mo stable 10 builds yet. I guess u chose cyanogen because it is very popular or because ure used to it, but ill go ahead and suggest anyways u flash jellybam or foxhound or rootbox roms, they are very stable and well developed.
As for the camera app: simply go into stock rom and thru titanium backup make a backup of the camera app(its advisable to clear app cache and data first), then flash the new rom and stuff, and then reinstall titanium backup and install the app backup. It should be easy since i own both original jelly bean camera and samsung galaxy s3 stock camera apps on my phone... reverting back to stock is useless once u got the power of the dark side of root
Sent from my GT-I9300 using xda app-developers app
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.
Hello,
please help me with my S3 ( I9300 ).
Since 8 days I´m encountering a strange behaviour with my S3.
I assume it hast to do with partitions and / or false use of TWRP.
I´ve already flashed numerous times with different phones and recoveries and odin. I Never had any issues before.
Discription : Wiping partitions by recovery does not seem to work. When installing a new rom by TWRP or CWM I end up with two mingeld systems and old apps or I have a clean system but there are absolutely no widgets. When formatting system with TWRP / CWM I sometimes get an error "
I´ve already installed JB stocfirmware with odin with pitfile, repartition and nand erase and that system worked. Fusion rom KK worked too ( installed through recovery ).
But installing omnirom lollipop failed again. Resetting through android factoryreset left my with a clean system but with no widgets at all again.
WTF is going on ?
I think it all started when I used TWRP and did the "fix permission " thing. But I´m not sure there.
I can´t pinpoint what makes installing a rom fail or work . Pehaps I need to completly delete all partitions and rebuild my S3 from scratch ?
Slimkat and Fusionrom ( both KK ) worked at one time and Fr can be restored by TWRP.
Any help would be greatly appreciated !!!!!!!!!!
I just want to be able to try out new roms without running into these problems again.
@Skyfire1:
1. Missing widgets aren't caused by corrupt partitions.
2. FacoryReset from settings maybe not executed correctly in connection with TWRP - reset from TWRP.
3. Try another LP-ROM, if there are still errors.
Thank you. Then what causes the missing Widgets effect? Installing Slimkat worked one time and then again not the other time ? Maybe I have ore than one problem ?
@Skyfire1: I didn't saw/read anything about this. Test gradually. Make shure that JB-Firmware +TWRP 2.8.6.1 work correctly (download all files freshly to avoid fe 9305-choice). Then try a slim LP-ROM, fe Euphoria whithout GApps or other apps (SlimROM is outdated atm) .
Installed euphoria by twrp and no widgets again. But they are there , they just don`t show when using appdrawer button. Longpress on screen makes them available. Is this just a change in Android or what ? I´d feel pretty stupid if that was all
@Skyfire1: I usually don't use stock launcher, but shall flash the actual build from today and will look at your issue.
To whom it concerns: on HomeScreen long tap opens the available widgets. Long tap on a widget and move to place it on HomeScreen.
rp158 said:
@Skyfire1: I usually don't use stock launcher, but shall flash the actual build from today and will look at your issue.
Click to expand...
Click to collapse
I don`t as well. Nova works fine for me
rp158 said:
@Skyfire1:
To whom it concerns: on HomeScreen long tap opens the available widgets. Long tap on a widget and move to place it on HomeScreen.
Click to expand...
Click to collapse
I knew about that. It´s only that I never used that method. I always went to the appdrawer and swiped to the right...
When that didn´t work anymore and the problems with the wiping occured I thought it to be one problem with different effects.
So everything seems to be fine again . I`ll do some testing and flashing .
What I learned from this is that wiping may or may not work and that changes in behaviour of the launcher can have more than one reason.
Thanks a lot for all your help!!!!