Database Users

[HELP] Milestone 2 bricked (SBF Not Working, No Recovery, No Battery Charge)

Hey i will try to be as precise as possible. I'm posting in this section because in the general section the help isn't as effective as here.
Here is my problem:
A few days ago i flashed GB MIUI on my Milestone 2 everything worked perfectly and i used the phone a whole day. That night i've put the phone to charge and went to bed. Il the morning when i push the power button the phone didn't boot. I was stuck at the first M bootscreen (Red at the time).
I wasn't able to do anything no recovery the phone didn't seem to be charging so i decided to flash Stock FR SBF (One i used many times)
Once completed i let the phone tying to Boot for about one hour. After that i pulled the battery out and tried to get to recovery but no success. Holding the X button while booting wasn't getting me to recovery because the wouldn't get pass the First Moto bootscreen (Recovery open after that).
So i've flashed since then a handful of SBF from and-developpers:
2.2 FR
2.2 CH
2.2 UK
2.2.2 FR
2.2.2 CH
2.2.2 UK
2.2.2 Hong Kong
2.2 China
Official GB Leak signed
Still wasn't able to get throught the first moto bootscreen.
r2beta0 had an idea so if someone can please help me get through this. I think i'm done with flashing things...
r2beta0 said:
Hmm, I just had an idea that needs elaboration. As we know we can flash any partition of the phone using sbf_flash or RSD Lite. If his problem really can be solved doing a data wipe it would be also solved by flashing a new "empty" CG37.smg. It doesn't need to be signed because /data is not checked by bootloader. So, we need a Milestone2 /data empty image (CG37.smg). One could do a data wipe and take the image of with dd command, but it would be a HUGE file (6,5 GB). I don't know if we can use a smaller file just to clean his /data. Maybe someone can elaborate that.
Click to expand...
Click to collapse
dangpzanco said:
Maybe you can flash a modded SBF, with a modded CG37 and a new CG that points to addresses from the middle of data to its end, and make two partitions with data spare space for the dual booting project, is that even possible?
Well, at least when you pack and zip it the SBF won't be hard to upload.
PS: Does the Milestone 1 full SBFs have the data CG included?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
I tried holding X button while i plug the phone the Wall charger but no sucess either. I just can't get to the screen with the Exclamation point...
I've tried to be as precise as possible to help people who will or already tried to help me. Please don't delete my thread or move it after i've put so much effort in this...
I've search in hundreads of threads around different forum XDA is my last chance...
I thanks everyone who will take some time to help me or even at least read this.

I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here

r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
I just did it no results still the same!
I don't think it looks good.
I didn't pull out the battery yet i wan't to give it a chance. I'll edit this post

Something is very wrong with your phone. I think your best bet is to reflash stock SBF and send your phone to warranty.

Did you try other options "dumb"? For example, change the simcard, change the sdcard, charge the battery with other alternative (universal charger)

r2beta0 said:
Something is very wrong with your phone. I think your best bet is to reflash stock SBF and send your phone to warranty.
Click to expand...
Click to collapse
Emacore said:
Did you try other options "dumb"? For example, change the simcard, change the sdcard, charge the battery with other alternative (universal charger)
Click to expand...
Click to collapse
I removed the sim card removed the sdcard, charge the battery with a milestone 1 avec two different charger. No results
@r2beta0 i think you are right i'll wait i someone help me until tomorrow evening if not i'll send it back to moto.

Have you tried to use sbf_flash on linux/mac?
Sent from my Milestone 2 XDA App

I think i'm going to try that. Will report later

