Database Develop

[Q] noob root questions...

I was hoping someone could help out, i'm a noob for sure, but i do have a LOT of linux kernel programming experience, and have been an SA for over 16 years...
anyhow, here is my issue:
I got my droid bionic on presale a few days before it came out. I rooted using a manual method found here on the forums back in beginning october, and did the root 4ever thing...After rooting, I installed liberty rom v2.0 and have been on that with no updates/mods/changes since that day in october.
MY bionic is currently on 5.5.886. I have not seen any posts about getting it to .893, or anything later for that matter. I would really like to get back into flashing new roms, testing ICS and making this thing mine again, but it has all failed...
Here is what i have tried:
went back into CWM, restored back to original post-rooted stock rom, tried to run system update=failed, all of the instructions i have found on here refer to 893 and above, and have instructions for that, but none that i could find referred to what to do if you were still on a version prior to that...
Can anyone please assist me with getting to .902/.901 so I can enjoy some ICS goodness? or at least be back on a path of better performance/more updated os?
I am willing to paypal some beer money to anyone willing to help, thanks in advance!!

I can help you man.
But I don't take donations.
You have gtalk? PM me your gtalk name.

Noob
I am also having issues. My bionic is 5.5.886. I rooted shortly after getting it, then got over eager and deleted all of the bloatware (backed-up some with Ti but Ti is hanging trying to restore). Now, I can't update.
Is it as simple as me just flashing the current version rom?

kstimp said:
I am also having issues. My bionic is 5.5.886. I rooted shortly after getting it, then got over eager and deleted all of the bloatware (backed-up some with Ti but Ti is hanging trying to restore). Now, I can't update.
Is it as simple as me just flashing the current version rom?
Click to expand...
Click to collapse
You will have to flash the 902 fxz with RSDlite 5.6

