Develop Bugs

What have I done

I have really hosed my phone and have no idea what is going on. So I have been playing around with the puzzle lock mod and deodexed theme for a couple of days. So today I flashed the blue puzzle lock mod to check it out again. Than I made a few image changes to the theme I was using. Flashed it and it won't boot up. Kept saying force closed on google search and a whole bunch of other apps. So I wiped everything dalvik and all. odined the deodexed file again and applied the theme I was using yesterday before any changes. Same thing. So I repeated the process clearing cache formatting sdcard. I tried everything. I should meantion that the phone works fine before I apply the theme. So I odin stock ec05, rooted and applied the theme I have been using for months and it does the same thing. At some point it stopped force closing and just wouldn't boot past the samsung logo. Does anyone have any idea what the heck is going on and how to get this fixed?

crawrj said:
I have really hosed my phone and have no idea what is going on. So I have been playing around with the puzzle lock mod and deodexed theme for a couple of days. So today I flashed the blue puzzle lock mod to check it out again. Than I made a few image changes to the theme I was using. Flashed it and it won't boot up. Kept saying force closed on google search and a whole bunch of other apps. So I wiped everything dalvik and all. odined the deodexed file again and applied the theme I was using yesterday before any changes. Same thing. So I repeated the process clearing cache formatting sdcard. I tried everything. I should meantion that the phone works fine before I apply the theme. So I odin stock ec05, rooted and applied the theme I have been using for months and it does the same thing. At some point it stopped force closing and just wouldn't boot past the samsung logo. Does anyone have any idea what the heck is going on and how to get this fixed?
Click to expand...
Click to collapse
You didn't restore any backups after rooting?

Nope. Nothing. I have tried 20 times at least. I just tried a new cable also.

It sounds like that a update hosed the theme. Was there a update to say your launcher? Sorry all I got

No updates. I am using ODIN to put a clean system on. It boots and everything works fine. I boot into clockwork and apply the theme zip. Same one I have been using for months that has always worked. And it won't boot. I just don't get it. I thought ODIN was supposed to wipe the phone clean. If that is so than what is going on?

crawrj said:
No updates. I am using ODIN to put a clean system on. It boots and everything works fine. I boot into clockwork and apply the theme zip. Same one I have been using for months that has always worked. And it won't boot. I just don't get it. I thought ODIN was supposed to wipe the phone clean. If that is so than what is going on?
Click to expand...
Click to collapse
What root method did you use and is that the same as you had? Did you need to flash a custom kernel first before the theme?

I used the one click root, same one I have always used. I have used the odexed prerooted EC05 and the deodexed prerooted EC05 also. None of them work. No kernels. All stock.

crawrj said:
I used the one click root, same one I have always used. I have used the odexed prerooted EC05 and the deodexed prerooted EC05 also. None of them work. No kernels. All stock.
Click to expand...
Click to collapse
Don't most themes require a custom kernel for things like the boot animation and such?

Not for basic themes. I am not using boot images or anything special. Just image changes mainly. I have never used a custom Kernel. This just doesn't make any sense.

crawrj said:
Not for basic themes. I am not using boot images or anything special. Just image changes mainly. I have never used a custom Kernel. This just doesn't make any sense.
Click to expand...
Click to collapse
After the changes were done, did you re-sign the apps?

Nope. Didn't make any app changes. And I have tried old themes that I have used before any changes and they don't work.

crawrj said:
Nope. Didn't make any app changes. And I have tried old themes that I have used before any changes and they don't work.
Click to expand...
Click to collapse
I would try flashing a custom kernel and see if they work then.

I will try that but like I said I have never used a custom kernel and have never had a problem. I am about to flash the simply-blue-mod-6lockscreens.zip file again to make sure I am not losing my mind. I flashed that file yesterday and earlier today without problems. I am beginning to think something is wrong with the nand or something very serious. I don't know much about this though so I am really lost.

Doesn't ODIN wipe out the nand? If not is there a way to format it?

crawrj said:
I will try that but like I said I have never used a custom kernel and have never had a problem. I am about to flash the simply-blue-mod-6lockscreens.zip file again to make sure I am not losing my mind. I flashed that file yesterday and earlier today without problems. I am beginning to think something is wrong with the nand or something very serious. I don't know much about this though so I am really lost.
Click to expand...
Click to collapse
It may be a bad Odin flash. You could try again and use the .pit and repartition.