r2beta0 said:
I don't know if this is going to help, but you could try that anyway:
- Download MotoAndroidDepacker (utility to unpack/repack SBF's)
- Choose one stock SBF (2.2 FR for example)
- Open and unpack it with the utility
- Rename CG66.smg to CG37.smg (you are going to use preinstall image as data image, both are ext3, but has different sizes. Don't know if it's going to work).
- Use utility to open folder with unpacked images and repack it
- Put phone in bootloader mode and flash the repacked SBF (rebuilt/firmware.sbf)
- Post results here
Click to expand...
Click to collapse
I have the same probleme .... And this don't work for me too.....

Alex, same problem ? What happened ? with the rom MS2ginger ? Two french guys , it is weird ! Hope mine won't go that way !

EVEALEX62 said:
I have the same probleme .... And this don't work for me too.....
Click to expand...
Click to collapse
I've tried Linux but no result... We are 3 french who have the exact same probleme it can't be Hardware?
Our Milestone 2 are somewhat different than others... I've phoned motorola for my problem today they told me to send it to a partner repair center but he warned me that if they discover i did something to the phone it will cost my a lot of money...
I'm sending it monday morning i'm really hoping for a solution before than...

Im not sure about service sbf vs the one that wipes user data. We have that kind of sbf for m2?
On the other side, looks like ROM chip go bad.

I'll ask some obvious question...you did not have any errors when flashing ? it always complete the process? Can you get into the bootloader when it print version 70.12 or 70.13 ?
Another obvious thing, did you verify md5 after downloading sbf ?

pat972 said:
Alex, same problem ? What happened ? with the rom MS2ginger ? Two french guys , it is weird ! Hope mine won't go that way !
Click to expand...
Click to collapse
No I go to MIUI yesterday... very bad news................................ I hope find a solution.............
RSDLite don't finish, I must deconecte and reboot bootlader manually and replug to got "pass" result !!
Bootloader is the 70.13
And the SBF is good because I alway use this file (don't download new)
.................. PLEASE HELP ..................

EVEALEX62 said:
No I go to MIUI yesterday... very bad news................................ I hope find a solution.............
RSDLite don't finish, I must deconecte and reboot bootlader manually and replug to got "pass" result !!
Bootloader is the 70.13
And the SBF is good because I alway use this file (don't download new)
.................. PLEASE HELP ..................
Click to expand...
Click to collapse
So it happenned both to us when we intalled MIUI so the problem is MIUI. Because i was using CM7 since Endless7 post the instruction avec Defy's ROM. And the phone was perfect...
We both have French Milestone 2 and i don't think it is my fault. I quite shure i did everything straight. I maybe a noob in dev or other things. But I have experience in flashing things...
My bootloader is 70.12 so it's different than Alex. And i used just like Alex the French Stock sbf i used everything i needed a freash clean install
When i flash i get to the "Please reboot phone manually" like everytime and then pull the battery go to bootloader and get finish

I had problems with miui too. After install MIUI and try back to MS2Ginger, phone dont boot, stuck at the first M bootscreen. So I try a full wipe and same problem, stuck at the first M. Mine bootloader was 70.12, so I flash the 70.13 and the spanish 2.2.2 sbf, and after a data and cache wipe, phone boot again.
Note: After flash a sbf, I dont remove the battery and pull again to get "Pass" on RSD Lite... just waiting to finish the process and disconnect the phone

Motodoido said:
I had problems with miui too. After install MIUI and try back to MS2Ginger, phone dont boot, stuck at the first M bootscreen. So I try a full wipe and same problem, stuck at the first M. Mine bootloader was 70.12, so I flash the 70.13 and the spanish 2.2.2 sbf, and after a data and cache wipe, phone boot again.
Note: After flash a sbf, I dont remove the battery and pull again to get "Pass" on RSD Lite... just waiting to finish the process and disconnect the phone
Click to expand...
Click to collapse
My phone is supposed to have the 70.12 bootloader right? If i flash the new one won't the repair center see that i modified the software?
The is no 70.12 bootloader on and-developper so how do i get back?
My phone doesn't not get to PASS it never did even in past... Except when i could do a wipe data and cache before flash

If you flash the 70.13 you do not be able to back to 70.12, so think before. When RSD is in reboot your phone 30%, I always remove my phone and never have problems
If you want try, here is the 70.13

The bootloader for the sbf 2.2.2 is 70.13 ! I remenber well, i did the official update on a windows pc, and it started by updating bootloader! But it's good news and may be just some sort of sbf incompatibility with the bootloader...just find the correct ones?
Sent from my MotoA953 using XDA App

pat972 said:
But it's good news
Click to expand...
Click to collapse
What is the good news ????

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] Flashed Defy plus rom on defy

i flashed a Defy + rom/sbf (DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF)on my Defy .I realised that i should not have done that while going through some of the posts here . However i dont want to make more mistakes and hence seeking advice from experts here . Everuthing seems to be working fine except for the camera. I was able to root using a solution that i found on the net and after installing recovery using 2init i tried to install MIUI 2.3.7 . Everything went fine but after the installation from SD was completed and i tried to reeboot my phone it gave me a boot loader error ...something like Err : A5,35,70....
Experts what are the options that i have to go back to the stock rom ( i have a nandroid back up as well as a defy sbf) or anyother custom rom so that i get everything working in my phone ?
Thanks in advance

Discussed a million times already. Nothing can be done.

andr0idfreak said:
Discussed a million times already. Nothing can be done.
Click to expand...
Click to collapse
I tried the steps in this post http://forum.xda-developers.com/showthread.php?t=1486731&highlight=froyo+bl6&page=21, however after step 4 i.e flashing the sbf , the phone does nothing but a black screen. Can anyone help me with this ?

The solution is this post http://forum.xda-developers.com/showthread.php?t=1486731
follow this post "http://forum.xda-developers.com/showthread.php?t=1486731'
this will help you .. i have used it it works ...
only the touch is having a little problem otherwise everything gets back to normal!!!
@southpaw said:
i flashed a Defy + rom/sbf (DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF)on my Defy .I realised that i should not have done that while going through some of the posts here . However i dont want to make more mistakes and hence seeking advice from experts here . Everuthing seems to be working fine except for the camera. I was able to root using a solution that i found on the net and after installing recovery using 2init i tried to install MIUI 2.3.7 . Everything went fine but after the installation from SD was completed and i tried to reeboot my phone it gave me a boot loader error ...something like Err : A5,35,70....
Experts what are the options that i have to go back to the stock rom ( i have a nandroid back up as well as a defy sbf) or anyother custom rom so that i get everything working in my phone ?
Thanks in advance
Click to expand...
Click to collapse

gaushim said:
follow this post "http://forum.xda-developers.com/showthread.php?t=1486731'
this will help you .. i have used it it works ...
only the touch is having a little problem otherwise everything gets back to normal!!!
Click to expand...
Click to collapse
That's for BL6 and OP has flashed a BL7 SBF.

andr0idfreak said:
That's for BL6 and OP has flashed a BL7 SBF.
Click to expand...
Click to collapse
gaushim said:
follow this post "http://forum.xda-developers.com/showthread.php?t=1486731'
this will help you .. i have used it it works ...
only the touch is having a little problem otherwise everything gets back to normal!!!
Click to expand...
Click to collapse
Thanks for your help Gaushim.....but that is the same thread that i was refering to . I could not get any success beyond step 4 (i.e after flashing the sbf the phone just displays a black screen.)
andr0idfreak is right that method works for bl6 and not bl7......just hoping that someone here on the forum knows a way out....

if you have a green lense defy nothing can be done to fix your camera. however you can root your phone and install some custom roms (search on here for bl7 custom roms and there is a list somewhere).
to flash the rooted sbf follow the guide below. once rooted you can then install 2nd init and flash a rom. i use cm7 euro kang. i have a red lense defy and flashed a bl7 sbf...my battery doesnt charge and isnt recognized in any rom no matter which fix i flash. the only way i can charge it is through an external charger cos the usb charging doesnt work. not the best solution but i have two batteries and just swicth them around when one dies.
thread for rooted bl7 sbf is here
http://forum.xda-developers.com/showthread.php?t=1595013

[Q] Jelly bean OTA4 problem

hello. i flashed stock rom via odin. rooted phone, flashed cwm, jbv3, ota1,ota2,ota3,ota4,clock to right. but after i flashed ota 4 i have a problem on clock. more exactly at Alarm. when i set to ON an alarm the screen freeze for 1-2 sec and i get force close clock error. am i the only one haveing this problem since i haven't seen any other posts about this. if is it just me tell me what i did wrong or how can i fix this please.
and one more question. is is worth to use merruk kernel since i want more BATTERY saving ? is this kernel going to use more battery or not ?
thanks in advance

I have just set the Alarm, didn't cause any problem..Let's see what others say..
For Good Battery Saving you should use Kuro Kernel which comes by default with JellyBlast v3..Merruk Kernel can overclock Galaxy Y to 1.2 GHz, but it drains the battery too.. Good Luck

weird. i tried reinstalling again and again from the begining. i will tell you exact steps i'm making maybe i make something wrong.
1.i flash stock rom via odin ( DDLA1, i don't know if this is the best one but i have a problem with my signal and calls quality if i use other stock roms (don't know if this is the reason or is just my phone) maybe you can help me resolve this too)
2. i reset phone to factory settings
3. i copy root and cwm archives to sd-card
4. i flash root via stock recovery
5. boot phone and check if it's rooted
6. flash cwm, wipe data/cache/davlik cache
7. flash through cwm JBV3, boot phone, flash through CWM OTA1, boot phone, flash through CWM OTA2, boot phone, and so on for OTA3 and OTA 4.1(revised) then flash through CWM also clocktoright archive
8. so now. on boot i get an error for jelly bean search (i know how to resolve this - uninstalling it) and i still receive force close on clock when i try to turn on an alarm.
any help ? what am i doing wrong ? maybe my stock rom isn't good ? but read at step1 about my problem with calls quality and signal and tell me if the stock rom has anything to do with it or not.
thanks again ^^

JellyBean Search Force Closes at boot, that's not a problem at all Happens with everybody..The Alarm Bug is the problem...Did you flash the correct Stock ROM using Sir Doky73's tutorial...Wait for the answers too

well.that's the "thing". i didn't install any rom from Doky's post. i downloaded one from the web which contains all packages for odin (pit,boot,pda,phone and csc) and it's DDLA1 firmware. should i try with one of Doky's firmwares ? which one? because there are many of european multilingual packs ( i'm from romania)
EDIT : should i use this CSC which includes carrier setup for my country (romania) -> CSC Only: OXF CSC for XXLE1 (S5360) and the other files from S5360_XXLE1_OXXLE1_XXLE1 as it says in his post ?

