Hi there, I am not new to installing Roms in any way but I accidentally installed a d2lte Liquid smooth ROM instead of what my phone is, a d2att. So when installing the above ROM I did everything what I was supposed to do (clean install, format system). However, whenever I go on any ROM (Such as Quantum or Omni) I get an error as soon as it boots up, and my signal keeps turning on and off. I wiped data, cache and dalvik twice and go to a new ROM and the problem persists. For some odd reason, Carbon ROM works but I need a different one due to battery drain. I've never experienced this problem ever and I was hoping someone could please help me out?
Have you tried re-flashing the modem?
audit13 said:
Have you tried re-flashing the modem?
Click to expand...
Click to collapse
Yes i tried that earlier but still no luck. It's weird though how there was no problem on carbon rom and yet there was a problem when i went back to the Quantum Rom. Something happened on the LiquidSmooth Rom but i don't know what. I will again try reflashing the modem though thank you.
EDIT: Re-flashing modem did not help
Is it possible to use Odin to get back to a completely stock rom? If you have a 4.3 bootloader, you can't use Odin to flash a stock ROM.
A way to get back to a stock ROM for those on the MJB bootloader has been provided by enewman17. See AT&T I747 UCUEMJB Stock Restore in the development forum.
Related
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?
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers
danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???
Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).
Hi all, long time lurker and it's finally come to the point where I don't know what to do about my problem.
I've tried running multiple ROMs, CM10, CM11, AOSP, Carbon KK and for some reason, for each of these ROMs, the data doesn't seem to work. I have full reception and everything works well except I can't seem to get any sort of data transfer.
The only time the data works is when I restock the phone back to ATT I747 UCUEMJB stock ontop of installing the Modem CWM I747UCUEMJB.
I'm currently running AOSB Kitkat 1.2.9
Kernel version 3.4.79-cyanogenmod-g29c22cf
Modem CWM I747UCUEMJB
Any thoughts on how I can fix this data problem?
I am also facing this problme. I have only one ROM with working data is unified version for S3 of Illusion Rom. On SCH-R530U
Sent from my SCH-R530U using Tapatalk
AznBorder11 said:
Hi all, long time lurker and it's finally come to the point where I don't know what to do about my problem.
I've tried running multiple ROMs, CM10, CM11, AOSP, Carbon KK and for some reason, for each of these ROMs, the data doesn't seem to work. I have full reception and everything works well except I can't seem to get any sort of data transfer.
The only time the data works is when I restock the phone back to ATT I747 UCUEMJB stock ontop of installing the Modem CWM I747UCUEMJB.
I'm currently running AOSB Kitkat 1.2.9
Kernel version 3.4.79-cyanogenmod-g29c22cf
Modem CWM I747UCUEMJB
Any thoughts on how I can fix this data problem?
Click to expand...
Click to collapse
So I actually got it working and it was a weird fix... I've been using ATT_I747_UCUEMJP_StockRestore_2282014.zip to bring it back to stock and then using the rooting system from that stock rom.
My friend suggested to try using another root, so I brough it back to CF-Autoroot and it works. Not sure why... but maybe give it a try if your using that stock rom?
OK guys let's see if you can help me out here. The problem I am having is any aosp based ROM I flash I cannot get data to load. The cm based rom , deviant rom or aicp ROM. Here's what I've tried so far, I've tried coming from zone ROM doing the typical wipes in recovery with no luck. I've tried loading from my stock back up with no luck. Then I tried flashing the M modem and still no go. Last thing I tried was backing up EFS on zone since data works on that then flashing on aosp with no data. Has anyone else came a crossed this nagging issue ? [emoji20]
Rinkle McBally said:
OK guys let's see if you can help me out here. The problem I am having is any aosp based ROM I flash I cannot get data to load. The cm based rom , deviant rom or aicp ROM. Here's what I've tried so far, I've tried coming from zone ROM doing the typical wipes in recovery with no luck. I've tried loading from my stock back up with no luck. Then I tried flashing the M modem and still no go. Last thing I tried was backing up EFS on zone since data works on that then flashing on aosp with no data. Has anyone else came a crossed this nagging issue ? [emoji20]
Click to expand...
Click to collapse
Honestly your best bet is ask in those threads as many of us are not running aosp.
BAD ASS G3
Rinkle McBally said:
OK guys let's see if you can help me out here. The problem I am having is any aosp based ROM I flash I cannot get data to load. The cm based rom , deviant rom or aicp ROM. Here's what I've tried so far, I've tried coming from zone ROM doing the typical wipes in recovery with no luck. I've tried loading from my stock back up with no luck. Then I tried flashing the M modem and still no go. Last thing I tried was backing up EFS on zone since data works on that then flashing on aosp with no data. Has anyone else came a crossed this nagging issue ? [emoji20]
Click to expand...
Click to collapse
I'm sure you found the answer by now but in case you didn't you have to change your APN to ipvp6 to get data
I don't know where it was but I saw a post saying that you have to change it to ipv6 or something. It was on the development thread.
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