Database Users

[Guide] Easiest way from root to stock :)

I have read many posts, and did many tries.........we all know that Froyo ver that is out, is not a official one. In order to get Official OTA update, our phones must be in complete factory stage. Unlocked boot-loader is not an issue. Trust me, i tried many different ways to "unroot" my N1. Following many "how to's" uproot your N, in order to get OTA (Froyo), all tries have failed. I was flashing original roms (ERD79), replaced recovery image, and then i GOT an OTA with 2.1-update1, no sweat! Then, when it tried to install, there was an error every time. I was able to install that (ER27) update manually, but it was NOT the thing i wanted to accomplish. I knew that i will be able to receive next OTA with ver 2.2 (Froyo), but i also knew that this update will NOT install either. The problem is a recovery image! After been running many different custom roms, i have decide to try again to go back to the state from the beginning, so i can be sure i can be able to install official Froyo, when it is out. I was afraid to do this, but i did it anyway.............and it was successful. I restored my Nexus to the original state (except boot-loader of course), and after i got back to ERD79, momentarily i got OTA with ver 2.1-1. But this time, it has installed with no problem!!! I am running it right now, waiting for next (2.2) OTA update.
Ok, here we go:
Just go there and grab Google OEM file (PASSIMG.zip). Put it on your SD card (root dir).
Then restart your phone into boot-loader (trackball+power button).
Once there, top power button again. It will look for passimg file as always. It will load the passimg file. Note the blue status bar at right-upper corner of your screen.
Then, it will check that file, and finally you will see "do you want to start update?"
Press Volume UP, for YES............and wait.
After phone reboots - you are done! Completely back to stock!
Then you can go to "menu-settings-about-system updates" and you should see that your phone is already downloading update 2.1-1.
That is it.
If for some reason you end up with android screen with triangle and exclamation mark, just press VOL up and Power, at the same time, you will get into recovery screen, and reboot your phone from there.
One more thing...........i did that in my own risk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, please do not blame me, if something would happen to you Nexus (phone just exploded, or something....
)

Wow..can't get any simpler than that..thx for this.

Thanks. Very simple.

this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?

This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
-------------------------------------
Sent via the XDA Tapatalk App

Wow... Much appreciated!

laughter95 said:
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
Click to expand...
Click to collapse
Nope. Even if you unroot your phone, your bootloader cannot be locked back again (if you unlocked it). Rooted or not, if your bootloader was unlocked, you always get that unlocked padlock image on your first screen when you turn on your phone. However, I read somewhere that someone has sent his phone back for warranty exchange, after he revert everything to factory stage (except bootloader of course) and they (HTC) accepted. I don’t know how that happened...maybe they (HTC) overlooked that first screen??

As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.

justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
HA ha ha! You did NOT understand what i wrote! Read it again....and what if one does NOT have a Nan backup at all??
" You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. " <= that's total BS!!

Would this work on the AT&T N1?

RogerPodacter said:
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850

This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Th
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.

RogerPodacter said:
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
Click to expand...
Click to collapse
Yeah, it should be something like "HTP123990" which is your device number. Click once more and it'll show all the backups for that device.
Or just browse your SD card to the nandroid folder with a file manager like Linda:

wow thanks! it's so easy to use..and works!
i had so many problems with the froyo 2.2..though i really LOVE the speed and the new interface...but afterwards decided to switch back to 2.1 wait for official OTA...
thanks op!

shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.

http://forum.xda-developers.com/showthread.php?t=686593

Well coming from a rooted MoDaCo rom, I performed the steps and am now running the stock ROM and just been informed that there is an update available. Update is installing now and it works great.
Now I have my stock OS back while still rooted, and getting updates.
I just recently got my Nexus one a few days before Froyo hit. I've been sporting Froyo while traveling and getting barely any coverage. So this is a good test.
I'm on Fringe coverage now. With Froyo and its radio, I kept getting network disconnects. Flashing back to stock+update = 2/3 bars of EDGE.
Finally!

RogerPodacter said:
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
Click to expand...
Click to collapse
It's the fastest way to reload stock recovery/image/radio altogether.

