Related
Hey Guys-
Couldnt find a thread similar so I'll start my own.
6 days ago i updated my rom to CM 7.0.3 and the newest version of Savaged Zen Kernel (dont remember version). Everything was fine until leaving work last night and it began to boot loop in my pocket while driving home. Phone had worked as normal all day (web, text, talk), no changes made to phone either. The only thing i can do is get into the bootloader (by holding power and volume up). Although when i try to enter recovery from there to flash a backup, it just puts me back into the boot sequence again. Any help guys?
http://api.viglink.com/api/click?fo...ersonic-v2.3 - xda-developers&txt=PC36IMG.zip
download that rename PC36IMG and put on root of sd card now go into bootloader go into fastboot and it should stay start update press volume up for yes and then when its done put yes it gonna reboot now take out battery put it in evo again and go into bootloader againthen from bootloader go into recovery from there and you should see amon-ra and from there try to do a nandroid or flash a new rom
I got the update to go through, but now when it prompts me for a reboot it just keeps looping. Even when i select no i dont want to reboot and then try and go into recovery, it loops.
try taking out battery for 2 hours and try again
cool will let it rest and let you know the results when I try again.
ar4senal said:
cool will let it rest and let you know the results when I try again.
Click to expand...
Click to collapse
Do you have insurance on your Evo? Is it still within it's 1 year warranty? It sounds like you got the eternal bootloop of death. Is your bootloader S-on or S-off? The condition you're experiencing is unexplained and usually not fixable. running an RUU is your only hope, and if that failed...your pretty much out of luck.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&highlight=boot+looping+no+recovery+access
Yea I'm pretty sure it is still under warranty. I got the phone last August. My bootloader is S-Off. Ill check that thread out.
All you should need to do is wipe and re flash cm7... Our write and re store a back up
Sent by Supersonic!
could be the battery is bad and it is just not getting a constant connection, thus boot looping. i had this issue with a bad battery, swapped it out, no problems
For the record, I mis-spoke...
Sent by Supersonic!
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
First, there are a lot of instances of this happening. Well, not a LOT, but there are several threads about it.
Anyhow, give me a few minutes to upload a file to my mediafire. It's a walk through someone on here wrote that is very detailed and it takes some work, but if everything else fails, it has been known to work.
I'll post the link in a few.
http://www.mediafire.com/download.php?9zc41jsfs7sm1qf
That's it.
You said that you installed the new recovery and still getting loops. That's because you didn't do anything in recovery. Go into recovery and try wiping cache/dalvik cache. See if it boots. If it doesn't go back into recovery go to the wipe menu and wipe everything except SD card and rotate settings. Reflash cm7 and it should work. Loops are a common thing and easy fix
P.s. I don't know if you did this but ill throw it in there anyway. You have to wipe cache and dalvik cache when flashing new kernels.
Sent from my PC36100 using XDA Premium App
ar4senal said:
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
Click to expand...
Click to collapse
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
The issue is that I cannot get into recovery AT ALL. Have tried numerous things. It just wont go into recovery. I bit the bullet and took it into the Sprint Store, they pulled up bootloader and never noticed the S Off at the top. Unfortunately my phone had undergone some sort of water damage. (?) So they were unable to do anything for me, looks like ill be paying the $100 deductible for the refurb.
On a side note the tech at the store told me he has been harvesting parts from evos and epics, and has amassed quite a collection of odds and ends, and that if I ever needed a screen replaced, etc. He would do it under the table for a small charge instead of going through the insurance company. Since i still have the phone ill try all these things again just to see if I can get it working again.
@HipCat- Posted before i read your post....Ill try those steps here in a minute. Thats something I have not tried.
PhxkinMassacre said:
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I cant get into recovery.....
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.
You've probably heard about the Carrier IQ fuster cluck by now and, if you're like me, are up in arms and want it gone if you have it on your phone. I would suggest that you don't use the removal tool yet...
I am rooted using the "stock" method here: http://forum.xda-developers.com/showthread.php?t=1342728 and just downloaded the tool from http://forum.xda-developers.com/showpost.php?p=17612559&postcount=110 to check for CIQ on my phone (it was there) and purchased the license to remove it, which I also did. I then rebooted the phone as instructed but can't get past the SGS2 splash screen.
Can someone please help me... if I have to flash a new rom, fine - I can accept that. I should have been thinking before I did anything but I had only rooted up to this point and didn't have any Nandroid backups or anything and that's my fault. However, I used the internal phone storage or SD as my primary file location and need to access it to grab my files. Is there any way to do this if my phone isn't booting up?
I read another thread (can't seem to find it now I was on my mobile device), where another person did the same exact thing as you and had to ODIN to stock and start from scratch. The phone isn't bricked, but it's not going to boot now.
I'm disappointed because according to Caulkin's ROM CIQ is removed, but I used the tool you are speaking about as well and it states that CIQ still exists. I was going to pay the .99 and have it removed since that tool supposedly works for Samsung devices, but after reading that other thread and now yours - I'll pass.
I'd recommend re-ODIN'ing your phone, not from experience with the issue but just from what I read from the other thread - you aren't going to have much of another option.
EDIT: Here's the link to the thread with your exact questions pretty much and the answers you can expect - http://forum.xda-developers.com/showthread.php?t=1360988
Ugh. Thanks for the reply... this is so annoying. If I go that route, it's going to wipe all of my internal SD memory, too? I've already lost access to the items on my external card because I had that encrypted... but I used my internal for primary storage and have a LOT of items on there of great importance...
Starting from scratch I can deal with - losing all my files I can't.
What package are you on? It works on EG30, but not on EK02. Framework is different.
Worked find on my EG30. Waiting for it to be updated to the EK02 package. Should be around soon.
Not trying to nitpick, but you should always have at least two backups of your internal and external memory. That's at least what I do, usually I backup all my files once a week and do a NANDroid once a week. Saves the headaches from ever happening.
You could try three-fingering to see if you can get into recovery and see what you can do from there, but I don't think you are really going to be able to do much. This method has been tried and proven to soft-brick your phone.
I was going to attempt this method this morning and then did a simple search on XDA and found it had soft-bricked that guys phone I linked you too. That's all it would have taken...
Good luck.
I have some backups, as well as Titanium Media Sync running and Google+ uploading photos, but there are always gaps. Unfortunately I haven't done a 'hard' full drag and drop back up for a couple of weeks, and you can generate a lot of data in that time.
To tell you the truth I'm a little unsure about how or what it takes to have the ability to do a Nandroid backup. I've done plenty of them in the past but what I mean is that since I just did the stock root method I don't know if I needed to install CWM or something like that to get the ability to do a Nandroid. I just haven't had the time to research that fully so I hadn't done one yet.
For what it's worth, the ****storm about the CIQ thing just really exploded in the last 24 hours or less so I didn't think there was anything to look up about the removal tool. I guess I was so distracted about the BS that is Carrier IQ and just wanted it gone, so I ran the tool without thinking there was a database of information on it already. It was my bad.
In the automated rooting thread, you could choose Option C and select a kernel+CWM to install EG30+CWM and EG31+CWM are provided.
update: Fixed. Whew. Thanks for the suggestions, especially, sfhub. Did as you said over in the other thread http://forum.xda-developers.com/showthread.php?t=1342728&page=26 ... will post followups there but basically flashed the stock rom in odin and phone booted back up like nothing ever happened. Well, the only difference really was the media scanner took a considerable time longer than usual on that first clean boot. Thank you so much, again, and see you over in the other thread w/ a few more questions...
dbaybay said:
I read another thread (can't seem to find it now I was on my mobile device), where another person did the same exact thing as you and had to ODIN to stock and start from scratch. The phone isn't bricked, but it's not going to boot now.
Click to expand...
Click to collapse
Unfortunately, that was probably me. I freaked out too but just Odin the stock tar and all is well.....other than now being on E31 and now can't get any ek02 goodness.
Sent from my SGSIIE4GTuvwxyz....should I touch my nose or walk a straight line now?
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.
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