The Op was updated before you even made this commentAlright then, unless you guys are going to dig around to see if there is a workaround, you might as well update OP to let AT&T users this isn't possible.
The Op was updated before you even made this commentAlright then, unless you guys are going to dig around to see if there is a workaround, you might as well update OP to let AT&T users this isn't possible.
Are you always so hostile? Thanks for the work you put in but man, change your tampon.The Op was updated before you even made this comment
You misunderstood me. I ran both methods, once each, but people were saying you have to run the commands twice, which is what I was stating I did.First contrary to popular belief, I am female
Second, when you waltz into a thread all "I'm not a noob, but i decided to run both methods twice" Everyone's gonna look at you stupid....
Just making the kiddo some breakfast, then I'll get on it.^ Hey @N4styN1ghtm4r3 Pull your aboot if you would be so kind for @ryanbg
I'm 100% sure it's just this command in terminal emulator
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.mdn
correct me if it's wrong
I'm on OK3 too and tried flashing the PB1 modem using ODIN from the CM13 thread and it doesn't look like it took either.Has anyone else noticed you cant flash any firmware. I tried changing the modem and it will not flash. I pulled the plug and flashed PB1 full factory tar image and it flashed the system, boot and recovery images but it did not flash any bootloaders, firmware or modems. After full factory tar image flash in odin I still have an unlocked phone, which I should not. Do you have any input @beaups. Should this have relocked the bootloader.
Beaups has responded that there's a method to getting it to unprotect the partition to accept it. read backI'm on OK3 too and tried flashing the PB1 modem using ODIN from the CM13 thread and it doesn't look like it took either.
You can't flash the bootchain of other devices. Only boot/recovery/systemI unlocked my bootloader but i'm trying to flash a tmobile ota and i get this:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> rpm.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
Appears the key is different for ATT. That's really interesting since they never released a Developer Edition for ATT.Beaups has responded that there's a method to getting it to unprotect the partition to accept it. read back
Also @ryanbg, your aboot is here
So i should take everything out except for boot.img, recovery.img, system.img.ext4? I dont really know what all the files are for, just trying to avoid brick.You can't flash the bootchain of other devices. Only boot/recovery/system
So we're out of luck then?You can't flash the bootchain of other devices. Only boot/recovery/system
---------- Post added at 09:38 AM ---------- Previous post was at 09:34 AM ----------
Appears the key is different for ATT. That's really interesting since they never released a Developer Edition for ATT.
I think so unfortunately, unless we come across what we need.So we're out of luck then?
I advise against doing this. Just flash a custom rom. You can do this, but it might not work as expected.So i should take everything out except for boot.img, recovery.img, system.img.ext4? I dont really know what all the files are for, just trying to avoid brick.
Hypothetical question, if i'm on the OC4 bootloader(no OTA's since OC4) and running the PB1 firmware or just kernel and do the unlock method. Would you or anyone else know what the bootloader would be at? Just asking to give questionable ideas/thoughts to what JrKruse had posted. Just reading these posts day by day before i take the "plunge" for everything to "pan" out I'm currently running MOAR with OC4 firmware... Awesome Dev's with a community coming together..:good:Beaups has responded that there's a method to getting it to unprotect the partition to accept it. read back
Also @ryanbg, your aboot is here
I'd assume the 'dev edition' firmware variant att s5s need is probably some factory firmware, or might not even exist, the check is just simply in there because it was never taken out. Either way, chances are looking slimmer and slimmer for att folks :/I think so unfortunately, unless we come across what we need.
---------- Post added at 09:46 AM ---------- Previous post was at 09:45 AM ----------
I advise against doing this. Just flash a custom rom. You can do this, but it might not work as expected.
Whatever bootloader you're on, it'll remain the same.Hypothetical question, if i'm on the OC4 bootloader(no OTA's since OC4) and running the PB1 firmware or just kernel and do the unlock method. Would you or anyone else know what the bootloader would be at? Just asking to give questionable ideas/thoughts to what JrKruse had posted. Just reading these posts day by day before i take the "plunge" for everything to "pan" out I'm currently running MOAR with OC4 firmware... Awesome Dev's with a community coming together..:good: