Database Develop

Gingerbread Update Question

Hi everyone
I have a question, I rooted my phone (Nexus One AT&T version) with Androot after that I downloaded Rom Manager and install cyanogenmod 6.1 before that I do a backup of my stock rom with Rom Manager and stored in my Sd card.
My question are, in case I want to upgrade to gingerbread the only thing I have to do is return to my original rom backup with Rom Manager and rooted again with the androot?
Thanks for your replies.
Sent from my Nexus One using Tapatalk

Yes that should be it.

Actually...
To use ROM Manager, you have to install a custom recovery and with a custom recovery
you won't be able to get the update OTA, since the update will reboot after download
and try to install via the original recovery...
But of course the update will most certainly be posted here as a update.zip that you
can install via ROM Manager...
//Nik

ClockworkMod recovery will install the OTA update as it doesn't check signatures.

nikjensie said:
But of course the update will most certainly be posted here as a update.zip that you
can install via ROM Manager...
//Nik
Click to expand...
Click to collapse
+1
I'm sure that within 24 hours (or 24 minutes) of the first release, a repacked update.zip for custom recovery will appear. If you're coming from Cyanogen, take a nandroid and Titanium backup first, then wipe data/cache, before proceeding.
Keep in mind we *don't* yet know if any root exploits remain in Gingerbread. They may well have patched up the "rageagainstthecage" exploit by now. If your bootloader is locked and you want it to stay that way, and you still want the option of root access... then wait for the custom recovery update.zip and use that.

Thanks to all for the answers, I don't think gingerbread have much changes like cyanogenmod 6.1, but in case Google announces tons of surprises with gingerbread I known the best way to return back to get the update.
Thanks
Sent from my Nexus One using Tapatalk

Prep Work For a Successful Root of my D3

So, as this is my first post on XDA I'd like to first state that I am somewhat new to the rooting scene. I used to have a DX and rooted it with no major problems. I know this is probably best suited to be posted in the Developement section, but I currently dont have premissions to do so. I would like to make sure I have everything I need and a clear understanding of the process before I attempt to root my D3.
As a precaution I would like to comfirm that their is a current .SBF file that can be used to return the phone to stock should I do something stupid during the root process? I have found the following link on this site with a .SBF file but from reading the threads I cant determine if this will return the D3 to stock:
[Recovery] RSD v5.5.0 and 5.5.184 (aka 5.6.890) fastboot partitions/flashable zip: http://forum.xda-developers.com/showthread.php?t=1255198
Can someone confirm/verify if this will return my D3 to stock should I need to?
Also within this thread their is mention of Moto-Fastboot and something abbreviated as abd (i think). I am not familiar with either of these. Could someone also provide a breif explanation of what these are and their importance to the .SBF process?
I am also planing on using the following otpion to root my D3:
[Guide] one-click root for Droid 3 (and others) [UPDATED 9/8/2011]: http://forum.xda-developers.com/showthread.php?t=1240130
I want to say that I read somewhere that I have to download the SU.apk from the market place? Is this correct or does this option one-click process display the SU icon in the app draw as the z4root one click option did on my DX?
Also I know that I need to purchase/download the D3 boot loader file from the market plac, I think? Is there anything else that you would recommend that I download/purchase to ensure I dont brick my phone in the process?
Sorry this is so long, but thank you in advance to those that provide responses/suggestions/comments to my questions.

Yes, there is a fully functioning sbf available for the D3
Yes, that is the sbf that is needed. To actually use the sbf you will need rsd lite, which i also believe to be in that post with the sbf.
This sbf will indeed return your phone to fully functioning stock in the case that it should be needed. (i've had to do it my fair share of times)
ADB is a command prompt interface that allows you to interact with the files on your phone without having to go into something like root explorer.
Fastboot (power + vol up + vol down) is a pre boot menu that allows you to boot into different things (like the AP fastboot mode needed to flash an SBF or to go into recovery). To flash an sbf you need to connect your D3 to the computer (in computer mode, i think), and choose the xml file that is in the SBF after you've extracted it.
The one-click root allows you to root your phone hassle free
When i say this, I mean that it installs the Superuser.apk and pushed the busybox and su to the system/xbin, which is needed for some different processes that require root.
here is the link to the most updated version of the bootstrapper, which allows recovery to be entered through the power-off (by using the bp tools option in fastboot)
http://forum.xda-developers.com/showthread.php?t=1289254

smoshim, thank you very much for your assistance and explanations. I already have RSD Lite on my computer and actually meant to include that in my original post. I had it on hand for when I rooted my DX just incase. I did need to use it once but it wouldnt recognize that my DX was connected for some reason. So I had to use a disck based linux program to SBF my DX when I sold it. Hopefully, RSD Lite doesnt give me any issues should I need it for my D3. Well, It's almost 2 am here in Omaha and I need to get my sorry tail to bed. Gotta be up in 5 and a half hours to get my 3 boys out the door for school. I have been patiently waiting to root my DS as I wanted to be sure that all of the "kinks" have been worked out and also wanted to try out some custom roms. I loved the darkslide rom for the DX. In your opinion do you think I should also go ahead and download/install rom manager?

honestly, rom manager doesn't have much available for the d3 yet. it'll be more productive right now to just manually drop the ROMs into your sd and boot into recovery.
And, in my opinion, the roms that we have out now are awesome. And as people get impatient they're making more and more themselves. So even though there may not be too many to choose from compared to some other devices there are more and more coming into the works all the time. But it sounds like you know what's going on, and the sbf process is pretty painless if you're already familiar with rsd on your DX

upgrading from 902 to 905 help please~

ok so heres the deal. i already have the file downloaded via the updater in the settings already to get installed. but i used rom toolkit to modify my status bar and install a custom bootanimation as well as a few other things like that. do i have to use rsd lite and a full 902 fxz file to do a full sweep and clean recovery before installing 905? also does it require me to uninstall safestrap? i'm not entirely sure if anyone else has answered these questions as i don't know if anyone else has done these kind of things before upgrading to 905. i plan on installing the ICS leak after installing 905 thats why i wish to know these things as i'd rather not screw up my phone after i've put so much time and effort into making it the way i want it you know? OH one other question! i know that the ICS leak is rootable does that mean safestrap is also ICS leak friendly?

I believe you should be able to just run the update and the Bionic will reboot into stock recovery. I would create a nandroid just to be safe so you can restore if something goes wrong. I read somewhere that the ICS leak requires you to eliminate safestrap though I am not sure if that is true or not.

I decidex to go thd longer safer route of rsd lol. But i rooted the leak and safestrapped it and it still works so yay!!!! Lol
Sent from my DROID BIONIC using XDA

So you can successfully dual boot with safe strap on the leak? Great to hear!

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.

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.