Related
Every non-Aosp rom I've ever flashed (Acs, bonsai, midnight, simply aosp, viper, et..) have always ended up freezing and forcing me to remove the battery to re-boot, I've followed instructions, re-downloaded the roms etc. CM7 and MIUI, both Aosp, have never had that problem, always flashed right the first time, never had to flash twice. I guess I'm just curious if anyone can explain why aosp roms work fine (minus mms, 4g, and the other aosp bugs) and every rom based off of official releases always seem to end up failing?
Sent from my Samsung-SPH-D700 using XDA App
wrong section man, this is not development (it will be moved soon).
If you are following instructions to the point in ROM guides, I have no idea. Sorry. But more specifics on your problems would help us help you
Its because most of the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
GituSum said:
Its because the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
Click to expand...
Click to collapse
Not to sound like an ass, but that's not entirely true. I have never had to flash non-aosp roms more than once.
djbacon06 said:
Not to sound like an ass, but that's not entirely true. I have never had to flash non-aosp roms more than once.
Click to expand...
Click to collapse
Even after an odin? Cause I've had to every time. If I'm just going between two roms I don't. Maybe my phone is just picky
GituSum Epic 4G
GituSum said:
Maybe my phone is just picky
Click to expand...
Click to collapse
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
But yeah, even after clean ODIN installs it works fine first flash. Did that today as a matter of fact
djbacon06 said:
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
But yeah, even after clean ODIN installs it works fine first flash. Did that today as a matter of fact
Click to expand...
Click to collapse
Then ya mine is picky. I flashed EE03 last night and used odin to go back to froyo today and had to flash twice before it booted up. No big deal just an extra couple minutes to flash and boot up
GituSum Epic 4G
GituSum said:
Then ya mine is picky. I flashed EE03 last night and used odin to go back to froyo today and had to flash twice before it booted up. No big deal just an extra couple minutes to flash and boot up
GituSum Epic 4G
Click to expand...
Click to collapse
Haha you're not the only one! On DK28 I had to flash twice everytime! And then for a little while on EB13. I don't know what changed though. But I havent had to do it for a longtime. Maybe it's because I never boot into stock before flashing?
It mainly jas to do with us having a crappy recovery.
Sent From My Evo Killer!
djbacon06 said:
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
Click to expand...
Click to collapse
UH OH are you ACS guys developing AI and secretely putting it in our phones? hahaha
Even from a fresh odin, all other roms end up freezing, CM7 or MIUI I can flash over anything, and they always work, everytime.
Sent from my Samsung-SPH-D700 using XDA App
Flash srf and then vision 1.1 over it. Post in the right sub-forum.
Sent from my SPH-D700 using XDA App
Skimp Killah said:
Even from a fresh odin, all other roms end up freezing, CM7 or MIUI I can flash over anything, and they always work, everytime.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
I experience this to an extent as well.. w/ SRF 1.0.2 it flashes first time and works flawlessly..
What I've found is that all devices aren't created equal. Some work really well others are finicky.
What I've found that works for me is immediately after a flash, I can tell if it's gonna be wonky or work. After the flash, if it 'delays' before popping back up to the recovery menu, it's gonna fail. If the recovery menu pops up right away I'm good.
When it 'fails'.. I'll reboot system.. on the white samsung screen, pull the battery. boot back into recovery, then re-flash. boot system if it doesn't auto boot and you're good.
Not sure why it's like this, but it works for me. MY device doesn't always play nice w/ every version of every ROM and rather than whining in all of the ROM threads about why the rom sucks and I can't use it.. I've figured out a way to use them through troubleshooting and process of elimination using some of the 'fixes' that are posted in the different threads.
all Epics are not created equal. Just gotta figure out what works for yours.
EDIT: now that I think about it, (not that it's a big deal) I'm gonna go find noobnl's thread about checking for bad blocks on the ONEnand... just curious if journaling is trashing my NAND (I don't think it is, but ya never know)
EDIT: Still only 3 bad blocks. Nothing to worry about for me
spyder09 said:
UH OH are you ACS guys developing AI and secretely putting it in our phones? hahaha
Click to expand...
Click to collapse
LOL, I am by no means developing anything for ACS. I'm not a developer, just an advocate
And knowing how k0nane does things, there would be absolutely no trace of something like that in ACS roms
Try ec05plus its an odin tar, and it will work from the first boot...
Sent from my SPH-D700 using XDA App
GituSum said:
Its because the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
Click to expand...
Click to collapse
That's not true. He mentioned Simply which I know for a fact doesn't backup/restore data.
1.) Odin back to EC05
2.) Re-root and Install CWM3
3.) Let it convert you to EXT4
4.) Upgrade to CWM 3.0.2.5
5.) Wipe data.
6.) Go to Advanced/Mounts and hit Format /system
7.) Flash the rom of your choice
8.) If it fails again wipe data x3 and then system x3 for good measure, try try again.
Hope that helps.
Pst make sure to use the proper section next time
Still not sure why this is in development.
k0nane said:
Still not sure why this is in development.
Click to expand...
Click to collapse
Won't be for long, about to pm impaler unless you already have.
Sent from my SPH-D700 using XDA App
TheDub said:
That's not true. He mentioned Simply which I know for a fact doesn't backup/restore data.
1.) Odin back to EC05
2.) Re-root and Install CWM3
3.) Let it convert you to EXT4
4.) Upgrade to CWM 3.0.2.5
5.) Wipe data.
6.) Go to Advanced/Mounts and hit Format /system
7.) Flash the rom of your choice
8.) If it fails again wipe data x3 and then system x3 for good measure, try try again.
Hope that helps.
Pst make sure to use the proper section next time
Click to expand...
Click to collapse
Iv'e tried everything listed other than upgrading to the newest CMW, I'm thinkin I'm just gonna have to wait for CM7 or MIUI to have mms and what not.
Sent from my Samsung-SPH-D700 using XDA App
Moved to Q&A.
I should know this but I haven't tried it. Can I make a backup of my current SRF1.2 ROM via CWM, flash an EG22 rom and if I decide to go back to Froyo simply restore my CWM backup of SRF1.2?
Thanks
yes
5char
chris41g said:
yes
5char
Click to expand...
Click to collapse
Thanks, figured as much.
youll still have the eg22 modem, which will work, but you can odin just the ec05 or whatever modem you want back...
Well, for the most part yes. I do a ton of testing and I have gotten Google Services Framework errors on occasion when restoring a nandroid specifically after being on Gingerbread. It seems totally random though and if you aren't constantly changing setups like I am, you may not have this happen to you
Sent from my SPH-D700 using XDA Premium App
I always have 2-3 nandroid backups to switch between different roms etc. Been back and forth between EC05 based roms and EG22 w/plus kernel like 4-5 times this week alone, and no issues.
pvtjoker42 said:
I always have 2-3 nandroid backups to switch between different roms etc. Been back and forth between EC05 based roms and EG22 w/plus kernel like 4-5 times this week alone, and no issues.
Click to expand...
Click to collapse
I keep 3 or 4 nandroid backups myself. Perhaps its due to the absurd amount of testing I do that it catches up to me (sometimes 4 to 5 times changing setups in a day) that it catches up to me. Its not likely but it is a possibility.
Sent from my SPH-D700 using XDA Premium App
Hey John, with all the switching around and flashing, what method are you using for restoring apps and data? cwm advance nandroid restore or titanium backup or both?
I've been on srf exclusively but with all the cool new gb roms I'm itchin to play around. Also what is your current favorite new rom?
glenner444 said:
Hey John, with all the switching around and flashing, what method are you using for restoring apps and data? cwm advance nandroid restore or titanium backup or both?
I've been on srf exclusively but with all the cool new gb roms I'm itchin to play around. Also what is your current favorite new rom?
Click to expand...
Click to collapse
I never restore data from one ROM on to a different ROM. I always do a clean install of apps and such. What I do is flash a ROM, get all of my apps added, set it up exactly how I want it then make my nandroid. Now, when I do restore data I do it through CWM Recovery Advanced/Restore Data Only. I do that (for example) if I install SRF 1.2 fresh then restore data from a SRF nandroid. Now people do restore data only from one ROM to another and don't have problems. I just can't test thoroughly that way because it could be app conflict causing an error. I wouldn't recommend restoring data from a Froyo ROM onto Gingerbread though. Now my Favorite ROM??? Wow that's tough. On Froyo; (in no specific order) SRF 1.2, Urban Regeneration, and ERA ReVolt. On Gingerbread its a ROM that isn't out yet...CompKid's upcoming EG22 release is going to be a big hit. They are all good though. You really have to try them and see what works best for you
Sent from my SPH-D700 using Tapatalk
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
tramane said:
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
Click to expand...
Click to collapse
It won't matter as its the ics kernel that is the problem not rouge not Acs not cwm.....
Sent from my SPH-D710 using xda premium
I've been flashing with it. So have plenty of others. Some people bricked and they may have been using rogue but I wrecked a Honda once.... Its usually user error.
Sent from my SPH-D710 using XDA
You have a point.Im coming from original Epic 4g and im deffinetly confused about the kernels on Epic Touch.
This is what I mean:On original Epic they had kernels that you could flash on top of just about any rom in cwm or odin.But for Epic Touch im yet to find any kernels for it.Yes there are some stock EL29EG31,etc.. in wiki pages but thats it?
There are only two kernels on wiki that are non stock and they are Hitman's kernel and Rogue kernel,is that all we got?Og Epic had about 30 different nonstock kernels.
So my question is this:
1 Are Rogue and Hitman kernels come with their own cwm?
2 Are Rogue and Hitman are only two nonstock kernels?
3 Are all the other lernels on wiki EL29,EL26,EG30,etc.. are just stock or modified stock?
4 Can any of those kernels(besides ics Rogue of course) be flashed to any GB rom?
5 Are there any difference between different versions of Rogue and Hitman?Or latest is the best?
6 And if Rogue and Hitman also come bundled with their own version of cwm,what is the difference between those two cwm's?
I been on original epic xda forums for years and this **** is confusing,they should make a thread for new people.
Pretty sure its not user error, given that at least 3 of our most prominent bleeding edge devs bricked doing it. I made the mistake of believing it was user error, but all evidence points to the contrary.
The reason we have recovery on ICS kernels is there are things at this point that you can safely flash (basically, anything that doesn't wipe data). You can safely flash the visual voicemail .zips from rogue ICS recovery on AOSP roms, for example. But you can't flash a whole rom. You can make a nandroid for later restore from EL26 cwm. You can do a lot of things actually. Just don't flash an actual rom, and you should be fine.
lviv the reason there aren't many options on the ET for recovery is there aren't many devs that work with it. SteadyHawkin repacks rogue for us, and that's about it. We used to have a few others that did so, but now it's just SH. Personally I don't really care as rogue recovery works perfectly fine, and the reason we use stock CWM from EL26 is because it's all we need (no point in repacking another kernel since we all have access to that one, why waste the effort to put CWM on EL29 when chris41g did a fine job on EL26 and we are all using it for ICS flashing right now?). No point putting any more work into packing a diff recovery on ICS kernels when there's no source and there's a ton of fear of bricking going on.
I'm certainly no dev, but those are my observations.
I've said this before in the threads discussing the bricks. I am not a dev, so they can correct me.
I don't think the bricks had anything to do with the rogue repacks. I think it has to do with the way ICS handles the data partition. It seemed like the bulk of the bricks happened when we tried a factory reset, or wipe data and at that point we burned up our emmc chips.
Sounds crazy that that is possible just wiping a data partition, but it was pretty consistent.
At first I thought it was the temp touch recovery because that was what people were using when ICS was first leaked. I think most of us were also flashing it through the stock recover rather than odin or mobile odin. But, it began happening with rogue repacks as well.
Once the source drops these problems will probably clear up.
To the ops question, someone already answered. We can flash just about everything else with the repacks. I prefer the rogue repacks because he has streamlined them making them handier to use.
Sent from my SPH-D710 using Tapatalk
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Devi0124 said:
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
I've never bricked using the ICS repacked recoveries, and I've used em to flash to different roms without format.zips before we knew it was even an issue, but now that I know this could potentially brick your phone, I won't be doing anything in recovery anymore except flashing themes or something that does not involve wiping. I'm not longer on ICS anymore though, as I see it completely pointless until official is out. Too much flashing, and not enough functionality ATM to see usable, runs kinda slow too, not complaining at all just stating why I'm not on it, when it's official it will be great, and the devs will be able to tweak the final build for some massive speed.
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
i flashed roms with rouge
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
I'm another original epic owner that just switched to the touch....I've rooted and flashed ics.....now over there on the epic 4g we don't have ics source either...but we have cwm that flashes roms ,backups, restores, we can even flash a ROM to boot from the sdcard to calibrate the sensors and update your prl....so why do we need source on the touch to acquire those luxuries?
XDA Premium
rujelus22 said:
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
Click to expand...
Click to collapse
Same here as far as flashing things via rogue recovery. I even nandroided back to a gb rom from the fc24 repack, after wiping manually. I am not a fan of wipe all, i just like to verify my actions, so I do it manually. I am definitely not sure what is causing issues, but different phones have different actions on kernels in general, and our phones arent even near ready to handle them. That is why it is taking so long in order to push out official ICS, cause they need it to function on every phone, not just one. I am running mijjah XPLOD mini, and it works fantastic on my phone, but during charging it overheated until I flashed over the FD19 kernel.... Then problem solved. Maybe just a lot of these phones were first gen epic touches, and they couldnt handle the newest kernel..... I just bought my phone in december, so maybe my phone can handle it.... Just a something to ponder over.
Sent from my SPH-D710 using xda premium
Entropy512 said:
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
Click to expand...
Click to collapse
Thanks Entropy512 for the great response and insight! I hope more of the newbies (and some of the other hold outs) read your post. If guys like you, SiyahKernel, SteadyHawkin and some of other unbelievably fantastic devs can major issues and/or brick their device, and have found it to be the kernal (the other 'real' devs' have said that too!); than I for one and going with that! Thanks for all your work. Hopefully we'll get the final real source soon and than can pick through that.
-EViL-KoNCEPTz- said:
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I think you nailed it EK. If you watch what's going on in recovery when you flash the format all zip, it formats system which is not the same as a factory reset. After system it formats cache and dalvik. I haven't heard of any bricks flashing Calkulin's format all zip with an ICS recovery and then flashing an ICS rom. I've done it myself a few times but to be safe I now flash the EL26 kernel first.
For the life of me, I cant figure out why I can never restore my back ups after testing out various roms and kernels. I know it has something to do with the kernels and/or recoveries that are used when backing up and restoring but I cant seem to figure it out. Every time I try to restore a backup I usually get an MD5 mismatch and it fails. I THOUGHT that if I did the backup and restore using the SAME kernel/recovery versions that it would work, but that doesnt seem to be working. Is there something I am missing? Ill give you an example in case you have any tips.
I was running Calks v1.5 for awhile, then decided I wanted to try the AOKP rom. As noted in the AOKP thread, to restore, Odin the EL26 CWM kernel/recovery and run a back up. So I Odin the kernel/recovery, ran the backup, then attempted a restore just to see if it worked. Successfully able to restore from within that same CWM session. So I Odin EL26 CWM again, and this time flashed the AOKP and gapps and rebooted into AOKP. No problem there. Messed around with AOKP (which is awesome) but wanted my daily back so I Odin the EL26 CWM again, and tried to restore the Calk 1.5 and got the MD5 mismatch.
What am I doing wrong?
Are you renaming them? They can't have any spaces in the name, must be something like aokp_may10 instead of aokp may 10
Sent from my SPH-D710 using Tapatalk 2
Son of a *****!!! lol I definitely renamed the backups after they completed so I would know which one was which. And definitely had spaces in the names. So thats screwing up the MD5 hash? If I rename them back to what they were will they work?
I used to get that all the time if I copied the nandroid off to the pc and back.
Anyway, if that's not the case for you, I think it's because you are on a totally different version of recovery.
Wipe the phone using Calk's Format All, install Calkulin's v1.5 rom from scratch, boot into recovery and THEN do your restore.
Edit: Well, I saw you beat me to it on the post. LOL
I'll be your Plan B then.
tdunham said:
I used to get that all the time if I copied the nandroid off to the pc and back.
Anyway, if that's not the case for you, I think it's because you are on a totally different version of recovery.
Wipe the phone using Calk's Format All, install Calkulin's v1.5 rom from scratch, boot into recovery and THEN do your restore.
Click to expand...
Click to collapse
Nah I did the backup and attempted restore from EL26 CWM (so I could flash the ICS rom "safely"). I also didnt copy them from the SD card so hopefully thats one less reason for the failure. Thanks
ryan2202 said:
Son of a *****!!! lol I definitely renamed the backups after they completed so I would know which one was which. And definitely had spaces in the names. So thats screwing up the MD5 hash? If I rename them back to what they were will they work?
Click to expand...
Click to collapse
That im not sure of, but try to rename with no spaces and report back
Sent from my SPH-D710 using Tapatalk 2
!!! It f*cking worked lol. Many many thanks!! And to think of all the time I have wasted reloading roms from scratch... :beer:
Glad that worked! The bright side is your an expert at flashing roms now!
Sent from my SPH-D710 using Tapatalk 2
ryan2202 said:
!!! It f*cking worked lol. Many many thanks!! And to think of all the time I have wasted reloading roms from scratch... :beer:
Click to expand...
Click to collapse
Lol I remember having this problems back in the days of the galaxy s, I've spent so many hours setting everything up all the time more than testing the roms itself, until I asked this same question.
Sent from my SPH-D710 using Tapatalk 2
Are the ics roms safe to flash? The 1st time I flashed a ics rom,i had probs. No recovery,glitchy and jus plain janky. Im sure they have come along way. Can som1 recommend a safe stable ics rom that also has rogue recovery or acs?
Sent from my SPH-D710 using xda premium
If you want to go back to gingerbread use el29 restore get recovery then flash CyanogenMod 9 it is better than most roms based off leaks.
Here is the latest stock ICS.
http://forum.xda-developers.com/showthread.php?t=1694695
Give the devs a little time and you can flash a kernel with the recovery you want.
harley1rocker said:
Are the ics roms safe to flash? The 1st time I flashed a ics rom,i had probs. No recovery,glitchy and jus plain janky. Im sure they have come along way. Can som1 recommend a safe stable ics rom that also has rogue recovery or acs?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
They are safe to flash if you follow OP directions. Always flash from el26 cwm recovery and you're good. If you cant live without recovery, flash a touchwiz rom and use agat63s repack recovery.
SFhub just released an updated FF02+CWM repack built on GB code to avoid the eMMC lockup bug. However, you need to check the ROM and see if update-binary is corrected or not.
Please look for his post on this here:
http://forum.xda-developers.com/showthread.php?t=1694695&page=7
The other safe solution is the one that has been known - go back to EL26 and flash away from there. (GB doesn't have the offending code that causes the bug to be triggered.)
I've been using Calkulin's E4GT 2 v1.6 ICS rom since version 1.6 came out (FE22) and I haven't had a single crash or FC, and I've been getting good battery life.. I never even get close to dying and thats even with a couple hours of screen on time (games, facebook, lots of texting, ~1hour talk time).
I'd say go for it =) Just make sure you follow all instructions carefully! This ROM was very easy to flash.. I had been using Calkulin's GB rom (el29) and all I had to do was wipe my caches and flash his .zip file in CWM.. bam, ICS ^_^
When you say safe what is it you really mean... cuz its all SAFE if you know what you are doing..
Well nothing is ever 100% safe. There is always a small chance you could screw things up somehow (the eg31 deal back when the phone was first released, the emmc bug, etc). There are always possible unknown side effects that don't become obvious until down the line.
That said, if you are careful, the odds of doing something irreversible are extremely small on a phone that has been out for a few months or more.
Sent from my SPH-D710 using Tapatalk 2