Having trouble with all touchwiz roms, I can flssh a Touchwiz rom completely fine and boot jo problem, runs amazing but as soon as I reboot the device it hangs at the s4 boot logo screen and the ojly wwybto get out of the boot loop is to complete wipe and flash over again, I dont have this problem on any aosp roms. If anyone can help id greatly appreciate it , currently running the late stack wicked s4 rom with ktoonsez kernel, scared to death to reboot lol
Sent from my S4 (AKA The baddest of the bad)
re: clean start
CodenameRondo said:
Having trouble with all touchwiz roms, I can flssh a Touchwiz rom completely fine and boot jo problem, runs amazing but as soon as I reboot the device it hangs at the s4 boot logo screen and the ojly wwybto get out of the boot loop is to complete wipe and flash over again, I dont have this problem on any aosp roms. If anyone can help id greatly appreciate it , currently running the late stack wicked s4 rom with ktoonsez kernel, scared to death to reboot lol
Sent from my S4 (AKA The baddest of the bad)
Click to expand...
Click to collapse
To me it looks like it's time for your phone to get a fresh clean start.
Why not Odin flash back to stock firmware and go from there.
Afterwards you can root the phone and flash one of the excellent custom Touchwiz roms.
It's best if before you Odin flash the stock rom to be sure to do a factory reset,
wipe cache, wipe dalvik cache in the phone.
Here is the link to the Samsung Touchwiz Jellybean 4.2.2 MDL M919 stock rom: http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip
Good luck!
Actually thought about doing this, I just wish I knew what the problem was
Sent from my S4 (AKA The baddest of the bad)
Related
i just created myself a problem...i went in TWRP and into wipe and did a formated.... i when i flash the ROMS everything is fine... booted up everything... the problem is when i turn my phone off and turn it back on the phone is stuck at the samsung galaxy s4 logos... can someone please help me solve this problem...
Tmobile
Rom - Wicked v4
re: stuck
cloudi602 said:
i just created myself a problem...i went in TWRP and into wipe and did a formated.... i when i flash the ROMS everything is fine... booted up everything... the problem is when i turn my phone off and turn it back on the phone is stuck at the samsung galaxy s4 logos... can someone please help me solve this problem...
Tmobile
Rom - Wicked v4
Click to expand...
Click to collapse
Have you tried to go into twrp recovery and do a "factory reset" then reboot the phone
a couple times and see if the problem persist?
If it does then you will need to Odin flash the stock M919 Tmobile Jellybean Touchwiz 4.2.2 firmware.
(did you flash a AOSP/AOKP/CM10 rom prior to having this problem?)
good luck!
Misterjunky said:
Have you tried to go into twrp recovery and do a "factory reset" then reboot the phone
a couple times and see if the problem persist?
If it does then you will need to Odin flash the stock M919 Tmobile Jellybean Touchwiz 4.2.2 firmware.
(did you flash a AOSP/AOKP/CM10 rom prior to having this problem?)
good luck!
Click to expand...
Click to collapse
I have figured out what the problem was... I don't know if it true or not but it worked for me... i reflash my phone using formatted option and got in goomanager and i reinstalled open script recovery and it work now.... thank god... THANK YOU FOR THE INFO APPRECIATED VERY MUCH FOR YOUR HELP.....
I have the same issue on my wicked rom, what exactly did you do to fix it, I'm at a loss
Sent from my S4 (AKA The baddest of the bad)
I'm also having the same problem. I flashed a euroskank ROM, it runs fine. But I want to return to stock ROM. When I flash it, I see an "error restoring /data" ... when I reboot, all I see is the Samsung screen and it stays there. Help!! lol :crying: I don't have another backup of my stock ROM! I'm afraid I'll need to find it somewhere and flash it to the external SD card with ODIN.
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Wipe
Data
Cache
Delvik Cache
and Factory Reset.
Make sure you're flashing the correct GApps for android 4.2.x
Flashing a kernel has nothing to do with a status 7 error.
A status 7 error points to a outdated recovery or bootloader.
You should get ANY errors.
If you hate flashing why do it??
I honestly don't get that...
If you're here to make your phone to look "cool" you're in the wrong place.
Galaxy S3 / AoCP / V4A / Turbocharged
duoblade said:
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Click to expand...
Click to collapse
I would get TWRP recovery.. wipe dalvik / factory reset. and re-flash your rom.. I'm on Rogers as well and the status 7 error means that your recovery / bootloader is outdated.
So start by getting the most recent TWRP. I got it from goo.
btw: if you don't like custom rom, i suggest going to the sammobile site and getting your factory firmware. Use Odin to reflash back to stock. That should solve your hiatus towards custom roms...
correction
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
duoblade said:
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
Click to expand...
Click to collapse
sure but its fine custom Roms can be a Pain in the A$$ thats why am running stock rooted stable, great battery life, fast like custom roms, everything is perfect give a try with stock rooted no issues or problems like custom roms
Synergy Rom 4.1.2 w/ Ziggy Kernel using ATT Galaxy S3
HAPPY ROOTIN :cyclops:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
Has anyone flashed the Omega I9505 Rom on the M919. I did flash it a few weeks ago and it worked great. Used it for two weeks, then flashed a Google Edition Rom and soft bricked my phone.
I am not sure if the soft brick was due to, but I am hesitant to re-flash Omega rom since I have read that I should not be flashing other roms not designed for M919.
Just have the itch to go back, Omega rom ran really smooth and I feel that the phone ran the best on it.
I am just hesitant because I don't want to brick my phone, Soft or not; it is still very scary.
re: flashing roms
dss4me3 said:
Has anyone flashed the Omega I9505 Rom on the M919. I did flash it a few weeks ago and it worked great. Used it for two weeks, then flashed a Google Edition Rom and soft bricked my phone.
I am not sure if the soft brick was due to, but I am hesitant to re-flash Omega rom since I have read that I should not be flashing other roms not designed for M919.
Just have the itch to go back, Omega rom ran really smooth and I feel that the phone ran the best on it.
I am just hesitant because I don't want to brick my phone, Soft or not; it is still very scary.
Click to expand...
Click to collapse
Going back to Omega rom will NOT brick your phone.
Just be 100% sure to do a full wipe in cwm/twrp recovery before flashing any roms.
Complete full wipe includes wipe system, data, cache, dalvik cache and factory reset.
If you don't wipe all of the above you will have at least a 50% chance of bootlooping and or getting stuck
on boot screen and you will need to start all over again.
Omega rom is good but you will loose wifi calling unless you flash a rom specifically for the samsung M919 phone.
I would suggest the Wicked v7 custom rom it has all the bells and whistles including wifi calling and call recording.
Good luck!
Recently tried several times to flash cm or other aosp roms. Always get stuck on boot screen. Only roms that boot are tw based. So are aosp roms not possible on my locked bootloader? Is my bootloader locked lol?
Did you do a full wipe before you flashed?
Full wipe / factory reset.
Only way to go from TW to cm.
Pp.
Yes. Using twrp. Used the standard wipe method. Also tried wiping caches and the system. Ive even formatted my system. Still always stuck on boot screen. It is the CM boot screen however.
PanchoPlanet said:
Full wipe / factory reset.
Only way to go from TW to cm.
Pp.
Click to expand...
Click to collapse
So it is possible to go to a CM rom even with the MK2 bootloader. Can anyone confirm this?
Take a look at this,
Galaxy S4 How To Install CyanogenMod 11 CM 11 Kit…: http://youtu.be/gUhlLgMA-cA
Pp.
Looks like only TW roms for me.......Thanks everybody.
Cm isn't as bad on a device that doesn't need to be super reliable, like my phone, I need it to be on point at all times having a disabled child in school and never knowing when the school may call for whatever reason. I do run it on my Gal Tab 2 and it runs great, no issues and great battery life.
Pp.
Alex1212 said:
So it is possible to go to a CM rom even with the MK2 bootloader. Can anyone confirm this?
Click to expand...
Click to collapse
I have a T-Mobile S4 with MK2 and I've been running CM since I bought it.
Sent from my SGH-M919 using XDA Free mobile app
Seriously? Weird. Are u sure its not your modem thats mk2?
Alex1212 said:
Seriously? Weird. Are u sure its not your modem thats mk2?
Click to expand...
Click to collapse
Bootloader or modem doesn't make a difference, even with NH7 bootloader you should be able to flash any rom
Now I'm confused...So then what's the big deal about locked/unlocked bootloaders? Any idea why aosp roms won't boot on my phone? I'm fairly positive I've done every wipe and my twrp is the most recent one....thanks in advance
Alex1212 said:
Now I'm confused...So then what's the big deal about locked/unlocked bootloaders? Any idea why aosp roms won't boot on my phone? I'm fairly positive I've done every wipe and my twrp is the most recent one....thanks in advance
Click to expand...
Click to collapse
We don't have locked bootloaders.. Don't know, try different kernel after you flash or another recovery like cwm or philz
I thought they locked them with the mk2 bootloader when they added knox. Ill try again ive tried flashing kt kernel after flashing rom and gapps(made sure it wasnt the tw version). Ill try with cwm recovery. Thanks for trying to help. Ill make a backup of my current rom and try again.
Alex1212 said:
I thought they locked them with the mk2 bootloader when they added knox. Ill try again ive tried flashing kt kernel after flashing rom and gapps(made sure it wasnt the tw version). Ill try with cwm recovery. Thanks for trying to help. Ill make a backup of my current rom and try again.
Click to expand...
Click to collapse
If they were locked you wouldn't have been able to flash a custom recovery
Locked bootloaders are seen on the Verizon and att varients of the S4 , that's where safestrap comes into play. Locked means you can't flash a recovery/custom Roms etc. T-Mobile comes with unlocked BL allowing us to customize our phones. NH7 doesn't allow to you to downgrade BL's, not the same as locked BL. Its a Knox thing, and that only messes with warranty.
Pp. ?
Tried flashing liquidsmooth last night and again stuck at boot screen. Wiped phone flashed rom then gapps. Also tried wipe rom, gapps, kt kernel. Waited 30 minutes then just went back to backup. Thanks for clearing this up guys. Any suggestions?
Alex1212 said:
Tried flashing liquidsmooth last night and again stuck at boot screen. Wiped phone flashed rom then gapps. Also tried wipe rom, gapps, kt kernel. Waited 30 minutes then just went back to backup. Thanks for clearing this up guys. Any suggestions?
Click to expand...
Click to collapse
Can you state exactly what you wipe?
In twrp I use the standard wipe. I forget what it's called but it's the top right button. Brings you to a screen that says that this is all u need to wipe for flashing a new rom. I think it's basically a factory reset. In addition to that I go in advanced wipe and do both caches. I've also even tried wiping system and a few times I've even formatted my data which I think deletes absolutely everything. I tried using Odin to go back to complete stock and re root then Odin twrp. Still sits at boot screen unless I flash a tw style rom...... I'm starting to think it might not even be worth it anymore, not even sure what I'm missing out on honestly. It's just really bugging me that aosp roms won't boot.
That is rather odd, they boot.. Only other thing to try is to flash a different kernel or switch recovery to cwm or philz