I have flashed Defy+ DHT-25 SBF and it can't root. My device is a Defy with red lens.
If I want to install CM9, isn't that I should do the following?
1. Find a BL6 SBF that can root (better a small size one)
2. Root it.
3. Install bootmenu
4. Find a CM9 GB kernel ZIP and install it.
Is that right?
Where can I find a small size BL6 rootable SBF?
Which CM9 GB kernel is good?
i think your logic is right.
you can try miui.
i will try it now.
Related
We have an incorrect SBF for Defy+ DEFYPLUS_4.5.1-134_DFP-125_45.0.1250.MB526.NonEFIGSRetail.en.EU which has incorrect bootloader.
And we have a correct SBF file Defy+ 4.5.1-134-DFP-125-CEE.
With MotoAndroidDepacker we can extract (or repack) sbf file and then we get some smg files.
The CG39.smg contains the "system". This CG39 file is a simple image file, we can mount it under linux: mount -o loop CG39.smg /mnt
Is it possible to modify SBF file, and get a working NonEFIGSRetail.en.EU?
i downloaded and i want to try because i have a sbf file where the wifi has very good signal+no market and one that is newer and has market but the wifi is terrible weak signal. pls help, what to switch?
Modding sbfs is impossible because the locked bootloader checks that every sbf that is flashed/booted is signed by Motorola. If we change anything in the sbf, then we break the signature and we won't be able to boot. That's the reason why we can't play around with the kernel, which is something we'd all love to do.
CM7 + CM9 double boot
crakeron said:
Modding sbfs is impossible because the locked bootloader checks that every sbf that is flashed/booted is signed by Motorola. If we change anything in the sbf, then we break the signature and we won't be able to boot. That's the reason why we can't play around with the kernel, which is something we'd all love to do.
CM7 + CM9 double boot
Click to expand...
Click to collapse
Just searching for a way to "mod" my Pro Plus, and i bumped into this discution.
I want to try a modify a sbf file to flash it via RDS Lite ( we have no modded recovery or so for the Motorola Pro Plus ).
My question is this: Can't you try and "fake" motorola's signature on the sbf file. Or can you try and bypass the check for the signature?
mereTz said:
Just searching for a way to "mod" my Pro Plus, and i bumped into this discution.
I want to try a modify a sbf file to flash it via RDS Lite ( we have no modded recovery or so for the Motorola Pro Plus ).
My question is this: Can't you try and "fake" motorola's signature on the sbf file. Or can you try and bypass the check for the signature?
Click to expand...
Click to collapse
Well, you can't fake or bypass the signature, but you CAN modify an SBF file to some extent without touching the signature. See this thread:
http://forum.xda-developers.com/showthread.php?t=1097754
I installed 2.3.6 sbf via rsd lite and didnt quite understand what i was doing from there i bricked my phone but managed to get it working, is there any way at all that i can go back to 2.2?
If you flashed fixed sbf the answer is yes. For more info on this see this thread
so which are the fixed sbf's?
MotorolaDefyLuke said:
so which are the fixed sbf's?
Click to expand...
Click to collapse
This is a copy/paste from thread I mentioned above:
DOWNGRADE
If you come from Android 2.1 and never flashed Android 2.2 you can use the fixed sbf-files method. With this method you will have a option to downgrade to you personal stock Android 2.1 via direct sbf flash.
- First download nandroid backup and normal sbf file of you favourite rom.
- build your own fixed sbf:
- depack sbf-file with MotoAndroidDepacker and delete cg31.smg and cg39.smg
- repack sbf-file (MotoAndroidDepacker)
- install nadroid backup
- flash repacked sbf-file (this one without cg31/cg39)
More information: http://forum.xda-developers.com/showthread.php?t=945035
This is how you can make a fixed sbf - that's how fixed sbf looks like. If you flashed a full sbf then you can't downgrade no more.
Advice: read read read
thanks for the help
So yeah, I tried rooting my Defy+ but it failed in every try I did:
First I tried the tutorial on the CM Forum (for installing CM7) but it didn't work.
Second I tried SuperOneKlick and similar tools but all failed.
Third I searched in Google very much but only found ways with Flashing the ROM.
My problem now is:
1. I don't want to flash another ROM
2. I wan't to root my Phone for apps e.g. AdBlocker
My Versions and Numbers:
System Version: 45.0.2310.MB526.Retail.en.DE
Baseband Version: EPU93_U_00.60.03
Kernel Version: 2.6.32.9-ge281 b6e [email protected] #1
Build Number: 4.5.1-134_DFP-231
(dunno what you need or not)
So is there any way that I may have overseen to root my Defy+? (Without flashing a different ROM?)
just here http://forum.xda-developers.com/showthread.php?t=1542956&highlight=root+231
Edit: Only way is to flash them 2 roms as you have chosen the 231 version which is the latest one with no downgrades so you have to only use that version or higher (when it comes out)
Try this stock rooted rom.Just flash it via rsd lite!
I send the download link because i cant post link directly!
maybe to add im not that advanced^^ have no idea what you are talking about
can i also directly flash CM7 via rsdlite?
ok i tried to flash those thingys but rsd lite was unable to open these things saying me invalid filetype
what are you trying to flash? if you are using the link I sent you use the CEE versions (second one) As the CN one you have to flash 3 files instead or the 2 on the CEE one.
I have flashed that may times and it always works you might have to extract the .SBF file out of the zip folder. The RSD lite I have will do it for you but not sure if the older versions do.
Dear Friends
I know that if i want to go back to 0.32 based rom from official GB i have to first downgrade to Froyo. But my question is isn't there anyway by which we can directly flash Ezet's cm 7.2 without downgrading by modifying something may be? I am sorry, I am not a dev and don't know much about it, but the fact that i have to downgrade is kind of scary for me. There are a few more questoins;
How safe is downgrading to froyo?
What exactly is the (technical) reason why we have to downgrade (if at all) ?
My current setup is as following:
Rom: T.M.C. CM 7 (0.35)
Recovery: 5.5.0.4
Partition Scheme: Forumber's zip
I presume to downgrade I must do the following
1. Revert back to stock partition
2. Flash official froyo in pink screen mode by copying dload in internal as well as external sd card
Is this correct procedure?
Besides this i have my pink screen dump of stock froyo using dd on linux. Do you think restoring this backup is more safe in comparison to installing through pink screen?
Reasons why I want to downgrade : TS lag, Poor GPS in every 0.35 or 3.0.8 roms, poor battery backup.
Thanks for reading
Enlighten me friends....
Will this work?
Well the objective is to flash froyo baseband rom (e.g. Ezet's CM7.2) directly from gb baseband (404020) rom without having to install official froyo.
For now i know that the kernel and the baseband is different and from what i have read at droidforums.net
"The baseband is the subsystem of the phone that controls radio communications. It's a chipset on the phone that directly controls cellular hardware and communications with cell towers." (Enlighten me if this is wrong?)
Now i have the backup of my imei in 5iromtoolbox when i was on froyo. Does that also backup the baseband? If it does then
(1) We can reflash the froyo baseband on gb/ics(404020) using 5iromtoolbox, then
(2) replace recovery to 5.0.2.7
....????? (anything else required)
....????? (anything else required)
(?) flash cm 7.2 from Ezet?
Now the question is Will this work ? If so what will be exact steps
look at this
Can some dev look at this
http://forum.xda-developers.com/showthread.php?t=2205603
and tell weather a similar thing is possible for our device.
hello,
after reading almost everything i could read on the forums about the procedure of flashing roms, i'm left with a few questions that i couldn't find answers to, or i found more then one answer.I read all the following, and more:
1. [GUIDE] All-in-One Defy Beginner's guide by Zephyrot here: http://forum.xda-developers.com/showthread.php?t=1216982
2. [JB] CM10 Android 4.1.2 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=1768702
3. [GUIDE][KitKat][CM11] Updating to 4.4 by coolshahabaz here: http://forum.xda-developers.com/showthread.php?t=2568325
4. [Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=2515036
5. http://forum.xda-developers.com/showthread.php?t=2597719
6. http://forum.xda-developers.com/showthread.php?t=2644812
7. http://forum.xda-developers.com/showpost.php?p=49558697&postcount=3
8. http://forum.xda-developers.com/showpost.php?p=49558744&postcount=4
My devicee is a Defy+ with Gingerbread 2.3.6. I found here: http://sbf.droid-developers.org/phone.php?device=28 "Android 2.3.6 Blur_Version.45.0.1610.MB526.Partner.en.IL" rom which is supposed to be my stock rom.
1. My main concern is always to keep the option to go back to stock rom. As i read here, this might be a problem with Defy+, but only if i flash SBF files, which i dont plan to. Is it correct that i will be able to flash the stock rom with RDS_lite, motorola drivers and bootloader (power up with VOL up) at any time?
questions about recovery:
2. I understand that i need TWRP 2.3.6 in order to flash new roms, and since recovery is protected in Defy, i must use 2nd_init to bypass stock recovery. Is 2nd_init include the custom recovery in it? if so, which one? and what version?
3. can i install CWM or TWRP without using 2nd_init?
4. What is rom_manager (for CWM) or goo.im (for TWRP) and do i really need them?
5. what is update_recovery.zip mentioned as part of the procedure here http://forum.xda-developers.com/showthread.php?t=2515036 does it update the custom recovery or the stock recovery? is it really needed since some of the procedures described above skip this step?
choosing a custom rom:
6. I'm looking for adnroid 4.4. what is the difference between this: http://forum.xda-developers.com/showthread.php?t=2597719 (AOSP Android 4.4 for the Defy(+)) and this http://forum.xda-developers.com/showthread.php?t=2515036 (CM11 Android 4.4 for the Defy(+))
7. If i want a as-close-as-possible to google original kitkat 4.4, which one should i use?
Thanks,
Roy.
I have some of the same questions you have... will follow this topic, hoping for some info! thx!
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Click to expand...
Click to collapse
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
hotdog125 said:
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
Click to expand...
Click to collapse
Many many thks!
Im trying to up to CM 11 from 2 months.Now Im on 10.0(4.1.2).Every try to update recovery with "update-recovery.zip" or TWRP 2.6.3.0 finished with bootloop or without custom recovery and balck screen.And them flash stock .sbf and start all from the begining.And try and try....In your guide it have link to update recovery.It have something about 30+ seconds waiting after TWRP update.So I try.