Possible brick going back to the stock rom - Galaxy S III General (US Carriers)

I was flashing back to stock from CM9. I had already done it successfully earlier. However this time something went wrong and I don't understand what.
1. Wiped user data and dalvik cache using CWM.
2. Used the rom from here. Same file I used the first time.
3. Flashed using odin. Used PDA, and only Auto Reboot was checked.
I can't get it to turn off without pulling the battery. Trying to use the power button to turn it off just causes it to restart. In the video, the phone was powered on right before the start of the video.
Any advice welcome regarding where to go from here. Thanks.

try again, had the same issue, i just did it again and it worked

polish_pat said:
try again, had the same issue, i just did it again and it worked
Click to expand...
Click to collapse
Tried again at least 3 or 4 times with the same result.

You also have to go into the mounts section in cwm and format /system whenever you flash a completely different ROM.
Sent from my Sprint Galaxy S3

mercado79 said:
You also have to go into the mounts section in cwm and format /system whenever you flash a completely different ROM.
Sent from my Sprint Galaxy S3
Click to expand...
Click to collapse
Now that I'm in this situation, is there any recourse?

vinuneuro said:
Now that I'm in this situation, is there any recourse?
Click to expand...
Click to collapse
Can you get into CWM still?

Was informed about recovery mode. Clearing user data and cache there, and rebooting did the trick.

Related

[Q] Unable to Reboot

Hi guys. Need your help on this one. I flashed the latest omega rom and successfully restored my data. But whenever i reboot or power my phone off it can boot up past the samsung s4 logo. I would have to go back to recovery (twrp) format data. Then restore from back up then it can boot up. I would have to do it every time. I already tried reflashing the omega rom. After wipe but same thing the moment i reboot it will not het past the s4 logo. Any idea on this one. I really need help
mirvashstorm said:
Hi guys. Need your help on this one. I flashed the latest omega rom and successfully restored my data. But whenever i reboot or power my phone off it can boot up past the samsung s4 logo. I would have to go back to recovery (twrp) format data. Then restore from back up then it can boot up. I would have to do it every time. I already tried reflashing the omega rom. After wipe but same thing the moment i reboot it will not het past the s4 logo. Any idea on this one. I really need help
Click to expand...
Click to collapse
U can try two thing first
Go to recovery and wipe cache and dalvik cache and then reboot
Reboot and see if the problem is solved
If not the go to settings and reset the device and reboot this should clear that problem let me know what happens
Sent from my GT-I9500 using xda premium
123hiten said:
U can try two thing first
Go to recovery and wipe cache and dalvik cache and then reboot
Reboot and see if the problem is solved
If not the go to settings and reset the device and reboot this should clear that problem let me know what happens
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Thanks! Currently trying that. Will let you know right away....
Same thing cant get past Samsung s4 logo...
I will try to go back to stick rom using http://forum.xda-developers.com/showthread.php?t=2265477
Hopefully this works.
I have just finish flashing the official stock rom for my country and the carrier. Went through all the Software update. BOOM! now working.... Im just wondering what happened. but i am so glad i have my s4 up and running again. No more bootloops for me
mirvashstorm said:
I have just finish flashing the official stock rom for my country and the carrier. Went through all the Software update. BOOM! now working.... Im just wondering what happened. but i am so glad i have my s4 up and running again. No more bootloops for me
Click to expand...
Click to collapse
Good to hear that & bootloop happens for some system files clashing Etc
And ya to to be out of the issues i suggest do a full reser from ur device if u have not done that :good:

Stuck on Samsung Custom Screen w/ Custom ROM

Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Flash a different kernel.
Period
your welcome
TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.
what procedures are you using for all of this? is there a specific guide you are following?
xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.
jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.

Got rooted, installed custom recovery, lost root, now i'm confused...

So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.