I have ODIN'ed more the 20 times now. It looks like it is permissions. I tried fix permissions before but maybe I didn't follow the right sequence or maybe it just took more than once. This time I wiped 3x everything, fixed perms, odin, let boot and sit for a while, boot to cwm and apply theme zip, reboot and it loaded. I am going to try again with the current theme.

crawrj said:
I have ODIN'ed more the 20 times now. It looks like it is permissions. I tried fix permissions before but maybe I didn't follow the right sequence or maybe it just took more than once. This time I wiped 3x everything, fixed perms, odin, let boot and sit for a while, boot to cwm and apply theme zip, reboot and it loaded. I am going to try again with the current theme.
Click to expand...
Click to collapse
Cool. I am just now having a "fix permissions" discussion with another beta tester.

It sounds like odin is working fine and it's the theme that is causing the issue. If you had it working before with that specific combination of firmware+theme and you know it should be working, then it may be the recovery format... What CWM recovery are you using? Is it converting to EXT4, if so is the theme package compatible? I'd recommend using the latest version (if not already) http://forum.xda-developers.com/showpost.php?p=13746457&postcount=1
it doesn't force EXT4 or RFS. Best of luck.

Using 2.5 same as always. Not on ext4. Something is just not right. It is doing it again. I am not sure what is going on.

WTF. Now I think there is some conspiracy by maddoggin to take over all epics . I can flash simply-blue-mod-6lockscreens.zip with no problem. And if I flash a theme that doesn't work after flashing his theme it works. I could see that in some strange deodexed thing but I have flashed back to stock odex and can't get my odex theme to work either, which has always worked. I am about to go nuts over here.

[QUICK AND EASY GUIDE] Go From ANY ROM to CM9

I had a few questions on how to do this. I eventually figured it out and since I didn't see an exact "Guide" on how to do this besides a few posts from the CM9 Discussion thread I decided to post the steps I did here.
Hope this helps somebody!
WARNING: FOLLOWING THIS GUIDE WILL CAUSE YOU TO LOSE YOUR DATA (SDCARD will be fine though).
These are the exact steps I did.
1- Auto Restore Using ODIN via sfhub's TAR file to EL29; here (I used the SPH-D710.EL29_CL852097_ROOTED-oc-sfx.exe)
2- To install CWM, I used the Auto Root package (Option C) then (Option L); here
3- I then downloaded CM7 and GAPPS here and placed them on my microSD card
4- Booted into recovery and wiped data/factory reset, wipe cache, wipe dalvik cache, and go back to "Mounts and Storage" and clicked on format /system. I then flashed CM7 and GAPPS (Directions on how to flash here here)
5- Go back to the main menu of recovery and reboot system
6- I verified I was able to boot into CM7 without any issues (Wait until it completely loads and did another reboot).
(Optional) I went back into recovery and made a backup
7- I then downloaded the CM9 zip file and GAPPS file (Download here scroll down for Alpha4 and GApps v7.1) and placed both of these on the microSD card
8-I then booted into recovery and flashed the CM9 zip file, flashed GApps v7.1 file, and wiped data/factory reset; (how to video here)
9- Reboot system
10- Enjoy CM9!
(Optional) You won't have a custom recovery after you flash CM9. If you want a custom recovery, I recommend you use this one here. I flashed it through Mobile ODIN and had no problems. I used the "Rogue Stock FB21 rev2 (Odin Tar)". Read this post if you want to flash through regular Odin here

Thank you very much. I was looking for something just like this
EDIT: Why can't you flash straight to CM9?

Korey_Nicholson said:
Thank you very much. I was looking for something just like this
Click to expand...
Click to collapse
Not a problem! Happy to share this stuff for everyone

Vandam500 said:
Not a problem! Happy to share this stuff for everyone
Click to expand...
Click to collapse
Why can't you flash straight to CM9?

Korey_Nicholson said:
Why can't you flash straight to CM9?
Click to expand...
Click to collapse
Honestly I'm not sure. I've seen several posts of people having issues when trying to go from any of the leaked ICS ROMs to CM9 (Some of them semi-bricking their devices). This is apparently the safest way to do it.

