yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Bionic] RandomPooka:
I'm almost tempted to try it tonight. Except for the part where I'm happy where my phone is at the moment, it's at like 50% charge, and it needs to be fully charged by 4:30 AM for work and an hour or more going through all this with minimum time actually CHARGING is not going to get me there in time for work tomorrow :(
[Motorola Droid Bionic] crobs808:
To each their own. The manual creation of the stand-alone battery charger cable took all if 5 minutes.
[Motorola Droid Bionic] diesel73turbo:
Hey guys, i am havng a problem going back to 902 from 2231. I was on 905 eclipse for a while and then took the 2231 when it leaked. I finally had time to mess with it today and was going to go to either 2233 or 229 but after FXZing I am stuck at the moto screen. I used pathsaver for linux and everything flashes and writes ok during the FXZ and everything loads up ok when it boots in to recovery at the end, it just hangs at the moto screen at the end (i left it there for well over 20min before pulliing the batt). My battery was full at the start as well. I am going to try again tomorrow on a windows machine with RSD to see if that makes a difference. Any ideas? or did i miss something incredibly obvious? Thanks in advance
[Motorola Droid Bionic] Saint Isaiah:
Have you tried going into stock recovery and wiping the data/cache?
[Motorola Droid Bionic] diesel73turbo:
Just tried it and it doesnt seem to have made a difference. I dont get it...its the same file i used when i went from 905 back to 902 to get back to stock before so i know it worked.
[Motorola Droid Bionic] RandomPooka:
I had problems using an FXZ if I didn't start in Fastboot mode or one of those similar modes on the phone.
[Motorola Droid Bionic] Underwater Mike:
I had exactly the same issue. I'd flashed in fastboot several times with no problem then got stuck. Re-flashing via RSD solved it. Have you tried that?
[Motorola Droid Bionic] SamuriHL:
It seems to work well. Reverts to 902 temporarily, and then prompts you when and how to manually boot into recovery to apply 905 and the latest ics update, wipe the cache, reboot, apply root if wanted, done. I tried to make it as easy and painless as possible.
[Motorola Droid Bionic] crobs808:
Again, do the system format and all wipes BEFORE installing any ZIPs, in stock recovery or CWR/Safestrap.

If you install the ZIPs before wiping you are basically combining systems. This is what causes people problems (data drops, UI glitches, etc.)

Do not do ANY wiped after installing a ZIP. It's too late at that point.
[Motorola Droid Bionic] fastpakr:
You can wipe the cache at -any- time in the process. Installing a zip doesn't affect the cache in any way.
[Motorola Droid Bionic] SamuriHL:
That is a HEAVILY disputed point. We've asked rom developers about this and they say it matters not when you wipe the cache as long as it's done before you reboot. Before the zip update or after has not made one difference at all for me on my Xoom with Team EOS. And I've been updating it since January with no factory wipe. I have 0 problems with it. As long as the cache partition is wiped before you reboot into the phone, it's fine.
[Motorola Droid Bionic] nite001:
ics

well got 229 ics up and running with root tried putting jb on samsung galaxy tab 2

but it came back with a status 7 and system/build.prop no such file will need to dig deeper lol
[Motorola Droid Bionic] crobs808:
Cache if not the important one. It is really the format of the system that must be done before, I just lump in everything else since you're already in the menus doing it so why not do them all.

System must be done before, that is undisputed. Do everything else afterwards if you really want to split up the process, not sure why though.
[Motorola Droid Bionic] SamuriHL:
Huh? :confused: The script I posted flashes all the partitions in the same order that they're done using the RSD Lite FXZ. That includes system. So I really don't get the point?
[Motorola Droid Bionic] diesel73turbo:
That did it. Thanks for the help guys. Apparently if you're coming back from an ics you have to flash with RSD on a windows machine. I even used the same xml file so its all RSD.
[Motorola Droid Bionic] crobs808:
I don't think I was addressing you, just users who are still learning this process - they need to know to format the system first.
[Motorola Droid Bionic] SamuriHL:
Ok. Yea, users who are learning are advised to look at the work of people like P3Droid, timmy10shoes, and many others who are leaders in our community. That's how I learned. When I wrote the script, I followed the order of the FXZ so as to keep as much as possible the same. I started with the 902 pathsaver script as a base and worked from there. You can learn a LOT by looking at what others have done.

