Database Users

[HOW TO] Get back to stock Bell rom!

These are the steps i took to get back to the Stock bell rom. I take no credit for this method, NFHimself made the scripts, and mods for deodexing.
This takes an hour at least.. Make sure your battery is FULLY charged, Do a backup first as well to save your sd card contents.. You have to do a factory reset after the process is complete.
1)reinstall a fresh sbf of the french 2.1.1 and login to motoblur. French sbf can be found in this thread, Close to the bottom of the page.
2) enable usb debugging.. menu, settings, applications, development, then check usb debugging
3) go to NFHimselfs deodex/mod thread here
4)download Version 9, and extract it to your computer
5)Run the menu.bat file
6) choose the root option. and follow the instructions. If it doesn't complete successfully, unroot and try again. Took me a couple times to get my phone rooted properly.
7) once root is complete, choose restore phone. This will automatically download the files needed to get you back to the stock rom. It will take a little bit of time to download, so have a drink or smoke or something.
The restore will take an hour or so to complete. Be patient.
I got to the point where it said waiting for phone to shutdown, so i pulled the battery and did it manually. Once my phone booted back up again, it was on the stock bell rom.
Thanks to all who helped me! Y2whisper and kieller from the support.motorola forums.
Don't forget to thank NFHimself.
NOTE: I had to do a factory reset to get the Market app back.
I managed to get the bell update with no problems!

right on I was wondering how I would get back to the stock Bell.....I'm running the French 2.1.1, so when the time comes I can sit back for an hour or so and bring the phone back to stock...........yaaaahoooo......

nate_benji were you on the french 2.1.1 before you did this?? cause I'm on 2.1.1 and I am rooted, just wondering if I have to do all over... flashing 2.1.1 again and root??? but I guess it can't hurt with a fresh install......guess I'm getting lazy in my old age...lol

dillfever said:
nate_benji were you on the french 2.1.1 before you did this?? cause I'm on 2.1.1 and I am rooted, just wondering if I have to do all over... flashing 2.1.1 again and root??? but I guess it can't hurt with a fresh install......guess I'm getting lazy in my old age...lol
Click to expand...
Click to collapse
Yes, i was on the french 2.1.1. The only reason i did a fresh install of the french 2.1.1 sbf is because the rooting method is a little different than using gingerbreak. I tried with a normal root, but it didn't work. NFHimself's mod/deodex application has the root option built in. That's what I used, and it worked well.

What's the benifit over the french 2.2.1 ???

YBrazeau said:
What's the benifit over the french 2.2.1 ???
Click to expand...
Click to collapse
The new update, I presume.
If I get bored between now and an international release or leak of GB then perhaps I'll give this a shot too. Thanks for sharing it, guys! Great work as always.

YBrazeau said:
What's the benifit over the french 2.2.1 ???
Click to expand...
Click to collapse
The benefit is you get the bell updates, who knows when the other carriers will release the gingerbread updates. Mind you bell is slow at releasing anything..
Sent from my MB860 using XDA App

Thanks nate, then when the time comes that's exactly what I shall do......

The biggest benefit of this would probably be that when you do this it would be really hard to tell if you ever modded the phone. Also Bell is likely to get the Gingerbread update before people in Europe.

I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..

Could it be possible to get a direct link to the French 2.2.1 sbf, this way everything needed is in one location?
Thanks

capercb said:
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Click to expand...
Click to collapse
I am having this exact same issue. Is the mmcblk0p3 file that is included within the backup_OLYLA_U4_0.37.4.tar.gz that NFHimself posted possible corrupt?

davisx said:
I am having this exact same issue. Is the mmcblk0p3 file that is included within the backup_OLYLA_U4_0.37.4.tar.gz that NFHimself posted possible corrupt?
Click to expand...
Click to collapse
I don't think so. i did it from a fresh flash of 2.1.1 and it worked fine. you just have to make sure you rooted using his scripts. that was a problem i was having using his app before i used these scripts.

capercb said:
I am doing a restore and got a tar crc error and a error on restoring mmcblk0p3 - should i wait till it finish .....i don't like the the crc error..thanks 1 done cat /data/local... ! bus error shsu (no boot) failed to boot 2 ...starting rsd mode, reflashing now...anyone know why there is a crc fail..
Click to expand...
Click to collapse
I had that too i believe. Not sure why mmcblk03 failed, but all the rest passed for me. Did you re-sbf and try it again?

