Hi all,
I've recently rooted my phone as per mrRobinson's thread and used TWRP to flash Liquidsmooth 2.9 my phone. It worked beautifully for a night and then a day later, while I was receiving/typing a text, the phone went into ~2 cycles of reboot loop. Later during the day, while I was reading on the browser I would get random reboots after the phone seemingly freezes.
I tried reflashing the ROM after wiping everything (except for the internal storage) a few times.
Has anyone had this problem or experienced a similar situation? I tried searching a bit and reading the Liquidsmooth 2.9 thread but nothing about random reboots seems to occur... yet.
Thanks guys.
Experiencing reboots as well, after upgrading from 2.8 to 2.9. Primarily only happens when plugging in my phone to charge. This wasn't happening when I was on 2.8.
Perhaps this would be a more appropriate thread for these entries?
http://forum.xda-developers.com/showthread.php?t=2346973
Phone: Samsung Galaxy S III SGH-i747
Previous ROM: Liquid-JB-v2.8-OFFICIAL-d2att.zip
Current ROM: Liquid-JB-v2.9-OFFICIAL-d2att.zip
Sure said:
Experiencing reboots as well, after upgrading from 2.8 to 2.9. Primarily only happens when plugging in my phone to charge. This wasn't happening when I was on 2.8.
Perhaps this would be a more appropriate thread for these entries?
http://forum.xda-developers.com/showthread.php?t=2346973
Phone: Samsung Galaxy S III SGH-i747
Previous ROM: Liquid-JB-v2.8-OFFICIAL-d2att.zip
Current ROM: Liquid-JB-v2.9-OFFICIAL-d2att.zip
Click to expand...
Click to collapse
Unfortunately when I was posting this thread I was (and still am) under the 10 post limit, lol. I've decided to just stick to CM10 for now. I might try to reflash 2.9 again. If that doesn't work, I might try different settings for the CPU (eg. on demand? mine was set to interactive). Additionally, I think the liquid team is moving towards 4.3 so I'm not even sure if this is going to matter to them...
This didn't happen to me, but I upgraded from 2.3. Got a little behind on the releases lol. Also, which kernel are you using? With liquidsmooth the stock kernels don't like my phone so i have to flash another...
_alp1ne said:
This didn't happen to me, but I upgraded from 2.3. Got a little behind on the releases lol. Also, which kernel are you using? With liquidsmooth the stock kernels don't like my phone so i have to flash another...
Click to expand...
Click to collapse
Wait, are you saying the stock kernel that came with the liquidsmooth roms? Are you also using an S3? Lastly, which kernel are you using now (and did you change the CPU/performance settings)?
duketerm said:
Wait, are you saying the stock kernel that came with the liquidsmooth roms? Are you also using an S3? Lastly, which kernel are you using now (and did you change the CPU/performance settings)?
Click to expand...
Click to collapse
Well i meant the kernel that is automatically installed when you flash Liquidsmooth. I am using the ATT S3 at the moment. The kernel that came with liquidsmooth always caused random reboots and similar problems for me. Now i use the BMS kernel (here) and have no more problems. I didnt really mess with the CPU settings on the liquidsmooth kernel, just set max frequency to 1242mHz for some extra battery life. With the BMS kernel, I have it undervolted -105mV and again set max frequency to 1242mHz.
Sorry for the confusion.
equhmiduff
Hey guys
Same Problem here, but first of all am not a developer and i know nothing about it i installed font installer to change font after rooting and bricked my XT925 and after long looong search i flashed Liquidsmooth 2.8 and 2.9 and the constantly reboots always happening i heard it is because of RAM and running apps, so i installed RAM booster app and problem still exist suddenyl launcher freezes and device reboots
Tried ROMs : CM10.2 - PAC Man
Device : Droid Razr HD
Current ROM : Liquid 2.9
Launcher Used : TSF Shell - Next Launcher
Bootloader : Unlocked
Recovery : oudhs recovery
atteya.mohamed said:
Hey guys
Same Problem here, but first of all am not a developer and i know nothing about it i installed font installer to change font after rooting and bricked my XT925 and after long looong search i flashed Liquidsmooth 2.8 and 2.9 and the constantly reboots always happening i heard it is because of RAM and running apps, so i installed RAM booster app and problem still exist suddenyl launcher freezes and device reboots
Tried ROMs : CM10.2 - PAC Man
Device : Droid Razr HD
Current ROM : Liquid 2.9
Launcher Used : TSF Shell - Next Launcher
Bootloader : Unlocked
Recovery : oudhs recovery
Click to expand...
Click to collapse
Yes, I get the same problem: the phone freezes (eg. on browser, texting, etc.) and then reboots. I haven't tried reflashing it and changing CPU settings... Have you?
I don't know what to tell you guys. I went ahead and flashed every version of liquidsmooth from 2.5 to 2.9 everyday the past week and used them for about a day each, and i have not had any problems. No reboots, crashes. Not all s3's are created equal i guess...
sorry i couldn't be of help
_alp1ne said:
I don't know what to tell you guys. I went ahead and flashed every version of liquidsmooth from 2.5 to 2.9 everyday the past week and used them for about a day each, and i have not had any problems. No reboots, crashes. Not all s3's are created equal i guess...
sorry i couldn't be of help
Click to expand...
Click to collapse
Hmm, the only thing I can think of now is maybe the type of recovery we use? I used TWRP 2.6.0.0. What about you?
possible recovery issues--
duketerm said:
Hmm, the only thing I can think of now is maybe the type of recovery we use? I used TWRP 2.6.0.0. What about you?
Click to expand...
Click to collapse
I used clockworkmod, forgot which version. I will test different recoveries when I get home.
EDIT: I flashed it on cwm v6.0.3.1, which is not the latest version of cwm.
Sent from my SGH-I747 using xda app-developers app
Will test twrp 2.6 in a few minutes..... Will report back later if I can.
well..... Tried to flash liquid smooth today. Just finished unbricking my device a few minutes ago. Soft brick due to an error flashing. Reinjected IMEI and restored must everything.... Will reflash via CWM later.
_alp1ne said:
well..... Tried to flash liquid smooth today. Just finished unbricking my device a few minutes ago. Soft brick due to an error flashing. Reinjected IMEI and restored must everything.... Will reflash via CWM later.
Click to expand...
Click to collapse
Thanks for doing all of this. I have another question for you since you've told me you had to reinject IMEI... How did you back up your IMEI? I've been looking around but only the basic samsung thing worked for me since I'm already on CM10.
I tried to use this thread: http://forum.xda-developers.com/showthread.php?t=1804117 but I'm unsure how to run that gscript... Thanks for your help man.
duketerm said:
Thanks for doing all of this. I have another question for you since you've told me you had to reinject IMEI... How did you back up your IMEI? I've been looking around but only the basic samsung thing worked for me since I'm already on CM10.
I tried to use this thread: http://forum.xda-developers.com/showthread.php?t=1804117 but I'm unsure how to run that gscript... Thanks for your help man.
Click to expand...
Click to collapse
The thread you listed there confused me also... To use that USSD code you need to be on stock. I will try the gscript thing mentioned and tell you what happens. I also explained below what I did to backup.
Not sure what you mean by basic backup... but i will try explain everything anyway.
Method 1 -
This uses samsung's built-in NVRAM backup/restore function. I won't go into detail, but type in the following in a terminal-
Code:
su
reboot nvbackup
It will then boot into the bootloader, with some text telling you its copying the NVDATA to two partitions - fsg and backup .
to restore, type in
Code:
su
reboot nvrestore
DO NOT use the restore command without backing up first!! DOING SO WILL WIPE YOUR IMEI!!!
More Methods-
Method 2 -
.The devs of SynergyROM developed this - just download at the bottom of this post and flash in recovery.
This will generate some zips in sdcard/SynergyROM/backup. To restore, flash the one that begins with "keybackup".
-
There is a third way, called QPST. I would not use this unless you have balls of steel, and also it requires stock rom. Couldn't find anything about this, so i guess you could google it if interested.
_alp1ne said:
The thread you listed there confused me also... To use that USSD code you need to be on stock. I will try the gscript thing mentioned and tell you what happens. I also explained below what I did to backup.
Not sure what you mean by basic backup... but i will try explain everything anyway.
Method 1 -
This uses samsung's built-in NVRAM backup/restore function. I won't go into detail, but type in the following in a terminal-
Code:
su
reboot nvbackup
It will then boot into the bootloader, with some text telling you its copying the NVDATA to two partitions - fsg and backup .
to restore, type in
Code:
su
reboot nvrestore
DO NOT use the restore command without backing up first!! DOING SO WILL WIPE YOUR IMEI!!!
More Methods-
Method 2 -
.The devs of SynergyROM developed this - just download at the bottom of this post and flash in recovery.
This will generate some zips in sdcard/SynergyROM/backup. To restore, flash the one that begins with "keybackup".
-
There is a third way, called QPST. I would not use this unless you have balls of steel, and also it requires stock rom. Couldn't find anything about this, so i guess you could google it if interested.
Click to expand...
Click to collapse
Yeah, sorry. What I meant, was I used Samsung's backup--was that enough for you? Just worried about flashing another rom. Interestingly from what I read, the new versions of the IMEI format (3?) isn't supposed to cause problems--I guess that was wrong?
Additionally, the SynergyROM didn't work for me because apparently my bootloader is locked? I'm on AT&T and I thought AT&T had unlocked bootloaders?
duketerm said:
Yeah, sorry. What I meant, was I used Samsung's backup--was that enough for you? Just worried about flashing another rom. Interestingly from what I read, the new versions of the IMEI format (3?) isn't supposed to cause problems--I guess that was wrong?
Additionally, the SynergyROM didn't work for me because apparently my bootloader is locked? I'm on AT&T and I thought AT&T had unlocked bootloaders?
Click to expand...
Click to collapse
Samsung's backup was enough for me, but I did the other stuff just to be safe. AT&T's bootloaders do come unlocked, otherwise you wouldn't be on CM10 From the errors it gave me in recovery that im assuming you got also said something about unlocked EFS. The EFS is where the NVItems are located, and it might require an unlocked device, as in you can use any carrier's SIM. I will unlock my GS3 (or atleast try) right now.
I will report back on that later.
EDIT: I need to go to the store right now, so it might be a while.
_alp1ne said:
Samsung's backup was enough for me, but I did the other stuff just to be safe. AT&T's bootloaders do come unlocked, otherwise you wouldn't be on CM10 From the errors it gave me in recovery that im assuming you got also said something about unlocked EFS. The EFS is where the NVItems are located, and it might require an unlocked device, as in you can use any carrier's SIM. I will unlock my GS3 (or atleast try) right now.
I will report back on that later.
EDIT: I need to go to the store right now, so it might be a while.
Click to expand...
Click to collapse
Wait, so were you able to flash SynergyROM? And you did so without unlocking your device?
Thanks!
duketerm said:
Wait, so were you able to flash SynergyROM? And you did so without unlocking your device?
Thanks!
Click to expand...
Click to collapse
Oh dear.
I believe there is some miscommunication
The bootloader has always been unlocked. I'm not talking about the actual ROM (synergyROM), I'm talking about the IMEI backup thing they created.
Now, when I said unlock my phone, I DID NOT mean the bootloader, I meant carrier unlocking it, so I can use any sim from any carrier. I'll try to screenshot it later.
Sorry for the confusion duke.
_alp1ne said:
Oh dear.
I believe there is some miscommunication
The bootloader has always been unlocked. I'm not talking about the actual ROM (synergyROM), I'm talking about the IMEI backup thing they created.
Now, when I said unlock my phone, I DID NOT mean the bootloader, I meant carrier unlocking it, so I can use any sim from any carrier. I'll try to screenshot it later.
Sorry for the confusion duke.
Click to expand...
Click to collapse
Sorry, I think I'm being vague and not specific.
I'm wondering which IMEI back up steps you took. From what you've told me, it appears that you were able to run the Samsung backup, as well as the other ones (including SynergyROM backup?"). If you were able to run the SynergyROM backup, how did you do it? I was unable to run it because I got an error message saying that something was "locked" so I'm not sure how you got around to successfully flashing the SynergyROM.
Thanks for all the help.
Related
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Did you do a full wipe ???
ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).
Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.
i flashed synergy rom r14 after rooting the device initially and everything worked out fine, then kept getting the notification for the OTA for the 4.1.2 update...being that downloading OTA while rooted is a big no no (or always was before i came to the note) i decided to check synergy for updates to the rom and sure enough it was up to r47...so i downloaded and flashed and everything went smooth but after boot up it goes through the whole hand free activation and after saying the device is activated and then going through the PRL update and that checking out, it is supposed to do the soft reset and boot up and be good to go...well on second boot up it tries to activate the phone again (again saying Activation check and PRL update check) resulting in a boot loop that never stops....where did i go wrong...every phone ive had (touch pro 2, evo, evo 3d, nexus s) has always been a pretty straight forward root/flash process...so far this one seems to be a pain....any help?
Well clearly the problem wasn't worth the rooting process because you were able to flash Synergy w/o a problem. Hopefully you have a nandroid of stock rooted. I would pull the battery and try to restore your backup. Don't forget that for this phone Recovery access is via 3 buttons: power, home and volume (I forgot if it's up or down)
SantinoInc said:
Well clearly the problem wasn't worth the rooting process because you were able to flash Synergy w/o a problem. Hopefully you have a nandroid of stock rooted. I would pull the battery and try to restore your backup. Don't forget that for this phone Recovery access is via 3 buttons: power, home and volume (I forgot if it's up or down)
Click to expand...
Click to collapse
its up (down goes into odin) and sadly my stupidity and eagerness led me to not have a nandroid (yes feel free to leave the backlash, i deserve it), my question is...could it possibly be i a need to flash a different kernel? another idea i had was possibly calling sprint and seeing if the could walk me through the activation process (ive had them activate rooted phones before) i cant ever find the right button sequence (ie ##xxxxxx to get into the different menus) on the web
##72786# is the code you can use in a stock based rom with stock dialer that configures the data. It establishes a connection and then runs through that whole cycle you described in the OP. I'm kinda intoxicated so IDK if I answered your question or not
SantinoInc said:
##72786# is the code you can use in a stock based rom with stock dialer that configures the data. It establishes a connection and then runs through that whole cycle you described in the OP. I'm kinda intoxicated so IDK if I answered your question or not
Click to expand...
Click to collapse
well those r the type of combinations that i was looking for but sadly that one didnt help the situation
Gronde0715 said:
well those r the type of combinations that i was looking for but sadly that one didnt help the situation
Click to expand...
Click to collapse
So right now you are unable to get a data connection on any rom you try? If that is the case you will probably want to look in the DEVELOPMENT section for a totally stock rom that you can ODIN.
SantinoInc said:
So right now you are unable to get a data connection on any rom you try? If that is the case you will probably want to look in the DEVELOPMENT section for a totally stock rom that you can ODIN.
Click to expand...
Click to collapse
correct, alrighty ill try that
The last few weeks I've noticed something odd which as far as I can tell is harmless but would like to understand. When I restart my Note 2 it goes through the entire start up process to the point of being on the lockscreen (perhaps a little further as I can get to home screen). It then spontaneously reboots itself! After that reboot everything appears to be running fine. Any explanation as to why this might happen and how to correct. My device is rooted. Use philz kernal 4.87. I also tried going down to 4.65 but no change.
Thanks!
What other mods do u have? can you link me to the kernel
deeznutz1977 said:
What other mods do u have? can you link me to the kernel
Click to expand...
Click to collapse
Hi. The kernel is from this thread.
http://forum.xda-developers.com/showthread.php?t=2028103
It has many nice features. I'm struggling to recall when this all started. It was before I upgraded to 4.12 via kies. I actually have not done a lot of mods as I reserve my tinkering for my Note 1 and use the Note 2 for my daily drive. But on the Note 2 I first used chainfire scheme to root. Shortly after that I used the Xposed framework to have unlimited apps in multiview. Then a bit later flashed the Philz kernal (Used mobile odin to do that the first time).The other thing I use that depends on root is linux on android and titanium backup. I look at this as rather modest mods.
I'm considering starting again from scratch but if you have some suggestions I might give it a go. I'm still learning about android (here is another opportunity!) coming from a N900. It seems there is a possibility it is a bit sensitive as it is booting up such that if an app is attempting something before the boot up is completed it triggers it to reboot. (Sorry if that is vague sounding). Is there a system log I can check to possibly track this down? Let me know if you need any specific information and I'll try to provide it. Thanks!
mscion said:
Hi. The kernel is from this thread.
http://forum.xda-developers.com/showthread.php?t=2028103
It has many nice features. I'm struggling to recall when this all started. It was before I upgraded to 4.12 via kies. I actually have not done a lot of mods as I reserve my tinkering for my Note 1 and use the Note 2 for my daily drive. But on the Note 2 I first used chainfire scheme to root. Shortly after that I used the Xposed framework to have unlimited apps in multiview. Then a bit later flashed the Philz kernal (Used mobile odin to do that the first time).The other thing I use that depends on root is linux on android and titanium backup. I look at this as rather modest mods.
I'm considering starting again from scratch but if you have some suggestions I might give it a go. I'm still learning about android (here is another opportunity!) coming from a N900. It seems there is a possibility it is a bit sensitive as it is booting up such that if an app is attempting something before the boot up is completed it triggers it to reboot. (Sorry if that is vague sounding). Is there a system log I can check to possibly track this down? Let me know if you need any specific information and I'll try to provide it. Thanks!
Click to expand...
Click to collapse
That's recovery not a kernel.. 1, Backup all your apps&data with titanium . 2,download this: http://forum.xda-developers.com/showthread.php?t=1975560.. 3, Factory reset& wipe caches 4, flash the downloaded file in odin.. Dont flash anything else reboot, setup your phone. now one by one try out your mods you want rebooting to check if all is well.... Let me know how it goes
deeznutz1977 said:
That's recovery not a kernel.. 1, Backup all your apps&data with titanium . 2,download this: http://forum.xda-developers.com/showthread.php?t=1975560.. 3, Factory reset& wipe caches 4, flash the downloaded file in odin.. Dont flash anything else reboot, setup your phone. now one by one try out your mods you want rebooting to check if all is well.... Let me know how it goes
Click to expand...
Click to collapse
Thanks again. You're right. That work by Philz is recovery not kernal. I've gotten into a bad habit of calling it a kernel. I think the title in the thread used say kernal but I see it has changed. I've since removed 4 or 5 apps and since then I haven't seen the extra reboot take place. So far I've rebooted 7 times today. Doesn't mean the problem is solved but it is certainly happening less frequently! If I spot it happening again I will give mrRobinson's rom a go.
mscion said:
Thanks again. You're right. That work by Philz is recovery not kernal. I've gotten into a bad habit of calling it a kernel. I think the title in the thread used say kernal but I see it has changed. I've since removed 4 or 5 apps and since then I haven't seen the extra reboot take place. So far I've rebooted 7 times today. Doesn't mean the problem is solved but it is certainly happening less frequently! If I spot it happening again I will give mrRobinson's rom a go.
Click to expand...
Click to collapse
Hey, if you need help dont hesitate to pm me
I rooted my SGH-I317 awhile ago using galaxynote2root method. I have CWM recovery v6.0.1.4. I have flashed multiple roms including JellyThunder, Diaphanes and now I'm running Clean Rom.
I dont believe it's rom related because its happened on multiple roms but my problem started on Diaphanes and has continued on Clean Rom. When I am connected to wifi I am almost always not in service and I cannot send or receive messages. I know that I am in an area where I usually get excellent service so I'm not sure what is causing this problem.
I am still learning but I've come a long way thanks to some of you guys and any help would be awesome!
Have you done a full device wipe and restore to stock at any point to test ?
The symptoms you describe sound like something is missing. ..
It's too early to assume a hardware issue. ..
And a stock rom restore that includes the files known to function properly would be a good idea.
I suggest a full wipe, and an Odin restore of a rooted stock build. ...then report the findings. ..g
gregsarg said:
Have you done a full device wipe and restore to stock at any point to test ?
The symptoms you describe sound like something is missing. ..
It's too early to assume a hardware issue. ..
And a stock rom restore that includes the files known to function properly would be a good idea.
I suggest a full wipe, and an Odin restore of a rooted stock build. ...then report the findings. ..g
Click to expand...
Click to collapse
Could you point me in the right direction for such tasks?
All I found was Imnuts guide for such a thing but that is for SGH-I605 I believe.
So maybe my brain was malfunctioning...
Are you saying that I just need to flash a stock rom as I found here...http://forum.xda-developers.com/showthread.php?t=1986556
I thought you meant back to an unrooted version but then I reread it.
I always do a full wipe when I flash roms, so I'd just do that like normal?
meat614 said:
I rooted my SGH-I317 awhile ago using galaxynote2root method. I have CWM recovery v6.0.1.4. I have flashed multiple roms including JellyThunder, Diaphanes and now I'm running Clean Rom.
I dont believe it's rom related because its happened on multiple roms but my problem started on Diaphanes and has continued on Clean Rom. When I am connected to wifi I am almost always not in service and I cannot send or receive messages. I know that I am in an area where I usually get excellent service so I'm not sure what is causing this problem.
I am still learning but I've come a long way thanks to some of you guys and any help would be awesome!
Click to expand...
Click to collapse
What Modem you running? You might not have to flash back to stock.
Try flashing a different modem like the MC3, thats the latest one
I've never messed with my modem so I'd assume its as its always been. Can you link me to it? Is it the same as flashing a rom? Does it matter what rom im on?
Edit: I believe I found the download for mc3. So I just dl, reboot to recovery and flash it?
meat614 said:
I've never messed with my modem so I'd assume its as its always been. Can you link me to it? Is it the same as flashing a rom? Does it matter what rom im on?
Edit: I believe I found the download for mc3. So I just dl, reboot to recovery and flash it?
Click to expand...
Click to collapse
Yes, just reboot to recovery and flash it. There have been some significant improvements for some people after they upgraded to the newest modem. My data speeds over LTE almost doubled after the update.
Hope you get it working.
Very sorry for the late response ...
The thread link you posted is very old ....as we have much newer versions of rooted stock roms.
The latest is UCAMC3....and is available in the development section in several different configurations.
In an attempt to simplify the return to stock, look at the web site in the link you posted. "Scottsroms.com" is found in the developers signature line.
The site contains a rooted, deodexed stock rom that is flashable from recovery, and will produce the desired results while side stepping the need to use Odin.
Simply download the rom to your SD card, then boot to your recovery.
Wipe data/factory reset the device, and flash the new build.
Your original radio image will remain untouched, and once booted, the device will be clean and ready to be set the way you wish.
Ultimately, a simple fresh start is the logical next step....g
wont connect to my data network
Hi I just flashed the hawkish supreme rom to my galaxy note2 att and for some reason it wont connect to my mobile network the imei still there is not wipe but the imei sv says 06 I don't now if it right but I did twice thw flash wipe verything and still no success can anybody help me thanks
itsmekilla76 said:
Hi I just flashed the hawkish supreme rom to my galaxy note2 att and for some reason it wont connect to my mobile network the imei still there is not wipe but the imei sv says 06 I don't now if it right but I did twice thw flash wipe verything and still no success can anybody help me thanks
Click to expand...
Click to collapse
You are likely missing the correct APN settings. ..
Not all roms contain the pre-loaded configuration. ..
Check them in your network settings and enter then save the correct entries. ..
The APN lists can be found in the development section. ...g
thanks
gregsarg said:
You are likely missing the correct APN settings. ..
Not all roms contain the pre-loaded configuration. ..
Check them in your network settings and enter then save the correct entries. ..
The APN lists can be found in the development section. ...g
Click to expand...
Click to collapse
thank you you are the best:good::good:
Always welcome. ...g
New Modem...
Alright guys I tried to take the easy way out and simply flashed the CM3 modem. It has failed me. I've been on it for a few days now and run in to the same problems and maybe even worse.
I just flashed the CA4 modem to try that out (mainly because I have to go to work and dont have time to try a permanent fix right now), so I'll see how it goes. Other than that I believe I will be hitting up scottsrom.com and doing what you mentioned to side step a few of the steps for returning to stock.
I do have 1 question.....I'm on Clean Rom 4.8 and I am aware that there is an updated 4.9. Does it come with a modem? Even if not is it possible that updating would help my problem?
I appreciate the help.
4.9 does not contain a modem...
None of the roms do...with the exception of stock Odin builds...
Seriously. ..I would consider an Odin restore to stock...
You'll get all of the needed files. ..and the issues may resolve. ...g
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
dokgu said:
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
Click to expand...
Click to collapse
I agree with Elesbb. If the goal is jus tto get back to stock, just do an odin flash of the stock ROM. Be advised if you flash the latest Kit Kay update you will nto be able to go back to Jelly Bean. From your post it seems like you are partial to Jelly Bean. So if that's what you want, but sure you use the stock 4.3 ROM. You can find it around here on XDA somewhere with a quick search to make sure you have the right one.
As Elesbb said, you won't loose the 'sim unlock'. But you will lose root. However you can root the stock ROM just fine.
You might also consider one of the myriad of TouchWiz based custom ROMs. They are look just like TouchWiz that your wife wants, but have a lot of optimizations and options in them. Those should flash just like any ROM. If you still get the reboot issue then do the Odin back to stock, reroot, then flash the custom TW roms.
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Thread cleaned.
Rather than bashing a ROM or user let's keep on topic and help the OP resolved the problems he's having. Arguing over the virtues of a ROM doesn't help anyone.
Thank you,
Rwilco12
Before posting this thread I sent the aforementioned guide's poster (arocker). He sent me a reply saying not to use gapps as the stock ROM for Metro PCS already comes with Google apps. I'll try his suggestion first and see if the phone still reboots a lot.
If the problem persists, I will try the solutions mentioned here. Thanks a lot!
elesbb said:
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
dokgu said:
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
Click to expand...
Click to collapse
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Hello PanchoPlanet,
Thanks for the link. I went ahead and tried to unroot without Windows (Mobile Odin) as per the instructions on the link. I downloaded everything and went ahead to install the Mobile Odin APK. When I ran it to install the Flash Kernel, the app told me that the device is not supported.
To my understanding the guide is for M919 devices but should work for my wife's device as well (M919N - Metro PCS). I would like to try the guide for using Windows but I'm not really expecting for it to work or I might mess it up more. I'll try to search some more and provide the links where this forum will lead me to. But if you have any ideas, please let me know asap. Thanks!
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Ok, here's what I found:
forum.xda-developers.com/showthread.php?t=2446497
It seems like the perfect thread for what I am trying to achieve. Will let you guys know if it is successful. But it will have to wait for tomorrow. Gonna catch some sleep.
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And 100% of the time, they eventually just get old.
dokgu said:
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
Click to expand...
Click to collapse
That's a wierd situation, by swapping batteries you basically performed a battery pull, which acts as a reset, that in it self may have cleared your issue.
Now if battery is bad that could be an unusual problem. Maybe just replacing the battery will be the end of your mystery.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
The batteries are all the same. Don't worry about that.
Even if its a new battery if could have just been bad. A manufacturing defect perhaps.
Sent from your phone. You should be more careful where you leave that thing.
dokgu said:
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
Click to expand...
Click to collapse
This battery thing is wacky, anyway swapping batteries should not be a problem, it's just an energy storage container. Pulling the battery isn't like powering down the phone or resetting/rebooting ,sometimes devs request a battery pull to get the proper wipe effect that reboots can't provide.
You inadvertently solved your problem by accident. That's a good thing.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
You inadvertently solved your problem by accident. That's a good thing.
Click to expand...
Click to collapse
I have quite literally solved the vast majority of my problems this way.
Its a preferred method.
Sent from your phone. You should be more careful where you leave that thing.
Sometimes it's that "total disconnect "of power that kind of gets all the ducks lined up in a row and everything flows in the dynaflow.
Good.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
its very important topics and it might seen for every galaxy s4 users.just wonderful topics.
This exact same thing happened on my mother's 6-month old S3. If you're still wondering, you could try putting the old battery and running a CPU stress test app. It should increase the current draw and trigger a shutdown.
EDIT: whoops, sorry to kind of zombie. Didn't check the date.
Sent from my Galaxy S4