[Q] SBF modifying? Is it possible? - Defy Q&A, Help & Troubleshooting

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

Related

[Q] SBF and bootloader

Hello!
I read here that MM2 bootloader is locked (still true?).
However I understand also that SBF signed by motorola can be flashed with RDSLite.
Despite the fact that the bootloader does not accept SBF with invalid signature I see around software like SBF-Recalc and SBF / MBN Depacker. So, why someone wrote them if non official SBF can't be flashed?
Are those software able to create signed SBF files (I read about leaked Moto private key) ?
Sre they able to repack a modified SBF that can be flashed to the MM2 (with a locked bootloader)?
About the SBF files, i'm interested in information about the meaning of the internal partitions. For some of them I couldn't figure out what they are for. Is there any information about this?
Thanks
Andrea
http://and-developers.com/partitions:cdt
Sent from my Milestone 2 XDA App

[Help] Bricked Phone

Hello guys, I'm having a problem with my phone. I was trying out some scripts to improve the performance of the ms2, then all of a sudden it stopped working. So I turned it off and rebooted it, that's when it never came back again.
Following that, I tried flashing a sbf file, but using the RSDlite, no file is "clickable" to start flashing. What should I do??
I was using the EndlessCM7 but now I just want it working.... Any help would do!
Thanks...
Edit: ok so after searching (a lot) the forum, I got the answer from a post by r2beta0
Get the official ROM and start with that. Flash the SBF and it should wipe everything and put you back to day one.
Kangburra said:
Get the official ROM and start with that. Flash the SBF and it should wipe everything and put you back to day one.
Click to expand...
Click to collapse
The RSDlite would not accept any sbf, so I had to modify the froyo sbf, renaming some file, and then it worked flawlessly
Link the r2beta0's post, so other people with your problem could unbrick their phones.
Sent from my Milestone 2 XDA App
Quote- r2beta0
"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"

For anyone having issues installing the 4.3.7 Verizon update

For anyone having issues installing the 4.7.3 Verizon update. Or who lost root after the update and want root back. This is what I did and it worked just fine.
-Reset your phone back to factory settings in the settings -> privacy menu or in recovery mode.
-Get RDS Lite 4.9 or newer and SBF your phone back to 2.3.3 gingerbread so you have a stock verizon 2.3.3 gingerbread install. All the software including the 2.3.3 US Verizon SBF are on XDA in the fourms.
-Root phone with superoneclick
-Install OTARootkeeper from play store. Backup root and then temp unroot in app.
-Take the OTA update from Verizon which will install just fine now
-Restore root with OTARootkeeper
Now you have a stock Verizon Droid Pro running Android 2.3.4 with root. Enjoy!
SBF Files
Where did you get the files? I searched for them and the only thread had a link that I couldnt use.
SBF flash is not necessary.
4.7.3 Put on Sd card and sew through the rekaveri. You'll get an error because of what you can not ask. I did not flash because of build.prop.
Next download 4.6.8 SBF. and parse for the manual
http://forum.xda-developers.com/showpost.php?p=13146095&postcount=3
and cast your files you want to place.
After this update will be in place. And you will not lose
Firmware files can be found here http://forum.motofan.ru/index.php?s=&showtopic=1730230&view=findpost&p=1625509
asf1187 said:
Where did you get the files? I searched for them and the only thread had a link that I couldnt use.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1419303
If you need RDS Lite just google for it. Make sure its 4.9 or up though.
it just seems not success?why,there is something wrong with me,please give me some matters need attention
send from debian for android

[HOW TO] Downgrade from 19.6.3 to 19.5.3 RSD Lite or Fastboot