Just for the record, you don't want to "format" system ever. You may want to flash it, but, completely removing it will quickly create a non-working phone. I realize that's completely nitpicking, but, I don't want people to get the wrong idea. The system partition is quite important. :)
[Motorola Droid Bionic] crobs808:
No, literally you DO want to format the system. In Safestrap you select 'Mounts and storage' then select 'format /system'. Then you wipe data/cache and dalvik then flash your desired ROM of choice or go into stock recovery to flash this leak.

That's what the process has been for over a year on this device, there should be no confusion. It's the same with CWM Recovery also.
[Motorola Droid Bionic] SamuriHL:
I can assure you I've never formatted the system. If you're referring to a factory reset, that's different. If you're not, then I really truly have no idea what you're referring to and am confused.

EDIT: Just went into recovery. I see the option you're referring to now, but, I have personally NEVER done that and I never have issues. Very odd. This is the first time I've ever heard that before.
[Motorola Droid Bionic] crobs808:
You have to do that when moving back and forth between GB and ICS Roms. If you are just now moving from GB to ICS then it makes sense you haven't heard of it but a lot of us have been flashing unofficial ICS roms since the beginning of this year.

Hmm, I didn't realize there was this much confusion on the process - guess it's time to create another 'How-To' guide.
[Motorola Droid Bionic] SamuriHL:
Not something I did on my Xoom, either, and I've been rocking Team EOS on that since January. Very interesting. Thanks for the info!
[Motorola Droid Bionic] crobs808:
Each device requires much different steps than the others. Even among the Motorola devices the steps are very different.
[Motorola Droid Bionic] SamuriHL:
Good to know. Question though. If you're flashing the full system.img would that make formatting it unnecessary in this case? Note I'm not doing any custom roms....just the stock leaked ICS builds from Moto. I'm flashing system.img from 902 FXZ so it should return it to full stock.
[Motorola Droid Bionic] RandomPooka:
No point in assuming a ROM's install script formats /system for you. Yes, the majority likely will. But I've been caught doing that. Bad juju
[Motorola Droid Bionic] SamuriHL:
Yea but like I said, I haven't installed custom roms on the bionic. I think formatting system only applies to custom roms not official moto updates.
[Motorola Droid Bionic] RandomPooka:
Updating to the ICS leak is dependent on being on 905, as it's a patch, not a ROM proper. Wiping /system would be disastrous. Same for the 902->905 upgrade. That's like 50mb and is not a complete system.
[Motorola Droid Bionic] SamuriHL:
Exactly. Which explains why I'd never done it as I don't use custom roms on the bionic. At least not yet.
[Motorola Droid Bionic] TacoRosado:
Found my mistake!!!

I posted a couple days ago about a problem I had FXZing back to .902 from .2233. Had the same error occur today coming back from .229 to try the .230 leak. After a lot of research i found out it was just the usb port I was using. So just wanted to clear it up and hopefully help others if anyone is having the same problem.
[Motorola Droid Bionic] crobs808:
The system format is obviously not done for upgrades...goodness. I'll definitely be creating a new guide for this.

And yes, if you have a rom that installs the system.img, you still have to format the system beforehand, otherwise you are just combining the old system with the new system. Think of the system.img file like a zip file. It will extract to your phone's local storage overwriting any system apps and files that are in there that happen to have the same name but there will be a handful of files that don't get overwritten and still present after the flash.

Tutorial to come shortly.
[Motorola Droid Bionic] RandomPooka:
My front panel usb ports are 1.1 and they are not reliable for much of anything apart from collecting dust bunnies. Use the ones on the back for sure! Can't believe I never thought to suggest that.

A lot of custom ROMs format /system before installing on some devices. Haven't built one yet for this device, so I can't guess whether it's normal for bionic ROMs or not. I agree, though. Good habit to format /system first, just in case the install script doesn't. Worst case is that your format was redundant. But it only takes a few seconds
[Motorola Droid Bionic] Vnvjeep:
email lags horribly

I upgraded to 2233 from 905 stock... the upgrade itself took nearly 5hrs. But once it was done, it was glorious. Except... for the email app. I have 4 different kinds of Exchange accounts... 2010, 2007, 2003 and live.edu. Each one of them lags HORRIBLY. It can take anywhere from 5-10sec just to open up an email... or the same amount of time to see my email list.