Not true. I can confirm the method in this thread.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse

If i use mybackup pro to backup apps and data, how do I restore that stuff once I'm unrooted? Do you have to redownload mybackup pro? Sorry if this is obvious to some, I'm new to android and really want to be able to get the OTA update. Basically I'm wondering how the people that have used this method got all their info and apps back, Thanks.

[Guide] Upgrade Bell phone to Bell 2.3.4

This is a rough guide to help you upgrade your Bell phone to 2.3.4. This has been tested and it works.
*Usual disclaimer: I am not responsible for any damage to your phone.
This isn't detailed but should be enough to get you going.
You must have a Bell phone and your bootloader must be unlocked. Assume you will lose all data and BACKUP!!
1) Restore Bell System
Use NFHimself's GobStopper CWM zip to restore your phone to stock Bell 2.2.2 - at this link:
http://forum.xda-developers.com/showthread.php?t=1185171
2) Install 2.3.4 and root
- Download 2.3.4 zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1166362
- Download root cwm zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1159572
- Install edgan's kernel if you have d100 device
http://forum.xda-developers.com/showthread.php?t=1173225
- Install faux's d1100 kernel if you have d1100 device
http://forum.xda-developers.com/showthread.php?t=1156040
- Install CWM Recovery (attachment on first post):
http://forum.xda-developers.com/showthread.php?t=1185171
- go into CWM Recovery and install 2.3.4 zip from sdcard
- install Root zip from sdcard
Done!
Thanks to NFHimself, MagentoX , y2whisper and everybody who helped with this.

Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?

Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

What did you do, then, to make the ROM more "Bell-like"?
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
when you did step one did it say it downloaded the files prior to updating the device? this step takes approx an hour to complete.

So it looks like one of your partitions isn't close enough to bell. When I ran into this issue I went with option 1 - I flashed the French SBF and then ran NFS script to root and then restore to install the Bell partitions and checked for OTA. Now that NFS has updated his script to restore 2.2.2 partitions, the OTA may not find any updates which is fine.
awryter said:
What did you do, then, to make the ROM more "Bell-like"?
Click to expand...
Click to collapse
awryter said:
Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
Click to expand...
Click to collapse

Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!

If I do this, will I still have an unlocked bootloader?

once the entire process is complete, yes.

y2whisper said:
once the entire process is complete, yes.
Click to expand...
Click to collapse
So then could this be a permanent fix to the RAM issue?

Thanks for the detailed info on the scripts - it's great to get it from the horses mouth
NFHimself said:
Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!
Click to expand...
Click to collapse

First of all...Can anyone who has been using the new 2.3.4 tell me is there any significant differences in the performance of the phone in everyday use?
Second: Will the WebTop without the Dock MOD work with this new ROM?
Third: If I do this will I be able to install Bell official OTA when it comes out officially or it will brick my phone?

I Am already on 2.3.4 on a bell Atrix, I can honestly say the upgrade does about 0 ... now with that said the real thing that we need is a market fix so we can finally play order and chaos in Canada.
I give this Guide a 1/10 because its redundant and is not as cohesive as the other guides that are already available.
Edit: no unlock in this guide?! whats the point?!
Edit2: nvm you didt write a guide... my mistake, you just posted a bunch of links for lazy people

hate when i hit thanks instead of reply.....
anyways thanks ray of sunshine for that post. the thread was created by request, but if you do have a more detailed breakdown feel free to contribute.
@sservati
I have noticed quite the difference with 2.3.4. outside of the added features like gtalk w/video, there are little tweaks like being able view your contacts by your google groups. as well as some performance tweaks live wallpaper still seems laggy but other transitions are very smooth. as long as you are comfortable with unlocking your bootloader etc, this is something I recommend. if you are overly nervous about doing that. then stick to what you have.

The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!

didn't know about the timing, but yes make sure you follow that guide as well.
ah sorry to hear that.
Did you try doing the spare parts fix? (download spare parts and turn off compatibility mode)