Korey_Nicholson said:
Why can't you flash straight to CM9?
Click to expand...
Click to collapse
You can but you keep hearing people saying "iz brickz my fone" all the time because they tried to install CM9 with a kernal or rom that doesnt play very nice. So this is in a way the safest way to do it if you dont want to have any trouble. Ive been doing it like this since thats what someone posted on the cm9 thread when it first came out.
Edit: lo0l you beat me to the reply

Sounds good. Doesn't CM9 come with a kernel though?
If not, which kernel do you recommend using with CM9?

Korey_Nicholson said:
Sounds good. Doesn't CM9 come with a kernel though?
Click to expand...
Click to collapse
Ya it does since its an AOSP kernal.

Sephirothvfc said:
Ya it does since its an AOSP kernal.
Click to expand...
Click to collapse
Which kernel do you recommend using with CM9? What comes with it?

Korey_Nicholson said:
Which kernel do you recommend using with CM9? What comes with it?
Click to expand...
Click to collapse
At the moment thats the only kernal you can use with it. no other AOSP kernal out there that is available to download. Atleast this is from what i understand. First time rooting phones after i got this phone. Still getting the hang of all this.

Vandam500 said:
I had a few questions on how to do this. I eventually figured it out and since I didn't see an exact "Guide" on how to do this besides a few posts from the CM9 Discussion thread I decided to post the steps I did here.
Hope this helps somebody!
WARNING: FOLLOWING THIS GUIDE WILL CAUSE YOU TO LOSE YOUR DATA (SDCARD will be fine though).
These are the exact steps I did.
1- Auto Restore Using ODIN via sfhub's TAR file to EL29; here (I used the SPH-D710.EL29_CL852097_ROOTED-oc-sfx.exe)
2- To install CWM, I used the Auto Root package (Option C) then (Option L); here
3- I then downloaded CM7 and GAPPS here and placed them on my microSD card
4- Booted into recovery and wiped data/factory reset, wipe cache, wipe dalvik cache, and go back to "Mounts and Storage" and clicked on format /system. I then flashed CM7 and GAPPS (Directions on how to flash here here)
5- Go back to the main menu of recovery and reboot system
6- I verified I was able to boot into CM7 without any issues (Wait until it completely loads and did another reboot).
(Optional) I went back into recovery and made a backup
7- I then downloaded the CM9 zip file and GAPPS file (Download here scroll down for Alpha4 and GApps v7.1) and placed both of these on the microSD card
8-I then booted into recovery and flashed the CM9 zip file, flashed GApps v7.1 file, and wiped data/factory reset; (how to video here)
9- Reboot system
10- Enjoy CM9!
(Optional) You won't have a custom recovery after you flash CM9. If you want a custom recovery, I recommend you use this one here. I flashed it through Mobile ODIN and had no problems. I used the "Rogue Stock FB21 rev2 (Odin Tar)". Read this post if you want to flash through regular Odin here
Click to expand...
Click to collapse
I flashed the Rogue Stock FB21 kernel like you said. Is it suppose to give me the yellow triangle on the splash screen?

Korey_Nicholson said:
I flashed the Rogue Stock FB21 kernel like you said. Is it suppose to give me the yellow triangle on the splash screen?
Click to expand...
Click to collapse
If you odin a kernal into your phone even if its stock, yes it will give you the yellow triangle

Sephirothvfc said:
If you odin a kernal into your phone even if its stock, yes it will give you the yellow triangle
Click to expand...
Click to collapse
NoOoOoOo! I was such a good boy lol

Korey_Nicholson said:
NoOoOoOo! I was such a good boy lol
Click to expand...
Click to collapse
You can always redo step 1 and 2 and it will remove it. Then just restore your last backup of the El29 rom not CM9 lol

You can always just use this on ics
http://forum.xda-developers.com/showthread.php?t=1494114
Works great on cm9
Sent from my SPH-D710 using XDA App

Epix4G said:
You can always just use this on ics
http://forum.xda-developers.com/showthread.php?t=1494114
Works great on cm9
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
+1 to this Got rid of mine after I Odin'd in the FB21 kernel as well. It's now forever on my sdcard from here on out for ICS related stuff.

