Database Users

[Q] Couple of questions...

Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!

1) its up to you, it is possible to upgrade with root as long as you have any model except a r800 x
2) I dont think either is better just depends on what you want to do to your phone
3) It depends what you mean by complete. There will probably be a stable version that is better than the stock rom eventually, but im not a dev
Ota means "over the air" and a kernel if im not mistaken is the part of the phone responsible for managing sysyem resources and the like. Not that I know much about anything and I could be wrong lol
Sent from my R800i using XDA App

LemonPlusTea said:
Hi! I just got my xplay a month or two ago, and my last phone was a iphone. As such, stepping from the relatively easier to handle ios to android system's not exactly a piece of cake...
And I still have a couple questions despite lurking in this forums for a while...
1) im running 2.3.2 , rooted with gingerbreak. I heard there's an improvement in battery life.. so im quite tempted to update, but the thought of bloatware coming back kind of scares me.. ._.
So should I update?
2) is unlocked or locked bootloader better?
3) finally, will there be a final or complete version of cm7?
Also, would be great if anyone could explain what is an OTA and kernel...
Thanks!
Click to expand...
Click to collapse
This will be my second numbered answer today. Anyway:
1) What model do you have? I assume it's an r800i or r800a. If it is, I would head over to the development section and check out how to get the UK generic firmware on your phone without unlocking the boot loader. I did that, rooted it, then updated to 2.3.3 and removed a lot of bloat and it's good to go now.
2) I have unlocked the boot loader on every Android I've owned, but I haven't on this phone. I wouldn't until development takes off a little bit more. It will soon, but I probably won't even do it then, personally.
3) Yes, we have great people working on it. It's progressing majorly with each update.
Just next time search before posting...nah, I'm just kidding. Welcome to Android.
adb shove iPad2post.apk to /forum/thread

OTA means you are updating the firmware on your phone through your phone over wifi.
If you didn't remove the boats you can still do it by pressing the software update button on your phone. Just make sure that your bootloader is is still LOCKED.
Sent from my XPlay using XDA App.

Thanks guys! I'll try to flash the firmware on my phone after I get home from school. my xplay is a r800i. Also, if I use the UK firmware and update to 2.3.3, will it affect my ability to update to 2.3.4 as I live in Singapore?

No, when 2.3.4 comes out it would probably be available to generic uk before any other versions. As long as you freeze and not remove boats, you would be able to ota update to 2.3.4
Sent from my XPlay using XDA App.

Hey guys Im back from school.
Is it this thread to follow ?
http://forum.xda-developers.com/showthread.php?t=1119074
Because I saw another one ..
http://forum.xda-developers.com/showthread.php?t=1097591
^ which requires an unlocked BL. :O

Oh my god.. I didnt enable debugging and the process stopped halfway.. now the phone displays an exclaimation mark next to a phone.. did i just brick my phone? ...
EDIT : googled around and now im trying to restore my phone via SEUS...

