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
Related
I'm going to get a new phone in a couple weeks. I have Verizon as a carrier, and I want one I can root and throw on a loopback supporting kernel to run Linux as a VM. I'd just like to verify with others that the Verizon S3s from the store now don't have any current factory or OTA update that might be done that will thwart my plans. Is there anything to look out for?
None of the current updates prevent the debugrootfs for root or prevent the leaked aboot from being used. So any phone you get right now should be fine for modification.
jlspartz said:
Is there anything to look out for?
Click to expand...
Click to collapse
At this moment, the only thing to worry about is backing up your IMEI after unlocking your bootloader but prior to flashing anything in recovery. After you do this, you're all set.
Sent from my SCH-I535 using xda app-developers app
Did a Google and forum search and couldn't find anything concrete. Any help would be appreciated. Thanks in advance.
Sent from my SCH-I535 using Tapatalk
ProtheusIRC said:
Did a Google and forum search and couldn't find anything concrete. Any help would be appreciated. Thanks in advance.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
With 4.3, the bootloader is locked permanent and at the moment there's no way to unlock. Once on 4.3 you can't downgrade or flash custom rom/kernel or custom recovery, however, you can root 4.3 with saferoot here http://forum.xda-developers.com/showthread.php?t=2565758
So no CWM? Is anyone working on it? What about this "Safestrap"?
Sent from my SCH-I535 using Tapatalk
ProtheusIRC said:
So no CWM? Is anyone working on it? What about this "Safestrap"?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes no CWM or TWRP since the bootloader is locked. Safestrap is a method of installing a separate loader from the locked one, it's working on some model like att S4, note, but not Verizon S3. The software is not stable yet, still have many bugs and glitches. I won't touch it...not just yet.
Lol ok. Well at least we have root.
Sent from my SCH-I535 using Tapatalk
ProtheusIRC said:
Lol ok. Well at least we have root.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm still keeping my ears open for an unlocked bootloder. Root is all well and good, but I'm getting jittery about flashing a different rom. Any news about progress on this?
akambience said:
I'm still keeping my ears open for an unlocked bootloder. Root is all well and good, but I'm getting jittery about flashing a different rom. Any news about progress on this?
Click to expand...
Click to collapse
The bootloader will never be unlocked. The original bootloader on the Verizon s3 wasn't even "unlocked." It was a completely different boot image that was leaked. AFAIK, no bootloader has ever been unlocked through hard coding. There are simply loopholes & workarounds. Kexec and Safestrap are two examples of workarounds. They are pretty much just as good as the real thing so there is still hope for those crack-flashers taken off guard by the new update.
Still, I can't sympathize with people who start threads like these: There have been countless "I took the 4.3 update. How do I flash ROMs?" posts. If you were really into flashing, you would never be in this situation.
It's the cardinal rule. NEVER ACCEPT OTAs!!!!!!
BattsNotIncld said:
The bootloader will never be unlocked. The original bootloader on the Verizon s3 wasn't even "unlocked." It was a completely different boot image that was leaked. AFAIK, no bootloader has ever been unlocked through hard coding. There are simply loopholes & workarounds. Kexec and Safestrap are two examples of workarounds. They are pretty much just as good as the real thing so there is still hope for those crack-flashers taken off guard by the new update.
Still, I can't sympathize with people who start threads like these: There have been countless "I took the 4.3 update. How do I flash ROMs?" posts. If you were really into flashing, you would never be in this situation.
It's the cardinal rule. NEVER ACCEPT OTAs!!!!!!
Click to expand...
Click to collapse
You didn't have to word it in that way. You sounded as if you were talking to a child, and then told me, in not so many words "Boo hoo, cry about it". This thread is old and I've learned quit a bit since then so next time you necro post, how about not being such a ****?
Sent from my SCH-I535 using Tapatalk
ProtheusIRC said:
You didn't have to word it in that way. You sounded as if you were talking to a child, and then told me, in not so many words "Boo hoo, cry about it". This thread is old and I've learned quit a bit since then so next time you necro post, how about not being such a ****?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Didn't mean to come off as a ****. I was just responding to the bootloader comment and went off on a rant. Sorry if you were offended.
I was, but you are one of the few who take responsibility for offending someone, so it's cool.
BattsNotIncld said:
Still, I can't sympathize with people who start threads like these
Click to expand...
Click to collapse
This was the part that offended me the most. Now, I'm by no means a noob, but I am man enough to admit there are LOTS of things I don't know. This phone was my brothers. HE took the OTA then traded it to me. So I was trying to find a way out of it. I've come to terms (I think) with being stuck with a locked bootloader but I am hopeful about kexec. Who knows?
Apology accepted.
Sent from my SCH-I535 using Tapatalk
Yeah since I didn't even know your whole story, I wasn't necessarily referring to you (even though it sounded like that). I was more referring to people that said they knowingly accepted the OTA. I just worded it very poorly.
That's unfortunate how you ended up with the locked bootloader, but the devs we have are outstanding and I'm sure they'll get a workaround going very soon. :good:
Haha This is what happened when no one unlocked the boot loader..lol
Sent from my Galaxy Nexus using xda premium
Don't do it!!!I unlocked the boot loader with ez unlock app and booted into recovery and hard bricked my sch i535. Just got it back got fixed with jtag. Gabbyanne on eBay is a life saver... Don't do it to yourself. Trust me
Sent from my SCH-I535 using Tapatalk[/QUOTE]
Germanlopez007 said:
Don't do it!!!I unlocked the boot loader with ez unlock app and booted into recovery and hard bricked my sch i535. Just got it back got fixed with jtag. Gabbyanne on eBay is a life saver... Don't do it to yourself. Trust me
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Out of curiosity did jtag get you back to 4.1.2? I don't think anyone has reported one way or the other. From what I understand it should be impossible even for jtag but it's always good to verify.
ThePagel said:
Out of curiosity did jtag get you back to 4.1.2? I don't think anyone has reported one way or the other. From what I understand it should be impossible even for jtag but it's always good to verify.
Click to expand...
Click to collapse
It is impossible, you can't jtag the bootloader over the 4.3 baseband. It's more complicated after the update because the hardware keys are different. Changing the bootloader is only changing the software.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It is impossible, you can't jtag the bootloader over the 4.3 baseband. It's more complicated after the update because the hardware keys are different. Changing the bootloader is only changing the software.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I know just waned to make sure. You can never be sure until it is tried. For example invisiblek said that the ml1 firmware will brick the phone if you upgrade from a phone with the insecure bootloader because that's what happened to the s4 that took a 4.3 upgrade. Well I know from experience that wasn't true. Theory is just that until it has been tested who knows what samsung might have forgotten to do that might allow jtag to do that. Plus I have yet to hear if anyone has tried. Not saying it hasn't been done I just haven't seen anyone say more than got it back and it works.
*edit* I just found that thread he said you will brick and I must of missed the part where he said you probably wont if you upgrade the entire boot chain. But how would you end up in that scenario of being bricked? The root66 tars took out the entire boot chain and added only the insecure bootloader.
ThePagel said:
I know just waned to make sure. You can never be sure until it is tried. For example invisiblek said that the ml1 firmware will brick the phone if you upgrade from a phone with the insecure bootloader because that's what happened to the s4 that took a 4.3 upgrade. Well I know from experience that wasn't true. Theory is just that until it has been tested who knows what samsung might have forgotten to do that might allow jtag to do that. Plus I have yet to hear if anyone has tried. Not saying it hasn't been done I just haven't seen anyone say more than got it back and it works.
Click to expand...
Click to collapse
I get what you're saying, if it wasn't hardware coded then it could theoretically work.
The same thing could be accomplished through Odin though by flashing boot chains, ez unlock also proves it's hardware signed. Jtag would do the same thing ez unlock does, just on a more holistic level.
Best bet would be to Jtag a 4.3 developer edition bootloader, but I don't think it exists, because making one widely available for developer edition phones would be handing us an unlocked bootloader. They'd have to be made on a per phone basis with specific keys for each device. I highly doubt it exists, but if it did it might work if we could figure out how it's getting around the bootloader, like what step it's bypassing.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I get what you're saying, if it wasn't hardware coded then it could theoretically work.
The same thing could be accomplished through Odin though by flashing boot chains, ez unlock also proves it's hardware signed. Jtag would do the same thing ez unlock does, just on a more holistic level.
Best bet would be to Jtag a 4.3 developer edition bootloader, but I don't think it exists, because making one widely available for developer edition phones would be handing us an unlocked bootloader. They'd have to be made on a per phone basis with specific keys for each device. I highly doubt it exists, but if it did it might work if we could figure out how it's getting around the bootloader, like what step it's bypassing.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Truth but I had a idea a couple months ago but I don't have the balls to try it. With these qualcomm gs3 phones there is a emergency boot from sd card for the aboot. If you were hard bricked it might be possible to boot to the insecure bootloader that way. You could never do the flash back trick with terminal emulate so it wouldn't be a true fix but who cares unless you need your sd card (I do but I have learned to love 4.3).
ThePagel said:
Truth but I had a idea a couple months ago but I don't have the balls to try it. With these qualcomm gs3 phones there is a emergency boot from sd card for the aboot. If you were hard bricked it might be possible to boot to the insecure bootloader that way. You could never do the flash back trick with terminal emulate so it wouldn't be a true fix but who cares unless you need your sd card (I do but I have learned to love 4.3).
Click to expand...
Click to collapse
Really?
Ya, if you could do that you could simply run straight from the aboot file without the secure checks. That might actually work, but you'd have to get the insecure aboot loaded without it locking the phone, you'd have to try it immediately after loading the aboot image before a reboot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Really?
Ya, if you could do that you could simply run straight from the aboot file without the secure checks. That might actually work, but you'd have to get the insecure aboot loaded without it locking the phone, you'd have to try it immediately after loading the aboot image before a reboot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
well you would need the debrick file from the insecure bootloader. that is what the debrick image is its the aboot image. So now that I think about it a little more the only way that would work is if qualcomm has its own bootchain and I would not doubt if it did but I am not technical enough to figure that out. the only way for people like me to find out is try and I will not purposelessly brick to try. I cant even justify asking someone who is hard bricked to try it. They are already mad it happened why add that extra stress.
---------- Post added at 03:34 AM ---------- Previous post was at 03:30 AM ----------
holy cow its 3:23 here I better go to bed so I can wake up at 9 and hopefully not fall asleep driving tomorrow.
People I am stuck in this firmware since i got the phone.. I heard the others have had 2 updates the 1.54 and the 1.55..
Really need help
You should really let us know more about your situation. That post does next to nothing for troubleshooting. We need to know mods, changes, what you've done, etc. Also what you've tried. Tell us everything.
Sent from my HTC6525LVW
1ManWolfePack said:
You should really let us know more about your situation. That post does next to nothing for troubleshooting. We need to know mods, changes, what you've done, etc. Also what you've tried. Tell us everything.
Sent from my HTC6525LVW
Click to expand...
Click to collapse
1- I am not rooted and i bypassed the activation when I got the device since I am not living in the US.
2- I am using CDMA network here in my country.
3- whenever i look for an update it never shows anything. (No new Update nor You are running the latest version)
must.sayim said:
1- I am not rooted and i bypassed the activation when I got the device since I am not living in the US.
2- I am using CDMA network here in my country.
3- whenever i look for an update it never shows anything. (No new Update nor You are running the latest version)
Click to expand...
Click to collapse
If you are using it in another country on a different carrier you will have to download it manually and put the update in a spot where you can find and apply it from there using the stock recovery.
Sent from my HTC6525LVW using Tapatalk
dottat said:
If you are using it in another country on a different carrier you will have to download it manually and put the update in a spot where you can find and apply it from there using the stock recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I tried to open the stock recovery but it showed me a phone with a red alert in the screen what should i do?
must.sayim said:
I tried to open the stock recovery but it showed me a phone with a red alert in the screen what should i do?
Click to expand...
Click to collapse
Hold all 3 buttons in different ways. Lol. Hard to explain, but start mashing and holding your physical buttons. I found holding both volumes then tapping power a few times worked the quickest.
Sent from my HTC6525LVW
dottat said:
If you are using it in another country on a different carrier you will have to download it manually and put the update in a spot where you can find and apply it from there using the stock recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I tried it but the recovery is saying that the operation is invalid
Make sure you have read/write/execute access to the location and the file you are trying to use.
Sent from my HTC One (M8).
Me too
I am also stuck in 1.12.605.11 on a new M8 I got less than a week ago. I am on Verizon in the US. Checking for updates does the same thing has the OP. It says its checking then stops with no further messages. I am using the Weak Sauce root with S-On. Firewater didn't work when I tried it so makes me wonder if there are other issues with my phone.
Verdigo said:
I am also stuck in 1.12.605.11 on a new M8 I got less than a week ago. I am on Verizon in the US. Checking for updates does the same thing has the OP. It says its checking then stops with no further messages. I am using the Weak Sauce root with S-On. Firewater didn't work when I tried it so makes me wonder if there are other issues with my phone.
Click to expand...
Click to collapse
Yours is a different situation, your rooted the OP isn't. You might have better luck starting your own thread on the issue.
(MOD EDIT)
Dragbike Racer said:
Yours is a different situation, your rooted the OP isn't. You might have better luck starting your own thread on the issue.
Click to expand...
Click to collapse
WeakSauce is a temp root solution meaning I can turn it off and I wont be rooted anymore. I probably should've mentioned that I tried that too. I may be on a different network than the OP but a lot of other people elsewhere are having the problem so it seems to be network independent.
(MOD EDIT)
Flaming/Trolling
Flaming and Trolling are not allowed on XDA.
Let's try and remember to speak respectfully to one another.
Thank you,
-Neo
Forum Moderator
If you are using the Straight Talk Galaxy S4 with build number
JSS15J.S975LUDUANB1 and just want root and simple recovery
You can root using towelroot.
SuperSU will also deactivate Knox.
Safestrap version 3.72 works for getting a proper recovery installed with the option at boot for system or recovery. Note that it will say safestrap is disabled but will still allow your choice to boot into recovery.
Make a backup in recovery as soon as you can.
Or if you want awesomeness!! Do THIS!!
Here is the definitive guide for those wondering what to do that will work and be stable and AWESOME!
From the beginning:
1.Root with towelroot (search) AND install SuperSU from the play store.
2.Install the latest recovery from here using the DD method listed directions from the TWRP site. This is from T-Mobile and works! http://forum.xda-developers.com/showthread.php?t=2263001
MAKE A BACKUP!!! DO IT! No more messing around with Safestrap and the bitter warnings!
To get into recovery hold "home+volume up" during boot. Whoooo!!!!
3. Install the Lollipop gpe ROM from here: http://forum.xda-developers.com/showthread.php?t=2539361
This uses the aroma installer and works well.
You may, or may not have to input *#6463*# into dialpad to change settings to LTE etc.. This adjustment may alsobe in the ROM settings!
4. Optional - install the googy kernel
I like this kernel better though there isn't a huge difference from the hulk kernel. Make sure to install the GE edition 1.3.0. NOT TOUCHWHIZ! : http://forum.xda-developers.com/showthread.php?t=2741181
ENJOY!
sleekmason said:
Moderator, please move to relevant forum or incorporate into the general info thread if this isn't the right place.
If you are using the Straight Talk Galaxy S4 with build number
JSS15J.S975LUDUANB1,
You can root using towelroot.
SuperSU will also deactivate Knox.
Safestrap version 3.72 works for getting a proper recovery installed with the option at boot for system or recovery. Note that it will say safestrap is disabled but will still allow your choice to boot into recovery.
Make a backup in recovery as soon as you can.
The zip to allow tethering WILL NOT work, and you will be stuck on the Samsung logo.
Xposed works well, but do not use the option in gravity box to add the recovery option to your power menu or your device will freeze upon pressing the power button.
Greenify works well.
Advise against ROM installation, as well as initial upgrade. You will lose app to SD ability if you upgrade.
The boot loader is not unlocked, so no cool kernels here
Click to expand...
Click to collapse
I was able to use towelroot and my att s4 is running on the att towers with straight talk.
mrphotoman said:
I was able to use towelroot and my att s4 is running on the att towers with straight talk.
Click to expand...
Click to collapse
Have you downloaded safestrap? Or tried anything with Xposed?
sleekmason said:
Have you downloaded safestrap? Or tried anything with Xposed?
Click to expand...
Click to collapse
No not yet, I just got the phone so I haven't done a lot to it yet. I was able to get tethering working and it was pretty easy and I got a nice extended battery case for it yesterday that I love. Other than that I haven't had time to do a lot else to it.
mrphotoman said:
No not yet, I just got the phone so I haven't done a lot to it yet. I was able to get tethering working and it was pretty easy and I got a nice extended battery case for it yesterday that I love. Other than that I haven't had time to do a lot else to it.
Click to expand...
Click to collapse
Can you tell me what you did for tethering? I tried once but was unable to get it to work.
sleekmason said:
Can you tell me what you did for tethering? I tried once but was unable to get it to work.
Click to expand...
Click to collapse
sure, i have a how to vid but i am waiting on the mod to approve it so i can post it. it definately works on the newest updated att phone
mrphotoman said:
sure, i have a how to vid but i am waiting on the mod to approve it so i can post it. it definately works on the newest updated att phone
Click to expand...
Click to collapse
Excellent! Please post a link to it here as well when you get it uploaded
Updated
See first post
I used tmo twrp. Flashed tmo and att roms. I also have the Odin file. I am not sure but I am on the s975L which I thought was att not sure but pretty sure. However it also says i337 underbattery ...I've tried more tmo roms than anything. No safestrap but I might try that later. Seems we don't have locked bootloader. This is great. However unlock is next for me. Having a blast hacking the hell out of it. So far I have had no issues. Again I'm not new to this. Lol. It's an addiction. I have sprint note 4 as my DD. So this is my fix. Lmao.
Sent from my SM-N910P using XDA Free mobile app
Droid2drummer said:
I used tmo twrp. Flashed tmo and att roms. I also have the Odin file. I am not sure but I am on the s975L which I thought was att not sure but pretty sure. However it also says i337 underbattery ...I've tried more tmo roms than anything. No safestrap but I might try that later. Seems we don't have locked bootloader. This is great. However unlock is next for me. Having a blast hacking the hell out of it. So far I have had no issues. Again I'm not new to this. Lol. It's an addiction. I have sprint note 4 as my DD. So this is my fix. Lmao.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know, the bootloader IS locked, but can be bypassed using Loki to patch kernels for custom roms. Glad to see somebody else on this phone
sleekmason said:
As far as I know, the bootloader IS locked, but can be bypassed using Loki to patch kernels for custom roms. Glad to see somebody else on this phone
Click to expand...
Click to collapse
That's strange. If it was locked I wonder how I've used tmo twrp no loki or SS and flashed tons of roms so far...I just odined back from a modem issue. But rerooted now off to get some modems etc...boot and all. I'll keep reporting. Thank you bro. I maintain many devices and carriers and am about to start a channel on YouTube. I do music writing now with keyboard. Now I'm just getting a hand on s4 straight talk and will make a list of all working roms.
Sent from my SM-S975L using XDA Free mobile app
Droid2drummer said:
That's strange. If it was locked I wonder how I've used tmo twrp no loki or SS and flashed tons of roms so far...I just odined back from a modem issue. But rerooted now off to get some modems etc...boot and all. I'll keep reporting. Thank you bro. I maintain many devices and carriers and am about to start a channel on YouTube. I do music writing now with keyboard. Now I'm just getting a hand on s4 straight talk and will make a list of all working roms.
Sent from my SM-S975L using XDA Free mobile app
Click to expand...
Click to collapse
True.. I don't know as much about it as I like. I just wasn't able to use fastboot or "unlock" using fastboot.
If you are working with the modems let me know how that goes, and maybe you can help with an issue I'm having? My GPS won't work after trying a ROM with safestrap. What I've posted here is a result of trying to fix it. I consistently show NO satellites. I consulted the local phone fixers to no avail. I was wondering if it could be related to a modem issue? I think the ROM I first tried did something deep to my phone, though Phone Info showed at the time everything to be original concerning baseband etc.. And a factory reset didn't help.
I'm at the point now of thinking its hardware rather than software but the coincidence to trying the ROM was too high.
Hey everyone!
I am working with this phone and am trying to get a backup modem, can you please ,make a suggestion?
Also are there any ROMs that allow easy access to umts menu through servicemenu? I know the base firmware cripples this and I'm trying to get a work around!
thanks in advanced!
I have an sch-i535 Galaxy S3 Verizon phone. I'm not using it on a network anymore and just want to use a custom rom. Is there ANY way to wipe, replace, do something with the locked bootloader since I'm not using the phone as a phone?
oneway2k said:
I have an sch-i535 Galaxy S3 Verizon phone. I'm not using it on a network anymore and just want to use a custom rom. Is there ANY way to wipe, replace, do something with the locked bootloader since I'm not using the phone as a phone?
Click to expand...
Click to collapse
Your out of luck. Locked bootloader means no way to return to a previous version on Android. Even if its not being used as a phone it's basically stuck there. There are jtag services out there to revert back to 4.1.2 but I've heard a lot of mixed thoughts on those
Sent from my N5
ShapesBlue said:
Your out of luck. Locked bootloader means no way to return to a previous version on Android. Even if its not being used as a phone it's basically stuck there. There are jtag services out there to revert back to 4.1.2 but I've heard a lot of mixed thoughts on those
Sent from my N5
Click to expand...
Click to collapse
Since I'm not too concerned about breaking this phone, can someone point me to info on the procedure for using JTAG to go back to 4.1.2? I have found some advertisements but no how-to.
oneway2k said:
Since I'm not too concerned about breaking this phone, can someone point me to info on the procedure for using JTAG to go back to 4.1.2? I have found some advertisements but no how-to.
Click to expand...
Click to collapse
I'd suggest mobile tech videos. There is a thread on xda about them but there are mixed reviews
Sent from my N5
http://forum.xda-developers.com/showthread.php?t=1734949
Moved to Q&A.
If you decide not to go the jtag route you could:
1) install SafeStrap
2) flash SuperliteROM into stock slot
3) flash XPosed and the modules that would make SLR look and act as you like.
This is what I have done with the i535 I picked up that was on NE1.