Korey_Nicholson said:
I flashed the Rogue Stock FB21 kernel like you said. Is it suppose to give me the yellow triangle on the splash screen?
Click to expand...
Click to collapse
I saw the yellow triangle on the screen but it always went past it and booted right into the ROM. Is that what you mean't?

I just flash stock CWM, wipe everything including system, and then flash CM9. Perfect all the way
Sent from my SPH-D710 using XDA App

I was on the leaked ICS ROM and want to go back to a different ROM. My phone is kinda soft bricked now. I downloaded the EL29 auto restore and it's running now but it's stuck at the last percentage (data.img) part.
It's been sitting here for 30+ minutes and last night I let it sit for about 1.5 hours.
My phone won't boot up but I can get into download mode but it won't auto restore to the EL29. I don't know what I'm missing. Any help would be appreciated.
Thanks.

Android300ZX said:
I was on the leaked ICS ROM and want to go back to a different ROM. My phone is kinda soft bricked now. I downloaded the EL29 auto restore and it's running now but it's stuck at the last percentage (data.img) part.
It's been sitting here for 30+ minutes and last night I let it sit for about 1.5 hours.
My phone won't boot up but I can get into download mode but it won't auto restore to the EL29. I don't know what I'm missing. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
sorry my friend but its time to exercise your Insurance. Look in general as there is a specific thread for your issue. Did you use the Hitman recovery from Steady Hawkin?
Your phone is bricked
http://forum.xda-developers.com/showthread.php?t=1504808 - You may want to look at this one
http://forum.xda-developers.com/showthread.php?t=1509795
http://forum.xda-developers.com/showthread.php?t=1516868
http://forum.xda-developers.com/showthread.php?t=1524463
There's more just did not want to clutter the thread up anymore

T989D/Rom manager/ Downloading roms

Ok I looked all over the place and I could find anything about this issue. I have the telus s2x t989d and I went on rom manager and downloaded cyanogenmod 9 for my phone( only one available). Then I went in to install it and when it finished it just stayed on the really cool cyanogen boot screen and I had to power off and restore. Ive tried it a few times and nothing changed. I wiped the cache and stuff too. what should I do?

Are you trying to lead it directly from the app or are you trying to flash from recovery? Rom manager is buggy on the t989/t989D series. Flashing from an app is not recommended AT ALL due to potential of bricking the device
I guess my question is, what's your exact process you took...(i.e. steps taken)
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!

Ya I have been using the app. Can I still use the app to download roms? And then can I go into recovery from the app or just exit it and reboot it myself?