Ok.. my phone started up fine after running SEUS.. but I clicked restore to factory instead of update..
I want to try updating to 2.3.3 with root again.. So can anyone point out anything I did wrong the previous time?
1. I downloaded the generic UK version (http://forum.xda-developers.com/showthread.php?t=1119074) and flashtool 0.2.8 (http://forum.xda-developers.com/showthread.php?t=920746)
2. I used flashtool and flashed the .tft file and followed the onscreen instructions...
3. the flashing stops halfway cause i didnt enable usb debugging (?) and it causes my phone to be unable to boot up and trauma for me for panicking for 30 minutes. ._.
I tried flashing again with USB debugging on..?
My version is now 2.3.3 after I restored with SEUS, however.
07/046/2011 18:46:02 - INFO - Flashing adsp.sin
07/046/2011 18:46:05 - INFO - Flashing kernel.sin
07/046/2011 18:46:07 - INFO - Flashing amss_fs.sin
07/046/2011 18:46:07 - INFO - Flashing fota1.sin
07/046/2011 18:46:08 - INFO - Flashing fota0.sin
07/046/2011 18:46:09 - INFO - Flashing apps_log.sin
07/046/2011 18:46:09 - INFO - Flashing amss.sin
07/046/2011 18:46:19 - INFO - Flashing cache.sin
07/046/2011 18:46:20 - INFO - Flashing system.sin
07/046/2011 18:46:44 - ERROR - Error flashing. Aborted
07/046/2011 18:46:44 - INFO - Now unplug the device and power it on
07/046/2011 18:46:44 - INFO - Then go to application settings
07/046/2011 18:46:44 - INFO - turn on Unknown Sources and Debugging
( after that resulted in the same problem as before but luckily I knew how to fix it again.. ._. )

It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...

Dousan said:
It might be that you're not using the latest version of flashtool, it's 0.2.9.1 and it's the beta one and afaik it's the only one to support the play.
Regards Dousan...
Click to expand...
Click to collapse
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.

LemonPlusTea said:
I see.. Cause I thought beta might not be stable!
Thanks alot! Time to go try again ^_^
EDIT : Same error with the newest flashtool.. ._.
Crapp...
I unpacked the 0.2.9.1 and ran the X10 Flash Tool... and it still doesnt like me..
It seems it hates me more and more..
now instead of even starting flashing after i send my phone into flash mode it gives me this error..
ERROR - USB\VID_0FCE&PID_ADDE\5&1F015A4B&0&5
Triple edit : Now Im back to square one of flashing till system.sin and getting an error.. ._.
Click to expand...
Click to collapse
Maybe it's a corrupt download or the unpacking of the .zip/.rar file went bad. Could try a reunpacking or/and redownload?
Regards Dousan...

Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?

LemonPlusTea said:
Redownloaded the flashtool 2 times and the generic UK ftf 3 times already.. could it be my computer's problem?
Click to expand...
Click to collapse
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread

TheBassman369 said:
I know back in my Galaxy S days the firmware tool Samsung used worked on one of my computers but didn't work on the other. I would try another computer if you had access to one.
adb shove iPad2post.apk to /forum/thread
Click to expand...
Click to collapse
Alright, I'll try it with my sister's laptop ^^..
Entire day has been miserable without my apps... :l

Nope.. still doesnt work.. ._.

LemonPlusTea said:
Nope.. still doesnt work.. ._.
Click to expand...
Click to collapse
Man. That's crazy. I have no idea what to do. Hopefully you can get it.

When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...

Did you install the Sony software from your phone first?
Mine needed it to get the drivers. It said it had errors but I let it go for a while and it finished no problem.

Dousan said:
When flashing, have you ticked the 'erase data' (I'm not sure it's the exact name) or are you flashing without erasing? Cus it looks like that's where the error occurs when it's supposed to flash the data?
Regards Dousan...
Click to expand...
Click to collapse
Yeah I checked the erase data box all the time...
@ncaissie, im not entirely sure what you mean... Would you mind explaining?

[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] - Manual Update from Stock 3.2.1 to Stock ICS

Hi All,
So I'm tired of my stock 3.2.1 flipping between the "Your Device is Up to Date" and "Poor Network Coverage" messages when checking for the ICS update.
I current have:
Acer_A500_7.014.14_COM_GEN1
Through this wonderful forum, I downloaded:
Acer_A500_7.014.14_041.203.01_COM_GEN1_1333444737199_8ec8b991.zip
I found out it was encrypted, so I downloaded the Acer decrypting tool and unzipped it.
So with that said, I have a few questions:
1) Will this release of ICS work with my current device?
2) If yes, how do I update my stock 3.2.1 to ICS? Do I need to root it before I can update it, or can I simply copy the update to an SD/USB Stick and update from there?
3) Do I need to decrypt the install, or can I use the encrypted version?
Or should I simply stop being so damn impatient and just wait for the OTA?
Thanks.

Have you been back to the Market (Play Store) and installed the recent Enhancement Update to the Acer Update Readiness Tool? Should allow you to connect to those "lazy" servers.

Hello,
I just did the manual install to ICS myself that way:
1) dowload the ICS update you mentionned
2) decrypt the zip with the acer decrypt tool
3) only extract the update.zip in the decripted zip to the root of the external sd
4) shutdown the tablet and restart it pressing both power + volume dow button which start the update automatically
Ps: a good thing is that this update does not wipe existing intalled apps or existing data
Hope this helps

is this the official ics rom update
Is this the official rom update to is?

