Database Users

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions

[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=1169409​Step 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

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

[HOW-TO] Install 2.1 + Fastboot + Recovery + Custom ROMs on GT540! (n00b friendly!)

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

[AT&T][UCKB2]Heimdall One-Click -Total Stock- **now with or without root

Introduction
This package will totally reset your Captivate to UCKB2. This is the current version pushed out on new Captivate devices today. This package is intended for use on AT&T, however it will work with the Rogers SGH-i896 if you reset APN.
Note: this is stock rooted, I will put up a non-rooted version soon.
This package includes:
Repartitioning: Repartition to stock KB2
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Total Stock:
Download AT&T Samsung Captivate Total Stock UCKB2
http://files.teamkomin.com/Captivate/SamsungCaptivate-SGHi897-UCKB2-NoRoot-One-Click.jar
Total Stock Rooted:
Download AT&T Samsung Captivate Total Stock UCKB2 "Rooted Version"
http://files.teamkomin.com/Captivate/SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
{
"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"
}
Your device will end up as it came from the factory:
How I created this package:
I obtained the stock 2.1/2.2 bootloader which Trae uploaded
The stock Captivate part.pit came from my device using Heimdall(Download Pit option)
Uploaded the KB2 firmware to my device with bootloaders from nerz
Performed "wipe data" in recovery mode
Exploited the root prompt at the battery charge sequence using UART and grabbed the stock, wiped dbdata/cache partitions and params.lfs partition
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate this one-click
This procedure can be reproduced for any custom ROM in the future.
Credits:
nerz- kb2 firmware: http://forum.xda-developers.com/showthread.php?t=1263379
Trae32566- 2.1/2.2 bootloaders: http://forum.xda-developers.com/showthread.php?t=1095067

Partition problems have been fixed.
Please use a good USB cable so that we don't clutter this thread with "this dosn't work"

Nice work!
Trying this out now on Win7 from Pinnacle 1.2 (RFS) will let you know results. I have been waiting to try UCKB2, thanks Adam!

Just wanting to be sure before I try and brick my phone lol.
When coming down from gigglebread, we need to use the froyo bootloaders i assume.
I dont know if its from running this in windows, but the flash bootloaders check box is greyed out for me. i clicked the details box and i am able to change the true false values for the flash column.
can i assume that i need to have the bootloaders set to true as they are set to false by default? also should i just true them all?

madmattco said:
Just wanting to be sure before I try and brick my phone lol.
When coming down from gigglebread, we need to use the froyo bootloaders i assume.
I dont know if its from running this in windows, but the flash bootloaders check box is greyed out for me. i clicked the details box and i am able to change the true false values for the flash column.
can i assume that i need to have the bootloaders set to true as they are set to false by default? also should i just true them all?
Click to expand...
Click to collapse
You wont brick your device if you don't flash bootloaders. Follow the instructions. If it wont boot, then flash again with bootloaders. This is a safety feature. If your device wont boot after flashing, then check flash bootloaders and flash it again.

Thanks for the quick reply Adam. Worked like a charm. Always a god job from you.

Adam... this is EXACTLY what i've been looking for. My wifes captivate hates every rom I've tried and I wanted to get her back to stock.
THANK YOU!

Adam,
Can I use this to go back to stock from CM7?

If you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
then your partitions are changed and it won't work and do not try it on Windows or Mac. On Linux, you can use this to correct the repartitioning problem and flash it. http://forum.xda-developers.com/showpost.php?p=17485056&postcount=23

Thanks for putting this together. I saw a need for this, but lacked the skills to completethis complicated task. Any chance of putting together an Odin package for it?
Edit
Can I dl your files and use the Odin 1 click creator to make an Odin flashable?

mrhaley30705 said:
Thanks for putting this together. I saw a need for this, but lacked the skills to completethis complicated task. Any chance of putting together an Odin package for it?
Edit
Can I dl your files and use the Odin 1 click creator to make an Odin flashable?
Click to expand...
Click to collapse
Hell no. Odin is closed source. It also uses closed source drivers. I don't support that at all.
You edited .. sure. If you want. I will have no part of Odin until the source is opened.

FOSS ....
Sent from my SAMSUNG-SGH-I897 using XDA App

c0ldburn3r said:
Adam... this is EXACTLY what i've been looking for. My wifes captivate hates every rom I've tried and I wanted to get her back to stock.
THANK YOU!
Click to expand...
Click to collapse
I know right LOL...
Sent from innerspace on my hacked telly...

i own an unlocked cappy.....
if i use this, will it lock my device again?????/

syanz87 said:
i own an unlocked cappy.....
if i use this, will it lock my device again?????/
Click to expand...
Click to collapse
No. Once unlocked, always unlocked.
Sent from my Inspire 4G

Worked well via Win 7 64bit, XP although it slowed up a bit (ran it live) and on Ubuntu 11.04. Switched back to pinnacle and all is right.
c0ldburn3r said:
Adam... this is EXACTLY what i've been looking for. My wifes captivate hates every rom I've tried and I wanted to get her back to stock.
THANK YOU!
Click to expand...
Click to collapse
Are you sure it is not simply an EBKAC error? I have to check my wife's every couple of Weeks. Simple uninstall of crap she downloaded and used for two mins plus delete cache seems to solve the problem.
Sent from my SAMSUNG-SGH-I897
Sent from my SAMSUNG-SGH-I897

Great job adam been waiting on something to be done like this with heimdall. Its a great utility and most of all open source. I've noticed less bad flashes with heimdall also and altogether less frustration.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.

This package worked great on both of my Captivate phones. You and Ben have done a great job along with all others who have supported the project. It will be awesome once your able to get the re-partitioning to work properly on Mac's along with Windows.

Great work. I didn't think it would work because one click unbrick didn't recognize my phone. But I opened the file, plugged in and it detected my phone. I didn't actually flash it, but I figure if it sees my phone, it should flash with no problem.

mrhaley30705 said:
Great work. I didn't think it would work because one click unbrick didn't recognize my phone. But I opened the file, plugged in and it detected my phone. I didn't actually flash it, but I figure if it sees my phone, it should flash with no problem.
Click to expand...
Click to collapse
If you have the phone ! Computer screen and heimdall recognizes your phone...hit start cause that's basically download mode
Sent from my SAMSUNG-SGH-I897 using XDA App

Read through noob guides but still having problems with the auto BL unlock

I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.

But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode

Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)

You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.

My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think

So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...

Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)

Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)

I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse

live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.

"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem

Thanks everyone
{
"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"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz

If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium