Hey all. I've got a USCC Electrify M, bootloader unlocked and rooted running twrp 2.?.?> and I have a few questions.
First now that my boot loader is unlocked do I still need to flash using the retail edition files?
Next, If so do I need to use SafeStrap to do it? and is it ok to use safestrap with an unlocked bootloader?
Next, most of the roms are built from the Verizon rom, If I flash these will I break my phone due to bad build.prop, radio, and possibly other files like apn's and whatnot.
and last , if so can I use the stock files from the post at teamuscc to replace the files with the correct ones for USCC, either before or after flashing.
I know this is a tall order, but I'm relatively new to the whole safestrap bootloader thing coming from an Electrify 1 that I managed to unlock after the 2.3.5 unlock lockout, and not too familiar with the whole rom contents thing yet. Once I get a few answers to my other posts I may feel more comfortable just giving it a whirl. I do have a nandroid of where I am now, but don't want to screw anything up that can't be fixed with that.
Thanks for any info.
Hello all, I come asking for help. I recently had an issue with my note 3. I tried to update my twrp with the twrp manager, I had safestrap 3.75 and then used the twrp manager to try and flash the new 3.8.4.0 twrp, but after it flashed I went to recovery and tried to install cm12 but kept getting the error "this build is for hltevzw, you have a ." When trying to install. So I went full stock, flashed the new stock stuff via odin. Then rerooted with towelroot, installed superSU, then the safestrap 3.75. Now I can get to safestrap recovery, but if I try to install cm12, I will follow directions, flash rom, flash gapps, then I've tried flashing superSU as some have suggested, and tried not flashing superSU, but then my phone reboots, goes past the splash screen showing the unlock and says custom, sits at a black screen for a while, then reboots. Only when it reboots, at the splash screen it says loafing recovery in red at the top, then I get a screen saying that custom software has been detected and I need to take the phone in to Verizon or something like that. The only way to get out of it is to shut down, boot into download, and then hit volume down to cancel. It just keeps doing that same thing over and over. I was able to get eclipse rom installed, but cm12 always does the same thing. I've also gone into the safestrap 3.75 recovery and flashed the twrp 3.8.4.0, it says it was successful, but then I'll reboot, get to the safestrap screen, hit recovery, and it is still the older one with safestrap 3.75, not the updated one I just flashed. If I try to shut down my phone and power on using volume up, home, and power, I get the stock recovery saying that it has detected custom software and blah blah blah. So, I have a bunch of problems and honestly I am not sure what is going on. I have scoured the Web for 3 days now trying to find instructions on updating the recovery, every single one is the same as I described above with the same outcome. I've also been searching for how to install cm12, with the same results. Can anyone help me, I am so annoyed, lost, confused, and just.... please help. Thank you.
Tldr; recovery stuck on safestrap 3.75 regardless of flashing the newer twrp 3.8.4.0, and when trying to reboot into recovery using volume up, home, and power, I get the stock recovery with a message saying custom software detected. Please help.... please. I am on hltevzw with nc4. Rooted with towelroot, and safestrap 3.75.
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
mirrin said:
you have a retail note 3 cm12 is for the dev edition the retail bootloader will only load samsung based firmware note 3 or 4 or the s5 are possible but all with touchwiz running the samsung kernel.
if you had a dev note 3 it has an unlockable bootloader and you needed to unlock that first.
If you had a dev unit and updated it via kies you just turned it into a retail unit permanently...
Click to expand...
Click to collapse
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
danwguy said:
I do have the Verizon version, so no dev ed here, but tamasek has put out a version of cm12 that works on the verizon, sprint, and t-mobile versions of the note 3. I realize it's unofficial and we aren't supposed to post about problems with unofficial builds, but my problem covers more than just cm12 not working. I never knew that tidbit about upgrading via kies ruins dev edition though, that's a trip.
Click to expand...
Click to collapse
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
mirrin said:
Yep kies loads the retail bootloader and since it is the exact same hardware with the exception of an unlock able bootloader and a dev bit flipped the retail bootloader will load to it and flip the dev bit off... it may work or hard brick the unit i can't remember i want to say the unit worked and was for all intents a retail unit after that.
I can't find any thing on a version of cm12 for the retail version also sprint and t-mobile don't count those devices don't have locked bootloader I was looking to confirm but I know the t-mobile one was unlocked looking at the sprint section that one seems like it too.
only att and Verizon locked them... and Verizon has the $ 700 dev units in which all that was done is a bit was flipped and an unlock able bootloader installed.
just found his thread on it yes his cm12 is for dev units on Verizon only...
Click to expand...
Click to collapse
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
danwguy said:
The one I was trying to load up was from here https://s.basketbuild.com/devs/temasek/Samsung Galaxy Note 3 - HLTEVZW/CM12/Old
it's for dev editions only? That is a huge disappointment, I was really hoping to get some android Learn on my phone
Do you have any idea why, after I flash the twrp 3.8.4.0 recovery from safestrap recovery, after I reboot I am still showing safestrap and the older twrp. It's like the new version flashes, but then just disappears and the old version loads up.
Thank you for all your help man, I really appreciate it.
Click to expand...
Click to collapse
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
donc113 said:
Because TWRP doesn't work on the Verizon Note 3...that is why SafeStrap exists. Safestrap is based on TWRP but is not TWRP.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
They exist in different areas of memory safe strap essentially hijacks the boot process before the phone can boot and tells it to instead boot this way if you want to update the version of twrp it us using you need to update safestrap it is what is holding us back from 4.4.4 and it will be what slows 5.0 unless someone updates safestrap or comes up with something new. All I know is I'm going to get a nexus next time I'm done with this locked bootloader bull****.
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
danwguy said:
Thank you guys both for your help. I completely understand what you guys are saying. I guess I got confused because I found an official twrp 3.8.4.0 for hltevzw, so I thought it should work. I'm wondering how hard it would actually be to put the newer version of twrp into safestrap. I know the person that was building it is no longer developing it, so does that mean that we are pretty much not getting 5.0 unless we wait for Verizon to push it?
Click to expand...
Click to collapse
Not necessarily the developers working on jasmine have been claiming to be working on a replacement for safestrap.
Verizon will eventually push out 5.0 but I doubt it will be anytime soon even then if I don't have root I don't want so I am not sure what I'll end up doing I'll try to wait it out maybe a mistake will happen and 5.0 will have some thing that leads to a bl unlock. If only they would make root an option like the dev menu...
and my prediction for when verizon will put out 5.0 I would say October is not out of range. Also it will likely be the note 3's last update that Verizon gives.
I purchased a Verizon branded Note3 quite some time ago. Came to be already rooted on the stock rom.
It started acting a bit funny, and I didn't like it. Figured I might finally try flashing a custom ROM as I did with my Note 1 AT&T.
Followed some directions on custom recovery ( I did confirm that recovery was stock ). Flashed in TWRP with Flashify as per my reading on the forums here. Got the "verizon software not authorized error". Bummer, I guess the bootloader was still locked or something.
I got the phone back into normal operation by going into download mode, and cancelling to reboot. It operates normally until I attempt to access recovery.
What steps do I need to take to either.. (links to proper threads are ok, just need a hint in the right direction)
Unlock the bootloader, flash a recovery and get a custom ROM..
Or simply return to stock recovery for completely normal operation.
-Thanks in advance.
Maybe better luck in Verizon Note 3 forum. Most of us here have international note 3.
Sent from my SM-N920C
I know there threads that cover some of my questions, but I want to make sure I have everything squared away before I go down path.
I currently have a Verizon Galaxy S4 with 4.4.2. It is rooted and has the MDK boot loader. I want to upgrade to 4.5 and use Magisk (mainly so my son can keep playing Pokemon). I am under the impression that to run Magisk I need a non rooted version of 4.5. Am I correct in this impression? Would a stock 4.5 that is Deodexed work with Magisk? Once I find one I can just flash with TWRP and then install magisk correct?
I have 3 main concerns
Don't want to lose the unlocked bootloader.
Don't want to have to wipe the phone.
Want to make sure I can still remove the OTA update app.
jed.padilla said:
I know there threads that cover some of my questions, but I want to make sure I have everything squared away before I go down path.
I currently have a Verizon Galaxy S4 with 4.4.2. It is rooted and has the MDK boot loader. I want to upgrade to 4.5 and use Magisk (mainly so my son can keep playing Pokemon). I am under the impression that to run Magisk I need a non rooted version of 4.5. Am I correct in this impression? Would a stock 4.5 that is Deodexed work with Magisk? Once I find one I can just flash with TWRP and then install magisk correct?
I have 3 main concerns
Don't want to lose the unlocked bootloader.
Don't want to have to wipe the phone.
Want to make sure I can still remove the OTA update app.
Click to expand...
Click to collapse
Well, first of all, there is no android 4.5 as far as I know.
There is 4.4 and then it jumps to 5.0.
Second, your device does not have an unlocked bootloader. Verizon phones pretty much all have a locked bootloader, and no way to unlock them.
Updating to the latest Android might make rooting impossible.
And since your bootloader is locked, Magisk won't work.
GDReaper said:
Well, first of all, there is no android 4.5 as far as I know.
There is 4.4 and then it jumps to 5.0.
Second, your device does not have an unlocked bootloader. Verizon phones pretty much all have a locked bootloader, and no way to unlock them.
Updating to the latest Android might make rooting impossible.
And since your bootloader is locked, Magisk won't work.
Click to expand...
Click to collapse
I was under the impression that MDK was the only unlocked bootloader Verizon ever had. It was only on the first round of phones.
jed.padilla said:
I was under the impression that MDK was the only unlocked bootloader Verizon ever had. It was only on the first round of phones.
Click to expand...
Click to collapse
I'm pretty sure it is locked. It's just easier exploitable.
But I may be wrong.
Edit: Apparently only the Developer Edition has the unlocked bootloader. The MDK is locked.
GDReaper said:
I'm pretty sure it is locked. It's just easier exploitable.
But I may be wrong.
Edit: Apparently only the Developer Edition has the unlocked bootloader. The MDK is locked.
Click to expand...
Click to collapse
So at this point my options are update the phone to something else with no root so I can continue to play.
Leave my phone rooted and no longer play.
jed.padilla said:
So at this point my options are update the phone to something else with no root so I can continue to play.
Leave my phone rooted and no longer play.
Click to expand...
Click to collapse
There was a way to "hide root", other than Magisk.
But it's a real pain. You'd have to go into recovery and type some terminal commands each time you want to hide root, and then go back into recovery and undo everything once you want to get root back.
GDReaper said:
There was a way to "hide root", other than Magisk.
But it's a real pain. You'd have to go into recovery and type some terminal commands each time you want to hide root, and then go back into recovery and undo everything once you want to get root back.
Click to expand...
Click to collapse
Well that is a big fat meh then. Thanks for the help.
I have a Sprint Galaxy S7 Edge SM-G935P running on 7.0 and have been looking for a way to root my device. I was looking around the cf autoroot website and you can customize your own root package for your device. They list my device on there and it lets me build an odin flashable root package for it. Will this work? Or will it brick my device? It even lets me pick the exact device, and android security patch level and build version that is currently installed on my phone. Ive read that this phone has a locked bootloader that is locked down tight and its hard to get unlocked. This says
BOOTLOADER UNLOCK
If your bootloader is not unlocked, depending on the device, it may be automatically unlocked (wiping all data), flashing may fail, or the device may brick altogether.
So will it unlock my bootloader and root my phone? or will it not work? I havent seen anything about this method when i just google "sprint galaxy s7 edge root" and i dont see anything about it on this forum, i figure if it worked that more people would be talking about it and using it. Any advice? should i try it? it also gives links to the stock boot and recovery images, and i also have a copy of them saved on my pc.
give it a try, the worst thing that will happen is you will brick your device. Then you will have to play dump and get it replaced.
BDog21 said:
I have a Sprint Galaxy S7 Edge SM-G935P running on 7.0 and have been looking for a way to root my device. I was looking around the cf autoroot website and you can customize your own root package for your device. They list my device on there and it lets me build an odin flashable root package for it. Will this work? Or will it brick my device? It even lets me pick the exact device, and android security patch level and build version that is currently installed on my phone. Ive read that this phone has a locked bootloader that is locked down tight and its hard to get unlocked. This says
BOOTLOADER UNLOCK
If your bootloader is not unlocked, depending on the device, it may be automatically unlocked (wiping all data), flashing may fail, or the device may brick altogether.
So will it unlock my bootloader and root my phone? or will it not work? I havent seen anything about this method when i just google "sprint galaxy s7 edge root" and i dont see anything about it on this forum, i figure if it worked that more people would be talking about it and using it. Any advice? should i try it? it also gives links to the stock boot and recovery images, and i also have a copy of them saved on my pc.
Click to expand...
Click to collapse
It won't work. There is a thread here about rooting. You need a special boot image and it is unstable.
The latestThread for easy rooting appears to be here
https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969