Didn't want to clutter any other thread but wanted to know about the package and the script in the newest 7/1/11 build.
Does a wipe need to be done?
I installed through the orange CWM and it just recovery looped so I did the 3 finger to recovery and flashed from RED CWM and now it boots to CM7 just fine. Didn't do a wipe.
Should this package be able to be flashed from previous versions and maintain settings or does it require that a wipe be done beforehand?
Can the update script be modified to not convert if it has already been done?
Could the new packages be setup in more of a Delta apply?
Sent from my SCH-I500 using XDA App
The bootloops appears to be an issue with the 7/1 (Build 6) release of CM7 (also an issue with MIUI 1.7.1.3 which is based upon 7/1 CM7).
7/4 (Build 7) CM7 did not do this for me.
So, I wouldn't worry about the bootloop issue anymore.
As for wiping, it is good practice to wipe before installing any rom unless the dev explicitly says it is unnecessary. However, if you did not and you are not having force close issues, then I wouldn't worry about it.
It is my understanding that the filesystem is converted to MTD once and then everytime you reinstall the ROM (or update to a new version), it only checks to see if you are properly converted. JT would be able to answer this question better, this is only what I have observed.
Jp
Well I am happy for a response and will take it at face value since I spent some time setting myself up again.
While I agree with wiping g before an update there really isn't a reason you can't try it first and see if it works or not.
I know that I had to edit a file to get the 7/1 version to install so I was thinking there might be something else in there that could keep from wiping.
Sent from my SCH-I500 using XDA App
Related
I would like to start a thread for things that have been discovered using the gingerbread leak. I can't add to the post in the development section and I dont really think its the right place. I flashed the zip posted in the dev thread. If you wipe the data before flashing then it doesn't work as the set up will try to run and will force close. I found that the super user app force closed quite abit and that it started if open from within the market. I could not get root explorer to work at all. The biggest issue I had was that it would find the sim card im unsure if this bug was intentional to prevent people using the test release. I assume that it is also related to not having a imei number while using this rom.
aaronbutton said:
The biggest issue I had was that it would find the sim card im unsure if this bug was intentional to prevent people using the test release. I assume that it is also related to not having a imei number while using this rom.
Click to expand...
Click to collapse
Well, you got a bad flash. The SIM is working and IMEI is there as well. In fact, pretty much everything seems to be working except it cannot be rooted.
I made a succesfull instalation too, but got the same problem: not root at all. I tried z4root, gingerbreak and superoneclick.
Any other idea on how to root the device?
But Andy said his rom is rooted??
Sent from my LG-P500 using Tapatalk
lekhwani said:
But Andy said his rom is rooted??
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
His rom is rooted I guess there is a gingerbread leak over the Internet which is fake...the OP flashed that leak rom.
I thought you must be aware of the new rom :
http://forum.xda-developers.com/showthread.php?t=1115487
People, if you want to try the russian leak... first, you must flash it via the EXE provided on that site. Otherwise, no GSM!!!
Then, root it like this:
Code:
> adb shell
$ echo 1 > /data/local/lge_adb.conf
Reboot device. Then, you need to remount /system rw, adb push flash_image binary on it and AmonRa recovery image, flash it, reboot to recovery. Now, you can flash it once again with the ZIP from here: http://forum.xda-developers.com/showpost.php?p=14546945&postcount=132)
Now, you will have it rooted. Notes:
- WiFi unstable
- rooting semi-unusable, highly annoying toolbox binary nonsense sticked there by LG which is probably causing this, see http://forum.xda-developers.com/showpost.php?p=14553363&postcount=154 (Edit: confirmed bug by andy)
- generally, not worth the hassle
- to go back, you must use KDZ to restore stock 2.2.x ROM, otherwise, no GSM!!!
Be prepared you will end up messing with emergency mode a couple of times as well. Chances to brick your phone completely. Not for the faint-hearted people really.
I flashed the first zip that was released for recovery, There is normally a force close from the set up app when this is done this way though, but I got around this by not clearing the data and hence it already having the data and the app not running. Maybe flashing the zip with out wiping gave me other errors. Andys zip has got around the set up FC by removing it, it also has root like the one I flashed. I found the wifi stable though for the little time I used it. I think flashing this is a waste of time though I had to do a clean install as my back up wouldn't work zeam ect, FC'd
I don't have any problem at all Just wanna root cause i want to install market enabler.
is all working better then CM7??
Definitly yes.
and this ROM have all features from CM7. Like a special menu, power menu et cetera?
And main question have this ROM flash player?????
In tweeter
@LG_Russia said that this ROM are NOT OFFICIAL release
what do you think about it?
Sure, it´s not official release, cause its TEST release. Its not a final build.
So I currently have Das BAMF 3.0 flashed onto my HTC Thunderbolt. It's working perfectly fine; but say I wasnt to flash another ROM, do I have to wipe my data and cache again via clockwork recovery? (yes I backed my phone up and backed up with titanium back up)
Yes or you will run into issues like me
Sent from my ADR6400L using XDA App
When switching between ROMs from different devs one should always wipe data/cache. Different devs sometimes use different packages for some of the base system apps and the data usually won't "mesh". If you don't wipe, you may not notice a problem initially...but a few day's later you'll be asking "Why does XXXX force close on me?"
Only time you shouldn't have to worry about wiping is if you're flashing nightlies or incremental versions of a rom where not much has changed unless the dev states otherwise in the release post.
Hi,
I'm running CyanogenMod 7 Nightly on an Incredible S. I was on Nightly #68 and today I updated to #89. For the update, I backuped my rom, wiped the Data and Dalvik cashes as is recommended. When the update was done, I had to re-setup my phone from the Android's first boot screens as well reinstall all of my apps and set the options like they were beforehand manually.
I'd like to know if there is a way to make updating roms a little quicker by not having to go through this whole process every time? ie: update rom and still have the phone as it was. I could understand that it may not be possible when going from CM to Virtuous Unity for example. But I'm wondering if I'm missing a step when it comes to simply updating the version of a single rom?
Thanks for any help!
You need a partition with the stable ROM and one to experiment with Nightlies.
lifehacker.com/5826050/how-to-dual-boot-multiple-roms-on-your-android-phone
There is no need to do any wipe going from one nightly to the next.
If you do wipe don't wipe data and you don't have to do set up again.
I do recommend titanium backup for times that you have to do full wipe.
Alright, thanks guys! I should be good to go now!
Sent from my Incredible S using xda premium
I bought device in Europe with German Vodafone 2.3.4/4.5.2A rom.
I get reboots with all roms i tried as well as all custom kernels i tried while these all stuff work on other peoples devices with no issues whatsoever..
Before flashing rom i wipe device with moto-fastboot and cwm like anyone else who is familiarized with the procedure.
I follow all instructions and all but somehow i end up with issues not many people have.
What the hell doing wrong if anything at all?
well this is the wrong section to post in, but have you tried factory resetting from the phone?
Wrong section. It might be that your CPU is getting very hot, so it keeps rebooting.
Tried factory reset off course but i don't have any single issue with stock software. Just with custom ROM's and kernels i want to play with.
Also, I haven't noticed it gets hot that much.
how come it doesn't get hot and reboot that much to other people?
What problems beside the reboots?
Sent from my MB860 using Tapatalk
@schwarzlichtkind, something like widgets missing after reboots, display staying turned on (when talking) when it needs to turn off.. annoying stuff like that..
Which CWM are you using?
Sent from my MB860 using XDA App
when you install a rom do u wipe data, cache, and dalvik cache before flashing the rom?
then do you fix permissions after flashing?
i recommend you do this when you flash a NEW rom, if you are installing an update just wipe cache and dalvik before flashing, then fix permissions after.
latest romracers..i always tend to run latest software, hence the topic
I'm having a similar issue since I got my phone back from repair, no matter what I do faux's kernel 0.2.2 and 0.2.3 cause random reboots and the phone not turning on and heating up. So far 0.2.1 hasn't caused me any problems, hopefully 0.2.1 fixes this and 0.2.4 (in the future) doesn't give problems.
First of all, please post question on the Q&A forum, not on the Android Development one.
Second, please organize your things before asking, and ask a serious question to get a useful answer. Based on your question, 90% of the answers will be guesses.
I reccomend you pick a ROM you like, try it without any custom kernels for a while and see if you get the same reboots. If so, then post a question on the appropriate ROM's discussion thread, don't create a new one just because.
Edit: Post reported btw
Sent from my MB860 using xda premium
Are you sure you fully wiped? data cache and dalvik? if you did you can try using rom manger and official CWM
everytime a flash a rom i use this tool without fail. option 10. then i do the appropriate wipe in recovery. have never had a bad flash. i am anal like that. : )
http://forum.xda-developers.com/showthread.php?t=1314607
I have problems with faux's latest kernels also. Just stick to the stock cm7/blur/MIUI kernels and you should be fine.
Sent from my MB860 using XDA App
try under volting using setcpu. i too had this random reboot issue. but did an undervolt of 100mV (for 1.45GHz). i use faux's 1.45ghz kernel v2.3
have fun!
a possible radio issue i think...
Which radio works better? I have N_01.100.00R
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?