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
The last few weeks I've noticed something odd which as far as I can tell is harmless but would like to understand. When I restart my Note 2 it goes through the entire start up process to the point of being on the lockscreen (perhaps a little further as I can get to home screen). It then spontaneously reboots itself! After that reboot everything appears to be running fine. Any explanation as to why this might happen and how to correct. My device is rooted. Use philz kernal 4.87. I also tried going down to 4.65 but no change.
Thanks!
What other mods do u have? can you link me to the kernel
deeznutz1977 said:
What other mods do u have? can you link me to the kernel
Click to expand...
Click to collapse
Hi. The kernel is from this thread.
http://forum.xda-developers.com/showthread.php?t=2028103
It has many nice features. I'm struggling to recall when this all started. It was before I upgraded to 4.12 via kies. I actually have not done a lot of mods as I reserve my tinkering for my Note 1 and use the Note 2 for my daily drive. But on the Note 2 I first used chainfire scheme to root. Shortly after that I used the Xposed framework to have unlimited apps in multiview. Then a bit later flashed the Philz kernal (Used mobile odin to do that the first time).The other thing I use that depends on root is linux on android and titanium backup. I look at this as rather modest mods.
I'm considering starting again from scratch but if you have some suggestions I might give it a go. I'm still learning about android (here is another opportunity!) coming from a N900. It seems there is a possibility it is a bit sensitive as it is booting up such that if an app is attempting something before the boot up is completed it triggers it to reboot. (Sorry if that is vague sounding). Is there a system log I can check to possibly track this down? Let me know if you need any specific information and I'll try to provide it. Thanks!
mscion said:
Hi. The kernel is from this thread.
http://forum.xda-developers.com/showthread.php?t=2028103
It has many nice features. I'm struggling to recall when this all started. It was before I upgraded to 4.12 via kies. I actually have not done a lot of mods as I reserve my tinkering for my Note 1 and use the Note 2 for my daily drive. But on the Note 2 I first used chainfire scheme to root. Shortly after that I used the Xposed framework to have unlimited apps in multiview. Then a bit later flashed the Philz kernal (Used mobile odin to do that the first time).The other thing I use that depends on root is linux on android and titanium backup. I look at this as rather modest mods.
I'm considering starting again from scratch but if you have some suggestions I might give it a go. I'm still learning about android (here is another opportunity!) coming from a N900. It seems there is a possibility it is a bit sensitive as it is booting up such that if an app is attempting something before the boot up is completed it triggers it to reboot. (Sorry if that is vague sounding). Is there a system log I can check to possibly track this down? Let me know if you need any specific information and I'll try to provide it. Thanks!
Click to expand...
Click to collapse
That's recovery not a kernel.. 1, Backup all your apps&data with titanium . 2,download this: http://forum.xda-developers.com/showthread.php?t=1975560.. 3, Factory reset& wipe caches 4, flash the downloaded file in odin.. Dont flash anything else reboot, setup your phone. now one by one try out your mods you want rebooting to check if all is well.... Let me know how it goes
deeznutz1977 said:
That's recovery not a kernel.. 1, Backup all your apps&data with titanium . 2,download this: http://forum.xda-developers.com/showthread.php?t=1975560.. 3, Factory reset& wipe caches 4, flash the downloaded file in odin.. Dont flash anything else reboot, setup your phone. now one by one try out your mods you want rebooting to check if all is well.... Let me know how it goes
Click to expand...
Click to collapse
Thanks again. You're right. That work by Philz is recovery not kernal. I've gotten into a bad habit of calling it a kernel. I think the title in the thread used say kernal but I see it has changed. I've since removed 4 or 5 apps and since then I haven't seen the extra reboot take place. So far I've rebooted 7 times today. Doesn't mean the problem is solved but it is certainly happening less frequently! If I spot it happening again I will give mrRobinson's rom a go.
mscion said:
Thanks again. You're right. That work by Philz is recovery not kernal. I've gotten into a bad habit of calling it a kernel. I think the title in the thread used say kernal but I see it has changed. I've since removed 4 or 5 apps and since then I haven't seen the extra reboot take place. So far I've rebooted 7 times today. Doesn't mean the problem is solved but it is certainly happening less frequently! If I spot it happening again I will give mrRobinson's rom a go.
Click to expand...
Click to collapse
Hey, if you need help dont hesitate to pm me
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
internetpilot said:
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
Click to expand...
Click to collapse
It's been a long time since I've dealt with custom recoveries, but I believe that's just the normal background for it. It's like you're tinkering with the inner working of an Android (wiping cache, etc), so you've opened up the green robot.
That's what I recall from when I still had stock about 9 months ago...
If it shows up like that, that means you have the stock recovery...use GooManager or Rom Manager to install a custom recovery while booted up.
Sent from my buttered S3
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
internetpilot said:
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
Click to expand...
Click to collapse
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there.
Click to expand...
Click to collapse
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
internetpilot said:
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
Click to expand...
Click to collapse
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
Click to expand...
Click to collapse
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
internetpilot said:
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
Click to expand...
Click to collapse
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
flastnoles11 said:
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
Click to expand...
Click to collapse
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
internetpilot said:
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
Click to expand...
Click to collapse
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
flastnoles11 said:
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
Click to expand...
Click to collapse
True. I always forget the Odin option for when recovery fails. But I'd be without the data and current configuration (basically starting from scratch).
In the last two days I've seen posts from over a dozen people now who are encountering this issue with brand new Sprint S3's. I'm kinda hoping more and more people encounter this problem increasing the chances of it being resolved... Haha
It doesn't matter once your rooted and booted all you do us download either rom Manager or goo manager and install the custom recovery of your choice from the running phone. Doesn't get any easier.
Sent from the future via Tapatalk 4
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
internetpilot said:
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
Click to expand...
Click to collapse
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
edfunkycold said:
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
deutscher3891 said:
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
Click to expand...
Click to collapse
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
internetpilot said:
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
Click to expand...
Click to collapse
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
deutscher3891 said:
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Both directly from Sprint.
lvpre said:
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
Click to expand...
Click to collapse
The problem isn't really root. Depending on the method, we can get root. It's the custom recovery that's the problem -- it can't mount anything so you can't flash anything, backup, wipe, etc via recovery.
Hi all,
I've recently rooted my phone as per mrRobinson's thread and used TWRP to flash Liquidsmooth 2.9 my phone. It worked beautifully for a night and then a day later, while I was receiving/typing a text, the phone went into ~2 cycles of reboot loop. Later during the day, while I was reading on the browser I would get random reboots after the phone seemingly freezes.
I tried reflashing the ROM after wiping everything (except for the internal storage) a few times.
Has anyone had this problem or experienced a similar situation? I tried searching a bit and reading the Liquidsmooth 2.9 thread but nothing about random reboots seems to occur... yet.
Thanks guys.
Experiencing reboots as well, after upgrading from 2.8 to 2.9. Primarily only happens when plugging in my phone to charge. This wasn't happening when I was on 2.8.
Perhaps this would be a more appropriate thread for these entries?
http://forum.xda-developers.com/showthread.php?t=2346973
Phone: Samsung Galaxy S III SGH-i747
Previous ROM: Liquid-JB-v2.8-OFFICIAL-d2att.zip
Current ROM: Liquid-JB-v2.9-OFFICIAL-d2att.zip
Sure said:
Experiencing reboots as well, after upgrading from 2.8 to 2.9. Primarily only happens when plugging in my phone to charge. This wasn't happening when I was on 2.8.
Perhaps this would be a more appropriate thread for these entries?
http://forum.xda-developers.com/showthread.php?t=2346973
Phone: Samsung Galaxy S III SGH-i747
Previous ROM: Liquid-JB-v2.8-OFFICIAL-d2att.zip
Current ROM: Liquid-JB-v2.9-OFFICIAL-d2att.zip
Click to expand...
Click to collapse
Unfortunately when I was posting this thread I was (and still am) under the 10 post limit, lol. I've decided to just stick to CM10 for now. I might try to reflash 2.9 again. If that doesn't work, I might try different settings for the CPU (eg. on demand? mine was set to interactive). Additionally, I think the liquid team is moving towards 4.3 so I'm not even sure if this is going to matter to them...
This didn't happen to me, but I upgraded from 2.3. Got a little behind on the releases lol. Also, which kernel are you using? With liquidsmooth the stock kernels don't like my phone so i have to flash another...
_alp1ne said:
This didn't happen to me, but I upgraded from 2.3. Got a little behind on the releases lol. Also, which kernel are you using? With liquidsmooth the stock kernels don't like my phone so i have to flash another...
Click to expand...
Click to collapse
Wait, are you saying the stock kernel that came with the liquidsmooth roms? Are you also using an S3? Lastly, which kernel are you using now (and did you change the CPU/performance settings)?
duketerm said:
Wait, are you saying the stock kernel that came with the liquidsmooth roms? Are you also using an S3? Lastly, which kernel are you using now (and did you change the CPU/performance settings)?
Click to expand...
Click to collapse
Well i meant the kernel that is automatically installed when you flash Liquidsmooth. I am using the ATT S3 at the moment. The kernel that came with liquidsmooth always caused random reboots and similar problems for me. Now i use the BMS kernel (here) and have no more problems. I didnt really mess with the CPU settings on the liquidsmooth kernel, just set max frequency to 1242mHz for some extra battery life. With the BMS kernel, I have it undervolted -105mV and again set max frequency to 1242mHz.
Sorry for the confusion.
equhmiduff
Hey guys
Same Problem here, but first of all am not a developer and i know nothing about it i installed font installer to change font after rooting and bricked my XT925 and after long looong search i flashed Liquidsmooth 2.8 and 2.9 and the constantly reboots always happening i heard it is because of RAM and running apps, so i installed RAM booster app and problem still exist suddenyl launcher freezes and device reboots
Tried ROMs : CM10.2 - PAC Man
Device : Droid Razr HD
Current ROM : Liquid 2.9
Launcher Used : TSF Shell - Next Launcher
Bootloader : Unlocked
Recovery : oudhs recovery
atteya.mohamed said:
Hey guys
Same Problem here, but first of all am not a developer and i know nothing about it i installed font installer to change font after rooting and bricked my XT925 and after long looong search i flashed Liquidsmooth 2.8 and 2.9 and the constantly reboots always happening i heard it is because of RAM and running apps, so i installed RAM booster app and problem still exist suddenyl launcher freezes and device reboots
Tried ROMs : CM10.2 - PAC Man
Device : Droid Razr HD
Current ROM : Liquid 2.9
Launcher Used : TSF Shell - Next Launcher
Bootloader : Unlocked
Recovery : oudhs recovery
Click to expand...
Click to collapse
Yes, I get the same problem: the phone freezes (eg. on browser, texting, etc.) and then reboots. I haven't tried reflashing it and changing CPU settings... Have you?
I don't know what to tell you guys. I went ahead and flashed every version of liquidsmooth from 2.5 to 2.9 everyday the past week and used them for about a day each, and i have not had any problems. No reboots, crashes. Not all s3's are created equal i guess...
sorry i couldn't be of help
_alp1ne said:
I don't know what to tell you guys. I went ahead and flashed every version of liquidsmooth from 2.5 to 2.9 everyday the past week and used them for about a day each, and i have not had any problems. No reboots, crashes. Not all s3's are created equal i guess...
sorry i couldn't be of help
Click to expand...
Click to collapse
Hmm, the only thing I can think of now is maybe the type of recovery we use? I used TWRP 2.6.0.0. What about you?
possible recovery issues--
duketerm said:
Hmm, the only thing I can think of now is maybe the type of recovery we use? I used TWRP 2.6.0.0. What about you?
Click to expand...
Click to collapse
I used clockworkmod, forgot which version. I will test different recoveries when I get home.
EDIT: I flashed it on cwm v6.0.3.1, which is not the latest version of cwm.
Sent from my SGH-I747 using xda app-developers app
Will test twrp 2.6 in a few minutes..... Will report back later if I can.
well..... Tried to flash liquid smooth today. Just finished unbricking my device a few minutes ago. Soft brick due to an error flashing. Reinjected IMEI and restored must everything.... Will reflash via CWM later.
_alp1ne said:
well..... Tried to flash liquid smooth today. Just finished unbricking my device a few minutes ago. Soft brick due to an error flashing. Reinjected IMEI and restored must everything.... Will reflash via CWM later.
Click to expand...
Click to collapse
Thanks for doing all of this. I have another question for you since you've told me you had to reinject IMEI... How did you back up your IMEI? I've been looking around but only the basic samsung thing worked for me since I'm already on CM10.
I tried to use this thread: http://forum.xda-developers.com/showthread.php?t=1804117 but I'm unsure how to run that gscript... Thanks for your help man.
duketerm said:
Thanks for doing all of this. I have another question for you since you've told me you had to reinject IMEI... How did you back up your IMEI? I've been looking around but only the basic samsung thing worked for me since I'm already on CM10.
I tried to use this thread: http://forum.xda-developers.com/showthread.php?t=1804117 but I'm unsure how to run that gscript... Thanks for your help man.
Click to expand...
Click to collapse
The thread you listed there confused me also... To use that USSD code you need to be on stock. I will try the gscript thing mentioned and tell you what happens. I also explained below what I did to backup.
Not sure what you mean by basic backup... but i will try explain everything anyway.
Method 1 -
This uses samsung's built-in NVRAM backup/restore function. I won't go into detail, but type in the following in a terminal-
Code:
su
reboot nvbackup
It will then boot into the bootloader, with some text telling you its copying the NVDATA to two partitions - fsg and backup .
to restore, type in
Code:
su
reboot nvrestore
DO NOT use the restore command without backing up first!! DOING SO WILL WIPE YOUR IMEI!!!
More Methods-
Method 2 -
.The devs of SynergyROM developed this - just download at the bottom of this post and flash in recovery.
This will generate some zips in sdcard/SynergyROM/backup. To restore, flash the one that begins with "keybackup".
-
There is a third way, called QPST. I would not use this unless you have balls of steel, and also it requires stock rom. Couldn't find anything about this, so i guess you could google it if interested.
_alp1ne said:
The thread you listed there confused me also... To use that USSD code you need to be on stock. I will try the gscript thing mentioned and tell you what happens. I also explained below what I did to backup.
Not sure what you mean by basic backup... but i will try explain everything anyway.
Method 1 -
This uses samsung's built-in NVRAM backup/restore function. I won't go into detail, but type in the following in a terminal-
Code:
su
reboot nvbackup
It will then boot into the bootloader, with some text telling you its copying the NVDATA to two partitions - fsg and backup .
to restore, type in
Code:
su
reboot nvrestore
DO NOT use the restore command without backing up first!! DOING SO WILL WIPE YOUR IMEI!!!
More Methods-
Method 2 -
.The devs of SynergyROM developed this - just download at the bottom of this post and flash in recovery.
This will generate some zips in sdcard/SynergyROM/backup. To restore, flash the one that begins with "keybackup".
-
There is a third way, called QPST. I would not use this unless you have balls of steel, and also it requires stock rom. Couldn't find anything about this, so i guess you could google it if interested.
Click to expand...
Click to collapse
Yeah, sorry. What I meant, was I used Samsung's backup--was that enough for you? Just worried about flashing another rom. Interestingly from what I read, the new versions of the IMEI format (3?) isn't supposed to cause problems--I guess that was wrong?
Additionally, the SynergyROM didn't work for me because apparently my bootloader is locked? I'm on AT&T and I thought AT&T had unlocked bootloaders?
duketerm said:
Yeah, sorry. What I meant, was I used Samsung's backup--was that enough for you? Just worried about flashing another rom. Interestingly from what I read, the new versions of the IMEI format (3?) isn't supposed to cause problems--I guess that was wrong?
Additionally, the SynergyROM didn't work for me because apparently my bootloader is locked? I'm on AT&T and I thought AT&T had unlocked bootloaders?
Click to expand...
Click to collapse
Samsung's backup was enough for me, but I did the other stuff just to be safe. AT&T's bootloaders do come unlocked, otherwise you wouldn't be on CM10 From the errors it gave me in recovery that im assuming you got also said something about unlocked EFS. The EFS is where the NVItems are located, and it might require an unlocked device, as in you can use any carrier's SIM. I will unlock my GS3 (or atleast try) right now.
I will report back on that later.
EDIT: I need to go to the store right now, so it might be a while.
_alp1ne said:
Samsung's backup was enough for me, but I did the other stuff just to be safe. AT&T's bootloaders do come unlocked, otherwise you wouldn't be on CM10 From the errors it gave me in recovery that im assuming you got also said something about unlocked EFS. The EFS is where the NVItems are located, and it might require an unlocked device, as in you can use any carrier's SIM. I will unlock my GS3 (or atleast try) right now.
I will report back on that later.
EDIT: I need to go to the store right now, so it might be a while.
Click to expand...
Click to collapse
Wait, so were you able to flash SynergyROM? And you did so without unlocking your device?
Thanks!
duketerm said:
Wait, so were you able to flash SynergyROM? And you did so without unlocking your device?
Thanks!
Click to expand...
Click to collapse
Oh dear.
I believe there is some miscommunication
The bootloader has always been unlocked. I'm not talking about the actual ROM (synergyROM), I'm talking about the IMEI backup thing they created.
Now, when I said unlock my phone, I DID NOT mean the bootloader, I meant carrier unlocking it, so I can use any sim from any carrier. I'll try to screenshot it later.
Sorry for the confusion duke.
_alp1ne said:
Oh dear.
I believe there is some miscommunication
The bootloader has always been unlocked. I'm not talking about the actual ROM (synergyROM), I'm talking about the IMEI backup thing they created.
Now, when I said unlock my phone, I DID NOT mean the bootloader, I meant carrier unlocking it, so I can use any sim from any carrier. I'll try to screenshot it later.
Sorry for the confusion duke.
Click to expand...
Click to collapse
Sorry, I think I'm being vague and not specific.
I'm wondering which IMEI back up steps you took. From what you've told me, it appears that you were able to run the Samsung backup, as well as the other ones (including SynergyROM backup?"). If you were able to run the SynergyROM backup, how did you do it? I was unable to run it because I got an error message saying that something was "locked" so I'm not sure how you got around to successfully flashing the SynergyROM.
Thanks for all the help.
...when I constantly keep reading about issues with flashing? I very rarely read about anyone having issues with CWMR, yet I almost never see anyone recommend it over TWRP.
So, why do so many people recommend TWRP when it doesn't appear to be as stable as the alternative?
Fanboyism and user experience. Dealt with so much of this topic on the S2.
Sent from my SGH-M919 using xda app-developers app
HampTheToker said:
...when I constantly keep reading about issues with flashing? I very rarely read about anyone having issues with CWMR, yet I almost never see anyone recommend it over TWRP.
So, why do so many people recommend TWRP when it doesn't appear to be as stable as the alternative?
Click to expand...
Click to collapse
I like it because it is quick, lightning quick. I NEVER had any issue or problem flashing, backing up or restoring with TWRP v2.5.0.2.
HampTheToker said:
...when I constantly keep reading about issues with flashing? I very rarely read about anyone having issues with CWMR, yet I almost never see anyone recommend it over TWRP.
So, why do so many people recommend TWRP when it doesn't appear to be as stable as the alternative?
Click to expand...
Click to collapse
Used it for two years on galaxy nexus, nexus 4 and now the s4 without any issues. Nothing compares to twrp when it comes to ui simplicity and speed. Nandroid back ups have always been reliable and way faster to make and restore. For example, cwm or philz will take about 15 to do a TW nandroid to internal and about 50 to sd card, while twrp takes 6 and 9 minutes respectively. A gpe takes less than four minutes to sd.It's been a no brainer for me for the last two years.
Sent from my SGH-M919 using Tapatalk 2
I still use classic cwm.
laureanop said:
Used it for two years on galaxy nexus, nexus 4 and now the s4 without any issues. Nothing compares to twrp when it comes to ui simplicity and speed. Nandroid back ups have always been reliable and way faster to make and restore. For example, cwm or philz will take about 15 to do a TW nandroid to internal and about 50 to sd card, while twrp takes 6 and 9 minutes respectively. A gpe takes less than four minutes to sd.It's been a no brainer for me for the last two years.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Don't leave 4 ext out of the conversation of all time great recoveries. Sadly, as far as I know, the 4ext team only makes recoveries for HTC devices
Sent from your phone. You should be careful where you leave that thing.
norml said:
I NEVER had any issue or problem flashing, backing up or restoring with TWRP v2.5.0.2.
Click to expand...
Click to collapse
This.
TWRP 2.5.0 had some major bugs which caused the device to hang and soft brick on (all) restarts.
Even just a soft reboot.
So then I tried using CWM.
Which I noticed, doesn't flash a ration of roms (including Darthstalker).
(Not bashin' on you Jovy, love the rom).
After updating to 2.6.0 it got rid of all bugs.
I am now using TWRP again as my main.
So answer to your question.
TWRP is more reliable.
Sent from my SGH-M919 using XDA Premium 4 mobile app
HampTheToker said:
...when I constantly keep reading about issues with flashing? I very rarely read about anyone having issues with CWMR, yet I almost never see anyone recommend it over TWRP.
So, why do so many people recommend TWRP when it doesn't appear to be as stable as the alternative?
Click to expand...
Click to collapse
I agree with you on this. ..I'm no stranger to roms and custom recovery and when I used twrp I got a soft brick, got out of that and continued to try; screen hung and I could not accomplish ANYTHING with twrp. I went with cwm recovery touch and have had ZERO problems. People can talk up twrp all they want but for some of us it just does NOT work. Its not us its twrp itself. Im not a novice and I've had these exact same problems with twrp. I was used to a reliable recovery like 4 ext but on this device that can't be used so I tried twrp. It was a awful expirence for me which was easily remedied by flashing cwm touch. For what ever reason some of us have serious issues with twrp. And its issues are NOT caused by us!!! It does have a serious problems for certain devices for what ever reason. Im happy now using cwm touch. I would have used twrp if it worked properly on my device but it did not...and its NOTHING ive done to cause its malfunction I'm quite certain of that. ..for those who can use it without issues that's great. But some of us can't use it at all. Its nothing but problem after problem. Recovery hanging and its not stable for some of us. And like I said its not related to anything WE did or did not do to cause this behavior.. I'll stick with cwm touch for now because I need a stable recovery. .. I do believe twrp works great for some users but for other users its a nightmare.. if you can successfully use it that's wonderful but some of us can't. .and the problems aren't related to something we've done. ..
Skipjacks said:
Don't leave 4 ext out of the conversation of all time great recoveries. Sadly, as far as I know, the 4ext team only makes recoveries for HTC devices
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
O man. ..I really like 4ext recovery. He says he's working on it, and I truly hope he is. Great recovery.
Sent from my SAMSUNG-SGH-M919 using Tapatalk 4
I have used TWRP 2.5.0.2 for months and didn't have a single insue flashing ROMs, Nandroids, etc..... Fast, easy, great UI, etc.........
......That is until I started flashing ROMs which used Aroma. TWRP then gave me nothing but problems regarding Samsung splash screen freezes, fruitlooping etc. I spent hours and hours troubleshooting these issues, until I realized the issue was with TWRP.
I flashed Philz Touch Recovery a couple of months ago and have had zero issues. Philz does take longer for backups and restores, but I don't mind because I have issue free flashes and restores, which has saved me untold hours of troubleshooting & frustration.
I have had ZERO issues with TWRP 2.5.0.2 and I can tell you that I flash a ton of ROMs...every day. Backups are lightning fast compared to CWM so with TWRP I don't have to decide whether I want to wait 20-30 min to make a backup as they're usually done in about 6 min. I will say that starting from 2.6 and on I have had problems when flashing ROMs but I just went back to 2.5.0.2 and its all peachy again.
Seems to be that some phones don't work well with it..if your phone is one of the ones that plays well with TWRP 2.5.0.2 then I would recommend it because of how much faster backups are made and restored.
I used it up until 2.6 and recommended it to people because of the touch interface and ease of use. The interface started to get really slow in 2.6 and I got annoyed by it so I switched to Philz Custom Recovery (based on CWM) and I love it.