Database Info

EK-GC120 Verizon Update

I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.

swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
Click to expand...
Click to collapse
I give up. How did you root this device in the first place?

perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.

Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app

perlmane said:
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.

swjpilot said:
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
Click to expand...
Click to collapse
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.

perlmane said:
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
Click to expand...
Click to collapse
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......

swjpilot said:
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
Click to expand...
Click to collapse
Since VZW does not support Kies firmware updates, I am afraid to try it. I will have to wait until someone finds the 4.1.1 release of this device and ODIN it.

Anyone still have the boot.img for the latest verizon? Even the full update will work to extract it. This is the only missing piece to extending the custom kernel to all variants.

perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
swjpilot said:
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Click to expand...
Click to collapse
If you are still around can you confirm you used the "Exynos" Abuse apk to root your Verizon GC120. The Samsung specs page for it aren't clear about whether it's an Exynos quad core using a qualcomm board or an entire qualcomm chipset/board. Thanks!
And if anyone Verizon has found a way to root the current Verizon version and/or the odin file for 4.1.1 please reply here or let me know! Thanks!

swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Click to expand...
Click to collapse
That link is dead end. Can you please repost that firmware update?

Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.
http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0
EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.

CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...
Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).

Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update

twistedumbrella said:
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
Click to expand...
Click to collapse
I know you think no one else could possibly know better than you but the link in the op leads to nothing.

Jiggity Janx said:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Click to expand...
Click to collapse
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.

twistedumbrella said:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Click to expand...
Click to collapse
edited out...
You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.

Jiggity Janx said:
My problem here starts and ends with you. You cant expect to come across the way you do belittleing or correcting everyone every chance you get and then wonder why someone responds that way to something that appears to be a comment directed at the very last thing stated in the post immediately before yours. You dont get to have it both ways and then act innocent and deflect when you are called out on it.
Click to expand...
Click to collapse
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.

twistedumbrella said:
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
Click to expand...
Click to collapse
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.

Jiggity Janx said:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Click to expand...
Click to collapse
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.
As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.

Gs5 active sport ...

Anybody rooted this one yet?
Sent from my SM-G860P using XDA Free mobile app

cortacanya said:
Anybody rooted this one yet?
Sent from my SM-G860P using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot should work. It works on the standard S5 and AT&T S5 active as well as Verizon variants.

CCallahan said:
Towelroot should work. It works on the standard S5 and AT&T S5 active as well as Verizon variants.
Click to expand...
Click to collapse
tries and just hung there

cortacanya said:
tries and just hung there
Click to expand...
Click to collapse
Correction-- app says
"phone isnt currently supported"

Sprint Galaxy S5 Sport
I am interested in this as well.
My searches have only turned up false leads.
Model: SM-G860P
Kernel Version: 3.4.0-2113914
Kernel Date:: July 11 2014

cortacanya said:
tries and just hung there
Click to expand...
Click to collapse
Go to device info in settings and look at the Kernel version. What date is listed?
**EDIT...NM, I see the kernel date listed in dallas532's sig as July 11. Towelroot will not work with Kernel dated after June 3rd.
You can put in a request to CF here to create a working CF Auto Root for your device. Just be sure to post the recovery.img file as listed in the OP if/when the source code is available.

CCallahan said:
Go to device info in settings and look at the Kernel version. What date is listed?
**EDIT...NM, I see the kernel date listed in dallas532's sig as July 11. Towelroot will not work with Kernel dated after June 3rd.
You can put in a request to CF here to create a working CF Auto Root for your device. Just be sure to post the recovery.img file as listed in the OP if/when the source code is available.
Click to expand...
Click to collapse
Request has been made!

I returned mine on launch day for a regular gold s5 because of the software differences. I tried all different ways I could think of to root and couldn't get a recovery to stick without soft bricking the phone.
Sent from my SM-G900P using XDA mobile app

s5 active 860p
i hope someone can help with root...i will donate to whoever makes this happen,or points me in right direction.

tomlirr324 said:
i hope someone can help with root...i will donate to whoever makes this happen,or points me in right direction.
Click to expand...
Click to collapse
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx

UPdownLoAD said:
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
Click to expand...
Click to collapse
I am still awaiting a reply from anyone, I check on websites daily, made a request to CF, even downloaded vroot and tried...nothing yet

UPdownLoAD said:
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
Click to expand...
Click to collapse
I feel the same way. I knew I should have purchased the regular S5. Damn it. I guess we're stuck. If anyone hears anything please post it here. I'll do the same. Thanks !

I'd be willing to trade my regular Sprint s5 for the sport if anyone is interested. Message me.