Why are you installing the FR Orange (2.3.4)? The 1100/d00 issue is dealt with in the unlock guides - this thread clearly notes the steps are for unlocked phones only to install Bell 2.3.4.
Anyhow, there are some great threads on unlocking international phones and folks should really consult those to unlock.
Carrion332 said:
The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!
Click to expand...
Click to collapse

Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.

Carrion332 said:
Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.
Click to expand...
Click to collapse
I'm having the same issue with a couple apps that i've purchased.
Anyways back on topic, I was on on cherryblur 0.5 and i managed to get to the bell GB following most of this guide. I tried to do a restore of a nandroid backup i made before going to GB, but for some reason the phone wouldn't boot. It would just stay at the moto symbol. Im assuming it was because of the boot.img. I tried for a few hours to get it to work, but then gave up and flashed the 2.1.1 french sbf, and then used NFHimselfs system restore script to get me back to the stock bell rom. It worked very well, just took a long time.
Personally I really like this Bell rom, works very well for me. Battery life has increased, its FAST, and there's no ram issues. As for the Webtop stuff, im not sure about. I rarely use it.
Just noticed that after flashing the bell_ihop.sbf to unlock the blootloader, the ram goes back down to 300mb. I wonder if someone can dig deeper into the bell_ihop bootloader and possibly fix the ram issues.

Save a copy of 4.5.91 sbf

if you are still on 1.8.3 stock, you can get a copy of 4.5.91.sbf file by using Motorola Software Update, handy if you need to flash a clean version of 4.5.91 on 4.5.40 or 4.5.91(OTA upgraded).
by default, the sbf file is saved to:
C:\Program Files (x86)\Motorola\Software Update\firmwares\1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
copy it to somewhere else before Motorola Software Update finishes flashing or it will get deleted automatically.

erasen1 said:
if you are still on 1.8.3 stock, you can get a copy of 4.5.91.sbf file by using Motorola Software Update, handy if you need to flash a clean version of 4.5.91 on 4.5.40 or 4.5.91(OTA upgraded).
by default, the sbf file is saved to:
C:\Program Files (x86)\Motorola\Software Update\firmwares\1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
copy it to somewhere else before Motorola Software Update finishes flashing or it will get deleted automatically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Have you flashed it yet? I sent Kennithpenn a pm about this and he asked me not to release it. He also told me it is not safe to flash via rsd!!

flashing ...

erasen1 said:
flashing ...
Click to expand...
Click to collapse
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?

NYG-SBXLII said:
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
Click to expand...
Click to collapse
at first, I used Motorola Software Update tool to flash, it flashed successfully - as expected
then I tried to flash it using RSD Lite v5.0, also flashed successfully, it actually did not erase user & data partition, retaining all apps & settings.

NYG-SBXLII said:
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
Click to expand...
Click to collapse
the phone was BL unlocked before, I flashed from 4.5.40 back to 1.8.3 sbf, then " fastboot oem lock" ( not sure if it locks the phone back), then Motorola Software Update tool & RSD.

erasen1 said:
at first, I used Motorola Software Update tool to flash, it flashed successfully - as expected
then I tried to flash it using RSD Lite v5.0, also flashed successfully, it actually did not erase user & data partition, retaining all apps & settings.
Click to expand...
Click to collapse
Ok, well 4.5.40 was never released so thats probably why you where able to downgrade to 1.83. Im not sure if it is a good idea to flash this after 4.5.91 though. probably not a good idea to release unless someone has the ball's to flash it from 4.5.91 bl unlock.
edit: well you flashed it via rsd after you used Motorola Software Update. So it might be all good..
edit: **** it, i've got insurance, im going to give a go... I was bl unlocked and flashed leaked ota
edit: confirmed, 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf is safe via rsd 5.3.1 after ota bl unlocked 4.5.91!
edit: this seems to be a service sbf as it does not wipe data!

NYG-SBXLII said:
I sent Kennithpenn a pm about this and he asked me not to release it.
Click to expand...
Click to collapse
What do you mean he told you not to release it. The upgrade file is freely available from Motorola now. You can download direct to your PC from the software updater.

