yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 Android Development] Legitsu:
ill have 3 CID 15s in friday and a couple of CID11's

two of the 15's are spoken for
[Verizon Galaxy S 5 Android Development] GeTex:
I'm looking to trade my my other 11 for a 15, also AL50 I just got rid of my spare screen :(
[Verizon Galaxy S 5 Android Development] al50:
Darn, wish I'd known..... :( been looking for one for a few months now....that or or bricked/hardware damaged device....no extra funds have put a damper on things.....hopefully something will luckily happen....:o
[Verizon Galaxy S 5 Android Development] bubbaclubba:
CID11 chip exploit...

Has anyone found an exploit for the CID 11 chips? I read thru everything did I miss something?
[Verizon Galaxy S 5 Android Development] Legitsu:
nope CID11 devices are SOL limited to safestrap only roms and NO root on marshmellow
[Verizon Galaxy S 5 Android Development] GeTex:
the bottom of the OP would have answer your question
[Verizon Galaxy S 5 Android Development] bubbaclubba:
These op's normally have updates to them later on in the thread, I know at the time the op was updated there was no exploit. I know my account only has 2 posts but that is only because after a long hiatus my account was rendered inactive. So I'm not a new to this at all I just asked a question to be sure I hadn't missed anything. You shouldn't bash everyone for asking questions. Last time i checked the purpose of this site is information sharing. Yes most that do ask questions at the end of a thread are just to lazy to read. But I did. So there ya go smarty pants.

---------- Post added at 03:31 AM ---------- Previous post was at 03:28 AM ----------

Thanks for the info. I wasn't sure I hadnt missed something.
[Verizon Galaxy S 5 Android Development] GeTex:
but the OP is consantly updated since I maintain my threads(until i post a notice) so if you had read, you'd save wasted time.
[Verizon Galaxy S 5 Android Development] qwewqa:
Could you explain how this works under the hood? Have the s7 (US) and seeing if I can do something similar.
[Verizon Galaxy S 5 Android Development] Legitsu:
no the s6/s7 are not unlockable

http://theroot.ninja/disclosures/SAMDUNK_1.0-03262016.pdf
[Verizon Galaxy S 5 Android Development] jrkruse:
I did post a custom MM Rom for you CID 11 chips. It's not rooted but you can still use safestrap to flash zips and mods. There are 2 different ones one stock with safestrap and a version of my all google play store Rom which is very slim
[Verizon Galaxy S 5 Android Development] fukenbiker:
<-fine job thank you!

I have obtained root and unlocked the bootloader, on my Samsung chipset SM-G900V, and I presently use Titanium to freeze the PB1 bloatware.

I see this: "Samsung SM-900V - No BS v5 OK3 - Work" in your signature... I wonder if that's what I've been looking for? It's a debloated TW ROM? ... but I have to ask... when you flash that OK3 firmware? doesn't that lock your bootloader again?
[Verizon Galaxy S 5 Android Development] GeTex:
it's a heavily debloated Rom by [MENTION=6697968]CVertigo1[/MENTION], it works fine, and no, firmware flashes will not ever lock the device, a full flash with a bootloader will, firmware zips contain usually just system, NONHLOS, RADIO, ect(i think) While a full tarball has alot more

If your bootloader is unlocked, you can install TWRP and flash Cvertigo1's PB1 NO BS rom which is just your System partition, it will nicely debloat you. You could try and find a custom kernel too! It's just a Flashable ZIP, heck you could just use flashfire to flash it! then just flash a supersu zip and your done!
[Verizon Galaxy S 5 Android Development] jrkruse:
For all you people that have Toshiba 11 bootloaders that cannot be unlocked and you still come here and hope. Here is an actual custom MM rom for you guys it is not rooted but it is a fully working port of Phoenix V15 S7 ported rom. Dont say you have been forgotten about!

https://xdaforums.com/verizon-galax...phoenix-rom-v15-0-6-0-1-t3555880#post71012769
[Verizon Galaxy S 5 Android Development] fukenbiker:
Thanks!

I'm going to buy you a beer. You've inspired me with the courage to flash a ROM with my new Custom Recovery! I will plug Cvertigo1's PB1 NO BS rom into my next search of xda...

