Welp... Anyone on my rooted OF1/lower want to experiment?

trailblazer101

Senior Member
Dec 17, 2010
926
782
123
Pennsylvania
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...

Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.

I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
 

Scott

Retired Recognized Developer
Feb 20, 2007
29,233
66,256
263
Fargo
www.scottcrosler.com
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...

Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.

I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
Actually, I have been thinking about this myself and I agree with your observations...

In addition to... I think its a vendor partition that holds this info and it can surely be changed some how. I noticed it the same way you did however, I used a "loaner" device from VZW. I thought I had power button issues but nothing a good cleaning with Canned air cant fix. So I sent the "loaner" back (which BTW could not boot because of all the testing I did) and just let the process go. However, now that I have seen your post (which I agree with) you either

A. Solidified my thought process :)
B. Guessed and theorized for 7 days with a loaner phone ;) lol, like I did...

Either way... I think we are both looking at this the same. And I think it has to do with the kernel build date. I will tear down the boot.img tomorrow and see what I can figure out.
 
Last edited:

elliwigy

Forum Moderator / Recognized Developer
Staff member
Mar 16, 2011
12,983
8,844
253
Phoenix
www.sampwnd.com
Actually, I have been thinking about this myself and I agree with your observations...

In addition to... I think its a vendor partition that holds this info and it can surely be changed some how. I noticed it the same way you did however, I used a "loaner" device from VZW. I thought I had power button issues but nothing a good cleaning with Canned air cant fix. So I sent the "loaner" back (which BTW could not boot because of all the testing I did) and just let the process go. However, now that I have seen your post (which I agree with) you either

A. Solidified my thought process :)
B. Guessed and theorized for 7 days with a loaner phone ;) lol, like I did...

Either way... I think we are both looking at this the same. And I think it has to do with the kernel build date. I will tear down the boot.img tomorrow and see what I can figure out.
i currently have a vzw s6 on og5 that ill be sending back.. unfortunately it wont help the cause..

i figured it would not work but worth a shot.. hopefully someone willing to sacrifice root potentially will take the dive :-/..

you guys are more experienced with android than i am for sure!

Extreme Syndicate L
 

TechBSwift

Senior Member
Jul 14, 2010
2,495
1,386
0
i currently have a vzw s6 on og5 that ill be sending back.. unfortunately it wont help the cause..

i figured it would not work but worth a shot.. hopefully someone willing to sacrifice root potentially will take the dive :-/..

you guys are more experienced with android than i am for sure!

Extreme Syndicate L
I'm considering getting rid of s6 edge in the next couple of days. If my plan comes through I will test your theory prior to selling my phone

Sent from my SM-G925V using Xparent Green Tapatalk 2
 

unctarheel87

Member
Mar 18, 2015
5
5
0
So in the process of developing a rooted OG5, I locked myself out with the new bootloader.
Details, for those interested: I wanted to get everything (kernel, bootloader, etc) on OF1, since it's the easiest way to patch things, and I have only been on OF1 system + modem. So I made a OF1 flashable package including everything except system, which I left as a stock not-cleaned odexed rooted build I through together. Well it flashed fine, but upon boot it recognized that the system was of the old SYS_MAGIC value (1 as compared to 2), so.... yeah. It wouldn't let me boot. I should've thought ahead, so it's my fault, but...

Okay, so what I would want for someone on my rooted OF1 (if lower, move up to my OF1, not the official!) to try something that may work, but probably not. At the very end of the stock OF1 (and OG5) update package it updates that SYS_MAGIC value to 2, so you can't go down to anything 1 (OE2, OC3, etc). But if we're rooted maybe we could use FlashFire to flash a custom made package that ONLY includes this magic updater. command This would leave the system on my rooted OF1, but allow booting when flashing everything else (kernel, bootloader, etc). It's a two step process, though, because if it works (ONLY if it does, which you'll know) you'll need to flash all that other stuff right away/after.

I have packages ready, but I won't post them here because this is gray territory... It won't break anything permanently, but there's always a slim chance you'd have to flash a full OF1 package, losing root. so If you're okay with that, message me. Mine as well try, since there isn't anything else I can do anymore...
I'd be happy to test this out; I don't mind losing root if it comes to that.
 

compywiz

Senior Member
Mar 12, 2010
90
8
0
Have you guys heard any news? Unfortunately, I am pretty close to being done with using the old software version and the bugs it comes with, just to retain root.

It's really nice to have, but with (hopefully) Samsung Pay around the corner, I'm likely going to be throwing in the towel since it will require a software update.
 

elliwigy

Forum Moderator / Recognized Developer
Staff member
Mar 16, 2011
12,983
8,844
253
Phoenix
www.sampwnd.com
its not a matter if anyone is working on root for of1 since roots are typically exploits in the android os so new root methods are typically based on OS... for example, if root is done for android 5.1 it might work on OG5 5.1 for us..

known exploits for 5.0 were patched in OFx firmwares so new exploits need to be found in general.

Sent from my SM-G925V using XDA Free mobile app
 

supersmash19

Senior Member
Apr 18, 2015
123
36
0
Brooklyn
Would love to know if this worked. I really want to update to 5.1.1 and see how it is for myself but don't want to lose the ability to downgrade again. I may end up just doing it anyways though so I might as well test this in the process. I've been seeing that no one's gotten a response though

Sent from my SM-G920V using XDA Free mobile app