I decided to dump the cache/data for the email app, and start over, hoping that the upgrade pooched something with it's db. No dice. It still lags just as bad as ever. I changed it from push to checking every 15mins since push no longer seemed to work effectively either.

Other than email, everything else seems to behave pretty well. But I *have* to have a responsive email app, else it feels like I'm losing years off my life.

Anyone have any ideas? I'm thinking of going the FXZ 902->905 OTA and blowing everything away, and then upgrading to 230... as a last resort.
[Motorola Droid Bionic] SamuriHL:
http://www.droidforums.net/forum/motorola-droid-bionic/214902-downgrade-902-no-app-data-loss.html

230 does seem to fix the email issues that people had been having.
[Motorola Droid Bionic] crobs808:
You should be using K9 for POP/IMAP email and Touchdown for Exchange. The built-in email apps are just bare minimum efforts to have an email client, but pretty worthless in any ROM (e.g. no ability to search emails, no collaboration tools for Exchange, etc.)
[Motorola Droid Bionic] RandomPooka:
I will admit that I like that the stock email app on blur allows for push notifications with yahoo mail accounts. Then again, it's only personal account and I haven't ever used a search function in any mail client in the last 20+ years
[Motorola Droid Bionic] Vnvjeep:
I've tried touchdown, but it just doesn't do anything for me... and... it's UGLY. Takes me longer to do anything on there. :) I'm actually perfectly happy with the capabilities of the regular email client. And yes, you can actually search through your email... even on Gingerbread. I don't use any POP/IMAP accounts... I live Exchange.
[Motorola Droid Bionic] crobs808:
To each their own. I've never had a phone with a built-in email app that I liked. The only built-in app that I use is Maps/Navigation I guess, and that is even arguably a Market download.
[Motorola Droid Bionic] Vnvjeep:
On 230 now...

Well, I FXZ'd to 902, OTA'd to 905, and threw 230 on there... Can't say I'm impressed yet. Email has gotten "slightly" better, but it still experiences some major delays there. Definitely not snappy like 905 was. I'm also seeing alot of timeouts happening when flipping between apps, or waiting for apps to function... but that was happening on 2233 as well. Don't think this is the final product yet... let's hope not. Well, I guess I'm off to the 230 thread so I can start whining over there... :)

Thanks for your help and input...
[Motorola Droid Bionic] Underwater Mike:
FYI, I'm seeing a lot of lag in screen response on .230, especially on close buttons and the like.
[Motorola Droid Bionic] SamuriHL:
Give it a day or two to settle down a bit. I've had no problems with 230 and it's been really good for me and a lot of others. I do believe this will end up being OTA unless there are any major bugs found. Sadly, this is a better release than the RAZR people seem to have gotten so I think we'll be seeing it go live by the second week of August.
[Motorola Droid Bionic] crobs808:
Wasn't able to get WiFi connected to any network on 2231 and now on 2330 and still no luck. It asks for the WEP/WPA key then saves the network but never connects. I then manually connect to the network and it does nothing. I FZX'd to 902, upgraded to 905 via recovery then upgraded to 2330.
[Motorola Droid Bionic] RandomPooka:
Not having any wifi issues with 232. Went to it from 229, though so I can't say for your leak
[Motorola Droid Bionic] urphonesux:
We're getting there motorola!

Only issue I am having right now is apps are exiting webtop mode even though Im not connected to the lapdock. It's new though because an actual screen is popping up before i open a new app that looks like the android is updating screen. This only happens after i disconnect from the lapdock and a soft reset :crying: fixes it
[Motorola Droid Bionic] Underwater Mike:
I had the same issue, but after a reboot and cache wipe, everything started to work (even though I wiped /cache when updating). Dunno if that will help you or not -- I assume you tried already?

---------- Post added at 11:20 AM ---------- Previous post was at 11:19 AM ----------

Can anyone tell me what evil will manifest if I uninstall the Backup Assistant (which I never use). Is there some reason people keep it installed? For example, does some useful bit of functionality depend on its presence?
[Motorola Droid Bionic] RandomPooka:
Basically, there's a risk involved in removing any blur components. Try freezing all 3 (?) related entries in Titanium for a few days and wait for ripples and waves.

