Database Info

[Q] CM7 to Stock 2.3.4

Hey,
I'm new to Android, and still pretty bad with it, so when I set out to flash a custom rom last week, I never bothered to setup a backup. I didn't think it was going to be as complicated to get back to the way it was when I took it out of the box. I guess I'm still use to the iPhone. Now, I'm not completely happy with my phone and am looking to go back to stock.
I've looked in to it, and it seems easy enough, but I just have a couple of questions:
Pre-CM7 I'm pretty sure my phone was GRI54, and i9020, It's now GRI40. Does this make any difference?
And, finally, where can I download an official version of this?
Any help is greatly appreciated,
Thanks.

Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=1056062

Graham19 said:
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've downloaded the i9020a one, but when I'm trying to update it it's saying "Installation aborted". I tried doing it from clockwork mod - and I don't know anything about it. Do you know where I'm going wrong here?

tylerisgood said:
I've downloaded the i9020a one, but when I'm trying to update it it's saying "Installation aborted". I tried doing it from clockwork mod - and I don't know anything about it. Do you know where I'm going wrong here?
Click to expand...
Click to collapse
Use the unofficial full rom for the i9020a. apply it from cwm. Then wipe the phone
Sent from my Nexus S

Matridom said:
Use the unofficial full rom for the i9020a. apply it from cwm. Then wipe the phone
Sent from my Nexus S
Click to expand...
Click to collapse
Do you know where I can get this download from?
I haven't been able to find anything for this. The closest I found was someone saying 'use this one instead', but that got me stuck at the Google screen.

tylerisgood said:
Do you know where I can get this download from?
I haven't been able to find anything for this. The closest I found was someone saying 'use this one instead', but that got me stuck at the Google screen.
Click to expand...
Click to collapse
It is in my sticky for the 2.3.4 ota. Very first post
Sent from my Nexus S

Matridom said:
It is in my sticky for the 2.3.4 ota. Very first post
Sent from my Nexus S
Click to expand...
Click to collapse
Sorry, maybe I'm doing something wrong, but I've tried using that zip a few times (286d814dee5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip 12mb) and it says install failed.
I boot into recovery, factory reset, wipe cache, install zip from sd card, pick the file, agree.

Have you checked the MD5 hash to ensure the download isn't corrupt?

Graham19 said:
Have you checked the MD5 hash to ensure the download isn't corrupt?
Click to expand...
Click to collapse
I'm incredibly new to this, and have no idea what this means. How do I try this?

Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4

Matridom said:
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Click to expand...
Click to collapse
I love you. Thanks a lot

One last quick question:
Is it possible to get rid of clockwork?

tylerisgood said:
One last quick question:
Is it possible to get rid of clockwork?
Click to expand...
Click to collapse
yes, the default for all stock 2.3.4 roms will restore the recover back to stock on each reboots you have to rename/delete the install-recover.sh script to prevent it from happening

Matridom said:
yes, the default for all stock 2.3.4 roms will restore the recover back to stock on each reboots you have to rename/delete the install-recover.sh script to prevent it from happening
Click to expand...
Click to collapse
Sorry? I have to delete the files to keep clockwork from being removed?
All I did was flash it, restart, and clockwork was still there.
Also, my phone's internet speeds seem really slow now. Could this be from now having a different build? (GRI54 -> GRJ22)
Sorry for my complete lack of knowledge. It's quite obvious I jumped into something that's much over my head.

tylerisgood said:
Sorry? I have to delete the files to keep clockwork from being removed?
All I did was flash it, restart, and clockwork was still there.
Also, my phone's internet speeds seem really slow now. Could this be from now having a different build? (GRI54 -> GRJ22)
Sorry for my complete lack of knowledge. It's quite obvious I jumped into something that's much over my head.
Click to expand...
Click to collapse
A stock rom has the script. So flashing it will also restore stock recovery. If the rom you installed does not restore the recovery partition, the the rom was not completely stock.
Sent from my Nexus S

Matridom said:
A stock rom has the script. So flashing it will also restore stock recovery. If the rom you installed does not restore the recovery partition, the the rom was not completely stock.
Sent from my Nexus S
Click to expand...
Click to collapse
I used the rom you linked.