[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.

[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

Planning to get back on OTA

So its been awhile since I flashed a ROM to my BIONIC. That was back before ICS was even released for the BIONIC. So I started looking at updating to one of the more stable ROMS that has way better performance that this stock one. Currently I have 6.7.232 on my phone and I would like advice on which ROMs are best for this device. I have looked into some such as Gameblur, Raging Bionic, and Icarus HD. Thus far I havent really decided on one but I have noticed that some of them are on Jelly Bean. I am not sure if I have to return to the OTA path to update to any of these. I also have Safestrap 3.11 installed. Any advice would be appreciated. thanks.

Any help out there?? Thanks.

HarielA4 said:
I have looked into some such as Gameblur, Raging Bionic, and Icarus HD. Thus far I havent really decided on one but I have noticed that some of them are on Jelly Bean. I am not sure if I have to return to the OTA path to update to any of these. I also have Safestrap 3.11 installed. Any advice would be appreciated. thanks.
Click to expand...
Click to collapse
Well Gameblur and Raging Bionic both require one to be on the 98.72.22 Moto 4.1.2 Jellybean update. Incarus HD however is ICS base and can be flashed with your current setup.
If you are destine to update your stock side I would first prep what you currently have on there right now. See this HERE for getting stuff ready.
I would backup anything on the internal storage before hand and make sure that you have a full battery.
You will find the proper FXZ files HERE. If you are on 6.7.2-223 update then use the one for 4.0.4. It would be easier to root again through the update process. After you have completed the restore processes and root through the HOB. Make sure you have VooDoo Root Keeper installed on your phone to back up Root and to disable Root. Then with a good Data connection you are going to take the update Via OTA. Once the update is complete and you are fully booted up. Use VooDoo to restore your Root and test using root explore or NoFrills CPU.

nobe1976 said:
See this HERE for getting stuff ready.
Click to expand...
Click to collapse
The link provided there has a post from the OP that states House of Bionic is discontinued and to use House of Moto. Should I do that?
Secondly I havent for sure decided which Rom I will be moving to. I feel that the interface I have been using is kinda laggy. I installed Next launcher to see if that made a difference and it was more responsive but still my system memory usage skyrockets after a couple hours and sometimes the only way to resolve it is to restart the device. Any recommendations as to which Rom I should move to?

HarielA4 said:
The link provided there has a post from the OP that states House of Bionic is discontinued and to use House of Moto. Should I do that?
Click to expand...
Click to collapse
You can try using the House of Moto stuff also depending on what you feel more comfortable on using. The HOM was desighned to have one interface for all Moto devices instead of each having its own individual setup. I would still use HOB for your purpose only because I don't know if he added in the script to root the device, which was made for ICS versions not JB hence the discontinued portion of it.
HarielA4 said:
Secondly I havent for sure decided which Rom I will be moving to. I feel that the interface I have been using is kinda laggy. I installed Next launcher to see if that made a difference and it was more responsive but still my system memory usage skyrockets after a couple hours and sometimes the only way to resolve it is to restart the device. Any recommendations as to which Rom I should move to?
Click to expand...
Click to collapse
I have tested and played around with a lot of different ROMs and tweaks to find the one that I am ultimately satisfied with. Flying Jelly, well the name speaks for itself, Rage, and GameBlur (which I had minor help in) all work fine for there purpose.. One must pick and choose which one suits there purpose. So my suggestion would be to install SafeStrap 3.60, which is the latest updated one, and create a few slots and run each the same as you would Stock or any other firmware to measure which one suits your needs.....

In a previous post you wrote "If you are on 6.7.2-223 update then use the one for 4.0.4.". I went to the FXZ site and it shows that the 4.04 rom has version 6.7.223 on it already. I already have root. Why would I need to install the same version again and reinstall root to get on the OTA. I just want to make sure I understand this to avoid making mistakes. Thanks.

Then if you feel confedent that all will go well then just install Voodoo to backup and disable root. Take the OTA update and see if it will install. The most that will happen is that if it detects that something is missing from the current firmware you have the installation process will fail and reboot back into what you currently have. At that point you will have to FXZ your stock back to the way it was installed originally, root, then backup root and disable, then take the OTA. ICS is way easier to root then JB. I have kept Root before via OTA when I got it, so I know it Voodoo will keep the backup and install it..

nobe1976 said:
Then if you feel confedent that all will go well then just install Voodoo to backup and disable root. Take the OTA update and see if it will install. The most that will happen is that if it detects that something is missing from the current firmware you have the installation process will fail and reboot back into what you currently have. At that point you will have to FXZ your stock back to the way it was installed originally, root, then backup root and disable, then take the OTA. ICS is way easier to root then JB. I have kept Root before via OTA when I got it, so I know it Voodoo will keep the backup and install it..
Click to expand...
Click to collapse
I think I miscommunicated what my question was. The instructions say to install the FXZ for the 4.0.4 that has the same version of Android OS that is currently installed. the further instructions say to install the OTA from verizon but everytime I check for an update nothing shows up on my phone. Where else can I get the OTA?
In addition I want to know what I should do about safestrap. Should I remove it before installing the OTA or is it fine to leave as is when I go to install the OTA?

OK... If you cannot even get Big Red to send you the update. You can fxz the update, but at that point you will loose root, but have the option to keep your current data. Go see House of Moto or House of Bionic over at droidrazr.com
As far as Safestrap I would just uninstall recovery through the app the reboot so it clears out before the fxz process.
$3π+ £®m€ ×X× BiOπI¢ oπ $ø|/|£ťhïñğ ¢ű$ț¤|/|

fyi I think he took House of Bionic down, didn't see a link. I can however attest that House of Moto worked perfectly fine. Flashed fresh .232 and VZW sent me the OTA (I tried voodoo rootkeeper before updating). I did lose root despite following all of the steps. To get it back your best bet is to boot up a live Ubuntu disc. I tried the VM that someone compiled but it kept failing.
PS: nobe1976, how the hell did you fit 3 ROMS on your phone? I can only fit one ROM (besides obviously stock). Wish we could install ROMs through safestrap to SD (internal or external).

mikemikemikexxx said:
fyi I think he took House of Bionic down, didn't see a link. I can however attest that House of Moto worked perfectly fine. Flashed fresh .232 and VZW sent me the OTA (I tried voodoo rootkeeper before updating). I did lose root despite following all of the steps. To get it back your best bet is to boot up a live Ubuntu disc. I tried the VM that someone compiled but it kept failing.
PS: nobe1976, how the hell did you fit 3 ROMS on your phone? I can only fit one ROM (besides obviously stock). Wish we could install ROMs through safestrap to SD (internal or external).
Click to expand...
Click to collapse
This is the Exploit I have been using the past few days.. HERE.
However Samuri didn't remove the HOB site, He just doesn't maintain it as much since HOM. Here is the LINK to that f needed.