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.
Related
Hey guys, I seem to be having a problem on my phone recently.. Every time I start it up, or try to load an app or something, I get a message saying the process ends. This happens with Google Apps, Gingerbread Keyboard, Etc. I've tried wipe x3 then reflash, but it doesn't do anything.
I'm running
Genocide Kernel, Firmware 2.2.1, And Simply AOSP v3.1.2
I believe it's still on SFR 1.2 , but it's not saying that in the build number so I'm not sure..
someone please help.
If you have a good nand backup you can do a factory data reset and then restore advanced data. That will clear up any of the FCs. Or clear data in each of the apps giving you problems in settings>applications>manage applications>all and scroll to google services framework and click it and clear data. Do the same for the Gingerbread keyboard and any other app FCing.
kennyglass123 said:
If you have a good nand backup you can do a factory data reset and then restore advanced data. That will clear up any of the FCs. Or clear data in each of the apps giving you problems in settings>applications>manage applications>all and scroll to google services framework and click it and clear data. Do the same for the Gingerbread keyboard and any other app FCing.
Click to expand...
Click to collapse
I will try this, but the other problem is, it just started having problems with the android processor. Like, I did a restore, and all the sudden, I'm getting all the errors I was getting originally, and like the core & android processor thing is failing.
JWhitez said:
I will try this, but the other problem is, it just started having problems with the android processor. Like, I did a restore, and all the sudden, I'm getting all the errors I was getting originally, and like the core & android processor thing is failing.
Click to expand...
Click to collapse
Sounds like you did not have journaling enabled. The Factory Data reset and a reflash of your ROM should fix it. Find out how to enable journaling for your ROM and do it.
kennyglass123 said:
Sounds like you did not have journaling enabled. The Factory Data reset and a reflash of your ROM should fix it. Find out how to enable journaling for your ROM and do it.
Click to expand...
Click to collapse
I'm sort of new to this, so just one more question. Now, I had Syndicate Frozen Rom 1.2 on originally, then I flashed Simply AOSP 3.1.2 . Which one would I reflash, Simply AOSP or SFR?
JWhitez said:
I'm sort of new to this, so just one more question. Now, I had Syndicate Frozen Rom 1.2 on originally, then I flashed Simply AOSP 3.1.2 . Which one would I reflash, Simply AOSP or SFR?
Click to expand...
Click to collapse
I believe Simply AOSP is a full ROM including kernel so that would be what you would reflash.
kennyglass123 said:
I believe Simply AOSP is a full ROM including kernel so that would be what you would reflash.
Click to expand...
Click to collapse
EDIT: Thank you very much. I just did it and it's working very well. I think it might have messed it up because I was trying to load 2 kernels without knowing it. Thanks for all the help.
JWhitez said:
So theres no need to flash the Genocide Kernel I used for SFR?
Click to expand...
Click to collapse
When you install a new ROM like AOSP all of that is gone. If you want to do SFR and Genocide instead of AOSP then go ahead. We should get you up and running first though and then you know the steps to take when it screws up again.
kennyglass123 said:
When you install a new ROM like AOSP all of that is gone. If you want to do SFR and Genocide instead of AOSP then go ahead. We should get you up and running first though and then you know the steps to take when it screws up again.
Click to expand...
Click to collapse
Yeah Kenny is right, as usual. If you decide to try SRF 1.2, flash the ROM, then journal on zip, then the kernel you want to use then reboot and enjoy.
Sent from my SPH-D700 using Tapatalk
JohnCorleone said:
Yeah Kenny is right, as usual. If you decide to try SRF 1.2, flash the ROM, then journal on zip, then the kernel you want to use then reboot and enjoy.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks John, welcome to the party. I think what you suggest is exactly what he needs. He just PMd that after selecting another theme in Simply AOSP it started FCing again.
JohnCorleone said:
Yeah Kenny is right, as usual. If you decide to try SRF 1.2, flash the ROM, then journal on zip, then the kernel you want to use then reboot and enjoy.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks, I'm back on SFR 1.2 with no problems, but I didn't need to flash jounral on, so I don't know. Would you know what to do to get on Simply AOSP 3.1.2 , because it has a kernel built in.
JWhitez said:
Thanks, I'm back on SFR 1.2 with no problems, but I didn't need to flash jounral on, so I don't know. Would you know what to do to get on Simply AOSP 3.1.2 , because it has a kernel built in.
Click to expand...
Click to collapse
Well, if you already have the ROM downloaded and it includes a kernel, all you should have to do is wipe everything 3x and flash it
Sent from my SPH-D700 using Tapatalk
JohnCorleone said:
Well, if you already have the ROM downloaded and it includes a kernel, all you should have to do is wipe everything 3x and flash it
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Whenever I do that, I get all those FC's...
I'll give it a go again if I don't decide to go to EG22..
JWhitez said:
Whenever I do that, I get all those FC's...
I'll give it a go again if I don't decide to go to EG22..
Click to expand...
Click to collapse
I would suggest either pming or posting on the AOSP thread what setup you're on and how best to convert to their Rom. Sometimes they've heard of conflicts or tricks that they can walk you through. I love SRF, but if you want to explore, you should know what works best to transition. You'll get it going, just keep toying. Worst you have to do is Odin and that's not terrible for the phone now and again.
The Root said:
I would suggest either pming or posting on the AOSP thread what setup you're on and how best to convert to their Rom. Sometimes they've heard of conflicts or tricks that they can walk you through. I love SRF, but if you want to explore, you should know what works best to transition. You'll get it going, just keep toying. Worst you have to do is Odin and that's not terrible for the phone now and again.
Click to expand...
Click to collapse
I gave up on it.. Went to EG22. Still debating on whether or not to go back to SFR / Simply AOSP.. because the battery life on RandomROM is absolutely amazing. But I'll PM him.
I've tried enabling the bluetooth both thru the pull down button and through the settings menu. It acts like it's starting to turn on, and then after a few seconds, just goes dark again.
Tried reboot. No luck.
Used ACS Recovery to do a pre-ROM wipe before flashing the new ROM.
Can't post in developers forum yet, so hopefully someone here can help. I read every page and every entry in the applicable forum for the ROM I flashed, but no one reported this problem or solutions.
Any ideas? I'd rather not have to flashback to stock or whatever. I've seen plenty of helpful posts for other bugs in the ROM. Just nothing for this. HELP!
Thanks,
Epic 4g
Gingerbread 2.3.5
ROM Revival MTD v2
JrWicked said:
I've tried enabling the bluetooth both thru the pull down button and through the settings menu. It acts like it's starting to turn on, and then after a few seconds, just goes dark again.
Tried reboot. No luck.
Used ACS Recovery to do a pre-ROM wipe before flashing the new ROM.
Can't post in developers forum yet, so hopefully someone here can help. I read every page and every entry in the applicable forum for the ROM I flashed, but no one reported this problem or solutions.
Any ideas? I'd rather not have to flashback to stock or whatever. I've seen plenty of helpful posts for other bugs in the ROM. Just nothing for this. HELP!
Thanks,
Epic 4g
Gingerbread 2.3.5
ROM Revival MTD v2
Click to expand...
Click to collapse
Backup that rom... flash a different rom... if bluetooth works then its that rom... btw I would strongly suggest not using acs recovery... use cwm 5.0.2.7... it is the officially supported recovery for our epics! Also acs does not play well with mtd roms so that may be your problem!
Sent from my SPH-D700 using Tapatalk
Get rid of ACS Recovery. It is not supposed to be used for MTD ROMs.
kennyglass123 said:
Get rid of ACS Recovery. It is not supposed to be used for MTD ROMs.
Click to expand...
Click to collapse
Bah humbug acs not play well with mtd blah!
I used it to convert to mtd when cyanogen first came and it worked just fine...... acs not the problem because even if he was on bml cwm5 before flashing he would have the same results.
Please stop blaming that recovery ^^
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
However once on mtd he shouldn't be using it
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Biggoron said:
Bah humbug acs not play well with mtd blah!
I used it to convert to mtd when cyanogen first came and it worked just fine...... acs not the problem because even if he was on bml cwm5 before flashing he would have the same results.
Please stop blaming that recovery ^^
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Click to expand...
Click to collapse
Maybe it worked for YOU but it is highly recommended to use CWM 5.027 to convert and note that if you want to convert and restore nandroid data it must come from 5.027.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Maybe it worked for YOU but it is highly recommended to use CWM 5.027 to convert and note that if you want to convert and restore nandroid data it must come from 5.027.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm pretty sire recoveries don't differ from phones... software is software its not a hardware difference just saying. How is your day going kenny?
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Biggoron said:
I'm pretty sire recoveries don't differ from phones... software is software its not a hardware difference just saying. How is your day going kenny?
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Click to expand...
Click to collapse
Ah always better after you brighten my day Biggie...lol.
BTW you know software is what drives the hardware. So any flash can go wrong at some point whether Odin, CWM, ACS, or Bonsai Recovery. Just sayin'...LOL. How you been?
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Ah always better after you brighten my day Biggie...lol.
BTW you know software is what drives the hardware. So any flash can go wrong at some point whether Odin, CWM, ACS, or Bonsai Recovery. Just sayin'...LOL. How you been?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
GRRRR.... oh me I'm good I see what your saying but how would be able to flat out blame that software for all you know it was the rom .... okay end of argument no reason to keep up this fiasco anyways I'm not saying to not use the official cwm I'm just saying you can't blame the issue on the recovery... I've had tons of bluetooth issues concerning kernels never the recovery
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
I agree...just trying to narrow down the possibilities. Probably just needed to delete some bluetooth data files. I forget which ones force the bluetooth database to rebuild.
Sent from my SPH-D700 using XDA App
BRICKED
Thank u all for the replies. I DID use ACS to do the pre-rom wipe, but I thought CWM got changed afterwards, somewhere in the process of flashing the new ROM, etc. Funny that several of you mentioned the possibility of that being the issue. I went to boot into recovery to check, and my phone bricked. #*(#@$%&. So, I had to odin back to stock and then root again, then use Titaniun just to get to my pre-ROM settings. I'm just gonna go without the custom ROM for now.
JrWicked said:
Thank u all for the replies. I DID use ACS to do the pre-rom wipe, but I thought CWM got changed afterwards, somewhere in the process of flashing the new ROM, etc. Funny that several of you mentioned the possibility of that being the issue. I went to boot into recovery to check, and my phone bricked. #*(#@$%&. So, I had to odin back to stock and then root again, then use Titaniun just to get to my pre-ROM settings. I'm just gonna go without the custom ROM for now.
Click to expand...
Click to collapse
You mean sponged, not bricked. As long as there is life you are not bricked. Just grab the official CWM 5.027 and flash that. When doing conversions like that don't use ROM Manager and all should be well. When in doubt, wipe wipe wipe.
Hi,
I'm thinking of taking the jump into CleanGB 1.05 MTD. Currently I have a rooted EI22 build. I'm going to update to the EI30 modem first but I'm unsure of the steps to get the CleanGB 1.05 build installed because of the change to the MTD filesystem. There is a how to video on the BML 1.03 page but I can't find anything on the MTD 1.05 build. From reading I think there are extra steps I need to take, or maybe the ROM does all the steps already.
Doea anyone have a link to a video, or instructions for loading the CleanGB 1.05 MTD ROM?
Thanks
JM
As long as you have ClockworkMod you are good to go. Most (I think all) MTD roms auto-convert for you. Then enjoy!
^^^^exactly... if you have cwm 5.0.2.7 you're good to go... if you're using acs recovery flash cwm first... all the roms do the work fo you...
Sent from my SPH-D700 using Tapatalk
Hey Noles, do you know what happens if you try to flash an MTD with CWM 3.XXX whatever? Does that also auto update to 5.0.2.7?
Coycaine said:
Hey Noles, do you know what happens if you try to flash an MTD with CWM 3.XXX whatever? Does that also auto update to 5.0.2.7?
Click to expand...
Click to collapse
I would think so... but people have reported errors using acs recovery when trying to conver to mtd using that recovery... so 3.x.x.x may give you the same problems... never tried it though so I'm not 100% sure...
Edit- and after flashing an mtd rom and converting to mtd DO NOT flash another recovery... not even 5.0.2.7... the cwm that the mtd rom installs is the only recovery that works on mtd for our phones
Sent from my SPH-D700 using Tapatalk
Coycaine said:
Hey Noles, do you know what happens if you try to flash an MTD with CWM 3.XXX whatever? Does that also auto update to 5.0.2.7?
Click to expand...
Click to collapse
MTD ROMs have their own MTD only version of CWM 5.0.2.7 that gets flashed with the conversion. Do not try to change it after converting..
It is also best to just update to CWM 5 before trying to convert. Just to be sure.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
MTD ROMs have their own MTD only version of CWM 5.0.2.7 that gets flashed with the conversion. Do not try to change it after converting..
It is also best to just update to CWM 5 before trying to convert. Just to be sure.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Hahaha I was editing my post with that info as you posted... lol... great minds think alike I guess...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Hahaha I was editing my post with that info as you posted... lol... great minds think alike I guess...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yup! LOL. You are always right there with the same answers I would give.
Hi,
just wanted to thank you guys for the help. I copied the CleanGB_MTD zip onto my SD card then used CWM to flash from card and presto... a few reboots later and now I'm running a new ROM. So far it seems to be going well.
Thanks again.
JM
Sweet, found the perfect thread for my question
I'm running cleanGB Mtd 1.05, came from CM7. I have unsuccessfully tried to flash a few things, I have an epic ringtones zip I picked up somewhere along the way that gives you a ton more system ringtones, I also tried to flash some ei22 transparent mms themes....anyway, none worked. did the usual process, wiped cache, dalvik, and nada. Nothing there. At least they didn't cause any harm either.
Not sure why this is....my only guess was they were designed for bml ROMs? Thought i had a good understanding of bml/mtd in which case i didn't think it would really matter which partition I'm on for these flashable zips to work....any takers?
Sent from my SPH-D700 using XDA App
mookdawg7 said:
Sweet, found the perfect thread for my question
I'm running cleanGB Mtd 1.05, came from CM7. I have unsuccessfully tried to flash a few things, I have an epic ringtones zip I picked up somewhere along the way that gives you a ton more system ringtones, I also tried to flash some ei22 transparent mms themes....anyway, none worked. did the usual process, wiped cache, dalvik, and nada. Nothing there. At least they didn't cause any harm either.
Not sure why this is....my only guess was they were designed for bml ROMs? Thought i had a good understanding of bml/mtd in which case i didn't think it would really matter which partition I'm on for these flashable zips to work....any takers?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yeah you did everything but the most important...mount system in CWM before flashing.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Yeah you did everything but the most important...mount system in CWM before flashing.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Pardon my ignorance KennyG, is this a necessary step I have to do manually every time I flash zips in MTD CWM? Something that never had to be done in CWM on BML... Please point me in the right direction if I am outta line here...or I know, I know...I should head right to search regarding MTD CWM and BML CWM...
mookdawg7 said:
Pardon my ignorance KennyG, is this a necessary step I have to do manually every time I flash zips in MTD CWM? Please point me in the right direction if I am outta line here...
Click to expand...
Click to collapse
Yes, and not a problem...I forget half the damn time and wonder why the changes to my theme are not showing up...LOL. You have to mount system anytime you want to flash something in MTD except ROMs and kernels...they seem to mount system for you. Restoring backups do not need system mounting either. MTD is still a new animal to us.
lol, we crossed posts, I was just editing that last one but you already were lightning fast on the reply. Thanks for that, and all that you contribute to the forum, I know your work well!
mookdawg7 said:
lol, we crossed posts, I was just editing that last one but you already were lightning fast on the reply. Thanks for that, and all that you contribute to the forum, I know your work well!
Click to expand...
Click to collapse
Just glad to help. I kick myself everytime I forget to mount system.
kennyglass123 said:
MTD ROMs have their own MTD only version of CWM 5.0.2.7 that gets flashed with the conversion. Do not try to change it after converting..
It is also best to just update to CWM 5 before trying to convert. Just to be sure.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Does that mean that, once converted to mtd, a person can back up and restore freely?
I had been holding off on the mtd because i thought restoring a nandroid would be cumbersome. Something about changing all the ext4 to yaffs2 in order to make it work.
sent from my secret underground bunker
mjben said:
Does that mean that, once converted to mtd, a person can back up and restore freely?
I had been holding off on the mtd because i thought restoring a nandroid would be cumbersome. Something about changing all the ext4 to yaffs2 in order to make it work.
sent from my secret underground bunker
Click to expand...
Click to collapse
You can back up and restore your MTD ROM freely, even a way of using ROM Manager (ask me). BUT you cannot restore backups of BML ROMs without jumping through all those hoops that you hinted about.
mookdawg7 said:
Sweet, found the perfect thread for my question
I'm running cleanGB Mtd 1.05, came from CM7. I have unsuccessfully tried to flash a few things, I have an epic ringtones zip I picked up somewhere along the way that gives you a ton more system ringtones, I also tried to flash some ei22 transparent mms themes....anyway, none worked. did the usual process, wiped cache, dalvik, and nada. Nothing there. At least they didn't cause any harm either.
Not sure why this is....my only guess was they were designed for bml ROMs? Thought i had a good understanding of bml/mtd in which case i didn't think it would really matter which partition I'm on for these flashable zips to work....any takers?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You must go into mounts and storage in cwm and mount /system... flash... unmount /system.... reboot...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
You must go into mounts and storage in cwm and mount /system... flash... unmount /system.... reboot...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Too slow....but more thorough to make up for it...LOL.
I am sure I have forgotten to unmount as well....need some of that Chinkocobra or whatever it's called.
I'm going to hijack my own thread to ask this. I do not have enough posts to put this in the developers fourm which is probably a better place.
How do the custom ROM's for the EPIC4g (any phone I guess) come about? The few ROM's I've looked at seem to be one man operations (i.e. toadlife for the CleanGB I use). Clearly the CM effort is a larger team effort. I'm very happy with the CleanGB ROM after a few days of use but I'm looking forward to an ICS based phone. I don't think I'm brave enough to jump onto a release candidate so I'm probably not switching to CM9 RC0 any time soon.
So is the normal path of develpment for the CM team the first release a new ROM (CM7 for gingerbread, CM9 for ICS,..) and then do the other custom ROM developers take this as a starting point to do their thing? Now that CM9 RC0 is out should I expect to see a bunch of custom RC0 ROMs released in the next few weeks?
Thanks for the help. Oh and if you see Toadlife ask him when CleanICS-MTD is coming ;-)
JM
I've had my GSII T-989 a little over a month, and it's been rooted for a couple of weeks and after reading many many posts I've finally decided on my first ROM - Tuesday Blu Ray. (I'm sure I'll be trying out many others too)! My question is; is it okay to flash the ROM and the MODs/fixes and that awesome theme 'Blu Pulsar' before my first reboot in CWR, or should I flash the ROM, let it settle for the recommended 10 minuets, then go back and flash the MODs/fixes and the theme?
I also created an update.zip of Titanium Backup; can I flash that right after flashing the ROM, or should I reboot before flashing anything else?
Thanks guys...I've spent many hours reading a lot of posts here and I'm excited to start trying out these ROM's. If not just a little anxious my first time too
I personally wait 10 minutes before I do ANYTHING else with the phone. I don't think it'll hurt it if you flash them before you boot for the first time but I wait. Just to be safe
Sent from my SGH-T989 using XDA
P.s. warfare is a beast
Sent from my SGH-T989 using XDA
hiz99 said:
I personally wait 10 minutes before I do ANYTHING else with the phone. I don't think it'll hurt it if you flash them before you boot for the first time but I wait. Just to be safe
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Flash rom, flash updates/themds and reboot, ignore the n00bs, flashing a theme for the rom replaces apps like SYSTEMUI and framework, wont cause issues and actually a good idea..
At above, why double post for that? n00b..
doug36 said:
Flash rom, flash updates/themds and reboot, ignore the n00bs, flashing a theme for the rom replaces apps like SYSTEMUI and framework, wont cause issues and actually a good idea..
At above, why double post for that? n00b..
Click to expand...
Click to collapse
He was actually right Mr.Doug
You run the risk of a bootloop if u flash a theme or u run the risk of unlimited forcecloses at boot.
Its like this.
Wipe
Flash Tom
Fix perms
Reboot and let the system settle
Then flash extras.
M&S
Master&Slave™ said:
He was actually right Mr.Doug
You run the risk of a bootloop if u flash a theme or u run the risk of unlimited forcecloses at boot.
Its like this.
Wipe
Flash Tom
Fix perms
Reboot and let the system settle
Then flash extras.
M&S
Click to expand...
Click to collapse
I hope Tom likes whatever you're flashing him.
But yeah you need the ROM to settle with the original files first. Why? Our phones are stubborn *****es.
Sent from my SGH-T989 using xda premium
Teo032 said:
But yeah you need the ROM to settle with the original files first. Why? Our phones are stubborn *****es.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
^That's funny right there lol
Thanks! That's what I needed to know. Flashing tonight after work... Can't wait now!
Sent from my SGH-T989 using Tapatalk
Weird, I usually always end up having to reflash some part of the ui when I do a new build, I've never had issues..
Only issue I got this time around (was a fresh flash via CWM and reflash updated framework and systemUI, aswell as additional stock apps I forgot to put into build. Such as keis and a few others..) is simply my screencaptureservice.apk didnt compile right, and only mod I did was changing directory, which I've done before xD never had issues just flashin an update after installing
doug36 said:
Flash rom, flash updates/themds and reboot, ignore the n00bs, flashing a theme for the rom replaces apps like SYSTEMUI and framework, wont cause issues and actually a good idea..
At above, why double post for that? n00b..
Click to expand...
Click to collapse
Yeah solo...you're the noob
Sent from my SGH-T989 using XDA
doug36 said:
Weird, I usually always end up having to reflash some part of the ui when I do a new build, I've never had issues..
Only issue I got this time around (was a fresh flash via CWM and reflash updated framework and systemUI, aswell as additional stock apps I forgot to put into build. Such as keis and a few others..) is simply my screencaptureservice.apk didnt compile right, and only mod I did was changing directory, which I've done before xD never had issues just flashin an update after installing
Click to expand...
Click to collapse
yeah there are times when something breaks or it just goes into bootloop, especially if the ROM is using a different launcher or something.
one time I was missing my status bar lol. It doesn't happen much on this device, but it did once. However, it happens a lot in other devices.
removal of moderated material
Your method of flashing may work but its not the ideal way. If you flash a new rom that way and have issues you will not be able to figure out the root cause. Also its not a good idea to keep calling some one a noob for a simple reply of what they suggest. If I see it again from you, you will be reported. Its this kind of attitude that's bringing down a community that's supposed to be helpful and respectful to everyone new or not.
Even though he called you one back the point is you started it.
Alright....so alittle history. kc_exactly is to blame and to thank for this. He just got me thinking. Especially with people starting to test the JB port from houstonn. Which only flashes with CWM.
Disclaimer: You do this at your own risk!! Can't blame anybody but yourself if it messes things up!
I installed sk8erwitskil's Touch CWM 6.0.2.7 v14.4.7 from the ATT forums here. http://forum.xda-developers.com/showpost.php?p=34567118&postcount=1.
I wanted to see if it would work as kc had said in a post earlier. And it did and does!!! CWM backup works using .tar. I haven't tried dedup yet.
So what's the purpose of this post you ask? Well, from what I've found out so far, we can install CWM, create a backup using .tar which is default, and restore with it. In "mount and storage" I formated system, data, cache. In advanced, I formated dalvic cache. Pretty much wiping out the phone and it restored just fine. Actually 4 times so far.
So, and again, part of this has been said by kc_exactly, if you keep TWRP, AND CWM6027 recoveries, your ROM of choice, and backups in both TWRP and CWM on your Internal storage you'll be able to bounce back and forth testing the JB port or whatever else will require CWM.
I've done this multiple times now and it's worked everytime!!!
Make a TWRP backup
Install CWM 6027, reboot to system
reboot to recovery and make a CWM backup using .tar
That's it!!
Now each time you want to use a different recovery, just install it, reboot to recovery and restore your backups.
Maybe this is old news, or even a "No sh*t Sherlock" thing. But our CWM had too many issues, and I'm really liking sk8erwitskil's Touch version. And it seems to be working well. I was in CWM for at least 10min straight and it never got hot.
It does have somewhat of a learning curve, so make sure you read sk8's instuctions on the first 2 posts.
Re: CWM6027Touch from ATT forum
engine95 said:
Alright....so alittle history. kc_exactly is to blame and to thank for this. He just got me thinking. Especially with people starting to test the JB port from houstonn. Which only flashes with CWM.
Disclaimer: You do this at your own risk!! Can't blame anybody but yourself if it messes things up!
I installed sk8erwitskil's Touch CWM 6.0.2.7 v14.4.7 from the ATT forums here. http://forum.xda-developers.com/showpost.php?p=34567118&postcount=1.
I wanted to see if it would work as kc had said in a post earlier. And it did and does!!! CWM backup works using .tar. I haven't tried dedup yet.
So what's the purpose of this post you ask? Well, from what I've found out so far, we can install CWM, create a backup using .tar which is default, and restore with it. In "mount and storage" I formated system, data, cache. In advanced, I formated dalvic cache. Pretty much wiping out the phone and it restored just fine. Actually 4 times so far.
So, and again, part of this has been said by kc_exactly, if you keep TWRP, AND CWM6027 recoveries, your ROM of choice, and backups in both TWRP and CWM on your Internal storage you'll be able to bounce back and forth testing the JB port or whatever else will require CWM.
I've done this multiple times now and it's worked everytime!!!
Make a TWRP backup
Install CWM 6027, reboot to system
reboot to recovery and make a CWM backup using .tar
That's it!!
Now each time you want to use a different recovery, just install it, reboot to recovery and restore your backups.
Maybe this is old news, or even a "No sh*t Sherlock" thing. But our CWM had too many issues, and I'm really liking sk8erwitskil's Touch version. And it seems to be working well. I was in CWM for at least 10min straight and it never got hot.
It does have somewhat of a learning curve, so make sure you read sk8's instuctions on the first 2 posts.
Click to expand...
Click to collapse
This looks promising. Thanks for "guinea pigging" it.
Sent from my LG-LS970 using xda app-developers app
Xiutehcuhtli said:
This looks promising. Thanks for "guinea pigging" it.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'm glad I tried it too!
Right now I'm in flashaholics heaven. I have a TWRP ICS backup, a CWM ICS backup, and a CWM JELLYBEAN backup!! I'm able to play with whatever blows up my skirt. OK pants.
To all the *****y posts about this phone not going anywhere? Stay away!! We have a hellava DEV crew that is moving right along. And I'm lovin it!!!
engine95 said:
Thanks. I'm glad I tried it too!
Right now I'm in flashaholics heaven. I have a TWRP ICS backup, a CWM ICS backup, and a CWM JELLYBEAN backup!! I'm able to play with whatever blows up my skirt. OK pants.
To all the *****y posts about this phone not going anywhere? Stay away!! We have a hellava DEV crew that is moving right along. And I'm lovin it!!!
Click to expand...
Click to collapse
what i did was after i flashed jelly bean and restored my apps and stuff, i re installed twrp and made a backup so i never have to switch from twrp to cwm.
Re: CWM6027Touch from ATT forum
But don't we need to use CWM to flash and/or update houstonn updates?
Sent from my LG-LS970 using xda premium
Thanks for the info, this works great on my OG!
roguejam said:
Thanks for the info, this works great on my OG!
Click to expand...
Click to collapse
Works Great!!!
engine95 said:
But don't we need to use CWM to flash and/or update houstonn updates?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
If I'm reading the thread correctly, the idea is that you make a backup including the recovery so you can switch back and forth at will.
VoluntaryMan said:
If I'm reading the thread correctly, the idea is that you make a backup including the recovery so you can switch back and forth at will.
Click to expand...
Click to collapse
I'm not sure if this is a question, or a comment? So I'll take it as a question.
You are correct. It's been working great for me so far. I'll bet I've restored over 20 times now and it's worked great. I've put it through all its paces and it's worked fine. I've tested and played with houstonn JB and I gotta say I really like JB!
So from what I can tell, we can use this recovery, and do whatever we want. Play with JB for a while, then switch back to ICS.
Sent from my LG-LS970 using xda premium
engine95 said:
I'm not sure if this is a question, or a comment? So I'll take it as a question.
Click to expand...
Click to collapse
I was trying to answer your question. Looks like you figured it out already though.
VoluntaryMan said:
I was trying to answer your question. Looks like you figured it out already though.
Click to expand...
Click to collapse
My bad then. Well, I guess I gave everybody an update.
Sent from my LG-LS970 using xda premium
wifi not working
i just flash it twice on lg e970 at&t....my wifi is not working any help................
gomzy85 said:
i just flash it twice on lg e970 at&t....my wifi is not working any help................
Click to expand...
Click to collapse
This is an older recovery. And the wifi has to do with the ROM, more than likely. Go to the TWRP thread or the root guide, under Working Recoveries. There you'll find the newest recoveries. KK included.
Then go to the ROM thread that you flashed and your answer is probably there. If not, ask there.
Sent from my LG-LS970 using XDA Premium 4 mobile app