Database Info

IMEI issue

Hey guys,
Did some searching but couldnt find anything about my specific problem. Recently installed a couple new ROMs and when I was backing up and restoring between them (with CWM) I somehow lost my IMEI and it was showing as B000000000. I made the mistake (you learn the hard way I guess!) of not backing up my IMEI beforehand, but my first question is how could it get lost by performing CWM backup/restores? Improper data/cache wiping?
I came across the IMEI repair writeup using QPST to manually write a new NV and that seemed to work. However when I rebooted, the IMEI was one number short (ie- my IMEI is 15 numbers and the phone was displaying the first 14 but cutting off the last number) and I still have no service, and I'm not roaming. My second question is, does anyone have any ideas where to go from here??
Thanks!
Mike

Are you sure you followed everything in this post ?
http://forum.xda-developers.com/showthread.php?t=1867442
There is stuff in the last pages about downgrading your phones radio if there is issues. I don't really know because I haven't had this issue and had backed up all my stuff before messing with my phone. Either way questions about that issue should be asked in there.
Good luck!

Please read forum rules before posting
Questions go in Q&A
Thank you for your cooperation
Friendly Neighborhood Moderator

Thanks for moving the thread, sorry about the misplacement. Mercuie - I tried the method you linked me to and ran into an issue with the software. When I plug my phone in, my computer's dev manager sees it on port COM14, and when I run the software there is an option in the dropdown menu to select COM14, but it is unable to connect. The ERI status just sits there trying to connect and if I click anything else in the GUI it crashes the program. A reboot of my phone and computer doesn't help. I have MS Vista with .NET 3.5 installed, but not sure if I have the right diagnostic drivers...
edit: tried using the samsung MEID repair tool again and this time when i try to connect to COM14 a red ! comes up and says "In user or invalid port". Not sure why since device manager is definitely still showing my phone as COM14, but it's not crashing anymore

I think my issue is resolved guys =) The QPST injection worked, I just needed to wait long enough for it to reestablish connection on Verizon's network. Thanks!

just kidding! I jumped the gun with my previous post. My mobile data was restored for about 10 minutes then it was lost again. Not really sure what's going on here and why i have intermittent connection. My IMEI in Setting>About Device>Status is correct.

Probably need to reprovision your phone/sim card.
I don't have the key sequence handy ... do a search in these forums for reprovision.
Edit: Enter *2767*3855# into your dialer. This will factory reset your phone, which includes wiping your internal sd.
Sent from my SCH-I535 using xda premium

thanks for the reply. I backed up everything including my internal sd card onto my external card and ran the reprovision sequence. The phone reset, but everything in /mnt/sdcard is still there and I still do not have service. IMEI/MEID seem to still be intact as well my phone number, but Network is Unknown, Mobile network state is disconnected, ERI version is none, and IP address is unavailable. Thoughts??
Edit: tried the reprovision a second time and now I'm Roaming

Bump.. anything guys n gals?
Sent from my SCH-I535 using xda app-developers app

Don't know if this will help, but try removing your sim card and rebooting phone. Shut down phone, reinsert card, reboot and see what happens.
If still no service, reprovision again.
Edit: If you are roaming, you have service. The roaming prompt is a persistent problem with imei restoration that I don't think has been solved yet.
Sent from my SCH-I535 using xda premium

Have you tried to reprovision since getting it fixed? Also, the tool that is linked that you tried and didn't have any luck with is suppose to fix your problem. I haven't tried it but others have had success with the same problem that you are having.
Sent from my SCH-I535 using xda premium

pdinphx said:
Don't know if this will help, but try removing your sim card and rebooting phone. Shut down phone, reinsert card, reboot and see what happens.
If still no service, reprovision again.
Edit: If you are roaming, you have service. The roaming prompt is a persistent problem with imei restoration that I don't think has been solved yet.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
No luck. I removed the SIM, rebooted and it had nothing, then powered down, reinserted the SIM, and rebooted and still roaming. Also tried another reprovision and same result. I know I technically still have service since I can make/receive calls, but I have nothing in the way of mobile data and don't want to turn roaming data on for fear of extra charges. Is it worth brining to Verizon at this point to see if they can do anything? I mean I don't really see them doing much beyond factory reset and playing with the SIM card, which I've already done.
@HHF2:
Yes I reprovisioned multiple times after restoring my IMEI with no luck. The QPST tool worked to restore my IMEI. I saw the Samsung repair tool had an option for ERI repair I believe, but I was never able to get it to connect to my phone via COM port without crashing.