I want to say there's the main interface apk, a background service apk, and an authentication apk? Something along those lines
[Motorola Droid Bionic] RandomPooka:
It's obviously not integral to ICS itself, but other motorola stuff that is tied to the core framework may require those extra "useless" bits to check in at boot or at certain intervals
[Motorola Droid Bionic] Underwater Mike:
Yes, there are three. I just froze all of them and am waiting for the trans-dimensional tunnel to spawn down in my basement. :D
[Motorola Droid Bionic] RandomPooka:
Rofl! If you get one, I'm doing it too
[Motorola Droid Bionic] crobs808:
Reference to Sliders? Impressive.
[Motorola Droid Bionic] RandomPooka:
That was underwater Mike, not me. I don't know the reference, sorry
[Motorola Droid Bionic] :
It is the one thing I love about my Rezound, being able to flash leak over leak over leak. Getting a bionic for my fiance in a few days and have to figure out what I am going to do with all these leaks.
[Motorola Droid Bionic] SamuriHL:
The bionic community has been awesome. The fact that they tested going back to 902 rather quickly and found that it was possible completely put my fears at ease. In fact, I've released a script to help go between leaks without losing data. There was also another process that was possible that I was unaware of when I wrote that which could have helped people who were on leaks move forward. I guess it helps to be cautious but also helps to be informed. :D If you want to play with the ICS leaks, I recommend my script. The first leak you install won't need anything other than being on 905. Currently 6.7.232 is the latest ICS leak. You can sideload that right on top of 905 and you'll be good to go. If a new leak comes, then you'll wanna maybe look into my script. It's been a pretty fun experience playing with these leaks.
[Motorola Droid Bionic] texassax:
I followed these steps on my original device and it worked great (thanks!). I just had to get a replacement device because my microUSB port was broken and now I'm having problems. since it's a stock device I didn't need to worry about FXZing back to stock, so I ran the OTA 905 update, then ran the ISC update. now upon boot it says, "AP Fastboot Flash Mode (S) (Boot Failure)".

I thought I would just FXZ back to 902, but when I select the FXZ you attached RSD says, "Please check input file. Either XML format is wrong or image files associated with it are missing."

Unfortunately I have to leave for work now. Any ideas for me to try when I get back home?
[Motorola Droid Bionic] :
SamuriHL,

I was wondering if you could point me in the direction of your script. I looked around the forums a bit and could not find a thread for it.

Thanks,

Anarchy
[Motorola Droid Bionic] SamuriHL:
http://www.droidforums.net/forum/motorola-droid-bionic/214902-downgrade-902-no-app-data-loss.html

Enjoy!
[Motorola Droid Bionic] amageus:
You should be able to use SamuraiHL's script above to fix your issue. It sounds like something borked when you did your upgrade. As far as RSD the FXZ file might need to be unzipped or something as it was pointed out in several posts or another thread. But you should be able to use the same files from Samurai's script or just use his script. It's pretty easy to use. One thing I want to point out is that when it's loading the webtop images into memory it would look like it's hanging but its not. At least that's what I had assumed on this POS computer of mine at work. Results will vary with others but let the script do it's work and you should be good to go.
[Motorola Droid Bionic] texassax:
I can't run the script if I can't boot the phone. unless someone has a handy link for another modified FXZ to prevent data loss, I guess I'll just use an unmodified one.
[Motorola Droid Bionic] SamuriHL:
You CAN but it's not straight forward. If you're in an unbooting situation, I would boot into fastboot manually and use RSD to do the full FXZ. There is one that will keep your data.

http://www.droidforums.net/forum/mo...-5-893-fxz-901-902-compatible-902-update.html

Use that one.
[Motorola Droid Bionic] amageus:
i forgot that Samurai's script tries to push the 2 files. I edited his runme.bat to exclude pushing the 2 files and get straight to moto-fastboot. Best of luck on FXZ'ing without data loss.
[Motorola Droid Bionic] SamuriHL:
Why in god's name did you edit my script rather than just renaming the updates dir???? :)
[Motorola Droid Bionic] RandomPooka:
Be sure to remove the lines in your xml referring to emmc before you use RSD lite and send your phone back to 902. There's no reason to format the internal sd card that I can think of
[Motorola Droid Bionic] SamuriHL:
The one I linked to I believe has that removed but it never hurts do double check. If you have my full zip file for the House of Bionic, I have a modified XML file in there that you can use, as well. It's got a nodataloss extension. Just rename the original xml and take the nodataloss off and use that in RSD.
[Motorola Droid Bionic] RandomPooka:
You don't even need to rename the .xml file. I've got two .xml files in the same directory with similar names. One has SaveSDCard appended to it, very creative :)

