Develop Bugs

[Q] Does being rooted prevent or have anything to do with the metro flash?

Does being rooted prevent or have anything to do with the metro flash?
I ask because Hboot shows S-Off
I cannot unroot.... cannot set user permissions in clockwork. please help...

mexigga said:
Does being rooted prevent or have anything to do with the metro flash?
I ask because Hboot shows S-Off
I cannot unroot.... cannot set user permissions in clockwork. please help...
Click to expand...
Click to collapse
I am pretty sure being rooted will not prevent you from flashing to Metro. If anything, being rooted is necessary. S-off will not have an adverse effect on the flashing to Metro process, either.
Everything you need to know is here:
http://forum.xda-developers.com/showthread.php?t=704161

I got it to root prior to reading this. I will take to M PCS and see if flash is successful (this time around)
thanks.

mexigga said:
I got it to root prior to reading this. I will take to M PCS and see if flash is successful (this time around)
thanks.
Click to expand...
Click to collapse
Wait.......you're taking the Evo to Metro PCS? I don't think they are going to be very helpful seeing as this is not something they condone. What you need (and please read the thread to clarify because I have never personally done this myself but will be doing it soon for a friend of mine) is to have an existing account with Metro so that you can add the info from that account to the Evo and therefore activating on Metro. Unless you know someone that works there and knows what they are doing with this, I don't think you should bother taking it over to them.

Sorry, I should have clarified: I am existing and need to have phone Metro Flashed to get the service. Merely adding the # isn't working as I am on their system already.
I lost the Metro Flash when I screwed up my 1st attempt at rooting.
Here's the problem. Evo is stock & unrooted. People at Metro (right now) are saying that they can't get their computers to read my evo so they are re-downloading drivers, etc. It failed first attempt (today) to metroflash.
I was successful at another corp. store and may need to try where it succeeded.

mexigga said:
Sorry, I should have clarified: I am existing and need to have phone Metro Flashed to get the service. Merely adding the # isn't working as I am on their system already.
I lost the Metro Flash when I screwed up my 1st attempt at rooting.
Here's the problem. Evo is stock & unrooted. People at Metro (right now) are saying that they can't get their computers to read my evo so they are re-downloading drivers, etc. It failed first attempt (today) to metroflash.
I was successful at another corp. store and may need to try where it succeeded.
Click to expand...
Click to collapse
So Metro is helping you flash a phone from another carrier over to them? Talk about customer service! lol

For what it's worth I've never even had to have an EVO rooted to swap its carrier.
Keep in mind though, if you put any AOSP ROM on your phone you will lose the ability to enter ##DIAG# to enter diagnostic mode, and lose the EPST stuff. (For editing settings on the phone, not through QPST/CDMA WS)

If you are flashed to metro or in my case cricket, and you root then you might lose web/mms. Talk and text can be obtained without rooting but web and mms need rooting to run on the proxy work around.

mexiking713 said:
If you are flashed to metro or in my case cricket, and you root then you might lose web/mms. Talk and text can be obtained without rooting but web and mms need rooting to run on the proxy work around.
Click to expand...
Click to collapse
That's where I screwed it up the first go-around. My Evo is good now.

Necrosan said:
For what it's worth I've never even had to have an EVO rooted to swap its carrier.
Keep in mind though, if you put any AOSP ROM on your phone you will lose the ability to enter ##DIAG# to enter diagnostic mode, and lose the EPST stuff. (For editing settings on the phone, not through QPST/CDMA WS)
Click to expand...
Click to collapse
that's the part (AOSP) I didn't realize when I got into android flashing/rooting...
Could've saved me a lot of heartache had I been patient and did more homework on XDA.

Flashing s3 to boost issues

I have had consistent issues flashing this s3 sprint to boost mobile.
My main two questions are where is the general knowledge you guys have about qpst , qpxt, dfs and cdma workshop coming from ?
I mean there are 10 + guides on the sprint s3 to boost BUT all the guides to not explain a thing. Neither do any other guides for other flashes. The are only explicit directions. Which I have followed and consistently get errors no matter the variable that I change ( different roms mainly ).
I have searched the internet from morning to night trying to find answers and it seems this giant ball of knowledge about these programs is either hidden or not there for some odd reason.
Either way I can post up screen shots of the errors if that would help.
Or does someone know 100 % of a current working guide?
Any help will be much appreciated as I agreed to flash a phone after only rooting 4-5 phones and being very knowledgable of that area assuming from all the threads on how to flash phones interpreting them as a "doable" task but this is some deep stuff.

I retract my statement about being able to post screen shots as I do not have the required 10 posts yet. I am not that knowledgeable about quite a few things on this site so looking to learn a lot.
I am assuming I can still send a link to the screenshot via PM for anyone feeling crazy enough to help. :good:

99428813
And now after trying flash a few different roms I am getting a new error in dfs - get sec code cds error. That is after sending what has previously worked as the spc. Does the spc change ? I would presume it doesn't.