tylerisgood said:
I used the rom you linked.
Click to expand...
Click to collapse
I've never used it myself.
Looking over the zip file, the script has been renamed, so it's not 100% stock.
Normally you would need to root the phone to change the file name.
Perhaps renaming the file in the zip will correct the issue?
try renaming /etc/install-recovery.sh.bak to /etc/install-recovery.sh and re-apply the zip. ( no need to wipe )
That rom was posted by dsixda, he may be able to confirm what needs to be done.
If you had root, it would be fairly easy to rename it.

Matridom said:
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Click to expand...
Click to collapse
That was my upload, but is it confirmed that the radio in this one gets flashed to AUCKD2? I uploaded another one with the same radio but slightly different.

Matridom said:
Download this:
http://myunspace.com/?d=4DD679381
Install it through CWM
Wipe the phone
you now have stock 2.3.4
Click to expand...
Click to collapse
This doesn't seem to work. It does gets you back to stock rom but I still have the old modem I flashed, old APN, CWM Recovery and still there and factory reset doesn't works. Just hangs with the little Android guy and an exclamation mark.
Is there something like ODIN for Nexus S to go back to stock?

SpoonerPS3 said:
This doesn't seem to work. It does gets you back to stock rom but I still have the old modem I flashed, old APN, CWM Recovery and still there and factory reset doesn't works. Just hangs with the little Android guy and an exclamation mark.
Is there something like ODIN for Nexus S to go back to stock?
Click to expand...
Click to collapse
This should work:
http://android.grdlock.net/index.ph... S&PHPSESSID=9dc0c107b878587d1e0b21ec1e3130ef
This should bring you to stock 2.3.3 for the i9020a
Then apply the official patch:
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
This will then bring everything to stock 2.3.4 with proper baseband and recovery

[RECOVERY] Custom Recovery Image [CWM Touch 6.0.3.2]

https://github.com/StarKissed/ek-gc100_recovery
This recovery was made using the EK-GC110 recovery.img ramdisk from the latest firmware release. The CWM Touch 6.0.3.2 is from a Samsung Galaxy SGS3 (Same board), modified with the custom kernel for the EK-GC (stripped version from this forum). The original recovery was used to provide the corrected init and fatal values, but all other aspects are relatively identical to the SGS3.
The recovery functions work, and appear fully functional. Keep in mind this is still in the testing phase. Work is being done to rebuild the necessary device configuration files based on information about the EK-GC and SGS3. The only aspect untested is the sdcard formatting options.
StarKissed Galaxy Cam Recoveries
This brings custom recovery to the Galaxy Camera, which is accessible by holding the zoom toggle to the right (red indicator should be on +) and pressing the power button. The difference between recovery and download mode is whether or not the shutter button is also held. Keeping the shutter button pressed will result in launching the Odin download mode.

It gets better
Any idea if it works on the EK-GC100 (3G and Wi-Fi version) ?
Sent from my GT-N7100 using Tapatalk 4 Beta

RavenY2K3 said:
It gets better
Any idea if it works on the EK-GC100 (3G and Wi-Fi version) ?
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Should work on all variants. The radio isn't called by recovery so I see no reason it wouldn't.

I was thinking more along the lines of the partition tables, I wasn't sure whether there were differences in that respect between devices and, whether it makes a difference even if there was.
Sent from my GT-N7100 using Tapatalk 4 Beta

RavenY2K3 said:
I was thinking more along the lines of the partition tables, I wasn't sure whether there were differences in that respect between devices and, whether it makes a difference even if there was.
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If you have a root file browser, they are in /dev/block/platform/dw_mmc/by-name and the partition names should list where they link.
System is p9, boot p5, data p13, recovery p6
If they don't match, it would only be calling the by-name links instead of specific numbers. I avoided that for extra stability, but it would still work properly. I use the by-name for mounts and flashing in the zips already.

Hey I can't get this to flash.. stuck at NAND write when I use the gz and Odin says the MD5 is incorrect if I unpack first.
Any help?

