Database Develop

The point of BIONICPathSaver?

I may be a noob but what exactly is the point of this. I keep both update.zip's on my sd card(893,901). I just tried this. Im on stock 5.5.886 rooted. booted in stock recovery and applied both updates. Now im on .901 and still rooted. I didnt get the cdt.bin error or anything. What is BIONICPATHSAVER supposed to do?

From my understanding, its an extra string of security that keeps root open. I did the same thing and it worked. But my first attempt wasnt soo lucky. I ended up bricking my bionic. No worries though, i used my motorola limited warranty. Now i just have my verizon warranty left
Sent from my DROID BIONIC using xda premium

The point of this tool is to save your ass.
it can be and should be used to go from a pre 901 rom to a 901 rom as well as helping you unbrick your phone.
I needed it to go from liberty 2.0 to eclipse 2.1

Primarily its for people who got off the update path via cheesecake updates. It returns you to the upgrade path so that you can once again receive the OTA updates. Atleast thats my understand of it.

you will need it if you ever want to go back down to 5.5.893.
It was created for people that loaded 5.7.893 or 5.5.894 that were off the update path. If they release ICS for 5.5.893 and not for 5.5.901 at the same time, you may want to go back to get ICS.

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

Upgrade to. 905?

What are the risks involved? I might want to upgrade to Eclipse 3.0, but am concerned about how the unsafe update migbt affect future Verizon OTAs processing.

With the quick avaible way to FXZ your way back to the 902 stock path I would think it would be worth a shot. Check out the link posted below. Currently I think Verzion wouldn't be applying anything soon so there is a great chance to run the leak 905 while you wait for a official update. Had to use this FXZ process just yesturday due to some radio issues with any rom I had on my Bionic. Currently still only Stock and rock solid. Good Luck and let me know how it goes I might jump to the 3.0 update to as long as the Market will fully update to the new Play Store.
http://www.droidhive.com/forums/index.php?/topic/87-902-bionic-pathsaver-for-windowslinuxmac/

ronaldheld said:
What are the risks involved? I might want to upgrade to Eclipse 3.0, but am concerned about how the unsafe update migbt affect future Verizon OTAs processing.
Click to expand...
Click to collapse
At this point, I'd say the risks are pretty much none

another problem is the only ROMs on .905 is Eclipse, so upgrading to that eliminates trying ICS ROMs.
Anyone know when the .905 OTA will start?

ronaldheld said:
another problem is the only ROMs on .905 is Eclipse, so upgrading to that eliminates trying ICS ROMs.
Anyone know when the .905 OTA will start?
Click to expand...
Click to collapse
It has started already.

I just went to Verizon Support and could not find the 905 update...If I go back to stock, will I get an OTA update??

Will this update brick my rooted phone which currently has version 902 on it?

Is it possible to upgrade from 904? Flashing the zip through stock recovery hasn't worked for me. Keep getting an error message.
Sent from my DROID BIONIC using Tapatalk 2

lhkjohn said:
Is it possible to upgrade from 904? Flashing the zip through stock recovery hasn't worked for me. Keep getting an error message.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
It's not possible to go from .904 to .905. The update.zip for .905 looks for system files from .902 before doing anything. It's supposed to fail for you until you FXZ back to .902
lpfas29 said:
Will this update brick my rooted phone which currently has version 902 on it?
Click to expand...
Click to collapse
It shouldn't brick, but you may lose root. Also if you've frozen and/or removed bloatware the update will fail.
ronaldheld said:
another problem is the only ROMs on .905 is Eclipse, so upgrading to that eliminates trying ICS ROMs.
Anyone know when the .905 OTA will start?
Click to expand...
Click to collapse
I was surprised at how well ICS ROMs played with my phone when I was on .904. It may be worth it to try on .905 too. Even then, the devs will probably make updates soon to accommodate the new kernel in .905.
rosystreasures said:
I just went to Verizon Support and could not find the 905 update...If I go back to stock, will I get an OTA update??
Click to expand...
Click to collapse
OTA updates are made for stock phones. The .905 update only updates phones that are running completely stock .902 phones. The OTA updates fail on anything that is not stock. OTA updates are built to expect a certain existing revision of the software. If that is not present, the update will fail. You must revert to stock 5.9.902 if you want .905 to install.

I, too, am getting an error msg about the xml not being correct, or I am missing certain image files. I haven't removed any of the bloatware.
I had 902. Rooted and ROM'd with Eclipse 2.2. Installed CoreDroid_Eclipse_2.2. Curious, will Core Droid not work with Eclipse 3.0?? (IF I ever get the 902 stock again...)

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.

Update to 906?

Hi - Haven't seen any other threads on it, maybe because it's a stupid question, but I wanted to ask if most everyone has taken the update to 906, or if anyone is still hanging out on 890? I have my D3 on 890 with the 906 system. Back when I flashed the 906 system, I did notice the camera was faster (one of the changes in the change log for 906) but I still get random reboots here and there and lately I've been wondering if I should just SBF and take the update itself so I get the updated kernel and baseband as well, but I really don't like that it's a one-way-street. Has everyone who still has the phone moved on to 906 and is it worth it--will I notice more of a difference than where I'm at right now with just the 906 system? Are all the ROMs compatible with the newer kernel? I am still running stock, but I do like keeping my options open so that is probably my biggest concern.
I'm pretty sure I could easily take a nandroid, save it elsewhere, SBF and do the update, and then reroot and restore my nandroid and all should be peachy as I have it now, but with the newer kernel & baseband. Should I?
Thanks!

I think you'll find most people have upgraded. There is an 890 SBF with enough bits of 906 to permit its use, essentially bringing you back to what you have now. Or, go the safe route as I do - SBF 890, perform the OTA upgrade and use Safestrap to protect your original system while you tinker.
Sent from my DROID3 using xda app-developers app

Phibernaut said:
I think you'll find most people have upgraded. There is an 890 SBF with enough bits of 906 to permit its use, essentially bringing you back to what you have now. Or, go the safe route as I do - SBF 890, perform the OTA upgrade and use Safestrap to protect your original system while you tinker.
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. I'm not worried so much about ability to SBF.. it looks like that 906 SBF that was put together works pretty well for most people. Just was concerned that I could be missing out on some good ROMs if I do upgrade, such as ones that haven't been updated (or won't be) to the 906 base. That and if I'd be gaining anything noticeable from the kernel/baseband upgrade, over just having the system as I do now.

Overall performance seems a bit zippier with 906 and I've been able to use any ROM through Safestrap. Not sure if flashing direct with CWM would be any different.
Sent from my DROID3 using xda app-developers app

I would say there are minor noticable changes with .906
if I had to say yes or no I would take the plundge
sence alot of the roms now use the .906 system files your phone being on the .906 ota would help things move more smoothly

I am keeping my phone on 890 because from what I've heard things just work better like with the 883 radio stuff. I am running MavROM which is based off of 906 so I do get better battery life.

Thanks for the responses. I guess I'm leaning more toward taking the upgrade.. why not I guess at this point. Any other 890 holdouts around with an opinion?