fearthefox said:
Could it be possible to get a direct link to the French 2.2.1 sbf, this way everything needed is in one location?
Thanks
Click to expand...
Click to collapse
I updated the original post, with a link to another thread that has a list of all known atrix sbf's. The french one is close to the bottom of the list.

Is this the one you are referring to...
Branding: Retail France
Version: 2.1.1 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: N/A
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
As you opening post says french 2.2.1 and I cannot find that on the page you linked to.

nate_benji said:
I had that too i believe. Not sure why mmcblk03 failed, but all the rest passed for me. Did you re-sbf and try it again?
Click to expand...
Click to collapse
Ya I got it but really weird ..notice when the program expands there is no mmcblk03 in the file also when it finish it keep coming up as timeout so I removed it from usb and pulled out the battery restarted and dl the update..It seems like a good update so far..ty
Sent from my MB860 using XDA App

Hi,
I removed partition 3 from the backup, it's your Motorola pds partition, it's not necessary to get back to stock, there are no sbf files that overwrite it. I also updated the atrix mods app to not reference partition 3.
Cheers!

NFHimself said:
Hi,
I removed partition 3 from the backup, it's your Motorola pds partition, it's not necessary to get back to stock, there are no sbf files that overwrite it. I also updated the atrix mods app to not reference partition 3.
Cheers!
Click to expand...
Click to collapse
Awesome! Thanks for creating the scripts, and the app. Made it possible to get me back to the stock bell rom, without a cwm backup. Now that reminds me, time to root, install cwm and do a backup!
Thanks again NFHimself..

fearthefox said:
Is this the one you are referring to...
Branding: Retail France
Version: 2.1.1 Full
Android Version: 2.2.2
Bootloader Version: N/A
Webtop version: N/A
Requires RSD Lite 5.0.0
Requires Moto Android (De)packer 1.3 to edit.
As you opening post says french 2.2.1 and I cannot find that on the page you linked to.
Click to expand...
Click to collapse
Sorry thats a typo, it should be 2.1.1

STEP BY STEP How to install CM7.1.0 - FreeXperia Project

streamnlnl said:
Sorry for the late reply , I just see those post.
I haven't a x10 anymore. I have a arc S now.
So i don't read all the post on the x10 tread. I can't help anymore with the most question . But I have a idea. Just copy past my first post (or edit to your liking) and open a new tread. That person must be someone that actually can help.
If that is done, let me know so I can contact a mod and close this tread.
It hoe if I have helped somebody.
Greets Streamnlnl
Click to expand...
Click to collapse
After seeing the same question over and over again, I'm going to try to make a step by step guide for install this ROM.
So that the main tread will be as clean as possible.
In the second post, I will post tips and the most commen Q & A.
If you want to discuss about this ROM, please do that here
Now let's get started...............
First you need to unlock your boatloader.
You can read and ask ALL of your questions about unlocking here
(If you don't have a unlocked boatloader, there is a solution for that. But I suggest to unlock your boatloader. FXP team make this for unlocked bootloader. So you be warned. If you still want to install this with a locked bootloader, I suggest to go to cobrato tread, thank him for this.)
When you have a unlocked bootloader you are good to go to install this beautiful ROM .
THE ROMS ARE NUMBERED BY WEEK NUMBER.
I call the ROM FXP(week number), because I don't always have time to keep this up_to_date. Sorry for that!
Download the 2 files in this post (FXP(week number) & GAPPS ADDON)
FXP(week number) will be called something like this: update-cm-7.2.0-RC0-es209ra-KANG-signed
There are 3 files in update-cm-7.2.0-RC0-es209ra-KANG-signed
#Flashtool
#FXP(week number)
#unlock
Unzip those files on your PC
Put the map FXP(week number) (The one you just unzipped) and GAPPS ADDON (the one you have download at the start) somewhere on your SDcard.
Open flashtool and run the X10FlashTool.exe
No press Flash.
You will see just one file.
#x10i
Now flash that one, with this you will get the CWM.
After this reboot your phone en press repeatedly on the back button till you enter CWM.
Here you do:
1) wipe data/factory reset
2)wipe cauche partition
3)advanced ====> wipe Dalvik Cache
Now you can install the ROM:
1)Install zip from SDcard =====> choose zip from sdcard ===> and then go to the place where you have left FXP(week number) on your sdcard.
2)install now GAPPS ADDON, the same way you have install FPX(week number).
When it's done reboot your phone and enjoy
If I have write something what isn't correct.
PM me and I will edit it correctly.
To keep this up-to-date, also PM me for the bugs or tips.
So that I don't need to read every single post.
Thanks in advance
.

