Related
Hi, I have been trying to get my s4 i9505 networked unlock. It's currently on EE. I bought it from someone who has gone abroad so can't ask them to get ee to do it. I have tried 3 online unlocking sites, the last was recommended on here but non of them can do it. I have tried to install several firmwares but hoping that would remove the ee lock But they all seem to be ee firmware. Is there a firmware that you can tell me about which will do what I want. Or is there a way I can conect to my computer and do a hardware unlock. Hope someone can help as getting desperate now.
A friend of mine has a insurance supplied s4 i9505 Which is unlocked. Is there a way we can copy the firmware on his and install on my or completely clone the phone . ?
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Strephon Alkhalikoi said:
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Click to expand...
Click to collapse
Thank you for the reply, can I install a modem . I think I have read that you can't down grade the firmware ? If this is wrong. Where can I find the 4.2 firmware . Thanks
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Strephon Alkhalikoi said:
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Click to expand...
Click to collapse
Ok thanhs you the info , looks like I'm a bit stuck . I don't really understand why the unlocking sites can't generate a Code. If I put another sim into the phone it doesn't tell me I an incorrect sim .
unlock
Is there anyone on here in uk who can offer to unlock this phone for me
1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.
I just got an SM-G975F/DS ~ seems like the Taiwan version.
My current issues:
Can't disable emergency alerts!!!
Can't clear voicemail notification from tray. Infuriating.
No hosts file override (need this for app development & Adaway)
Samsung bloatware
I don't give a f*ck about Knox or Samsung Pay but I like the stock camera so I have a few questions about the root process.
First it seems like this is the process just to have root in with Stock ROM. Please correct me if I'm wrong.
For randoms reading this: THIS WILL NOT WORK ON USA Snapdragon VERSION
Enable OEM Unlock from developer menu.
Boot into download mode (Plug in PC connected USB cable while holding Bixsby Button + Vol Down)
Unlock bootloader by pressing volume up and confirming (not actually unlocked yet due to Samsung trickery)
Quick setup OS with Internet connectivity knowing it's gonna be wiped again.
At this point Samsung's Vaultkeeper service should detect OEM unlock and finally actually unlock the bootloader.
Install Magisk with this guide.
So it seems like this process would patch just the AP partition with Odin while keeping the ROM and Recovery stock.
So here's the questions.
If I continue to run stock ROM with Magisk with this method any official OTA updates must be done manually or I risk bricking the device?
If I install TWRP and try out some roms and don't like them can I go back to stock?
Is it possible to flash stock rom WITHOUT Magisk after doing all this?
I plan on writing some simple guides on this when I'm done since the current ones are a bit confusing so I would appreciate some clear and concise answers the the above questions.
Thanks all!
Hey i have samsung galaxy tab s5e lte (sm-t727v) it is unlocked verizon tab i want to flash samsung stock firmware to remove varizon boatload & pre-installed apps & also some features like call & message continuity are blocked by verizon. So can you please suggest which firmware stall i flash & how. I’ve tried flsahing sm-t727 & sm-t725 via odin but it gives error (secure check fail : Pit)
Im curious about tthis myself, but ive kind of resignes myself to the fact im probably goong to have to get an s6 directly from samsung that allows the option to unlock the bootloadr out of the box. There is a new "security update" from verizon though, im curious about what it actually patches before I update.
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
purplerose1414 said:
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
Click to expand...
Click to collapse
Where did you find the T727R4 firmware?
Ryche666 said:
Where did you find the T727R4 firmware?
Click to expand...
Click to collapse
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
anyone else have success with this? ive followed everything so far but i'm stuck trying to unlock bootloader. the option is there in developer options i can turn it on or off in there but when i power down and boot into download mode the option to unlock bootloader isnt there and it says OEM Lock On (u1)
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
It was cuz i was on a newer fw version for R4 (feb4) i downgraded to the Dec one and i now i have my bootloader unlocked (shows in dev settings, get notification at boot, and says oem lock off in download mode) but i keep getting a error about "only being able to flash official firmware versions (vbmeta)" . turns out this is from my KG Status being PRENORMAL instead of Checking. you can check this in download mode as well. did you have any issues with that or kknow what i'm talking about? there are guides that say to do things like roll the date back on your phone manually then check for updates but it doesnt work
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
also i'm a little confisued about the end of your directions. I am not a Verizon Subscriber i bought this 2nd hand for a deal i am on TMO (not planning on really using data on thin atm but still) Am i correct in thinking after you flashed R4 BL AP CP and CSC, then booted into the R4 firmware and went through initial setup, then reboot to recovery to unlock bootloader and then flashed the t727u AP, left the R4 bootloader, and flasshed VZW CP and CSC? i cant seem to get mine to boot if i do that i get hash check errors when it tries to boot and spits me out into download mode. if this is the case do you remember or can you check the exact versions of CP, AP, and CSC you flashed? right now what i did was flash all R4 tars to go from 727v to 727r4, went though setup and verified i have oem unlock option in dev options then rebooted to download mode and unlocked bootloader THEN i FLASHED 727u versions of AP CP and CSC since my error with the vzw ones i mentioned earlier. Last question. should i be putting my sim in? i notice when i flash the U firmware i get a message about carrier settings update and it makes it reboot
thanks for replying btw
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
albinoman887 said:
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
Click to expand...
Click to collapse
See, as soon as I switched from T727V to T727U I stopped even seeing kg status in download mode. In my original post in this thread I thought that meant I had tripped it. I really have no clue why just switching to unbranded firmware would make that difference either. I just lucked out on the magic cocktail to unlock Verizons bootloder, I was kind of hoping it would be easy peasy for others. Like, my poor tablet went through odin every day for a straight month.
E: Just saw your edit in your post. I'll have exact firmwares I used asap. In the meantime, my hotspot worked just fine on the unbranded CP and CSC, maybe try that?
ok let me know ill be up a few more hrs
---------- Post added March 10th, 2020 at 12:19 AM ---------- Previous post was March 9th, 2020 at 11:55 PM ----------
you didnt happen to do anything outlined in this thread did you?
https://forum.xda-developers.com/tab-s5e/how-to/samsung-galaxy-tab-s5e-debloat-root-info-t3935010
i wonder if you disabled a Knox apk at the right time to make KG status go away
I'm really scared of bricking my LTE AT&T tablet if I flash the only firmware I was able to grab.
Any way to find the specific stock firmware for my sm-t727A? I've tried Frija, and went all over google to no avail; I can only find other stock firmware.
If I just want to switch to sm-t727u firmware from sm-t727v firmware without rooting do I need to go through the extra step of flashing the us cellular version first?
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I get to the unlock the bootloader part but then when I go back in and try to flash the U software according to your instructions, it doesn't work. Could it be that the software has been updated since the instructions were written and it won't work now?
I have tried every version of Patched Odin and followed these directions to a T. I even went back and tried other things and can't get this to work. If someone can help me get the U software to flash on my SM-T727V, I got $20 I'll Venmo or Zelle you.
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I am trying to copy your process with a Tab A 2019 unlocked, but Sprint variant with no success so far. I have bricked it a lot, but it doesn't seem to want an unlocked firmware for the same model . I haven't tried flashing it's bootloader though, out of fear of bricking it ( I have unlocked its bootloader already).
Hey guys, just found the thread. Anyone know if an unlocked SM-T727A can be OEM unlocked? I mean the bootloader. The option is always missing no matter how many time I try according to the tutorials, which makes me doubt if a branded S5e doesn't even have this capabililty. Perhaps that's why I am here seeking a chance to flash it to an SM-T727U. Thanks for anyone who replies.
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Wieczorkiewicz said:
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Click to expand...
Click to collapse
Help me ola if u r there. I have same t727a of att live outside The US. I just want to skip Att block and use SMS app, so flash Usc t727r4 via Odin patched is enough for me? And if i want update from android 9 to 10 i just do same thing with Q firmware?
i try flash USC T727R4 on ATT T727A success for first time, but Massage app still require link other SamSung phone to use. I have full funtion simcard inserted but Google massage app cant recognize too.
Btw, convert to USC is good, no ATT bloatware and now have OTA outsite The US.
Hello. I am a Noob when it comes to rooting, but I've unlocked over 600 androids and 10 iPhones, so I "ain't no dummy"...lol.. My problem is this... I took an SM-G935P w/ unlocked bootloader and flashed G935U (bootloader 11 ) 8.0 firmware to it. Now i can use it on whatever network, which is cool, but even though in Developer Options it has the OEM Unlock toggle turned on, I cant seem to be able to root the damn thing.. TWRP keeps failing ( Recovery), CF Auto Root fails (Recovery)...Even the One Click Root crap fails.. I've seen several Oreo root files, but they are all for binaries well below mine...
I need some help here. Did I possibly lock the bootloader when I flashed the firmware to U? What can i do now to acheive root?
Mahalo
lodog1974 said:
Hello. I am a Noob when it comes to rooting, but I've unlocked over 600 androids and 10 iPhones, so I "ain't no dummy"...lol.. My problem is this... I took an SM-G935P w/ unlocked bootloader and flashed G935U (bootloader 11 ) 8.0 firmware to it. Now i can use it on whatever network, which is cool, but even though in Developer Options it has the OEM Unlock toggle turned on, I cant seem to be able to root the damn thing.. TWRP keeps failing ( Recovery), CF Auto Root fails (Recovery)...Even the One Click Root crap fails.. I've seen several Oreo root files, but they are all for binaries well below mine...
I need some help here. Did I possibly lock the bootloader when I flashed the firmware to U? What can i do now to acheive root?
Mahalo
Click to expand...
Click to collapse
How did you manage to flash G935U bootloader to G935P, hence unlocked carriers. mine is also G935P