LostMoonOfPoosh said:
Ya I have been using the app. Can I still use the app to download roms? And then can I go into recovery from the app or just exit it and reboot it myself?
Click to expand...
Click to collapse
its recommended to simply download the rom zip the boot into recovery and install there. I use cm9 stable with tdj Darkside kernel 6 and flash everything through twrp recovery never had a single boot loop in any room I've flashed. What rom are you running currently?
1.Download rom and place in external sd card.
2. Reboot into recovery
(You may want to wipe data/factory reset depending on what rom you are running and clean install are typically recommended unless coming from a previous version from same developer (i.e. cm, aokp, etc)
3. Flash darkside super wipe and cache wipe if using cwm non touch
4. Flash rom, gapps and kernel (if so desired on the gapps and kernel)
5. Reboot and wait 10mins
6. Reboot again and have fun!
Let me know if that helps
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!

EnigmaticGeek said:
its recommended to simply download the rom zip the boot into recovery and install there. I use cm9 stable with tdj Darkside kernel 6 and flash everything through twrp recovery never had a single boot loop in any room I've flashed. What rom are you running currently?
1.Download rom and place in external sd card.
2. Reboot into recovery
(You may want to wipe data/factory reset depending on what rom you are running and clean install are typically recommended unless coming from a previous version from same developer (i.e. cm, aokp, etc)
3. Flash darkside super wipe and cache wipe if using cwm non touch
4. Flash rom, gapps and kernel (if so desired on the gapps and kernel)
5. Reboot and wait 10mins
6. Reboot again and have fun!
Let me know if that helps
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Click to expand...
Click to collapse
So I should just find the rom on my computer instead then?

Im downloading cyamogenmod 9 now from their website. I guess rom manager is pretty much useless for me then? I liked it because it would only show me roms that work for my phone so I dont make any mistakes.

ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...

LostMoonOfPoosh said:
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
Click to expand...
Click to collapse
I would use only super wipe
then flash ROM
reboot
wait ten minutes WITHOUT TOUCHING ANYTHING!!
reboot.
Its a proven formula that has worked for me, many, many times
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Also, super wipe and cache wipe are found here read OP carefully
http://forum.xda-developers.com/showthread.php?t=1477955

LostMoonOfPoosh said:
ok I did it. but it didnt work... it just loaded up stock unrooted ics. with all my stuff gone. i have backups so im not worried about that, but i dont know why CM didnt flash...
Click to expand...
Click to collapse
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?

EnigmaticGeek said:
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
Click to expand...
Click to collapse
is work fist root then factory reset then flash.

kiruba8 said:
is work fist root then factory reset then flash.
Click to expand...
Click to collapse
You need to have a recovery flashed to your phone to even start the root process. Cwm, cwm touch, or twrp. All are available in the sticky section as well as development section. If you are running stock recovery then that's your primary issue.
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!

LoopDoGG79 said:
I would use only super wipe
then flash ROM
reboot
wait ten minutes WITHOUT TOUCHING ANYTHING!!
reboot.
Its a proven formula that has worked for me, many, many times
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Also, super wipe and cache wipe are found here read OP carefully
http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
Ok i looked at the darkside link you gave me. Will it for sure work with the telus version s2?

LostMoonOfPoosh said:
Ok i looked at the darkside link you gave me. Will it for sure work with the telus version s2?
Click to expand...
Click to collapse
Yes, the only difference between T-Mobile and Telus versions is cosmetic. Telus is the T989D, T-Mobile is the T989. There is a reason why they are so closely named.
Sent from the pink Unicorn from the Darkside.

EnigmaticGeek said:
Stock unrooted ics? What recovery are you using, have you flashed a recovery through odin at all with this device?
Click to expand...
Click to collapse
oh ya I have CWM recovery flashed so im good in that department. Im going to try out darkside superwipe now and see if that helps.

well I used darkside and then flashed my rom. Now it wont even go past the telus loading screen... Ive restored back again. I made it alot farther than this with rom manager haha. I actually saw the cyanogenmod opening cinematic... Ill try the darkside cache wipe this time and see if that helps. I downloaded the rom right from the cyanogen website...

Well neither is working. It just stays in the Telus loading screen. Not even the Samsung screen will load. I don't know what else to do...
Sent from my SGH-T989D using xda app-developers app

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.

Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway

CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?

You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"

CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.

Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.

A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!

cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!

Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?

cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't

So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.

cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.

Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).

So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!

cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.

Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app

cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?

Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

Everytime I reboot my phone is stuck at the Logo

I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?

nayte1993 said:
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
Click to expand...
Click to collapse
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing

C.Sweat said:
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
Click to expand...
Click to collapse
Could I return to stock using Odin? If so I'll try that when I'm able too.

nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
Yeah you sure can. :good: Go here for instructions and stock firmware

nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
try a factory reset/wipe first, before you go to stock again

Bob Hodges said:
try a factory reset/wipe first, before you go to stock again
Click to expand...
Click to collapse
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.

nayte1993 said:
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
Click to expand...
Click to collapse
AFTER you flash stock rom, perform factory reset wipe, and you wont get stuck. flash recovery. and then flash custom rom and you should be fine

wrong kernels...period

TheAxman said:
wrong kernels...period
Click to expand...
Click to collapse
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.

nayte1993 said:
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
Click to expand...
Click to collapse
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.

Toleraen said:
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Click to expand...
Click to collapse
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.

nayte1993 said:
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
Click to expand...
Click to collapse
That's a matter of preference...just make sure to pull a TW kernel. Of course, the kernel built into Wicked should work just fine as well.
I've been a fan of ktoonsez's kernel (link in my sig). 7/7 got a little crashy on me, but 7/2 has been running smooth

Problem fixed, thanks everyone.