Would this work for me if after pulling the OTA I am stuck at the Motorola M with Dual Core? Could I flash this SBF and get my phone back up and running? I tried using the Motorola Software Update software but not sure what mode to connect my phone for it to recognize it.. Connected via Fastboot the software says:
"Motorola Software Update is unable to identify you device at this time. Please Try again"
Thank you in advance

NYG-SBXLII said:
Ok, well 4.5.40 was never released so thats probably why you where able to downgrade to 1.83. Im not sure if it is a good idea to flash this after 4.5.91 though. probably not a good idea to release unless someone has the ball's to flash it from 4.5.91 bl unlock.
edit: well you flashed it via rsd after you used Motorola Software Update. So it might be all good..
edit: **** it, i've got insurance, im going to give a go... I was bl unlocked and flashed leaked ota
edit: confirmed, 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf is safe via rsd 5.3.1 after ota bl unlocked 4.5.91!
edit: this seems to be a service sbf as it does not wipe data!
Click to expand...
Click to collapse
NYG, Thanks for experimenting..
Question: So if I do the OTA update, then I MOD the hell out of it. I can use this SBF file and RSD to go back to stock and my phone will be like nothing ever changed...???

you shouldn't install this directly, but it is very handy to have (in order to extract images)
my method is to download it through the program but disconnect the phone as soon as it starts to download. when it finishes, you should have the file there, copy/move it whatever and exit the program.

b30sam said:
NYG, Thanks for experimenting..
Question: So if I do the OTA update, then I MOD the hell out of it. I can use this SBF file and RSD to go back to stock and my phone will be like nothing ever changed...???
Click to expand...
Click to collapse
Yes, but just like the ota, after you flash this, you can never flash firmware lower than 4.5.91 again or you will get a hard brick. Also depending on what ROM you are on before you flash this you may have to manually wipe data because this sbf does not.

franciscojavierleon said:
you shouldn't install this directly, but it is very handy to have (in order to extract images)
my method is to download it through the program but disconnect the phone as soon as it starts to download. when it finishes, you should have the file there, copy/move it whatever and exit the program.
Click to expand...
Click to collapse
This file can now be downloaded from the dev section. http://forum.xda-developers.com/showthread.php?t=1181932

Automatic bootloader UNLOCK/ROOT for AT&T 1.26/1.57/1.83/4.5.91 [UPDATE 07/31/11]

UPDATED/CLEAN SCRIPT V4.2 07/31/11 8:00PM EST
PLEASE DO NOT CHANGE ANY FILE PERMISION OR COMPATIBILITY JUST RUN THE SCRIPT
* I consolidate everything in a single menu, so now Automatic Bootloader Unlock, Automatic Root for Unlock users, Automatic CWM for Unlock users, Mobile Hotspot for Unlock users, Automatic Fix for Softbrick (NO OS SCREEN/some "Failed to boot 0x1000"), fastboot/moto-fastboot checking for troubleshot & Official GB 2.3.4/4.5.91 Restore from Motorola
* Default CWM now: Tenfar's recovery-en-goapk-0630-1029
* Optional CWM Rom Manager's recovery-clockwork-4.0.1.4-olympus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* New executable file "MAIN"
* Now with menu selection to chose what version come from to apply the correct pudding
* Added compatibility layer for Windows 7 x64 users as follow: "set __COMPAT_LAYER=WINXPSP2" <----- I JUST REMOVED
Check screenshots of each step side by side (PC <-> Phone Screen)
AFTER GET THE BOOTLOADER UNLOCK YOU CAN ONLY FLASH BY RSD SBF'S WITH "PUDDING" FOR NOW ON, SO IN OTHER WORDS BE CAREFULLY WHEN YOU USE RSD AFTER "UNLOCKED" BOOTLOADER
* CONFIRMED, IS SAFE TO RSD THIS SPECIFIC SBF FROM MOTOROLA:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
MD5: 56721d893e43b814e95683a00b165555
SHA1: e00786e975b4f1d9fba2ff90c1ee6bbf95bb47b2
SO NOW ON FOR UNLOCKED BOOTLOADER USERS THIS CAN BE A BASE IF SOMETHING GO WRONG AND YOU NEED OUT OF THE BOX STATE FROM MOTOROLA
Need to be flash with RSDlite V5.3.1
Prerequisite:
1. ATT ATRIX 4G device
2. Windows PC
4. No matter what version you have 1.26 / 1.57 / 1.83 / 4.5.91 (*)
5. Proper USB drivers Installed (You can found them at: http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers)
6. A little of Patience
PROS:
* You will ended with an unlock bootloader (BL)
Procedure:
1. Download the attached file
2. Unzip the file inside of a new folder on your hard disk
3. Now is time to run the magic, go to the folder you just unzip the files in and double click or run "MAIN" file
4. A new windows DOS box will show up and just follow the procedure!
5. Flashing pudding part will take a little longer so be patience and let the magic do their work
6. At the end of the process your phone will reboot automatic.
7. Enjoy it!
Thanks to the2dCour for pudding sbf
Thanks to Tenfar for CWM (I prefer it due to the ABD option in recovery! NICE)
Thanks t0dbld for Mobile Hotspot patch
(*) Some users with 4.5.91 will need to run "fix" file to recover from a softbrick after the first attempt
(*) It seemd the new 2.3.4/4.5.91 pudding do a wipe after flash it, so have a backup just in case (I tested 1.83 and at least this preserve the data)
Download file here V4.2:
http://www.megaupload.com/?d=NXU82L12

