Database Users

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

[GUIDE] How to Install Cyanogenmod 7.1 from Stock 2.1

The procedure is quite simple.
Step 1.
Download the following tools:
Cyanogen Mod 7.1 for Xperia X8 (code named Shakira)
FlashTool
FXP030 kernel (2.6.29)
Step 2.
Step 2.1
Follow the guide located here to unlock your bootloader, do this before continuing with the rest of this guide it is important to have your stock firmware rooted for this step.
Step 2.2
Unzip flashtool to its own folder e.g. /Flashtool/.
Unzip FXP030 kernel to the Flashtool/firmwares/ folder - the directory should look 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"
}
Step 3.
Step 3.1
Open Flashtool and click on the 'Flash' button, select the FXP firmware from the list on the left hand side and click OK.
Step 3.2
Follow the on screen instructions.
Step 4.
Copy the update-cm-7.1.0-X8-signed.zip to the root of your MicroSD Card as shown below. (Please note that you can do this using a MicroSD Card reader OR your USB cable.
If you do not have a card reader then switch your phone on after flashing the FXP kernel and when you see the FreeXperia logo, repeatedly press the Back button until CWM loads. Once CWM has loaded scroll down to the Mounts and Storage menu. Once on the mounts and Storage menu scoll down to mount USB Storage and copy the update-cm-7.1.0-X8-signed.zip file to the root of the SD card.
Step 5.
Load CWM via the method described in Step 4 and select 'Install Zip from SD card.' then select 'Choose Zip from sdcard' and select the update-cm-7.1.0-X8-signed.zip that you copied over to the root of the SDCard in the previous step, Select the yes option using the volume buttons and let CWM work its witchcraft.
Step 6.
Go back to the main menu of CWM and select 'wipe data/factory reset'.
Next from the main menu of CWM select 'wipe cache partition'.
Finally from the main menu of CWM select 'Advanced' and 'wipe dalvik cache.
Optional
If you want the google apps installed you can download them here. To install them perform Step 4 through to Step 5 and instead of copying 'update-cm-7.1.0-X8-signed.zip' to the root of your sdcard, copy gapps-gb-20110613-signed.zip instead. All instructions in Step 4 and Step 5 that state you should use 'update-cm-7.1.0-X8-signed.zip' should use the file 'gapps-gb-20110613-signed.zip' instead.
Notes:
I'm having issues with the networking with this custom firmware, specifically the network (3G or WiFi) seems to 'drop' after any amount of small usage. If I use a Browser or the Market place for a short amount of time, they simply end up unable to load any pages whilst android reports that wifi/3g signal strengths are full. I tested the connectivity using ping commands from terminal and pings are succesfull. I'm unsure where the issue lies. I suspect however the issue is in the FXP Kernel, some people have reported using FXP 028 Kernel resolves the issues but I've been unable to find them.
Anyway I hope this helps people who are confused as to how to install this.
Credits:
Thanks to Paschalis for correcting an error in my wording.
Thanks go to dbts25 for pointing out mistakes and un-neccessary steps in the guide, sincethen the guide has been edited to be easier to follow and less convoluted.
Thanks go to rav3n_pl for the revised bootloader bundled with the kernel.

Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..

Paschalis said:
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Click to expand...
Click to collapse
Ah Yes, I mean stock. It's 2:34am... That's my excuse haha, between university and sleep deprivation the mistakes keep mounting hehe. Thanks for pointing that out anyways.
And yes, it seems this kernel has issues with data connectivity, and call volume as well for some odd reason. It boggles the mind as to why it's been labelled 'stable'. Stable usually means it's solid and won't fall over and die, plus data connectivity on an android handset is really a critical feature, if it is buggy the custom firmware should not be labelled as stable.

It really need custom kernel?

Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!

EL_BELLACO said:
It really need custom kernel?
Click to expand...
Click to collapse
Yes, if you don't use a custom firmware it will get stuck in a boot loop and be unable to boot.
Paschalis said:
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
Click to expand...
Click to collapse
If I come across it I will, I'll edit my guide to feature it as a work around for connectivity issues for people in the meantime, if it works correctly.
I've got to admit though, issues aside - it is amazing what the open source community is capable of creating. CM 7.1 looks absolutely fantastic, I love the boot animation.

I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.

termin8tor said:
.
Step 5.
Turn your phone on and repeatedly press the back button until you are displayed with the CWM menu. On this menu select 'install zip from sdcard' and then choose the 'choose zip from sdcard' select the cyanogenmod file you downloaded and let it do its thing.
Click to expand...
Click to collapse
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.

poisike said:
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
Click to expand...
Click to collapse
Can you please share the FXP028 kernel?

has any of you tried the dx kernel yet? with cynanogen mod 7.1

No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879

dbts25 said:
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
Click to expand...
Click to collapse
I've edited the guide to eliminate that pointless step in the original guide version, thankyou for pointing it out!
Additionally the google apps step has been added to the end of the tutorial.
tonks22 said:
has any of you tried the dx kernel yet? with cynanogen mod 7.1
Click to expand...
Click to collapse
Unfortunately the rom will not boot with the DX kernel, I tried it myself and it gets stuck in a boot loop.
rav3n_pl said:
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
Click to expand...
Click to collapse
I have included the correct kernel for the official cyanogenmod 7.1 rom and slipstreamed your edited loader into the kernel package for peoples convenience. Thanks for linking me to your post!
Hope this helps people!

It seems that this Rom and kernel [cm7] doesn't work.When i flash the kernel my SD is not recognized.And if i uninstall the kernel and try to flash the rom...i get a biiiiigg eror

i hope that they will also make a ROM that is compatible with stock kernel so that it will be easy to install... im having second thought of unlocking my bootloader because of this:
Before I start I must emphasise the fact that meddling with the bootloader is highly dangerous and will result in a hard brick if you don't follow proper instructions. Then, you will have to go and repair your phone by sending it to SE . I am not responsible if your phone dies on you because you didn't follow instructions or you screwed up somehow. I must also mention that this will probably void your warranty (rooting already probably voided it though) and that there is NO WAY to relock bootloader as of now.
Click to expand...
Click to collapse
i know they can make one because they are great programmer...

if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App

Paschalis said:
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??

mikel_0004 said:
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
Click to expand...
Click to collapse
There:
http://forum.xda-developers.com/showpost.php?p=17656148&postcount=1

Can it be installed WITHOUT unlocking the bootloader?
Thanks

thu001 said:
Can it be installed WITHOUT unlocking the bootloader?
Click to expand...
Click to collapse
I`m not 100% sure that cm71 rom will work on stock kernel...
When I flashed it under installed CM7 it stuck on bootanimation. Mybe full wipe? Not tried.

Hello
I installed on my Xperia X8 CM7.1 (I had version 2.1 of Android root), but it does not work the WiFi network and the 3G connection is disconnected, it did not work properly Market (having installed the GAPPS). My question, is there any way to get back to my terminal to android 2.1? I did a Back up of my system, but in trying to restore from CWM mistake I make, I guess it is for the kernel.

[Q] Without Recovery (For NINJAS)

Ninjas and Developers ...
... I have a Defy 525 MB actually brick, spent MS2Ginger4 and after the first restart did not carry over.
... not applied the SBF-Fixed and maximum I can do is to connect the device, but is boot looping.
I have only the logo image (M) when I apply any xxx ROM 4.5.1 or later, otherwise is just black with white light.
I guess my problem could be solved if I could apply the wipes, but when I access the original recovery menu commands are not accepted when tightening button to select (Power)
below is a picture of what happens ... I think not mount command can not apply the wipes
{
"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"
}
E: Can not mount / cache / recovery / command
E: Can not mount / cache / recovery / caller
E: Can not mount / cache / recovery / log
E: Can not open / cache / recovery / log
E: Can not mount / cache / recovery / last_log
E: Can not open / cache / recovery / last_log
Click to expand...
Click to collapse
It's impossible to get out of it, have tested dozens of sbf files, drivers of different versions, all updated, rsd lite different versions (also updated)
I tried windows 7 on windows XP 64 and 32
Is there any way to apply the wipes without the recovery? is there any way to fix the recovery?
... indeed, a dead end.
I have no money to another smartphone, I have no phone.
Please Help Me.
Thanks
SOLVED: New Windows, New Drivers and New RSD, brought defy back to life
Click to expand...
Click to collapse

hey,
look at this what Casper87 original have post, just rename the zip to update.zip put it on sdcard and try to apply with stock recovery
Casper87 said:
here it's a update file made by @nepotu ,wich contains bootmenu 1.1.8 , TWRP 2.1.0 , multiboot 0.5.3 and CWM 5.0.6
http://db.tt/o0kNpJMv
Click to expand...
Click to collapse
i think that work
Edit:
Ooh missed that u have flashed some full sfb after u got this error, than this update do nothing for u without su rights cwm or the other stuff don't work.
what sfb u flash at last?
ok finally bl7 can be root look at this -»
Chamelleon said:
Finally with help from people from many other forums Defy with BL7 was rooted.
For now we have no script to make it on the phone without wipe but I'm very happy that it's working.
Rooting Procedure
1. Wipe phone twice (2x make Wipe Data/Cache in stock recovery)
2. Flash 4.5.1-134 DFP-231 CN or 4.5.1-134 DFP-231 Retail.en.EU CEE (It doesn't matter what version of this two You flash but it must be the same with version from point 4).
3. Wipe again (Data/Factory Reset)
4. Flash rooted SBF 4.5.1-134 DFP-231 CN Rooted SBF Part.1, 4.5.1-134 DFP-231 CN Rooted SBF Part.2 or 4.5.1-134 DFP-231 Retail.en.EU CEE Rooted SBF
Click to expand...
Click to collapse
but without wipe the cache think it don't work, u can try to flash first part and than wipe.
Defy mit Android 4.0.4 CM9 RockZ

tks, but didnt work ...
when i flash rooted SBF, the phone enter on a booterror screen (bootloader)
... with a regular SBF 4.5.1-134_DFP-2312xxxxx.sbf the phone starts without boot error - but in bootlooping, when i enter on the recovery menu, i can change the options (navigate) but when press the powerbutton to select an option nothing happens ...
is like if i doesnt press anything
excuses for this poor english

have u flashed the right two sbfs to get this work?
is that over all in bootmenu? u can't enter a custom recovery or adb?
have u flash the bootmenu cwm update file?
think ur problem is that u can't get root rights to get the bootmenu work right, without su that is a better screensaver
Defy mit Android 4.0.4 CM9 RockZ

AnTerNoZ said:
have u flashed the right two sbfs to get this work?
is that over all in bootmenu? u can't enter a custom recovery or adb?
have u flash the bootmenu cwm update file?
think ur problem is that u can't get root rights to get the bootmenu work right, without su that is a better screensaver
Defy mit Android 4.0.4 CM9 RockZ
Click to expand...
Click to collapse
If u can read correctly his phone does not boot even after flashing sbf...
@op u sure sbf flashing completed correctly? U should try again
hav u flashed full sbf? Which one?
u need to tell us what things u did in order to recover?
Sent from my MB526 using xda premium

nogoodusername said:
If u can read correctly his phone does not boot even after flashing sbf...
Click to expand...
Click to collapse
ooh ^^ my mistake, i mixed up recovery and bootmenu >.> i just have more to sleep than 2h to read right what's going on ^^ SORRY
Defy mit Android 4.0.4 CM9 RockZ

okay you can do one more thing if your mobile is in warranty.
flash some sbf which makes your phone look like it has crashed and then take it to service centre near you and then convince the service guy that its DOA(motherboard has crashed) and so he will replace it...
since in my country a third party company (reddington) looks after motorola's service so the service guy knew nothing about bootloader and my mobiles state was completely dead so he replaced the motherboard(he told me motorola has instructed to replace the motherboard if phone is not able to start)..and got the phone working

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

sorry for the posting on a wrong area
Click to expand...
Click to collapse
... I need others tools, custom and experimental SBf's, others (and radical) ways to recovery my Defy ... No hope for a while ...
Ninjas cannot help me ...
...

radical.. go to a motorola service center and say u pay for a revert to stock ROM, because ur data is expensive or save the world or something like that. this reflash were rewriting the board from defy with this special omap tool and the bin file... that's really radical..
sry, the only thing i think that worked for u, was the rooted sbf's flashed. i wish ur defy good luck to revival from the nirvana:thumbup:
Defy mit Android 4.0.4 CM9 RockZ

Back to life
... I explained that I did everything to revive Motorola, reading several times to update the drivers and the RSD I could revive the device ... removed the old drivers and RSD, cleaned the registry, installed everything updated and did not work.
yesterday i formatted my notebook and installed Windows 7 Ultimate 64 in English, flash a 134_DFP-4.5.1-231 before taking on technical assistance (hopeless) and to my surprise the starts moved from bootloop.
Lesson is:
on a clean install of windows with drivers and RSD updated with the correct SBF file, your motorola is more likely to come back to life.
I tried everything, for 10 days and several times - today I can say with certainty, the problem was in the operating system of the notebook.
Thank you to everyone who helped

omarvin said:
... I explained that I did everything to revive Motorola, reading several times to update the drivers and the RSD I could revive the device ... removed the old drivers and RSD, cleaned the registry, installed everything updated and did not work.
yesterday i formatted my notebook and installed Windows 7 Ultimate 64 in English, flash a 134_DFP-4.5.1-231 before taking on technical assistance (hopeless) and to my surprise the starts moved from bootloop.
Lesson is:
on a clean install of windows with drivers and RSD updated with the correct SBF file, your motorola is more likely to come back to life.
I tried everything, for 10 days and several times - today I can say with certainty, the problem was in the operating system of the notebook.
Thank you to everyone who helped
Click to expand...
Click to collapse
That's great to hear that ur moto is on the right way now, shame on Microsoft
what ROM u want to flash now? i recommend CM9
Defy mit Android 4.0.4 CM9 RockZ

I think the device may not even be bricked, who go through this need should test the entire environment out of the device before taking to the service.
I used MS2Ginger and 7.2 CM ... now I'm happy with the ICS
Thank you AnTerNoZ ...

[4.2 Rom Release] FrozenPika10.1_V1.0.2

{
"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"
}
I DON'T HAVE TO SAY THAT THIS ROM NEEDS OFFICIAL ICS TO WORK...DONT SEND ME PM'S SAYING THAT THIS ISN'T WORKING YOU NEED OFFICIAL ICS FIRST NOT GB NOT AURORA NOT KALO NOT NOTHING ONLY ICS OFFICIAL!!!
Based on the latest Cm10.1 4.2.2 by Ivan Autumn
Remove useless apps
New adreno GPU drivers
Patched Rom for better memory usage
Better memory task killer
Smooth as this rom can be
Ringotnes from Nexus 4
Smoothscroll
Remove CRT
Kickasskernelizer
P.M.R Tweaks
Patched I/O
Partially fixed BT (Disconnects from time to time)
Add adb to kernel
Removed GPU
*REMEMBER* Dont use any kind of task killer
If you are on Official ICS or any other ICS based Rom
1)After updating to Official ICS
2)Unlock bootloader (pink screen)
3)Install CWM recovery
4)Format data/restore to factory settings
5)Format cache
6)Advanced-Format dalvik cache
7)Mounts-Format system
8)Install the rom
If you are Updating the FrozenPika
1)Format data/restore to factory settings
2)Format cache
3)Advanced-Format dalvik cache
4)Mounts-Format system
5)Install the rom
If you are any other .35 Rom (Stock,Kalo,CM7,MIUI)
1)Update to Official ICS
2)Unlock bootloader (pink screen)
3)Install CWM recovery
Code:
[U]FrozenPika10.1_V1.00[/U]
1)Initial Release
[U]FrozenPika10.1_V1.0.1[/U]
1)Ringotnes from Nexus 4
2)Smoothscroll
3)Remove CRT
4)Kickasskernelizer
5)P.M.R Tweaks
6)Patched I/O
7)Partially fixed BT (Disconnects from time to time)
8)Add adb to kernel
9)Removed GPU
10)More i can't remember :P
[U]FrozenPika10.1_V1.0.2[/U]
1)Try to disable the vsync
2)Remove seeder [COLOR="red"]*No more needed*[/COLOR]
3)Add [URL="http://forum.xda-developers.com/showthread.php?t=2113150"]CrossBreeder[/URL] [COLOR="Red"]*Seeder like feature*[/COLOR]
3)Replace superuser with SuperSU
4)Add AwesomeBEATS_v5
5)Edit kernel to have MTP as default
6)Some more tweaks
7)Change bootanimation
[U]Bugs[/U]
1)A bit laggy
2)Video recording dont work
3)No youtube videos for now
FrozenPika10.1_V1.0.2
*FLASH THIS PATCH AND ONLY FLASH IT IF YOU HAVING PROBLEMS WITH WIFI*
FrozenPikaSv1.0.2.zip*Latest based on Shendu*
FrozenPika10v1.6.8.zip*Latest based on cm10*
GPS Config
Thanks Ivan Autumn for CyanogenMod10
Thanks Genokolar for unlocking the the ICS the bootloader*
Thanks AndroidON for smooth scrolling the guide*
Thanks zepelinrox for kickasskernelizer script!!*
Thanks all the XDA developments for the great work they do!!

gooood!...any particular instructions?

vispo60 said:
gooood!...any particular instructions?
Click to expand...
Click to collapse
About?there is a change that kickass and supercherger dont run on first boot properly so you need to re run it there are two scripts on init.d and data folder!run it just to be sure

I have installed 4.0.3 Official ICS V100R001C00B927 rom. and I flash the rom of you and you say need CWM 5.0.2.7, and when I press CWM 5.0.2.7 by kalo's .but i press vol + and power, the machine is not in recovery. Now I do? expect people to help.
and now my machine does not use anymore.
and as well as the problems I asked above.
Thanks a lot
p/s: Available means when I remove the memory card and press vol + vol - and the power it out pink screen connected to the computer does not see the drive to copy the recovery should not know how! hu hu
machine error on startup :
image signature verify fail!
your boot/recovery image may have an incorrect signature
plesea update you image to a signature official one.
you canremove battery for power down.

quangcon1980 said:
I have installed 4.0.3 Official ICS V100R001C00B927 rom. and I flash the rom of you and you say need CWM 5.0.2.7, and when I press CWM 5.0.2.7 by kalo's .but i press vol + and power, the machine is not in recovery. Now I do? expect people to help.
and now my machine does not use anymore.
and as well as the problems I asked above.
Thanks a lot
p/s: Available means when I remove the memory card and press vol + vol - and the power it out pink screen connected to the computer does not see the drive to copy the recovery should not know how! hu hu
machine error on startup :
image signature verify fail!
your boot/recovery image may have an incorrect signature
plesea update you image to a signature official one.
you canremove battery for power down.
Click to expand...
Click to collapse
You cant use recovery above ics you need to flash now step2 from 4.0 to make it work again and then step2 for 2.3and then flash cwm

Looks great! I'm about to try. Thank you!

No wifi.
How could I fix this?

lucmhv said:
How could I fix this?
Click to expand...
Click to collapse
fix what?

I have to flash the ics file step 2 official update right? (More than 600m file right?)
phone in pink screen is not connected to the computer?
How can the connection?

No wifi.
pikachukaki said:
fix what?
Click to expand...
Click to collapse
Fix the WiFi, because it doesn't even turn on

I apply rom 2.3 official, press vol + vol-and power -> phone firmware update screen stands at no more vegetarian.
firmware update
step 1/2
unpacking
---------------------------------
The full update will take approximately 2 minutes
due to not turn off the device.
not run again.
I waited 30minutes it was still in this screen.
please help

ok ok ok
all ok, I flash the phone without the battery attached work.
Phone is launched, happy happy.
thanks you very much!

quangcon1980 said:
I have to flash the ics file step 2 official update right? (More than 600m file right?)
phone in pink screen is not connected to the computer?
How can the connection?
Click to expand...
Click to collapse
if you are on 2.3 you need only to flash step1 from ics!
lucmhv said:
Fix the WiFi, because it doesn't even turn on
Click to expand...
Click to collapse
You have another phone this is for pro not -51 i cant do anything use the wifi libs from aurora that works for you
quangcon1980 said:
I apply rom 2.3 official, press vol + vol-and power -> phone firmware update screen stands at no more vegetarian.
firmware update
step 1/2
unpacking
---------------------------------
The full update will take approximately 2 minutes
due to not turn off the device.
not run again.
I waited 30minutes it was still in this screen.
please help
Click to expand...
Click to collapse
Put step 2 update and press volumes and power again after step1 the phone just shut down
Sent from my U8800Pro using xda premium

ok ok ok
all ok, I flash the phone without the battery attached work.
Phone is launched, happy happy.
thanks you very much!

Added 928 version!!

Hi Pika Nice Work Mate. I Want Your Advice. I Am Kalo GB Should I Update To ICS New Version? How Is This NEw ROM? This Version ICEPIKA Is Rooted? In Titanium Backup Having Same Problem As Before I Have To Install Everyapp Sepratly?

husen4u said:
Hi Pika Nice Work Mate. I Want Your Advice. I Am Kalo GB Should I Update To ICS New Version? How Is This NEw ROM? This Version ICEPIKA Is Rooted? In Titanium Backup Having Same Problem As Before I Have To Install Everyapp Sepratly?
Click to expand...
Click to collapse
If you dont like to test dont leave kalo for now...although 928 is very good i dont recomended to ppl who don't want to test things..if you want although i found this version much better than the previous and no i dont have problem with titanium i used 5.4.0 and restore is working properly..and yeah root is out of the question we don't post custom roms without root only officials!!

Don't use for U8800-51
lucmhv said:
How could I fix this?
Click to expand...
Click to collapse
You have an U8800-51, forget ANY Rom with number B927 or B928. For ICS, only use the Aurora 4.1 (http://forum.xda-developers.com/showthread.php?t=1532662):cool:
Good luck.

pikachukaki said:
If you dont like to test dont leave kalo for now...although 928 is very good i dont recomended to ppl who don't want to test things..if you want although i found this version much better than the previous and no i dont have problem with titanium i used 5.4.0 and restore is working properly..and yeah root is out of the question we don't post custom roms without root only officials!!
Click to expand...
Click to collapse
Thanks buddy
Sent from my U8800pro using xda app-developers app

b928
B928 is excellent i highly recommend it.But after i flashed step one phone went into bootloop.So i copied step 2 in the sd and made a forced update pressing vol+ vol- and powerbutton and everything worked ok.Step 3 went smoothly.

[ROM STOCK] REVIVE YOUR DROID PRO! [Dec-08-14]

Hi guys! Maybe the tittle is getting you confused, but it's so, now you're gonna unbrick and revive your Droid pro and also install de last update ( 4.7.3.XT610.Verizon.en.US) for your phone. "IT MEANS IT'S ONLY FOR VERIZON MODEL". Just follow the next instructions and you'll get it .
I know like me, many of you have gotten a brick in your phone or have your phone bricked for the time being. The first step that we'll do is unbricking the phone.
First:
Mod Edit link removed
Second:
Extract both archives, install one of the two installers of RSD, once RSD is installed, search for the DROIDPRO_2.26.20.sbf file that extracted.
Third:
Let's get your droid pro into bootloader mode,for this keep volume up and volume down keys + power button at the same time for 5 seconds, if do it right you'll get onto a screen 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"
}
Now, connect your phone by usb cable to you computer, (Remember to have installed drivers in your pc) RSD show that your droid is online, click on the search button and select DROIDPRO_2.26.20.sbf file, once this is done click on start button and RSD will begin to flash the phone, wait for the process , when it finishes, your phone will reboot and alive again!
For update your for to the last version just go> Settings>About phone>check update after first update and reboot, phone will show a pop up message with a new update, download and install all necessary times.
Hope I could have helped you :fingers-crossed:

Very useful post, since noone before mentioned the bootloader mode, only fastboot that didn't work in my case. I need to try this when I get my phone back from a magician who is trying to fix it....
Regarding the post itself, you should clearly declare that the SBF is from American (VERIZON) model, since it will brick European ones even more than they already are

A question regarding the SBF file that you have provided..
Is it SBF of Stock GB 2.3.4..???
Imagine that I have rooted my phone but now I want to remove Root from my phone permanently, so in that case can I follow these steps to get the pure Stock ROM..???
I am totally new to Motorola and coming from hTC, so that's why asking so many questions..

Mohammad Hashir said:
A question regarding the SBF file that you have provided..
Is it SBF of Stock GB 2.3.4..???
Imagine that I have rooted my phone but now I want to remove Root from my phone permanently, so in that case can I follow these steps to get the pure Stock ROM..???
I am totally new to Motorola and coming from hTC, so that's why asking so many questions..
Click to expand...
Click to collapse
That the Pre-final update for "Verizon" motorola droid pro, android 2.3.3. And yes, If Your phone is the Verizon droid pro, you can flash this firmware. Don't worry, ask all what you need

migui0401 said:
That the Pre-final update for "Verizon" motorola droid pro, android 2.3.3. And yes, If Your phone is the Verizon droid pro, you can flash this firmware. Don't worry, ask all what you need
Click to expand...
Click to collapse
Yes I have "Verizon" version.. After flashing SBF of GB 2.3.3, I will get OTA of GB 2.3.4, right..??
Thank You..

Mohammad Hashir said:
Yes I have "Verizon" version.. After flashing SBF of GB 2.3.3, I will get OTA of GB 2.3.4, right..??
Thank You..
Click to expand...
Click to collapse
Yes, just go to settings, about phone and check update.

migui0401 said:
Yes, just go to settings, about phone and check update.
Click to expand...
Click to collapse
Why don't you work on developing CM9 and CM10..???
EDIT: Can't I use ADB commands on Droid Pro..?? I tried entering "adb devices" into Command Prompt to list attached devices but it showed nothing in the list.. Phone was connected with the PC in Charge Only mode..
EDIT 2: The link to RSD Lite is not working..

Mohammad Hashir said:
Why don't you work on developing CM9 and CM10..???
Click to expand...
Click to collapse
I'm student and really don't have time for developing a new rom, I'm considering, but for the time being, I cant.

Mohammad Hashir said:
Why don't you work on developing CM9 and CM10..???
EDIT: Can't I use ADB commands on Droid Pro..?? I tried entering "adb devices" into Command Prompt to list attached devices but it showed nothing in the list.. Phone was connected with the PC in Charge Only mode..
EDIT 2: The link to RSD Lite is not working..
Click to expand...
Click to collapse
First, which rom are you using? Is usb debugging on? Do you have the correct drivers?
Download RSD here: http://pc.cd/5cL

migui0401 said:
First, which rom are you using? Is usb debugging on? Do you have the correct drivers?
Download RSD here: http://pc.cd/5cL
Click to expand...
Click to collapse
I am using the Stock GB 2.3.4, and yes USB Debugging is enabled.. I have the drivers installed..

Mohammad Hashir said:
I am using the Stock GB 2.3.4, and yes USB Debugging is enabled.. I have the drivers installed..
Click to expand...
Click to collapse
I don't know but, maybe ADB is not supported in stock. Now, i'm going to flash stock firmware in my phone, i'll let you if ADB works for me.

I bricked my phone, flashed the SBF using RSD Lite but still getting bootloop, Droid logo in red color coming again and again..
Please help..
EDIT: I got it working now, after flashing the SBF, I went into recovery (R+M then Volume up and down keys) and performed "wipe data/factory reset" and "wipe cache partition", and now it is working..
Thank You..

Mohammad Hashir said:
I bricked my phone, flashed the SBF using RSD Lite but still getting bootloop, Droid logo in red color coming again and again..
Please help..
EDIT: I got it working now, after flashing the SBF, I went into recovery (R+M then Volume up and down keys) and performed "wipe data/factory reset" and "wipe cache partition", and now it is working..
Thank You..
Click to expand...
Click to collapse
Every time you flash the firmware over a custom rom, you must do a factory reset from recovery.

migui0401 said:
Hi guys! Maybe the tittle is getting you confused, but it's so, now you're gonna unbrick and revive your Droid pro and also install de last update ( 4.7.3.XT610.Verizon.en.US) for your phone. "IT MEANS IT'S ONLY FOR VERIZON MODEL". Just follow the next instructions and you'll get it .
I know like me, many of you have gotten a brick in your phone or have your phone bricked for the time being. The first step that we'll do is unbricking the phone.
First:
Download RSD Lite 6.1.x from here: http://pc.cd/5cL
And the SBF files from here https://my.pcloud.com/#page=publink&code=XZ3EMZwDjXjAu2s7BETYRGNfKhWL5MpSa7
Second:
Extract both archives, install one of the two installers of RSD, once RSD is installed, search for the DROIDPRO_2.26.20.sbf file that extracted.
Third:
Let's get your droid pro into bootloader mode,for this keep volume up and volume down keys + power button at the same time for 5 seconds, if do it right you'll get onto a screen like this,
Now, connect your phone by usb cable to you computer, (Remember to have installed drivers in your pc) RSD show that your droid is online, click on the search button and select DROIDPRO_2.26.20.sbf file, once this is done click on start button and RSD will begin to flash the phone, wait for the process , when it finishes, your phone will reboot and alive again!
For update your for to the last version just go> Settings>About phone>check update after first update and reboot, phone will show a pop up message with a new update, download and install all necessary times.
Hope I could have helped you :fingers-crossed:
Click to expand...
Click to collapse
These links no longer work :crying:
Can someone please help me with these sbf files.
I bricked my Droid Pro would love getting it back.
Thanks

Newyork! said:
These links no longer work :crying:
Can someone please help me with these sbf files.
I bricked my Droid Pro would love getting it back.
Thanks
Click to expand...
Click to collapse
Try again.

migui0401 said:
Try again.
Click to expand...
Click to collapse
Tried.
:crying:

Newyork! said:
Tried.
:crying:
Click to expand...
Click to collapse
Try the links on the Op first post. In the beginning of the thread.

migui0401 said:
Try the links on the Op first post. In the beginning of the thread.
Click to expand...
Click to collapse
Thanks!!
Downloading it now, will try tomorrow.
I hope i won't need anymore help

migui0401 said:
Every time you flash the firmware over a custom rom, you must do a factory reset from recovery.
Click to expand...
Click to collapse
Hello,
and if I try push power + R +M and there is onluy sign "!" and Android symbol? And there is no possible to choose any option to wipe data?

baroo89 said:
Hello,
and if I try push power + R +M and there is onluy sign "!" and Android symbol? And there is no possible to choose any option to wipe data?
Click to expand...
Click to collapse
Press both volume buttons when you see the exclamation mark, and you will get the menu.