I have TWRP 2.7.0... question? I saw something about 3.0 and suspect it's nothing to worry about... it's like ODIN right? The older versions still work fine, right? I shouldn't have to try to get the latest edition of TWRP, right?
[Verizon Galaxy S 5 Android Development] GeTex:
it doesn't really matter
[Verizon Galaxy S 5 Android Development] BlueLaguna88:
its not letting me flash TWRP through Odin, wont even detect the zip

I'm Unlocking the bootloader method 2, in on the final step, i downloaded the TWRP Zip via the link and i rebooted to Download and odin wont detect it
[Verizon Galaxy S 5 Android Development] GeTex:
...odin cant flash zips...
[Verizon Galaxy S 5 Android Development] BlueLaguna88:
ok, what i download is a zip , i've even unzipped it and Odin still doesn't detect it, the instructions says use odin to flash TWRP
[Verizon Galaxy S 5 Android Development] BlueLaguna88:
thank you
[Verizon Galaxy S 5 Android Development] ChrisG12:
upgrading to QA1 bootloader

I have a Verizon S5 with 15 CID, rooted (towelroot) /unlocked bootloader (option #4) on NCG / 4.4.2 with TWRP. Wanted to upgrade the bootloader to QA1. Followed the directions in the OP. Flashed TWRP_prepare and it seemed to work (other than the flash was instant... thought it would take at least a few seconds). Anyway proceeded to download mode and odin'd the pit and PB1 file. Odin declared success (or "pass" or whatever it says) and phone rebooted. However I do not appear to have safestrap installed - I see no where to enter safestrap. TWRP seems to have been replaced with a stock looking recovery and my status switched from "custom" to "official". Other than that nothing appears different - phone works fine, still have root, etc... What went wrong? I tried repeating the process twice - same result.
[Verizon Galaxy S 5 Android Development] izzyfanto:
I have read the OP, and skimmed through the 293 pages, but haven't seen anywhere that mentions the predictability of getting and 11 vs a 15. Is there a way to tell from carrier what you'll get? I have a Verizon S5. Is it just a toss up that if I got another Verizon it will be a 11?
[Verizon Galaxy S 5 Android Development] Legitsu:
---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------

[/COLOR]

uhh if you odin'd pb1 you relocked the bootloader and flashed stock firmware .....

if you wanna upgrade to QA1 and keep twrp/root you need to root > unlock the bl again > flash twrp

then install this zip

https://xdaforums.com/verizon-galaxy-s5/development/rom-verizon-stock-rooted-odexed-t3551404
[Verizon Galaxy S 5 Android Development] ChrisG12:
Sorry - to be clearer - I followed the section in the OP to upgrade my bootloader. In that section it provides a file called "PB1_Firmware_Only_NK2_Kernel.tar.md5" - that is what I odin'd not a full PB1 rom.
[Verizon Galaxy S 5 Android Development] Legitsu:
yea I don't know why he said todo that its unnecessary just flash one of the aios from twrp odin the twrp image back in [MENTION=5414005]GeTex[/MENTION] you really need to streamline this

please for the love of ****ing jebus stop recommending safestrap its unsupported its a hack job its fugly , you have redundant scripts every-ware you don't need to be unlocking the boot loader twice once the CID is changed you can just flash ANY dev ABOOT/recovery no need to run it again the cid is the same across every device that uses this unlock no need to run samdunk again

its unnecessary we have TWRP use it fix the scripts as needed package the proper twrp recovery binary so it works like every other unlocked device ever there is no good god dam reason to have to use safe-strap AT ALL once you have the boot-loader unlocked
[Verizon Galaxy S 5 Android Development] GeTex:
with that attitude i'm gonna need to ask you to stop
[Verizon Galaxy S 5 Android Development] Legitsu:
assholemodeenable

its

stupid

this doesn't need to be this hard what it is is YOU repacking stuff without the correct installation scripts making it 3x harder for these idiots to understand you are relying on safecrap because you are running samdunk twice when you only need todo it once because the CID is the same for all aboots unlocked in this manner it says so right in the samdunk paper

its also way wayyy wayyy more work for you you got twenty extra steps to go from A to B when it should just be boot recovery > flash zip DONE

you need to remember most of these people can't tie there shoes without a 10 step instructional video =-/

---------- Post added at 01:49 AM ---------- Previous post was at 01:38 AM ----------

the modus operandi has always been

unlock boot-loader > custom recovery; flash Rom, Kernel, modem ?update TWRP

and let god sort em out

by trying to package it in one step you complicate the process and accually make it less intuitive for the people that have done this before

so far you have had a bunch of people whine about it being too hard well now I am telling you the same thing ITS TOO HARD :P
[Verizon Galaxy S 5 Android Development] GeTex:
it's a shared effort between me and [MENTION=1949695]jrkruse[/MENTION], no one else has been helping and me and jrkruse are doing our best considering we've been here doing it for a while. Honestly if everyone wants to whine and complain instead of making suggestions in the form of what i exactly should edit and change, then honestly I think I'm going to be taking a long break from this thread because i get absolutely nothing from helping all of you, I do it because I genuinely love helping the community but if the community wants to slap it back in my face all the time, then I will take my leave

i cannot tell your attitude across screens but i'm reading it as a giant middle finger
[Verizon Galaxy S 5 Android Development] jrkruse:
If you odined PB1 how to you still have an unlocked bootloader and root?

Edit sorry I didnt see your follow up post

either get back to fully stock rooted kitkat rom running safestrap or stock rooted lollipop rom running safestrap. Even if your bootloader is unlocked you need to have stock recovery and stock boot.img installed then flash the Safestrap QA1 Bootloader unlock zip in safestrap

---------- Post added at 03:31 AM ---------- Previous post was at 03:11 AM ----------

You said you can just flash any dev aboot once your cid is changed. Well let me make a few things perfectly clear. You cannot update your bootloaders while on Marshmallow without using safestrap. You have to have Stock recovery and stock boot.img installed befor a bootloader can be flashed. and on Marshmallow to have stock recovery and boot.img means no root and without root or safestrap you cant flash the updated firmware. You can use odin but it will relock your bootloader so you would be stuck with no way to root without going back to pb1 which requires you to goback to pb1 bootloader. So if you can figure out a way to flash the updated bootloader and unlock it without safestrap then let me know.

---------- Post added at 03:41 AM ---------- Previous post was at 03:31 AM ----------

In this reply with what you said how would you update your bootloader from lollipop to marshmallow. How would you run the samdunk script to ulock your marshmallow bootloader without root? You cannot have root on Marshmallow without an unlocked Marshmallow bootloader. You cant flash your Marshmallow bootloader while still on lollipop rom with root because your rom will not boot with a marshmallow bootloader. So you need to explain to me in detail how you would unlock a marshmallow bootloader without using safestrap

---------- Post added at 03:43 AM ---------- Previous post was at 03:41 AM ----------

I will update some instructions in the OP that needs clarifying on the update process and if the guy comes up with a method to unlock Marshmallow bootloaders well you can just delete all my stuff and use his
[Verizon Galaxy S 5 Android Development] Legitsu:
I was talking about once you where rooted and unlocked after that you should have no need of safe-strap,roms should be shipped with whatever aboot/firmware needed if you aren't using stock tw based

if you are using a boot with dm-verity enabled which means no root

if its off you can do whatever you want to whatever partitions you want how ever you want

once you have a unlocked boot loader and are on twrp you can do anything you want flash pre-cid'd boot-loaders all day so long as you are dev status and secureboot disabled (you generate a backup of whatever bootloader revision you need thats already been CID'd and package that into a flash-able format the only thing it cares about is the checksum so long as its not touched it should't be trigging a secure-check fail

this avoids the need for the stock recovery/aboot song and dance

there should be no reason TWRP can't write the aboot/boot/recovery image and disable dm-verity on its own SAFESTRAP is TWRP just on the stock kernel , yes if you get it wrong it will soft-brick but thats always been the case

the issue I had is everything is one flash-able zip nice great useful if you wanna get setup with a rom and never change it ... if you wanna swap between bls and basebands,,, then it becomes a pain because safestrap doesn't work on nougat s e.g lneage 14.1/AICP12 hell AOKP MM had some issues with SS when I tried it

also initially if you wanna go custom which is the entire point of this the you will be changing base-band frequently,so far I have run into some minor announce running AICP 12 and had to switch from PF4 to QA1 to get decent service

once you are on TWRP ideally that is ALL you should ever need
[Verizon Galaxy S 5 Android Development] jrkruse:
Oh and by the way [MENTION=5417447]Legitsu[/MENTION] I have zips to do this process from flashfire but it was found not to be very reliable either. I may research flashfire again it has become alot better since I tried it

---------- Post added at 04:16 AM ---------- Previous post was at 04:13 AM ----------

You cannot flash bootloaders in TWRP it does not work you also cannot flash modems

Edit: I think your not getting the picture: In order to flash a bootloader or secondary bootloader or modems you must have the stock recovery and the stock boot.img installed or those items are write protected and cannot be over written unless the stock recovery and boot image is present. So once your on Marshmallow there is no way to have root meeting the above requirements. Safestrap is used because it does not require root to boot into safestrap as long as you installed it while you had root thats why the stock boot.img and recovery image can be installed. This is why I have a flashfire prepare zip that can be flash in TWRP it injects safestrap into your current rom and flashes the stock boot and recovery image the boot.image is kitkat but thats ok because its still official verizon boot.img and this allows safestrap to be reached at boot. Safestrap can then flash the updated bootloaders and modem because write protection is removed because stock boot.img and stock recovery are present. Flash Fire can be used to update your bootloader from Lollipop to Marshmallow because you can have root on lollipop without having a modified boot.img but on marshmallow there is simply no way to have root on the stock boot.img so flashfire cannot flash the bootloaders and modem because of write protection the same with twrp. Im sorry but without flashing back to Pb1 everytime to update your marshmallow bootloader the only way is safestrap. And even if you wanted to goback to PB1 each time to update your bootloader I still have to make a booloader already dev unlocked to flash in flashfire because flashfire wont flash the samdunk script so I would still have to use safestrap to unlock bootloader and pull the unlocked bootloader to put in a flashfire package. Im done explaining myself. Like I said I found a way be fortunate I did. Head over to the note 4 forums and see how hard it is for them to update bootloader. They are fortunate that kingroot will temp root marshmallow roms for them but it wont for S5. Like I said if you feel you have a better method write it up test it and post it. S5 development is about dead anyways. I just released some things because I was bored but my time is numbered here.
[Verizon Galaxy S 5 Android Development] mattnin:
Legitsu, if you're so smart and think you have it all figured out, then make whatever working procedure available to us idiots so we can flash this phone easier, otherwise shut up because you have provided nothing useful to us at all except wasting everyone's time.

I'll be waiting to hear your excuses...

---------- Post added at 07:54 AM ---------- Previous post was at 07:44 AM ----------
[Verizon Galaxy S 5 Android Development] izzyfanto:
Maybe I don't understand, but I was able to flash a different modem via Odin while on TWRP and LOS. . . am I missing something? Thanks y'all for your work btw!
[Verizon Galaxy S 5 Android Development] jrkruse:
Are you sure it changed
[Verizon Galaxy S 5 Android Development] Legitsu:
I am aware of the write protection

its possible to turn it off and I was operating under the assumption that it was already done

anyway if it hasn't been then you would need to fire up ida and get the symbols for the LK

and then extract the needed ccconfig/sb flags and turn it off once all that is done you can boot stock images > flash modded images with wp off then you are home and fancy free

this art has some information about what makes up the aboot/pbl/sbl as well as a method for disabling download mode

https://ge0n0sis.github.io/posts/20...-mode-using-an-undocumented-feature-of-aboot/ (why would you want to lol)

I barely have time to reply to these threads if I don't die in the next 6 months and I get some I will look at it further
[Verizon Galaxy S 5 Android Development] izzyfanto:
Yes sir. I used your thread for PB1. A couple weeks ago, I flashed PJ2 via Odin.
[Verizon Galaxy S 5 Android Development] GeTex:
Woah, everyone slow down a bit. I'm still trying to follow what everyone is saying. Also no need to attack [MENTION=5417447]Legitsu[/MENTION] I am offended by his behavior but I believe he has good intentions, I just do the think he fully understands some of the way the system works, because it does behave funny. If he seriously found a way to remove the write protect flag, that's great but I don't know if he realizes that at every boot, the flag is re-enable. At boot, the bootloader checks boot.img and recovery.img, if either one fails a signature check, it turns on write protect to avoid losing dev status. The long story short is this, it could be possible to do it inside recovery and flash the bootloader once, but that would be it. Which might not be so bad.

Someone above asked how to get back into safestrap, just flash the NK2 kernel
[Verizon Galaxy S 5 Android Development] Legitsu:
yea I know it re-enables I know its a CC flag I KNOW its possible to change it I just kind of figured that had been done because its how EVERY-OTHER Device Handels it

don't get me wrong I am not knocking any of the info you posted I just don't like things that aren't simple <_< and I don't much care for samsungs bassackwards solutions to things

if you can figure out what flag it is set it then all your problems go away because then it no longer cares what you do .. if you screw up get you to start from zero

I doubt the section for enabling/disable write protect is gonna be hard to find in the lk/sbl its just a question of does dev status give us enough access to toggle the flag and can we use twrp to set it

has anybody tried flashing a ORIGINAL Factory dev edition bl before they enabled wr
[Verizon Galaxy S 5 Android Development] jrkruse:
delete
[Verizon Galaxy S 5 Android Development] Legitsu:
the write protect on SBL has been a thing since at least the S3

You can change the CSC config by patching aboot to disable the write protect flag

years ago there was a patch for the s3? that did exactly that allowing you to flash and or brick your device in any manner you wanted

you can indeed odin whatever modem/no-hols you want write protect or not it only cares about the SBL bootloader

the update script in the op is overly complex in my book it does more then it needs to (boot-loaders should be separate from modems) it needs a terminal for a yes/no prompt and safestrap i

and yes I do a lot of *****ing a basically no coding believe me if I had time I am 90% sure I could reduce condense this process way down I have a few ideas about modifying twrp with better support for this device ,slots for the various firmware/boot loaders versions to eliminate all this musical safe-strap non-sense

I also have a possible very tiny extra small microscopic ray of light for CID11 devices but I am not entirely sure if its gonna work as I usually sell S5's as soon as I can get them
[Verizon Galaxy S 5 Android Development] jrkruse:
Well if anyone could do it it would be chainfire and his app flashfire can't even do it on Samsung s5. I agree it can be done its probably as easy as rooting the new s8 will be
[Verizon Galaxy S 5 Android Development] Legitsu:
getting bl write protect off should be no-ware near that hard CID11 devices yea probably fked (need kexec for that and thats a dead horse) shame because the way samsung is headed KEXEC is gonna be the only shot

I finally had time to sit down and flash my personal S5 with AICP12.1-nightly boeffla-venom kernel 8 for LOS tonight maby tomarrow I will see what it will take to resuscitate multirom and use slots

not that its needed from what I have seen of nougat on this there should be no reason to drop back to lolipop

also I have tested king2su on a total of 3 S5's now pretty sure you can add it to the op
[Verizon Galaxy S 5 Android Development] ryanbg:
Your proposed solution is partially correct, but not in the way we would want it. The CC data does indeed contain a flag for write protection on certain partitions like the modem if the device is determined to be modified (rooted, etc.). Unfortunately, the WP flag we want is actually set by aboot when it checks if the device is a developer device. This is set regardless of flags in PARAM partition, system/binary status, etc... I've looked into this pretty deeply and have yet to find a solution short of modifying the eMMC firmware (but this is really dangerous and I wouldn't be the right person to do it.)
[Verizon Galaxy S 5 Android Development] Legitsu:
I thought about simply re-mapping/re-basing it to a section we have write access too by manipulating the partition parm or some kind of intermediate loader to point it else-ware not quite sure its possible

Emmc firmware is ehhhhhhh but we are already poking that bear ... who knows what else he could be guarding
[Verizon Galaxy S 5 Android Development] ryanbg:
Think of the eMMC as it's own computer, complete with a microcontroller and RAM. We want to modify data contained within that system, but the only link we have to it is a couple data lines, and command/clock lines. All we can send across this interface is requests for reading/writing/erasing, in addition to some secret vendor commands. None of that memory or data is 'mapped' anywhere to our device other than the MMC/SPI interface. Any 'trickery' that needs to take place can only occur over this MMC interface, because we aren't connected to it anywhere else. Things like JTAG are useless in this situation, because they only provide access to the Snapdragon SoC, there's no TAP on the eMMC chip. Hopefully this puts it into better perspective.
[Verizon Galaxy S 5 Android Development] GeTex:
It's exactly as I thought [MENTION=766721]ryanbg[/MENTION] thank-you for clarifying this! Do you have any suggestions by any chance cause currently I think me and [MENTION=1949695]jrkruse[/MENTION] have done the best we can with our uhhh... Current avalible tools...