I would try a different computer if you have installed all of the correct drivers for the computer that you are using.
Sent from my SCH-I535 using xda premium

pdinphx said:
Edit: If you are roaming, you have service. The roaming prompt is a persistent problem with imei restoration that I don't think has been solved yet.
Click to expand...
Click to collapse
Not true. This tool will repair an injection and get rid of roaming.
http://forum.xda-developers.com/showthread.php?t=1867442

Thanks guys - I will try that tool again from a different computer when I get home from work.

apacseven said:
Not true. This tool will repair an injection and get rid of roaming.
http://forum.xda-developers.com/showthread.php?t=1867442
Click to expand...
Click to collapse
Think he already tried this ... there is still no guaranteed way to fix this problem.
Most people have resolved it by getting replacement phones ...
Sent from my SCH-I535 using xda premium

No luck from a different computer. No luck with a replacement SIM card i got from Verizon. A member in another thread posted about how he was in the same situation and was able to flash a downgraded modem and get the Samsung repair tool to repair his ERI, then flash the new modem again. I will try that route next. If still nothing then I'll probably have to Odin back to stock and see if that fixes it and if not then lobby for a new phone :\

pdinphx said:
Think he already tried this ... there is still no guaranteed way to fix this problem.
Most people have resolved it by getting replacement phones ...
Click to expand...
Click to collapse
I've encountered a number of people (myself included) who have used this tool (which was made specifically to repair roaming status, mind you), to repair the roaming issue after an IMEI injection. So yes, there is a guaranteed way to fix the roaming issue. No point in getting a replacement handset.
OP: I was able to get the connection for ERI repair after downgrading my modem too, so I definitely recommend trying that. If you can get that to connect, you should be back in business.

apacseven said:
I've encountered a number of people (myself included) who have used this tool (which was made specifically to repair roaming status, mind you), to repair the roaming issue after an IMEI injection. So yes, there is a guaranteed way to fix the roaming issue. No point in getting a replacement handset.
OP: I was able to get the connection for ERI repair after downgrading my modem too, so I definitely recommend trying that. If you can get that to connect, you should be back in business.
Click to expand...
Click to collapse
Glad to hear! So before I do anything just wanted to verify... How did you go about flashing the downgraded modem? Just placing it in the root of your external sd card, rebooting into [CWM] recovery, doing a data/cache wipe/factory reset, and installing from zip (VRLF2)? Then run the Samsung repair tool and once (hopefully) data is restored, do the same thing to flash the latest modem (VRLHE)? My next step was to Odin back to stock but I'd like to try this method first since it seems to have worked for you.

apacseven said:
I've encountered a number of people (myself included) who have used this tool (which was made specifically to repair roaming status, mind you), to repair the roaming issue after an IMEI injection. So yes, there is a guaranteed way to fix the roaming issue. No point in getting a replacement handset.
Click to expand...
Click to collapse
Good for you.
Unfortunately, not everyone has had the same luck.
Hope the OP has the same fortune as you.
Edit: This sounded unnecessarily dickish. I hope this works for the OP ... I do know owners for whom this did not, for whatever reason, work.
Sent from my SCH-I535 using xda premium

Help! MiUI raped me