GriffinSauce said:
Hey I can't get this to flash.. stuck at NAND write when I use the gz and Odin says the MD5 is incorrect if I unpack first.
Any help?
Click to expand...
Click to collapse
Download the tar version without the md5. Once the md5 is written to the file it can't be removed, but goo provides md5s to verify locally. I've tried md5 -r and that didnt work, but apparently neither did the homebrew md5sum

twistedumbrella said:
Download the tar version without the md5. Once the md5 is written to the file it can't be removed, but goo provides md5s to verify locally. I've tried md5 -r and that didnt work, but apparently neither did the homebrew md5sum
Click to expand...
Click to collapse
I see only .img and .gz files. Tried unzipping and removing the MD5 check, no dice.
Odin hangs at "NAND write" now.. Luckily no problems after resetting the device (no cwm though )

GriffinSauce said:
I see only .img and .gz files. Tried unzipping and removing the MD5 check, no dice.
Odin hangs at "NAND write" now.. Luckily no problems after resetting the device (no cwm though )
Click to expand...
Click to collapse
That's what I get for trusting my script. It missed copying the basic tar to the folder to upload. It should be uploaded shortly. That one should solve it.

twistedumbrella said:
That's what I get for trusting my script. It missed copying the basic tar to the folder to upload. It should be uploaded shortly. That one should solve it.
Click to expand...
Click to collapse
Argh, that didn't work either so I took a good hard look and I see I have an EK-GC100 ...
Sorry for wasting your time so far.
Do you think it is possible to make it compatible? Can I supply my stock recovery for that?

GriffinSauce said:
Argh, that didn't work either so I took a good hard look and I see I have an EK-GC100 ...
Sorry for wasting your time so far.
Do you think it is possible to make it compatible? Can I supply my stock recovery for that?
Click to expand...
Click to collapse
It should have been already but with the stock one I can make sure it will be
Sent from my PG86100 using Tapatalk 4

twistedumbrella said:
It should have been already but with the stock one I can make sure it will be
Sent from my PG86100 using Tapatalk 4
Click to expand...
Click to collapse
https://www.dropbox.com/s/osyk8p05kjcicjg/recovery.img
This is the stock recovery of my device. Thanks for taking the trouble!

GriffinSauce said:
https://www.dropbox.com/s/osyk8p05kjcicjg/recovery.img
This is the stock recovery of my device. Thanks for taking the trouble!
Click to expand...
Click to collapse
I didn't forget about you. Tomorrow I should be able to get something together that will work.

Alright, I took the stock recovery that was posted and used the kernel image and modules from that, tweaked the partition tables a little more, and hopefully it should now work. Samsung is weird. Some have an internal_sd and external_sd, some have sdcard and this extSDCard, some have sdcard and sdcard1. No wonder apps always have issues with trying to use the card.

twistedumbrella said:
Alright, I took the stock recovery that was posted and used the kernel image and modules from that, tweaked the partition tables a little more, and hopefully it should now work. Samsung is weird. Some have an internal_sd and external_sd, some have sdcard and this extSDCard, some have sdcard and sdcard1. No wonder apps always have issues with trying to use the card.
Click to expand...
Click to collapse
Thanks again!
Still no go. I tried recovery.08-13-2013_08.42.tar and recovery.08-13-2013_08.42.tar.md5. Still halting at "NAND Write Start!"
Tried with Odin v3.07 and 1.3. Also did flash a stock rom via Odin the other day, so it should work..
Could there be some write protection on the recovery?

GriffinSauce said:
Thanks again!
Still no go. I tried recovery.08-13-2013_08.42.tar and recovery.08-13-2013_08.42.tar.md5. Still halting at "NAND Write Start!"
Tried with Odin v3.07 and 1.3. Also did flash a stock rom via Odin the other day, so it should work..
Could there be some write protection on the recovery?
Click to expand...
Click to collapse
There shouldn't be. I don't use Odin, though. I have a Mac, so I have a compiled version of the Heimdall or whatever that one is. The original flash was done with Odin, though. I wonder if its a lock from the service provider. Let me see if I can somehow get a proper md5 attached. That may help.

Ah but I can try Heimdall too. I'll try tonight.
Sent from my HTC One X using Tapatalk 4