Tips:
# For faster bootup, just add this line in build.prop:
Code:
debug.sf.nobootanimation=1
Also, if you experiences battery drainage, simply change your governor from performance to ondemand (thanks to Hzu)
# For settings and explanation about CyanogenMod Settings look here
and for the standard home screen (adw-launcher) look here
Q&A:
Q: What are the changelog for latest version?
A: at the time of writing it's version FXP030 and you can look for the changelog here
Q: Is there any ETA for the next version?
A No, but if you want you can contribute here
Q: I really want to thank the dev, how can I do that?
A: You can hit the thank you button on his post,
or you can donate here
Q: Are there more pics about this ROM available?
A of course, You can look here , here or here
Q: Can I use Rom Manager with this Rom?
A: Yes you can
Q: Are all of the cm settings available
In this rom?
A:Yes
Q:
A:
.

Great job!!!!

For faster bootup, just add this line in build.prop:
Code:
debug.sf.nobootanimation=1
Also, if you experiences battery drainage, simply change your governor from performance to ondemand.
I found this from the past few releases and some people complained about battery drainage so I tried to find the source and this is what I found.
J said they set it to performance so that the phone will be faster and easier to test out features.
Sent from my X10 using XDA App

Maybe someone here can help me. I've followed those instructions but when I go to CWM based recovery and pick install from sd card it keeps saying cannot mount /sdcard
xrecovery on the other hand reads it just fine.
Maybe this is related to other roms not detecting my sd card.
Any suggestions?

Has anyone tried to flash dooms fxp for unlocked bootloaders with CM7??

which version of cwm do i use?? im using doomlords kernel where it has two versions of cwm and xrecovery

fcb1 said:
which version of cwm do i use?? im using doomlords kernel where it has two versions of cwm and xrecovery
Click to expand...
Click to collapse
Read the op mate, it tells you how to install the rom, the part that says flash the fxp firmware with flashtool will give you the correct recovery, you can not use Dooms cwm's as you also need the kernel in FXP.
From the op....
Now flash FXP, with this you will get the CWM.
Click to expand...
Click to collapse

Any ideas guys? I even flashed back to 2.1 and started over but in CWM I keep getting can't mount /sdcard

Can you please give us some more info?
What exactly have you did?
Like, do you have a unlocked bootloader? Did the flashtool say that it was successful?
What kind of baseband do you have. Etc etc.

streamnlnl said:
Can you please give us some more info?
What exactly have you did?
Like, do you have a unlocked bootloader? Did the flashtool say that it was successful?
What kind of baseband do you have. Etc etc.
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader. The Free Xperia screen comes up and I press the back button to get into recovery.
I'm running the .71 baseband and have had no problems flashing from flashtool.
Before I was running a custom 2.3.3 rom and I unlocked the bootloader, flashed in the FXP custom kernel and got the same problem of mounting sd card in recovery.
I just went back to stock 2.1 (This rom reads my sd card just fine), flashed .71 baseband, flashed FXP kernel and still got the same error when I entered recovery to install custom zip.

Why mounting sdcard?
If you put the right files before flashing on your card. You don't need to mount your card.
Can you access your card trough the menu?
Install zip from sdcard?
Edit.. i was reading your latest post on xda and are you sure that you have successful unlocked your bootloader/
in HOW-TO]UNLOCK bootloader for X10 you find a tool in the second post (s1tool.7z).
If I rember it correctly, when you run it you can see 2 different things in the fist line
RUNNING S1_EROM VER "R8A013" ======> locked bootloader
or
RUNNING S1_EROM VER "r8A013" ======> unlocked bootloader
(can anyone confirm this?)
@takerfan you got a PM