Please, I desperately need some help. I flashed the dreaded MiUI ROM to my Samsung Galaxy S3 (Verizon), and upon reboot, noticed immediately that my IMEI was gone. This is my fault because I had no backup. So I proceeded to take the IMEI off the phone itself (under the battery compartment) and flashed it back on the phone via that one tool (if you need to know specifically what tool I'm talking about, I will look it up). Now, my IMEI shows restored, the phone CLAIMS to be activated and I have function 4G LTE data access, however, when I place a phone call, I get the message 'Mobile Network Not Available'. I cannot get it to place phone calls. In my About screen, the following information is present:
Model Number
SCH-I535
Android version
4.0.4
Baseband version
I535VRLHE
Kernel version
3.0.8-1092717
[email protected] #1
SMP PREEMPT Fri Oct 5 15:36:02 KST
2012
Build number
IMM76D.I535VRALHE
Hardware version
I535.10
My phone number, MIN, PRL version, ERI version, MEID, IMEI, and ICCID all SEEM to have valid values, as far as I can tell. Obviously, it's not a good idea for some of that information to be posted on a public forum.
But please, help me, if you can.

Re provision your phone with the dialer code. I don't remember it right now, but Google repro vision galaxy s3.
Sent from my SCH-I535

kintwofan said:
Re provision your phone with the dialer code. I don't remember it right now, but Google repro vision galaxy s3.
Sent from my SCH-I535
Click to expand...
Click to collapse
The code doesn't do anything on my device. Developer mode is turned on. *2767*3855# is the code I'm finding.

I believe reprovisioning this phone is going to resolve my issues, however, I cannot get the reprovision code to work in the dialer. I have read that may be because of a recent OTA update, so I am flashing back to an older stock ROM and trying again. Please jump in and help if I am going about things the wrong way or with words of encouragement if I'm on the right track.

I was gonna say go back to a stock ROM and try it. If you make a nandroid before reverting you should be able to restore it after fixing your issue and have working miui.
Sent from my SCH-I535

V1R4G3 said:
I believe reprovisioning this phone is going to resolve my issues, however, I cannot get the reprovision code to work in the dialer. I have read that may be because of a recent OTA update, so I am flashing back to an older stock ROM and trying again. Please jump in and help if I am going about things the wrong way or with words of encouragement if I'm on the right track.
Click to expand...
Click to collapse
Correct. It was removed because it was a pretty bad security hole. Odin back to an older stock, repovisioning should work.
Sent from my SCH-I535 using Tapatalk 2

Is root66 ok?

V1R4G3 said:
Is root66 ok?
Click to expand...
Click to collapse
It should be. Is it software version VRLG1?
Sent from my SCH-I535 using xda app-developers app

Go into APN and select the first option (CBS) I believe, make sure it uim not nv and check that you are on LTE/CDMA/evdo. Once everything is selected properly reboot and try calling or texting.
PS. Also when rebooting, fully power off and remove and reinsert sim and power on.
Sent from my SCH-I535 using xda app-developers app

Success! I had to flash an older ROM and reprovision the device. I am now confident that there is no error I can't recover from! Thank you very much, everyone.

V1R4G3 said:
Success! I had to flash an older ROM and reprovision the device. I am now confident that there is no error I can't recover from! Thank you very much, everyone.
Click to expand...
Click to collapse
Good to hear!
Sent from my SCH-I535

V1R4G3 said:
Success! I had to flash an older ROM and reprovision the device. I am now confident that there is no error I can't recover from! Thank you very much, everyone.
Click to expand...
Click to collapse
Hey I'm having the same exact problem as you. Could you explain to me what you did exactly and which files you did? Which older ROM file did you use and what does it mean to reprovision a phone? This phone has been killing me for the whole week

Have you contacted the proper authorities or used a rape kit? ER?
Sent from the Matrix

[Q] Can't connect to Verizon after flash

I helped a friend of mine root and flash his Galaxy S3 yesterday.. He ended up not liking the ROM we flashed onto the phone because MMS was not working on it. It was the Team Venom ROM I believe.. Then we tried flashing another ROM today (Illusion 1.1.1) and it messed up his service completely. The phone wouldn't connect to Verizon's network at all (it wouldn't send/receive text messages or phone calls) so we tried going back to Team Venom because we know it worked.. Now no matter what ROM we attempt to flash, it just either says, "Searching for service..." or "Hands free setup failed, retrying."
We attempted going through some steps we found in a post here on XDA about changing CDMA mode to RUIM, but there is no option for RUIM mode in his network settings.
I have at&t and have no idea how Verizon's network works or how to fix it, so some help would be greatly appreciated. Thanks.

It should have an option for sim in CDMA subscription type. Also go to phone status is his imei there?
Sent from my VS920 4G using xda app-developers app

kintwofan said:
It should have an option for sim in CDMA subscription type. Also go to phone status is his imei there?
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
Yes, we found the IMEI and managed to get it fixed. Disregard this thread please.

TreyChristopher said:
Yes, we found the IMEI and managed to get it fixed. Disregard this thread please.
Click to expand...
Click to collapse
Now back it up before flashing anything else
Sent from my VS920 4G using xda app-developers app

help
TreyChristopher said:
Yes, we found the IMEI and managed to get it fixed. Disregard this thread please.
Click to expand...
Click to collapse
I just did the same thing how did you fix it???

rworster said:
I just did the same thing how did you fix it???
Click to expand...
Click to collapse
what "same thing" and have you done the following:
check your phone status in system
system >about phone >phone status
if your imei is correct (a bunch of long numbers) then do following:
if you can boot up and just can't connect, go into system:
system settings >more >mobile networks >CDMA Subscription >select RUIM/SIM
this should fix your non-connect problems. IF YOU have done all this, and it still doesn't work, starting hitting google to find a solution that works, as this has been the main culprit.
:cyclops:

Phone Number/MIN changing along with CDMA subscription

New issue, maybe I narrowed it down,
My phone number only seems to switch when I'm under "NV" for my CDMA subscription. It appears to be randomly switching back to NV periodically. If I put it in airplane and switch it back, it will correct my phone number and allow some messages to be sent. Any info on what settings should be there how to keep that from switching or any other info regarding this?
My phone number is currently showing up as 000-000-3720
My MIN is currently showing up as 0000003720
I do have a IMEI and MEID

boconnor341 said:
New issue, maybe I narrowed it down,
My phone number only seems to switch when I'm under "NV" for my CDMA subscription. It appears to be randomly switching back to NV periodically. If I put it in airplane and switch it back, it will correct my phone number and allow some messages to be sent. Any info on what settings should be there how to keep that from switching or any other info regarding this?
My phone number is currently showing up as 000-000-3720
My MIN is currently showing up as 0000003720
I do have a IMEI and MEID
Click to expand...
Click to collapse
really? nobody ever has had this problem?? I cant hardly ever use my phone!!! please help

Which rom are you using that causes this issue? Have you done any of these steps to resolve it?

SlimSnoopOS said:
Which rom are you using that causes this issue? Have you done any of these steps to resolve it?
Click to expand...
Click to collapse
It is with any and every rom. Is the link you provided typical of only Cyanogen roms? I have done the first step but it only temporarily fixes it and then it automatically reverts back. I have done the second step with the sim removed. Hopefully that works. Ill keep you updated.

boconnor341 said:
It is with any and every rom. Is the link you provided typical of only Cyanogen roms? I have done the first step but it only temporarily fixes it and then it automatically reverts back. I have done the second step with the sim removed. Hopefully that works. Ill keep you updated.
Click to expand...
Click to collapse
That's not Cyanogen specific it's AOSP rom specific. If it keeps happening to you a lot then the only thing I could tell you is to stick with TW roms.
Sent from my SCH-I535 using xda app-developers app

I used touchwiz roms and they were rebooting me after sending these texts.
I tried the root66 file and I accidentally flashed it through "phone" instead of "PDA". Stupid stupid mistake. It just stayed on the boot screen forever. What do i do in this situation? Please help

boconnor341 said:
I used touchwiz roms and they were rebooting me after sending these texts.
I tried the root66 file and I accidentally flashed it through "phone" instead of "PDA". Stupid stupid mistake. It just stayed on the boot screen forever. What do i do in this situation? Please help
Click to expand...
Click to collapse
Hmm, that may be a problem. What does it do after you pull the battery? Can you pull the battery then try booting back into download mode? Cuz there's not much I can suggest unless you can boot back into download mode.

I can get into download mode. I guess im going to try and follow one of these Unbrick tutorials with odin..

You need to Odin again . use the invisiblek file wipe. Put in DL mode and Odin again. Upon boot factory reset call Verizon as and they will provision. It will appear to fail. But then flash aosp and then reset ruim sim from nv then set to automatic then reboot. That is how I fixed the issue many times.
Sent from my SCH-I535 using xda premium

boconnor341 said:
I can get into download mode. I guess im going to try and follow one of these Unbrick tutorials with odin..
Click to expand...
Click to collapse
Good, Odin flash (in PDA!) either VRALG1 or VRBLK3 tar using Droidstyle's guide in the dev section. Root/unlock afterwards. You shouldn't need the soft brick method.
Sent from my SCH-I535 using xda app-developers app

Droid2drummer said:
You need to Odin again . use the invisiblek file wipe. Put in DL mode and Odin again. Upon boot factory reset call Verizon as and they will provision. It will appear to fail. But then flash aosp and then reset ruim sim from nv then set to automatic then reboot. That is how I fixed the issue many times.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Just recovered neighbors s3 using this method. Usually you won't need provisioning but if you do either use th method in threads located in xda or if unable call big red and they will eventually do it . Which in this case I had her call. I was in her home. Lol What it does is reprovision SIM. And usually will fail on their end but flashing back to aosp and toggling the above setting you should be ok . I'm not sure but honestly I've done this many times for people and myself. There are other ways and in some cases provisioning isn't needed...anyway good luck ..let us know ..I just couldn't believe as I was responding to your post she had knocked 30 minutes later...lmao. . Peace
Sent from my VZW-I535 using xda premium

Small carrier, model/build version, flashing decision issues

Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium

Lrs121 said:
Just got an upgrade from my carrier (a small local carrier) and I chose the s3. Came from some Motorola peice of fail. I'm looking to root and flash an insecure bootloader but I have encountered a confusing conflict. Having a Verizon model phone with a us cellular build of android loaded. And yes I'm certain it is a Verizon model phone (google schi535mbb if you don't believe me) with us cellular stock rom loaded (with some tweeks like 4g disabled). Rom and software model say the following R530 & d2usc. Bootloader is I535VRALE6 baseband I535VRLF2. This as far as I can tell was acomplished by a company called ultimobile. Which customizes devices to function on small mobile carriers. If anybody has any ideas or suggestions on what I might try, please let me know. I just don't want to screw something up and have a brick, just coming from a device that was all but brickable.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.

prdog1 said:
Interesting. From the sound of it it may just be software blocked. Verizon root and unlock should work. The trick is gonna be finding software that will work with that carrier. If it is using straight UC Cellular may be able to run what those guys are running. If it is that small carrier that controls access then that would be the problem. Without a backup of the stock rom don't know how you would get it running again. According to the numbers it is a Verizon S3 running Us Cellular. Good luck.
Click to expand...
Click to collapse
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium

Lrs121 said:
The recovery that's on it right now has built in options for nvbackup. From what I've read that is the radio, imei, and other files used to connect to the network. I was gonna make several backups of everything as soon as I gained root control. The real problem comes down to when I go to throw cm on here. Figuring out which vzw or usc will cooperate with the carrier files.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2

Addiso said:
Make a nandroid backup and maybe post to see what your running as?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium

Lrs121 said:
Was definitely gonna make a nandroid, but as for 'post to see what I'm running as' what do you mean?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Maybe the build.prop?
Edit: Attach it via Pastebin!

SlimSnoopOS said:
Maybe the build.prop?
Edit: Attach it via Pastebin!
Click to expand...
Click to collapse
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium

Lrs121 said:
Here ya go. Have fun http://pastebin.com/eUj5z2VT
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2

Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's weird though right? I'm not sure how to go about suggesting how to flash roms. I have to side with prdog1 and say it's a VZW GSIII running USC. I really can't suggest a good way to proceed since it's hard to tell what you would use to revert back to stock in case of emergences.
Anyone familiar with Team US Cellular? Any input from there?

Addiso said:
Looks like us cellular under the ultimobile ID?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.

Lrs121 said:
thats what i saw too. the difficult thing to figure out is if to use the verizon unlock and root or the us cellular model. it is most definately a verizon model of phone just loaded up with us cell software. ive flashed verizon a based rom over a locked down motorola peice of fail, but that couldnt touch the kernel, base band, or anything but the system with out it requiring a complete reflash to stock. i dont exactly have that option if every thing screws up in the process of gaining root. id have to take it into the store and wait till they can reflash it there.
Click to expand...
Click to collapse
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
ro.build.version.incremental=R530UVXALK5
Click to expand...
Click to collapse
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!

SlimSnoopOS said:
I'm fairly certain you should use the unified toolkit to root and maybe unroot. In your build.prop, I noticed it reads on the fifth line:
and the toolkit supports LK5 build for the d2usc. I think they're both locked down the same but on Team US Cellular's website that's what I'm seeing some people have used too. Idk about your specific case using another carrier but a d2usc GSIII but I'm thinking that's a start. Idk about returning to stock though.
Edit: Gonna add this, this means there is an Odin flashable of LK5 available somewhere.
Edit x2: POW!
Click to expand...
Click to collapse
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable

Lrs121 said:
really i need to gain fastboot access to the phone. there are some files i need to check and i need to pull the special recovery that came with the phone. if i can do that i should be able to pull what i need from the phone to be able to return to stock. im also gonna perform an nvback up, a qpst backup and the synergy back up. but first things first i need fastboot access to the phone. i know how to get into recovery and download mode but for the life of me i cant figure out how to get to a fastboot compliant mode. from there i can figure how im gonna proceed to root.
edit: what i see in download mode
odin mode
Product name: sch--i535
custom binary download: yes (1 counts)
current binary: custom
system status: custom
Qualcom secureboot: enable
Click to expand...
Click to collapse
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?

SlimSnoopOS said:
Here's a left field suggestion, could you call this UltiMobile company and ask about what they used?
Click to expand...
Click to collapse
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.

Lrs121 said:
havent done that yet. its on a list of things to do the problem is that everywhere they put information out they say to contact the carrier not them for everything. i may just have to wait till the phone isnt so new at my carrier and let the IT department play around with it for a while. i can then get information from them.
Click to expand...
Click to collapse
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.

SlimSnoopOS said:
That's real tricky but sounds like your best option. At least you're rooted and unlocked with the VRALE6 bootloader and can debloat. Out of curiosity, what recovery are you using that has all these options?
As an aside, this table tells you where the recovery partition is. I've heard of people using dd commands to pull whatever partition they want to their sdcard but idk how viable an option this is in terms of pushing a recovery to that partition. I'm not recommending you try it either.
Click to expand...
Click to collapse
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app

Lrs121 said:
The vrale6 is unlocked? If so then why does it say that the qualcom secure boot is enabled. And I haven't rooted just yet but am working on it. Its a recovery built by ultimobile.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.

SlimSnoopOS said:
Yes indeed. VRALE6 is the prerelease bootloader that was leaked which EVERY d2vzw (d2usc I suppose too) uses in order to allow flashing of roms/kernels. It's a little weird to explain but basically everyone's Download Mode reads almost the same. Mine reads "custom binary: Samsung Official" though and I'm rooted/unlocked. Idk the technical or even the proper way to explain it but the unlocked VRALE6 bootloader has no bearing on what Download mode says. Although your custom binary should be at 0 if/when you do warranty exchanges.
Click to expand...
Click to collapse
Ah makes sense now it just doesn't do a hash/encryption check. I've dealt with a lot of bootloader stuff with my old phone. the phone came like that with the count at 1. Was like that before I tried anything. Probably was triggered when the d2usc stock was flashed onto it. Which probably means I should stick with d2usc builds to ensure compatibility with connecting with my carrier.
Sent from my Nexus 7 using XDA Premium HD app