GriffinSauce said:
Ah but I can try Heimdall too. I'll try tonight.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Alright. At least then I can try to zero in on the issue.
Sent from my Galaxy Nexus using Tapatalk 2

I fixed the problem.
Just unzip and flash this through Odin.
Reboot with power + zoom+
You're in CWM recovery, enjoy!

Delux9364 said:
I fixed the problem.
Just unzip and flash this through Odin.
Reboot with power + zoom+
You're in CWM recovery, enjoy!
Click to expand...
Click to collapse
What problem? What model? What was done? If it's anything more than signing with the right md5, you may want to submit a pull request.

CF-Auto Root for MH8 firmware

Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!

Obagleyfreer said:
Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!
Click to expand...
Click to collapse
Pointless thread. Everyone knows to find chainfires thread.

boterkaaseneieren said:
Pointless thread. Everyone knows to find chainfires thread.
Click to expand...
Click to collapse
Well yes, but still good to know and please don't be offended by his comment. That kind of comment is indeed pointless! We're all here to learn and have fun, keep this kind of comment to yourself please...

Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.

can we downgrade with this

pnr2020 said:
can we downgrade with this
Click to expand...
Click to collapse
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way

donalgodon said:
Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.
Click to expand...
Click to collapse
Yeah that's what I thought too.
Hopefully we can fix it in time

Obagleyfreer said:
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way
Click to expand...
Click to collapse
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck

pnr2020 said:
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck
Click to expand...
Click to collapse
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?

give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade

pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122

DjeMBeY said:
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122
Click to expand...
Click to collapse
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile

I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t