sakurasyaoran said:
Is this the official rom update to is?
Click to expand...
Click to collapse
Yes, i believe so since my tablet was never and is not rooted.
This is what I see in the settings
Android version: 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer_AV041_A500_RV03RC01_WW_GEN1
Build number: Acer_AV041_A500_1.031.00_WW_GEN1
Image P/N: FM.S14A0.00U

scubapro10 said:
Hello,
I just did the manual install to ICS myself that way:
1) dowload the ICS update you mentionned
2) decrypt the zip with the acer decrypt tool
3) only extract the update.zip in the decripted zip to the root of the external sd
4) shutdown the tablet and restart it pressing both power + volume dow button which start the update automatically
Ps: a good thing is that this update does not wipe existing intalled apps or existing data
Hope this helps
Click to expand...
Click to collapse
Thanks.....I tried it, and the process appeared to start ok. But after about 30 seconds the Android robot showed up with an exclamation point in a triangle.
So maybe this update was not for my system. I guess I'll just be patient and wait for the OTA upgrade.
(and yes, I do have the tab enhancement installed in case anyone is wondering).

v1perfan said:
Thanks.....I tried it, and the process appeared to start ok. But after about 30 seconds the Android robot showed up with an exclamation point in a triangle.
So maybe this update was not for my system. I guess I'll just be patient and wait for the OTA upgrade.
(and yes, I do have the tab enhancement installed in case anyone is wondering).
Click to expand...
Click to collapse
Forgot to mention, just before updating to ICS, i tried to use another 3.2 stock rom to see if OTA was working better, so maybe this update to the other 3.2 rom is also necessary. The 3.2 stock rom i've used is this one: Acer_A500_7.006.01_COM_GEN2 available in this post: http://forum.xda-developers.com/showthread.php?t=1113878
More info in my initial post http://forum.xda-developers.com/showthread.php?t=1622253
Good luck

scubapro10 said:
Forgot to mention, just before updating to ICS, i tried to use another 3.2 stock rom to see if OTA was working better, so maybe this update to the other 3.2 rom is also necessary. The 3.2 stock rom i've used is this one: Acer_A500_7.006.01_COM_GEN2 available in this post: http://forum.xda-developers.com/showthread.php?t=1113878
More info in my initial post http://forum.xda-developers.com/showthread.php?t=1622253
Good luck
Click to expand...
Click to collapse
Thanks for the update. I didn't think the firmware would work on GEN1, so I'll give it a whirl....

v1perfan said:
Thanks for the update. I didn't think the firmware would work on GEN1, so I'll give it a whirl....
Click to expand...
Click to collapse
If you look my initial post, you can see i was in 3.2.1 gen1 then i moved to 3.2.1 gen2 and now im in 4.0.3 gen1

Do you have the update.zip file only. Its hard for me to decrypt it. My laptop recognize it as a virus the decrypt file I mean.
Thanks
Sent from my A500 using XDA

scubapro10 said:
If you look my initial post, you can see i was in 3.2.1 gen1 then i moved to 3.2.1 gen2 and now im in 4.0.3 gen1
Click to expand...
Click to collapse
*** FIXED!!!!!! ***
I found out the SD card type is VERY IMPORTANT!!!
When I initially tried to install the ICS update from a generic SD card I would get the robot / exclamation / triangle error (I was using a Patriot 8GB SDHC Class 4 card).
I then tried using a Sandisk 2GB MicroSD card - UPDATE SUCCESSFUL!
I didn't have to use a Stock 3.2.1 image or anything - I just went straight to 4.0.3.
My new build number is ACER_AV041_A500_1.031.00_WW_GEN1 with Android version 4.0.3 of ICS goodness.
Thanks to everyone who gave me ideas and who posted on other sites!
EDIT - So I installed it, but then I had the dreaded DHCP-Wifi reboot problem. I fixed it by doing a factory reset, and all is good.

