When this happens, the fix is to "wipe data/factory reset" from recovery. In CWM, it's on the front page.
[GUIDE] Flashing ROMs correctly, every time
- Thread starter cobraboy85
- Start date
-
- Tags
- question
I have done that like 1000 times but still the same error, this phone became un flashable it seems. I have wipe that format system, wipe everything and still nothing, its really frustrating and worse because i had flash the phone a lot of times super easy and with no problems.
Could it be the partition tables or the buil prop, or the kernel, im trying it from stock factory firmware it should go ok with no problems i really dont understand what is the problem, i am doing it like i have always done it, installing the samsung official android version, then rooting and then flashing with cwm or twpr latest version doing thes wipes, it have always work with no errors and now its not working.
Here is the steps i have always used that worked and now seem useless.
Install official android version 4.0.4 for sgh t999
Root using the method from xda
Flash superuser via cwm
Update cwm via rom manager or use goomanager for twpr
Wipe data/ factory reset
Wipe cache
Wipr dalvik cache
Flash rom
Flash gapps
Reboot
Never had problems till now.
Last edited:
This issue has gone on for way too many pages for me to re-read everything. So, if you wouldn't mind, a quick numbered recap?
1) Can you flash with Odin, and successfully use, completely stock UVDLJC? The .tar.md5 from SamMobile (link in my signature). Is this functional for you?
2) When you flashed Wicked, did you attempt to use the stock LJA kernel? I believe it's an option in the Aroma installer, but it's been a while, so I could be incorrect.
3) You are currently using CWM Touch 6.0.3.1. Have you attempted to use TWRP 2.5.0.0?
4) You have attempted to flash AOSP ROMs as well, and had the same issue? Have you tried other kernels with these, as well?
1) Can you flash with Odin, and successfully use, completely stock UVDLJC? The .tar.md5 from SamMobile (link in my signature). Is this functional for you?
2) When you flashed Wicked, did you attempt to use the stock LJA kernel? I believe it's an option in the Aroma installer, but it's been a while, so I could be incorrect.
3) You are currently using CWM Touch 6.0.3.1. Have you attempted to use TWRP 2.5.0.0?
4) You have attempted to flash AOSP ROMs as well, and had the same issue? Have you tried other kernels with these, as well?
1) Yes right now im using stock uvdljc dow loaded from sammobile and is running normal.
2) Yes i left evrything stock did not change anything and got stuck in the black and white wicked screen never booting up. And left the kernel stock.
3) i have us cwm touch 6.0.3.1, non touch 6.0.3.1 and twrp 2.5.0.0 and still got stuck on the wicked screen.
4) i have tried flashing liquidsmooth and slim bean roms i have used already and now get the symlinks: some symlinks have failed. When i got to properly install this roms i have used bms kernel and kt747 with them mostly kt747.
In CWM i get symlinks : some symlinks failed status 7
In TWRP i get symlinks : some symlinks failed Error executing updater binary in zip
And sorry for all the post it just weird for me that suddenly i cant flash even the same roms i have once flash.
Last edited:
Thanks for all your help i tried and get it to work mounting system and cache in twrp. Thanks for everything u guys are life savers.
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