This should steer you in the right direction.
http://forum.xda-developers.com/showthread.php?t=2581259

SPrposi Rebecca
retailguy said:
This should steer you in the right direction.
http://forum.xda-developers.com/showthread.php?t=2581259
Click to expand...
Click to collapse
Thank you for the post! I did try that one. My phone at this moment will not let me get passed the put your password/spc in portion of the guide.
I actually purchased the Galaxttoboost.com guide and it worked well on the incognito side but the galaxy side it failed.

Thinkskater said:
Thank you for the post! I did try that one. My phone at this moment will not let me get passed the put your password/spc in portion of the guide.
I actually purchased the Galaxttoboost.com guide and it worked well on the incognito side but the galaxy side it failed.
Click to expand...
Click to collapse
You have to downgrade your rom for the old password to work. I forget how far you have to downgrade, maybe 4.1.1? I don't remember but that is what you have to do. I am also not sure if there are any implications if you have knox in your bootloader. There might be, read up on that.

retailguy said:
You have to downgrade your rom for the old password to work. I forget how far you have to downgrade, maybe 4.1.1? I don't remember but that is what you have to do. I am also not sure if there are any implications if you have knox in your bootloader. There might be, read up on that.
Click to expand...
Click to collapse
LIF_update_FULL_Odex (4.1.1).zip (
Per the galaxytoboost.com guide this is the needed rom to access msl info and is whats currently downloaded. They did specify another rom to use with QXDM that I just noticed. Is that normal?
And I just found out that under baseband version ( where the label for what bootloader I have ) it says unknown.....

Thinkskater said:
LIF_update_FULL_Odex (4.1.1).zip (
Per the galaxytoboost.com guide this is the needed rom to access msl info and is whats currently downloaded. They did specify another rom to use with QXDM that I just noticed. Is that normal?
And I just found out that under baseband version ( where the label for what bootloader I have ) it says unknown.....
Click to expand...
Click to collapse
The new rom yielded the same results. No msl via the get my msl app or no response via getprop ril.MSL in terminal. Same response in QXDM as well. When I put in password and the correct 01f..... password for the 4.1.1 it displays the error - RequestItem - Error response received from target.
What would make my phone completely unresponsive to these programs????

Hard Bricked Phone, long story.

I assume since this is the AT&T Galaxy S 3 section, you already know that I have the SGH-i747 model.
So I've been looking for a while, and I can't find anyone that has caused my same problem the way I did. I'll give the entire story: After having my S3 for a while, I decided to try rooting. I did it successfully, and got CyanogenMod installed. I don't know what, but I wanted to go back to touchwiz. I loaded a backup because it was exactly what I had before CM. fast forward about a month and a half, AT&T keeps bugging me about some update. It's the 4.3 update, I find out, after I installed it. Now, here's the confusing part. The SuperUser app was left over, but I have no CWM and no root privileges. I used this watch?v=yuBuD9aL12o (Paste after yt url) tutorial to root and get SuperSU, and it worked. The phone restarted many times in that entire process, and in the end it worked. One forum told me to install and apk called EZ-Unlock12.apk to unlock my boot loader. (I have included the exact APK if you want to look at it.) It just said successful and I closed out. Now, I wanted to flash CWM again with ODIN. I installed the drivers, and booted up ODIN. This is when it happened. I loaded up the CWM.tar.md5 file into ODIN, (not exact file name but you get what I mean), and it did it's verification and said it was good. I don't remember having my phone plugged in while doing this. I went to shut down my phone and put it in DL/ODIN mode. But now it has happened. I tried to bring my phone back up, but it didn't give ANY feedback. The only possible way to make it do ANYTHING is to plug it in without the battery, and i get the red light. I think it may have been that boot loader unlock program that messed it up, but I can't say for sure.
TL;DR I hardbricked my phone and don't know what went wrong.

Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068

audit13 said:
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I meant SGH-i747, sorry for any confusion.

Did you try the unbricking method I linked? I think that may be the only way to unbrick the phone since it appears that your bootloader has been corrupted. If the unbrick method doesn't work, you'll probably have to have it repair via jtag.

Were you able to get it back to normal state? I am in the same situation as you with the same problem and was wondering if i should go do the method someone provided or just go ahead and pay for a jtag service.

Getting Sprint GS3 on VM help...

Hi all, I've never been to this side of the forums, I'm usually in the AT&T s3 threads. So heres whats going on my cousin has VM and a friend of his gave him a Sprint S3 thinking he could activate on VM since they use the sprint network. Well he found out he couldn't do it directly. but after a quick search on google we found that it could be done. Ive been searching here and google and got a lot of info on the procedure but couldn't find a step by step tutorial. Ive already rooted the S3 and flashed a TWRP recovery, Downloaded Conquest rom for it.
I also have downloaded the CDMA tools DFS tools, how to use it i'm clueless. IS there a video or tutorial on this?
After reading this thread several times :
http://forum.xda-developers.com/showthread.php?t=2060085
The donor phone is a LG optimus V
I know that 4g isnt going to happen, unless he had a 4g donor.
Do I need to root the LG phone to get the MSL info via apk like MYMSL Reader?
Is DIAG mode ##DIAG# from the phone dialer?
What is the samsung password and how do I get it?
Any help will be GREATLY appreciated....

I know the only way you used to be able to get the msl on the optimus v was to use CDMA workshop. Its been years since I have had one, so there might be an easier way now.

pbailey212 said:
I know the only way you used to be able to get the msl on the optimus v was to use CDMA workshop. Its been years since I have had one, so there might be an easier way now.
Click to expand...
Click to collapse
Thanks
I did come across another thread that I didnt find originally This Looks like what I need ONCE I get the MSL and/or whatever from the Optimus V. Back to searching and reading
http://forum.xda-developers.com/showthread.php?t=2270191
and this
http://forum.xda-developers.com/showthread.php?t=991668

Have unlock code, still says invalid sim

hi everybody
Friend of mine gave me this phone with the unlock code.
The phone keeps going to the hands-free activation screen ( which fails of course because it's either got no sim or a T-Mobile SIM in there)
Someone said it said enter double hashtag and then the msl code followed by hashtag
That just takes me to a screen where I can enter the "NAM info" T-Mobile's nearly worthless support told me to put my phone number into both the mdn and msid fields. Obviously this didn't work.
I tried the double hashtags 72786 hashtag to reset the radios, no joy. But before it should no signal at all any of the time where is now it does seem to have a connection to Sprint.
I found other sites that said that I need to enter the UICC unlock code, tapping that option or update PRL or pretty much anything else on that settings screen, just kicks open the hands-free activation screen again, before I did the step above to reset the radio I kept getting a 407 error.
Something that's probably complicating this whole process is that this phone did have a custom ROM on it and still has TWRP on it. The custom rom was wiped and I grabbed the Android 6.0 debloated stock ROM from on here and installed that to get this thing unlocked.
I'm open to trying custom roms but I need one that's going to be as stable as stock.
I would appreciate any help you guys could provide I've wasted probably about six hours on Google already. I got a lot of what appears to be pretty low-level information off of the hands-free activation menu though I've posted those photos.

dosmastr said:
I got a lot of what appears to be pretty low-level information off of the hands-free activation menu though I've posted those photos.
Click to expand...
Click to collapse
Attached
One thing I find curious as you can see in one of the images that says that the Linux version is 4.0.4. But the ROM is definitely a 6.0. I'm an IT guy but I'm pretty novice when it comes to cell phones, is this something to do with the kernal?
I've been trying to download Dr ketan mod but while there's instructions for the p varient, there's no ROM download for the P version of the note 4 on his site.

dosmastr said:
hi everybody
Friend of mine gave me this phone with the unlock code.
.
Click to expand...
Click to collapse
I can't really help you but I can give you some info.
For 1, to unlock it correctly, you should be on stock firmware. You use Odin for that. There are plenty threads here that explain how.
2. Even if you do go stock. I've seen multiple people that can't unlock this phone, even with sprint help. It's like they don't care.
But yes, I've always heard what unlocks the phone is the uicc unlock code. But good luck getting it or getting it to work.
3. I wasted a week trying to figure out unlocking my phone. Not because of $, just wanted to try to figure it out. But i said, F#&k it. And paid Idone apps to unlock mine. Worked flawless!
Good luck!
As far as roms. There are plenty that work great.

aaron74 said:
I can't really help you but I can give you some info.
For 1, to unlock it correctly, you should be on stock firmware. You use Odin for that. There are plenty threads here that explain how.
Looks like I broke the second half for the quote mechanism, sorry when u load up Odin, will it find the stock round that's supposed to be on this phone? Cuz I got what I thought was a closest to it.
The phone still has trwp recovery on it tho, and it knows it's custom.
I got the msl code, seems to work. My fear is that the problem is on the phone and not the carrier end.
How would a non stock ROM impact this process assuming that everything was kosher on the carrier end?
Click to expand...
Click to collapse

dosmastr said:
aaron74 said:
I can't really help you but I can give you some info.
For 1, to unlock it correctly, you should be on stock firmware. You use Odin for that. There are plenty threads here that explain how.
Looks like I broke the second half for the quote mechanism, sorry when u load up Odin, will it find the stock round that's supposed to be on this phone? Cuz I got what I thought was a closest to it.
The phone still has trwp recovery on it tho, and it knows it's custom.
I got the msl code, seems to work. My fear is that the problem is on the phone and not the carrier end.
How would a non stock ROM impact this process assuming that everything was kosher on the carrier end?
Click to expand...
Click to collapse
I don't understand. Does your phone work with service? Did it ever have service? If it had service and now it don't, then you did something.
All i meant. Is if your trying to unlock your phone. It's best from stock.
Click to expand...
Click to collapse