streamnlnl said:
Why mounting sdcard?
If you put the right files before flashing on your card. You don't need to mount your card.
Can you access your card trough the menu?
Install zip from sdcard?
Click to expand...
Click to collapse
That's the thing, when I go to install custom zip from the menu it gives me an error that says "Can't mount /sdcard"
edit: Yes, I ran the tool and the r was lowercase. I even did recover to relock the bootloader and the R became uppercase and I again unlocked it.
edit2: I think I should mention this..whenever I flash a 2.3 rom whether it's stock or custom, the rom does not detect my sd card. Once I go back to 2.1 it does. Do you know why this is the case?

Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.

jusiek said:
Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.
Click to expand...
Click to collapse
That is nothing, ignore the message.
takerfan said:
That's the thing, when I go to install custom zip from the menu it gives me an error that says "Can't mount /sdcard"
edit: Yes, I ran the tool and the r was lowercase. I even did recover to relock the bootloader and the R became uppercase and I again unlocked it.
edit2: I think I should mention this..whenever I flash a 2.3 rom whether it's stock or custom, the rom does not detect my sd card. Once I go back to 2.1 it does. Do you know why this is the case?
Click to expand...
Click to collapse
Try unmounting the sd card from mounts & storage menu in recovery and choose install zip from sdcard again. See if this helps.
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
xXHITMANXx508 said:
Has anyone tried to flash dooms fxp for unlocked bootloaders with CM7??
Click to expand...
Click to collapse
Yep, works fine here.

jusiek said:
Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.
Click to expand...
Click to collapse
It's because you haven't unlocked your bootloader, the phone would not allow you to flash unsigned .sin files, which means you can't flash the FXP kernel.

jusiek said:
Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.
Click to expand...
Click to collapse
Are you saying that after flashing the kernel it still says turn on debugging bla bla? That's normal. See if it shows freexperia upon turning on your phone.
If not, then you have not unlocked your bootloader.
Sent from my X10 using XDA App

Hzu said:
That is nothing, ignore the message.
Try unmounting the sd card from mounts & storage menu in recovery and choose install zip from sdcard again. See if this helps.
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
Yep, works fine here.
Click to expand...
Click to collapse
In mounts and storage it only gives me the option to mount sd and when I select that it gives me the same error. Xrecovery works fine but I can't flash cm7 with that.

I've made the leap and installed this ROM. First of all I want to say how brilliant it is and it'll obviously only get better. I've also installed FXP28 on my wife's x8 with similar results. Great work FXP team!
So on to my problem... when I go to bed my phone has switched itself off and my alarm hasn't gone off. When I switch it back on there was still 20 odd % battery remaining. This has happened twice. I've been running the govener on 'on demand'. One thing that is odd is that the phone has a flashing green light which presumably means it is in fact not off. The only way to wake it up though is to hold the power button.
Does anyone have any suggestions? Thanks.

Ok. Another problem. Cannot get wifi tether to work at all... also USB tethering doesn't work and could only get barnacle to work with no security.
Is anyone having success with tethering.
PS. I never had a problem with my previous rom - Wolf's!
Sent from my X10i using XDA App

Updated phone to 2.3.6, no service, cant install radios

long story short I havent used this phone for months and I just sold it and once I updated the phone it said no service so I did research and tried updating my radio but I keep getting signature verification failed... Whats the matter?
2.3.6
bb: NO DGSXXF1
build:grk39f
kernel v: 2.6.35.7.gf5f63ef [email protected] #1
What am I doing wrong? I would like to ship the phone out today

can somebody please tell me how to return the phone to the stock version that radios work!!!! man this is driving me crazy I just wiped everything off my phone now I think I gotta root it again

Seems like you flashed a bad image, the obvious solution would to be dig deeper on the image you flashed to find something more up to date.
Sent from my Nexus S using XDA App

n023b said:
long story short I havent used this phone for months and I just sold it and once I updated the phone it said no service so I did research and tried updating my radio but I keep getting signature verification failed... Whats the matter?
2.3.6
bb: NO DGSXXF1
build:grk39f
kernel v: 2.6.35.7.gf5f63ef [email protected] #1
What am I doing wrong? I would like to ship the phone out today
Click to expand...
Click to collapse
I'd download the full ROM version of the latest firmware (available in this forum) and re-flash from recovery, probably worth wiping system/data/cache etc via recovery first.
The full ROM will include the latest radio image for your handset along with everything else it needs.
Best of luck.