Obagleyfreer said:
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?
Click to expand...
Click to collapse
Flashing older firmware with PIT didn't work for me.
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
Let me know if it works for you - unfortunately didn't for me.
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Click to expand...
Click to collapse
Any chance of a step-by-step guide on how you did this? Especially what you deleted. Also is there any chance it would work if you wanted to go back to an older stock ROM? Reason I want/need stock is because I use the Bluetooth RSAP profile - unless anyone knows if this is included in the CM ROMS...
If you boot into recovery does it have any of the KNOX lines or is the recovery with CM different to stock? If so perhaps it would be possible to do something like (assuming I've understood correctly) : Root Phone -> Install CM -> Un CM the phone with a stock ROM?

Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
please put up a step by step guide to what you did

pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes

@DjeMBeY
thanks for bootloader and i added here that same bootloader but for Odin cread as tar file
Zippyshare ---> http://www28.zippyshare.com/v/62712373/file.html

no work
DjeMBeY said:
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes
Click to expand...
Click to collapse
Im tested,and not working for me. Im use kt-sgs4 kernel with mh8 rom, with root, busybox and the system is ok...but the bootloader is nt cool, i cant intall any custom rom. No voice, and cant call. Odin .tar file no working nand flash fail...
I think install with odin mh1 rom, and install philztouch recovery and intall bootloader recovery...its fine?Thanx

Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.

donalgodon said:
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.
Click to expand...
Click to collapse
Hopefully it helps at least a couple of people.
The problem comes when you need to send your phone back to Samsung for warranty purposes.
Even if you have old firmware, reset flash counter etc. I can bet my bottom dollar when it returns from Samsung they would have flashed the new firmware and new bootloader to your device. They are great like that!!

Really afraid my phone might be broken, someone please help me. (Soft Bricked)

I'm going crazy. I wanted to upgrade my Samsung Galaxy S5 SM-G900F finally from 4.4.2 to 6.01. I rooted it years ago and never cared to upgrade through OTA, since it never worked. So I found out about the FlashFire app recently, and used it to flash a 6.0.1 firmware stock zip file I downloaded. Followed all instructions, left all deselected partitions as is, only flashed boot, recovery, system, cache and preload. FlashFire started working on it, reboots into loading logo screen for a while, I start getting concerned but then it loads up a screen showing "Optimizing files" of like 250. Once that got done, it rebooted. Here is where I'm stuck since then.
My phone has been soft bricked, it's stuck on an endless Samsung logo screen, that gently flashed back and forth, and there's a blue notification light on during this. So I googled what I can do, and I tried using Volume Up + Power Button + Home button, since that would get me into recovery mode. That works, but instead of the Samsung recovery mode I get the Clockwork mod recovery screen. I had completely forgotten that I even had that. But, the same options are there too, so I wipe cache, wipe user data, wipe dalvik and factory reset. Once I did that, I selected reboot.
And the same thing happens. Endless Samsung logo screen. Stuck on it for hours. Now I honestly don't know what to do. I've done the recovery mode options 3 times, nothing changes.
Someone please help me out, I can't figure out what went wrong and how I can fix it. I can't afford a new phone...Ideally, I would like to be able to completely reset the phone entirely to factory settings. Is this possible? I appreciate any advice I can get.

Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk

tys0n said:
Download odin and flash the whole firmware tar.md5.
4.4.2 to 6.0.1 is a big step so you'll probably need all partitions in that file.
Skickat från min SM-A310F via Tapatalk
Click to expand...
Click to collapse
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?

tempest22 said:
Thanks for replying. Which firmware? I don't understand what you mean by all partitions. Will this Odin method really fix my bootlooped phone?
Click to expand...
Click to collapse
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.

tys0n said:
For some reason the recovery flash diden't work, and custom recoveries can't extract the csc-zip that its inside cache.img.
It could be that bootloader, modem and other partitions needs to be updated as well.
Yes. I think you'll need to flash the whole firmware with odin.
Click to expand...
Click to collapse
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?

Help pls

tempest22 said:
When I googled how to properly use FlashFire when I first used it (which then lead to this soft brick) I read that you shouldn't flash the modem and other priority partitions that were unselected. So now I should do it?
Where is the best place to get firmware? And which firmware do I even get? 6.0.1? Or my old 4.4.2 to get it back to it's original state?
Click to expand...
Click to collapse
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.

tys0n said:
Either 4.4.2, 5.0 or 6.0.1 would do since you only flashed four partitions.
Use http://updato.com/firmware-archive-select-model?r=&v=&q=SM-G900F&exact=1&rpp=15
You can sort it by version, date, region etc.
Click to expand...
Click to collapse
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?

tempest22 said:
Ok. So you're saying I download let's say the 6.0.1 from there, then I download Odin, connect my phone in download made and flash ALL partitions from that firmware? This will get my phone out of this crazy bootloop Samsung logo soft brick it's been in for 3 days?
Click to expand...
Click to collapse
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.

tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Ok, how exactly do I flash whole .tar.md5 package? I've been looking at how to use Odin and I don't really see how to do that.

tys0n said:
You make it sound like odin is some shady, untrusted software while it's in fact the very same software that samsung service centers use, flashing the very same firmware packages. I'd say it's far more reliable than any app you can flash with.
They're only good for smaller partitions like boot, recovery but not for upgrading android versions.
I can't guarantie anything, but yeah, going from 4.4.2 to 6.0.1 I'd say you'll probably need updated bootloader, modem etc to make it work. Flashing whole .tar.md5 package will fix that.
Unless you have some better idea...
And don't be mad at me if it turns out it's not working.
You're the one who messed it up in the first place. I'm just trying to help.
Click to expand...
Click to collapse
Odin worked. Thanks!

Delete

Delete

Craz Basics said:
Would anyone be willing to test this for me? I replaced the "boot.IMG-ZIMAGE-file" (kernel) in the ENG bootloader with the one that is in the stock one, hopefully making this as stable as stock, and we can root. This I'm hoping will give is the same performance, so no more lag. Anyone who has this (the s7 or s7edge) that doesn't use it as a daily driver for example, and wouldn't be too sad if it bricked, would you mind checking this out?
"dm_verity_signature_checker" is still not in this boot.img, so I believe this should still have write protection off.
Thanks
S7Edge:https://drive.google.com/file/d/0Bygh6W_e2Fo5dnF5RE1sQ2w5X2c/view?usp=drivesdk
Flat S7:https://drive.google.com/file/d/0Bygh6W_e2Fo5Sm1aU3RZdUo3LTQ/view?usp=drivesdk
Just flash in AP and if successful try and root please - I used nougat files so I'd guess to be on nougat, not sure though
Click to expand...
Click to collapse
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
which firmware version is this made from? I am currently on the 930U QE2 fw.

r3xx3r said:
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
Click to expand...
Click to collapse
Okay thanks, I'll see if I can update

r3xx3r said:
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
which firmware version is this made from? I am currently on the 930U QE2 fw.
Click to expand...
Click to collapse
And this is from g930A, but shouldn't matter should it? Link is updated btw

I'm rooted and have no lag?

I tried flashing with princecomsy Odin and it failed. Some secure boot error came up.

sabresfan said:
I tried flashing with princecomsy Odin and it failed. Some secure boot error came up.
Click to expand...
Click to collapse
That's all I get as well. I can't seem to change anything and still flash. Try and flash with this?:http://glassechidna.com.au/heimdall/

riso123 said:
I'm rooted and have no lag?
Click to expand...
Click to collapse
How so?

I don't see how this would work. Has anyone had anything other than a brick or write fail error?

Craz Basics said:
How so?
Click to expand...
Click to collapse
No idea. I just don't. I'm not sure why rooting would present any lag anyway?

riso123 said:
No idea. I just don't. I'm not sure why rooting would present any lag anyway?
Click to expand...
Click to collapse
The point of this post lol. The ENG boot.img isn't meant for a daily driver. It's for samsung to test things (write protection is off). The kernel I guess wasn't tweaked for performance so it lags. Root doesn't make it lag, the boot.img does.

rlewis312010 said:
I don't see how this would work. Has anyone had anything other than a brick or write fail error?
Click to expand...
Click to collapse
Nope

r3xx3r said:
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
which firmware version is this made from? I am currently on the 930U QE2 fw.
Click to expand...
Click to collapse
Try again through flashfire? Pretty sure you gotta mount system

Craz Basics said:
Try again through flashfire? Pretty sure you gotta mount system
Click to expand...
Click to collapse
Downloading the Chinese rom from your other thread, but I tried to flash the modified s7 edge eng boot (becasue I have the s7 edge) before you edited the post through flashfire and right after it was done secure boot came in and had to stop it. So im pretty sure that in order to flash a boot.img not from samsung that we would have to change the bootloader (which I'm hoping the Chinese rom would do). FIngers crossed! :good:

branstonmorgan said:
Downloading the Chinese rom from your other thread, but I tried to flash the modified s7 edge eng boot (becasue I have the s7 edge) before you edited the post through flashfire and right after it was done secure boot came in and had to stop it. So im pretty sure that in order to flash a boot.img not from samsung that we would have to change the bootloader (which I'm hoping the Chinese rom would do). FIngers crossed! :good:
Click to expand...
Click to collapse
How did secure boot stop it?

Craz Basics said:
How did secure boot stop it?
Click to expand...
Click to collapse
I'm pretty sure flashfire successfully flashed it and then when my device rebooted secure boot told me that the firmware was not authorized and in parenthesis it said boot.img.

branstonmorgan said:
I'm pretty sure flashfire successfully flashed it and then when my device rebooted secure boot told me that the firmware was not authorized and in parenthesis it said boot.img.
Click to expand...
Click to collapse
Okay sweet. Could you flash the stock bootloader (BL file of stock firmware, not Chinese firmware) and see if flashfire can flash it? If it can then we should be able to flash Chinese firmware
Pretty sure you know but mount system
Also, I believe you're downloading the wrong firmware (my fault, I only put flat s7 link up).
It's updated Now, links for both s7 and s7 edge

This is getting good. That's one thing that was never tried. Using flash fire to flash the Chinese firmware.
Sent from my SM-G935U using Tapatalk

Root-Maniac said:
This is getting good. That's one thing that was never tried. Using flash fire to flash the Chinese firmware.
Click to expand...
Click to collapse
Yeah this is pretty good

Root-Maniac said:
This is getting good. That's one thing that was never tried. Using flash fire to flash the Chinese firmware.
Click to expand...
Click to collapse
Check this out first! https://forum.xda-developers.com/s7...heoretical-variant-bootloader-unlock-t3627286