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.
Related
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.
Hello everybody!
I was searching the web when I found this website (link: http://android-soluciones.blogspot.com/2016/12/archivos-eng-boot-samsung_27.html? ) offering the Engboot files for the SM-G93xx too, therefore, I downloaded this file "ENG_BOOT_G935F_PH3.tar" from the website and opened it with WinZip to confirm if it even stands up to basic scrutiny, it had a "boot.img" file in it, which seems legit. (Screenshot attached)
I then decided to download all of the S7 and S7 edge links on the website and zip them all up. So, well here you go!
Link to Folder: Google Drive link :fingers-crossed::fingers-crossed:
Hope this is Legit!
UPDATE: Thanks to @murtaza02, @Rainbow_Dash and @GethPrime, we have confirmed that the Boot file is valid, however the Sboot file seems to be signed and has hints of it being a bootloader. If that is good enough for you, you may try and flash the file to your device! Though I am in NO way encouraging anybody to flash the files and will not be held liable for any damages.
By the way, All links have been updated to Google Drive!
UPDATE #2: Thanks to @Rainbow_Dash , who bravely flashed the Engkernel for his phone from the source website to his S6 Edge+ , we now know for sure that the at least the engkernels are VALID! Rainbow then also ran the root.bat file from here (Link: Root.bat XDA thread link). Result: The phone boots up and it shows that it is an Engkernel, furthermore, the root.bat worked and the S6 got root!
Disclaimer: Nobody who has contributed to this thread can be held responsible for any and all damages to your phone related to the content of this thread.
do you really trust a website named Adroid Soluciones ending in a domain that changes with your country you live in?
just flash it, see how your S7 would turn up into a useful brick.
avatar_ro said:
do you really trust a website named Adroid Soluciones ending in a domain that changes with your country you live in?
just flash it, see how your S7 would turn up into a useful brick.
Click to expand...
Click to collapse
This website has extracted these files from this website (Link: www.rohitfileserver.com ) which admittedly is not reputable too, but is more reputable than some random website on the internet, especially as it charges users to download the files from its server.
Edit: Additionally the Engboot Files are listed as for Exclusive users only.
Sent from my Samsung SM-G935F using XDA Labs
try flash and let us know whats happen
Sooo what is this engboot for?
magikmichael said:
Sooo what is this engboot for?
Click to expand...
Click to collapse
Engboot files are bootloader files that are signed by the manufacturer (Samsung) so that they do not trip the flash counter (Knox) and disable things such as DM-Verity. They are primarily kept secret by the manufacturer and are used by the devs of that company, the No Knox rooting method for Snapdragon S7 and S7 edge was made possible through the leaking of the Engboot for Snapdragon firmware. Please correct me if I am wrong as I am quite new to the world of rooting and flashing, especially on Samsung devices.
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
Engboot files are bootloader files that are signed by the manufacturer (Samsung) so that they do not trip the flash counter (Knox) and disable things such as DM-Verity. They are primarily kept secret by the manufacturer and are used by the devs of that company, the No Knox rooting method for Snapdragon S7 and S7 edge was made possible through the leaking of the Engboot for Snapdragon firmware. Please correct me if I am wrong as I am quite new to the world of rooting and flashing, especially on Samsung devices.
Click to expand...
Click to collapse
Thanks for clearing this up. Didnt know this and i am not new to rooting. I've been around here since my HTC Wildfire. Would be awesome if its true so we can root without trippin knox 0x1.
Random04 said:
Engboot files are bootloader files that are signed by the manufacturer (Samsung) so that they do not trip the flash counter (Knox) and disable things such as DM-Verity. They are primarily kept secret by the manufacturer and are used by the devs of that company, the No Knox rooting method for Snapdragon S7 and S7 edge was made possible through the leaking of the Engboot for Snapdragon firmware. Please correct me if I am wrong as I am quite new to the world of rooting and flashing, especially on Samsung devices.
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
Thing is files on that site are boot.img (Kernel with ramdisk and stuff and not the bootloader) so i dont really see how this would help on getting root while keeping knox efuse intact well if anyone is willing to flash these to test go ahead but i wouldnt advise so
So this is actually the engKernel and NOT engBootloader? If true, people already tried rooting using engKernel. Didn't work. DM-Verity kicked in upon reboot ever time.
There is an engineering boot file in the folder it is named in the name of ENG_SBOOT (if I am right).
Edit: There is also an "ENG_ROOT" file which may be an actual modified boot file (though I do doubt that It is) :fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
There is an engineering boot file in the folder it is named in the name of ENG_SBOOT (if I am right).
Edit: There is also an "ENG_ROOT" file which may be an actual modified boot file (though I do doubt that It is) :fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
Nah it would have to be called sboot.bin in order to be recognised as a bl. By odin
fake ?
Probably the same one we had. Any one try yet on nougat?
Sent from my SM-G928T using Tapatalk
Ivan_Meler said:
Nah it would have to be called sboot.bin in order to be recognised as a bl. By odin
Click to expand...
Click to collapse
Umm... It is actually called SBoot.bin it is just zipped up in that folder, I opened it with WinZip and it has a file named sboot.bin in it.
I will upload a screenshot when I can use my laptop.:good:
Edit: Here is the screenshot, I have also uploaded a link to the sboot, engboot, and the questionable engroot files in this post separately so people can look into it without downloading the whole folder.
Link: SM-G935F.zip Google Drive link
Root-Maniac said:
Probably the same one we had. Any one try yet on nougat?
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
Please don't try on Nougat as the files seem to be ordered by the last letters in their firmware. I am not sure what is the firmware number for Nougat, so if you would try please try after checking the firmware because flashing an Marshmallow bootloader to a Nougat ROM would probably almost definitely brick it. I recommend installing it on Marshmallow first.
I guess we are waiting for the (proverbial) other shoe to drop? (i.e. Someone who was going to root their phone, warranty be damned and may try the files on their device) As it seems (at least to me) that the files are (at least) somewhat legit.
It seems to me that the real question is if the files will trip KNOX?
Hoping they will not! (for whoever feels brave enough to try :fingers-crossed: )
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
I guess we are waiting for the (proverbial) other shoe to drop? (i.e. Someone who was going to root their phone, warranty be damned and may try the files on their device) As it seems (at least to me) that the files are (at least) somewhat legit.
It seems to me that the real question is if the files will trip KNOX?
Hoping they will not! (for whoever feels brave enough to try :fingers-crossed: )
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
Someone recently found Engboot files for the S7 active on a paid site, so it's definitely possible this is legit.
https://forum.xda-developers.com/showthread.php?t=3473649
I'm on nougat and not using the device. If I thought it was for nougat I would have tried already
Don't have time to downgrade and try.
Sent from my SM-G928T using Tapatalk
Someone tried already ? Looks interesting
jal3223 said:
Someone recently found Engboot files for the S7 active on a paid site, so it's definitely possible this is legit.
https://forum.xda-developers.com/showthread.php?t=3473649
Click to expand...
Click to collapse
Thanks for the legit vote! I am definitely hoping this would work and have no intention whatsoever of spreading malware. By the way, I am currently also trying to open the file and check it out, as I am a total newbie, it would help quite a lot if someone experienced would like to check this out and confirm this is legit or malware. (hint, hint)
Otherwise, it may take me some time to figure this out.
By the way, Can anyone point me to a tutorial about opening boot.img and/or sboot.bin files on Windows (if possible) (maybe through Cygwin)? I would really appreciate it!
Edit: Thanks to jal3223, I am planning to check if these are valid files through comparing them side-by-side to the files that are confirmed legit for the S7 Active.
Thanks jal3223! :good:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..
khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..
khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude
NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.
najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how
NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.
I rooted last night using SamPwn and everything was working well until today... After one of the reboots I did today my phone stopped showing service, my sim card, network operators, and it wont hold an apn.
I have tried power cycling, removing the sim, resetting network settings, and wiping all cache.
Is there any way to only reflash the network portion? I have rooted and flashed quite a few things but havent bothered going into the intricacies and I feel as though this phone has less wiggle room for error. Hopefully you guys can get me a swift answer.
Thanks in advance!
BumpinPanda said:
I rooted last night using SamPwn and everything was working well until today... After one of the reboots I did today my phone stopped showing service, my sim card, network operators, and it wont hold an apn.
I have tried power cycling, removing the sim, resetting network settings, and wiping all cache.
Is there any way to only reflash the network portion? I have rooted and flashed quite a few things but havent bothered going into the intricacies and I feel as though this phone has less wiggle room for error. Hopefully you guys can get me a swift answer.
Thanks in advance!
Click to expand...
Click to collapse
Searching the SamPWND thread should net you a literal ton of solutions, but I'll try to sum it up for you.
Extract the stock firmware for whatever version you're running (QGL,QH3, ETC), and be sure to use 7zip for all of these extraction/archiving steps, then extract the modem.bin from the CP file and NON_HLOS.bin from the BL file. Now, highlight modem and non_hlos files and use 7zip to add to archive, you'll want to keep everything default, and the end result should be a tar file with whatever name you chose for the archive. Use Odin to flash this archive in the AP slot, it should work fine, but if not, you can try using the modified Odin (all default options for both). Once done, be sure to reboot to recovery and clear the cache and also a Network factory reset from settings if you're still unable to gain signal. If you're still not getting signal, you can try flashing the entire CP file and Home_CSC file (be sure to use the HOME_CSC, as regular CSC will overwrite root and start you over from scratch) using their respective slots in odin, though if modem and non_hlos doesn't get it up and running, that may be a redundant step.
Good luck!
instead you can flash combination file COMBINATION_FA70_G955USQU1AQD8 , just google for it. that will help to get Network Signal again
IJoxer said:
Searching the SamPWND thread should net you a literal ton of solutions, but I'll try to sum it up for you.
Extract the stock firmware for whatever version you're running (QGL,QH3, ETC), and be sure to use 7zip for all of these extraction/archiving steps, then extract the modem.bin from the CP file and NON_HLOS.bin from the BL file. Now, highlight modem and non_hlos files and use 7zip to add to archive, you'll want to keep everything default, and the end result should be a tar file with whatever name you chose for the archive. Use Odin to flash this archive in the AP slot, it should work fine, but if not, you can try using the modified Odin (all default options for both). Once done, be sure to reboot to recovery and clear the cache and also a Network factory reset from settings if you're still unable to gain signal. If you're still not getting signal, you can try flashing the entire CP file and Home_CSC file (be sure to use the HOME_CSC, as regular CSC will overwrite root and start you over from scratch) using their respective slots in odin, though if modem and non_hlos doesn't get it up and running, that may be a redundant step.
Good luck!
Click to expand...
Click to collapse
Thank you for this. I did a few queries in there and didn't come up with much but that could be due to my lack of optimized searching.
I ended up reflashing the csc and it wiped all my data but restored my data. I was at work when this happened and, being that I work in a Verizon, I need my phone quite a lot. I have since backed up my EFS and noted the suggestions in this thread so it will not happen again.
Once again I appreciate the help and I am sure it will save me in the near future!
012345678 said:
instead you can flash combination file COMBINATION_FA70_G955USQU1AQD8 , just google for it. that will help to get Network Signal again
Click to expand...
Click to collapse
I will try this next time this happens, thanks!
BumpinPanda said:
I will try this next time this happens, thanks!
Click to expand...
Click to collapse
Just note that the combination firmware he referenced is a universal firmware, and if you use a vzw firmware (ie QGL), it tends to cause issues with data/connectivity. Mixing carrier firmware and universal firmware has always cause me to start fresh, after 20+ roots using SamPWND, we finally came to that consensus.
Just something to keep in mind, 955U1 and 955U do not mix, regardless of version.
IJoxer said:
Just note that the combination firmware he referenced is a universal firmware, and if you use a vzw firmware (ie QGL), it tends to cause issues with data/connectivity. Mixing carrier firmware and universal firmware has always cause me to start fresh, after 20+ roots using SamPWND, we finally came to that consensus.
Just something to keep in mind, 955U1 and 955U do not mix, regardless of version.
Click to expand...
Click to collapse
Funnily enough, besides this issue, my service improved over stock with the root.
But even if that's the case doesn't the U1 simply signify an unlocked firmware version? Why does that cause an issue?
BumpinPanda said:
Funnily enough, besides this issue, my service improved over stock with the root.
But even if that's the case doesn't the U1 simply signify an unlocked firmware version? Why does that cause an issue?
Click to expand...
Click to collapse
Well, technically, it stands for a universal firmware, but I knew what you meant. 955U firmware is carrier specific, while U1 is Universal, as in it should apply to whichever carrier you have, so long as your sim card is in working order and tells the firmware which CSC to use correctly.
For whatever reason, when rooted and flashing the U1 firmware, the csc doesn't quite stick as it should, at least in my observations. Obviously flashing the modem and non_hlos is supposed to cure this issue (no data/connectivity/modem crashes), but I find it doesn't do much but change it in prop settings. My theory is that it's something to do with the efs partition superceding the csc flashed to system after using Ufirmware for root.
Regardless, I'm still trying to find a way to alleviate this issue, but it's a known bug that should be noted when rooting and using a mixture of U and U1 firmware.
IJoxer said:
Well, technically, it stands for a universal firmware, but I knew what you meant. 955U firmware is carrier specific, while U1 is Universal, as in it should apply to whichever carrier you have, so long as your sim card is in working order and tells the firmware which CSC to use correctly.
For whatever reason, when rooted and flashing the U1 firmware, the csc doesn't quite stick as it should, at least in my observations. Obviously flashing the modem and non_hlos is supposed to cure this issue (no data/connectivity/modem crashes), but I find it doesn't do much but change it in prop settings. My theory is that it's something to do with the efs partition superceding the csc flashed to system after using Ufirmware for root.
Regardless, I'm still trying to find a way to alleviate this issue, but it's a known bug that should be noted when rooting and using a mixture of U and U1 firmware.
Click to expand...
Click to collapse
Are you staying on root or stock? The root has helped my data issue slightly over stock and apparently the update for the stock firmware to fix my issue is in the works (but not yet released).
If you do find a stable solution let me know, it's working for now but I still drop to 1x frequently (which happened before root as well).
Thanks again for your help
BumpinPanda said:
Are you staying on root or stock? The root has helped my data issue slightly over stock and apparently the update for the stock firmware to fix my issue is in the works (but not yet released).
If you do find a stable solution let me know, it's working for now but I still drop to 1x frequently (which happened before root as well).
Thanks again for your help
Click to expand...
Click to collapse
Root does seem to help if, like I said, you don't mix and match firmwares, I'm on stock at the moment but will be rerooting tonight. There is a new carrier firmware for vzw and TMO, I'll be using vzw to accomplish the second part of the root method and updating to it (QI6). I'll update with how it goes later tonight or tomorrow, but here the link for the newest vzw firmware.
http://updato.com/firmware-archive-select-model?record=E15BA006A8B211E7963AFA163EE8F90B
IJoxer said:
Root does seem to help if, like I said, you don't mix and match firmwares, I'm on stock at the moment but will be rerooting tonight. There is a new carrier firmware for vzw and TMO, I'll be using vzw to accomplish the second part of the root method and updating to it (QI6). I'll update with how it goes later tonight or tomorrow, but here the link for the newest vzw firmware.
http://updato.com/firmware-archive-select-model?record=E15BA006A8B211E7963AFA163EE8F90B
Click to expand...
Click to collapse
Ah, I see. Root helped even though I used the universal firmware in the SamPWND thread (that could just be an individual issue regarding my area/device).
I'd love to see the results of the new firmware so I am looking forward to your update! Was that the main reason you chose to remove root? That and the 80% situation are the only things bothering me so far. Appreciate the link, you saved me a search
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