So I saw on rootzwiki we should be getting kit kat starting may 23 or something. What do I have to do to retain root? I'm on mostly stock vruemj9 with some xposed framework. I don't wanna brick it. Should I just Un root and hope for a new exploit? Should I look at note 3 updates with root? Any advice would be excellent. Also, if there is a way to unlock the BL during this process that would be excellen as well.
cb
Sent from my rooted, xposed, and locked Verizon note 2.
Every thread to your question always said to avoid otas. So I would just wait until they come up with an exploit. Who knows maybe with this new update it will unlock our bootloader.
Sent from my SCH-I605 using Tapatalk
Freeze SDM 1.0 to block the update until we see what is up. I don't think the bootloader will be unlocked and other Sammy phones on kit kat are having a hard time getting root.
Okay sounds good. Are there any free apps that do freezing?
Sent from my rooted, xposed, and locked Verizon note 2.
Is that confirmed or speculations? The May 23rd date?
The guy on rootzwiki said it was a reliable source.
Sent from my rooted, xposed, and locked Verizon note 2.
chuckbeez said:
Okay sounds good. Are there any free apps that do freezing?
Sent from my rooted, xposed, and locked Verizon note 2.
Click to expand...
Click to collapse
I don't know of any, I own titanium backup and use that.
International version rolling out now. Glad to know something is coming!
http://pocketnow.com/2014/04/25/galaxy-note-ii-android-4-4-kitkat-update
coolpoete said:
International version rolling out now. Glad to know something is coming!
http://pocketnow.com/2014/04/25/galaxy-note-ii-android-4-4-kitkat-update
Click to expand...
Click to collapse
Finally! I saw that too and got on the xda asap!
I'm in the exact same situation as the OP (apart from having a UK note 2) I want to give kitkat a go but want to keep root and avoid tripping knox...so I'm waiting and watching. But I'm impatient lol
Related
OK. I am going to provide as much detail as I can for now. Please let me know what additional information will help you help me. Thanks
I have a S4 for Verizon. I have been trying to root it so I can load the Google edition image on it. However, none of the tutorials I have seen seem to work on my device. I bought it brand new direct from Samsung off contract (didn't want to loose my unlimited data) so I don't think I can get a warranty replacement through Verizon (haven't rooted it yet). The furthest I seem to get is that SuperSU gets installed but will not download the binaries. So I cannot continue with the rest if the steps with rooting and re-imaging. Also, most steps have you install a specific kernal version as the first step but not sure if that is happening because my screen don't look the same as the ones in the tutorials.
Phone: SCH-1545
OS ver: 4.3
Kernal: 3.4.0
Build: JSS15J.1545VRUEMJ7
HW ver: 1545.06
Thanks.
http://forum.xda-developers.com/showthread.php?t=2531704
http://forum.xda-developers.com/showthread.php?t=2550383
Sent from The new iPad using Tapatalk HD
rsalas187 said:
http://forum.xda-developers.com/showthread.php?t=2531704
http://forum.xda-developers.com/showthread.php?t=2550383
Sent from The new iPad using Tapatalk HD
Click to expand...
Click to collapse
I will check those out. Thanks for the quick response. :good:
Just so you know, the only thing available for MJ7 build is root. Installing a custom recovery or custom ROMs is not possible at this time.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
Just so you know, the only thing available for MJ7 build is root. Installing a custom recovery or custom ROMs is not possible at this time.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Are you certain? Other people seem to be imaging their Verizon devices with the Google Edition images. Thanks
deathtical said:
Are you certain? Other people seem to be imaging their Verizon devices with the Google Edition images. Thanks
Click to expand...
Click to collapse
Not with MJ7 firmware they aren't.
If you didn't buy a developer edition, you my friend, are screwed.
tech_head said:
Not with MJ7 firmware they aren't.
If you didn't buy a developer edition, you my friend, are screwed.
Click to expand...
Click to collapse
Typical. Is there no way to flash it with a different firmware so that I can do more with it? Thanks
deathtical said:
Typical. Is there no way to flash it with a different firmware so that I can do more with it? Thanks
Click to expand...
Click to collapse
No. Once the phone is updated, there is no way to go back.
As I stated above, all we can do is root. With root we can debloat and use Xposed framework to make some changes.
riker147 said:
No. Once the phone is updated, there is no way to go back.
As I stated above, all we can do is root. With root we can debloat and use Xposed framework to make some changes.
Click to expand...
Click to collapse
That doesn't really accomplish what I want though. Not your fault obviously. Do you know if this is a Verzion thing or just the device itself? Thanks
deathtical said:
That doesn't really accomplish what I want though. Not your fault obviously. Do you know if this is a Verzion thing or just the device itself? Thanks
Click to expand...
Click to collapse
It's Verizon, they lock down every phone they sell. You have to do research before you buy your phone if you want custom software on Verizon, or switch carriers.
joshm.1219 said:
It's Verizon, they lock down every phone they sell. You have to do research before you buy your phone if you want custom software on Verizon, or switch carriers.
Click to expand...
Click to collapse
I know Verzon sucks in that regard but the service is awesome. I get full 4G coverage just about everywhere and I've got unlimited data still. Plus, I didn't buy it from them, I payed full price from an online vendor so that I wouldn't have to change my contract.
Oh well, guess I'll just have to keep an eye out for when someone finally cracks it.
I hate waiting....
All,
I have the Verizon Galaxy S4 Developer Edition. I purchased this one b/c it had an unlocked bootloader and I like to install custom recoveries so I can install custom ROMs. Originally, it came with the MDK firmware on it and I was able to root it and install a custom recovery.
I applied the OTA MJ7 update. While I am able to root the device, I have not been able to install a custom recovery. After doing a ton of reading and soft bricking, everyone says that the latest firmware locks down the bootloader so that you cannot install custom recoveries.
Here lies my confusion...I bought the Developer Edition so my bootloader would never be locked and I could always install custom recoveries. Is there something I'm missing? Is it possible for me having a Developer Edition phone to install a custom recovery even though I'm on build I545VRUEMJ7?
In talking with Samsung support, they said that the bootloader will NEVER be locked with any updates on the Developer edition. Any information or help is much appreciated.
Thanks,
Jonathan
Where did you purchase it from?
Sent from my SCH-I545 using xda app-developers app
richii0207 said:
Where did you purchase it from?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I purchased it directly from the Samsung website. I tried to post the link but it wouldn't let me since I haven't made enough posts. If you google "galaxy s4 developer edition", it is the first non-advertised link that shows up. That's where I purchased it from.
If you take the cover and battery out, it says Developer Edition on the phone.
jontjioe said:
I purchased it directly from the Samsung website. I tried to post the link but it wouldn't let me since I haven't made enough posts. If you google "galaxy s4 developer edition", it is the first non-advertised link that shows up. That's where I purchased it from.
If you take the cover and battery out, it says Developer Edition on the phone.
Click to expand...
Click to collapse
As i understand it when you took the update it locked your bootloader, but please anyone correct me if im wrong
See that's what I thought too... That the update possibly locked my bootloader but how can I check if it is locked or not?
Sent from my SCH-I545 using xda app-developers app
michaelg117 said:
As i understand it when you took the update it locked your bootloader, but please anyone correct me if im wrong
Click to expand...
Click to collapse
Thats what I've heard too. I'm no expert in the Dev S4, but I think I've seen a thread or two stating the same kind of problem. Which is crazy if you ask me.
Edit
I know Surge1223 I think posted the Dev Edition MDK firmware somewhere on here, I suggest maybe checking with him, maybe you can flash that back in your phone and be good?!
If nothing else, find that thread and ask him what to do... My guess is he'll have an answer for you.
I've read that it can re lock your phone and ive also read that the updates will not lock it up.... So I'm not really sure.
Good luck though!!!
Sent from my SCH-I545 using XDA Premium 4 mobile app
jontjioe said:
See that's what I thought too... That the update possibly locked my bootloader but how can I check if it is locked or not?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
If you took the OTA, you no longer have the same bootloader and in effect locked the bootloader on your phone. Far as I know.
safestrap enabled, Hyperdrive driven
jontjioe said:
All,
I have the Verizon Galaxy S4 Developer Edition. I purchased this one b/c it had an unlocked bootloader and I like to install custom recoveries so I can install custom ROMs. Originally, it came with the MDK firmware on it and I was able to root it and install a custom recovery.
I applied the OTA MJ7 update. While I am able to root the device, I have not been able to install a custom recovery. After doing a ton of reading and soft bricking, everyone says that the latest firmware locks down the bootloader so that you cannot install custom recoveries.
Here lies my confusion...I bought the Developer Edition so my bootloader would never be locked and I could always install custom recoveries. Is there something I'm missing? Is it possible for me having a Developer Edition phone to install a custom recovery even though I'm on build I545VRUEMJ7?
In talking with Samsung support, they said that the bootloader will NEVER be locked with any updates on the Developer edition. Any information or help is much appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
You locked your bootloader.
You used ODIN to install a MJ7 OTA file?
Consumer firmware can be installed on a Dev. edition, but it locks the bootloader.
They should have said something about that. They didn't?
I don't think you are going to get anywhere with support unless you send the phone back for a replacement. IMHO
tech_head said:
You locked your bootloader.
You used ODIN to install a MJ7 OTA file?
Consumer firmware can be installed on a Dev. edition, but it locks the bootloader.
They should have said something about that. They didn't?
I don't think you are going to get anywhere with support unless you send the phone back for a replacement. IMHO
Click to expand...
Click to collapse
Yeah, I used ODIN to flash MJ7. Sucks. I will just have to be more patient next time and not flash the latest thing right away. Seems like it is taking forever for someone to crack this bootloader.
jontjioe said:
Yeah, I used ODIN to flash MJ7. Sucks. I will just have to be more patient next time and not flash the latest thing right away. Seems like it is taking forever for someone to crack this bootloader.
Click to expand...
Click to collapse
most likely, the bootloader won't be cracked. Too much security in place
decaturbob said:
most likely, the bootloader won't be cracked. Too much security in place
Click to expand...
Click to collapse
How bad is it that people like him hey a Dev Edition that SHOULD always stay unlocked in my opinion, then are able to lock it back up?!?!
To me that's ridiculous. I'd be more than pissed if that was me.
There was a thread somewhere on here containing a conversation between that person and Samsung I think, and the Sammy rep told that person that the Dev Edition would never be locked even through any OTA.
Seems like such a circle jerk dealing with those people, I've fired off a couple emails myself just for laughs to Samsung about various things, and that's all they do is BS us.
What a shame, a Dev S4 that is just like my locked up mj7 S4.
Sent from my SCH-I545 using XDA Premium 4 mobile app
I am an owner of a DevS4. What the OP did was definitely not a good thing. The DevS4 came originally with I545OYUAMDK. The retail S4 came with I545VRUAMDK. The only difference is that the DevS4 has a different ABOOT partition which allows for the unlocking. By applying the MJ7 OTA or ODIN file he essentially over-wrote his ABOOT partition, locking his phone down and turning it into a regular retail S4. The DevS4's are now sold with I545OYUEMJ7 - he applied I545VRUEMJ7. Unless Samsung will help him out by flashing the firmware to his phone so he can go back to Developer state, he is SOL with a DevS4 now turned into a locked down retail S4.
I only say this based on what I have seen/witnessed.
I've seen this happen before and Samsung took the phone and flashed the correct firmware, not saying you'll be so lucky but search around and you may find what I'm remembering.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Crazy. Dev edition phones should have an efuse that prevents locking. Trying to flash locked firmware should fail.
Sent from my SCH-I545 using Tapatalk
tech_head said:
Crazy. Dev edition phones should have an efuse that prevents locking. Trying to flash locked firmware should fail.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Exactly. Lot of money for something that can easily be screwed up.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Just goes to show they don't have a real interest in a Dev device.
Sent from my SCH-I545 using Tapatalk
tech_head said:
Just goes to show they don't have a real interest in a Dev device.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Not so sure if it a case of not having interest, I just don't think they thought it out fully. They produced them and spent the money investing in it. There is a Note 3 Developer edition as well. They just didn't fully think out the implications of support, updating, etc. Which is a shame. The Samsung Developer Device program could have been huge if it was executed properly. To take a retail device, change a few letters from "VRE" to "OYU", slap a sticker on it and call it a developer device, while it still contains KNOX and other developer unfriendly aspects was poor execution.
Maybe there should be a caution sticky here to not ODIN Consumer Ed images onto Dev Ed devices.
Its odd that Samsung even has this program but I guess they want devs to create Samsung Apps for carrier devices.
Skeetch79 said:
Not so sure if it a case of not having interest, I just don't think they thought it out fully. They produced them and spent the money investing in it. There is a Note 3 Developer edition as well. They just didn't fully think out the implications of support, updating, etc. Which is a shame. The Samsung Developer Device program could have been huge if it was executed properly. To take a retail device, change a few letters from "VRE" to "OYU", slap a sticker on it and call it a developer device, while it still contains KNOX and other developer unfriendly aspects was poor execution.
Click to expand...
Click to collapse
DEV owners gotta understand wtf they are doing
Listen I feel sorry for the OP but it's completely his fault for flashing a consumer device image. I know if I were Samsung I wouldn't expect people who buy DEVELOPER editions to do something as silly as that.
Sent from my SCH-I545 using XDA Premium 4 mobile app
So I did a little searching before posting so don't ream me please ??
1) Does the dev edition s4 also have a locked bootloader? That would be f'in whack.. If it us unlocked and my second q doesn't pan I may try and swoop one up. ..
2) I have a friend with a tmobile s4 that he cracked the digitizer and just reported it lost... If I took his board could I unlock it to big red? If so what would be the consequences?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Zooandbio4me said:
So I did a little searching before posting so don't ream me please ??
1) Does the dev edition s4 also have a locked bootloader? That would be f'in whack.. If it us unlocked and my second q doesn't pan I may try and swoop one up. ..
2) I have a friend with a tmobile s4 that he cracked the digitizer and just reported it lost... If I took his board could I unlock it to big red? If so what would be the consequences?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The Dev Edition S4 normally does not have a locked bootloader. I say normally because some users took an Over The Air update which did lock the bootloader. So it depends on whether the bootloader is a stock MDK bootloader or if the user took a subsequent OTA update which in turn locked / changed the bootloader. Also, there is no factor image for the Dev Edition, so if it is locked it is going to stay locked for the foreseeable future. As for your second question, I'm not sure that will work. I think the firmware differences between TMO and Verizon plus the difference between GSM and CDMA will not be easy to overcome. But I don't know that for sure.
I'm not trying to be a know it all trust me lol but the dev s4 never got otas I don't believe. The users who locked then up did so by using Odin and retail firmware.
Just throwing that out there.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I'm not trying to be a know it all trust me lol but the dev s4 never got otas I don't believe. The users who locked then up did so by using Odin and retail firmware.
Just throwing that out there.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I don't take that as you being a know it all, you're probably right. I just know some Dev owners did something to lock their bootloaders I just assumed (wrongfully) that it was an OTA of some sorts. Sorry for the misinformation.
Mistertac said:
I'm not trying to be a know it all trust me lol but the dev s4 never got otas I don't believe.
Click to expand...
Click to collapse
I know one user who received his DevEd about the same time as me. He received an OTA that locked his bootloader. I have never received an OTA, and I'm still running stock (more or less) DevEd.
It's funny how I bought the DevEd, because I wanted a guarantee that I could ROM the device. But I fell in love with the stock OS, and don't care if I ever have KitKat.
asharad said:
I know one user who received his DevEd about the same time as me. He received an OTA that locked his bootloader. I have never received an OTA, and I'm still running stock (more or less) DevEd.
It's funny how I bought the DevEd, because I wanted a guarantee that I could ROM the device. But I fell in love with the stock OS, and don't care if I ever have KitKat.
Click to expand...
Click to collapse
No kidding? I didn't know any of them got OTAs. At least you have the option to flash whatever you want if you did get bored with stock.
Sent from my SCH-I545 using Tapatalk
Hot off the press, this was just leaked by SXTP-Developers can anybody bring this baby over to the Verizon Note 3?
Here's the link http://sxtpdevelopers.com/samsung-sch-i545-verizon-kit-kat/
KachowPow said:
Hot off the press, this was just leaked by SXTP-Developers can anybody bring this baby over to the Verizon Note 3?
Here's the link http://sxtpdevelopers.com/samsung-sch-i545-verizon-kit-kat/
Click to expand...
Click to collapse
We probably don't have to worry much about bringing it to the Note 3 as I'm sure KK for our phone isn't too far behind. About damn time we see something!
Sent from my SM-N900V using Tapatalk
mlin said:
We probably don't have to worry much about bringing it to the Note 3 as I'm sure KK for our phone isn't too far behind. About damn time we see something!
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Wouldn't it be a much safer approach to bring this S4 leaked version over to our Note 3? I mean you could be right KK for the Note 3 might be just around the corner, but what if that version of KK has a similar affect as the version that AT&T received, where the update wiped out Root and there was no way to restore it. Maybe that is something that is just going to happen with the Verizon KK update, Root will be lost, and the bounties will raise again. If you ask me, what if we take a look at the S4 KK leaked ROM and see if it is something that can be ported over to the Note 3, maybe it can, maybe there's a way to keep Root and enjoy KitKat.
KachowPow said:
Wouldn't it be a much safer approach to bring this S4 leaked version over to our Note 3? I mean you could be right KK for the Note 3 might be just around the corner, but what if that version of KK has a similar affect as the version that AT&T received, where the update wiped out Root and there was no way to restore it. Maybe that is something that is just going to happen with the Verizon KK update, Root will be lost, and the bounties will raise again. If you ask me, what if we take a look at the S4 KK leaked ROM and see if it is something that can be ported over to the Note 3, maybe it can, maybe there's a way to keep Root and enjoy KitKat.
Click to expand...
Click to collapse
I guess I don't know about obtaining root on a stock AT&T KK Note 3, but it seems there are plenty of custom, rooted ROMs based off the newest release. Porting a new version of android without the kernel (for those of us using SS) just seems like it'd be a lot of work and a PITA. Admittedly, I don't know much about this stuff so it may be more straight forward than I know.
Sent from my SM-N900V using Tapatalk
Would it be possible use a stock KitKat ROM from another carrier such as Sprint, extract the radio, then insert the Verizon radio from S4 leak? I don't know much about ROM building or porting a ROM, but I know you need the correct radios to get it to work properly, maybe if cross-build with what is already available something should work right? and I hope on the retail version side of things...
When you start tweaking like that, it's becomes no longer signed, and then it won't flash. Plus I think the kernel is different, which is an automatic stop, as we can't flash different ones.
Sent from my SM-N900V using xda app-developers app
I'd think that the biggest issue with porting an S4 ROM to the Note 3 would be S-Pen support. Is that not a concern?
Personally I would try to use a Canadian 4.4 Rom since we have had the update for over a month now up here
Sent from my SM-N900W8 using xda app-developers app
Borderpatrol1987 said:
When you start tweaking like that, it's becomes no longer signed, and then it won't flash. Plus I think the kernel is different, which is an automatic stop, as we can't flash different ones.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
SafeStrap ignores the boot.img even if present, so it can't get flashed on a retail N3.
Anything to note on the S4 leak such as root methods and what not?
The note 3 tar was posted on their site and in another thread. No root exploit is publicly available yet.
Sent from my SM-N900V using Tapatalk
Still No Root?? Ugh. :banghead:
Sent from my SCH-I545 using XDA Free mobile app
No.
That's why if one wants to update, they do it with a way back.
Ugh :banghead::thumbup:
Sent from my SCH-I545 using XDA Free mobile app
How about this?
androidsdna.com/root-verizon-galaxy-s4-i545-on-5-0-1-lollipop-and-enable-tethering
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Murcus said:
How about this?
androidsdna.com/root-verizon-galaxy-s4-i545-on-5-0-1-lollipop-and-enable-tethering
Click to expand...
Click to collapse
Nevermind, those download links are dead.
PingPong Root almost worked on my device....but doesn't root. You may want to help them get us on track!
I think we r going to be stuck wit no root method for OC1 update :/ I'm starting to lose hope.
Me to I'm Starting To Lose Hope.
Sent from my SCH-I545 using XDA Free mobile app
You could buy an MDK model.
spotmark said:
You could buy an MDK model.
Click to expand...
Click to collapse
Well true. But my next phone will be a note a developer edition phone. I mostly use my phone for wifi hotspot. But I'm guessing I will have to buy foxfi it works. But I was trying to avoid it buying the version. And hoping to get root back.
Root
I too have messed up ,installed Lollipop . I have an s4 I545. Now I think Before I get the next phone I will check to see if it is rootable.
What I don't understand is if we can root the s6 Why wouldn't it work on the s4? Am I missing something?
Thanks
traco1 said:
I too have messed up ,installed Lollipop . I have an s4 I545. Now I think Before I get the next phone I will check to see if it is rootable.
What I don't understand is if we can root the s6 Why wouldn't it work on the s4? Am I missing something?
Thanks
Click to expand...
Click to collapse
I'm guessing different chips then s6 uses the exynos 64 bit and the s4 uses snapdragon 32bit.
Ikr It's Weird That We can root the s6 but not the vzw s4 it turns out pingpongroot supports kernels built before may 15 and are kernel was built March 30 so it's probaly possible that the exploit pingpongroot uses would exist in our phones just a guess though are kernels are different of course it's a possibility
I read somewhere that there will be a lollipop 5.1 update by the end of July but it's unofficial if that's true
Bren123 said:
Ikr It's Weird That We can root the s6 but not the vzw s4 it turns out pingpongroot supports kernels built before may 15 and are kernel was built March 30 so it's probaly possible that the exploit pingpongroot uses would exist in our phones just a guess though are kernels are different of course it's a possibility
Click to expand...
Click to collapse
Yes I see where u going but also look at note 4. It still can't get root. And it's been how many months it's been out.
I'm sure if that update does come out there probably going to mess something up in that update but it's suprising the note 4 still doesn't have root you would think the note 4 would already have root it's not like the s4 that's almost 2 years old
Bren123 said:
I read somewhere that there will be a lollipop 5.1 update by the end of July but it's unofficial if that's true
Click to expand...
Click to collapse
If, and that is a pretty good IF, they update the S4 to 5.1 Verizon's version will never see it. Verizon is just too lazy and only care about their cash. I was surprised to see us get 5.0
They may both be lollipop, but have different code. Also, this update was sent AFTER the s6 exploit, meaning Samsung/Verizon had time to patch it. Therefore, the same method won't work.