Related
It seems like Mijjz's Blend ICS ROM is getting a lot of hits and could be a daily driver. I use my phone for work so I have been a little hesitant to jump on the ICS wagon until reading more. After digging, I still have some questions from the folks using it now...
Is it REALLY as easy as formatting and installing from the ZIP? I'm running Blazer's ROM now..
Does Exchange work?
GPS (without needing to complete some sort of Vodoo ritual)?
Just back up your current setup. That way if you don't like it you can go back.
You can flash from gb rogue recovery(not touch recovery) to ics. Make sure you wipe everything well. (except sd card)
If you go back, make sure to use the 1 click Odin, DO NOT TRY TO FLASH YOUR GB BACKUP FROM ICS RECOVERY. ALWAYS ODIN. I usually go back to el29 to upgrade ics versions, it insures a clean install. Good luck! Gps and exchange have been working, if they don't you probably did something wrong.
Sent from my SPH-D710 using Tapatalk 2 Beta-3
robbyr said:
It seems like Mijjz's Blend ICS ROM is getting a lot of hits and could be a daily driver. I use my phone for work so I have been a little hesitant to jump on the ICS wagon until reading more. After digging, I still have some questions from the folks using it now...
Is it REALLY as easy as formatting and installing from the ZIP? I'm running Blazer's ROM now..
Does Exchange work?
GPS (without needing to complete some sort of Vodoo ritual)?
Click to expand...
Click to collapse
I've been using Goodness since version 1. It is 100% a daily driver!
1) Yes it really is as easy as all that. I'd follow the instructions in the OP just to make sure you get it right but yeah, piece of cake.
2) Exchange works, most of the time. I know there have been a few releases where it hasn't but Mijjah is super responsive and gets it fixed extremely quickly.
3) GPS had some issues in the beginning but I've not had any issues. I got lost downtown yesterday and pulled it out, got a lock in five seconds and it got me right where I needed to be.
Long story short? Just do it! It's the best ROM out there! Team Nocturnal kicks butt and if you have questions hope on their thread and you'll get an answer super fast. Everyone there is super helpful and friendly.
Enjoy your new ROM!
GPS is either completely random or people are having alot more trouble than they should be.
FC07+ for me GPS has worked out of the box everytime.
robbyr said:
It seems like Mijjz's Blend ICS ROM is getting a lot of hits and could be a daily driver. I use my phone for work so I have been a little hesitant to jump on the ICS wagon until reading more. After digging, I still have some questions from the folks using it now...
Is it REALLY as easy as formatting and installing from the ZIP? I'm running Blazer's ROM now..
Does Exchange work?
GPS (without needing to complete some sort of Vodoo ritual)?
Click to expand...
Click to collapse
What the other 3 posters said is all 100% correct. Be sure to read the first 4 posts in the thread, not just the first one. Follow the posted flashing instructions, have questions, check the FAQ in post #4.
Team-Nocturnal Blended ICS
I have been running the blend roms since fc07 every update and I am like you i use my phone everyday for work and i was worried. One night i sat and read every post in the forum for the blend ics rom and decided to do it. Fc07 was a lil buggy so i flashed back to el29 for a about a day then decided to try it again. Second go round everything worked except gps i used the work around that they tell u to use and i havent had trouble since. The only other bug was apex launcher if u tryed to dl it from the market and use it it would fc every now and again and that was on fc18. Other than those two small issues everything else has been awesome.
DOHCHP sent from ICS Epic Touch
It seems like the GPS bug is gone with FC22. Is that correct? How about battery life?
robbyr said:
It seems like the GPS bug is gone with FC22. Is that correct? How about battery life?
Click to expand...
Click to collapse
GPS does appear to be fixed. Battery life seems to vary depending on your phone and your setup but I myself am averaging between 10 and 12 hours. I saw a post yesterday where somebody had 24+ hours!
I'm running 2.3 right now and am wanting to flash the newest version. Can I do this from the current recovery or do I need to go back to GB? What is the best process to do this? Noob here haha
Do not flash roms from an ics recovery. Always odin to el29 with CWM then flash ics through CWM
Sent from my SPH-D710 using Tapatalk 2 Beta-3
tkemack said:
Do not flash roms from an ics recovery. Always odin to el29 with CWM then flash ics through CWM
Sent from my SPH-D710 using Tapatalk 2 Beta-3
Click to expand...
Click to collapse
The thread for the ROM says you can do it with just the Calk wipe zip and a few other things Besides, what does Odin to el29 mean? Told you I was a noob.
Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.
My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks
Probably.
I'm running AOKP without any issue. What have you installed recently? Did you flash custom kernel, overclock cpu, change cpu voltages, etc...? Download OS Monitor app and see which processes are eating cpu and your battery. Maybe it's time to wipe everything clean: factory reset, wipe external sdcard, and reflash the ROM. An sdcard full of stuffs can cause the media scanner process to run long and eat up battery.
S-beamed from my GSIII via xda premium
I wouldnt go as fsr as blaming the rom right away, especially if its a milestone. More kernel related and or user error. Give us more info to help you solve this so you can use your the way you want to.
Sent from my SGH-T999 using xda premium
There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.
vx117 said:
There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.
Click to expand...
Click to collapse
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.
More like kernel related but yes aokp and cm10.1 can mess up your phone at times
Aerowinder said:
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.
Click to expand...
Click to collapse
Yes, but even with custom kernels it can get buggy. No kernel is one-size fits all since each chip is unique. You gotta pick and choose which kernel works best for your phone.
Kyle Chen said:
My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks
Click to expand...
Click to collapse
I was having that issu as well but it was with touch wiz roms and kernels it actually ended up being a dud phone and battery. .. I have done a warranty exchange and it fixed it I also got an anker battery too and its been doing good only gets hot when I have it on charge and use it.. so it would ight not be just the rom. Try a different kernel see if its the battery getting hot and go from there. Isolation is key bud:thumbup:
Sent from my SGH-T999 using Tapatalk 2
This morning my phone was stuck on the AOKP boot logo and it was overheated like crazy. I did a battery pull and waited for the phone to cool down. After that I booted it back up, but the battery drained pretty fast and the phone still heated up.
I did not flash any custom kernals or anything. Just AOKP milestone 1.
Maybe I will wipe the entire phone and reflash aokp.
OR
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.
+1
I've been running AOKP since 2 hours after I got my d2tmo, initially KAsp3rd's unofficial builds, and now the official "nightly" builds... I have been using a very stable build since January, but recent official developments have me flashing regularly again.
Every single build since JB 4.2.2 MR1 has been very unstable on my device, somewhat randomly rebooting quite regularly... I say "somewhat" randomly because there are a certain few actions I can perform which will cause reproducible immediate reboots on demand, including but not limited to trying to DISABLE* USB Debugging. I've noticed that the device is far more likely to reboot itself when attempting to run apps as superuser. I noticed that Koush's Superuser app/infrastructure is embedded/integrated in the ROM and when I installed the latest version from the Google Play Store, it said that my su binary was out of date, so I updated it... It didn't resolve the random reboots, but when the device did reboot next, it performed some additional setup steps, including prompting me for my first & last name which was really odd because the initial setup had, I thought, been completed, and the device had been rebooted (by itself mostly) at least a dozen times prior to this.
I suspect these issues might have something to do with the superuser integration in the ROM and I ask that you who are experiencing similar random reboots take note of any patterns such as whether it occurs more often when attempting to perform superuser privilege escalation.
Currently I'm testing whether setting "Superuser Access" to "Disabled" helps at all. I'll report my findings once a conclusion is established.
*I'm trying to disable it to troubleshoot why the device doesn't show up when I issue `./adb devices` on my PC running Ubuntu 12.10 Linux; it doesn't even show up in the list of connected USB devices when I issue a `lsusb` command which is weird. I've rolled back to my backup of the January AOKP 4.1.2 build and confirmed that the device is visible to adb, so it doesn't seem to be an issue with my hardware...
P.S. I've posted about it in the new official d2tmo AOKP Nightly thread on the RootzWiki Forum (linked above).
---------- Post added at 11:29 AM ---------- Previous post was at 10:50 AM ----------
Disabling Superuser didn't seem to help at all. It has still rebooted itself twice since then.
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
PM me for a modified SlimBean build I use if interested. No random reboots and I have had the same issue in the past. Also, you could try wiping 3 times (cache,dalvik, factory reset and system) and then install KT747. Its the most up to date kernel as far as the patches and drivers go.
Sent from my SGH-T999 running Chihuahua v1 ROM
re: acceptable
Ch4m3l30n said:
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
Click to expand...
Click to collapse
Why should any amount of crashes or random reboots be "acceptable" to anyone when there are so many
other roms in these xda forums to choose from which do not crash at all and are full of excellent features? LOL
Make a backup. Wipe cache and data. Then try another rom
Sent from my SGH-T999 using xda premium
My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.
Kyle Chen said:
My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.
Click to expand...
Click to collapse
did you try reformatting your sdcard(s), factory reset, format /system partition (via recovery), and reflash the ROM? maybe just reformat the sdcards first, and see if that helps.
S-beamed from my GSIII via xda premium
Kyle Chen said:
<snip>
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.
Click to expand...
Click to collapse
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.
bwb8771 said:
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.
Click to expand...
Click to collapse
I ended up flashing like a touchwiz galaxy s5 themed kitkat rom, which I have been using since September. Before that I used cyanogenmod 11. Haven't tried AOKP in a long time. When I get time I plan to flash some lolipop rom I guess.
Is there any activity on AOKP any longer, loved rom but it looks like 10/18/14 is the last build i can find.....
Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Anyone ever have this problem?
over16bit said:
Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Click to expand...
Click to collapse
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
alloycowboy said:
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
This...but use Odin to go back to stock. Dont' just try to flash a stock ROM.
REALLY reset it hardcore by using Odin to flash the stock firmware package in its entirety.
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
over16bit said:
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
Click to expand...
Click to collapse
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Flash the 10.16 AOSP 4.3 build of KT's kernel. Any build newer than that is for CM based ROMs compiled AFTER 10.20.
alloycowboy said:
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
over16bit said:
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
Click to expand...
Click to collapse
Sounds like hardware problem. I hope im wrong.
Let us know how it goes after you odin back to stock
Sent from Insane S4
SICK MADE DEVELOPMENT
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