Database Users

stock rom failed to flash?

I'm using custom recovery to flash (TWRP) and I downloaded the stock MF9 sprint rom and it fails right when i hit install, i'm replacing liquid smooth 2.9
Updating partition details
Installing '/external_sd/SPR-L720VPUAMF9
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
error flashing zip '/external_sd/SPR-L720VPUAMF9
Updating partition details...
Any help would be appreciated, also when i flashed to liquid smooth it works fine and when i flash back do i need to flash my kernel again?

Turn off signature verification? I've only flashed the stock deodexed once and haven't had any problems.just a guess.

w7excursion said:
Turn off signature verification? I've only flashed the stock deodexed once and haven't had any problems.just a guess.
Click to expand...
Click to collapse
I kept searching found that you need to use Odin to flash back to stock and so far its working about half way there currently. Thank you though!

Oh sorry I didn't get that you were going back to factory stock. Hope it works.

bounddyy said:
I kept searching found that you need to use Odin to flash back to stock and so far its working about half way there currently. Thank you though!
Click to expand...
Click to collapse
Yup got it to work

[Q] AT7T GS4 Softbrick help

Hello, and thanks for reading this. I know it's long, but I wanted to be specific.
I got a brand new AT&T Galaxy S4 yesterday, and decided I wanted to run CM. I easily rooted using this
method, but ran into problems in multiple attempts to install CWM. I found out about the MF3 software version, which I have, so I installed safestrap.
In safestrap, I factory reset, installed CM 10.2-20131102.zip
snapshot, and then installed loki-doki.zip as mentioned in this thread (there were some mentions in the xda forums but I can't find the one I was looking at earlier.) The problem is I forgot to make
a new rom slot/partition thing, so I think I wrote over the stock rom.
Now, when I turn on the phone, an option for safestrap comes up. If I choose to not go through safestrap, the screen goes blank black, but the phone stays on until I
hold the power button and it vibrates, indicating a power down. Safestrap's recovery mode still works as expected.
What I've already tried:
1. Factory reset. Nothing changed.
2. Create rom slot for CM, install, and boot (Has since been uninstalled). Nothing changed.
3. manually put stock rom zip into phone. Computer did not recognize device.
4. Use adb to push same stock rom zip onto phone. ADB did not see device.
5. Change PIT via ODIN as per a thread I can no longer locate. Nothing changed.
6. Take a stock rom and flash it from ODIN (I used the PDA, then bootloader, option because I wasn't sure which to select.) Both failed.
Is this something y'all can help me with? What do I do? If you have any ideas, questions, comments, please ask. I know I need more information.
Thanks for the help.

FalseAim said:
Hello, and thanks for reading this. I know it's long, but I wanted to be specific.
I got a brand new AT&T Galaxy S4 yesterday, and decided I wanted to run CM. I easily rooted using this
method, but ran into problems in multiple attempts to install CWM. I found out about the MF3 software version, which I have, so I installed safestrap.
In safestrap, I factory reset, installed CM 10.2-20131102.zip
snapshot, and then installed loki-doki.zip as mentioned in this thread (there were some mentions in the xda forums but I can't find the one I was looking at earlier.) The problem is I forgot to make
a new rom slot/partition thing, so I think I wrote over the stock rom.
Now, when I turn on the phone, an option for safestrap comes up. If I choose to not go through safestrap, the screen goes blank black, but the phone stays on until I
hold the power button and it vibrates, indicating a power down. Safestrap's recovery mode still works as expected.
What I've already tried:
1. Factory reset. Nothing changed.
2. Create rom slot for CM, install, and boot (Has since been uninstalled). Nothing changed.
3. manually put stock rom zip into phone. Computer did not recognize device.
4. Use adb to push same stock rom zip onto phone. ADB did not see device.
5. Change PIT via ODIN as per a thread I can no longer locate. Nothing changed.
6. Take a stock rom and flash it from ODIN (I used the PDA, then bootloader, option because I wasn't sure which to select.) Both failed.
Is this something y'all can help me with? What do I do? If you have any ideas, questions, comments, please ask. I know I need more information.
Thanks for the help.
Click to expand...
Click to collapse
A few things...
CM will not work on SafeStrap as of right now, it's AOSP-based whereas SS currently only supports TouchWiz-based ROMs.
Is your stock ROM-slot intact, or did you flash over it as well? if so move on to the next bullet.
Your need to take these files and use ODIN to flash back to stock MF3 (I don't know what stock files your using) and start from scratch.
Alternatively, you can try to flash a TouchWiz-based ROM (look here) in a ROM-slot other then stock in SafeStrap and see if it works, just don't forget to flash the MF3 modules afterwards.

NighthawkXL said:
A few things...
CM will not work on SafeStrap as of right now, it's AOSP-based whereas SS currently only supports TouchWiz-based ROMs.
Is your stock ROM-slot intact, or did you flash over it as well? if so move on to the next bullet.
Your need to take these files and use ODIN to flash back to stock MF3 (I don't know what stock files your using) and start from scratch.
Alternatively, you can try to flash a TouchWiz-based ROM (look here) in a ROM-slot other then stock in SafeStrap and see if it works, just don't forget to flash the MF3 modules afterwards.
Click to expand...
Click to collapse
I really appreciate the help. I had no idea CM would not work with SafeStrap. Is it possible to get CWM through SafeStrap? If not, I'll just have to do some research to see if I want one of the TW-based ROMs, I've never looked into it before. Actually, just before you posted, I started the Odin flashing in this thread, which seems to be another thread pointing to the same file downloads written by the same guy as the thread you posted. The phone is back to perfect stock; no root, no SafeStrap, still MF3 software version. I'm going to reroot and reinstall SafeStrap, and not be so reckless this time. Thanks again for the help!

No CWM won't run on the locked MF3 bootloader. SafeStrap is "recovery" itself designed specifically for MF3 devices. Just use a TW Rom and br careful!
Sent from my SGH-I337 using Tapatalk

NighthawkXL said:
No CWM won't run on the locked MF3 bootloader. SafeStrap is "recovery" itself designed specifically for MF3 devices. Just use a TW Rom and br careful!
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Do you think you could help me install a ROM? I tried to get GoldenEye, but it didn't work. I made a new ROM slot and didn't change any of the default sizes. Then I activated that ROM slot, wiped the data, and intalled the GoldenEye zip file from the /sdcard folder. The I rebooted, and installed the MF3 modules on the same ROM slot. Then I rebooted again, but all I got was a black screen. I was able to get back into SafeStrap and the stock ROM still works, but what did I do wrong installing GoldenEye?
I deleted and then remade the ROM slot, and tried installing the two files again without rebooting in between, but it didn't change anything. But I did notice the following when trying to install the MF3 modules:
Installing 'sdcard/jflteatt-MF3-modules.zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
E:Unable to mount internal storage.
SafeStrap says "Successful," but this text doesn't sound like it. I couldn't find any in-depth tutorial on using SafeStrap, so I'm not sure what to try next.
Thanks for the help.

FalseAim said:
Do you think you could help me install a ROM? I tried to get GoldenEye, but it didn't work. I made a new ROM slot and didn't change any of the default sizes. Then I activated that ROM slot, wiped the data, and intalled the GoldenEye zip file from the /sdcard folder. The I rebooted, and installed the MF3 modules on the same ROM slot. Then I rebooted again, but all I got was a black screen. I was able to get back into SafeStrap and the stock ROM still works, but what did I do wrong installing GoldenEye?
I deleted and then remade the ROM slot, and tried installing the two files again without rebooting in between, but it didn't change anything. But I did notice the following when trying to install the MF3 modules:
Installing 'sdcard/jflteatt-MF3-modules.zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details...
E:Unable to mount internal storage.
SafeStrap says "Successful," but this text doesn't sound like it. I couldn't find any in-depth tutorial on using SafeStrap, so I'm not sure what to try next.
Thanks for the help.
Click to expand...
Click to collapse
All of this is covered in the "SafeStrap" thread.

[Q] Troubleshooting ROM Install Issue

Ok, so I had a quick question before I do something stupid. I've been trying to install ROMs on my g900v but some fail, and some are successful. I do the same steps with all ROMs; wipe, install, boot. Some of them just won't install.
My question is: Do I have to have matching firmware or kernal installed prior to flashing the ROM for it to install successfully? (i.e. NK2 firmware on my phone would prevent a ROM made with NI2 firmware from installing)

thesmashippy said:
Ok, so I had a quick question before I do something stupid. I've been trying to install ROMs on my g900v but some fail, and some are successful. I do the same steps with all ROMs; wipe, install, boot. Some of them just won't install.
My question is: Do I have to have matching firmware or kernal installed prior to flashing the ROM for it to install successfully? (i.e. NK2 firmware on my phone would prevent a ROM made with NI2 firmware from installing)
Click to expand...
Click to collapse
Yes, have to be the same firmware version. You are referring to flashing through safestrap, correct?

Yes, using safestrap. So I have to have the matching firmware flashed before I attempt to flash there ROM? Also do I need to flash the kernel? Or does flashing the firmware include the kernal?

thesmashippy said:
Yes, using safestrap. So I have to have the matching firmware flashed before I attempt to flash there ROM? Also do I need to flash the kernel? Or does flashing the firmware include the kernal?
Click to expand...
Click to collapse
All you have to do is flash the firmware only tar nothing else. When you install whatever rom you want just boot into download mode after you install the rom then flash the firmware in odin. Each rom thread has the installation instructions in the op which should also have a link to the firmware needed for that rom.

Savagerun said:
All you have to do is flash the firmware only tar nothing else. When you install whatever rom you want just boot into download mode after you install the rom then flash the firmware in odin. Each rom thread has the installation instructions in the op which should also have a link to the firmware needed for that rom.
Click to expand...
Click to collapse
Ok, my issue starts before that then. I go to install, we'll say Optimal ROM since that's the last one I had trouble with, and it says failed on the install. I wipe, and I have the proper firmware installed beforehand, but it still fails. I'm stumped.

thesmashippy said:
Ok, my issue starts before that then. I go to install, we'll say Optimal ROM since that's the last one I had trouble with, and it says failed on the install. I wipe, and I have the proper firmware installed beforehand, but it still fails. I'm stumped.
Click to expand...
Click to collapse
Don't know why it's failing for you as long as you're doing a full wipe then flashing the rom (make sure the md5 matches on your rom download) then flash the firmware you shouldn't have a problem.

Savagerun said:
Don't know why it's failing for you as long as you're doing a full wipe then flashing the rom (make sure the md5 matches on your rom download) then flash the firmware you shouldn't have a problem.
Click to expand...
Click to collapse
So the md5 for the firmware has to match the md5 for the ROM I'm trying to install? I mean I'm not new to this stuff, but the newer everything gets, the more complicated it gets, ya know. new phone for me and its a little more complicated this time around.

thesmashippy said:
So the md5 for the firmware has to match the md5 for the ROM I'm trying to install? I mean I'm not new to this stuff, but the newer everything gets, the more complicated it gets, ya know. new phone for me and its a little more complicated this time around.
Click to expand...
Click to collapse
No what i was saying is after you download a rom you should check to make sure the md5 of that rom matches the posted md5 that's under every rom link. If your downloaded rom's md5 doesn't match what's posted then you got a bad download and you'll need to download the rom again till the md5 matches. Im thinking you have a bad download since you're failing installing certain roms. There's a few md5 checkers in the playstore or you can use a file manager like Astro file which i use to check my md5. That's the first place i would start if a rom failed to install.

Savagerun said:
No what i was saying is after you download a rom you should check to make sure the md5 of that rom matches the posted md5 that's under every rom link. If your downloaded rom's md5 doesn't match what's posted then you got a bad download and you'll need to download the rom again till the md5 matches. Im thinking you have a bad download since you're failing installing certain roms. There's a few md5 checkers in the playstore or you can use a file manager like Astro file which i use to check my md5. That's the first place i would start if a rom failed to install.
Click to expand...
Click to collapse
Oh, awesome. Thank you!

[Q] I don't get it

I had to Odin and went back to ncg. I have searched and posted in relevant forums and no answers that work. I am rooted have safestrap and I have flashfire. I would like to go up to the new MOAR rom. For some reason when I try to flash anything with safestrap it fails everytime, just shows updating partitions and then a red failed.
When I try with flashfire I can not see zips on my SD or internal. Everyone says it should work fine. It doesnt. I did repatriation with pit when going to ncg. I try flashing the stock rooted OA8 and it fails. Any help is super appreciated. I did not have trouble when I first got the phone and rooted but I started at OA8 and went to ncg.

Noob Question: ROMs not working?

I rooted my device using the following method:
(I CANT POST LINKS YET)
(In short, I downloaded Odin3 v. 3.10.6 & Installed TWRP 3.0.2). Whoop!
So I verified my device is now rooted (via Root Check app). Now here's where I'm running into trouble .. I'm wanting to install the Dr. Ketan ROM (Galaxy S7 conversion) using the following method:
galaxynote4root[DOT]com/t-mobile-note-4-roms/how-to-convert-galaxy-note-4-into-galaxy-s7-edge/2/
But I'm running into the problem where when I load the ROM, it says the following:
no MD5 file found
Zip file is corrupt!
Error installing zip file ‘/external_sd/N910_MM_DrKetan_ROM_M4_XDA.zip’
Do I have to download a custom Marshmallow ROM if I already have stock Marshmallow 6.0.1 on my phone for above ROM to work correctly? (My phone is the SM- N910T version). Any help would be greatly appreciated. I'm so interested in getting into this but there's so much information out there, I'm getting a bit overwhelmed and not sure quite where to start. I know there is a link on this site to get this ROM going but I'm really not understanding their process and above site puts everything in laymen's terms for me- thanks in advanced
Update:
I verified the downloaded ROM has an MD5 via MD5 Check Utility v2.31

I found out I had a corrupted SD card, I swapped them out and everything worked seamlessly.