I saved the original .xml just in case I ever need to go all the way stock for a sale or whatever, and it's a good idea to have a written record of the mount points, just in case. It's not like having both .xml files takes more than a few kb of disk space, anyway
[Motorola Droid Bionic] texassax:
if I flash .230 can I restore a nandroid backup from .2233?
[Motorola Droid Bionic] SamuriHL:
People on rootzwiki have done so. I'd be cautious with that. It could be fine or it could go horribly wrong. :)
[Motorola Droid Bionic] texassax:
haha, sounds like I'll do a little extra work, flash .230 (since I'm skeptical of trying .2233 again), and just restore my crap via TB.
[Motorola Droid Bionic] SamuriHL:
TB is worse. And you should be using 232, not 230. (For the record, 4 digits does not make 2233 newer....it's really 223.3). If you use TB to restore your data, do NOT restore system data with it or you will encounter issues. Apps and app data only.
[Motorola Droid Bionic] texassax:
sorry, I didn't mean system data, just apps and their data. I planned on flashing .230 because it was newer and 2233 was mean to me. I might as well do .232, though, I suppose.
[Motorola Droid Bionic] homeeey:
That is not a FXZ file that he posted, just the xml file that is used within the full package. Note his file is only 2.1K, not large enough for a full FXZ

Just get a full FXZ file and try again.

I had the exact problem coming from stock .905 with the boot failure. Tried going back to .905 twice and same problem. A Factory Reset before booting into ICS the first time was the fix for me. Clearing cache might have worked as well, but never tried. Samurai's method has you do a clear cache before first boot, so that may have been all I needed.
[Motorola Droid Bionic] SamuriHL:
I would at this point. Any reason you're not using my script?
[Motorola Droid Bionic] texassax:
since I was already running stock 905 I thought it wouldn't be helpful since it would downgrade me. I did use your FXZ to flash without data loss and I certainly will use your script for future leaks. thank you :)
[Motorola Droid Bionic] SamuriHL:
Ah, ok. So you just need to put the 232 update on your sdcard-ext and flash it. My new script can still help with that, too. It has an option to push the updates to your phone for you so you can then manually flash them in recovery. Easy enough to push it to the phone by hand, too.
[Motorola Droid Bionic] RandomPooka:
Do an advanced restore of data only, and you SHOULD be fine. If not, you can always wipe data and set it up the long way.
[Motorola Droid Bionic] texassax:
so I've successfully flashed .232. I'm trying to run razrs edge to root, and it's hanging up on "waiting for device", won't make past that after waiting for several minutes. USB debugging is enabled, I have the drivers installed, and I've tried it on both mass storage and MTP.
[Motorola Droid Bionic] SamuriHL:
You're not the only one that's happened to. I don't think it ever got fixed on the other person's phone. NO IDEA what causes that issue. We weren't able to figure it out. There's a long, painful way to get around this but it requires wiping the phone. FXZ back to 902, take the 905 update, and motofail root the device. Then install voodoo rootkeeper and protect root, then do the 232 update and you should be able to restore root in voodoo rootkeeper. Long, painful, but, hopefully will work.
[Motorola Droid Bionic] da93benz190:
Updating

Been out of the phone scene for awhile and been meaning to give ICS a try. I have been reading over the last several hours on updating to this ICS leak but I wanted to confirm a few things so if anyone can help I would appreciate it.

My Bionic came with 893 and I rooted it, after months and months I decided to update it but it would never take the OTA update due to rooting and system file editing, Moto Support told me I was SOL and had to send it in however I was fortunately able to find some of petes tools to FXZ back to .893 then update to .902, 903, then eventually .905

Right now I am on OTA .905 and rooted via motofail (I think). I have installed Voodoo OTA RootKeeper and enabled it, unfroze all apps in TB, and made a FULL .905 backup. Am I missing anything else or am I OK to apply this ICS update or should I follow the instructions @ http://xdaforums.com/showthread.php?t=1771993 ???