CWM Feature Request - MD5 Sums Builtin - Samsung Epic 4G Touch

It would be super cool if CWM had MD5 sum checking built in.
I like to download roms to my phone directly and then reboot to flash them and I can't be the only one.
Having this automatically check for the same filename as the zip but with an md5 on it would be pretty sweet.
Though MD5 is pretty weak these days, SHA1 would be better but I'll take what I can get.
Not sure if CWM is actively developed or if the Rogue or ACS guys could add this but it shouldn't be that big a deal and actually useful compared to just making CWM prettier.
Seems like most people have stopped giving MD5 sums cause people are confused by it. If it was just part of CWM maybe people would start using it again?
Or possibly make a new zip?
e.g. mymod.cwm (actually a zip file)
mymod.md5
mymod.zip​
Nothing ruins your day like a bad rom download.

When you sign your zips, it creates a manifest and every single file has an individual sha1-digest. If you have a bad download it should fail the signature verification, unless you turn it off.

Aha
One last chance to showcase my ignorance here.
Is there a default warning if the zip is not signed?
If not it might be good to annoy lazy modders with users asking "Why does CDW complain about this missing signature thing?"

mightypenguin said:
One last chance to showcase my ignorance here.
Is there a default warning if the zip is not signed?
If not it might be good to annoy lazy modders with users asking "Why does CDW complain about this missing signature thing?"
Click to expand...
Click to collapse
So I just tried 2 installs, one where I modified the contents of the zip, leaving the manifest intact.
CWM complained and gave an error.
The 2nd, I eliminated the cert and the manifest. This one it installed no problem.
So if you don't sign your zips, CWM will install without complaining. I'm sure stock will not let you install unsigned zips at all.

I want to turn md5 OFF in CWM. I hate when phone just sits checking md5 in a nandroid!
Sent from my SPH-D710 using Tapatalk

sfhub said:
So I just tried 2 installs, one where I modified the contents of the zip, leaving the manifest intact.
CWM complained and gave an error.
The 2nd, I eliminated the cert and the manifest. This one it installed no problem.
So if you don't sign your zips, CWM will install without complaining. I'm sure stock will not let you install unsigned zips at all.
Click to expand...
Click to collapse
I've modified the zip and been able to flash without issue more than once.
Sent from my SPH-D710 using Tapatalk

AestenD said:
I've modified the zip and been able to flash without issue more than once.
Click to expand...
Click to collapse
It isn't really an "issue" per se with CWM. It is whether you want the option to complain about file changes turned on or not. Since you have the ability to turn off verification in CWM, it is more for safety than for protection. In the stock recovery, it is for both.
With CWM (the vanilla one chris41g packs in) if your zip is not signed, it doesn't care, make any changes you want, it'll still install.
If it is signed and you turn off signature verification, it doesn't care either, again make any changes you want, it'll still install.
If it is signed and you have signature verification enabled, it will complain, which is the expected behavior, otherwise you would have a bug in CWM.
This is with the stock CWM. You may be using some version that has different default options.
If you use stock recovery, then it needs to be signed using Samsung's keys and there is no option to installed unsigned zips.

sfhub said:
It isn't really an "issue" per se with CWM. It is whether you want the option to complain about file changes turned on or not. Since you have the ability to turn off verification in CWM, it is more for safety than for protection. In the stock recovery, it is for both.
With CWM (the vanilla one chris41g packs in) if your zip is not signed, it doesn't care.
If it is signed and you turn off signature verification, it doesn't care either.
This is with the stock CWM. You may be using some version that has different default options.
If you use stock recovery, then it needs to be signed using Samsung's keys.
Click to expand...
Click to collapse
Correct as always. Sfhub's word is to be trusted. Another Rockstar thank God on our forum.

Signed Corruption Possible?
It appears possible that a signed zip file could be corrupted during download and not caught when unzipped by CWM. How?
http://docs.oracle.com/javase/1.3/docs/tooldocs/win32/jarsigner.html
I'm assuming that the CWM is looking for "a signature file, with a .SF extension".
So if the corruption:
1. removed that .SF file from the zip
2. changed it's extension
3. Corrupted the data inside it (unlikely)
Then it's possible that CWM would go on blissfully happy and not complain because it didn't realize the zip was supposed to be signed? Or are there other redundancies that make this extremely unlikely?
**If** this is true than it would be one argument for "Always warn if not signed"

IMO you are describing such "targeted" corruption that you are virtually describing someone purposely making changes to avoid detection rather than random corruption. If someone really wanted to modify something you are downloading, then could just resign it and you wouldn't be any wiser even with the proposed warn on unsigned.
If you really want to trust what you are downloading, use the stock recovery, which will warn on every signature failure and only accept official Samsung signed software.
If you want the change in CWM, go to the CWM development team and propose it to them.

Everyone keeps talking about an advanced option in CWM recovery which permits disabling signature recovery. This is not present in the current version aavailable on the Android Market which has led to thousands of people not being able to load recent versions of ICS. I have tried rom's from different sites and they all produce the same "signature failed" message.
Could someone please post a link to the version of CWM recovery that actually works - we wold all be very grateful!
Thanks, Mike.

Related

Rom Manager Issue