Alright so to start off here's the usual, I'm not responsible if you brick your phone or if your computer starts spitting corrosive acid at you, you know the general anything and everything that can happen on this planet.
So basically I have two files I'm uploading right now. The flash.zip that you have to download and the RSD lite zip that is optional.
You need to download the flash.zip or both and extract them and install RSD. After doing so you'll have to put your phone into fastboot by powering it off and holding the power button and vol - key together until it pops up in AP flash. (YOU DON'T NEED TO DO THIS IF YOUR USING THE LAUNCH.bat)
After all of that you need to plug in your phone to your desktop and assuming you have all the drivers installed you need to either open RSD and select the xml in the folder you extracted from the flash.zip and select your phone and start the flashing process.
Now if your phone is not recognized by RSD you need to run the LAUNCH.bat and it will do the whole process in about 5-15 minutes (rough estimate)
After everything is done your phone will reboot and your on 19.5.3 and can root your phone permanently and gain system r/w permissions with my other thread HERE.
Credits:
Credit for the downgrade through fastboot go to myself and Google for fastboot of course.
Credits for the other stuff in the other thread are in the link up above.
Download Section:
FLASH.zip
RSD 5.7
Is this for unlocked bootloaders only? I just tried it and it keeps failing because I get this:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
RSD Lite says:
Failed flashing process. 2/17 flash partition "gpt.bin"
Really hope this isn't for unlocked users only cause I just wiped my phone for this to test it and root
Jay_P11 said:
Is this for unlocked bootloaders only? I just tried it and it keeps failing because I get this:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
RSD Lite says:
Failed flashing process. 2/17 flash partition "gpt.bin"
Really hope this isn't for unlocked users only cause I just wiped my phone for this to test it and root
Click to expand...
Click to collapse
Its for the non-dev Droid Maxx/Droid Ultra's with locked bootloaders. It sounds like your on a os lower than 4.4 or higher than 4.4. Can you give me your system specs? (Android version, System version, and phone model)
TheOriginalist said:
Its for the non-dev Droid Maxx/Droid Ultra's with locked bootloaders. It sounds like your on a os lower than 4.4 or higher than 4.4. Can you give me your system specs? (Android version, System version, and phone model)
Click to expand...
Click to collapse
Android 4.4.4
Build SU4.21
System Version 21.11.21.obake_verizon.Verizon.en.US
The update said it was 19.6.3 when I downloaded it so now I'm really confused
Jay_P11 said:
Android 4.4.4
Build SU4.21
System Version 21.11.21.obake_verizon.Verizon.en.US
The update said it was 19.6.3 when I downloaded it so now I'm really confused
Click to expand...
Click to collapse
Yeah it said that probably from a previous download or something whats important is that you didnt brick your device. Can you boot?
TheOriginalist said:
Yeah it said that probably from a previous download or something whats important is that you didnt brick your device. Can you boot?
Click to expand...
Click to collapse
All is well. I backed up my pics and stuff as I always do before trying something like this, so nothing major was lost. Just gotta re-install all my apps cause google backup somehow chose to not help me in my time of need but I guess the version I came from was what it said was 19.6.3 and I never bothered to double check before trying anything. Man would it be great if this worked on 4.4.4 though. Have you or anyone else tried the root method on 4.4.4? If not (unless you're sure it won't work) I'm willing to try the root process.
Jay_P11 said:
All is well. I backed up my pics and stuff as I always do before trying something like this, so nothing major was lost. Just gotta re-install all my apps cause google backup somehow chose to not help me in my time of need but I guess the version I came from was what it said was 19.6.3 and I never bothered to double check before trying anything. Man would it be great if this worked on 4.4.4 though. Have you or anyone else tried the root method on 4.4.4? If not (unless you're sure it won't work) I'm willing to try the root process.
Click to expand...
Click to collapse
No but I've tried my own exploits on other Android versions like 4.4 and 4.2.2 on this phone. I just wont risk updating to 4.4.4.
Thread is not needed. The simple process would be to simply download the fxz from the reputable sbfdevelopers and flash. Nothing else is needed. Again repost.
Topsnake said:
Thread is not needed. The simple process would be to simply download the fxz from the reputable sbfdevelopers and flash. Nothing else is needed. Again repost.
Click to expand...
Click to collapse
Again I am just trying to simplify things for people. Especially if they have issues with RSD Lite.

Help Recovering Please

I eventually decided to flash Kitkat onto my Defy+.
Followed this guide here:-
http://forum.xda-developers.com/showthread.php?p=52342403#post52342403
Everything worked fine until I got to the actual flashing of the KK Rom. TWRP had loaded fine but insisted I had no OS installed and on exit suggested device was not rooted?
Phone kept saying failed and to re partition. So I tried the Resize.zip from another guide. This did nothing either , still the same.
It had also had the following error, "Error Executing Updater Binary In Zip".
So I tried the solution here:-
https://kalitutorials.wordpress.com/2015/06/19/solve-error-executing-updater-binary-in-zip/
Now I cannot boot into TWRP or Clockworkmod recovery. When I try to boot phone it just sits on Motorola Sign but doesn't progress and no led flashes to enter TWRP. Battery needs to be removed to switch off.
If I power up with Volume down pressed, I get picture of Android Green Robot standing up with an yellow exclamation in a white lined triangle. No options are shown.
Pressing Vol up and down I get me to Android System Recovery <3e>. Options there are, reboot system now, apply update from sdcard, wipe data/factory reset, wipe cache partition.
I can also enter bootloader using vol up and power.
Any ideas anyone, found this guide to try to fix but don't want to try anything else without some confidence it will work.
http://www.tech-zealots.com/tutorials/unbrick-motorola-defy-or-defy-100-working/
I have a nandroid backup created in normal recovery btw. I would prefer to flash back to it if possible.
Thanks
G
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
dc239 said:
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
Click to expand...
Click to collapse
Thanks for your reply.
Tried what you suggested but after flashing that sbf the phone tries to boot up but after logo drops back to bootloader 9.10 with ERR:a5,69,35,00,27 .
I managed to get the Retail UK sbf referred to here:-
http://forum.xda-developers.com/showthread.php?t=1421526
Tried flashing it but end up with a black screen bootloader and just white led lit. Reflashed the sbf u suggested and back to Bootloader with Err.
Googling seems to suggest I am just needing to get the right sbf for the phone.
I have the Nandroid backup made with Clockworkmod recovery. Is there anyway to flash it?
TIA
G
Sorted
After extensive digging and climbing the steep learning curve. Decided the problem was that the sbf file u suggested was DFP 231 and possibly my phone was DFP 2311. Found Firmwares here:-
https://firmware.center/firmware/Motorola/Defy+ (MB526)/Stock/
And downloaded the DPF 2311 Rom, only was one. (DEFYPLUS_U3_4.5.1-134_DFP-2311_BLUR_SIGN_USADEFYEMARAB1B8TFDE004.0R_PDS03C_USAJRDNGIBRO2DE_P020_A025_M002_Service1FF.sbf). Tried flashing it and voila system is back, albeit it started up in German.
Gonna try the rooting mehod here:-
http://forum.xda-developers.com/showthread.php?t=1820282
For anyone elses benefit, the links for Roms at Android Developers don't work. The retail EU Firmware mentioned in the rootong guide is available on the site referred to above. U can tell when you click the link to the Android Developers site as the browser URL shows the full file name as follows.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
The rooted one I think is the same one you linked me to and is still valid in the Rooting guide too.
Thanks for all help and I hope this is of use to someone else.
G
Minor question still remains.
If I am trying to install Kitkat rom. DO I still need to Root phone if the rooted 231 has been installed, I presume not?
G
Followed rooting guide and so now have a rooted 231. All good
Now for KK.
G

Categories

Resources