Yes, the GS5 Sport (Sprint SM-G860P) is rootable
cortacanya said:
Anybody rooted this one yet?
Sent from my SM-G860P using XDA Free mobile app
Click to expand...
Click to collapse
UPdownLoAD said:
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
Click to expand...
Click to collapse
Good to see ya interested in this phone too, UPdownLoAD! I hope all went well with the Torque dev when I had to pop off of the grid right after rooting that (this one is A LOT easier...trust me).
I just bought this phone earlier this week and hadn't looked into its rootability. I figured that, since it is a Samsung phone on Sprint, it would have an unlocked bootloader (and it does). There are, however, zero support tools for these. This is not TowelRoot eligible due to the newer patched kernel and is not on the CF-Auto-Root list yet.
I took a little time during the LLWS today to get this thing rooted and confirmed before I go out of town on business for a week and it turned out just fine.
Solution: Simply employing the use of a custom recovery and using the "fix su binaries" and "prevent stock recovery flashing" options upon exiting after entering the recovery.
Ok, yes, there is no official release of CWM, TWRP or Philz for this device yet. I have a custom recovery that is in Chinese that I, personally, know how to decipher, but would not release it here*. Hopefully, there is an official recovery on the way or someone properly builds one in English. CWM used to have an automated recovery builder tool server-side, but I think it has been offline since March of this year. Again, I am about to head out on business soon and don't have a lot of time until on my flights to dig more into this, but wanted to give the certain thumbs up to anyone considering this phone but didn't know if it would have root.:good::good::good:
In summary: YES, the Sprint Samsung Galaxy S 5 Sport (SM-G860P) on the latest OTA build (NG3) is rootable just fine.
*Please do not ask me for the recovery that I have...Google is your friend (it's only in a single public location as of right now), but I did not want to be responsible for someone grabbing it and guessing what characters mean and borking their phone.

I need help.
VicFreeze said:
Good to see ya interested in this phone too, UPdownLoAD! I hope all went well with the Torque dev when I had to pop off of the grid right after rooting that (this one is A LOT easier...trust me).
I just bought this phone earlier this week and hadn't looked into its rootability. I figured that, since it is a Samsung phone on Sprint, it would have an unlocked bootloader (and it does). There are, however, zero support tools for these. This is not TowelRoot eligible due to the newer patched kernel and is not on the CF-Auto-Root list yet.
I took a little time during the LLWS today to get this thing rooted and confirmed before I go out of town on business for a week and it turned out just fine.
Solution: Simply employing the use of a custom recovery and using the "fix su binaries" and "prevent stock recovery flashing" options upon exiting after entering the recovery.
Ok, yes, there is no official release of CWM, TWRP or Philz for this device yet. I have a custom recovery that is in Chinese that I, personally, know how to decipher, but would not release it here*. Hopefully, there is an official recovery on the way or someone properly builds one in English. CWM used to have an automated recovery builder tool server-side, but I think it has been offline since March of this year. Again, I am about to head out on business soon and don't have a lot of time until on my flights to dig more into this, but wanted to give the certain thumbs up to anyone considering this phone but didn't know if it would have root.:good::good::good:
In summary: YES, the Sprint Samsung Galaxy S 5 Sport (SM-G860P) on the latest OTA build (NG3) is rootable just fine.
*Please do not ask me for the recovery that I have...Google is your friend (it's only in a single public location as of right now), but I did not want to be responsible for someone grabbing it and guessing what characters mean and borking their phone.
Click to expand...
Click to collapse
So I have tried to root my gs5 sport and have ran into a big problem. I think it is a big problem. My phone did not like the rooting that I tried and now is restarting over and over. I don't know what to do. Any help would be nice. Thanks

nate2mars said:
So I have tried to root my gs5 sport and have ran into a big problem. I think it is a big problem. My phone did not like the rooting that I tried and now is restarting over and over. I don't know what to do. Any help would be nice. Thanks
Click to expand...
Click to collapse
Most likely you'd need the Stock The file to Odin back to stock. But I'm not even sure those are available. Least I haven't seen anything mentioned about em.
Not sure what root method you tried, but there's been alot of talk going around for a week or so, that neither cf root, or towelroot methods don't work.
Next time (to be totally safe) it may be best to wait for a stock tar file to be available, before Taking a chance like this. Just a thought. Head to the SamMobile website and look up your devise to see if they got the Stock tar up. Still a pretty new device, so not sure if they'll be around yet. That sux tho.
Good luck!
Sent from my SM-G900P using Tapatalk

nate2mars said:
So I have tried to root my gs5 sport and have ran into a big problem. I think it is a big problem. My phone did not like the rooting that I tried and now is restarting over and over. I don't know what to do. Any help would be nice. Thanks
Click to expand...
Click to collapse
The NG2 and NG3 tars are out. Get NG3 and prepare to wipe the entire device if you Odin the whole tar. It would be more helpful to know what you actually did (the method) versus saying "I tried to root". Since there is no automated root specific to this device yet and TowelRoot would not cause a bootloop, you likely ran something you certainly should not have (if it wasn't made for this phone model, why would you do that?) You've likely hosed up the phone/system to the point where you have to run the full tar (versus just the boot/kernel or the modem to "fix" with your user & system data in tact).
Grab the NG3 tar from sammobile or samsung-firmwares and Odin back to stock.
FYI TO ALL: everything is running smoothly after running my Titanium Backup restore from my old GS5 and pushing in Xposed modules. Also have successfully applied the hotspot tweak to my telephony.db and SD card write access. Hopefully I get some time during flights with Wi-Fi to pump out a recovery worth wide-releasing sometime this week if no one else chimes in.
Sent from my SM-G860P using Tapatalk

I await patiently for some one to root and a custom recovery. I actually like this phone and prefer it over the regular but awesome GS5. I just wish for more support. I have rooted and customized every android phone I have gotten within a day of purchase, so it became habit and ritual. Now I sit here waiting patiently.

cortacanya said:
I await patiently for some one to root and a custom recovery. I actually like this phone and prefer it over the regular but awesome GS5. I just wish for more support. I have rooted and customized every android phone I have gotten within a day of purchase, so it became habit and ritual. Now I sit here waiting patiently.
Click to expand...
Click to collapse
Chainfire has posted Auto Root for the G860P:laugh:

cortacanya said:
Chainfire has posted Auto Root for the G860P:laugh:
Click to expand...
Click to collapse
Indeed. Here is a link to the CF-Auto-Root download:
http://download.chainfire.eu/460/CF...-Root-kltesprsports-kltesprsports-smg860p.zip
Just download, extract and flash the Tar with Odin using the PDA option. Let the device reboot into the temporary recovery and self-root.
Sent from my SM-G860P using Tapatalk Pro

ENGBOOT for SM-G930F (UNTESTED): Probably False (not Tested on a device)

Hello everybody!
I was surfing through the web when i found this file uploaded on 4shared claiming to be an Engboot for SM-G930F.
Naturally, I was sceptical about this file, as I am completely uneducated about the nuts and bolts of Android, I could neither confirm or deny that this is a valid file or not, so I decided to post the link to XDA , so much more knowledgeable people can take a look at it and see if it is a valid file or not. I don't want to flash this file on (bought yesterday) my S7 Edge, so here I am!
If anybody is feeling brave enough to try this on their phone, please go ahead and tell if this worked or not
Disclaimer: I am not responsible in any way for bricked devices, this file is completely untested.
Original Link: [url]https://www.4shared.com/get/X3a35HZTba/SM-G930F-ENGBOOT-bay_MrTpO.html[/URL]
Zippyshare (no registration) Link: [url]http://www80.zippyshare.com/v/axSXOCtR/file.html[/URL]
Edit: This is important because if this file works, you could thereotically flash anything you want WITHOUT tripping knox.
Also you can easily unbrick your phone by flashing the stock ROM if it comes to that.

Noob you can test self on your phone. We are not your tester here.

Schrotty35 said:
Noob you can test self on your phone. We are not your tester here.
Click to expand...
Click to collapse
I'm sorry that I apparently did not make it clear in the original post, but I have a S7 EDGE not a S7, so flashing this would probably brick my phone and yield no good result. I made this thread so the community may possibly benefit from this.

and what is SM-G930F-ENG(BOOT)_BST.bsp??

KPOCAB4EG said:
and what is SM-G930F-ENG(BOOT)_BST.bsp??
Click to expand...
Click to collapse
Engineering Bootloader.
Sent from my G930F using Tapatalk

KPOCAB4EG said:
and what is SM-G930F-ENG(BOOT)_BST.bsp??
Click to expand...
Click to collapse
You saw that too! I saw that through WinRar , after searching through the web I saw that it is a Binary Space Partitioning file, I am currently searching the web to see how to open it.
Sent from my Samsung SM-G935F using XDA Labs

The Game said:
Engineering Bootloader.
Click to expand...
Click to collapse
Does this work?:fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs

The Game said:
Engineering Bootloader.
Click to expand...
Click to collapse
lol lol lol i google'd what is:
Best Smart Tools (BST) – Supported Models & Features:
#SAMSUNG / Support Models & Features:
Samsung features:
- Reading full information via ADB or MTP interface
- Safe and fast flashing – supported tar, md5, smd, img, bin, rfs etc files format.
- Remove screen lock w/o usb debugging, w/o root, don’t lost userdata (support re-lock).
- OneKey Recovery (support 4.3/4.4.2 remove screenlock don’t lost userdata)
- Unlock/Read all unlock codes.
- Samsung Qualcomm Direct Unlock (no need root, no need wipe efs, no original imei loss)
- Repair damaged IMEI, backup/restore SuperIMEI.
- Repair baseband unknown.
- Read/write EFS,NVM,PIT,QCN,Cert files
- Repair SN, Cal Date, BT Addr, WiFi MAC, Product Code, HW Version etc
- Auto try to root when operation need rooted
- Repair Boot SDCard – brick phone repair
- App2SD
- Factory reset
Click to expand...
Click to collapse
this is no Engineer Boot
main function for this app - unlock mobile network

KPOCAB4EG said:
lol lol lol i google'd what is:
this is no Engineer Boot
Click to expand...
Click to collapse
I am not sure what you mean by that, that is BST not BSP
Sent from my Samsung SM-G935F using XDA Labs

Random04 said:
I am not sure what you mean by that, that is BST not BSP
Click to expand...
Click to collapse
http://gsmbest.com/en/ShowProduct.asp?Id=4 and Go To "Update logs"
* About Samsung "Reset FRP Lock" patch files(*.bsp):
Click to expand...
Click to collapse
this is no boot and no from samsung

KPOCAB4EG said:
http://gsmbest.com/en/ShowProduct.asp?Id=4 and Go To "Update logs"
this is no boot and no from samsung
Click to expand...
Click to collapse
Thanks KPOCAB4EG, I was unsure about this myself too. :good:
Sent from my Samsung SM-G935F using XDA Labs

Alright, I just stumbled upon this. I'm assuming no one has tested this. From what I've read in post 8, is it safe to say that this file is *supposed* to fix the IMEI issue coming up as 000000000?
This might be what I need because my phone is giving me the following error in recovery
"dm-verity verification failed...
Need to check DRK first..."
Also as I mentioned above my IMEI is all 0's, which I'm assuming is caused by a faulty EFS partition.
No matter how many times I try to flash stock firmware through ODIN, I always end up in the same spot.

m0d hipp¥ said:
Alright, I just stumbled upon this. I'm assuming no one has tested this. From what I've read in post 8, is it safe to say that this file is *supposed* to fix the IMEI issue coming up as 000000000?
This might be what I need because my phone is giving me the following error in recovery
"dm-verity verification failed...
Need to check DRK first..."
Also as I mentioned above my IMEI is all 0's, which I'm assuming is caused by a faulty EFS partition.
No matter how many times I try to flash stock firmware through ODIN, I always end up in the same spot.
Click to expand...
Click to collapse
Hi,
This file is probably going to make your situation worse, you should follow this guide: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 or alternatively make a new thread so people can properly help you.
Best of luck!:good:
Sent from my Samsung SM-G935F using XDA Labs

Thanks for the response. I have came across that thread and tried those steps, but it didn't help unfortunately. I have also tried several other things such as hex editing the EFS partition and using 3rd party tools to try and change the IMEI, but nothing seems to be working. My last resort might have to be going through Samsung Service Center.
The odd thing is that I have a SM-G930T, however according to my IMEI on here: http://www.imei.info, it's showing as SM-G930F which is confusing. IMEI is 357752072430049

m0d hipp¥ said:
Thanks for the response. I have came across that thread and tried those steps, but it didn't help unfortunately. I have also tried several other things such as hex editing the EFS partition and using 3rd party tools to try and change the IMEI, but nothing seems to be working. My last resort might have to be going through Samsung Service Center.
The odd thing is that I have a SM-G930T, however according to my IMEI on here: http://www.imei.info, it's showing as SM-G930F which is confusing. IMEI is 357752072430049
Click to expand...
Click to collapse
That IMEI checker will tell you your model number and then your exact variant in the brackets.
By the way, which third party tools/other methods have you tried?
Sent from my Samsung SM-G935F using XDA Labs

Random04 said:
That IMEI checker will tell you your model number and then your exact variant in the brackets.
By the way, which third party tools/other methods have you tried?
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
The thing that's confusing is that SM-G930F and SM-G930T are 2 different models.
My phone, is a tmobile version, which should be SM-930T (snapdragon chipset), according to the IMEI checked with my IMEI it shows that it's SM-G930F which is an exynos chipset. This is what's confusin to me...
I tried flashing twrp on there using herolte, heroqltechn and heroqlte and none of them worked. I tried it through ODIN, I tried it through flashfire, I tried it through adbshell using the DD command and none of those methods worked.
As far as what I have tried regarding the DRK and IMEI fixes...
I have tried flashing the SM-G930T PK1 and PIA stock firmware and nothing fixed it.
I have tried restoring full backups I made (prior to having these issues) with flashfire, and I got it to boot, but then I got a error with it being able to decrypt my storage so it forced me to go into the stock recovery and wipe data\factory restore and wipe cache, after I did that the DRK and IMEI issue came back.
From what I've read it seems I need a custom kernel (which apparently isn't an option right now) for me to bypass the IMEI and DRK issue.
The other option I read was to write the certificate back to my phone. I asked if I am able to pull the cert from an old backup that I made, but was told that it's not possible to pull it from a backup.
I also tried taking the EFS.img file from an old backup (prior to these issues) and tried restoring it, and this didn't fix anything.
I tried taking EFS and hex editing the value into it, still nadda.
When I was desperate, someone mentioned using the PIT file from a stock tmobile firmware and using that to re-partition the phone as well as doing a NAND erase on the phone as well as an EFS clear and bootloader update, so I tried that and still nothing.
If anyone can provide any assistance it would be greatly appreciated, but I'm not sure what else to try. Unfortunately my options are somewhat limited by a locked bootloader.

950U stock rom 7.0 with flashable root... SafeStrap needed

First off Safestrap is need for this to work...:good:
This is a complete stock system .IMG I pulled from BQL1 /BRB1 just to keep the same as rest of the roms out there.....Fully bloated nothing removed...100% Stock
The stock images here will now work for SafeStraped Revision 5 or 6 bootloaders in order to obtain nougat rooted
No mods/No crazy fancy foot work....This is a do it your self stock rooted rom setup for all who wants it....
And no this uses the same kernel as other roms, Battery charges to 80% like any other for Snapdragon S8
Manual fix for 80% charge
https://forum.xda-developers.com/galaxy-s8/how-to/wip-manual-charge-past-80-snap-dragon-t3918553
This is the last nougat firmware available before We went to nougat...
Super stock 7.0 No bags/No wallplugs
Without further ado
I have updated with BRB1 as well at bottom of this post.
Download the stock system .IMG from here https://drive.google.com/file/d/1kPJaF4AMNyMr-3RLfycKuX3ZOxPQeWz1/view?usp=sharing BQL1 here
We need busy box from here...... https://drive.google.com/open?id=1k1zOTMAAuqL1KydoHj_QpOwmOQQqSTXT I used this one as i know it works if you want to update go ahead.
We need system mode SU Not system-less from here..... https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Ok Now we got all that. Place the system .img on internal SD card and extract there.....Then goto TWRP in SafeStrap......
We want to wipe system cache and dalvik....Like always...:good::good::good:
Then after that flash that sys.img to system..
We need to then flash Su and Busy box....For good measure factory reset after all said and done...
Before reboot Reboot to download mode....
In download mode then flash your respective CSC file in Normal odin I use 3.13
If you do not do this you will have a bunch of metro pcs cricket and tmobile crap as well as double and triple menus,So you are warned
Once all this is done reboot system as normal sign in and do your thing enjoy a 100% stock rooted rom.....
No xposed no nothing Be aware xposed will break Bluetooth pairing on reboots...
Also on a side note.If you are on bootloader revision 3 or 4 you cannot downgrade to root nor is root available for these revisions
Revision 5 or 6 bootloaders see here for safestrap, https://forum.xda-developers.com/galaxy-s8/development/root-t3904613
Then you can follow this starting with system img... DO NOT ATTEMPT TO FLASH REV 4 OR LOWER BOOTLOADERS ON REVISION 5
Make sure to give our man @jrkruse the proper credits he deserves for Bringing this to revision 5 bootloaders..
Instructs for rev 5 or 6
https://forum.xda-developers.com/showpost.php?p=79004426&postcount=29
Again you must already Safe-strap installed...
Credits
As always Thank @partcyborg for root and wonderful rom for our S8.
@mauam for the version of SU downloads
As well as @Chainfire for all of his hard work and SU
@YashdSaraf for his version of busy box
@TheMadScientist For all this crap here lol:good::good::good:
If I am missing any one just hollar at me:good:
Disclaimer This is a build your own system from scratch So any issues you may have can be possibly helped here but in the end it is your own accord of flashing and modding Dont cry to me when you break something
Im a mechanic Not a rom developer I just know there are several out there that dont like the other roms available for our S8 locked bootloader. So just another option:good::good::good:
This is Jrkruzes safestrap method and zips in this post very helpful
https://forum.xda-developers.com/showpost.php?p=79004426&postcount=29
And BRB1 latest 7.0 here https://drive.google.com/open?id=1h6e-3qCkE4JhiAlGjk94jpCz2CVMir8Z
And here is the BRB1 baseband CP for odin https://drive.google.com/open?id=1BuUc-R6jU7ha4nn4vkPrLfvfz2axi5Ru
Flashing this is similar to flashing the first one.But if you are on my stock rooted now you can dirty flash this system followed by su then busybox and then open odin and reflash CSC or a no signal situation will present itself.
Other than that I did dirty flash all of my apps and most of my settings were left untouched...

Thanks i'll try later this week

MalharB said:
Thanks i'll try later this week
Click to expand...
Click to collapse
This is stricktly 100% stock no mods no nothing everything included

TheMadScientist
No bags/No wallplugs[/QUOTE said:
?????
And btw, Congrats! ?
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse

Well I almost did mine in. Dropped from 2 foot in my otter box. I loca glued another tempered glass on top and as good as new

Debloated at all by chance or no? I read the OP and it said nothing of it so I assume no but I thought I would ask.
Sent from my Samsung SM-G950U using XDA Labs

bradical711 said:
Debloated at all by chance or no? I read the OP and it said nothing of it so I assume no but I thought I would ask.
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
Nope. I figured keep it full as soon as anything where to come out you woulda wanted that. Lol. Fully bloated. Plus it gives each of you something to do for the day...???

Any chance of seeing a super stock BRB1 IMG sometime soon at all?
Sent from my Samsung SM-G950U using XDA Labs

bradical711 said:
Any chance of seeing a super stock BRB1 IMG sometime soon at all?
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
I would assume its the same method as this i will download the firmeware to day and extract it all and post it up:good::good::good:
remember we can only go as far as u2 is.... and no oreo as we do not have a permissive kernel..
On a side note some reason I cant download firms from sam mobile so Im using some off site no name site But will upload em to my drive for your pleasure of downloading
And on a second side note you should be able to more or less dirty flash this one But I would reflash SU and busy box just incase as well as any other system based mods you do Cause as again this will be 100% stock so any debloation you have done will be undone again This note is for any one already running the stock rooted system not coming from other roms

bradical711 said:
Any chance of seeing a super stock BRB1 IMG sometime soon at all?
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
It is done good sir

TheMadScientist said:
It is done good sir
Click to expand...
Click to collapse
Thank you so much! I greatly appreciate it. I will update to the stock (BRB1) IMG when I'm off work later and update from PartCyborgs (BQL1) which I've been using as my daily driver for months on end lol. Anyways, thank you again, it is much appreciated by me and the community!!
Sent from my Samsung SM-G950U using XDA Labs

By the way @TheMadScientist, you should make a correction to your OP about your build number versions. One of them is wrong. Specifically when you say the build number BLQ1 twice in the OP. It should be BQL1 instead of BLQ1 so people don't get confused. I know it's a minor typo but I thought I'd point it out. Or maybe you noticed but didn't care to fix it, who knows lol. Also, quick question, is there anyway I could go about deodexing these ROMS of yours? Or should I message PartCyborg how to go about it?
Sent from my Samsung SM-G950U using XDA Labs

bradical711 said:
By the way @TheMadScientist, you should make a correction to your OP about your build number versions. One of them is wrong. Specifically when you say the build number BLQ1 twice in the OP. It should be BQL1 instead of BLQ1 so people don't get confused. I know it's a minor typo but I thought I'd point it out. Or maybe you noticed but didn't care to fix it, who knows lol. Also, quick question, is there anyway I could go about deodexing these ROMS of yours? Or should I message PartCyborg how to go about it?
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
I can't remember what he used to to it. I would msg him. I'll fix typos later lol. I didn't even notice

So now after several weeks. I can most def say cyborgs rom has much better battery life. Than stock. I still make it through the day but at the end I'm finding myself with 25 to 35% now instead of 35 to 55
I have slightly underclocked. And a few build prop tweaks from back in the day. But seems pretty rock solid....

I'm in oreo g950u.
My bootloader version 3.
is that work? Can you give tutorial in video?
I'm from indonesia.sorry for my bad english

Vicky_666 said:
I'm in oreo g950u.
My bootloader version 3.
is that work? Can you give tutorial in video?
I'm from indonesia.sorry for my bad english
Click to expand...
Click to collapse
This will not work with BL 3. You cannot downgrade either. There is no way for you to root with ANY ROM on the regular S8 above BL 3 as of right now.
Sent from my SM-G950U using XDA Labs

Thanks for the step by step.. I'm hoping to do this with the g950u1 firmware. I am guessing since you said you must start with rooted firm, if I use magisk and get systemless root the add safe strap then proceed to your steps that should put me in the right direction.. then I could make a full system backup to make a flushable stock pre rooted firmware I could store in case of a rainy day.. does this sound logical or am I a bit mistaken?. I'd like to create a true 4 file firmware from a system backup after I make any adjustments or add any apks so that if I ever need to reinstall.. everything will flash without having to readjust settings or use data to download any of the apps/flushable .zip files as well as avoid the need for re writing the build.prop and such. I'm open for any suggestions if you have any. Thanks again!

In first part there is no CP just sys.img SU & BusyBox
So I assume no need of CP there
And in BRB1 there is CP file do we have to flash that thru regular Odin or we can skip that.
Thanks

MalharB said:
In first part there is no CP just sys.img SU & BusyBox
So I assume no need of CP there
And in BRB1 there is CP file do we have to flash that thru regular Odin or we can skip that.
Thanks
Click to expand...
Click to collapse
You can flash that to update your baseband to the latest rootable with Odin. Just so you can have all the latest updates possible
The CP is totally optional though

TheMadScientist said:
You can flash that to update your baseband to the latest rootable with Odin. Just so you can have all the latest updates possible
The CP is totally optional though
Click to expand...
Click to collapse
Thanks

Downgrading stock Samsung

I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app

Try This
Pawprints1986 said:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi there,
Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you
You can try and use this website as I Prefer this website than Sam mobile
The website is www.updato.com

Pawprints1986 said:
I just had this thought... Since Samsung is basically on lockdown now.... I wonder what would happen if you install a custom ROM, in order to make the phone not care which android version or security version you currently have, and then tried to flash the downgraded stock rom that you wanted in the first place? Anyone ever tried this?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
First of all, if the bootloader is locked, you can't flash a custom ROM, so that shoots that idea in the head.
Second, a custom ROM is basically only a system.img and kernel. Even if you were able to flash a custom ROM, your stock bootloader is still there. Flashing a custom ROM will not change whether or not you can downgrade the bootloader, the part of your device where bootloader is located is unaffected by any custom ROM or system.img.
Sent from my LGL84VL using Tapatalk

KIBS2173 said:
Hi there,
Well I have tried downgrade from firmware 6.0 to 5.0.2 and it did work so it might work for you
You can try and use this website as I Prefer this website than Sam mobile
The website is www.updato.com
Click to expand...
Click to collapse
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?
Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares

Try This
Pawprints1986 said:
What was your software versions before and after the downgrade? Im just curious if you were still on the first bootloader version and thats maybe why it worked?
Ive been doing a little reading on combination roms... but im not sure where a reliable source would be, or if i can make my own combining 2 different firmwares
Click to expand...
Click to collapse
Hi there,
well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0
I was however able to update the phone from version 5.0.2 to 6.0 using ODIN
and the phone rebooted with new boot loader, recovery, and even it has a new downloader.
The phone was working alright but it didn't had any playstore.
I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason
So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.
And it was flashed successfully.
And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.
And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.
Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.
So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version

KIBS2173 said:
Hi there,
well I was using a Samsung A5000 which was the original version of the A5 series and it was the Chinese version of the phone, so therefore it had the HONGKONG VERSION on it in order to get Google PlayStore because playstore is banned in China. However, the HongKong Samsung service only updated the phone up to version 5.0.2 and China had the latest firmware update which was android 6.0
I was however able to update the phone from version 5.0.2 to 6.0 using ODIN
and the phone rebooted with new boot loader, recovery, and even it has a new downloader.
The phone was working alright but it didn't had any playstore.
I tried numerous ways to install playstore which resulted the phone to lag and heat up for some reason
So I had to downgrade it from 6.0 to 5.0.2 and I used ODIN again.
And it was flashed successfully.
And no when I flashed it from 5.0.2 to 6.0 it had the new boot loader and I didn't have to unlock the boot loader at all.
And I think by 2017 THE SAMSUNG KNOX service was discontinued so i don't see a reason why there would not to downgrade your phone.
Combining two roms with different coding can brick your phone. As most custom roms are built by building over the existing rom.
So by concluding you can try to downgrade the firmware or you can change the firmware to another region or you can wait till samsung to release another software update which might fix your problem or just re-install the whole OS with the same version as there might be a missing file when it was updated to that version
Click to expand...
Click to collapse
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk

Try this
Droidriven said:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi there,
Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong
BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE

KIBS2173 said:
Hi there,
Well I have tried to combine 2 firmwares together which ended up bricking one of my android devices. since it was a mediatek device I just gave up on the SPFLASH TOOL as it just gave out error codes. However if you have tried it and became successful well think i have done something wrong
BUT I THINK IT WILL BE ALRIGHT FOR YOU TO DOWNGRADE THE DEVICE
Click to expand...
Click to collapse
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.
What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
Sent from my LGL84VL using Tapatalk

TRY THIS
Droidriven said:
Were the two firmwares that you tried to combine for the exact same model number device? Or were they for a different device? That makes a difference.
What I described is basically the same as porting a Samsung firmware from a US variant of a device to work on an international model of the same device(i.e. port stock lollipop for a US variant of Samsung Galaxy S6 to work on an international variant of Samsung Galaxy S6). It's a common procedure.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi there,
Yeah they were for the exact phone and model. For some reason SpFlash Tool bricks Mediatek Devices. I think someone should create another version of spflash tool just like ODIN. Odin is actually a great software to flash all Samsung devices I Had no problems with it.
But Spflash tools are still in Beta mode. The software is not reliable.
I had to get a new motherboard for my device because of the hard brick however my pc is still able to detect the device but it won't install the firmware. Keeps on giving me error 4032 something like that.

Droidriven said:
Combining 2 firmwares that were made for the exact same model number, does not cause a brick unless it wasn't done correctly. For example, a 5.0 firmware can be mixed and matched with a 6.0 firmware if they are for the same device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Can you lead me to anywhere explaining how to do this in detail?
I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...
I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.
Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
Can you lead me to anywhere explaining how to do this in detail?
I'm still researching. I saw somewhere that Oreo had a not as strict security downgrade and there was possibility that upgrading to Oreo and then downgrading to marshmallow might work.... But I tried to no avail. So there goes that theory...
I wasn't concerned about the upgrading as nougat and Oreo are basically the same, I'm not really losing or gaining by varying between those 2.
Still would love to have the best of both worlds though... Appearance of lollipop/marshmallow in all areas but with version either 7 or 8. The leaks of samsungs spin on 9 look a little promising.... A little.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Here is a guide to extract the two firmware files.
Extract one firmware in a folder of its own and extract the other in its own folder.
https://www.rwilco12.com/forum/showthread.php?tid=74
You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.
https://forum.xda-developers.com/showthread.php?t=2446269
Or this guide
https://www.rwilco12.com/forum/showthread.php?tid=92
***NOTE***
Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Here is a guide to extract the two firmware files.
Extract one firmware in a folder of its own and extract the other in its own folder.
https://www.rwilco12.com/forum/showthread.php?tid=74
You basically only need to switch the system.img from the older firmware, in other words, remove the system.img from the firmware that won't allow downgrading, then, extract the system.img from the older firmware that you want to downgrade to, then put the older system.img into the firmware that won't allow downgrading. Then repackage the file into an Odin flashable .tar.md5 following this guide.
https://forum.xda-developers.com/showthread.php?t=2446269
Or this guide
https://www.rwilco12.com/forum/showthread.php?tid=92
***NOTE***
Some things may have changed since those guides were written. You might need to switch more than just the system.img files from the two firmware files. Do some researching and reading to find out and understand exactly which parts you need to swap around in order for the finished file to flash correctly.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night
I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! it sounds safer than just leaving components out completely

Pawprints1986 said:
Thanks! My brain is kinda pooped for tonight, but I will definitely dig into these tomorrow night
I had read a bit about removing the sboot.bin file from the firmware i want to use, but it feels risky to remove it entirely. I like the idea of using it but allowing that other system image to flash, much like youve described! it sounds safer than just leaving components out completely
Click to expand...
Click to collapse
Also, do some Google searches for:
"How to port Samsung stock firmware"
Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Also, do some Google searches for:
"How to port Samsung stock firmware"
Or similarly worded searches to understand what is involved when modifying Samsung stock firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.
Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
So, if I try this, and it doesn't work.... Is the worst case still that I may need to reflash twrp and the official firmware that does work? I had that happen when just regularly trying to flash the marshmallow official firmware, I think it's called "soft brick" cuz it wiped the nougat/oreo but couldn't install anything in its place, but I found my way out of it with no issues. And since I have no personal things on there yet I wasn't worried about wiping and losing anything. I have a twrp backup I also made of nougat after rooting but before messing with anything, so I've got that to fall back on too.
Still reading but just wanted to be sure, that the worst case is just needing to reflash proper working firmware/recovery if needed.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
Sent from my LGL84VL using Tapatalk

Droidriven said:
As long as the two firmware are for the same device and as long as you read carefully about what you're doing and you don't do something completely wrong, the worst you should expect is a soft brick or a bootloop, in which case, you'd flash the original stock firmware or you'd flash TWRP then restore the nandroid backup that you created from stock nougat.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.
I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
Sent from my [device_name] using XDA-Developers Legacy app

Pawprints1986 said:
New little snag. Oreo uses lz4 compression while Marshmallow uses regular .img disk image compression. I wonder if I'm better off converting the marshmallow one to lz4 or converting the other Oreo files I'll be using into regular img files. Hmm.
I did start to Google that and people have converted the Oreo files to img before Odin could read the lz4 ones. But I wonder if the other way around could work too. Or, do they even need to be the same? Hmm.... Will need to do a bit more reading than expected
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Exactly, this isn't the kind of thing that has a clear cut, everything you want to know guide. It's the kind of thing you'll have to figure out and piece together from different sources.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.
Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.
I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.
The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.
so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there.
ETA: So I just decided to go through everything once more, and decided to keep certain files as bin files like original, and the other files as img, as they were originally within the oreo rom. I was mistakenly thinking that all files had to be either img or bin, but upon another check through i did notice that the file type within the same rom can vary. I feel better about that now Still just working on the courage to flash it. I didnt truly edit any of the files. I only either renamed the extension thereby converting types of files. otherwise i only decompressed and then recompressed things. I didnt do any true open notepad and edit type stuff. Just sticking with the basics here

Pawprints1986 said:
Okay, so upon some more research, and finding a couple of tools here on xda, heres what ive been able to do.
Before I did anything I made copies of both roms in a separate new folder, so that I wasnt modifying my original downloads.
I decided that since I had read about people doing this successfully before Odin could read lz4 compression, here on xda I found a tool and removed that compression. Since marshmallow uses img but oreo uses bin files, I then found another thread that states that you can simply rename the file with extensions visible to convert them from .bin to a regular .img, like marshmallow uses. I did this for all the oreo files, replacing only the system.img with the marshmallow one, removing the oreo one to another folder for now. (The only thing im still debating is if i should have gone the other way, and renamed the marshmallow system.img into a .bin file instead. If I try and it fails, that may be my next attempt.) I was then able to use another tool I found here on xda to take the new tar files I made and replace the .md5 extension and recompressed my new editions. There were a few folders within these tar files originally (Meta data was one) that I simply left alone but included in the same tar file that they were in before.
The only thing ive yet to do is actually try to flash them. But, if Ive read everything properly, they are ready to flash. Im only nervous to find out if the absolute worst case if it doesnt work is it will give me some kind of error. the only one i didnt bother with was home_CSC since that 1 is only for restoring with your files present, and im looking to start from scratch, so ill keep those removed from the mix.
so basically the only thing i changed was bin files to img files, and removed the oreo system.img and put the marshmallow system.img in its place. Im wondering now if i should go back and change those files back to .bin extensions. Then that way nothing crutial can screw up? hmm.... but im *almost* there
Click to expand...
Click to collapse
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.
I can't say that I'm 100% certain about this, but..
As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.
I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
Sent from my LGL84VL using Tapatalk

Droidriven said:
I'm not sure about changing back to bin files or not. You could always make a copy that is not converted and a copy that is converted.
I can't say that I'm 100% certain about this, but..
As long as you are working with stock files and followed instructions, you shouldn't cause any real permanent damage but you might get errors of some kind, those might be correctable. You might cause a soft brick or have to restore the device by some complex processes but it should be restorable, sometimes its tough to restore but can be done.
I would look for information about whether the question about bin vs img is a valid question and what potential problems it can cause.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
This is becoming so beyond frustrating... I went though tonight, deleted my previously modified files... I wanted to go through and only undo the lz4, without all that renaming I had done. Did that just fine.
Gather up the guts to finally try it in odin though? Well, i dont even know what the error is. In odin 3.13, it gets to "file analysis" and just sits there. I unplugged and was still even able to restart the device back in to the oreo that was still on it, it did nothing at all. So i did a little bit of searching and it seems that an older version of odin fixes this. So i downloaded the recommended 3.09... Odin gets to the same point and then the program straight up shuts down! Ive even tried compatibility mode for windows 7 thinking maybe. I had ran it as administrator each time.
so the phone is fine.... but i cant get the program to even try it let alone give me any kind of error to work with....
ive given up for tonight!
The other idea i had was to check "phone bootloader update" in odin and just try to flash the straight up marshmallow rom, but googling that gets mixed results.