Related
I am pretty sure but just want to check, if i upgrade from cm6 to cm7 will i lose all data on my phone? Also if i get to cm7 and do updates will those also erase data?
1. Don't post questions in this section
2. You can upgrade from cm6 to cm7 without wiping, and will retain all your data. However if you encounter problems or force close, you might have to, but I've seen a lot of people upgrade without wiping and it went fine.
3. "If i get to cm7 and do updates will those also erase data" I have no idea what you're asking.
I think he means will flashing CM7 nightly builds over the top of each other cause data loss? In which case, no.
i didnt see him mention nightlies anywhere. but to answer his question, you can just do a regular upgrade without losing any data. i would do a nand backup before just in case, and if you DO have any problems you can restore it.
but i had no problems upgrading cyanogen rom. as long as you stay within the same ROM, and move from an older to newer version, its ok. but you can upgrade from cyan 2.2 to stock 2.3, for example. full wipe is needed there.
Yesterday i flashed if i remember the 223 leak. I flashed from 905, rooted with razor ics root. I went in to sqlite and changed the setting to get the free hotspot and than rebooted. Now on my top banner the wifi icon and my signal icon stay gray! They never got to blue! I have data service but the are always gray. Also later my signal strength went noticeably lower than before i flashed! Any help would be great! ...... also i just noticed that my browser is talking! Had chrome installed, couldn't find anything in the settings so i uninstalled and went to reinstall. Play store says that NOW its not compatible with my device! And now my stock browser is talking to me! PLEASE HELP!!!!!!
Sent from my DROID BIONIC using xda app-developers app
One thing at a tine.
Browser talking - check you're accessibility settings, see if Talkback is enabled.
For the GNow, that does not come with the ICS leaks. Either you installed an unofficial leak, or you installed GNow before the leak, or you installed it after the leak. There is a thread in XDA that details how to get GNow working in ICS.
For the sqlite mod, change the string back. Foxfi is free, doesn't require root, and works.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Thanks, I FXZed back and reloaded everything no sqlite no root and everything seems good! Still lost data for a while last night but l don't have great service at home! Might root later today, we'll see!
Sent from my DROID BIONIC using xda app-developers app
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
bhp117 said:
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
Click to expand...
Click to collapse
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
What? We have a locked boot loader... can't run .235 on one side and .905 on the other lol
What he said was correct.. you cannot use RSD lite to fxz back to .902/.905 with .235 so unless you're a fool don't make the move... 232 is great
Finally Iced Out Legitimately... Bionic is back
You cannot go back to fully stock Gingerbread anything once you flash .235 so for the sake of newer users being thrown off the upgrade path and not being able to FXZ back to .905 we all should just leave it at that.
cnorman76 said:
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
I think you've gotten the gist of the info, but I'll reiterate.
You have to be on .905 to flash any of the current ICS leaks (and there is a 99% chance of that being true with any future leaks / soak tests / final OTA b/c .905 is the current official OS version for the BIONIC.
You can flash .235 off of .905, but once you are in .235, you cannot restore your phone to .905 via FXZ, and you cannot try to fool the system with a simple Nandroid backup of .905 that you restore over .235. The reason is that the update script also looks to patch several things.
First of all, no update script ever includes the boot.img of the version that is being installed. It includes a patch file that requires you to have either the boot.img of the system that you are coming from, or the system that you are going to. Any other version and it throws up an error and does not allow the update to continue. IOW, if, say, leak .241 comes out, and you're on .235, you have no way to getting .241 without using a method to make the .241 kernel. You cannot flash the .905 kernel onto a .235 system - it trips eFuse and bricks the phone. You have no .241 kernel to install b/c, as I said, the update only includes a patch file, not the full kernel.
Second, even provide that you pass that (which in theory you might as you are on a .235 leak with only .905 /system restored from a Nandroid backup, and if the new leak uses the exact same kernel you'll pass), it also verifies every file in /system that it is going to patch, along with every file in /preinstall that you are going to patch. Restoring that Nandroid backup does wonders for having the .905 /system on your phone, but the current leak you are on has already patched several files in /preinstall, so those signatures will not match, and you'll fail the verification step, and ultimately the update will fail.
For the record, a typical FXZ flashes 17 different partitions on our phones. Nandroid backups on the BIONIC typically can only make backups of 3-4 of those partitions. We have figured out ways to grab a few more of them, but we are still stuck at grabbing a couple of them, and there are 4-5 that we cannot grab from our phones at all.
Since the folks with RAZRs went through something very similar in May and June, mattlgroff figured out a way to fool the update into thinking you have all the components correct in place that need to be there, and the update proceeds. Thus far, after bricking my phone trying to FXZ back to .905 / .902, I used a script to get back on .235, then verified that the move to reinstall the .235 leak works. If another leak is found, then I can test the second part of the script, that which allows new leaks to be installed. The script does not allow any older ICS leak to be installed, and currently there is no way to go back to a previous leak nor a previous GB stock FXZ at all. Even if we had a .223X ICS FXZ or a .22X ICS FXZ or a .230/.232 FXZ, they would not work on a phone that has been updated to .235.
That is why we're saying hold off unless you're 100% positive you're willing to accept the risk - this is way beyond the risk associated with rooting your phone. If Motorola makes the next leak force the phone to have components from .905 that we cannot flash into a .235 upgraded phone, I (and several others that have taken the plunge) might be permanently stuck on .235 until an FXZ for a version of ICS higher than or equal to .235 is released. And that typically takes 6-8 weeks.
HTH
crobs808 said:
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
Click to expand...
Click to collapse
Make a guide if you will and state the proper steps to do so
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
dblkspecial said:
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i noticed that the other day when I got a text while my screen was locked. I naturally pulled the notification bar down and noticed that I didn't unlock my phone at first. Tried it just now and it's unlocking without swiping to unlock. My home button doesn't do anything howerver.
I have been on the .2233 ICS Leak for a couple of weeks now and it is pretty good but wanted to get up to .232 now (I know, stay away from .235)
However I went to flash the .232 and I got an error - do I need to do this in order .2233 then .229 and so on??
I am rooted, any other details?
devilcub52 said:
I have been on the .2233 ICS Leak for a couple of weeks now and it is pretty good but wanted to get up to .232 now (I know, stay away from .235)
However I went to flash the .232 and I got an error - do I need to do this in order .2233 then .229 and so on??
I am rooted, any other details?
Click to expand...
Click to collapse
No, you can only install the leaks from .905. See this thread for a way of downgrading to .905 so you can install the new leak without loss of data.
http://www.droidforums.net/forum/motorola-droid-bionic/214902-downgrade-902-no-app-data-loss.html
You can also use my upgrade guide HERE. This WILL delete all your user data though, which in my opinion is the better way to do it so you have a clean system once you get to .232 - nothing lingering around from and old setup. All you have to do is backup files first to your SD card, if they are not already on there.
problems with process com.android.phone!.
it is the only problem apart from dropping DATA on ICS bionic.
I am running LiquidSmoothBLUR and for some reason it seems to just constantly end this process.
It is stuck in a loop and my phone is unusable.
This happens after my second reboot after a new flash, every time. It works fine for a few reboots and then it just constantly crashes.
I don't know what to do.
Stock ICS OTA 2233 works fine, apart from the data problems -- I'm on ATT US.
anyone offer any help? i'm baffled. I've tried repairing permissions but it still doesn't work!
solidus636 said:
problems with process com.android.phone!.
it is the only problem apart from dropping DATA on ICS bionic.
I am running LiquidSmoothBLUR and for some reason it seems to just constantly end this process.
It is stuck in a loop and my phone is unusable.
This happens after my second reboot after a new flash, every time. It works fine for a few reboots and then it just constantly crashes.
I don't know what to do.
Stock ICS OTA 2233 works fine, apart from the data problems -- I'm on ATT US.
anyone offer any help? i'm baffled. I've tried repairing permissions but it still doesn't work!
Click to expand...
Click to collapse
Well if the ICS leak 2233 worked fine and the problem only happens when you apply the LiquidSmoothBLUR rom then I would point at the rom you are trying to install. Something's borked in your installation or perhaps you're trying to load a program that isn't compatible with LiquidSmoothBLUR. Did you make sure to follow the instructions on installing the rom to the dot? Most roms require you to wipe your cache but if you're installing the rom directly on top of the leak without wiping cache you could run into issues. Or perhaps you're one of the few phones that isn't compatible with the new rom. Try downloading a the rom from a different source and reinstalling it.
it's weird. it happens on nearly EVERY single custom ICS rom, has happened on a leak. and yes I am flashing properly, definitely not missing any steps! wipe dalvik and cache, data, format system, then install the rom, and it is from a good source, checked the MD5 checksums, everything ads up!
another question : installing a custom ICS based on a leak ON TOP of 905 would stop me from downgrading, correct? say if i install project rectacle v2 -- a 232 based motoblur rom -- would it stop me from downgrading?
also -- safestrap is only for the leaks, correct?
solidus636 said:
it's weird. it happens on nearly EVERY single custom ICS rom, has happened on a leak. and yes I am flashing properly, definitely not missing any steps! wipe dalvik and cache, data, format system, then install the rom, and it is from a good source, checked the MD5 checksums, everything ads up!
another question : installing a custom ICS based on a leak ON TOP of 905 would stop me from downgrading, correct? say if i install project rectacle v2 -- a 232 based motoblur rom -- would it stop me from downgrading?
also -- safestrap is only for the leaks, correct?
Click to expand...
Click to collapse
I don't think that installing Reticle on top of .905 would even boot up. If it's based on a leak, such as .232, it requires a kernel from one of the leaks to run. If you want to install an ICS ROM on top of .905, you can't use one which was based on a leak. Most of the compatible ones are CM9 based and are either fairly old builds, or specifically say that they can be flashed on the non-leak versions. As for safestrap, there are versions that work with the .905 base, I'm not sure, but I think you need something lower than a 2.x build for that.
[B]droid bionic ota ics not getting notifications, hanging badly slowly deterorating . i am willing and wanting to root or reset safely please help traveling for Christmas and need it to work please[/B]
I am having the same issue. The first time it happened, I lost all audio - music, ringtones, phone calls had no sound from me nor from the other party. Phone was extremely laggy and would freeze up then eventually reboot. I was lucky if I could get 5 minutes of use. Sometimes it would happen immediately after reboot. I did a FDR after ICS update and installed all my apps fresh. Many apps "unfortunately, stop" and I cannot get them to work without another uninstall/reinstall. Fortunately, I had a nandroid backup right after the fdr and reinstallation of all my apps. Restoring back to that point has helped tremendously with everything but the audio issue. My music audio still goes out every day or two, but, can be fixed with a reboot now.
Not sure, but it sounds like the hardware is at fault. If an FXZ won't fix it than, I am sorry to say, your phone's dying and no amount of software will fix it.
Just remember, only the ICS specific FXZ file will work for an ICS phone. Any others will be disastrous.
reflash reflash reflash. fxz i always start from scratch, why beat around the bush
I tried to fxz back to stock using HOB in order to upgrade to ics and it kept failing on the final reboot. I was finally able to update by installing the update from .zip file in recovery mode. I read the HOB instructions numerous times before and after and if I was doing something wrong, I cannot determine what it could have been. There is another thread of someone having the same issue after fxz'ing successfully with other devices, so, sounds like some devices may be problematic.
If an audio driver was corrupted. Would a FDR followed by restoring a nandroid backup potentially fix the problem, or, would the corrupted driver be in the backup file?
Well I bit the bullet and did a nandroid backup, then performed a FDR, then restored the backup (yes, the one I was using while having issues). I have had no sound hangs (used to be daily) or any other issues for 4 days now. Also, battery life seems significantly better, especially when idle. My battery was draining like crazy before. Might be worth a try and you have nothing to lose but a few minutes of your time. I didn't do fxz because I couldn't get my phone to fxz successfully when I wanted to do the ics update.