[Q] Soft-Brick Assistance

Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
_retro said:
Note: I may not use terms correctly, I have spent the past hour reading threads similar to mine in order to (hopefully) use the correct terms to describe my predicament.
I was using TriForce ROM 3.0 and I wanted to mix things up a bit because it was too much like the stock ROM. I found Negalite S4 and tried my hand at that, with devastating consequences. I booted my phone into TWRP did a wipe and then proceeded to install the Negalite S4.zip onto my phone. It got stuck in a boot loop. After a good 30~ minutes of it continuously rebooting I turned it off and booted back into TWRP. However, now that my phone was wiped, it is not a recognized device by my computer any longer. Since I wiped the phone clean the .zip is no longer on my phone either. So, all I have now is a phone that can boot into recovery (TWRP); which is a soft-brick (correct me if I'm wrong).
I have read other threads and the xda community informs the user to use KIES or ODIN (I have used ODIN once before). However, try as hard as I can to understand their directions... I don't know what to do with ODIN.
My computer does not recognize my device at all. It will only boot into recovery otherwise it's stuck in an infinite boot loop. I am really scared that I have ruined such a valuable phone and so I am not thinking clearly - which is only adding to my "noobishness."
Can anyone please help me out in a way that I can understand? All help is much appreciated!
Click to expand...
Click to collapse
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
_retro said:
Thank-you for the detailed response, I'll get started now! I did wipe the SD card, you're right. I'm so glad that you posted, thanks again.
If I need help I'll edit this post (no bumping within 24 hours). I'm hoping I have enough smarts to knock this out though. Again, thank you so much.
EDIT: Excuse my ignorance. I'm not sure what MDL stock is, I figured it was the default ROM - I have a nandroid of that. However, even after re-installing the samsung drivers, rebooting both my phone and computer - nothing happens. I don't know how to proceed from here. I can imagine I'm becoming a pain and do apologize.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
ROMANTiC KiD said:
http://forum.xda-developers.com/showthread.php?t=2375523
The link above is the tar file for stock MF9. If you just use the link for the from the first post you just need to download the first file (not the kernel). Once downloaded you need to extraxt that zip and you will get a .tar.md5 file from it. Later open odin and make sure only auto reboot is checked. Click on the PDA slot and find the .tar.md5 file you downloaded click on it. Next put your phone into download mode and connect it to your computer. Wait for it to install drivers and you will see a yellow box with "com:[some number]" once you see that click start and from there let it do its thing and whoola you have your phone back to MF9 stock. Good luck!
Sent from my SPH-L720
Click to expand...
Click to collapse
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
_retro said:
Well, you did it! That post is solid, I understood every-bit! My phone (most likely) is downloading the firmware now. I don't know how long it will take to get off the "Downloading... Do not turn off target !!" screen, but I'll edit this post after letting it sit over night! Thank you both so much.
Click to expand...
Click to collapse
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
ROMANTiC KiD said:
Your welcome glad to help again, should take less than 10 mins. If its more than that just reboot your computer and repeat the steps from opening odin and finding your file. Another GS4 saved ;D
Sent from my SPH-L720
Click to expand...
Click to collapse
You were right, it was quite snappy. I cannot believe I was so panicked over this! My babies safe ... for now.
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
reverepats said:
So how did Twrp wipe nor SD card? When by boot into recovery and immediately click on Wipe, it'll wipe everything Necessary except the internal and external memory. Did you click the option to choose what you want to wipe? Happens more than ya may think, cause I've done it myself lol. Good to hear it's back up, I still get freaked out by those occurrences
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
It wasn't human error through TWRP, it was an error while flashing Negalite. It asks if you want to wipe everything, data, or nothing at all. Silly me thought let's wipe EVERYTHING! Heheh
3ncrypt3d said:
Okay, download and install Samsung drivers from the Internet if your phone isn't installing them on its own. Download MDL stock. Open ODIN. Put your phone in download mode. ODIN should see your phone. Flash stock MDL. Use goo manager to install TWRP again after your booted on stock MDL. Or use ODIN to do it. Redownload the custom ROM you want and then flash in TWRP. Also wiping the phones dalvik, cache system ect shouldn't have erased your SD card in the first place. You mist have accidentally checked the wipe SD card in advanced wipe options. You never need to do that. So next time also have a nandroid backup on your external SD. I keep one on internal as well in case external card goes bad cause sometimes that happens. And never select that wipe SD card option. Unless of course you really do want to wipe your SD card. Don't do that and keep a full backup of your last working ROM and you'll not have this problem again.
Click to expand...
Click to collapse
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Ridddeathmetal said:
ODIN IS NOT RECOGNISING MY PHONE ...WHAT TO DO????:crying::crying::crying:
Click to expand...
Click to collapse
Reinstall drivers, use different USB ports, used different USB cables?
Sent from my SPH-L720 using xda app-developers app
romantic kid said:
reinstall drivers, use different usb ports, used different usb cables?
Sent from my sph-l720 using xda app-developers app
Click to expand...
Click to collapse
tried 4 ports...in different pc also but same result used 3 cables...but none recognising it.....drivers have been downloaded and reinstalled

Stuck on Galaxy S4 Boot logo after setting up Alpha S4

I tried searching the ROM thread but with 70 pages worth of comments, it's hard to see anything even if i search using keywords.
My issues is, i tried installing Alpha S4, everything goes well, i go though aroma installer, the rom installs, boots up fine, i can play around with it for a while, restore all my apps, setup 3minit and all my other stuff. My problem is once i reboot, i get stuck on the boot logo for ever and ever. No matter what i do, clear cache and dalvik (which usually works for this issue) i just keep getting stuck. It's not a boot loop, because it doesn loop, it just hangs there.
I'm not sure what to do, ive formatted and re-installed the ROM at least 6 times today, no matter what i do, i get the same issue. At first i though, maybe if i reboot after setting up my apps, or each time i change 3minit settings, but now i've just let the rom boot, skipped the startup screens and rebooted and i get locked up again
Any suggestions?
I Have i337m, used bioshock kernel, if that helps
polish_pat said:
I tried searching the ROM thread but with 70 pages worth of comments, it's hard to see anything even if i search using keywords.
My issues is, i tried installing Alpha S4, everything goes well, i go though aroma installer, the rom installs, boots up fine, i can play around with it for a while, restore all my apps, setup 3minit and all my other stuff. My problem is once i reboot, i get stuck on the boot logo for ever and ever. No matter what i do, clear cache and dalvik (which usually works for this issue) i just keep getting stuck. It's not a boot loop, because it doesn loop, it just hangs there.
I'm not sure what to do, ive formatted and re-installed the ROM at least 6 times today, no matter what i do, i get the same issue. At first i though, maybe if i reboot after setting up my apps, or each time i change 3minit settings, but now i've just let the rom boot, skipped the startup screens and rebooted and i get locked up again
Any suggestions?
I Have i337m, used bioshock kernel, if that helps
Click to expand...
Click to collapse
Is it a 4.3 rom? And what recovery are you using?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
its a 4.2 rom and i'm using twrp...here is what a member in the rom thread suggested, i'll try it and report back
GrandMasterB said:
You are using TWRP and you have selected 'format data' and typed YES to continue. Either way the only way to fix it is to Odin back to stock and make sure you don't do it again. Its a TWRP/S4 bug that has not been fixed yet. I still prefer TWRP personally but you have to make sure you don't select the 'format Data' button or use shabbys or philz recovery instead.
Click to expand...
Click to collapse
polish_pat said:
here is what a member in the rom thread suggested, i'll try it and report back
Click to expand...
Click to collapse
it worked for anybody with the same issue...dont wipe data in twrp
polish_pat said:
it worked for anybody with the same issue...dont wipe data in twrp
Click to expand...
Click to collapse
What version of twrp did you use?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
What version of twrp did you use?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
the latest goomanager provides...not sure what it is, i'm guessing its 2.6.1.0

Categories

Resources