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.
Related
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] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"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"
}
Nice for you to localize everything, ATT users will be grateful.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.
Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?
Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604
Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.
Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
theres the moto-fastboot file i was looking for!
much appreciated.
Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.
humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.
humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.
SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight
after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way
A WARNING: IN THE EVENT OF A BRICKED DEVICE, I AM NOT RESPONSIBLE! YOU DO THIS AT YOUR OWN RISK. KDZ UPDATER WILL BRICK YOUR PHONE IF NOT USED PROPERLY. SO FOLLOW THESE INSTRUCTIONS CAREFULLY!!!
So, you want to install custom recovery and custom ROMs? Well, you're in the right place. Follow this guide to it's exact instructions, and you will be fine.
You will need:
A computer running Windows (Sorry Mac & Linux users!)
Your phones USB cable. (If you don't have one, you can see a list of them here on Amazon)
We will need a couple of downloads first, so download these files:
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio).
KDZ Updater
Also, make sure you have your drivers installed. If you don't, get the .zip from here and install all 3 .exe files that are in the zip.
Now to install the Fastboot ROM!
First of all, extract KDZ Updater to the desktop. Then run the msxml.msi file to install the MSXML Parser that is needed to run KDZ. A window should then pop up that looks like this:
{
"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"
}
^^Select install now.
But if this comes up:
It is already installed, and you can close the window.
Once that is sorted, open up KDZ_FW_UPD.exe (Windows Vista/7 users, make sure to right click and select RUN AS ADMINISTRATOR!)
Change the type of flash by selecting the 'Type' dropdown box and select 3GQCT (SUPER IMPORTANT!)
And make sure PhoneMode is set to DIAG.
Click the
icon and select the KDZ file you downloaded earlier.
Prepare the phone by enabling USB Debugging by going to Settings>Applications>Development>Enable USB Debugging, also go into Settings>SDCard & Phone Storage and make sure 'Mass storage only' is unticked. Then connect the phone to the computer via USB cable and let Windows install any drivers it needs.
Click 'Launch software update' and do not use your computer until the update is complete. The update will take roughly 10-20 mins to complete. Your phone should reboot automatically.
Installing recovery:
You have multiple choices to choose from.
ClockworkMod Recovery 2.5.1.8 (Recommended)
ClockworkMod Recovery 4.x (Recommended but you may run into incompatible .zip files, download the recovery_clockwork_x.x.x.x_swift.zip file)
Amon RA 2.2.1 (Recommended)
Amon RA 1.7.0.1 (Not recommended due to incompatibility with zip files and recovery backups. Also .zips must be signed)
Download the recovery image of your choice (I strongly recommend Clockwork 2.5.1.8)
Next put your phone in Fastboot mode by rebooting then holding Camera+Power, make sure USB Cable is plugged in. Also let Windows search Windows Update for drivers.
Download fastboot.exe from here: http://adf.ly/2M8Hi and extract it to the desktop. Also put the recovery image you downloaded onto the desktop too.
Be sure to have your fastboot drivers installed, if you use Vista/Windows 7 then the driver should be auto-downloaded from Windows Update, if you use XP or the drivers won't install from Windows Update, then look at this.
Open a command prompt and type the following:
Code:
cd Desktop
fastboot devices (if you see ? fastboot then your device is recognized)
fastboot flash recovery name_of_recovery.img
fastboot reboot
When fastboot says rebooting, hold down HOME and wait. You should see clockwork pop up. Recovery is now on your phone. You can delete the fastboot, kdz and recovery file from your pc because we won't be needing them again. Unless you need to use fastboot.exe again, but just download the fastboot.zip again if you need it) The other files, we don't need.
(NOTE: If your phone reboots with no boot logos (LG logo and animation), or when you flash recovery and it doesn't come up, follow the steps found here. Thanks to fishears for the post!)
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Recovery backups usually contain some .img files and a nandroid.md5 file. The folder containing these files will need to go in the sdcard\clockworkmod\backup folder. Flash them by going to Backup/Restore>Restore>Then pick the backup folder.
Recovery update.zips contain three (or four) files/folders:
boot.img (file)
install-busybox.sh (file, only appears in SOME ROMs)
system (folder)
META-INF (folder)
DO NOT EXTRACT THESE, just put the .zip file on your sdcard, then go into recovery and go to install .zip from sdcard>choose .zip>pick the .zip you downloaded. (NOTE FOR SWIFTDROID: You MUST put the update-cm-xxxxx.zip file found in the SwiftDroid_x.x.x.x_Recovery.zip on your sdcard for it to install!!!)
If you need any help, PM me or reply to this thread.
Don't forget to say
if I helped!
Enjoy!
Want to go 'advanced'? Check out this guide resizing your partitions so you can have more app space!
(Also, if a mod could sticky this thread I would be very thankful. Cheers!)
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
scribbclubber said:
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
Click to expand...
Click to collapse
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
effortless. said:
...
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio)....
Click to expand...
Click to collapse
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
nutterbg said:
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
Click to expand...
Click to collapse
It is meant to include a fix for calling while connected to 3G. Me and many other users encountered a problem where we could not recieve calls on 3G. I flashed this and my problem was gone. Also, i'm unsure how to check the baseband firmware, in 2.2 ROMs, this is visible, but I looked in the build.prop, and it was a set text (under ro.ril.baseband I think) but yes, you could flash this KDZ, restore backup and all would be well. But if you needed the modified partitions, just use the tutorial that is in my signature, then flash backup.
Good idea
effortless. said:
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
Click to expand...
Click to collapse
yep well said, when they appear and post without using search bar...lol think that i've did it myself but i used to save improtant notes and like that no need to search again and again, the thread should be stuck for noobs..
the guides are already here but posted on different threads and not at start, so agree that pics alongside instruction is a good idea.
Do I need recovery_clockwork_4.0.1.4_swift, that is on Mur4ik's site, to install SwiftDroid_v2.0_RC4, or I can use recovery clockwork 2.5.1.8 that I already have on my phone?
EDIT:Nvm, fixed it.
Added info on making sure 'Mass storage only' is unchecked before using KDZ to solve some peoples issues with the phone not being detected.
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
DamDSx said:
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
Click to expand...
Click to collapse
Obviously if you needed to root then I would have included the steps. Also around 99% of custom ROMs are rooted anyway.
I have a rooted and already updated to 2.1.
Would this still work?
KenifJambo said:
I have a rooted and already updated to 2.1.
Would this still work?
Click to expand...
Click to collapse
Of course, you would have to do this anyway if you want to install custom ROMs
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Danzano said:
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Click to expand...
Click to collapse
It already has been lol
In 2.1, you can check baseband in hidden menu.
Sent from my GT540 using Tapatalk
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Aktivehate said:
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Click to expand...
Click to collapse
As far as I am aware, it works perfect, GO is just some branding from some providers.
^^ Could someone back me up on this,
Thanks
Well that's good to know, i had one with 1.6 but made some things go wrong with the drivers, and the usb settings in android, but know i have this guide so i am gone try it.
When I tried it i had some trouble with the kdz flasher, but i did'nt knew of the msxml stuff and it was with windows 7.
Could someone upload another fastboot rom,preferably a version v20a or v20b
Sent from my GT540 using XDA App
This is for a clean install. You can also install straight from Froyo. Just start at the CM7 part below and skip the Odin portion.
FLASH AT YOUR OWN RISK
**If after you get on and are rocking the ICS of your dreams, you wake up one day and get the Encryption Unsuccessful - Reset Android - ICS Issue, see bottom of post for possible solution**
DO NOT HIT RESET repeat DO NOT HIT RESET
It is a bug that is hitting all ICS ROMS (AOSP-Passion, AOKP-Zen/Euphoria, Docmasters, CM9,...) on many different types of phones (Captivate, Vibrant, I-9000) and someone got hit with it in my OG Transformer Tablet (TF101) forums too.
You have been warned.
FLASH AT YOUR OWN RISK
I have made some observations as to how and why the Encryption Error strikes. See this thread starting at page 38 on (my post is #379 and after).
If running CM9 then this may be a work around before the issue strikes. I have not tried this and take no responsibilty if it works or not. Good Luck
USB mode switch for SGS1 on CM
Click to expand...
Click to collapse
What you need. All files can be found in the [Repository] Essential Hard To Find Files
Odin or (AIO ToolBox AND .net files) ***DO NOT PM me for this, I will just delete your PM and not respond. If you want ODIN, use Google and Download it. Sorry for this but my Dropbox account is suspensed b/c of too many downloads***
Gingerbread Bootloaders Go here for instructions.
CM7
Whatever ICS ROM you want to flash
These directions should work with any ICS ROM because the OPs and requirements (i.e. GB bootloaders, CM7 first,...) for all are essentially the same.
Click on Gingerbread Bootloader and ICS to take you to their respective threads.
**Note that this step (Installing Gingerbread Bootloaders) is reported to be optional as the Rainbows seemed to be fixed** Note: ICZenwich does REQUIRE Gingerbread bootloaders for CWM purposes.
If you want to use different Kernels (this is done after you flash the ICS ROM) on Neobuddy89's ICS Passion or Euphoria, Closedcircuit has them all in one place. Check out his thread here and make sure to thank him otherwise you might have to search for them on your own and we all know what a P.I.T.A. that is don't we?
.::IMPORTANT::.
Remember that you have to do this steps before and after update your kernel:
Wipe cache
Wipe dalvik cache
Flash kernel
Fix permissions
Click to expand...
Click to collapse
If for some reason your External_SD card (soon to be called EMMC after you get on ICS) does not mount. See here. Click the link within and flash it in CWR and you should be good to go
Click to expand...
Click to collapse
Standard Disclaimer Applies: This is your choice to do this, not mine. If something goes wrong, ask. If something goes horribly wrong, it is on you.
The video: This was done by DJeddieone and is very informative and helpful. Please watch it and hit his thanks. What follows is generally the same thing but with a few differences and in written form for all those people that need text instructions.
Watch this video, then read the below, watch the video again. Video has Froyo bootloaders and getting into recovery is different key combo, see GB thread below about that.
Just to make sure, I am going to start at the very beginning.
Flash back to stock 2.1 with Odin and the pit/pda files already included in the Toolbox. You should already know how to do this if you are flashing ICS. If not, then use the search to find out how.
Download and put Clockwork Recovery.zip on your internal SD card. Make sure it is labeled Update.zip and is the only .zip on the root of your SD card (should look like this /sdcard/update.zip). Can be directly downloaded from my signature or the Noob Guide stickied in the Q&A sections. Thanks s15274n
On your INTERNAL SDcard create a folder called ICS or something.
Download the CM7 file and put in the ICS folder (doesn't matter about the 911 issue b/c you aren't going to be using CM7 anyways)
Put the ICS ROM version that you already downloaded in the Folder also.
So let's start.
**Note that this step is reported to be optional as the Rainbows seemed to be fixed**
You need to open Odin and boot phone into download mode. Download the Gingerbread Bootloader and put it on your Desktop and in Odin, click on PDA and browse to the GB bootloader and click it. Your option but I do not tick the Auto-Reboot just in case of a bad flash. Once it passed, you are good. Unplug and reboot.
To start the flashing process, you should have 2.1 (stock-Eclair) on your phone as per above directions
Once it is fully booted, turn it off.
Push the Volume-Down + Power until you see the Vibrant come up and let go of the Power but keep ahold of the Volume-Down button. This will boot you into recovery. (If you are on Froyo Bootloaders, then it is Volume Up AND Down + Power) Can be tricky, so try it a couple of times if it doesn't work the first try.
Tab down to Reinstall Packages and click it. Let it run. If it gets back to the Blue Recovery, you might have to do it again. This will install the CWR that you put on your internal SD that you downloaded from my signature earlier. The recovery will go from Blue (stock) to Green (CWR).
Wipe Data/ Factory Reset, Wipe Cache and go to advanced and Wipe Dalvik-Cache, go to "Mounts and Storage" and format /system (if flashing Euphoria you'll need to format /data too), hit Back twice to front page of CWR.
***See Bottom why you need to flash CM7 before.***Also, if coming from a Voodoo Kernel based 2.2 or higher ROM-Disable it before flashing CM7.***
Scroll down to "Install from SD Card" and scroll down to your ICS folder. Find your CM7 file and hit it. Once it finishes, reboot. It will probably bootloop. This is normal. Pull your battery and boot into (turquoise [or red or green]) recovery again, "Install from SD" and reflash CM7.
Once it finishes, reboot. First boot takes longer than normal because it has to build the Dalvik-Cache. It should boot up this time. Let it fully boot up and settle for a minute or two. Hit power on the side and reboot into recovery directly from the Extended Power Menu.
**There is a point in the flashing of CM7 where you will think that the install either aborted or is finished. IT IS NOT DONE. Let is sit and completley boot up. Don't get trigger happy. You will see a toast to install your Google password. Then is when it is fully booted.**
Once you are in recovery, scroll down to your folder and find the ICSv? (or whatever version you are wanting to flash) and flash it. First boot takes a long time just like before on CM7. Might also get into a bootloop like in CM7 too. If so, then do the same as before and reflash ICSv?, but this time you'll have to use the Volume-Down + Power (or if on Froyo Bootloaders the above key combo) to get into recovery. Boot up and you are good to go in you new ICS rom.
**IMPORTANT**
Why do I need to flash CM7 before ICS? Can't i just go from Eclair to ICS? i have seen some people do it this way and it worked for them.
ICS kernels and working recoveries use a MTD based /system (hence the flash to CM7, as CM7 will convert your /system properly) and Eclair/Froyo are either RFS or Ext4 (voodoo). It also converts your Externa_SD into the EMMC partition.
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
If you get the Encryption Unsuccessful - Reset Android - ICS Issue
{
"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"
}
Go here in the Captivate Forums.
******************
Couple of things.
Once you are in ICS
*your external sd is now called EMMC
*the GPS is sketchy (although there are new kernels that are reporting this issue fixed-see your respective ICS thread)
* there are some Deep Sleep issues
* when you RECEIVE a call, you will have to hit mute/unmute for them to hear you. (this seems to have been cleared up now)
These are all known bugs and if you ask about them in the thread, you'll get flamed for sure.
Good luck. The whole process should only take a hour or so and most of that is just finding the files and watching the video. Actual flashing should only take 10-20 minutes.
Hit the thanks. Pretty much gave everything needed to flash from 2.1 to 4.0.3
A computer lets you make more mistakes faster than any invention in human history – with the possible exceptions of handguns and tequila. ~Mitch Ratcliffe
Change log:
4/17/12 - I have made some observations as to how and why the Encryption Error strikes. See this thread starting at page 38 on (my post is #379 and after). Put in link to Play.Store for USB mode switch for SGS1 on CM and tag at top of guide re: its use.
4/2/12 - Emphasized the Encryption Bug to make it more visible and warning of hazards.
3/30/12 - Put in section at Top and Bottom about the Encryption Unsuccessful - Reset Android - ICS Issue and a link to the solution/workaround to the Captivate thread.
3/12/12 - Bolded AND in the kernel instructions re: wiping before AND after kernel flash. Put in something about waiting for CM7 to fully boot up and that it may seem like it is aborting or done, however it isn't and you need to wait for a complete boot. Don't jump the gun on this and pre-maturely pull out. This is called CyanogenMod-us Interruptus.
3/8/12 - Explained why you need to flash CM7 before ICS. Put in link to fix External Mounting issue.
2/22/12 - Put in blurb about PMing me for AIO Toolbox and made the Toolbox Secondary to Odin
Included Closedciruit's thread with the ICS Passion and Euphoria Kernels.
Put in blurb about RANDOM OFFSET error and how to fix/bypass it.
2/18/12 - Took out Dropbox links because my account got suspended for TOO MUCH TRAFFIC. You are on your own for those right now until I find another solution. I am not going to register for another file sharing site.
2/15/12 - Put Dropbox links in OP with Froyo and Gingerbread Bootloader. Revised to make this all ICS ROM compatible since the OPs and per-requisites are essentially the same.
2/12/12 - Now AIO Toolbox, .Net and CM7 have direct download links since MultiUpload is down
1/15/12 - Revised to show that you can come from 2.1 OR 2.2
Yea, rainbows are fixed. If you don't flash a gb bootloader you wont see the kernal boot image. That's the only known issue. So its not really needed
Thanks for the nod, good job man.
I'm glad you put the AIO toolbox there. It seems no one knows how valuable that little program is.
thanks woodrube for the simple guide. the video from djeddieone seems to be fairly simple also.
i heard that if odin was used to go back to stock eclair to never use kies mini for a future update or else it would hard brick the phone. I've never odined back to stock however tempting to install cm7 i fell victim to a bootloop so i freaked out and odined back to froyo kb5. the question is now, if i used odin to go back to froyo would it be the same outcome as using odin to stock eclair when tempting to update with kies mini?
the reason why i ask is, i had given up flashing a custom rom, hoping for a stock update. but if thats not possible anymore i will go ahead and flash ics.
i tried my best searching. if i'm asking in the wrong place please redirect me. thanks and be patient with the noob.
lazynoob said:
thanks woodrube for the simple guide. the video from djeddieone seems to be fairly simple also.
i heard that if odin was used to go back to stock eclair to never use kies mini for a future update or else it would hard brick the phone. I've never odined back to stock however tempting to install cm7 i fell victim to a bootloop so i freaked out and odined back to froyo kb5. the question is now, if i used odin to go back to froyo and not eclair would it be the same outcome as using odin to stock eclair when tempting to update with kies mini?
the reason why i ask is, i had given up flashing a custom rom, hoping for a stock update. but if thats not possible anymore i will go ahead and flash ics. thanks and be patient with the nood. i tried my best searching.
Click to expand...
Click to collapse
Couple of things. First DO NOT USE KIES. Kies will hardbrick you device. Not sure why anyone still uses this but don't. Second, you bootlooped in CM7 b/c of an CWR mismatch. This is normal for CM7. What you would want to do it pull the battery and reboot into recovery and reflash CM7, essentially over-top of itself. It should boot up the second time.
Don't give up on flashing custom ROMs. Once you do it, you will love all the cool things that you never knew you could do. Follow my instructions above and you can essentially flash whatever ROM you want from 2.1.
yea figured it out watching some youtube clips. should have reflashed. so what you are trying to say is kies mini in general is dangerous? i have used it sveral times to update when on stock. mine and my wife's vibrant.
last question, if the impossible happens and vibrant gets a stable stock update, will i be able to just odin to stock eclair and update? if not with kies maybe using odin?
thanks for your help. hoping to help those like me in the future. can't wait to start flashing.
lazynoob said:
so what you are trying to say is kies mini in general is dangerous? i have used it sveral times to update when on stock. mine and my wife's vibrant.
last question, if the impossible happens and vibrant gets a stable stock update, will i be able to just odin to stock eclair and update? if not with kies maybe using odin?
Click to expand...
Click to collapse
Kies is bad. Really surprised you haven't bricked it yet. Stick with Odin to do your fresh flash. The Vibrant is not going to get an update, so don't count on that (see the petition in my signature if you want that to change). Fortunately we have an outstanding development community.
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice. All of these have working GPS and 911, so no issues there. Any GB ROM (CM7 included) will not have functioning 911, just an fyi.
Bump (sort of b/c I updated some things on the OP)
Reserved. Good guide here. Thanks for the effort for those who are not so familiar with flashing like me. Gonna flash ICS when i get my Vibrant back. Thanks buddy.
multiupload seems to be done, does anyone have another link or can they send me AIO Toolbox?
Quikster said:
multiupload seems to be done, does anyone have another link or can they send me AIO Toolbox?
Click to expand...
Click to collapse
help? does anyone have this file or another link? PM me
outstanding development community.
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Woodrube said:
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Click to expand...
Click to collapse
awesome, i greatly appreciate that
OP updated with Dropbox links to AIO Toolbox, .Net add-on and CM7 7.1 ROM.
Thanks for the Guide, works perfectly. Now im enjoying ICS Passion v13 RC1.
I was in TeamToxic-D9RC3 rom. This is what i did:
- I started from CM7 part.
- Reboot into Recovery
- Wipe Data/ Factory Reset, Wipe Cache and go to advanced and Wipe Dalvik-Cache.
- Locate ICS folder-Install CM7.
- After boot into CM7-reboot into Recovery again.
- Install ICS Passion RC1.
- After finish installation, wait bout 5mins.
- Reboot into Recovery again, flash cleanup patch then reboot.
- That's it.
Thanks to:-
-Neobuddy
-Nelson for the Kernel
-Romanbb for source hack to enable FB sync
-Daniel for the Bootsplash and other graphical enhancements
-CM9/Teamhacksung for the drivers
-Annex for cosmetic upgrades which are really better than Stock ICS AOSP.
psycho for Mods
-Woodrube
Woodrube said:
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Click to expand...
Click to collapse
Thank you very much
Woodrube ... thanks for the nice tutorial. Couple questions re. the GB Bootloaders.
Woodrube said:
**Note that this step is reported to be optional as the Rainbows seemed to be fixed**
Click to expand...
Click to collapse
When you say "Rainbows seemed to be fixed" ... does this mean:
a) GB Bootloaders are still REQUIRED - ie. it's the GB Bootloaders that "fix" the rainbows?
b) Or ... GB Bootloaders NOT required - ie. some type of fix has now been incorporated into the ICS ROM packages?
Sorry for asking for noobish clarification, but I wanted to avoid any possibility of turning my phone into a paper weight.
Woodrube said:
Your option but I do not tick the Auot-Reboot just in case of a bad flash.
Click to expand...
Click to collapse
This is a great suggestion. Thanks for the tip.
Woodrube said:
Gingerbread Bootloaders
Click to expand...
Click to collapse
adyscorpius' link for his modified JFD ODIN file is down (ie. Multiupload is down). Wondering if anyone has this particular file or a fresh link to download it? It'd be nice to not have to worry about whether a JFD package has the proper boot.bin / sbl.bin combo or not.
{
"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?