Most radio problems can be fixed by restoring an EFS backup.

Flash the latest stock from and radios via fast boot.
Sent from my Nexus S 4G using xda premium

No need... Ull need root explorer and a radio that your phone works with.
Flash the radio first ( no service still)
Then go into root explorer and your going to go.into efs file and move the following files to root of SD
Nv.log
Nv_Data.bin
Nv_Data.bin.md5
Once u do that... restart your phone and u will be fine.
Note the once u move the files into SD Card... the files will automatically be in efs file again and remain in SD Card as well
-Google

iGoogleNexus said:
No need... Ull need root explorer and a radio that your phone works with.
Flash the radio first ( no service still)
Then go into root explorer and your going to go.into efs file and move the following files to root of SD
Nv.log
Nv_Data.bin
Nv_Data.bin.md5
Once u do that... restart your phone and u will be fine.
Note the once u move the files into SD Card... the files will automatically be in efs file again and remain in SD Card as well
-Google
Click to expand...
Click to collapse
Did this the other day forgot to tell you guys it worked. Thank you!

DEFY Becomes DEAD After Flash-- Help

My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.

cute_kayani said:
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
Click to expand...
Click to collapse
I think I got the answer for you......
Use below mentioned steps and share the outcome:
1. Download the compressed SBF and extract using any software like 7zip or something - http://www.mediafire.com/?s3uc8cb782w1oue
[Note: Do not use any download manager while downloading.]
2. Use RSD Lite to flash the phone with the SBF file;
3. After flashing let the phone boot up and hopefully it will resolve the issue.
However if the phone is still in boot loops then try entering Stock recovery and wipe data/format and wipe cache also.
Please use the above steps and share the outcome.

ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,

cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!

okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do