Is "carpet" another one if these new fangled terms for the inner workings of the Atrix, or just a typo? Because if it's not a typo then you have broken the rule of not using a cooking reference. I propose "jello".
Oh, and does this kill the data partition like regular pudding?
Sent from my MB860 using XDA App

This will help a lot of people not familiar with fastboot. Good job!
Sent from my MB860 using XDA Premium App

updated carpet to folder... And this DO NOT KILL DATA PARTITION!
phobos512 said:
Is "carpet" another one if these new fangled terms for the inner workings of the Atrix, or just a typo? Because if it's not a typo then you have broken the rule of not using a cooking reference. I propose "jello".
Oh, and does this kill the data partition like regular pudding?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse

Your Welcome!
jruweaver said:
This will help a lot of people not familiar with fastboot. Good job!
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse

im a noob to the atrix and all this bootloader stuff lol. when i go to run the “unlock” file what should my phone be at should it be at home screen off or fastboot? srry for the noobie question.

Nice, will this work over Gingerblur? Or should I back off to restored 1.8.3 stock first? Thanks seems like people will never give me an answer . I'd hate to have to reinstall everything backed up again.
After installing this, do I go with the official update on the phone route or use RSD-lite?

crs353 said:
im a noob to the atrix and all this bootloader stuff lol. when i go to run the “unlock” file what should my phone be at should it be at home screen off or fastboot? srry for the noobie question.
Click to expand...
Click to collapse
did you proceed to read the cmd prompt??
your phone should say "Starting RSD protocol support" before plugging your phone in. enter RSD mode by following instructions given in cmd prompt .
THIS IS AWESOME mramirezusa...thanks!!

Has anyone tested this? I want to try it out, but don't want to be the first one which seems to be the case.

If you run the file "unlock", it will tell you exactly what to do with your phone for example "turn on and press vol up..."
crs353 said:
im a noob to the atrix and all this bootloader stuff lol. when i go to run the “unlock” file what should my phone be at should it be at home screen off or fastboot? srry for the noobie question.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

Work in Gingerblur, you don't have to restored to 1.83 stock and it did not touch your data partition but always is good to have a backup of your data
As you stated you have gingerblur so some of your /system files are already been changed if you try to do an OTA it will not pass the file checking before it applied the OTA and run RSD route can wipe your data depending on the SBF (full or service)
I recommend you to flash RSD 1.83 "SERVICE" so it did not wipe your data and then run OTA directly from your phone
LivingChampion said:
Nice, will this work over Gingerblur? Or should I back off to restored 1.8.3 stock first? Thanks seems like people will never give me an answer . I'd hate to have to reinstall everything backed up again.
After installing this, do I go with the official update on the phone route or use RSD-lite?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

