Related
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
crud accidentally posted this in general
locoboi187 said:
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
Click to expand...
Click to collapse
I have been rooted with stock kernel for quite sometime without any los
Sent from my Samsung Galaxy S2
R1ptide said:
I have been rooted with stock kernel for quite sometime without any los
Sent from my Samsung Galaxy S2
Click to expand...
Click to collapse
How man? lmao
locoboi187 said:
So basically Sprint gave me this ticket a week ago to get my phone diagnosed and then replaced. However, the LOS problem only occurs when i root. I have the USB Jig to reset the Odin Count, so I'm wondering if such problems occur only on root should i service it? Has anyone who's been rooted for a week not experienced ONE LOS? Just wondering if its worth the trouble because LOS is not an issue with the phone, just on Sprint's side. I guess some of you got lucky, or what?
Click to expand...
Click to collapse
Just install su+binaries+bb while you've got a root kernel and then flash the pulled stock kernel. If you want CWM there is a CWM+pulled stock kernel too, I haven't tested it yet but I'd imagine it would be just as reliable. I also hear the LOsT kernel is getting fantastic results however if you want an aftermarket performance kernel with extremely reduced LOS occurrence.
Any kernel built off of the released kernel source has this issue...while stock phones have gotten LOS it happens far far less.
It's not the rooted kernels fault...the 'stock build' non-rooted kernels built from the released kernel source also feature this bug. Samsung is giving us the deep dicking on this one. Those bastards should probably release the actual kernel source. This is holding up a lot of progress.
If you're worried about being rooted and taking it into sprint, don't be. We work on rooted phones and it doesn't void your warranty with us.
However, we still haven't received software to flash phones so there's not much they'll be able to do.
Sent from my SPH-D710 using xda premium
daneurysm said:
Just install su+binaries+bb while you've got a root kernel and then flash the pulled stock kernel. If you want CWM there is a CWM+pulled stock kernel too, I haven't tested it yet but I'd imagine it would be just as reliable. I also hear the LOsT kernel is getting fantastic results however if you want an aftermarket performance kernel with extremely reduced LOS occurrence.
Any kernel built off of the released kernel source has this issue...while stock phones have gotten LOS it happens far far less.
It's not the rooted kernels fault...the 'stock build' non-rooted kernels built from the released kernel source also feature this bug. Samsung is giving us the deep dicking on this one. Those bastards should probably release the actual kernel source. This is holding up a lot of progress.
Click to expand...
Click to collapse
I've tried that but no luck. I want to try out viper's ROM i guess. I'm not rooted currently. But what EXACT steps would you like me try? I do full wipes each time, including system and just in case the built in factory format.
squshy 7 said:
If you're worried about being rooted and taking it into sprint, don't be. We work on rooted phones and it doesn't void your warranty with us.
However, we still haven't received software to flash phones so there's not much they'll be able to do.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Oh no I'm not worried about being rooted. I can simply unroot and plug in the jig and im set. What i want is root and no LOS haha
locoboi187 said:
I've tried that but no luck. I want to try out viper's ROM i guess. I'm not rooted currently. But what EXACT steps would you like me try? I do full wipes each time, including system and just in case the built in factory format.
Click to expand...
Click to collapse
First go here:
http://forum.xda-developers.com/showthread.php?t=1282415
Follow the directions to install ODIN, drivers, etc. Also carefully follow the directions for using ODIN. Flash that. It'll nuke everything you have now but you will start back up with a brand new stock rooted install with busybox.
If you want to save what you have now flash a CWM+pulled stock kernel first, do a nandroid backup and then flash that rom in ODIN. then if you want you can re-flash the CWM+pulled stock kernel to restore your data partition if you really want...but...I recommend not. Just start over fresh. It's not that big of a pain...and if it is use Titanium Backup instead.
To stay as-stock-as-possible I recommend just putting that rooted-stock+busybox and sticking with that starting over fresh. I never got an LOS on that. If I seriously **** things up I always revert to that and it works every single time. (sometimes I break my wifi or 4G or both when screwing with custom kernels...damned if I know why, but flashing that fixes it every time).
If you still have LOS issues you are just unlucky, unroot and get a new phone and start over...but I doubt it. I bet that works out wonderful for you.
EDIT: and if that works out for you, and I'm sure it will, then you can start modifying things one at a time...next thing would be the pulled stock kernel+CWM. see how that runs...if that is fine (and it probably will be, I've never tested it though) then flash viper rom with CWM and take it from there. if something gets borked you will know at what step it occured which will make diagnosing the problem much easier...just test thoroughly after each modification.
flash this:
http://forum.xda-developers.com/showthread.php?t=1269437
then flash this:
http://forum.xda-developers.com/showthread.php?t=1305099a
that will leave you with root, CWM5, and stock kernel
daneurysm said:
First go here:
http://forum.xda-developers.com/showthread.php?t=1282415
Follow the directions to install ODIN, drivers, etc. Also carefully follow the directions for using ODIN. Flash that. It'll nuke everything you have now but you will start back up with a brand new stock rooted install with busybox.
If you want to save what you have now flash a CWM+pulled stock kernel first, do a nandroid backup and then flash that rom in ODIN. then if you want you can re-flash the CWM+pulled stock kernel to restore your data partition if you really want...but...I recommend not. Just start over fresh. It's not that big of a pain...and if it is use Titanium Backup instead.
To stay as-stock-as-possible I recommend just putting that rooted-stock+busybox and sticking with that starting over fresh. I never got an LOS on that. If I seriously **** things up I always revert to that and it works every single time. (sometimes I break my wifi or 4G or both when screwing with custom kernels...damned if I know why, but flashing that fixes it every time).
If you still have LOS issues you are just unlucky, unroot and get a new phone and start over...but I doubt it. I bet that works out wonderful for you.
EDIT: and if that works out for you, and I'm sure it will, then you can start modifying things one at a time...next thing would be the pulled stock kernel+CWM. see how that runs...if that is fine (and it probably will be, I've never tested it though) then flash viper rom with CWM and take it from there. if something gets borked you will know at what step it occured which will make diagnosing the problem much easier...just test thoroughly after each modification.
Click to expand...
Click to collapse
It says that it doesn't wipe data. I don't suspect it wipes the system partition either.
R1ptide said:
flash this:
http://forum.xda-developers.com/showthread.php?t=1269437
then flash this:
http://forum.xda-developers.com/showthread.php?t=1305099a
that will leave you with root, CWM5, and stock kernel
Click to expand...
Click to collapse
How has this worked for you?
locoboi187 said:
It says that it doesn't wipe data. I don't suspect it wipes the system partition either.
Click to expand...
Click to collapse
then wipe it, lol. Or not, try it without wiping first. If problems persist the only stuff that is left is in /data has to be the source of problems... but, after you flash that you can flash the pulled stock kern+CWM and nandroid just to be safe.
if after that still no dice, well, it's the phone or a very very very unlucky location...but that theory is still up in the air. (I don't buy it)
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
locoboi187 said:
How has this worked for you?
Click to expand...
Click to collapse
I've also done that too. Worked great for me.
I will report back. I only get LOS when I'm in school. It appears when i go to an area where i get no bars, a circle with a slash will appear. So far so good.
Lol, I just got an LOS on 00001.PRL (alltel/verizon towers) with full bars. I haven't seen an LOS in weeks, I haven't seen it happen with full bars though.
I can confirm for the first time I do not suffer from LOS. I used R1ptide's instructions and all went well. I went to a party where no one ever got signal, so when my bars went empty i received a circle with a slash for a second. HOWEVER, it went back to the bars and didnt stay stuck on that stupid circle.
Everything is definitely good
Sent from my SPH-D710 using xda premium
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.
When last Feb. I finally switched from my iToy to my N7100, I thought that 'flashing' was something that some perv did while wearing a raincoat.
(Hey, I'm pushing 70)
I Finally got my device rooted. I know that it's rooted because while using CF Auto, It wanted me to flash a Triangle Away update, and my binary count went down from 22 to one... so I know at least that worked.
Overjoyed that in Odin, when flashing I first got the notice "Reset!" and then after a few minutes and a restart, I got the "Done" notice (or whatever it said) as I never unplugged from the USB as it says you're supposed to. I just forgot.
Prior to "upgrading" to 4.3 Indian version, I had the stock Rom 4.1.2 running the Perseus Kernel... loved it, but upgrading to 4.3 has turned out to be the worst decision so far.
I still have a lot of Root apps on the phone but they don't work, but as I said, Triangle Away did work.
Should I uninstall the existing ones like Tit. Backup Pro and a few others and re-download them?
Does CF Auto Root automatically install SuperSU? Or should I uninstall that and re-download that too?
One last question....
Assuming that I do have Root, and I'm able to get Titanium Backup Pro working and am able to freeze and/or uninstall the Knox files... What about the ODEX files with Knox.
On this site, I have heard both pieces of advice... Delete and not delete the ODEX'd files.
What is it?
Nobody ever comes up with a definitive answer on this site... it's just a bunch of opinions, usually with the disclaimer, "Worked for me", or something like that... combined with the fact that I really hate working with the Windows partition on my Mac to do the flashing.
Oh, one more thing.
I'd like to go back to the Perseus kernel which somebody mentioned here on XDA.
Are there any kernels for the N7100 that are only useable with 4.1.2 that I should NOT use with 4.3, or does it matter. In other words, would it work with 4.3 as it did with 4.1.2?
Too bad that I don't have somebody like ChainFire living next door. Haha!
I have to thank the XDA site for most of my knowledge since last Feb. when I thought that rooting had something to do with digging up a tree in my front yard.
One more thing (again), I just got an update for Rom Manager Premium and it looks like I can download a CM stable release, which I'm gonna do as soon as I get some of these things ^^^Above answered and ironed out.
I'd like to stick with AOSP as opposed to AOKP but I'll do anything to get away from this current ROM.
Thanks in Advance to anyone who can answer some of these Noob questions.
1-ok i think that you have a custom recovery now, i had these issues a lot on 4.3, if you have custom recovery TWR or CWM you can install any rooted 4.3 rom, but before you do so make sure you backed up your efs folder (VIP you will lose signal if this folder corrubted), after a clean install of any rooted rom, just install ur apps again, if you don't have custom recovery you will need to flash any recovery from Odin, if you can't install recovery from odin so this will be bec. of knox, report back bec. this is another story.
2- some kernels works fine with 4.1.2 or 4.3, and some old ones are only 4.1.2, so make sure that you will flash the right kernel (e.g. devil, AgniPure Stock, ....)
3- don't try to update to CM now, frist make sure that you have a fully working rooted rom with custom recovery install, i also don't recommend flashing roms using any app (rom manager fore example), i think the best flash is the one you do from recovery with clean flash
Just A Follow-Up...
Hey, thanks, evaworld!!!
UPDATE:
I decided to try Root Explorer again (It never worked before to delete anything before this time) and do a search for anything with Knox in it.
I found everything Knox and checked all the boxes except for the ODEX'd files, hit the trash can and wow... it asked for Root privileges. I gave it, and everything was gone in a flash (Pun intended).
Then I tapped on Ti Backup Pro and got the dreaded 'Android device I.D. changed' message so I came back here to XDA and read literally every post on it (Again, opinions are divided) and decided to ignore.
After that, nothing was working for me in Google Play, so I just deleted the data in Google Play Services, Google Play Store, and now I'm waiting for it to take effect in Google Play... whenever I did that in the past, it usually took a couple of hours for it to register. (?)
Now, all of my Rooted apps that I've tried so far are working, but somewhere along the line they pushed Samsung Link on my phone even though I've had Samsung Apps disabled since day one.
The funny thing is that with a Binary Count of 22, I did absolutely nothing differently than this time (Except for an abortive try with Philz_Touch that I don't particularly like the GUI in P_T)... same USB cable, same port, same Windows partition on my Mac, etc. etc. it took this time and I'm pretty overjoyed!
I'll follow evaworld's advice on the ROM... better not throw too much into the mix until I decide that everything is all ironed out.
And, yes, I did click the "Thanks" button for you.
Very good that you have root, but also note that your setup isn't so stable (besides the fact that 4.3 isn't very stable with root apps e.g. I always have problems with titanium and Super and alot of other apps that requires root) , so just clean install a good 4.3 app (I recommend DN3), and after that you are free to do whatever you want (don't forget efs backup in sage place).
Sent from my GT-N7100 using XDA Premium 4 mobile app
I searched and couldn't find an answer to my specific situation but apoligize in advance if this is addressed. I really am new to this so don't want to screw something up.
Basically, if I am rooted with the current stock 4.3, can I take an OTA update? I don't mind losing root.
Background info:
I rooted a while ago, can't specifically but I recall it being a "one-click" method. I checked with root checker from the play store and it says I have root access. If I open SuperSU it tells me KNOX is detected and I know I never removed them so I think it's right. I am running L900VPUBMK4.
I hope 4.4 is released soon, so I'm really just preparing for that day. I need to do a factory reset in the next day or two anyways because my phone is acting up and I have a ton of junk on it anyways so I want a fresh start. I originally rooted to get wifi tethering working but that never worked out for me and I really don't need root at all.
Thanks in advance.
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Elw00d said:
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Can this be moved to QA then?
So did I install a custom recovery to root? Is there a way to check? I've tried several varieties of volume +/- and power to try to boot into recovery but nothing happens.
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
m5james said:
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
Click to expand...
Click to collapse
I looked on my laptop and remember what I used. I used Kingo Android Root to do it. It didn't appear to work because I never got a "success" popup. But when I did a root check it says I have it.
How do I check if I have a custom recovery?
I'm with you M5James - very confusing. Even the "one-click" idiot proof method I used confused me. Different boxes to check that I have no idea as to what they mean.
I've rooted, installed ROM's and kernals, OC'd, custom baked my own ROM's using 7Zip, I tweaked my GF's phone so that she could use it here in the States and then while we were in Dubai as well, etc. Nowadays, when it comes to things like pushing through ADB (I have no clue what that even means, I've just heard it enough that it sticks lol), all the [xxx] before the title of the ROM, kernal, etc and I just become a dear in headlights. Lastnight I tried Googling random things on how to remove root easily and one mentioned using Superuser and just clicking the Unroot Complete icon, which I did. Running random apps says I've removed root, Market doesn't work anymore (I'd upgraded to the Lucky Patcher Market is where I'm guessing the problem is), yet even though I don't have root, I still can't get the OTA to push 4.3 to my phone. I don't even really care about having 4.3 because I'm fine w/ using 4.1.2 at the moment, I'm just sick of the random pushes to my phone asking me to update.
In regards to my Note II with just installing things like custom ROM's, I haven't wanted to do anything wild to it for fear of being like the days of when I had a custom Samsung Epic...worked great OC'd, but could never get battery stats to work right, then the phone would freak out and become laggy, I'd reboot and then suddenly the battery was dead. I just want a simple root, add root-only apps as needed like WiFi Tether, then continue on being a texting whore lol.
If you have rooted your epic and installed custom recovery all this should be pretty simple. All the info is here. Its to the point where rooting and unroofing can be down in probably under 10 mins. You have to read.
Sent from my SPH-L900 using XDA Free mobile app
I read it all, but it's gotten to the point where it's overly technical sometimes. I get lost in jargon, acronyms, I liked it better when there were 5 REALLY good guys making ROM's that worked, not 30 people making their own variations in their basement, then it turns into a pissing match of who's got the latest, fastest, most battery efficient, you've gotta do this to do that, but don't do this if you want that (assuming I know WTF "that" is in the first place) otherwise you'll brick your phone (but you can maybe unbrick it this way), if you swallow this pill you'll get rid of one symptom but you'll get 15 other problems in it's place, etc...then I just say F'it and leave my phone the way it is lol
My wife has the note2, I have the s3 (both rooted, I'm running a custom rom). I think I'm gonna take her back to stock so so she can get the update, then I'll just flash a custom recovery and su zip. It'll give me a chance to clean up her phone.
Edit: thinking of using this
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2