Related
Please be patient with me, I'm new to the entire smartphone era.
I've spent the last week or so scouring these forums deciding what I can and cannot do with my brand new Epic. What I unfortunately was unable to find were directions put into laymans terms as exactly how to properly flash your phone (I am still even unsure as to the correct terminology for many things). When I read the wiki and the forums I'm lost about a paragraph in.
It would be incredibly appreciated if any of you had tips for a new person to these forums and to this lifestyle itself. I'd love to know how to properly modify my phone without breaking it (and not feel like I'm reading a medical dictionary). When/if I do mod my phone, I'd like to know how to go about restoring it should I for whatever reason need to take it in to the extremely... helpful.. Sprint store here in my area. I'm pretty quick to learn and as I said, I'd really love if someone willing to be patient with me would explain to me the ins and outs I would need to know to take advantage of my phones capabilities.
Well most roms now use ext4 filesystem instead of RFS (default) so you have to install Clockwork Mod 3 which will auto convert it
CWM3 directions:
Download Here
On phone go to applications -> development -> usb debugging (turn on)
plug phone into usb port, run the run.bat from the CWM folder (it might say something like restart server and wait for phone to reconnect i generally just close the window and run the run.bat again then it'll mount as r/w and install)
Then after your phone reboots transfer any ec05 ext4 rom to your sdcard, i suggest This one.
After that turn off your phone completely.
Hold volume down, camera button, power. This will boot into clockworkmod.
CWM will backup all data, format, then restore the data... it'll take a few minutes.
Now if you want to start fresh click wipe data / wipe cache and also go to advanced/wipe dalvic cache. If you want to keep all your apps just proceed to the next step
go to Install from sdcard, browse sdcard for the rom.zip, select it, let it do its magic, after its done go back to the main menu, reboot system, and you're done
EDIT: Cwm controls -> volume up/down to naviage, Power = back, Camera = select. I think you can also use the keyboard arrows and stuff but i find it easier using the buttons
I think you should start him with cw2.5 instead of 3.0. 3.0 will brick his phone unless he is ready to flash a rom right alway!!
Those directions are much easier to follow.
What are the negatives to doing this to your phone (besides the ultimate brick)? Would doing this allow me to give my phone the ability to hotspot it?
How would I go about restoring it should I not like Syndicate and wish to return to stock?
OmegaMateria said:
Those directions are much easier to follow.
What are the negatives to doing this to your phone (besides the ultimate brick)? Would doing this allow me to give my phone the ability to hotspot it?
How would I go about restoring it should I not like Syndicate and wish to return to stock?
Click to expand...
Click to collapse
If I was you I wouldn't be in such a rush to flash a rom. Root first and take from there. It took me a whole month to flash a rom before I felt comfortable with the terminology. Catch up on some reading first
hi I also am still new to this even though i flashed my phone at least a 100 times and got my buddys epic rooted i followed this forum http://forum.xda-developers.com/showthread.php?t=798067. they did a great job with links to get cwm2.5 and also the adb files. so when you root your phone the computer will find your phone. One thing that did keep me held up for a while was when you have your phone in debug mode. connect the phone to the usb. but do not press connect on your phone. hope this helps some. I spent about 3 long days reading and gathering everything before trying and like a day and a half trying.
shook187 said:
If I was you I wouldn't be in such a rush to flash a rom. Root first and take from there. It took me a whole month to flash a rom before I felt comfortable with the terminology. Catch up on some reading first
Click to expand...
Click to collapse
You're probably very right.
What permissions does rooting get me? To root my phone I should use clockwork or something different? If so, you suggested 3.0 and someone else 2.5. Opinions on both for a newbie?
shook187 said:
I think you should start him with cw2.5 instead of 3.0. 3.0 will brick his phone unless he is ready to flash a rom right alway!!
Click to expand...
Click to collapse
No such thing will occur. He might get it into a position of where he can only use odin but certainly not a brick. I have heard of only 1 person bricking their phone in 6 mths and that was a dev cuz he was messing with the bootloader. Jump in at your own pace.
Sent from my SPH-D700 using XDA App
OmegaMateria said:
You're probably very right.
What permissions does rooting get me? To root my phone I should use clockwork or something different? If so, you suggested 3.0 and someone else 2.5. Opinions on both for a newbie?
Click to expand...
Click to collapse
I never suggested 3.0, I would do 2.5. 3.0 Requires you to flash a rom cause it won't boot without a rom. If you use 3.0 without flushing a rom, you'll get stuck at the samsung screen.
shook187 said:
I never suggested 3.0, I would do 2.5. 3.0 Requires you to flash a rom cause it won't boot without a rom. If you use 3.0 without flushing a rom, you'll get stuck at the samsung screen.
Click to expand...
Click to collapse
Sorry, my mistake!!
I'll check out 2.5. Anything I should know about rooting in general?
OmegaMateria said:
Sorry, my mistake!!
I'll check out 2.5. Anything I should know about rooting in general?
Click to expand...
Click to collapse
The main thing which you already mention is the free wireless tether.
CWM 2.5.5 = the RFS root method. You can use it to install EC05 roms that have RFS support
It allows you to run programs with superuser... such as wifi tether, wireless tether, titanium backup, root explorer... thats about it for the basic user
If you want tweaks/fixes what you want is a custom rom... most all will have
Call log fix (remove the sms notifications from in your call log), Kernel fixes/updates/added features, deodexed, zipaligned, custom boot animations, voodoo audio/color, custom touchwiz, etc..
You wont brick your phone regardless, but if you do it exactly as i typed you wont have any problems either . The reason you want to put a rom on your sdcard before you boot into CWM3 is so you can flash a compatible rom that has a ext4 kernel...
EDIT: and regarding the negatives, well you wont brick your phone unless say your battery dies as you flash it... The ext4 non-journaled will actually make your phone last longer over the RFS system. The only thing I can think of is the root method removes the Free HD games and Asphalt 5 Demo which the official OTA updates check for when u get them. Doesn't matter though because you can update your rom through CWM anyways lol.
About positives, atleast for me: Longer battery life, faster phone, less annoying bugs, sexy look, custom boot/shutdown, free wifi tether/wired tether, automatic backups set every night at 5am.
I went straight to cwm 3.0.0.6 as a noob but I must have read 1000 posts in various forums regarding root, the file system(s), custom software/ROMs/kernels. The key is read post after post about where others have had issues until you no longer come accross any new issues. Then you know what you are getting into. Just remeber, glitches can occur and during flashing, there are writes that have no error checking and sometimes require a reflash at best and a system restore at worst. It comes with the territory. It is unlikely you will brick your device as long as you are careful to follow insructions, although the reality is (no matter how many times you hear how safe it is) that there is a very very slight chance that a glitch while using software such as odin could send you back to the Sprint store for a new one. Its exceedingly rare, though.
The small risk was worth getting the phone that I wanted originally - instant responsivness, access to every customization and dev. level control of the hardware (free tethering!) - everything runs better - games,browsers,vids (look better and sound better), music sounds better, etc. Etc. There are some seriously talented devs. here. If you decide to take the plunge, check out k0's ACS Frozen ROM and mysteryEmotionz (sp?) Theme(s). When you go from stock to those, you can't help but wonder WTF sprint and samsung are thinking. Yeah, its that good.
Good luck!
Sent from my SPH-D700 using XDA App
blu9987 said:
CWM 2.5.5 = the RFS root method. You can use it to install EC05 roms that have RFS support
It allows you to run programs with superuser... such as wifi tether, wireless tether, titanium backup, root explorer... thats about it for the basic user
If you want tweaks/fixes what you want is a custom rom... most all will have
Call log fix (remove the sms notifications from in your call log), Kernel fixes/updates/added features, deodexed, zipaligned, custom boot animations, voodoo audio/color, custom touchwiz, etc..
You wont brick your phone regardless, but if you do it exactly as i typed you wont have any problems either . The reason you want to put a rom on your sdcard before you boot into CWM3 is so you can flash a compatible rom that has a ext4 kernel...
EDIT: and regarding the negatives, well you wont brick your phone unless say your battery dies as you flash it... The ext4 non-journaled will actually make your phone last longer over the RFS system. The only thing I can think of is the root method removes the Free HD games and Asphalt 5 Demo which the official OTA updates check for when u get them. Doesn't matter though because you can update your rom through CWM anyways lol.
About positives, atleast for me: Longer battery life, faster phone, less annoying bugs, sexy look, custom boot/shutdown, free wifi tether/wired tether, automatic backups set every night at 5am.
Click to expand...
Click to collapse
I went into the run.bat file in the one click root and removed the 2 lines that give the command to delete the free hd games demo and asphalt 5 demo. Ran the one click root, and I still have those 2 installed on my phone. Beats having to reinstall them again in the future and preventing an update because of the missing apps.
Tirregius said:
I went straight to cwm 3.0.0.6 as a noob but I must have read 1000 posts in various forums regarding root, the file system(s), custom software/ROMs/kernels. The key is read post after post about where others have had issues until you no longer come accross any new issues. Then you know what you are getting into. Just remeber, glitches can occur and during flashing, there are writes that have no error checking and sometimes require a reflash at best and a system restore at worst. It comes with the territory. It is unlikely you will brick your device as long as you are careful to follow insructions, although the reality is (no matter how many times you hear how safe it is) that there is a very very slight chance that a glitch while using software such as odin could send you back to the Sprint store for a new one. Its exceedingly rare, though
Click to expand...
Click to collapse
Yeah I've spent the entire week when not at work reading about it to see if it's worth it. I have a hard time following the directions I find though because they're normally written for experienced folks and not beginners.
Apart from Rooting it (as explained very well earlier) I still have no clue about flashing, how it works, or how to do it. Nor do I want to just fiddle around with it and break it. I can't find a good guide on ODIN or backing up that I can understand comfortably enough to risk flashing my phone so I'm kindof at a loss.
Go on YouTube and search "randyshear". He has step by step videos for pretty much everything. Makes it easy
Sent from my SPH-D700 using XDA Premium App
OmegaMateria said:
Yeah I've spent the entire week when not at work reading about it to see if it's worth it. I have a hard time following the directions I find though because they're normally written for experienced folks and not beginners.
Apart from Rooting it (as explained very well earlier) I still have no clue about flashing, how it works, or how to do it. Nor do I want to just fiddle around with it and break it. I can't find a good guide on ODIN or backing up that I can understand comfortably enough to risk flashing my phone so I'm kindof at a loss.
Click to expand...
Click to collapse
I was the same way and to some degree still am. What I did was read and read. I read the WIKI several times realizing that a lot of it was written for someone more experienced than I. I also read how to restore a bricked device and return to stock a few times. I installed everything to return to stock on my PC so if I had a failure I already had my path back to working stock. I went to CM 2 just to get some experience. Then I went for it to CM 3 and Syndicate 1.0 and have been incredibly happy that I did.
Also know that terms like brick are used a lot but is then followed up with my phone will do this or that. In the definitions a brick is literally as good as a brick for a phone. The term is used way too much incorrectly so don't let that scare you. You will see when reading that there are only a few things to do if there is a problem. Frequently you will read to re download the files or use a different cable or USB port. If you keep reading you will become more comfortable with your ability to find the answers if there is a problem because there are people on here that seem to take great joy in helping people like you and I out and they have the experience and knowledge to help.
Trust me ... keep reading and searching and you will start to put the pieces together. Don't be discouraged. If you are really interested in this stuff, you WILL get there.
Sent from my SPH-D700 using XDA App
Definitely agree with JohnCorleone, Randyshear has a ton of very good youtube vids. Helpful with rooting also with picking a ROM. Just to add my two-cents. The "epic cookbook" http://forum.xda-developers.com/showthread.php?t=967014...Helped me over and over again. alot of info, without alot of scavenging throughout threads. Good luck
There is no need to flash a rom right off the bat. Rooting with one click will give you a good jumping point. I would one click root to cw3 let it convert to ext4 then do a backup. Use titanium backup to remove all the junk bloatware.
Sent from my SPH-D700 using XDA App
To be honest,
Once I got to the rogue et recovery I cried a little (because I actually got there.)
7 hours worth of beating sleep, numb legs from sitting down, afro being dry, and Samantha (samsung support person, cause I really was going to send my phone in..)
Two batteries *thank god!
Don't really, can't explain much. Just a load of reading of the "download shabby's/acs leaked fb17...." thread, xda search tool, google, and youtube.
I'm just glad, I found some way to enable recovery. No, 2 weeks without a phone, no going to the shipping retail location, no "not having my little cloud(white e4gt) in my hand." ....cheesy
I hear birds chirping outside, wow, and the sun is starting to come up.
Now I must figure out what I need to do next in recovery, then get out this desk chair (because my dsfgh...), and go to sleep!
XDA ROCKS!
Wut? You saying you brought your E4GT back from a brick?
Sent from my SPH-D710 using Tapatalk
How did that happen?
I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk
What type of brick lol? A soft brick all you need to do is go into download mode and ODIN over some new firmware, forget recovery lol. Unless it was a super brick from flashing ICS recovery where you luckily have recovery... your still pretty screwed. But if it was just a bootloop, soft brick the fix is simple.
slick_rick said:
I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?
K.0.0.L. said:
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?
Click to expand...
Click to collapse
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.
RainMotorsports said:
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.
Click to expand...
Click to collapse
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up
K.0.0.L. said:
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up
Click to expand...
Click to collapse
Wicked sensation is an ICS rom right? Did you flash AOKP 39 from ICS Recovery? The one thing you should not do? If the rom does not have a safe updater binary there is a high chance of super brick when flashing from even a safe ICS recovery, and even higher from the regular repacks. NEVER factory reset from any non safe ics recovery and never flash a zip in ICS recovery unless it is marked as safe to do so.
If when trying to ODIN stock firmware it gets stuck at Data.img then you really did it this time. From what I have heard there are 2 levels of the super brick. The kind where you can still get to download and recovery and the kind where you cant. Stuck on Data.img on the first kind is a bad sign.
As far as the triangle goes that comes up any time you odin an unsigned kernel etc like the el26 cwm one. It is just an indicator and should not be a part of your problem.
Flash any stock gb kernel it should remove the triangle! (ODIN)
I don't really know what's up right now...
The whole reason I'm in this mess is me changing settings when I first flashed AOKP 39. Like setting display, changing the wallpaper. Just going straight down the whole setting page.
I got to the DPI settings, changed it to something lower, 240 i think. Rebooted... Didn't like it, changed it back to the original, rebooted... the words and all were original but not the status bar, not the lock screen, not the navi bar.
It was super weird!
So I thought:
"...doing a factory reset would allow me to start fresh again. If that doesn't work, I can just start completely over(odin back to gb). that way I can install gapps(the arrangement of back and enter buttons confused me, causing me to restart)"
All of a sudden, phone didn't work. Can't really remember what happened at the time. If it went into boot loop or not. But it didn't go into the rom.
Somehow, I ending up doing stuff, since I just got it a week ago I really didn't know much, was just learning as I went. "new phone, new things to learn"
Anyways, ending up with "A" recovery, and I've always been able to get into ODIN.
recovery that works is: rogue_ET-recovery-1.2.2-FB27-rc0.tar
Now that I have some kind of recovery and odin I thought, maybe I could get back to stock. Just don't know how, thats were doing more searches came in. Still got NOTHING. lol.
I was aware of not flashing ics from an ics dadada messages. hint: i read stuff
I did a factory reset which caused all of this. Kinda know I shouldn't of done it now, ...never came across anything about not doing it at the time. I still haven't, I'll google that too.
Umm.. flashing stuff through pda doesn't work. to be more specific
when I look at the progress, it doesn't include data.img (so it PASS)
if I odin something and it says data.img, then its stuck there.
so that recovery I'm using: (volup+pwr)
bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) -> recovery
any other tries when getting into recovery WITHOUT odin rogue_ET-recovery-1.2.2-FB27-rc0.tar: (volup+pwr)
quick led(blue) -> bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) bootloop bootloop bootloop. Sometimes it will stay there for a few minutes then bootloop again.
-----
so right now, ....still trying to find a solution. I'm still on google and xda searching. I really don't want to do anything else because both batteries I think are nearly dead...
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.
AndroidRocksSocks said:
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
Click to expand...
Click to collapse
Suicide.
AndroidRocksSocks said:
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.
Click to expand...
Click to collapse
Because the /Data partition is borked.
RainMotorsports said:
Suicide.
Because the /Data partition is borked.
Click to expand...
Click to collapse
Right, had* to be something.
CPR?
If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.
evo-t said:
If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.
Click to expand...
Click to collapse
....lol he already said he is getting past that. Still the same issue though he is Super Bricked.
AndroidRocksSocks said:
Right, hand to be something.
CPR?
Click to expand...
Click to collapse
Your at the level where some people seemed to have been able to repartition the eMMC around the origina /Data area consuming space other partitions normally used. Its not considered stable.
There is no premenant fix that can be applied by you, a sprint store, or even jtag service. The Super Brick bug corruption occurs at the lowest possible level. You basically need Samsung to fix it, though just about anyone on the eMMC partner list technically can.
Phone replacement is the primary option or you can see about getting info about the repart here - http://forum.xda-developers.com/showthread.php?t=1644364
Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.
AndroidRocksSocks said:
Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.
Click to expand...
Click to collapse
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.
RainMotorsports said:
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.
Click to expand...
Click to collapse
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.
AndroidRocksSocks said:
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.
Click to expand...
Click to collapse
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.
RainMotorsports said:
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.
Click to expand...
Click to collapse
Oh wait a min...
Right, yea I did.
This one: Discussion thread for /data EMMC lockup/corruption bug
Hey I got my phone rooted, so I installed Titanium Backup, and then I uninstalled the stock browser, the download manager, and also android.downloader or something like that. And I broke my phone - now Google Play just crashes instantly.
I've tried reinstalling the firmware, and resetting to factory, but it's still the same.
Is there anything I can do, other than take it back to the store?
Help!!!!!
EDIT: It gives the error "Unfortunately the process com.google.process.gapps has stopped."
did you do a nandroid backup?> if not we need to know the exact application you deleted. future reference DONT DELETE. just freeze then its just a simple unfreeze and a freeze also stops the app from running. you will not get more available memory by doing this because this is on a different partition. Also never delete or freeze anything referring to com.android they are core funtions that are required for your device to run properly.
You deleted a process?!
My money would be that android.download or whatever process you deleted was required for Google Play to work. Hopefully you made a Nandroid before modifying processes. If not, you'll have to flash a stock ROM to get it back.
Alternatively, if you backed up system data with Titanium Backup, you might be able to find the process in there and restore it.
Echoing drksilenc, don't uninstall things through Titanium Backup unless you're positive it won't mess something up. How can you be positive? One, deleting processes always causes problems. Even freezing them can be messy. Don't do it. Two, in the case of an app, you'll know it's ok if you've had it frozen for a week or so and the phone hasn't acted up. Even with system apps, though, I recommend freezing rather than uninstalling. It's safer, and you never know if you might want/need that app again.
It gets worse.
I went down to the Bell store (my phone's actually from Bell, but they're similar to the AT&T ones, right?) and they wouldn't exchange it. So I tried going into the Clockwork Recovery, and wiped all of the little folders in "Advanced Settings." Because I noticed that Bell's add-on apps kept coming back, why weren't the other ones I deleted? And now it's a useless brick, says SAMSUNG and that's it.
Brand new one-day old superphone, totally wrecked. I don't even think there are any stock ROM's out there for this thing yet.
I'm a meathead.
I'll try reinstalling the firmware again that I did before, maybe I'll get lucky.
Nope, still nothin'.
So now I'm going to do something really crazy. Somebody on the interwebs says you can flash the SGH-1317M with the stock rom for the GT-N7105. Says it's the same thing except it's the international version and that it's even better.
I went to samsung-updates.com and searched for the Note 2, and sure enough, it's on their list of ROMs for the Note 2. So I'm downloading the GT-N7105, and I'ma gonna install it, unless someone here tells me different!
d3fau1t said:
Nope, still nothin'.
So now I'm going to do something really crazy. Somebody on the interwebs says you can flash the SGH-1317M with the stock rom for the GT-N7105. Says it's the same thing except it's the international version and that it's even better.
I went to samsung-updates.com and searched for the Note 2, and sure enough, it's on their list of ROMs for the Note 2. So I'm downloading the GT-N7105, and I'ma gonna install it, unless someone here tells me different!
Click to expand...
Click to collapse
I wouldnt do that!!! The boot.img will brick you im pretty sure! You cant download and flash a rom in development section? And I thought I saw a stock tar floating around?
truth77 said:
I wouldnt do that!!! The boot.img will brick you im pretty sure! You cant download and flash a rom in development section? And I thought I saw a sti c k tar floating around?
Click to expand...
Click to collapse
I found a Cyanogenmod ROM but even that says it's for the n7100. I can't seem to find anything for the sgh-1317m.
d3fau1t said:
So now I'm going to do something really crazy. Somebody on the interwebs says you can flash the SGH-1317M with the stock rom for the GT-N7105. Says it's the same thing except it's the international version and that it's even better.
Click to expand...
Click to collapse
Don't do that. For one, flashing a ROM for a different device is virtually always Detroit Brick City. Two, the guy's got two whole posts. Don't do it.
d3fau1t said:
I found a Cyanogenmod ROM but even that says it's for the n7100. I can't seem to find anything for the sgh-1317m.
Click to expand...
Click to collapse
Any rom in our dev section should fix you try clean rom ans stop using titanium vackup. Why are you debloating roms when devs did it for you already and obviously you see you have no clue what you're doing?
[/COLOR]Lol... that didn't work at all... I thoughtbthe links would copy over... look in the android dev section theres a rom there for you. .. 8)
Sent from my SGH-I317M using xda premium
Just flash any rom in the android development section usinf twrp or cwm, it will rebuild /system and fix any issues. In the future dont delete or uninstall system apps, just freeze them if you think yiu dont need it. Freezing stops the app from running ans taking up any cpu or memory so its almost as good as deleting (it still technically takes up space but this phone has plenty of space) with nine of the dangers. If something stopped working like play store, youvcan defrost the apps yiu froze easy enough.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
glitchsys said:
Just flash any rom in the android development section
Click to expand...
Click to collapse
Is that going to be ok even though I'm on a Bell phone and it's sgh-i317m? Cuz I don't see any ROM's that end in M...
Big thanks to everyone trying to help.
d3fau1t said:
Is that going to be ok even though I'm on a Bell phone and it's sgh-i317m? Cuz I don't see any ROM's that end in M...
Big thanks to everyone trying to help.
Click to expand...
Click to collapse
Yes we promise lol and dont freeze or delete anything just leave it to the devs and only download stuff from this forum i317/i317m
Sadly, failure
I downloaded CleanROM Lite 1.0.zip, put it on the SD card, and used Clockwork Recovery to install it. The installation went without a hitch, but trying to boot the phone, all I get is the SAMSUNG logo still. So I did a factory reset, wiped the cache, wiped the Dalvik cache, and did "fix permissions", but it's the same.
So I'm downloading the other ROM ("Stock Root - De-Odex") and will try that presently.
d3fau1t said:
I downloaded CleanROM Lite 1.0.zip, put it on the SD card, and used Clockwork Recovery to install it. The installation went without a hitch, but trying to boot the phone, all I get is the SAMSUNG logo still. So I did a factory reset, wiped the cache, wiped the Dalvik cache, and did "fix permissions", but it's the same.
So I'm downloading the other ROM ("Stock Root - De-Odex") and will try that presently.
Click to expand...
Click to collapse
These roms take a while to boot how long did you wait. Look you didnt break your phone from deleting apps just flash the rom and wait it will boot. Remember these roms are 750-800 mb worth of data to boot not 250mb like aosp roms, takes few mins to boot
truth77 said:
These roms take a while to boot how long did you wait. Look you didnt break your phone from deleting apps just flash the rom and wait it will boot. Remember these roms are 750-800 mb worth of data to boot not 250mb like aosp roms, takes few mins to boot
Click to expand...
Click to collapse
You might have been right. I'm so used to it just freezing up that maybe I wasn't patient enough and just assumed.
But it works now! I flashed the Stock ROM, and it booted up with no problems. Then I flashed the lite one again, and it works too. So now I'm going to try the other ROM on the dev page, see how it looks.
And it's still rooted, so hooray!
Thanks for all your help.
you REALLY need to do ALOT more READING, and ALOT LESS Flashing...
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
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