While I was aware that this phone was available for different carriers, I didn't realize there were multiple versions of the phone itself. So when it came out for Sprint (my carrier), I picked one up and left it stock for a few weeks. Eventually I wanted to root my phone so I began searching for simple root how-to's.
I went into this with only minor caution considering I've read so much about these simple rooting methods that "anyone can use".
These are the websites I ended up following for rooting my phone:
(I apologize that I'm a new user and can't officially make hyperlinks)
rumah-android[dot]com/root-samsung-galaxy-s2.html
android-advice[dot]com/2011/how-to-root-samsung-galaxy-s2/
Obviously it says "Samsung Galaxy S2" - but in reality it wasn't referring to our Sprint version of the phone.
So I followed the instructions to the letter, and everything ran with success. There were no errors or anything like that. So I rebooted the phone only to find that my first two buttons at the bottom of the phone were no longer working and I lost all service.
Now this is where I make mistake #2 -- I thought it was a good idea to "factory restore", thinking that I would have to just restart the whole process again - completely forgetting that once you overwrite the kernel you're only restoring what you overwrote.
Thankfully, I can still get into download mode, but where should I go from here?
Let me know if there's any information you guys need.
I'm not sure exactly what you did, but here is how to get it back to stock:
http://forum.xda-developers.com/showthread.php?t=1281287
After that if you still have no service you may have borked your modem/radio. I guess I'm tired because I can't find the thread to restore the stock radio, but its here somewhere. I'll look tomorrow and post it her if someone else hasn't already.
Hmm... You've seem to have done what I had done. You flashed a GSM version when your phone is a CDMA version. So the ROM is looking for a SIM card when the Epic 4G Touch doesn't have, or better yet, doesn't use one.
Here's a link to how-to root for the Epic 4G Touch
http://forum.xda-developers.com/showthread.php?t=1265429
^^ IDK if I can post hyperlinks yet, so yea...
My main reason for the link was so that you can get a ROM on your phone. As a just in case. The ROMs he links you to flash with Odin. I suggest clicking the link in his page instead of searching StarBurst and MidNight since there are the same ROMs on different devices.
If you have your phone working now, then oh. Never mind.
P.S. Just search for Epic 4G Touch and make sure it says that. This'll help prevent that. Also make sure it says "Epic 4G Touch" and NOT "Epic 4G". I almost made that mistake.
eagercrow said:
I'm not sure exactly what you did, but here is how to get it back to stock:
http://forum.xda-developers.com/showthread.php?t=1281287
After that if you still have no service you may have borked your modem/radio. I guess I'm tired because I can't find the thread to restore the stock radio, but its here somewhere. I'll look tomorrow and post it her if someone else hasn't already.
Click to expand...
Click to collapse
In case someone else stumbles upon this thread, I'm just letting you guys know that this did work for getting my device back to normal.
Related
Ok, I know people are going to say to search. I did for hours....
I used the utility at htc-unlockers to try and free up my radio for us sim card use.
Something went wrong and now I am stuck on the red green blue screen and it says serial at the bottom and usb if im connected to usb.
I saw some other threads mentioning this but I have no idea what to do.
Some of the terms didnt make sense to me.
Can someone please give me a step by step what to do?
ok so it looks like everyone is saying i need to 'flash' a 'rom'
how do i do that, and which rom would you advise for a us cellular touch pro 2 needing to work on att and t mobile.
links would be great
I tried each of these except the verizon
http://forum.xda-developers.com/showthread.php?t=578659
and i got an error 290, couldnt be used on my device
Those are Radio ROMs. You need CDMA roms. Basically there are a couple steps you need to perform first.
I would suggest reading the following thread:
http://www.mobileunderground.info/showthread.php?t=3407&page=1
I did buy the thing from htc-unlock and i think I did it wrong because now I have that boot screen issue.
its a us cellular touch pro 2 win 6.5
can someone link me to the rom I need to get it back running?
ok i fixed it. i can post a walkthrough for idiots.
It would involve links to other sites, so i need an ok from a mod or whatever because i know how pissy these forums can be.
I know there's been multiple threads on this topic but I can't figure out how to solve it after reading each one. Here's my story. I rooted it and then flashed CM10 via cwm recovery and everything was working fine. One day later without doing anything my 4g started slowing down and eventually I can't get anything but edge. I looked around xda and found out that i might be missing my IMEI. Sure enough my IMEI was a 0. I tried recovering to a back up but that didn't fix it so I injected it back in via Peoplearmy's method. The IMEI is now in place but I still wasn't getting anything but edge. I tried using odin to flash it back to stock which worked but I still wasn't getting anything but edge. Does anyone know what I need to do to fix this? I have contacted Peoplearmy but he hasn't replied yet and i need this fixed asap so it would be great if someone could help me out. This is the T-mobile version of the s3. If you need any more information please ask. Thanks. I would post this in another place but I don't have enough posts. Relatively new here.
After the Rooting procedure failed (for some reason), my phone just went popped up with an error "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
EDITS:
Progress 1: Got into the download mode but I cant seem to find the firmware appropriate for it:
SGH-1747M
Baseband: 1747MVLLH1
Progress 2: After scouring the internet I have found SGH-1747M
The problem is its 1747MVLALH1
Rather than 1747MVLLH1
Not quite sure at the moment if this is the right firmware for my phone
Advice would be appreciated
I'm sorry, can you be more clear? Can you not use the phone at all? Also, what method of root did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If you are able to get into download mode then you are good to go, it just sounds like whatever you were flashing was either incomplete or was interrupted, otherwise referred to as a bad flash. Mosy on over to this thread, http://forum.xda-developers.com/showthread.php?t=1739426 , read it through...maybe even twice and flash the stock rom with root. Once this is working you can proceed to installing a custom recovery. The easiest way ti do this is install Clockwork Rom Manager from the market and install ClockWorkMod Recovery. Once you have a recovery (and before you flash anything from here on for that matter) make a backup, this will give you a fall back in case of future bad flashes. Let us know how it goes.
You guys could say that I "bad flash"-ed it
I did rooting before with my S2 and it had no problem but when I flashed the S3 it said that it failed and thats when this problem arose
Anyway is I747MVLALH1 the same as I747MVLLH1 (my baseband)
I'm not sure what 'rooting procedure' you used as you didn't specify, but if you use the guide i linked in my previous post and follow the directions exactly you should be ok and chalk this up as a lesson learned.
dntesinfrno said:
I'm not sure what 'rooting procedure' you used as you didn't specify, but if you use the guide i linked in my previous post and follow the directions exactly you should be ok and chalk this up as a lesson learned.
Click to expand...
Click to collapse
Its the one made by chainfire and I probably got the wrong guide thats why it went like that
I'll try your guide hopefully it works
cant post links at the moment
Thank you sir, I'll probably try the clockwork mod when its confirmed working for Rogers users
It's entirely possible with all the different variations of the GS3, which is why i emphasized you read everything very carefully first, and follow each direction exactly. If something doesn't go as it is supposed then there is a reason, 'i'll just skip that step' rarely works :cyclops:. Let me know how it goes.
dntesinfrno said:
It's entirely possible with all the different variations of the GS3, which is why i emphasized you read everything very carefully first, and follow each direction exactly. If something doesn't go as it is supposed then there is a reason, 'i'll just skip that step' rarely works :cyclops:. Let me know how it goes.
Click to expand...
Click to collapse
It worked great
you literally saved my bum from spending 600 bucks - I appreciate it
for now Im just gonna leave it at that (stock and rooted) since you did mention in the Third step that your not quite sure if it works for Rogers users as well (clockwork etc..)
gek00 said:
It worked great
you literally saved my bum from spending 600 bucks - I appreciate it
for now Im just gonna leave it at that (stock and rooted) since you did mention in the Third step that your not quite sure if it works for Rogers users as well (clockwork etc..)
Click to expand...
Click to collapse
I believe you may have just misunderstood me, but yes CWM will work with Rogers based phones although not being a Rogers user myself i cannot offer any insight to any do's or don't specific to that carrier, if there are any. In any case, i'm glad you got your phone working, i've been in that position a few times myself.
dntesinfrno said:
I believe you may have just misunderstood me, but yes CWM will work with Rogers based phones although not being a Rogers user myself i cannot offer any insight to any do's or don't specific to that carrier, if there are any. In any case, i'm glad you got your phone working, i've been in that position a few times myself.
Click to expand...
Click to collapse
Oh yes, I apologize for that I might try it later on but one last question (if its not too much of a bother)
Would you mind giving me advice on what ROM is a "go-to" at the moment for the S3
Thanks in advance
The short answer to that question is no, as it is really a personal preference as well as device dependent, meaning the same ROM may or may not run the same way on two seemingly identical phones for any number of reasons. Personally I use the JB AOKP, which is also what i used to run on my GS2 , a lot of people seem to like Cyanogenmod as well. The only way to know is flash them and find out if you like them. Just always make sure to have a recovery backup handy in case you dont like it, or if anything goes wrong during the flash. Like i said before, the important thing is to read everything in the post carefully and follow the directions .
I attempted to root my Galaxy S3 (SCH-530M) From Metro PCS. I used odin and follow instructions carefully. I have rooted other phones this is my first problem I have ever stumbled upon this problem. I used a toolkit which allowed me to ROOT my phone but now I only get "Galaxy S3" logo and then screen turns black. I can boot into "safe mode" it shows clear cache, factory reset, ect.
I tried to follow instructions here:http://forum.xda-developers.com/showthread.php?t=2219755
Here are errors I received:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"Secure Check Fail" Sbl1 message. shows on my phone.
I am little frustrated been at this since 10am it is now 5PM. I can boot into recovery mode, phone turns on starts and everything but it stays on black screen and my led on top left side flashes bright blue.
Any info is a major thank you. I wish I can here to contribute but sadly I am in this bind.....I attached a screenshot from my desktop to show you guys what errors say.
The first thing you need to know is not all S3's are the same. Never flash anything not for your model phone.
The second is yours is an older metro model from when they were tied to Sprint I think it was. What this means is that it's a variant of Sprints model, and so you will be better off using their forum for future flashes and help. Do not flash anything you find here. They are not compatible.
Third is I don't recommend the toolkit. It's usually out of date and while it was helpful to some in the beginning, it now seems to cause more problems than anything. If you want root, search for root66 firmware in the Sprint forum. He may have your version there as well.
Finally, I didn't read the thread you linked, but 95% of the time, a factory reset will solve the hanging at boot.
I also highly recommend reading the stickies threads. Lots of great info you should know about and there are several methods to gain root.
For the Odin problem. Makes sure kies is NOT installed, try different cables and different usb ports.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
The first thing you need to know is not all S3's are the same. Never flash anything not for your model phone.
The second is yours is an older metro model from when they were tied to Sprint I think it was. What this means is that it's a variant of Sprints model, and so you will be better off using their forum for future flashes and help. Do not flash anything you find here. They are not compatible.
Third is I don't recommend the toolkit. It's usually out of date and while it was helpful to some in the beginning, it now seems to cause more problems than anything. If you want root, search for root66 firmware in the Sprint forum. He may have your version there as well.
Finally, I didn't read the thread you linked, but 95% of the time, a factory reset will solve the hanging at boot.
I also highly recommend reading the stickies threads. Lots of great info you should know about and there are several methods to gain root.
For the Odin problem. Makes sure kies is NOT installed, try different cables and different usb ports.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for advice but I think you missed a few things I pointed out. I am using a Metro PCS S3 the model you linked me too for root66 .tar is for Verizon S3 not Metro PCS. Verizon is i535 and mines is R530M would that also mess up my phone even more? I HAVE tried factory reset and cache wipe. Nothing is working phone stays stuck on black screen AFTER boot logo.
I went o sprint forums they told me my phone is NOT the same as theirs. I am aware of various S3 models it was many said to use ODIN and it caused me a world of problems right now.
Vepar_S said:
Thanks for advice but I think you missed a few things I pointed out. I am using a Metro PCS S3 the model you linked me too for root66 .tar is for Verizon S3 not Metro PCS. Verizon is i535 and mines is R530M would that also mess up my phone even more? I HAVE tried factory reset and cache wipe. Nothing is working phone stays stuck on black screen AFTER boot logo.
I went o sprint forums they told me my phone is NOT the same as theirs. I am aware of various S3 models it was many said to use ODIN and it caused me a world of problems right now.
Click to expand...
Click to collapse
I couldn't be sure if mrRobinson had made the root66 firmware for your model or not. If he did it would've most likely been in Sprints or maybe Verizon's root66 threads. All I meant was for you to check their threads to see if your variant was there. In ours, for example, there is also the T999V firmware, which is related to our T999, but is different.
What I am fairly sure of is your model is a CDMA device, like Sprints and Verizon's. T-Mobile and AT&T are GSM. When T-Mobile bought metro they stopped offering the R530, and replaced it with the T999N. Prior to this several people asked me for help with their R530M, and the best I could do was direct them to Sprints forum where others had posted about that model.
I suggested going there because there are people with the same model and they may have run into similar issues. And even if they haven't the rest of the info in that forum would be more relevant to your device than what you find here.
I'm not sure why you are having trouble with Odin. I've seen in other models forums where sometimes you may need something more, or something different than just the stock firmware. I don't know if that could help you or not, so I'm just trying to get you pointed in the direction where you might find someone who can.
There are some issues that are universal with things like Odin, but usually it ends up being a problem with the computer, the usb cable, bad/corrupted downloads, etc. Which is why I mentioned those. But you mentioned an error that showed on your phone, an sbl1 secure boot error or something like that. To my knowledge none of the GSM devices have ever shown this. Not that I remember anyway. But it may have something to do with a locked boot loader like Verizons, or it could be something entirely different. But again, you'd likely have better luck finding similar problems in the others forums.
If you can verify some roms that will work on yours, you may consider flashing CWM or TWRP using Odin. Then try flashing the Rom from recovery, factory reset and reboot. May not help, but it's something to try. Also, make sure you downloaded the latest firmware for your model and try it again.
If I get a chance I'll try to help find out more for you. But for now I hope that helps clarify what I was saying before and helps get you pointed in the right direction.
This would be a bit of a long shot, but you could go to your local store and see if they will offer some sort of trade for the T999N. (Doubtful, but it can't hurt to ask) Now that metro is with T-Mobile, you're likely to get better service with it, unless they've got something worked out where devices like yours can still use Sprint towers/networks.
Sent from my SCH-I535 using Tapatalk 4
Hey guys, this is my first HTC device. I've been reading through the threads here and in the intl forum and I just wanted to get a little info in one place as to what we can flash for this device. I sent mine off to someone with a Java Card, so now that I'm good to go, I wanted to see what all I (and other VZW users) can do at this early stage in the game. I know that until there is an easier way to S-Off/root/etc than sending your device to someone it is still kinda rocky as to development on this particular device, but I've heard mixed reviews on what ROMs/kernels are good to flash.
I assume that as long as I've got a custom recovery, flashing ROMs on this device would be the same as the other devices I've used... just pick the file in TWRP and flash, right?
As far as ROMs go, I've read that ViperOne works, along with InsertCoin with nothing extra.. just flash and go apparently. As for other ROMs, a little editing and some files from the stock VZW ROM should make them work, right? What files exactly would be needed?
Basically, if you've flashed anything, post your results here. What works, what doesn't, anything I should do before I start flashing myself. Any good threads I should read before I jump in. Thanks guys!
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
jtommyj said:
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
Click to expand...
Click to collapse
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
lordcheeto03 said:
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
Click to expand...
Click to collapse
Well first thing you need to have a custom recovery flashed.
Then you would need to backup your stock system. If you are in a soft brick then volume up and power being held at the same time should get you out of it.
There should not be a need to refresh firmware since the original firmware is all we have. I do believe an Ruu is being worked on currently.
Final word- if you're unsure,don't!!