Maybe what you are saying is correct!
Strongly Advice you to PM any senoir dev like DeathNotice01, Ronnieryan, or Sir Doky himself
I didn't tried flashing Stock ROM ever..So I don't quite know about it
Whatever you do, first ask a Dev for his advice Good Luck!

thanks...can you tell me what baseband version do you have ?

I experience the alarm clock bug too. But i don't see it as much of a problem because even though it force closes it still sets up an alarm. I was even able to wake up to it this morning.

yaur7_cs said:
hello. i flashed stock rom via odin. rooted phone, flashed cwm, jbv3, ota1,ota2,ota3,ota4,clock to right. but after i flashed ota 4 i have a problem on clock. more exactly at Alarm. when i set to ON an alarm the screen freeze for 1-2 sec and i get force close clock error. am i the only one haveing this problem since i haven't seen any other posts about this. if is it just me tell me what i did wrong or how can i fix this please.
and one more question. is is worth to use merruk kernel since i want more BATTERY saving ? is this kernel going to use more battery or not ?
thanks in advance
Click to expand...
Click to collapse
Yes bro i was too having this problem...i fixed it by pasting clock app of ota4 on system/files....

hmm, i think the clock need fix, but the alarm still work
sorry bad english

I too am facing fc in alarmclock .No need to worry it`s an error .Hope avijit will fix it next time.

Yes, faced the alarm bug. But able to set up the alarm, so not much of a worry! Hope the developer will fix it soon.

Clock bug resolved
yaur7_cs said:
hello. i flashed stock rom via odin. rooted phone, flashed cwm, jbv3, ota1,ota2,ota3,ota4,clock to right. but after i flashed ota 4 i have a problem on clock. more exactly at Alarm. when i set to ON an alarm the screen freeze for 1-2 sec and i get force close clock error. am i the only one haveing this problem since i haven't seen any other posts about this. if is it just me tell me what i did wrong or how can i fix this please.
and one more question. is is worth to use merruk kernel since i want more BATTERY saving ? is this kernel going to use more battery or not ?
thanks in advance
Click to expand...
Click to collapse
just copy clock.apk from OTA3 update and install using system app replacer ... thats it .. i m having same problem but now resolved by this method. one con is that clock have old look as that of gingerbread style instead of ICS.. enjoy..:good:

No need to worry Nemesis will be relesed soon.

keypad
plz change the landscape typing as like sony in which we see what screen is instead we have other screen
means as like potrait background keep the landscape background.

[Q]Blue led always on.

So the led on my defy+ is always blue. Also when i remove the battery the time resets itself to 1970 so i think it's internal battery is dead. Is there a way to check or even replace it?

no one?

You can take to a store for repair or contact the Motorola company. But either way I think you have to pay

Did u flash your phone lately? If so - try to recover it with original SBF.

Im going tot ry reflash the original rom and see where it goes.

densets said:
Im going tot ry reflash the original rom and see where it goes.
Click to expand...
Click to collapse
you need to flash a compatible sbf and not necessary to be your original.