You will not be the first one, I did this script for some coworkers overseas, so is already been tested
I tested my self in my unit twice before been release it
xploited said:
Has anyone tested this? I want to try it out, but don't want to be the first one which seems to be the case.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

A bell version of this would be awesome!
Sent from my MB860

I just updated and cleaned the script! file at the first post 07/24/11

Is there an easy way to tell if it worked or not? I'm hoping it did, seeing as apparently due to a bit of a softbrick issue at one point, it completely wiped my phone back to stock. I'm assuming it worked, since it seems that the unlock worked now that i have "Unlocked" displayed at the red M screen.

mramirezusa said:
UPDATED/CLEAN SCRIPT V2 07/24/11
Prerequisite:
1. ATT ATRIX 4G device
2. Windows PC
4. No matter what version you have 1.26 / 1.57 / 1.83 / 4.5.91 (*)
5. A little of Patience
PROS:
* You will ended with an unlock bootloader (BL)
Procedure:
1. Download the attached file
2. Unzip the file inside of a new folder on your hard disk
3. Now is time to run the magic, go to the folder you just unzip the files in and double click or run “unlock” file
4. A new windows DOS box will show up and just follow the procedure!
5. Flashing pudding part will take a little longer so be patience and let the magic do their work
6. At the end of the process your phone will reboot automatic.
7. Enjoy it!
Thanks to the2dCour for pudding sbf
(*) Some users with 4.5.91 will need to run "fix" file to recover from a softbrick after the first attempt
Click to expand...
Click to collapse
do u have to use a FRONT USB port, or can i use a back port?

I am rooted now, i have to use preinstall to get root back after doing this?...Can u make a bat file for that too....lol

Try it if it get recognize it will be fine. But I always recommend front USB port due the drop of the volts
Taas said:
do u have to use a FRONT USB port, or can i use a back port?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

This do not affect you actual root status, so if you have it right now it will be like that after unlock procedure
Taas said:
I am rooted now, i have to use preinstall to get root back after doing this?...Can u make a bat file for that too....lol
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

If you have the tag "unlocked" at boot left upper corner you have a Unlock Bootloader
elementaldragon said:
Is there an easy way to tell if it worked or not? I'm hoping it did, seeing as apparently due to a bit of a softbrick issue at one point, it completely wiped my phone back to stock. I'm assuming it worked, since it seems that the unlock worked now that i have "Unlocked" displayed at the red M screen.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

The Unofficial Thread of Official OTA Updates

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since we got update threads scattered everywhere, I figured I'd organized things into one thread, as well as give away some new updates.
Retail EU:
81.5.31006-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.32002-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.4002-91.2.26001.Retail.en.EU 4.0.4-4.1.2
Retail GB:
81.5.31002-81.5.39001.Retail.en.GB 4.0.4-4.0.4
81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2
Orange GB:
81.5.31002-91.2.26001.Orange.en.GB 4.0.4-4.1.2
O2 DE:
81.5.32002-81.5.39002.O2.en.DE 4.0.4-4.0.4
81.5.39002-91.2.26001.O2.en.DE 4.0.4-4.1.2
Vodafone FR:
81.5.31002-81.5.39001.Vodafone.en.FR 4.0.4-4.0.4
81.5.39001-91.2.26001.Vodafone.en.FR 4.0.4-4.1.2
Brasil BR:
871.110.12008-871.110.12012.Brasil.en.BR 4.0.4-4.0.4
871.110.12012-871.111.20003.Brasil.en.BR 4.0.4-4.0.4
871.111.20003-982.50.20.Brasil.en.BR 4.0.4-4.1.2
AmericaMovil MX:
871.110.13009-982.50.25004.AmericaMovil.en.MX 4.0.4-4.1.2
If you have an OTA update.zip please PM it to me or contact me on google talk ([email protected]) and I will quick add it to this thread, with safe hosting, credits to The Firmware Team's Pzyduck for providing safe-haven for these types of files.
Instructions for pulling an OTA update.zip:
Do NOT install the update! Do these first!
Be rooted. We got plenty of methods. Motofail2go for ICS, and my RAZRiRoot.zip for turl1's Clockworkmod.
Download the Root Explorer app, or the ES File Manager app. (Instructions are for Root Explorer.)
Open Root Explorer and go to the ~/cache/ directory, which resides on the root directory of the phone '~/'
Hit the 'Mount R/W' in the corner, if successful will then say 'Mount R/O'
Copy the update file .zip from the ~/cache/ to your sdcard, external to be safe. External is in ~/mnt/external1/ and Internal is ~/sdcard/.
Copy over the update file .zip from the sdcard(s) you chose to your computer and upload it.
You will want to use Voodoo's OTA Rootkeeper before updating if you have a locked bootloader, you can find my thread on a RAZR i compatible version here.
Send me or post a link here to the update and exactly what System Version you were on, and where the update takes you to.
The community will thank you for your help!
Enjoy. Remember to do your part to the community and contribute all updates!

Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?

