Related
Ok. So I see there is a system update. I wanted to make sure if there's anyway I can check to see that it's ok that I install this update. Will it interfere with anything? Mainly pertaining to my root and unbrickness of my phone.
Will I lose root? Will I become bricked? (Though I doubt the later) I just wanted to know are we in the clear on installing this.
Sorry, but this is the first time this has happened to me, being rooted with some type of OTA.
you know... i flashed the updated tar file using mobile odin and 1) kept the root and super user 2) gained the stock boot screen again but lost clockwork 3) didn't lose any of my apps or data.
so it's a mixed bag and from my experience i wouldn't recommend it because it replaces the kernel and you'd lose clockwork. i think there may be a version floating around that you can flash though.
btate0121 said:
you know... i flashed the updated tar file using mobile odin and 1) kept the root and super user 2) gained the stock boot screen again but lost clockwork 3) didn't lose any of my apps or data.
so it's a mixed bag and from my experience i wouldn't recommend it because it replaces the kernel and you'd lose clockwork. i think there may be a version floating around that you can flash though.
Click to expand...
Click to collapse
So... shouldn't I update through the OTA, loose my kernel, use ODIN to flash back my CWM and kernel? That sounds like a viable solution.
Sounds about right to me but I would probably wait for someone more learn-ed to chime in. Your mileage may vary using the method I used.. which admittedly is probably very noobish. I didn't have any problem flashing a CWM kernel through odin though. Here's the funny thing.. i kept reading that the stock kernel would "unroot" your phone.. but for a few days I actually kept the stock kernel and was still fully rooted (super user kept asking permission for a few things like widget locker and titanium... and they worked perfectly *shrug*).
It may be that I just don't understand it fully yet but it worked out fine for me.. but again.. your mileage may vary.
btate0121 said:
Sounds about right to me but I would probably wait for someone more learn-ed to chime in. Your mileage may vary using the method I used.. which admittedly is probably very noobish. I didn't have any problem flashing a CWM kernel through odin though. Here's the funny thing.. i kept reading that the stock kernel would "unroot" your phone.. but for a few days I actually kept the stock kernel and was still fully rooted (super user kept asking permission for a few things like widget locker and titanium... and they worked perfectly *shrug*).
It may be that I just don't understand it fully yet but it worked out fine for me.. but again.. your mileage may vary.
Click to expand...
Click to collapse
Alright, that sounds like a safer route. Ima go check around the ROMS. Maybe they've added the update as part of their ROM.
Expecting this update to fix many of my problems.
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.
For the last few days I have been googling/reading/ following threads and reading old posts. I'm having trouble deciding which version of TWRP is the most stable for N900T and allows full back up/restore with the least likely hood of bootloop. Maybe I missed something but I've tried to do my homework before asking. TIA...
drag&fly said:
For the last few days I have been googling/reading/ following threads and reading old posts. I'm having trouble deciding which version of TWRP is the most stable for N900T and allows full back up/restore with the least likely hood of bootloop. Maybe I missed something but I've tried to do my homework before asking. TIA...
Click to expand...
Click to collapse
The latest version works just fine. Use that.
drag&fly said:
For the last few days I have been googling/reading/ following threads and reading old posts. I'm having trouble deciding which version of TWRP is the most stable for N900T and allows full back up/restore with the least likely hood of bootloop. Maybe I missed something but I've tried to do my homework before asking. TIA...
Click to expand...
Click to collapse
Use Philz cwm. No one has had an issue. Twrp is not worth the headaches you will get.
TWEAKED 2.0 NOTE 3
BACARDILIMON said:
Use Philz cwm. No one has had an issue. Twrp is not worth the headaches you will get.
TWEAKED 2.0 NOTE 3
Click to expand...
Click to collapse
I've had less issues with TWRP than CWM..
cun7 said:
I've had less issues with TWRP than CWM..
Click to expand...
Click to collapse
Correct less but with Philz I have not seen anyone have any issue and it is fully customized
TWEAKED 2.0 NOTE 3
BACARDILIMON said:
Correct less but with Philz I have not seen anyone have any issue and it is fully customized
TWEAKED 2.0 NOTE 3
Click to expand...
Click to collapse
I've had plenty of issues with that recovery, Reverting itself to previous versions, not saving my settings, double touches when selecting things. The UI is boring and archaic IMO. TWRP is fully customizable and since the GUI is 100% .xml I can modify it entirely simply by dropping a file on my sd card....
I use what I use, to each his own. But I wouldn't make such bogus claims about somebody else's work simply because you have a bias for whatever reason I don't know.
cun7 said:
I've had plenty of issues with that recovery, Reverting itself to previous versions, not saving my settings, double touches when selecting things. The UI is boring and archaic IMO. TWRP is fully customizable and since the GUI is 100% .xml I can modify it entirely simply by dropping a file on my sd card....
I use what I use, to each his own. But I wouldn't make such bogus claims about somebody else's work simply because you have a bias for whatever reason I don't know.
Click to expand...
Click to collapse
Have you read the threads.
For the op. Check around to all 3 recovery forums and you decide for your self
TWEAKED 2.0 NOTE 3
BACARDILIMON said:
Have you read the threads. Majority are having issues with twrp cause it is junk. The devs don't help much even when log cats are sent. But you do you and I do me
For the op. Check around to all 3 recovery forums and you decide for your self
TWEAKED 2.0 NOTE 3
Click to expand...
Click to collapse
We all have our favorite recovery, then we have the one that works... Sometimes they are the same and sometimes they are not... But calling someones hard work Junk, when Its clearly not, is not following the spirit of XDA... Your making this way too personal...
cerj said:
We all have our favorite recovery, then we have the one that works... Sometimes they are the same and sometimes they are not... But calling someones hard work Junk, when Its clearly not, is not following the spirit of XDA... Your making this way too personal...
Click to expand...
Click to collapse
You are right. It was personal because I know we all take risk when messing with our devices. I lost all my info. I was/am mad. Like I said to the op do your homework.
TWEAKED 2.0 NOTE 3
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
BACARDILIMON said:
For the op. Check around to all 3 recovery forums and you decide for your self
TWEAKED 2.0 NOTE 3
Click to expand...
Click to collapse
TWEAKED 2.0 NOTE 3
BACARDILIMON said:
Have you read the threads.
For the op. Check around to all 3 recovery forums and you decide for your self
TWEAKED 2.0 NOTE 3
Click to expand...
Click to collapse
Apparently you haven't read the twrp thread too. The developer for note 3 is very helpful, responding and fixing bugs right away. 100% agree with @cun7. Philz CWM is so overwhelmed with all kinds of UI and touch driver settings that you can easily waste a day just to make it feel right. I personally find it too touch sensitive.
And something you probably don't know which I consider very important... it uses secure adbd binary which means no adb root r/w access for /system. Recovery is for doing " low level" stuff on the system you usually can't do when android is running and most of the time you need adb for that. I understand the secure-adbd concept in android but in recovery...? Really...?
nijel8 said:
Apparently you haven't read the twrp thread too. The developer for note 3 is very helpful, responding and fixing bugs right away. 100% agree with @cun7. Philz CWM is so overwhelmed with all kinds of UI and touch driver settings that you can easily waste a day just to make it feel right. I personally find it too touch sensitive.
And something you probably don't know which I consider very important... it uses secure adbd binary which means no adb root r/w access for /system. Recovery is for doing " low level" stuff on the system you usually can't do when android is running and most of the time you need adb for that. I understand the secure-adbd concept in android but in recovery...? Really...?
Click to expand...
Click to collapse
I agree but I going with functionality. Meaning it will flash a rom without soft bricking device. I have used twrp for years. Note2 galaxy S3 and others but I became a flashing king trying to recover from a simple rom flash. When asked in thread I would get pm telling me to change recovery. I did and no issue since. I have flashed over 20 roms and it all good. We can all agree that my statement was out of line hence I deleted it. But in same token it holds water for my experience.
TWEAKED 2.0 NOTE 3
I'm on TWRP 2.6.3.8 and have never had an issue with it. Restores everything fine. I've even flashed a ROM and then restored the data partition of a different ROM backup and it was fine. Everything restored as it should have. I also have only ever used TWRP going back to my Bionic days with Safestrap and then my VZW S4 was on TWRP.
I thought the only issue was using TiBu to restore backed up apps caused bootloops.
Eric214 said:
I'm on TWRP 2.6.3.8 and have never had an issue with it. Restores everything fine. I've even flashed a ROM and then restored the data partition of a different ROM backup and it was fine. Everything restored as it should have. I also have only ever used TWRP going back to my Bionic days with Safestrap and then my VZW S4 was on TWRP.
I thought the only issue was using TiBu to restore backed up apps caused bootloops.
Click to expand...
Click to collapse
I used 2.6.3.8 and boot looped. I did ask what I could ha en done wrong and was told I probably used wrong recovery..? So many conflicting stories with TWRP. I used it on my S3 and note 2 and never had a notable problem. Could be the introduction of Knox etc... causing the problems. But I will give Philz a go. Touch sensitivity etc seems a bit trivial. I just want to flash/ recover and not bootloop. I want it to be functional. Thanks for your input, much appreciated.
I went with Philz. .... I like the challenge of learning a new recovery and I like the UI. No problems so far. Made a couple back ups. One stock and one of Wicked and no problems restoring either one. Also backed up my EFS using the aroma installer for CYA purposes. Thanks for all of your input.
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
Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.