Database Develop

[Q] Recovering from rom ics leak

Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor

Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.

Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?

TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS

First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.

Problems after flashing ICS leak

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.

Older ROM.. Could use assistance getting current!

Hello,
I rooted/flashed my bionic a long time ago, and haven't fiddled with it since..I'm currently using:
ROM - KIN3TX V1.0
Kernel - 2.6.35.7-g686e6
Baseband - CDMA_N_03.1C.57R ltedc_u_05.15.01
System Version 5.8.894.XT875.Verizon.en.US
Version 2.3.4
Could somebody please lend a hand as to what I need to do to move forward with a current rom, or even properly flash back to stock? I'm asking because my 4G stopped working a while ago.. it was fine one day, then stopped. I haven't had time to mess with it, but i've changed sim cards (different phone number) and that didn't resolve the issue either..).. if anybody would be able to lend a hand getting back on the right path, or at least get my 4G working.. it'd be greatly appreciated!!
thanks,
Dennis

Curious about this one myself. A VZ tech rep told me tonight that ICS was officially released for the Bionic and that I should really check for an updated ROM.

You should be able to use the fxz file and get back to stock. There is one for the official .246 ics update.
You shouldn't need to do anything else
Note: this wipes all user data and in rare cases the entire sd card. So back up your stuff. There are a few guides in the Android development section of our forums. (If they have not updated their old .905 gb guide, do everything in their guide except use the [fxz].246 ics file {also in the android development forums})
Sent from my DROID BIONIC using Tapatalk 2

Thank you. I actually tracked down some info and ended up flashing the FXZ 904 update, so I guess that puts me a bit behind.. I'll look up the 294 today.. thanks again!

[Q] Going from 6.7.2233 (June Leaked 4.0.4) to OTA Legit

Hello Everyone!
First of all, please excuse the extreme noobness of this post. I do have a fair amount of knowledge about flashing roms and the like and even returning devices back to factory.... but only with samsung/nexus devices so the concept of a locked bootloader and dealing with that is a bit foreign.
Back in June I flashed/updated my boyfriend's Bionic to version 6.7.2233 (Android 4.0.4) because I didn't believe the device was ever going to actually get an ICS update legit from verizon. It has worked well but now that there is an official OTA update out there for it and the rumor from moto that it may one day be graced with Jelly Bean in some iteration, I would like to get it on a more legit path again.
I thought it would be as simple as using RSD to put it back on the right path but upon reading there seems to be a notion out there this will completely brick the phone. And upon more reading, I can't get a straight laced answer on what I'm suppose to do here to get from where I am to where I need to be.
I suppose my question is what steps do I need to take to get it to some form of official update so I can let OTA do its magic OR simply install the OTA version of 4.0.4.
tl;dr I need help getting from 6.7.2233 to the Official OTA update.

And to answer my own question...
http://forum.xda-developers.com/showthread.php?t=1810373
Thank you for anyone who was looking for an answer to this.

I hope you didn't painstakingly go through the entire process in that thread. You could have just used RSD Lite to flash directly to 6.7.246.

projektorboy said:
I hope you didn't painstakingly go through the entire process in that thread. You could have just used RSD Lite to flash directly to 6.7.246.
Click to expand...
Click to collapse
I did. But thats a good thing actually. I wanted to see if it would put me back on the path to OTA updates and it did. Its downloading 6.7.246 OTA as I type this (Albeit at the speed of snail... yay Verizon servers -.-)
If Bionic begins getting CM 10.1 nightlies I might considering going down the path to figuring out how to get that on it. Really would like some 4.2 hotness on this phone but 4.1.x would make me happy in the pants.

ikaritensi said:
I did. But thats a good thing actually. I wanted to see if it would put me back on the path to OTA updates and it did. Its downloading 6.7.246 OTA as I type this (Albeit at the speed of snail... yay Verizon servers -.-)
If Bionic begins getting CM 10.1 nightlies I might considering going down the path to figuring out how to get that on it. Really would like some 4.2 hotness on this phone but 4.1.x would make me happy in the pants.
Click to expand...
Click to collapse
You should really consider abandoning the updates and flashing .246 directly, either by using RSD Lite or else by using SamuriHL's Hose of Bionic (aka HoB ) utility.
Updates, in m experience, always leave some things messed up, and I and many others have been recommending a full Factory Data Reset when moving to ICS anyway. So, using RSD Lite will flash the fresh full .246 ICS build and it will be like your phone is brand new. RSD Lite will also unfortunately, wipe all of you internal memory, but you can edit the .XML file in the .246 archive to skip that one step so all you current settings, media, etc. are not erased.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD

[Q] Getting from an early ICS leak ROM to the JB OTA?

Hi guys, my mom has the Droid 4. I initially put her on the ICS leak 6.16.208 when it first came out. When the official ICS release (I think it was .219 or something) came out in August, since the .208 leak was working fine for her, I just left her phone alone. Now I see that there's finally a JB update for the Droid 4, and I'm wondering what would be a safe way to get from the ICS leak to the JB OTA.
Would I have to get from the ICS leak to the final version of ICS first, and then update to JB? Or is there another way to go about this? I apologize for asking; I've tried to research this on my own and I just find a clutter of threads that never really seem to talk about how to get off a leaked build.
I have Safestrap Recovery v2.0.0 installed. The unsafe system is the .208 leak, and the safe system is a custom ROM she didn't end up liking (a rather buggy AOKP port), so she just runs the .208 leak all the time.
Would anyone have any insight as to how I could proceed to ultimately get onto the JB OTA? If someone could just point me in the right direction, I'd really appreciate it. Thanks in advance.

I'd probably use the Fastboot/RSD Lite method to flash the release version of ICS, and then update to JB from there. My Droid 4 on GSM thread includes a section on how to flash ICS via Fastboot.
Hopefully we'll eventually get Fastboot files to go straight to JB, but I haven't seen them yet.

Lum_UK said:
I'd probably use the Fastboot/RSD Lite method to flash the release version of ICS, and then update to JB from there. My Droid 4 on GSM thread includes a section on how to flash ICS via Fastboot.
Hopefully we'll eventually get Fastboot files to go straight to JB, but I haven't seen them yet.
Click to expand...
Click to collapse
Thank you so much for your fast response and for writing this guide.
So from what I understand, just fastboot to the OTA ICS and then I can get to the JB OTA from there with the update.zip, right? Will fastboot wipe my data?
Also, is that "Upgrading to Jelly Bean" going to take me to the actual official JB OTA (not a leak)? Because it looks like the link lets you download 6.16.217 which I believe is the finalized JB OTA, correct? If so, that's very exciting. I was anticipating that I would have to wait for Verizon to actually push the JB OTA to me.
Once again, thanks a lot!

This is currently a "soak test". There is a chance that problems could be found with it, though with all the previous soak tests, the official version has followed a few days later and been exactly the same.
If you want to be really sure, you should wait until someone confirms that the two are the same.
Unfortunately I cannot remember if fastboot wipes your data as I tend to wipe my data after an upgrade anyway. If you're rooted I'd suggest you run Titanium Backup to be sure.

I'll use TiBu just to be sure. I actually just read an article that the JB OTA is currently rolling out, so I guess this should be the final version. Thanks for the help!