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.
Related
Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!
Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!
Thanks Already started doing that waiting for it to download now
Still no touchwiz... great!
Try flashing a stock rom via clockworkmod.
efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha
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
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
MTSL_Mantra said:
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
Click to expand...
Click to collapse
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Mr. Struck said:
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Click to expand...
Click to collapse
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
MTSL_Mantra said:
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
Click to expand...
Click to collapse
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Mr. Struck said:
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Click to expand...
Click to collapse
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
MTSL_Mantra said:
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
Click to expand...
Click to collapse
Did you install Philz as well or are you still using CWM?
Mr. Struck said:
Did you install Philz as well or are you still using CWM?
Click to expand...
Click to collapse
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
MTSL_Mantra said:
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
Click to expand...
Click to collapse
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal. All I can say is that, in my opinion, Philz is far superior, I would say give it another shot.
Sent from my SPH-L710 using Tapatalk
Mr. Struck said:
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I misspoke, I meant sdcard1 (or ext_sdcard or however the other recoveries reference it). None of them have been able to do it with their respective names. But that's (possibly) another issue, I just mean that's why I'm not positive switching would help. I could definitely be wrong though, I can try it if nothing else next time I get to a computer with Odin send it over.
There is a flashable zip as well just FYI. As to your backup location issues, I don't know what to tell you, I've never experienced that problem.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
Also, I know some users have had better luck renaming one of the bootloader assert lines to match the MK3 boot loader instead of deleting all the lines.
Sent from my SPH-L710 using Tapatalk
Maybe I'll try philz out then but if not I'm stumped.. I know it sholdn't be this difficult to do this crap, I'm glad that I'm learning some of the pitfalls, but some of these pitfalls don't seem like things other people have been encountering so I don't know what the deal is.
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
dokgu said:
Hello everyone,
I really need your help with my wife's Metro PCS Samsung GS4 M919N.
The thing is, we are now living outside the US so I had to unlock her phone. After ordering the unlock codes, I decided to root the phone and use a custom ROM while waiting for the codes.
That is why I found this guide here: androidforums.com/metropcs-galaxy-s4-all-things-root/790899-metropcs-galaxy-s4-all-things-root-guide.html
So while reading the guide, I aimed to have the following accomplished at the end:
Recovery: TWRP
Custom ROM: CyanogenMod 10.2.1
I then started doing the guide for the TWRP recovery by using Odin. I got the message saying that the flashing passed and went ahead to restart to recovery to install CM 10.2.1 as a custom ROM. The thing is that I keep on restarting to the stock recovery not TWRP. So I went to YouTube and found a video showing how to flash TWRP using GooManager. After following that guide, I went to restart to recovery and I successfully got into TWRP.
Now, to achieve my goal, all that's left to do is to flash CyanogenMod 10.2.1 (jfltetmo).
Before doing that, I decided to make a backup. After using TWRP to do a backup, I proceeded to installing the custom ROM + gapps (wiped with the default settings). Everything was working I think (I handed the phone to my wife so she was he one testing it). After some time, she decided she wants the stock ROM instead so I decided to download the androidforums.com/metropcs-galaxy-s4-all-things-root/783769-rom-recovery-flash-able-stock-m919nuvuamf2-rooted-deodexed-rom.html ROM.
I flashed the newly downloaded ROM + gapps (same file). This time, I couldn't get the gapps to work probably because it was meant for another version. So I decided to just restore from the backup I created earlier.
So, the usual stuff. Wipe. Restore. Restart.
Seems to be going smoothly because my wife was happy to see the old ROM she was used to.
Until the phone started to restart on it's own. (It's pretty much downhill from here on out).
At first I thought it was just a random thing that probably would never happen again. I was wrong as it became more frequent as days went by.
Recently I can't just restart the phone, I would have to remove the battery and then restart it. Now, it's getting really hard to restart the phone. Please help me fix this. I prefer to leave the phone rooted, but if the fix unroots the phone then so be it, anyway my wife prefers the stock ROM so only the unlocking was necessary.
Metro PCS Samsung Galaxy S4 M919N
Recovery:
TWRP 2.6.3.1
ROMs:
Stock Metro PCS
CyanogenMod 10.2.1
Let me know if you need more information from me. Hopefully I can restart the phone so I can give you some version numbers.
Thanks everyone!
Click to expand...
Click to collapse
I agree with Elesbb. If the goal is jus tto get back to stock, just do an odin flash of the stock ROM. Be advised if you flash the latest Kit Kay update you will nto be able to go back to Jelly Bean. From your post it seems like you are partial to Jelly Bean. So if that's what you want, but sure you use the stock 4.3 ROM. You can find it around here on XDA somewhere with a quick search to make sure you have the right one.
As Elesbb said, you won't loose the 'sim unlock'. But you will lose root. However you can root the stock ROM just fine.
You might also consider one of the myriad of TouchWiz based custom ROMs. They are look just like TouchWiz that your wife wants, but have a lot of optimizations and options in them. Those should flash just like any ROM. If you still get the reboot issue then do the Odin back to stock, reroot, then flash the custom TW roms.
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Thread cleaned.
Rather than bashing a ROM or user let's keep on topic and help the OP resolved the problems he's having. Arguing over the virtues of a ROM doesn't help anyone.
Thank you,
Rwilco12
Before posting this thread I sent the aforementioned guide's poster (arocker). He sent me a reply saying not to use gapps as the stock ROM for Metro PCS already comes with Google apps. I'll try his suggestion first and see if the phone still reboots a lot.
If the problem persists, I will try the solutions mentioned here. Thanks a lot!
elesbb said:
I didn't read everything but just wanted to say
VERY GOOD THREAD!
this is how threads should be done. Very descriptive, organized, told us everything you did and asked for help! Good job man! Only negative is it prolly should have gone in Q&A section but irregardless very good thread!
About your issue, I recommend flashing stock Odin tar file to everything back to stock and reroot and start over. Flashing stock will not lock it again it will remain unlocked. But should get you back up and fresh. Just be aware it will erase all your data and all of the internal SD card.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
dokgu said:
After trying arocker's suggestion to not flash gapps, the phone still reboots. So now, I am going to try your solution guys.
But before I do, I want to make sure that I am on the correct paths/links.
Here's what I found for the following:
ODIN
forum.xda-developers.com/galaxy-s3/themes-apps/27-08-2013-odin-3-09-odin-1-85-versions-t2189539
I've had a couple of chances to use ODIN but only using specific functions like flashing a recovery file while the phone is in download mode. I don't however have any experience using ODIN to put the phone back to stock where the phone gets unrooted. Having the phone unrooted is fine by me as I only needed to have the phone unlocked.
Any step-by-step guides for using ODIN for this specific purpose guys? I don't want to mess this up again.
Thanks and sorry for the trouble.
Click to expand...
Click to collapse
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Hello PanchoPlanet,
Thanks for the link. I went ahead and tried to unroot without Windows (Mobile Odin) as per the instructions on the link. I downloaded everything and went ahead to install the Mobile Odin APK. When I ran it to install the Flash Kernel, the app told me that the device is not supported.
To my understanding the guide is for M919 devices but should work for my wife's device as well (M919N - Metro PCS). I would like to try the guide for using Windows but I'm not really expecting for it to work or I might mess it up more. I'll try to search some more and provide the links where this forum will lead me to. But if you have any ideas, please let me know asap. Thanks!
PanchoPlanet said:
No trouble at all, check out the stickies in the beginning of threads.
Look for guides similar to this.
http://forum.xda-developers.com/showthread.php?t=2335109
Pp. Good luck.
sent from my bluetooth controlled toaster.
Click to expand...
Click to collapse
Ok, here's what I found:
forum.xda-developers.com/showthread.php?t=2446497
It seems like the perfect thread for what I am trying to achieve. Will let you guys know if it is successful. But it will have to wait for tomorrow. Gonna catch some sleep.
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
This thread talks about battery stuff and reboots:
http://au.ibtimes.com/articles/530338/20131216/samsung-galaxy-s4-problems.htm
Batteries can go bad a lot of ways. Extreme temperature, factory defect, phone drops, moisture, etc.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And 100% of the time, they eventually just get old.
dokgu said:
Okay, I'm running out of options. I was able to flash the stock ROM using Odin 3.07. The recovery looks like it came back to the stock recovery as I no longer have TWRP installed. When I install Root Checker, I see that I am no longer rooted. That's good.
But my original problem is still here. The phone reboots a lot. The phone is so unstable that it is barely usable.
I am now going to try one more thing.
I have a Galaxy S4 (I337M) from Rogers Canada (my wife has Metro PCS M919N). Mine got rooted and has CyanogenMod 10.2.1 as a custom ROM. My phone is working perfectly while hers reboots a lot. I was thinking it was because of a faulty battery. So I am doing an experiment by swapping the batteries. So far no reboots have occurred, but I will continue to monitor this.
Any ideas why the battery is kinda messed up?
Click to expand...
Click to collapse
That's a wierd situation, by swapping batteries you basically performed a battery pull, which acts as a reset, that in it self may have cleared your issue.
Now if battery is bad that could be an unusual problem. Maybe just replacing the battery will be the end of your mystery.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
The batteries are all the same. Don't worry about that.
Even if its a new battery if could have just been bad. A manufacturing defect perhaps.
Sent from your phone. You should be more careful where you leave that thing.
dokgu said:
The battery should be brand new as the phone was just recently purchased this April.
Anyways, so far no reboots have happened and any instability has not been shown at all. Everything looks ok, yet.
Anyone know if it is safe to swap batteries? Our phones have different S4 models. I'm not sure what the implications would be. Also what is this battery pull which acts as a reset? We've been pulling the battery a lot of times but the reboot still happens but not when we swapped batteries.
Click to expand...
Click to collapse
This battery thing is wacky, anyway swapping batteries should not be a problem, it's just an energy storage container. Pulling the battery isn't like powering down the phone or resetting/rebooting ,sometimes devs request a battery pull to get the proper wipe effect that reboots can't provide.
You inadvertently solved your problem by accident. That's a good thing.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
PanchoPlanet said:
You inadvertently solved your problem by accident. That's a good thing.
Click to expand...
Click to collapse
I have quite literally solved the vast majority of my problems this way.
Its a preferred method.
Sent from your phone. You should be more careful where you leave that thing.
Sometimes it's that "total disconnect "of power that kind of gets all the ducks lined up in a row and everything flows in the dynaflow.
Good.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
its very important topics and it might seen for every galaxy s4 users.just wonderful topics.
This exact same thing happened on my mother's 6-month old S3. If you're still wondering, you could try putting the old battery and running a CPU stress test app. It should increase the current draw and trigger a shutdown.
EDIT: whoops, sorry to kind of zombie. Didn't check the date.
Sent from my Galaxy S4
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