Vistaus said:
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Click to expand...
Click to collapse
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.

Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890

HSD-Pilot said:
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
Click to expand...
Click to collapse
Thanks! Uploaded to server, renamed, and added to the OP.

mattlgroff said:
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Click to expand...
Click to collapse
mattlgroff, im in 81.5.31006.Retail.en.EU - 4.0.4. and in software update i get notification of an ota. i down loaded that file when ask if i want to install it i select yes. but when in recovery it always fails. why, isnt that the official? because after that i tried flashing it in recovery but it fails too.
before alll this i was already on 81.5.40002.Retail.en.EU - 4.0.4. coming from 81.5.31006.Retail.en.EU. but i wanted to downgrade back to 81.5.31006.Retail.en.EU. and my phone died. thanks to hsd pilot my phone came back to life he sended me a file http://forum.xda-developers.com/attachment.php?attachmentid=1528201&d=1354399653. but now im stuck in what i told you at the begining. why?? what can i do to go back to 81.5.40002.Retail.en.EU. i know this is not the thread sorry but i was watching your new otas. and i cant install the one for my version.

Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890

HSD-Pilot said:
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
Click to expand...
Click to collapse
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.

mattlgroff said:
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.[/QUOTE
thank you guys!!! that was the problem and another one was that i erase alot of apk.s that i dont use so at time of flashing i saw it said something about an apk. missing so i fastbooted again and flash boot.img and here i am with the 40002.rt.eu. and now waiting for jellybean
Click to expand...
Click to collapse

If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.

joel_sinbad said:
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
Click to expand...
Click to collapse
Yes you can.

I have version 871.110.12008.XT890.Brasil.en.BR installed from sbf.droid-developers
My Razr i bootloader is unlooked and rooted. When i try to install the update with the android button (in about system) i recive error message after reboot. How can i install this update manually with fastboot console?
Thanks!

First, use an Root Explorer and copy your downloaded Update Zip out of the Cache Folder and leak it
Edit : Ok, it's in the OP already. Sorry, it's 1am in Germany :sly:
Your RazR i is rooted, how did you root it? If you used the Unlocked Root (insecure Kernel), than grap the boot signed out of the sbf you flashed and use fastboot to install it
fastboot flash boot boot_signed.
After that it should work. If not, you maybe deleted some System Apps. If that's the case, flash the system_signed.
Sent from my XT890

Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating

josmel91 said:
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
Click to expand...
Click to collapse
I have no clue. I'd ask in the Q&A section if you want an answer quickly

Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.

Semseddin said:
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Click to expand...
Click to collapse
After getting a DMCA Takedown Request from posting those before from the MB886 I'm afraid I can't help you there.

The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.

jenova941 said:
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
Click to expand...
Click to collapse
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works

mattlgroff said:
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
Click to expand...
Click to collapse
Thanks, downloading. Do I just flash it using CWM, RSD Lite or something else?