I have tried updating my rom through Rom manager and I keep getting an error. it says unknown volume path and cant mount backup path. Any assistance would be appreciated.
Posted in the wrong section this should be in Q&A. But I would advice not to use ROM manager and use another form of recovery like CWM.
Sorry about wrong section. What is CWM and where can I get it?
Pm me primedef lest they lock this thread
Sent from my Galaxy Nexus using xda app-developers app
primedef said:
Sorry about wrong section. What is CWM and where can I get it?
Click to expand...
Click to collapse
CWM is clockwork mod recovery.
Custom recovery used to flash ROMs.
Although I don't remember if there's different versions of it for each Nexus.
If this doesn't get automatically moved to Q&A, repost it there.
Agreed, and worst comes to worst, ROM Manager installs a version (possibly outdated) of cwm automatically, so you can always use that. Personally, I'd suggest flashing cwm 6.0.x and using that to manually flash everything from now on. Doing so (and understanding what you're doing) will vastly improve your Android experience, and knowledge, and may help you get out of a tight spot in the future, if something goes wrong with your phone. A little knowledge can go a looong way in the flash game.
Galaxy Nexus - Slim Bean 1.0
GooManager and TWRP is a superior replacement for koush's stuff. Just go with that and you'll never look back. They integrate well together and it actually works just like cwm and rom manager used to when it was 1st released a couple of years ago. Can't recommend it enough. I haven't used a properly working cwm/RM since the moto OG. But if you insist on cwm then I would find a version that has been been modified to function properly. Seems someone released a working touch version but I don't know if it integrates with the RM app.
Sent from my Galaxy Nexus using xda premium
primedef said:
I have tried updating my rom through Rom manager and I keep getting an error. it says unknown volume path and cant mount backup path. Any assistance would be appreciated.
Click to expand...
Click to collapse
Most likely failed if you don't have custom recovery installed as stated above
. Can't install custom ROM without custom recovery.
Travisdroidx2 said:
Posted in the wrong section this should be in Q&A. But I would advice not to use ROM manager and use another form of recovery like CWM.
Click to expand...
Click to collapse
Good call
primedef said:
Sorry about wrong section. What is CWM and where can I get it?
Click to expand...
Click to collapse
You can get it via ROM manager, choose install custom recovery. or you can flash it via fastboot.
jjhiza said:
Agreed, and worst comes to worst, ROM Manager installs a version (possibly outdated) of cwm automatically, so you can always use that. Personally, I'd suggest flashing cwm 6.0.x and using that to manually flash everything from now on. Doing so (and understanding what you're doing) will vastly improve your Android experience, and knowledge, and may help you get out of a tight spot in the future, if something goes wrong with your phone. A little knowledge can go a looong way in the flash game.
Galaxy Nexus - Slim Bean 1.0
Click to expand...
Click to collapse
I don't think it installs "automatically". It WILL choose the correct one for your device but you need to actually choose to install it. (sorry not trying to say you are wrong, just wanted to clarify for the guy
But like someone else said, you might want to download app called goo manager beta. Then open app, press menu, choose install openrecovery script. Say yes. Let it finish installing. Then reboot into recovery via the option in the app. That will give you TWRP2.2.0 as your custom recovery, i used to use cwmr for the longest time, one day i tried TWRP(and goo manager app) and i haven't looked back.
Just one MAJOR tip for you:
After installing a custom recovery, the VERY FIRST THING YOU SHOULD DO IS MAKE A NANDROID BACKUP.(choose option "backup" and let it do its thing) you won't regret making a backup. 75% of time before i flash/install something new or different i make a backup, this way if i don't like what i changed i can just restore and be back where i was. Plus, if anything ever goes wrong it's nice to have a couple nandroid backup files to choose from to recover your device to working condition.
ashclepdia said:
Most likely failed if you don't have custom recovery installed as stated above
. Can't install custom ROM without custom recovery.
Good call
You can get it via ROM manager, choose install custom recovery. or you can flash it via fastboot.
I don't think it installs "automatically". It WILL choose the correct one for your device but you need to actually choose to install it. (sorry not trying to say you are wrong, just wanted to clarify for the guy
But like someone else said, you might want to download app called goo manager beta. Then open app, press menu, choose install openrecovery script. Say yes. Let it finish installing. Then reboot into recovery via the option in the app. That will give you TWRP2.2.0 as your custom recovery, i used to use cwmr for the longest time, one day i tried TWRP(and goo manager app) and i haven't looked back.
Just one MAJOR tip for you:
After installing a custom recovery, the VERY FIRST THING YOU SHOULD DO IS MAKE A NANDROID BACKUP.(choose option "backup" and let it do its thing) you won't regret making a backup. 75% of time before i flash/install something new or different i make a backup, this way if i don't like what i changed i can just restore and be back where i was. Plus, if anything ever goes wrong it's nice to have a couple nandroid backup files to choose from to recover your device to working condition.
Click to expand...
Click to collapse
You're right...my explanation was a bit too simplified, I think. I meant that the process of installing cwm is automated when you choose to install it, versus having to manually flash it to the device. And you're 100% correct about immediately making a Nandroid after installing a recovery...having a stock, rooted system is always a prudent fallback. As for Too Manager; I actually just downloaded it the other day, because it gives me quick access to new Gapps whenever I need them, and it's a quicker solution than going to the site. I haven't used it for anything else at all, so I'm unaware of it's full capabilities... I would assume that anything that's hosted on Goo, is relatively easy to find via the app. Unfortunately, most of the JB ROMs I've flashed aren't hosted there. Yet and still, it's a very useful tool, even if you only use it to stay current with Gapp packages.
Galaxy Nexus - Slim Bean 1.0
jjhiza said:
You're right...my explanation was a bit too simplified, I think. I meant that the process of installing cwm is automated when you choose to install it, versus having to manually flash it to the device. And you're 100% correct about immediately making a Nandroid after installing a recovery...having a stock, rooted system is always a prudent fallback. As for Too Manager; I actually just downloaded it the other day, because it gives me quick access to new Gapps whenever I need them, and it's a quicker solution than going to the site. I haven't used it for anything else at all, so I'm unaware of it's full capabilities... I would assume that anything that's hosted on Goo, is relatively easy to find via the app. Unfortunately, most of the JB ROMs I've flashed aren't hosted there. Yet and still, it's a very useful tool, even if you only use it to stay current with Gapp packages.
Galaxy Nexus - Slim Bean 1.0
Click to expand...
Click to collapse
I fell in love with goo manager and TWRP as soon as i installed them, they are great. Was even able to find the beta versions of twrp2.2 on there. Tons of things are available on goo.you can usually find IMOSEYON lean kernel RC's on there as well. I even donated to not have to wait the 10seconds before download and help them get done new server equipment, hopefully they can get to their goal and we can get very speedy downloads.
(again sorry, i wasn't trying to step on ya toes or make ya look bad, i hate that i always want to clarify things further lol, makes me feel like a douche sometimes.)
Since this has not been closed or moved yet I just wanted to add that goo.im is great! I love that app for my getting downloads and gapps. I do have to say I tried twrp and it was faster but I never got the hang of it. Seemed you could only flash what was in your download folder? Or else I would have to move the file over to download folder to get it to flash. I guess on the dinc2 I got spoiled with touch ext4 recovery. It was a great recovery. I did notice the speed of twrp but decided to go back to my touch cwm since I already was familiar with the controls. Was probably user error on twrp since I see so many people love it on his forum.
ashclepdia said:
I fell in love with goo manager and TWRP as soon as i installed them, they are great. Was even able to find the beta versions of twrp2.2 on there. Tons of things are available on goo.you can usually find IMOSEYON lean kernel RC's on there as well. I even donated to not have to wait the 10seconds before download and help them get done new server equipment, hopefully they can get to their goal and we can get very speedy downloads.
(again sorry, i wasn't trying to step on ya toes or make ya look bad, i hate that i always want to clarify things further lol, makes me feel like a douche sometimes.)
Click to expand...
Click to collapse
No harm, no foul man. We all need correcting once in a while. I rarely get mad at anything in forums, other than people flaming devs or not following rules the devs have outlined (like asking a CM team member for an ETA, lol). You've actually me a reason to delve into the Goo app a bit deeper, to see what's there.
Galaxy Nexus - Slim Bean 1.0

Unable to upgrade Galaxy 3

When the update file downloads then it verifies but when it goes to install, it errors out and stops [see attached image]. There is also mention of Gmail.apk but when I go and look for it, it's not there. I have deleted the file and downloaded several time but wind up with the same result. I have put a copy in the ext sd card and tried from there but it will not install. Any ideas on how to do the upgrade?
Thanks, Dave
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
topherk said:
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
JOB Dave said:
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
Thanks for reading all of it. Most people would just look at the first page and the last page and say "Oh, it's not there!" That being said, I hope you have a better understanding of what's going on when you get an OTA notification.
Now that's been said, I had written a post on another thread that covers the steps A-Z. I've linked it and quoted it below.
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, it should have gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
JOB Dave said:
The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
I don't think there's a way to be "just a little rooted"
:silly:
Follow topherk's directions to a tee, and you'll be fine.
As a noob, I was scared to death knowing that I was rooted and I was going to get an OTA!
xda-developers has everything you need. The files, the guides, the support from senior members.
Relax and have fun...
---------- Post added at 06:11 PM ---------- Previous post was at 05:54 PM ----------
BTW, I flashed freeza's md4 odexd rom (cause a stock sg is odex), the md4 firmware, and the optimized kernel. Flashed (installed) them in that order. Just download them from the site onto your phone, and boot into recovery to flash each. Probably too paranoid, but i rebooted after each flash *just* to be sure). Cleared dalvik cache after installing the rom. Ummm, and ran checksum on my files before I installed them (I use md5 checker app).
Thanks, that got me started. now I have to figure out which rom and kernal I want to install.
ROMs come with kernels already, so if you're unsure ATM, just flash a ROM and then later you can check out kernel switching. Just make sure that the kernel you are flashing is for your ROM version (4.1.2, 4.2.2, etc) and for your type (AOSP, Touchwiz).
Since you are just starting out, I would suggest TPR (The Peoples ROM) or MOAR (Mother of All ROMs). Both in Android Dev section (as opposed to Original Android Dev).
TPR also has AROMA installer, so it lets you pick what apps, kernel, and other goodies you want to flash and basically on-the-spot customization.
Downloaded the file MD4_update_FULL_Odex.zip and followed the instructions above and got zip signature failure, see photo. I am wondering if it worth doing the upgrade.
~Dave
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
topherk said:
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
JOB Dave said:
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
Click to expand...
Click to collapse
Baseband has to do with what modem/radio you are on. This is independent of your ROM, so the two can be different version numbers.
The modem impacts your mobile data coverage and speeds. What you wanna do (if you wanna find the best modem for your area) is to switch modems and run each one for a week. Then switch. After you've gone through a couple modems, single out the ones that qork best and test those out till hou find the best and/or fastest one for your area and the places you frequent.

NOOB trying to flash ROM on AT&T GS3 get Error "no MD5 file"

I rooted my GS3, verified root. I am trying to flash ROM, every time I try through Goo manager and TWRP it fails I get error message "no MD5 file" doesn't matter if I download ROM from XDA (when I can find them) or download through Goo Manager. tried to even flash with ODIN, which only let's me restore to Stock ROM/Backup. which had MD5 file. when I try to browse for MD5 files I don't see them in the zipped or unzipped files on my PC, and not in ODIN either. I have verified developer options is on, and I tried with USB bugging on and off. and uncheck verify MD5 as well. I down loaded to pc and have tried to download directly to the device. not running antivirus on device and shut antivirus off on pc. will not copy files from pc to device. Device also stops or seems to loos connection on pc via USB Cable. What am I missing here? this is not rocket science!!
Have you verified MD5 of the ROM? Also, another suggestion, perhaps try to change recoveries from TWRP to CWM. However, you mentioned that you can't even download the Rom to your device? I assume you're able to browse the device's content since you used Odin to stock? Lastly, try to Odin back to stock, root it, flash recovery and give it a go.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Badfish63 said:
I rooted my GS3, verified root. I am trying to flash ROM, every time I try through Goo manager and TWRP it fails I get error message "no MD5 file" doesn't matter if I download ROM from XDA (when I can find them) or download through Goo Manager. tried to even flash with ODIN, which only let's me restore to Stock ROM/Backup. which had MD5 file. when I try to browse for MD5 files I don't see them in the zipped or unzipped files on my PC, and not in ODIN either. I have verified developer options is on, and I tried with USB bugging on and off. and uncheck verify MD5 as well. I down loaded to pc and have tried to download directly to the device. not running antivirus on device and shut antivirus off on pc. will not copy files from pc to device. Device also stops or seems to loos connection on pc via USB Cable. What am I missing here? this is not rocket science!!
Click to expand...
Click to collapse
Don't flash custom ROMs from goo manager or odin... Do your standard wipes, and flash from recovery. Maybe your recovery needs updated? What version are u on? You can verify md5 sums with a file explorer such as astro or there's even an md5 checker here in the forums. As far as transferring files from PC to phone, is your USB cable good?
---------- Post added at 02:06 PM ---------- Previous post was at 02:01 PM ----------
mgostom said:
Have you verified MD5 of the ROM? Also, another suggestion, perhaps try to change recoveries from TWRP to CWM. However, you mentioned that you can't even download the Rom to your device? I assume you're able to browse the device's content since you used Odin to stock? Lastly, try to Odin back to stock, root it, flash recovery and give it a go.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've never used twrp, been using cwm for years and am kind of partial to it.
At op, latest version for this is 6.0.3.6... U can use ROM manager to flash this if u wish. Not sure if this will help??
No MD5 file found
mgostom said:
Have you verified MD5 of the ROM? Also, another suggestion, perhaps try to change recoveries from TWRP to CWM. However, you mentioned that you can't even download the Rom to your device? I assume you're able to browse the device's content since you used Odin to stock? Lastly, try to Odin back to stock, root it, flash recovery and give it a go.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I have tried CWM as well. for some reason none of the ROMS no matter where I download from seem to pull the MD5 file, liquid smooth, paranoid 3.69, carbon, none, I try to browse the device for them and nothing. But I can't seem to even do my first flash! I noticed in any of the ROMS I download for some reason it does not pull the MD5 file. I have downloaded from here XDA and other sites, and android forums too! I don't get it. This should be fairly easy according to all the research I have done even before my first attempt. I can root no problem, I used Odin and Samsung GS3 Tool kit.
No MD5 file found
DMF1977 said:
Don't flash custom ROMs from goo manager or odin... Do your standard wipes, and flash from recovery. Maybe your recovery needs updated? What version are u on? You can verify md5 sums with a file explorer such as astro or there's even an md5 checker here in the forums. As far as transferring files from PC to phone, is your USB cable good?
---------- Post added at 02:06 PM ---------- Previous post was at 02:01 PM ----------
Yeah, I've never used twrp, been using cwm for years and am kind of partial to it.
At op, latest version for this is 6.0.3.6... U can use ROM manager to flash this if u wish. Not sure if this will help??
Click to expand...
Click to collapse
I followed your suggestion using CWM 6.0.3.6. and yes it does seem to work better! I am almost there! I am able to flash custom ROMS. but the seem to get hung up upon reboot. USB cables brand new. I even tried different USB Port and Different PC. Still being a bugger! I wish I could find other ROMS more easily on here! or even a little easier on some of the developer sites. I found a work around and pull my ext. SD card and download ROM to that and not on the PC. I found some really Nice one I would like to try but like I said seems to hang on reboot like hour and I get tired of waiting. Thanks for your help! any other suggestions would be GREATLY Appreciated!
Badfish63 said:
I followed your suggestion using CWM 6.0.3.6. and yes it does seem to work better! I am almost there! I am able to flash custom ROMS. but the seem to get hung up upon reboot. USB cables brand new. I even tried different USB Port and Different PC. Still being a bugger! I wish I could find other ROMS more easily on here! or even a little easier on some of the developer sites. I found a work around and pull my ext. SD card and download ROM to that and not on the PC. I found some really Nice one I would like to try but like I said seems to hang on reboot like hour and I get tired of waiting. Thanks for your help! any other suggestions would be GREATLY Appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=1705
Simple search is all it takes. Touchwiz based roms are in android development, while aosp ROMs are in the original android development threads. Don't forget to hit the "thanks" button to anyone who has helped u out! Good luck!!!
Badfish63 said:
I followed your suggestion using CWM 6.0.3.6. and yes it does seem to work better! I am almost there! I am able to flash custom ROMS. but the seem to get hung up upon reboot. USB cables brand new. I even tried different USB Port and Different PC. Still being a bugger! I wish I could find other ROMS more easily on here! or even a little easier on some of the developer sites. I found a work around and pull my ext. SD card and download ROM to that and not on the PC. I found some really Nice one I would like to try but like I said seems to hang on reboot like hour and I get tired of waiting. Thanks for your help! any other suggestions would be GREATLY Appreciated!
Click to expand...
Click to collapse
The Roms should not be that hard to find and as stated you NEED to verify the MD5 before installing. Thats the long weird numbers/letters in the download sceen. A bad flash is a headache. To double check, you are doing (in CWM or TWRP) wipe data, then wipe cache, then wipe dalvick right? If you dont do those things its a dirty flash and will cause issues. Then in CWM in the install from sdcard screen, try to toggle the signature verification option. Also, sometime when you go from CM to TW and back, it can be a problem. Try wiping/reset from the settings-backup and restore-factory reset option for a super clean wipe. Use caution though as this will delete internal sdcard so back it up and put the rom of choice on external SD. This is a hassle but needs to be done on occasion. If you use titanium backup, copy to folder to external sd and change restore location in preferences.
Something I just found.
I have flashed custom roms to my padfone2 and everything was fine but when I tried to flash zip file with stock rom it showed no md5 file error.
I had a look into the downloaded stock rom zip file and I found out that the actual zip file with rom in it was in a folder inside downloaded zip. As soon as I extracted the zip from downloaded zip and flashed it everything went without a problem. Maybe I'm just stupid not to have look at that in the first place but I hope it helped others. Best of luck everyone.
Good Afternoon sorry for bumping an old thread.
I joined today because I am having the same problem that the original poster had written about.
I have an ATT samsung galaxy s3, I had root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. It also says there was no MD5 information found. I have used the md5 file checker program and the MD5 matches up to
http://forum.xda-developers.com/showthread.php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline)
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
No md5 file found
HEY...AM NEW TO THE FLASHING ROMS, AND ROOTING, ANDROID DEVICES..I HAVE A GALAXY NOTE 2 VERIZON SCH-I605...I FALLOW ALL THE STEPS TO ROOT AND UNLOCK BOOTLOADERS AND ALL THAT TRYING TO FLASH THE NEW 4.4 KITKAT BUT NO MATTER WHERE I GET THE DOWNLOAD FROM..AFTER I TRY TO FLASH IT ON THE DEVICE IT GIVES ME A FAILED MESSAGE...
SKIPPING MD5.......
NO MD5 FILE FOUND..........BLAH BLAH BLAH
I MAKE SURE I CHECK THE MD5 TO MAKE SURE IT MATCHES AND ALL BUT FOR SOME REASON I JUST CANT FLASH ANYTHING TO MY PHONE....
CAN SOME1 HELP ME OUT....
Did you get a answer, I have same problem?
GN2RD809 said:
HEY...AM NEW TO THE FLASHING ROMS, AND ROOTING, ANDROID DEVICES..I HAVE A GALAXY NOTE 2 VERIZON SCH-I605...I FALLOW ALL THE STEPS TO ROOT AND UNLOCK BOOTLOADERS AND ALL THAT TRYING TO FLASH THE NEW 4.4 KITKAT BUT NO MATTER WHERE I GET THE DOWNLOAD FROM..AFTER I TRY TO FLASH IT ON THE DEVICE IT GIVES ME A FAILED MESSAGE...
SKIPPING MD5.......
NO MD5 FILE FOUND..........BLAH BLAH BLAH
I MAKE SURE I CHECK THE MD5 TO MAKE SURE IT MATCHES AND ALL BUT FOR SOME REASON I JUST CANT FLASH ANYTHING TO MY PHONE....
CAN SOME1 HELP ME OUT....
Click to expand...
Click to collapse
I can't believe this, because I have downloaded and burned roms before. Now I cannot download a rom and get an md5 file nomatter what I do.

[Q] Rooted but need HELP with ROM & Recovery Plz!

Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Making progress but still confused...?
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
BrianN_Cols_OH said:
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Click to expand...
Click to collapse
Success - Finally got CWM - Ready to play with ROMs
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
BrianN_Cols_OH said:
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
Click to expand...
Click to collapse
BrianN_Cols_OH said:
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
Click to expand...
Click to collapse
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
More updates...
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
nikon120 said:
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
Click to expand...
Click to collapse
New issues - need help with CM 10.1...
OK, I've made progress and learned a lot. Essentially restored the bricked phone by going back to stock. Then, I started my process again.
- Used ODIN to flash rooted kernel with CM 5.0.2.7
- Flashed Cyanogenmod 10.1.3
- Flashed correct Gapps (dated 8/12 I think)
Software great, but modem not working. So, then I found the forum for the NS4G modem patches. I've tried several and I did get one to work. But, the latest version of CM 10.1 has SU built-in. When I do the modem repair, it breaks my SU root.
I've tried the nitest kernal (by the way, I like the TWRP recovery better than CM - it). I've tried several of the modem patches.
Do I need to go back to a certain stable version of CM 10? What order to I need to apply things?
Here's what I have on the phone at the moment. It has SU/root but no modem.
- Android 4.2.2
- 3.0.79-JB42-nitest-nr kernel
- CM 10.1-20130526-NIGHTLY-epicmtd (although I've tried several other builds)
I was sooooooo close. Please help? How do I get my modem working AND keep my SU/root?
BrianN_Cols_OH said:
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
Click to expand...
Click to collapse
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Modem issues...
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
nikon120 said:
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Click to expand...
Click to collapse
More info...
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
BrianN_Cols_OH said:
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
Click to expand...
Click to collapse
Modem.bin
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
BrianN_Cols_OH said:
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
Click to expand...
Click to collapse
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Thanks!
Great, thanks so much. I will look for the modem files a little later.
nikon120 said:
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
BrianN_Cols_OH said:
Great, thanks so much. I will look for the modem files a little later.
Click to expand...
Click to collapse
Ok, all Epic modems and NS4G modems are reuploaded. I also included the swap files for each. Everything with (Flashable) means to be flashed within recovery. Those swap files are the blob changes I mentioned earlier. This way you can swap modems using recovery, rather than relying on Odin.
Everything in the Odin folder can be placed in the phone slot and flashed as-is. (No need to extract the .bin file from the archive.)
As for the built-in root manager in CM, I'd try reflashing the rom first, and then messing with the modem.

How I Installed An Edge ROM and Tricked My Phone Out

I have been asked by several people, on the forums and via PM. I thought that I would offer a step-by-step guide.
Will This Trip Knox? Yes, it will. Installing a custom recovery such as TWRP will definitely trip Knox. From what I have read installing a ROM, even through FlashFire, will trip Knox, as will flashing a kernel.
You Don't Seem To Care About Knox That is correct. To this point the only downside is that I won't be able to use Samsung Pay and I don't plan on that anyway. BUT.....if you do care and Knox matters, stop reading now and stick with stock.
I will also recommend that you grab ODIN and a stock TAR file for your phone. You can always find the latest firmware at SamMobile, but will need to create an account and free downloads are speed capped. It will be SLOOOOW. But you will get a zip with the file that you need inside. Good to have in case of accident. Here is where I got mine: http://www.sammobile.com/firmwares/download/47474/G920PVPU1AOE2_G920PSPT1AOE2_SPR/
That said.....assume that you have a rooted S6. Install TWRP Manager from the Play store, ignore anything it says about an SD card and click on "Install TWRP." The version that you are looking for is "zerofltespr.img." You can also download that from here https://twrp.me/devices/samsunggalaxys6sprint.html and use Flashfire to install. Reboot into recovery (see http://www.androidexplained.com/galaxy-s6-recovery-mode/ for an explanation) and make sure that TWRP is installed. If TWRP doesn't come up, make sure that you used the correct file and try again.) Now you are ready to begin.
1) The ROM that I used is the SAC23 ROM from here: http://forum.xda-developers.com/spr...ment/sac23ram9200srintdeoxedmoddedv1-t3107342 Download that and copy to your phone. You should also grab the "Recent apps fix long press on home" zip file from the bottom of that post.
2) You will also NEED (!!!!!) a kernel that is designed for the S6, otherwise you will bork your phone. I use (and recommend) the Ktoonsez kernel located here: http://forum.xda-developers.com/spr...elopment/kernel-kt-sgs6-ocv-ktweaker-t3093009 Grab that and copy to your phone.
3) For fingerprint recognition and private mode, you will need the Aroma installer from here: http://forum.xda-developers.com/showpost.php?p=60112854&postcount=2 If you use the Aroma installer (and I don't so I have no experience) be sure that those are the only two things that you install.
UPDATE 7/1/2015 Just had a report that fingerprint is working with this kernel: http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-kernel-t3146127
Anyone interested should read all posts for that kernel before flashing.
Once you have those files on your phone, you are ready to begin.
Return to recovery mode. Before you do anything else....Click on "Backup." Accept the default settings and let it do its thing. I always name my backups....calling this Stock is probably a good idea. Once that is done, if you break things, you can return to this.
Okay, now go to Wipe. The old-timers will disagree, but most of the time the default "Factory Reset" is all that you need. If you are paranoid (and who isn't?) after this you can go to Advanced and choose Dalvik Cache, Cache, Data and System. But I rarely do this anymore. Complete guide for using TWRP is here: http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Now go back to the main screen and select Install. You can select multiple zips. Flash the ROM, the kernel and that Recent Apps zip file. Be sure to set the kernel to flash after the ROM. Or you can flash them one at a time.
Once done, reboot phone and if all went well, you will see a new boot animation. First boot will take a while, let her go.
You should have a clean build so remember that you will need to reset Developers options, security (for allow Unknown sources) and other stuff.
With the Ktoonsez kernel, you will have the KTweaker app, very useful. If it doesn't install for you (and it didn't for me) the APK is located inside the zip file that you downloaded at S6\KT-SGS6-LP5.0-TW-G920P-05.28.2015.zip\system\app\ Extract that and install. I use downloaded Profiles a lot.
If all is well, but the fingerprint and private mode settings are things that you use, go back into Recovery and select ONLY those two items. I'll state again, I don't use them, have never flashed the Aroma installer and can't offer any help. I have seen that they work for some people, not for others..../me shrugs. I can't help with that.
I also use the Wicked One Theme from @dazedandconfused who is a master. See http://forum.xda-developers.com/spr...ps/theme-wicked-one-theme-s6-s6-edge-t3129822 for the theme and instructions. Be sure to follow the instructions about having the Urban theme from the Theme Store installed first. But this theme makes me very happy.
That is everything that I know....which goes to show how little I know!
EDIT: Missed a step....DOH!.... if you are using TWRP you should flash the zip file found here to address the Deep Sleep issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Happy ROM-ing.
Everything works except I cannot text at all
ScottBroker said:
Everything works except I cannot text at all
Click to expand...
Click to collapse
Are you using the stock messaging app or something else? Did you use the Aroma installer and, if so, was messaging working before?
koop1955 said:
Are you using the stock messaging app or something else? Did you use the Aroma installer and, if so, was messaging working before?
Click to expand...
Click to collapse
I use stock, and I tiried another as well. I did not use the aroma installer
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
ScottBroker said:
I use stock, and I tiried another as well. I did not use the aroma installer
Click to expand...
Click to collapse
I updated the PRL, rebooted and now it works, Thanks
ScottBroker said:
I use stock, and I tiried another as well. I did not use the aroma installer
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
I updated the PRL, rebooted and now it works, Thanks
Click to expand...
Click to collapse
Ah, good to know and thanks for posting the solution here.
Cheers.
koop1955 said:
Ah, good to know and thanks for posting the solution here.
Cheers.
Click to expand...
Click to collapse
Thanks for posting an alternative to the non existant development for the S6.
nice work on this Koop!!!!! I'm running Sacs rom and KToonz kernel smooth and trouble free, privacy mode and finger print scanner work 100%
sent from my S6 using tapatalk
Here's a question. Hope do you use the stock battery icon on Sac's ROM and not one of those gross 3minit or whatever ones? They're all hideous.
twiztid907 said:
Here's a question. Hope do you use the stock battery icon on Sac's ROM and not one of those gross 3minit or whatever ones? They're all hideous.
Click to expand...
Click to collapse
I have to say that it is really popular mod, but not to my taste either. Here is what I run for battery:
GSam Battery Monitor (also lets you customize the battery icon, but I don't)
Greenify and Wakelock Detector
With Ktoonsez, I have the Ktweaker installed. Click on the 3 dots upper left. Scroll down to KTweaker Shop Profiles and then pick from Conservative, Balanced or Performance (or grab some of each.) I am using the Conservative Profile "Dead By April." I love that name!
Average Per Complete Charge (now this is with light usage) 2 days 0 hours, with screen on 1 hour 41 minutes.
Not expecting to get the same battery life when I am traveling or with heavy usage, but that is still pretty remarkable.
koop1955 said:
With Ktoonsez, I have the Ktweaker installed. Click on the 3 dots upper left. Scroll down to KTweaker Shop Profiles and then pick from Conservative, Balanced or Performance (or grab some of each.) I am using the Conservative Profile "Dead By April." I love that name.
Click to expand...
Click to collapse
while I'll admit I haven't explored the KToonz settings much, I was wondering how you accessed profiles, this is good info, I'm trying out dead by April as I type this out lol
sent from my S6 using tapatalk
Missed a step
I edited the original post, but let me add this.
If you are running TWRP, you should flash the zip file found here to address the "No Deep Sleep" issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Hello, thank you for this great write-up! I PM'ed you the other day, and you helped me get my phone flashed and all.
However, I am still having issues with the Fingerprint scanner. If any other users do use the Fingerprint scanner, could you explain the steps in which you flashed each file? After using the Aroma installer to fix Fingerprint, I keep getting "Unfortunately, Fingerprint has stopped working." I just can't seem to get it working even with the Aroma installer. Maybe I am flashing files in the wrong order?
Thanks for any advice!
Android Attack said:
Hello, thank you for this great write-up! I PM'ed you the other day, and you helped me get my phone flashed and all.
However, I am still having issues with the Fingerprint scanner. If any other users do use the Fingerprint scanner, could you explain the steps in which you flashed each file? After using the Aroma installer to fix Fingerprint, I keep getting "Unfortunately, Fingerprint has stopped working." I just can't seem to get it working even with the Aroma installer. Maybe I am flashing files in the wrong order?
Thanks for any advice!
Click to expand...
Click to collapse
did you do a factory reset or dirty flash?
sent from my S6 using tapatalk
Another ROM Option
This is also an option for anyone having issues: http://forum.xda-developers.com/spr...ebloated-rom-samsuing-galaxy-s6-edge-t3126661
@Electronical Updates reminds all S6 users to flash the Ktoonsez kernel.
I hope to try this out this weekend.
scott_0 said:
did you do a factory reset or dirty flash?
sent from my S6 using tapatalk
Click to expand...
Click to collapse
I have tried both. I first wiped system, data, cache, dalvik and tried that. Then, I tried dirty flash from stock, flashing the ROM, kernel, and fingerprint fix, then wiped caches, and nothing. :/
Could you start the aroma installer, and on the first slide it tells you the version. Could you tell me which version you have? Maybe we have different versions, that could be the problem.. Thank you!
Edit: I also tried the other debloated ROM you mentioned, but it did not work with nor without the Aroma installer. If anybody wants to work with me to get this working, I can provide logs and information and test out whatever is needed. Thanks!
Thank you for this write up...glad to learn there is dev'ing going on for the edge.
Was hoping you could help; tried flashing twrp via odin, per instructions--root manager shows that I have TWRP 2.x.x. installed but when I try to boot into recovery I just get this crazy bright white screen. Was able to reboot normally the first time, but then tried booting into recovery with flashify and now stock on that bright white screen. I do have success with getting connections with odin, twrp flashing successfully. But now trying to flash back to stock firmware to get my recovery back and I have mixed results. PLEASE any help would be very much appreciated...might have borked my brand new s6 edge...but hope not.
Thanks in advance.
Unsuccessful
koop1955 said:
I have been asked by several people, on the forums and via PM. I thought that I would offer a step-by-step guide.
Will This Trip Knox? Yes, it will. Installing a custom recovery such as TWRP will definitely trip Knox. From what I have read installing a ROM, even through FlashFire, will trip Knox, as will flashing a kernel.
You Don't Seem To Care About Knox That is correct. To this point the only downside is that I won't be able to use Samsung Pay and I don't plan on that anyway. BUT.....if you do care and Knox matters, stop reading now and stick with stock.
I will also recommend that you grab ODIN and a stock TAR file for your phone. You can always find the latest firmware at SamMobile, but will need to create an account and free downloads are speed capped. It will be SLOOOOW. But you will get a zip with the file that you need inside. Good to have in case of accident. Here is where I got mine: http://www.sammobile.com/firmwares/download/47474/G920PVPU1AOE2_G920PSPT1AOE2_SPR/
That said.....assume that you have a rooted S6. Install TWRP Manager from the Play store, ignore anything it says about an SD card and click on "Install TWRP." The version that you are looking for is "zerofltespr.img." You can also download that from here https://twrp.me/devices/samsunggalaxys6sprint.html and use Flashfire to install. Reboot into recovery (see http://www.androidexplained.com/galaxy-s6-recovery-mode/ for an explanation) and make sure that TWRP is installed. If TWRP doesn't come up, make sure that you used the correct file and try again.) Now you are ready to begin.
1) The ROM that I used is the SAC23 ROM from here: http://forum.xda-developers.com/spr...ment/sac23ram9200srintdeoxedmoddedv1-t3107342 Download that and copy to your phone. You should also grab the "Recent apps fix long press on home" zip file from the bottom of that post.
2) You will also NEED (!!!!!) a kernel that is designed for the S6, otherwise you will bork your phone. I use (and recommend) the Ktoonsez kernel located here: http://forum.xda-developers.com/spr...elopment/kernel-kt-sgs6-ocv-ktweaker-t3093009 Grab that and copy to your phone.
3) For fingerprint recognition and private mode, you will need the Aroma installer from here: http://forum.xda-developers.com/showpost.php?p=60112854&postcount=2 If you use the Aroma installer (and I don't so I have no experience) be sure that those are the only two things that you install.
Once you have those files on your phone, you are ready to begin.
Return to recovery mode. Before you do anything else....Click on "Backup." Accept the default settings and let it do its thing. I always name my backups....calling this Stock is probably a good idea. Once that is done, if you break things, you can return to this.
Okay, now go to Wipe. The old-timers will disagree, but most of the time the default "Factory Reset" is all that you need. If you are paranoid (and who isn't?) after this you can go to Advanced and choose Dalvik Cache, Cache, Data and System. But I rarely do this anymore. Complete guide for using TWRP is here: http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Now go back to the main screen and select Install. You can select multiple zips. Flash the ROM, the kernel and that Recent Apps zip file. Be sure to set the kernel to flash after the ROM. Or you can flash them one at a time.
Once done, reboot phone and if all went well, you will see a new boot animation. First boot will take a while, let her go.
You should have a clean build so remember that you will need to reset Developers options, security (for allow Unknown sources) and other stuff.
With the Ktoonsez kernel, you will have the KTweaker app, very useful. If it doesn't install for you (and it didn't for me) the APK is located inside the zip file that you downloaded at S6\KT-SGS6-LP5.0-TW-G920P-05.28.2015.zip\system\app\ Extract that and install. I use downloaded Profiles a lot.
If all is well, but the fingerprint and private mode settings are things that you use, go back into Recovery and select ONLY those two items. I'll state again, I don't use them, have never flashed the Aroma installer and can't offer any help. I have seen that they work for some people, not for others..../me shrugs. I can't help with that.
I also use the Wicked One Theme from @dazedandconfused who is a master. See http://forum.xda-developers.com/spr...ps/theme-wicked-one-theme-s6-s6-edge-t3129822 for the theme and instructions. Be sure to follow the instructions about having the Urban theme from the Theme Store installed first. But this theme makes me very happy.
That is everything that I know....which goes to show how little I know!
EDIT: Missed a step....DOH!.... if you are using TWRP you should flash the zip file found here to address the Deep Sleep issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Happy ROM-ing.
Click to expand...
Click to collapse
I have the SM-G920P Sprint variant I downloaded all necessary zip files even the "deep sleep"zip, backed up my stock rom, wiped and installed well at least I tried. Loaded the SAC23 ROM zip, swiped to flash but the screen just went black and I found myself back at TWRP recovery screen. Tried repeatedly and to no avail. Wondering what I missed if anything.
king_ricardo said:
I have the SM-G920P Sprint variant I downloaded all necessary zip files even the "deep sleep"zip, backed up my stock rom, wiped and installed well at least I tried. Loaded the SAC23 ROM zip, swiped to flash but the screen just went black and I found myself back at TWRP recovery screen. Tried repeatedly and to no avail. Wondering what I missed if anything.
Click to expand...
Click to collapse
First off. please edit your post to not include the entire Original Post. It is both bad form and makes it difficult to find your question.
The first thing that I would do if I were you is to make sure that I had a good download of the SAC23 ROM. That is most likely where your problem is. I will check my download later and post the MD5, but you should re-download.
I checked MD5 using WinMD5 Free (shouldn't matter, there are several MD5 checkers)and the MD5 should be 3bb8163e902769f564a2f3adb3a1b7e6. Try checking that.
Android Attack said:
I have tried both. I first wiped system, data, cache, dalvik and tried that. Then, I tried dirty flash from stock, flashing the ROM, kernel, and fingerprint fix, then wiped caches, and nothing. :/
Could you start the aroma installer, and on the first slide it tells you the version. Could you tell me which version you have? Maybe we have different versions, that could be the problem.. Thank you!
Edit: I also tried the other debloated ROM you mentioned, but it did not work with nor without the Aroma installer. If anybody wants to work with me to get this working, I can provide logs and information and test out whatever is needed. Thanks!
Click to expand...
Click to collapse
Came here to say I had the same problem. The original ROM posted here was a Deodexed ROM, and the aroma tool posted was an odex version. There's an aroma installer for Deodexed Roms that works perfectly fine, just gotta use that. I'd post the link but I've been up all night and I have work in an hour lol. Have fun, the ROM is pretty nice!
@koop1955 @scott_0 have yuo guys flashed SacsROM v3?! It seems effin' amazing!! I'm verrryyy tempted to try it lol.

Categories

Resources