pranks1989 said:
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
Click to expand...
Click to collapse
I understand your concern and I appreciate your comment however, I would like to point this out that this firmware is for "India, Indonesia, Malaysia, Philippines, Thailand, Vietnam" and its safe to flash I have flashed it multiple times and its Rootable and even my flash is healthy.
You may visit this link and Control+F "JRDNEM_U3_3.4.3-33-1":
http://and-developers.com/sbf:defy
The chinese firmware which is suspicious of burning flash is "China - JDGC_U6_0.26.0" [Correct me if I'm wrong.]
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
cute_kayani said:
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
Click to expand...
Click to collapse
You may use this firmware or any different firmware from this link : http://and-developers.com/sbf:defy
The ROM which I have given you link is Rootable however not down-gradable.
You may refer this extract from All-in-one-Guide-for-Defy
SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.6, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
ATTENTION: This CG 7 Version is NOT rooteable. You wont be able to flash a lower version ROM nor Root to use CWM.
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
Official SBFs
Here is a list of all the OFFICIAL SBFs, meaning they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.
Ref == http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
The only thing which is important here will be to use a Froyo or newer version SBF.

Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now

cute_kayani said:
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
Click to expand...
Click to collapse
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!

Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now

cute_kayani I think you double posted mistakenly....
Have already answered your query above
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Click to expand...
Click to collapse
---------- Post added at 09:26 PM ---------- Previous post was at 09:12 PM ----------
One important thing for your information is the reason behind those black screens was that you must have flashed Froyo SBF before; which was not down-gradable and now at this point you were trying Éclair which resulted in this issue.
So, the Downgradibility of your previous flashed SBF was causing this issue.
Now, as you have flashed this Froyo SBF; so, now onward in case you need to flash you phone you need to use SBF which should be Froyo or newer and must have “3.4.3” or later Build Numbers.
Hope this helps someone who needs this information.

okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.

cute_kayani said:
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
Click to expand...
Click to collapse
LOL its official Froyo it might have more bugs

haha okay i am moving to miui.... but from past 7 days my defy remains dead due to Miui weekly rom update
hopefully this time miui wont make any problem

LOL
All the very best this time ..
You know what last week I also updated to MIUI 2.3.23 and my wifi was not working with that ROM however, it was working fine with my CM9 as I had dual boot.
Please update me if you also face this issue with the MIUI 2.3.30

currently am on 2.3.23 every thing is okay, and wifi also working now am updating it to 2.3.30. will tell you if there any wifi bug.

Will wait for your review!!

More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.

cute_kayani said:
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
Click to expand...
Click to collapse
Lol 2GB internal memory occupied
Yesterday night I flashed with MotoGinger III for a change... so far so good. However, AutoWifi fix is resetting my wifi pwd every 15 mins or so ..

Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.

Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.

[Q] Really weird problem. no sound on call in modified ROM's

problem: on 3 dif. roms (slim, AOKP) sometimes there is no sound on calls for both sides. more interesting my hung up command take no charge and the call actually hung up after a minute (then it appears 'no network') or on reboot/turn off. this happens randomly on 4.2.2 roms. (and ivv tried 4.2.1 slim also)
on stock 4.2.2 the problem does not exist.
tried to switch back and forth from stock to modified roms but nothing.
what do you guys think?

Make sure you're on the latest bootloader and radio.

Is this ok?

elada22 said:
Is this ok?
Click to expand...
Click to collapse
No, that's an old radio and you probably have the old bootloader as well then.
Here: http://forum.xda-developers.com/showthread.php?t=2147194

i flashed both radio and BL but now it shows:
baseband version: unknown
imei: (blank)
no network at all of course.
should i try and flash the zip file again?

elada22 said:
i flashed both radio and BL but now it shows:
baseband version: unknown
imei: (blank)
no network at all of course.
should i try and flash the zip file again?
Click to expand...
Click to collapse
What??
Try rebooting. Maybe flash again. Never heard of that before..

same result. anything else maybe? back to stock rom?

elada22 said:
same result. anything else maybe? back to stock rom?
Click to expand...
Click to collapse
What rom is that you're using? What is that "du_mako"..?

dirty unicorns
http://forum.xda-developers.com/showthread.php?t=2239428

Hm. I have no clue what could be the issue. Hopefully someone else can chime in.

im going to try and flash the zips separately
wish me luck
edit:
it didnt work
trying flashing back to stock rom
still no imei or baseband

elada22 said:
im going to try and flash the zips separately
wish me luck
edit:
it didnt work
trying flashing back to stock rom
still no imei or baseband
Click to expand...
Click to collapse
Are you using lte? Try switching to 2g if so.
However, htf did your imei get erased..??

flash the factory image should fix it up
the radio you flashed sound lik it was corrupted

not lte.
3g - 2g toggle both available on my carrier. not relevant.
my basebans is gone and so is the imei after flashing radio&bootloader.
take a look at this thread, i think its relevant.
http://forum.xda-developers.com/showthread.php?t=2060780

immunityx said:
flash the factory image should fix it up
the radio you flashed sound lik it was corrupted
Click to expand...
Click to collapse
im flashing this deodexed stock rom but still the same
http://forum.xda-developers.com/showthread.php?t=2010887

Nope that wont do it you need to flsah the factory image not just stock rom, the image contains stock bootloadr and radio and rom,kernel all in one
download here
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Extract it using winrar or winzip you shoulld see a bat file called flash-all
Boot your phone to bootloader by power button +vol down ill see s the green android
plug your phone up via usb cable to computer and run that flash-all bat file

Are you 100% sure both the radio and bootloader were for the n4 and not another device

immunityx said:
Nope that wont do it you need to flsah the factory image not just stock rom, the image contains stock bootloadr and radio and rom,kernel all in one
download here
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Extract it using winrar or winzip you shoulld see a bat file called flash-all
Boot your phone to bootloader by power button +vol down ill see s the green android
plug your phone up via usb cable to computer and run that flash-all bat file
Click to expand...
Click to collapse
ivv intalled the drivers like last time from here
http://forum.xda-developers.com/showthread.php?t=1992345
but look at the bat file trying to run....
in bootloader mode it shows the baseband version as the updated one - 48.
more details:
CARRIER INFO: none
SECURE BOOT: enabald
LOCK STATE: unlocked

username8611 said:
Are you 100% sure both the radio and bootloader were for the n4 and not another device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147194

elada22 said:
ivv intalled the drivers like last time from here
http://forum.xda-developers.com/showthread.php?t=1992345
but look at the bat file trying to run....
in bootloader mode it shows the baseband version as the updated one - 48.
more details:
CARRIER INFO: none
SECURE BOOT: enabald
LOCK STATE: unlocked
Click to expand...
Click to collapse
Grab the fastboot and adb android files and extract them in the same folder as the flash-all
ACtually i attached it here