gday, Been trolling site for ages, and now I need help.
I have had cm7 installed for months now, and all was ok until today. I turned the phone on and it stuck at google screen.
I have googled and tried various things all of which I don't understand and have probably made it worse.
If anyone could help me out it would be greatly appreciated.
mrs went and bought another phone, so Im gunna drop kick the defy out into the street.
ausdixie said:
mrs went and bought another phone, so Im gunna drop kick the defy out into the street.
Click to expand...
Click to collapse
flash another sbf..
btw if you going to through it then why not donate it to one of the devs as they might use it to experiment on it..
I replied to you in the other thread, if you don't want it I would take it.
Havent given up yet as i would like to give the phone to my son, if i ever get it going again. charging mcguyver at the moment. and thanks for replying fellas I appreciate it because i havent a clue.
ps smeg i have pm'd you but it doesnt seem to be working
Sainyam I have flashed many sbfs and i have made it worse
righto have this sbf flashed and working JDGC_U6_2.13.0.sbf\JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
system version 2.13.0.me525.chinaunicom.en.cn
android 2.2.2
kernal 2.6.32.9
build jdgc_2.13.0
dunno if this means anything but bootloader was 9.10
what should i do now
mine is also 9.10
so i am guessing you still have bl4 ..
so try flashing this...
if you dont have Telstra australia mobile..
then let me know...
if it is not installed then try this and then install cm7 on it ....
thanks to the land of smeg,
Phone is up and running,not original but damn close.
I havent done a custom rom because I would probably pick the wrong one an stuff it up again
I will post his directions for anyone else who royally roots their phone like I did.
.
You need to flash the 3.4.2-179-2 CEE nandroid over your chinese ROM
http://forum.xda-developers.com/show...&postcount=123
Then the 3.4.2-179-2 CEE fixed SBF
I can't find a working link for this. If you can't find one either you can make your own by downloading the Full SBF
http://sbf.droid-developers.org/umts...vice1FF.sbf.gz
and then use SBF Depacker:
http://forum.xda-developers.com/showpost.php?p=11195138
Delete the CG31 and CG39 and that will turn it into a Fixed SBF for you to flash.
Then install CM7 or CM9
make sure you use the CM7 kernel
ausdixie said:
thanks to the land of smeg,
Phone is up and running,not original but damn close.
I havent done a custom rom because I would probably pick the wrong one an stuff it up again
I will post his directions for anyone else who royally roots their phone like I did.
.
You need to flash the 3.4.2-179-2 CEE nandroid over your chinese ROM
http://forum.xda-developers.com/show...&postcount=123
Then the 3.4.2-179-2 CEE fixed SBF
I can't find a working link for this. If you can't find one either you can make your own by downloading the Full SBF
http://sbf.droid-developers.org/umts...vice1FF.sbf.gz
and then use SBF Depacker:
http://forum.xda-developers.com/showpost.php?p=11195138
Delete the CG31 and CG39 and that will turn it into a Fixed SBF for you to flash.
Then install CM7 or CM9
make sure you use the CM7 kernel
Click to expand...
Click to collapse
No worries, glad to help.
This is the solution to downgrade JDGC_U6_2.13.0 Chinese ROM with a BL6 kernel.
Have to use Nandroid/Fixed SBF method as this ROM updates CDT(CG31) and SYSTEM(CG39) to version 6, once a version goes up it can't be put back down, and if you flash a Full SBF of a lower version then the black screen problem will happen, but the Fixed SBF method flashes everything except CDT and SYSTEM (which have lower version numbers) and the Nandroid backup overwrites SYSTEM with the data while still keeping it at "version 6" as this is the minimum.
In future, when flashing ROMs do NOT try to flash ROMs which have higher versions than the Stock SBF if you wish to keep warranty, as even though you have effectively still gone back to that ROM, if the service centre looks carefully they will see that you are on higher Version CDT and SYSTEM which means that you must have been messing around with ROMs.
Related
I'm planning on putting CM7 on my Defy, but before I do that I want to make sure I can go back to the original OS.
The problem is, I can't find a full SBF for my current ROM version (T-Mobile US 34.4.9, build 3.4.2-107_JDN-9) to use if something goes wrong. My Defy came with this when I bought it, so presumably I can't downgrade to an Eclair SBF and update from there. I've found the two other official Froyo SBFs though: the 3.4.2-107_JDN-3 and 3.4.2-107_JDN-4 SBFs. I read that the -3 one is a dev build and doesn't easily update, so I don't want to use it. But I'm not so sure about the -4 SBF. Can I just flash that with RSD and then use an OTA update to get back to my -9 build back?
I'm very new to this (first post!) so please tell me if I'm wrong.
Never mind, I found out I was wrong. The -4 SBF is a leak too. But the official Eclair SBF (6.36) has the same CG version as the Froyo ROMs, so I can just use that.
glycolysis said:
Never mind, I found out I was wrong. The -4 SBF is a leak too. But the official Eclair SBF (6.36) has the same CG version as the Froyo ROMs, so I can just use that.
Click to expand...
Click to collapse
Can you help me revert back to stock, I look everywhere and nothing seems to work for me, try to flash 6.36 but I just get a black screen!
thanks!
Um, Me Too?
glycolysis said:
Never mind, I found out I was wrong. The -4 SBF is a leak too. But the official Eclair SBF (6.36) has the same CG version as the Froyo ROMs, so I can just use that.
Click to expand...
Click to collapse
I know, this is a really old post, but I have the same exact situation (except I want to try CM10 not CM7) and want to make sure I can go back to my stock T-Moble Froyo if something goes wrong. Can anyone confirm that going back to Eclair and then doing the OTA update back to Froyo works? I've seen other posts indicating that there are problems with this method.
I have asked to my telecoms operator the unsimlock code for my Defy, it said is yet unlocked but it is not
I have flash a full sbf 2.3.6. Before it was a 2.3.4.
Motorola can't give any code.
Is there a way to show to the operator that is still locked? Or a non paid way to have the unlock code (it's free with my operator)
I know that is a way to have a soft unock but only with cm7 or miui.
But i prefer a hard unlock for motorola rom.
THX.
Defy+ / 4.5.1-134_DFP-139 / 45.0.1390.MB526.Retail.en.FR
Bouygues telecom fr.
Always complain in a retail center. Take your defy, show him, let him call to services. Be persistent, not rude.
Indeed you could use a softunlock for CM7 or MIUI, don't know if you could for stock.
Thx for the answer. I have try this morning the softunlock with cm7 Nightly ( the only one cm7 i can install) but don't work . I think that the softunlock is only for 2.2.
Could you please try to install the nightly again and then flash the zip from my latest post on that threat?
Edit:
The zip
http://forum.xda-developers.com/attachment.php?attachmentid=908455&d=1329605492
Also you can try to write at russian forum - motofan.ru ( i'm not able to post link there...)
Just write IMEI and your model to them, probably you'll receive unlock code.
If you won't, only way is patch.
labsin said:
Could you please try to install the nightly again and then flash the zip from my latest post on that threat?
Click to expand...
Click to collapse
Thx. i have try but don't work anymore. I have flashed the cm7 zip, then, before reboot, flashed your zip. Trying to change baseband too but don't work.
Hellmanor said:
If you won't, only way is patch.
Click to expand...
Click to collapse
Yes, but for the moment not possible to find any patch for 2.3
Witch CM7 version are you using? Could you attach the files in defy_simlock_originals on your sdcard?
Could do the froyo for bl6 patch it from there and re install cm7
teamwork makes the dream work
labsin said:
Witch CM7 version are you using?
Click to expand...
Click to collapse
cm72-120127.0846-NIGHTLY-Defy+.zip
others don't work because of a 2.3.6 full sbf.
labsin said:
Could you attach the files in defy_simlock_originals on your sdcard?
Click to expand...
Click to collapse
Sorry but i don't understand what you want to say.
Could do the froyo for bl6 patch it from there and re install cm7
Click to expand...
Click to collapse
Do you mean to follow this way below? But i'm afraid this way don't work with Defy+?
Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))
How to Install CM7 after Installing a Full Gingerbread SBF: (!) Ok, first of all do all the steps above on "Installed full Gingerbread SBF and can’t go back to another rom"
Root your Defy (Using SuperOneClick 1.7 and not 1.9).
Install SystemRecovery from GoAPK. If you install 2nd init, you'll just get into a boot loop and have to start over.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM7 .Zip and then gapps zip file. DO NOT wipe again, you'll just go back to 2.2.2 CEE (if you accidentally do this, you can pick up again from step 3).
profit!
Click to expand...
Click to collapse
Yes it works with Defy+ if you are on a bld6 rom (not for the bld7 roms)
My patch from a couple posts back makes a copy of the patched file on your sdcard in the folder defy_simlock_originals. Could you post them here?
Don't know if the module works with the gingerbread kernel. That's why it is a good idea to try to get CM7 with froyo kernel. It's also handy if you wan't to install other roms (WIUI ...)
But could you fist give those files? Maybe i've made a mistake again ^^.
Edit:
Sorry you don't have the right guide. That one is for bld5 downgrade.
Here is for bld6: http://forum.xda-developers.com/showthread.php?t=1486731
labsin said:
My patch from a couple posts back makes a copy of the patched file on your sdcard in the folder defy_simlock_originals.Could you post them here?
Click to expand...
Click to collapse
Again, thank you for your help and time
(I have put .txt for upload)
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
labsin said:
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
Click to expand...
Click to collapse
Ok i'll try tomorrow
labsin said:
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
Click to expand...
Click to collapse
I have change the kernel with THIS METHOD
after, try with WIUI 2.2.17: no network; then with update-cm-7.1.0-11-Defy-signed: no network, even when changing baseband.
So, if all that i have made is right, maybe it's not fault of kernel.
Other difference between MB526 and MB525?
You get 'no network' all the time, even with the sim from the right provider, also without the patch?
I think you're the fist to try on a defy+. Maybe look to the Russian fora...
edit: And can you tell me what your Baseband version is? (in settings > about)
edit2: If it is EPU93_U_00.59.01 Try it after installing RC1.5 from here: http://www.defy-cm.net/jordan-cm7.1-RC/
labsin said:
You get 'no network' all the time, even with the sim from the right provider, also without the patch?
I think you're the fist to try on a defy+. Maybe look to the Russian fora...
edit: And can you tell me what your Baseband version is? (in settings > about)
edit2: If it is EPU93_U_00.59.01 Try it after installing RC1.5 from here: http://www.defy-cm.net/jordan-cm7.1-RC/
Click to expand...
Click to collapse
no network only with wrong provider: with the patch no code ask, but no network even with other baseband.
Yes it is EPU93_U_00.59.01 (cm7.2 working on defy+ as well)
with RC1.5 no boot after files install, stuck on google logo.
Now i have flash fix sbf to use 2.3.6 rom because of no battery problems and better battery life. So i'll wait and ask again to my operator.
Now baseband is EPU_U_00.60.03
Do you think if i'm able to put a official operator rom it will see that is no desimlocked? i don't have made backup of my official rom (newbie mistake ) so i have ask here if it's possible with this method.
Blocking by TI OMAP 3630
I have read this:
Blocking the Bootloader by TI OMAP 3630
Why and how is it locked Defy?
While Linux is Open Source Motorola keeps the Defy the locked bootloader. Why?
For commercial reasons of course: avoid too many warranty returns from sorcerer's apprentices who brické their phone, for example (although care is denied you still have to manage the folders!) But also the traders (who manage some of the guaranteed returns, but not that ... we shall see below).
So Motorola maintains bootoader of our favorite phone is not locked and ready to unlock the last views of Roma making the switch to SBF rootage and even more difficult. But the fact how this lock is it made?
Unlike other phones (other brands, but also other brand models *) easy to unlock, the Defy is equipped with a TI OMAP 3630 chip that manages its technology via "M-Shield technology 'in this block. So we did not do a software problem but rather a problem if one CPU is addressing this release.
This technology also manages the simlockage phone which also explains why the operators are far from favorable to the release of Defy.
No one arrived today to crack this lock: it should have the tool from Texas Instruments where he provided to authorized repairers to put the Motorola Defy mode "SE" (Systems Engineering) for this.
* These phones using Qualcomm chips or other, do not bénéfiecient techonologie the M-Shield and are much easier to unlock.
Click to expand...
Click to collapse
(Google trad) Or here in french
stucked at jrdan u97.21.51
I am new at this my defy went dead when tried to upgrade to 2.2 did not have backup. I searched the web and only jrdan u 97.21.51 will work and canot go back or change any more to any other roms. tried the rsd lite to flash diferent roms and nothing works. tried rom manager and 2ndinit recovery and nothing i get black screen. Is there anyway to get out of this? Please help
sion123 said:
I am new at this my defy went dead when tried to upgrade to 2.2 did not have backup. I searched the web and only jrdan u 97.21.51 will work and canot go back or change any more to any other roms. tried the rsd lite to flash diferent roms and nothing works. tried rom manager and 2ndinit recovery and nothing i get black screen. Is there anyway to get out of this? Please help
Click to expand...
Click to collapse
Wrong thread i think.
Have you try a wipe cache and data in stock recovery before rsdlite? see here how to do with Froyo
Hi, today i flash my defy+ with this sbf DEFYPLUS_U3_4.5.1-134_DFP-188_TMOUK,
The problem is i cant root, and cant change the sbf by another.
Is i flash another, the phone no boot, a not show anything on screen, led are off.
Only work whith the t-mobile sbf, but i dont have signal and my batery dont charge.
Anyone have any solution for this, please help me.
Sorry my bad english, im argentine!
jonatan25 said:
Hi, today i flash my defy+ with this sbf DEFYPLUS_U3_4.5.1-134_DFP-188_TMOUK,
The problem is i cant root, and cant change the sbf by another.
Is i flash another, the phone no boot, a not show anything on screen, led are off.
Only work whith the t-mobile sbf, but i dont have signal and my batery dont charge.
Anyone have any solution for this, please help me.
Sorry my bad english, im argentine!
Click to expand...
Click to collapse
Try this solution
h**p://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
thx but dont work...
Did you see this from the XDA thread about that sbf:
NO DOWNGRADE TO ANY 2.3.6 rom or 2.3.4 or FROYO/ECLAIR and no root if you flash full sbf
i see it too late... i´m sending my phone to official service, is on guarantee, i hope they can change or repair my phone, if not, i be too sad.
Only can wait and if they not repair or change, i have a very nice mini netbook
thanks for help !
You can try this http://forum.xda-developers.com/showthread.php?t=1486731
Is a new sbf with CG ver 6 and Froyo Kernel, then you can flash any ROM that uses Froyo kernel
EDIT
Sorry, that doesn't work, you flashed the CG ver 7
LeonardoJegigzem said:
You can try this http://forum.xda-developers.com/showthread.php?t=1486731
Is a new sbf with CG ver 6 and Froyo Kernel, then you can flash any ROM that uses Froyo kernel
EDIT
Sorry, that doesn't work, you flashed the CG ver 7
Click to expand...
Click to collapse
4.5.1-134_DFP-188 has BL7
jonatan25 said:
i see it too late... i´m sending my phone to official service, is on guarantee, i hope they can change or repair my phone, if not, i be too sad.
Only can wait and if they not repair or change, i have a very nice mini netbook
thanks for help !
Click to expand...
Click to collapse
hey man, you repaired your phone, i have a bricked defy+, where testing many solutions i just do it power on without battery detector, and works well if 3g disabled, i would like put as original and working all =\
So here it is, I accidentally picked the chinese JDGC_2.13.0 while flashing sbf and now my defy is a ME525 when I look into the phone information.
That sbf does not seem to be downgradable, as I only get a black screen after flashing any other sbf I used before, meaning the stock froyo or the nordic.
I seriously don't know what to do now. Is there something I can do to downgrade or make my phone a MB525 again?
I hate to break this to you,but i think you are screwed.If it is under warranty,give it to your service centre and act as if you know nothing.That is the best advice i can give you.Try to ask senior members about this and see if there is a way out of this.
you flashed a bl3 rom and now you cant downgrade to any froyo rom you flash this china rom and you need to have a froyo nanndroid buckap and an fixed sbf
tanarez said:
So here it is, I accidentally picked the chinese JDGC_2.13.0 while flashing sbf and now my defy is a ME525 when I look into the phone information.
That sbf does not seem to be downgradable, as I only get a black screen after flashing any other sbf I used before, meaning the stock froyo or the nordic.
I seriously don't know what to do now. Is there something I can do to downgrade or make my phone a MB525 again?
Click to expand...
Click to collapse
Upgrade to a non chinese BL4 Froyo. Or if you wish you may update to a GB BL6!! However then your phone will become MB526(Defy+) and you won't be able to downgrade to Froyo again!
You can find them here or go to dev section of XDA...
You may also need this Defy Image tools Use them to check the BL version... (smgver.exe)
pranks1989 said:
Upgrade to a non chinese BL4 Froyo. Or if you wish you may update to a GB BL6!! However then your phone will become MB526(Defy+) and you won't be able to downgrade to Froyo again!
You can find them here or go to dev section of XDA...
You may also need this Defy Image tools
Click to expand...
Click to collapse
He would be able to downgrade to Froyo. There is a Chinese BL6 Froyo sbf available in the forums.
niksy+ said:
He would be able to downgrade to Froyo. There is a Chinese BL6 Froyo sbf available in the forums.
Click to expand...
Click to collapse
Ya I tried that once when i wanted to try the CM9 nightly for Defy.. But its a chinese and have the potential to fry your LED!!!
Hello guys
Friend of mine gave me Motorola Defy to flash into stock rom as guy from local repair shop told him that this cannot be unlocked to all networks as long as its run Cyanogenmod and there is must to install original stock rom.
I have downloaded stock droid developers in ".sbf" extension and was researching xda in order to find out how to flash it but more I researched more I afraid become to do it.
I have found so many warnings not to downgrade that phone to Froyo, some posts saying not to flash ".sbf" at all but asked you guys for help.
Is there any safe way to reduce possibility of bricking this Motorola to the minimum?
Could someone advise me what should i do in this case? Should I give up flashing?
Helpful informations:
MB525 - on the label under the battery
MB526 - detected by system CM11-20140731-NIGHTLY-mb526
Recovery - TWRP
Thank You in advance for any help provided.
Regards
kamuflasz said:
Hello guys
Friend of mine gave me Motorola Defy to flash into stock rom as guy from local repair shop told him that this cannot be unlocked to all networks as long as its run Cyanogenmod and there is must to install original stock rom.
I have downloaded stock droid developers in ".sbf" extension and was researching xda in order to find out how to flash it but more I researched more I afraid become to do it.
I have found so many warnings not to downgrade that phone to Froyo, some posts saying not to flash ".sbf" at all but asked you guys for help.
Is there any safe way to reduce possibility of bricking this Motorola to the minimum?
Could someone advise me what should i do in this case? Should I give up flashing?
Helpful informations:
MB525 - on the label under the battery
MB526 - detected by system CM11-20140731-NIGHTLY-mb526
Recovery - TWRP
Thank You in advance for any help provided.
Regards
Click to expand...
Click to collapse
Hi, you can try this http://forum.xda-developers.com/showpost.php?p=50699347&postcount=511 to unsimlock while staying on cm11, but no idea if it will really work.
I have flashed my defy many times without any problems, i have used a sbf from this list http://forum.xda-developers.com/showthread.php?t=966537 and kept it as reference in order not to use a downgraded sbf.
Just make sure the defy is fully charged, rsd lite + motodrivers are installed .
bilibili2011 said:
Hi, you can try this http://forum.xda-developers.com/showpost.php?p=50699347&postcount=511 to unsimlock while staying on cm11, but no idea if it will really work.
I have flashed my defy many times without any problems, i have used a sbf from this list http://forum.xda-developers.com/showthread.php?t=966537 and kept it as reference in order not to use a downgraded sbf.
Just make sure the defy is fully charged, rsd lite + motodrivers are installed .
Click to expand...
Click to collapse
Flashing with RSD Lite didn't want to work as program didn't want to discover my phone, found another solution which is here http://forum.xda-developers.com/showthread.php?t=775913
Simple and works 100% even when my phone didn't turn on because wrong sbf, I could flash as many as I wanted to get the working one, which was mb526 2.3.6 version surprisingly
...
But now I need to get this devices rooted and all xda tutorials are about reflashing rooted sbf and installing twrp after that. Could someone advise me how to recognize rooted sbf which will be compatible with mb525??
I have tried framaroot to avoid flashing again but it didn't work unfortunately.
kamuflasz said:
Flashing with RSD Lite didn't want to work as program didn't want to discover my phone, found another solution which is here http://forum.xda-developers.com/showthread.php?t=775913
Simple and works 100% even when my phone didn't turn on because wrong sbf, I could flash as many as I wanted to get the working one, which was mb526 2.3.6 version surprisingly
...
But now I need to get this devices rooted and all xda tutorials are about reflashing rooted sbf and installing twrp after that. Could someone advise me how to recognize rooted sbf which will be compatible with mb525??
I have tried framaroot to avoid flashing again but it didn't work unfortunately.
Click to expand...
Click to collapse
Pre-rooted rom must have "rooted" in their name, framaroot works for me.