scuba dont do it man
scubapro10 said:
Forgot to mention, just before updating to ICS, i tried to use another 3.2 stock rom to see if OTA was working better, so maybe this update to the other 3.2 rom is also necessary. The 3.2 stock rom i've used is this one: Acer_A500_7.006.01_COM_GEN2 available in this post: http://forum.xda-developers.com/showthread.php?t=1113878
More info in my initial post http://forum.xda-developers.com/showthread.php?t=1622253
Good luck
Click to expand...
Click to collapse
hi scuba just been talking to acer and if you get bad connection on screen they say do a factory reset but i am waiting for a good signal cause a factory reset will wipe the lot and if u have 50 odd apps then you will be in for a long haul reinstalling also the ics firmware update will be rolling out after may 1st as it was put back do to bug fixing and they wanna get u.k devices up and running with no hitch also the playstore app people insist on downloading will force close apps and the tab will go crazy and then you have to reinstall apps ect i have heard so many tales dont do it unless you want to also this bootloader root thing dont do it man it will either make the tab useless and invalidate your warranty if u still have 1 many thanks ps i will wait for the ics firmware and do a system update from the tab cya happy days

v1perfan said:
*** FIXED!!!!!! ***
I found out the SD card type is VERY IMPORTANT!!!
When I initially tried to install the ICS update from a generic SD card I would get the robot / exclamation / triangle error (I was using a Patriot 8GB SDHC Class 4 card).
I then tried using a Sandisk 2GB MicroSD card - UPDATE SUCCESSFUL!
I didn't have to use a Stock 3.2.1 image or anything - I just went straight to 4.0.3.
My new build number is ACER_AV041_A500_1.031.00_WW_GEN1 with Android version 4.0.3 of ICS goodness.
Thanks to everyone who gave me ideas and who posted on other sites!
EDIT - So I installed it, but then I had the dreaded DHCP-Wifi reboot problem. I fixed it by doing a factory reset, and all is good.
Click to expand...
Click to collapse
Do u have the update.zip file u can share?
Sent from my A500 using XDA

sakurasyaoran said:
Do u have the update.zip file u can share?
Sent from my A500 using XDA
Click to expand...
Click to collapse
The one I used was from this page:
http://forum.xda-developers.com/showthread.php?t=1113878
Download and decrypt the file under the hyperlink named "Acer_A500_7.014.14_041.203.01_COM_GEN1"

Can u upload the update.zip file only?
Sent from my A500 using XDA

Anyone who can share update.zip file?
Sent from my Nexus S using XDA

Decryter says many antivirus false positive. I turn off the antivirus to decrypt and turn it on again.

[Q] Note 3 N900W8 soft bricked, backup not working.. can't find a compatible firmware

I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?

Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?

Yorgo1982 said:
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Click to expand...
Click to collapse
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.

Apra24 said:
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Click to expand...
Click to collapse
wait sammobile if u r with rogers bell telus fido vmc koodo, and if with other carrier contact them with ur phone model and serial num so they will upload it ..

Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
Did you restore from CWM/TWRP?

Pikezer1337 said:
Did you restore from CWM/TWRP?
Click to expand...
Click to collapse
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..

Apra24 said:
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Click to expand...
Click to collapse
If you restored through TWRP there is a good chance that you are softbricked. There are restoring issues that mess with the system partition.

Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition

Apra24 said:
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Click to expand...
Click to collapse
can u give the file name?
plz

Yorgo1982 said:
can u give the file name?
plz
Click to expand...
Click to collapse
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.

Apra24 said:
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Click to expand...
Click to collapse
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol

Yorgo1982 said:
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Click to expand...
Click to collapse
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.

Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317

Dumbo53 said:
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I'm wondering if the official Bell/Rogers firmware will be available any time soon? Does it typically get released soon after the phone launch, or are they withholding it for some reason?

Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.

eklipse1 said:
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
Click to expand...
Click to collapse
I was trying the Peru one for a while, but it kept hanging up during the bootup. The message was in a foreign language, but I'm assuming it was "initializing". It would initialize for about 3 minutes then an error message would pop up saying something is not responding.

Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app

eklipse1 said:
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I have been trying to. When I flash the firmware in odin, it reinstalls the stock recovery mod. Right after flashing firmware, it won't go into recovery mode on the first boot (first does some android robot install thing, then boots up). I attempted to install the TWRP recovery directly after the firmware, and then booting directly into recovery to factory reset, but I'm still getting a boot loop.

Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol

Yorgo1982 said:
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Click to expand...
Click to collapse
do they know it's rooted/void? Or did you somehow not trigger the knox/warranty void switch? I may just have to do the same thing...