[GUIDE] Flashing ROMs correctly, every time
- Thread starter cobraboy85
- Start date
-
- Tags
- question
Flashing Status 7
Hi i have a samsung galaxy s3 t999 and i have flash 3 different roms to my phone, but last week i went back to stock firmware and when i try to go back now to one of the roms using CWM i keep getting the status 7 error even if i try flashing the same roms i have previously installed. The steps i follow are downloading the rom, in this case liquidsmooth nightly latest version, update to the latest version of CWM using rom manager and wipe date cache and dalvik then installing the rom and the gapps. Any help would be appreciated.
Hi i have a samsung galaxy s3 t999 and i have flash 3 different roms to my phone, but last week i went back to stock firmware and when i try to go back now to one of the roms using CWM i keep getting the status 7 error even if i try flashing the same roms i have previously installed. The steps i follow are downloading the rom, in this case liquidsmooth nightly latest version, update to the latest version of CWM using rom manager and wipe date cache and dalvik then installing the rom and the gapps. Any help would be appreciated.
Misterjunky
Senior Member
re: error 7
Go into recovery and flash this CWM recovery which is made for your phone
Here is the link: http://d-h.st/jbT it is the newest version.
After flashing reboot to recovery and flash whatever rom you were trying to flash.
All should be good.
Just in case there is a problem, the error 7 can also mean that the rom you are trying
to flash might be corrupt for one reason or another and have a checksum error, if that's
the case you would need to download the rom again, and be sure to download it to your
computer not the phone then copy it to the phone and flash it.
Good luck!
Go into recovery and flash this CWM recovery which is made for your phone
Here is the link: http://d-h.st/jbT it is the newest version.
After flashing reboot to recovery and flash whatever rom you were trying to flash.
All should be good.
Just in case there is a problem, the error 7 can also mean that the rom you are trying
to flash might be corrupt for one reason or another and have a checksum error, if that's
the case you would need to download the rom again, and be sure to download it to your
computer not the phone then copy it to the phone and flash it.
Good luck!
Tanks for your fast response i have tried flashing the CWM file you told me but i cant it gets me status 7 error
It say this
Installing update...
assert failed: getprop("ro.product.device") == " d2tmo" l! getprop ("ro.build.product") == "d2tmo"
E: Error in /emmc/CWM-6023_tmo_naddict.zip
(Status7)
Installation aborted.
I rooted the phone from stock android 4.0.4.
---------- Post added at 05:00 PM ---------- Previous post was at 04:47 PM ----------
I tried installing it from internal and external card and get the say error, i dont know what im doing wrong i used to do the same procedure for flashing roms and it always worked. Thanks for everything.
Misterjunky
Senior Member
re: Rom Issues
If you cannot flash that cwm recovery zip file and it gives you the status 7 error then as a
last resort the only thing left to do is to Odin flash the stock Samsung Touchwiz Jellybean
v4.1.1 pre-rooted firmware to give you a fresh start.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benifit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
If you cannot flash that cwm recovery zip file and it gives you the status 7 error then as a
last resort the only thing left to do is to Odin flash the stock Samsung Touchwiz Jellybean
v4.1.1 pre-rooted firmware to give you a fresh start.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benifit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
- Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
- Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
- Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
- Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
- You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
- Click on the PDA button in the middle-right area of Odin.
- Browse to and select the Firmware you downloaded (TAR file)
- Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
- TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
- If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
- Click Start to begin the flash. This will take a while, so be patient!
- Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
- You may unplug the phone and close Odin if you wish.
- Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
- (It may seem to hang during boot, this is normal and you must be patient!!!)
Last edited:
Don't you guys have a TWRP recovery available for your device? In twrp it often says error 7 if you have md5 check on. Generally, turning it off allows things to flash fine. I think some zips just aren't signed properly, or something.
Sent from my EVO using xda premium
Sent from my EVO using xda premium
The naddict file is bad. That is the problem. I have tar files in my signature for Odin.
It's not a signing issue, it's a scripting issue.
It's not a signing issue, it's a scripting issue.
I have installed both samsung official versions 4.0.4 and 4.1.1 re root flash CWM 6.0.3.1 and still keep getting status 7 error. I downloaded the roms again and still the same, i even use TWRP 2.5.0.0 and get error and failed and use all the files Aerowinder recommended and still get the same error. Really dont know whats going on.
---------- Post added at 10:01 PM ---------- Previous post was at 09:50 PM ----------
Sorry in advance for insisting.
---------- Post added at 10:01 PM ---------- Previous post was at 09:50 PM ----------
Sorry in advance for insisting.
You can't get error 7 if you use my files. Because it's a tar file and you can't flash it with recovery. Use Odin to push the recovery (everything you need is in my signature), and your problems will stop.
No i mean i used all ur files, and have CWM running and rooted phone but when i try to flash liquidsmooth rom 2.2 d2tmo i get again status 7 error. I tried to use TWPR and still get and error. All is good till i try to flash a rom, i re download it and still the same thing. Sorry for the misunderstanding.
What is the model number of your phone, and what rom are you currently using?
My phone is Samsung galaxy s3 SGH T999
Android 4.1.1 official
Baseband T999UVDLJA
KERNEL 3.0.31 -370274 se.infra@SEP-91 #1 SMP PREEMPT Fri Oct 19 22:16:17 KST 2012
build numver JRO03L.T999UVDLJA
Does this happen for flashing custom kernel, i have installed bms and kt747 anyway thanks for the info i will try to find a way to make it stock if there is one.
---------- Post added at 11:43 PM ---------- Previous post was at 11:24 PM ----------
I did what you say, and at least the rom finish installing but it got stuck on the samsung galaxy s3 screen it did not reach the boot logo of the rom.
---------- Post added at 11:43 PM ---------- Previous post was at 11:24 PM ----------
I did what you say, and at least the rom finish installing but it got stuck on the samsung galaxy s3 screen it did not reach the boot logo of the rom.
Need to factory reset through recovery (because you went from 4.1.1 > 4.2.2). And you need to flash GApps, too. http://goo.im/gapps, get the ones for 4.2.2.
I did wipe data wipe cache wipe dalvik format system and then flash liquidsmooth then gapps 20130301 but i get stuck when the screen says galaxy s3 it doest go to the liquidsmooth loading screen.
---------- Post added at 12:19 AM ---------- Previous post was at 12:10 AM ----------
Sorry i have flash before and non of these happened, and thanks for all your help.
---------- Post added at 12:19 AM ---------- Previous post was at 12:10 AM ----------
Sorry i have flash before and non of these happened, and thanks for all your help.
Thanks for all your help but i still stuck on the samsung galaxy s3 screen it goes no further, but really thank you for everything.
Misterjunky
Senior Member
re: a sure fix
Here is a 100% sure way to fix the stuck screen on your phone.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your computer's desktop & unzip the file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock-rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
Good Luck!
Here is a 100% sure way to fix the stuck screen on your phone.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your computer's desktop & unzip the file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock-rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
- Download the stock-rooted Odin flash firmware for the T999 Tmobile Galaxy S3
- Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
- Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
- Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
- You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
- Click on the PDA button in the middle-right area of Odin.
- Browse to and select the firmware you downloaded (TAR file)
- Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
- TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
- If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
- Click Start to begin the flash. This will take a while, so be patient!
- Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
- You may unplug the phone and close Odin if you wish.
- Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
Last edited:
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
45So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there
it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers1Yeah I figured it will would be a useful guide. I'm just glad others feel the same. Beauty of open source - doing things because you like it and to benefit the community
Sent from garaxy1
Personally, I say no. A few people aparently found it to sometimes be necessary on a previous phone and are just more comfortable continuing to do it that way. I never have wiped more than once, and never had any problems.
Its just what you're more comfortable with in the end. It shouldnt hurt anything, so its not a wrong way, just unnecessary imo.
Sent from my SGH-I747 using xda app-developers app
