42 replies to this topic

[Captain Crypto]

Double post from the DEV board, which is pretty lonely with just my post.  Not sure where to post this question:

 

Is the S4 Dev bootloader actually write protected, so that it can't be accidentally locked?  I'm asking now so that I know how much of a comfort level I can allow myself while I'm messing around learning about this thing.

[livinginkaos]

It's hardware unlocked so you have no worries. Double response. How do you like them apples.

From My S4 Dev Edition

[Captain Crypto]

It's hardware unlocked so you have no worries. Double response. How do you like them apples.

From My S4 Dev Edition

Awesome!  Thanks.  Doubly.

[sparky697]

So does that mean we can use the commercial version tar to Odin back to stock with no issues? I noticed there is no factory tar for the dev.

Sent from my SCH-I545 using Tapatalk 4

[livinginkaos]

IDK if anyone has done that yet. I am sure you can, they are both MDK and have the same kernal version. The only thing I can think is that there is just something up with the updater. Because the dev ed. are on MDK and don't show an update, but the non-dev's have the ME7.

[rickw]

the stock dev edition is running a different kernel,when i flash a rom i have to flash a kernel with it

[SamuriHL]

Yea don't do that.  They are very much a different version.  Flashing the commercial version on your dev edition == bad idea.  Someone should pull the partitions on the dev edition and make an odin tar from it.

[livinginkaos]

There's a deodex tar out there . That's odd because my dev stock has the same kernal??? Only the build#/baseband have the OY instead of the VR

From My S4 Dev Edition

[SamuriHL]

I bet if you dd extract it it won't end up being the same as one from a commercial phone when compared.

[livinginkaos]

Why would they give them the same kernal # if they are different? That would be stupid. Do you know what block it is? I can pull them both tonight.

From My S4 Dev Edition

[SamuriHL]

do it by name.  I'll find the exact path in a minute.

[SamuriHL]

/dev/block/partition/msm_sdcc.1/by-name/boot

 

the by-name dir lists all the partitions and is handy as hell.

[livinginkaos]

Ok Thanks. I knew how to do that on moto

From My S4 Dev Edition

[rickw]

i have been looking all over the net looking for stock tar for dev edition

[SamuriHL]

Kaos isn't quite remembering all his Android training which is why I want him to go through this exercise.  Same kernel?  Ok, maybe I buy that.  Same signing keys used on the dev edition vs consumer edition?    Shhhh, don't tell him.  

[rickw]

[soocold]

alright, no more double sections. i already took care of the other thread.

 

ENJOY

[sparky697]

I'm trying to be good and not flash too many different things on here til I can get a stock tar. I have my stock backup, that has already saved my butt, but tar would be much better.

Sent from my SCH-I545 using Tapatalk 4

[SamuriHL]

You guys have got to learn how to make one.  You have to extract all the stock partitions first.  Then once you have them, you basically create a tar md5 using cygwin, adding the partitions in the correct order (which I don't know offhand but can probably find out) to the tar.  Getting an official leaked one from Samsung is what I like to call "unlikely".

[sparky697]

I'm gonna look into that this weekend if I get a chance. Now that I have an unlocked phone I should know how to fix it when I inevitably screw it up.

Sent from my SCH-I545 using Tapatalk 4