Related
So i did the ULVH1 update through ODIN, followed the instructions. Once i was on ODIN picked the file for it. Ran it at firt it said Boot! Then Pass! So phone trys to reset but i get stuck on the reboot screen! Did i just brick the phone? Im rooted and using a custom rom (jedi mind trick v7). I need help on this.
Oh onre more thing. When i was stuck on the reboot. I tried getting into CWM and it got me through. Aren't i suppose to be unrooted already once this update occured?
Reboot loop? If you can get into CWM, you can always wipe, flash, wipe cache to fix things. If you can get into CWM you're still ok.
Now the thing about unroot and recovery, there's sort of different things. You can be unrooted, but still have CWM. CWM just lets you flash new ROMs that aren't manufacturer certified, I believe. I forget the details. So booting into ICS you could be unrooted, but the recovery is still CWM/TWRP
You are much better off using TWRP then CWM.
premiatul said:
You are much better off using TWRP then CWM.
Click to expand...
Click to collapse
Would you still use TWRP to flash roms that the OP recommends using CWM or CWM Touch?
I also understand NAND backups you made with CWM won't be restored successfully by TWRP?
So I got it to work. Im a noob on this stuff, so i wasnt sure if the file that XDA had was bad or not. I used a diff. one from phandroid.com. Went through ODIN and it went through with no problem. Lost root and CWM. Basically im back to stock. I eventually rooted again and CWM. But the funny part about it is that why do i still have my pics on the gallery? I thought this deletes everything? Like i said. Im a noob! lol. Everything seems working fine. Screen shots (went back the old way, instead of Power and Volume down.) Also, ISIS is that on google play? :good:
No flashing back to stock does not erase your internal storage.
Sent from my SGH-T989 using xda app-developers app
Still a major noob here. I want to get cyanogenmod 10 onto my s3 but I've had issues ever since putting on UVALH3. If I want to get CM10 can someone walk me through all the steps to get there, or is it just impossible?
ambitionlessness said:
Still a major noob here. I want to get cyanogenmod 10 onto my s3 but I've had issues ever since putting on UVALH3. If I want to get CM10 can someone walk me through all the steps to get there, or is it just impossible?
Click to expand...
Click to collapse
Do you have a recovery installed like CWM or TWRP? Lets start with that.
sipple31 said:
Do you have a recovery installed like CWM or TWRP? Lets start with that.
Click to expand...
Click to collapse
Could it be I was supposed to do this before flashing CM10? Because I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
isikh said:
Could it be I was supposed to do this before flashing CM10? Because I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
Click to expand...
Click to collapse
pretty sure having a custom recovery isn't your issue if you are to the point of wiping caches and flashing kernels. The OP is asking how to wipe a stock ROM off and get CM on his/her phone i'm pretty sure.
sipple31 said:
pretty sure having a custom recovery isn't your issue if you are to the point of wiping caches and flashing kernels. The OP is asking how to wipe a stock ROM off and get CM on his/her phone i'm pretty sure.
Click to expand...
Click to collapse
I was asking about myself because I thought I had a similar problem
sipple31 said:
Do you have a recovery installed like CWM or TWRP? Lets start with that.
Click to expand...
Click to collapse
No i do not. I tried rooting my phone and it didn't take, and you need to root before CWM right? I had CWM when I was on Uvalh2 but when I went through the process of Uvalh3 I guess I lost it. Should I go ahead and do it? I have the zip file in my phone, still.
I should also mention that when I go into recovery the android dude is fallen over, dead. I'm guessing that's a bad sign.
That just means you're on stock recovery. Odin a rooted rom which you can find in the dev forums (root without tripping flash), then install twrp or cwm, then flash cm10, then flash desired radio.
Sent from my SGH-T999 using xda app-developers app
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?
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.
I am returning my phone to my dad because i'm getting an upgrade and he wants to sell it, so i tried to revert to stock from CM12.1 unofficial nightlies. I flashed the FNJ1 system and boot.img. my phone was on FNJ1. now it's stuck on the at&t logo and i cant do anyhting, any help?
AT&T SGH-I747 UCUFNJ1 CM12.1 unofficial nightly.
Edit: In the mean time i've reverted to cm12 but i still need to revert to stock so any help is greatly appreciated.
You have to factory reset after flashing back to stock. If you are going to sell it, I suggest doing so from stock recovery.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You have to factory reset after flashing back to stock. If you are going to sell it, I suggest doing so from stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I reflashed the FNJ1 rom and then factory reset afterwards and it still hangs at the AT&T boot logo, any other suggestions?
Where did the rom come from exactly? There are a few that I've seen. Did you check the md5 to make sure the download wasn't corrupted?
Can you verify your bootloader / baseband?
Using terminal emulator (twrp has one built in) enter this.
getprop ro.bootloader
getprop ro.baseband
Let us know what it says.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Where did the rom come from exactly? There are a few that I've seen. Did you check the md5 to make sure the download wasn't corrupted?
Can you verify your bootloader / baseband?
Using terminal emulator (twrp has one built in) enter this.
getprop ro.bootloader
getprop ro.baseband
Let us know what it says.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i used Enewman's fnj1 system and boot.img from the general forum here. and i cant boot into recovery only download mode, but i know for sure it was ucufnj1
also the other post is me:
We will need more detailed info if you don't mind.
What were you on before? cm 12.1
What "stock rom" and what recovery exactly did you flash. enewman's fnj1
How did you flash? cwm
You said it "still doesn't boot" but we're able to flash it, do you mean it just won't boot android? yes
Can you boot download mode? yes
What was wrong that made you need to flash the rom and recovery to make it boot, and how did it get to that point to begin with? need to get to stock to sell, wouldnt boot, and the soft brick help said to try flashing stock recovery.
I managed to boot into recovery by flashing an older version of CWM via Odin. i flashed CM12.1 back again and it boots! thank god i have a phone again. any ideas as to what is causing the softbrick?
Hard to say. I do know that enewman17 recommends flashing with twrp, and that's what most people have used AFAIK. So there may be something about the newer cwm that executes the script a little differently. That's purely a guess though. Could've just been a bad flash for whatever reason.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Hard to say. I do know that enewman17 recommends flashing with twrp, and that's what most people have used AFAIK. So there may be something about the newer cwm that executes the script a little differently. That's purely a guess though. Could've just been a bad flash for whatever reason.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Should I try flashing twrp and then flashing the stock rom?
if i'm not mistaken CWM has pretty much been abondoned and no longer updated.
twrp and philz are preferred.
then again , "couldve just been a bad flash for whatever reason".
"all i can really do is stay out of my own way and let the will of heaven be done"
l3gionaires said:
Should I try flashing twrp and then flashing the stock rom?
Click to expand...
Click to collapse
You can try it if you like. Keep cm available just in case though. You might try some of the other stock builds too. Check the general and development section. I think there's about 3 NJ2 roms, each done a little differently.
Sent from my SGH-T999 using Tapatalk
mrrocketdog said:
if i'm not mistaken CWM has pretty much been abondoned and no longer updated.
twrp and philz are preferred.
then again , "couldve just been a bad flash for whatever reason".
"all i can really do is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
TWRP is a million times better! works great thanks for the suggestion!
DocHoliday77 said:
You can try it if you like. Keep cm available just in case though. You might try some of the other stock builds too. Check the general and development section. I think there's about 3 NJ2 roms, each done a little differently.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i updated my bootloader and modem to nj2 then flashed the stock rom for nj2 (this time using TWRP) and had the same outcome, it just hangs on the AT&T logo. I think this phone is doomed to be a CM12.1 phone.
That's strange. Did you try a different one if the NJ2 stock roms as well?
Oh and did you check the md5 to make sure the download wasn't corrupted?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
That's strange. Did you try a different one if the NJ2 stock roms as well?
Oh and did you check the md5 to make sure the download wasn't corrupted?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
all md5s match and i tried enewman's deodexed fnj2 roms as well and it still hangs at AT&T Logo. maybe it's an issue of returning from Lollipop to KK?
Check the cm rom threads. Maybe someone else there has run into a similar problem. I don't use it myself, so I'm not familiar enough with it to say.
I'll try to do a little digging when I get home. There's got to be some sort of explanation!
(Have you ever tried reformatting /system to anything other than ext4? )
Sent from my SGH-T999 using Tapatalk
---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------
Maybe try another TW custom rom. Just to see if it does the same thing.
Sent from my SGH-T999 using Tapatalk
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
dawgdoc said:
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
Click to expand...
Click to collapse
i'll try these when I get home and update asap
also @ DocHoliday I don't Know how to do that
dawgdoc said:
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
Click to expand...
Click to collapse
l3gionaires said:
i'll try these when I get home and update asap
also @ DocHoliday I don't Know how to do that
Click to expand...
Click to collapse
#1 worked for me! for some reason when i was on NJ1, the recovery didn't work, so i guess updating to NJ2 fixed it? anyways who cares! I'm back to fully bloated TW! Thank you guys for all your help!
l3gionaires said:
#1 worked for me! for some reason when i was on NJ1, the recovery didn't work, so i guess updating to NJ2 fixed it? anyways who cares! I'm back to fully bloated TW! Thank you guys for all your help!
Click to expand...
Click to collapse
Glad to hear it worked. :victory: Now to find a buyer.