Can you provide a step by step guide how you flashed the GB sbf to your phone. I wanna give it a try as well.
Sent from my MotoA953 using XDA App
Sent from my MotoA953 using XDA App
Extracted SBF with sbf_flash -x or mono SBFDepackerMono.exe (opens a window)
Yes, I checked the SBF thread and found this tool, lookout:
Code:daniel@daniel-server:~/Área de Trabalho/smgver$ wine smgver.exe CG31.smg CG31.smg: signature not found! daniel@daniel-server:~/Área de Trabalho/smgver$ wine smgver.exe CG39.smg CG39.smg: signature not found!
Maybe we got the wrong unsigned SBF after all...
Uploading nandroid backup
Install instruction can find on first post.
Uploading nandroid backup
Install instruction can find on first post.
So it means if we follow this instruction with the files you upload, and we can boot the leak
GB rom successfully?
Ah okay...defy is way different :/
Sent from my MotoA953 using XDA App
Ok, a basic explanation on linux permission model:
All files/folders in linux have 3 different permission settings. The first is permission for the owner, second is permission for the group and 3rd is permission for everyone else.
In your example you have: -rw-r--r-- which means
- is not a directory (the first bit shows 'd' or '-')
rw- owner can read and write (if it were rwx he could also execute)
r-- group can only read (missing w and x flags)
r-- others can only read.
To set permission with chmod command:
1 - permission to execute
2 - permission to write
4 - permission to read
Code:You have to sum up numbers to give the permission you want. Lets for example give rwx (owner) rw- (group) r-- (other) 4+2+1=7 4+2+0=6 4+0+0=4 So your command would be: chmod 764 file
Easy right?
I built a fixed sbf without CG31@39.smg using the signed leak and MotoAndroidDepackerMono. And the nandroid backup(/system) I use this
http://xdaforums.com/showthread.php?t=1185878.
Then I follow every step you posted. But with no luck, I still got a total failure. My phone went into black screen after a short logo M, and I can`t even boot into motorola recovery.
Did I do something wrong? Or due to my bootloader is the new one,70.13 ?
Edit: which .smg in sbf is the kernel ?
Edit2: BL 70.13 could not be downgraded. Now I have flashed back to 2.2.2.
No...
CG ## Link ## Partition (/dev/block/mmcblk1:)
31 ## cdt.bin ## p6
32 ## prek(?) ## p22/23
33 ## cdrom ## p17(linked)
34 ## lbl ## p8
35 ## boot.img ## p15(linked)
39 ## system.img ## p21(linked)
40 ## cache ## p24(linked)
42 ## logo.bin ## p10
45 ## bpsw ## p14
47 ## recovery ## p16
53 ## kpanic ## p20
61 ## devtree ## p12
64 ## mbr ## ???
65 ## ebr ## p4
66 ## preinstall ## p25
Working folder's boot.img information (dsixda Android Kitchen log)
-------------------------------------
Kernel Base Address : 0x10000000
Page Size : 2048 bytes
Command Line: "console=ttyS2,115200n8 rw mem=498M@0x80C00000 init=/init ip=off motobldlabel=none mmcparts=mmcblk1:p1(mbmloader),p2(mbm),p3(mbmbackup),p4(ebr),p5(bploader),p6(cdt.bin),p7(pds),p8(lbl),p9(lbl_backup),p10(logo.bin),p11(sp),p12(devtree),p13(devtree_backup),p14(bpsw),p15(boot),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(prek),p23(pkbackup),p24(cache),p25(preinstall),p26(userdata)"
No...
My thoughts:
Code:CG ## Link ## Partition (/dev/block/mmcblk1:) 31 ## cdt.bin ## p6 32 ## prek(?) ## p22/23 33 ## cdrom ## p17(linked) 34 ## lbl ## p8 35 ## boot.img ## p15(linked) 39 ## system.img ## p21(linked) 40 ## cache ## p24(linked) 42 ## logo.bin ## p10 45 ## bpsw ## p14 47 ## recovery ## p16 53 ## kpanic ## p20 61 ## devtree ## p12 64 ## mbr ## ??? 65 ## ebr ## p4 66 ## preinstall ## p25 Working folder's boot.img information (dsixda Android Kitchen log) ------------------------------------- Kernel Base Address : 0x10000000 Page Size : 2048 bytes Command Line: "console=ttyS2,115200n8 rw mem=498M@0x80C00000 init=/init ip=off motobldlabel=none mmcparts=mmcblk1:p1(mbmloader),p2(mbm),p3(mbmbackup),p4(ebr),p5(bploader),p6(cdt.bin),p7(pds),p8(lbl),p9(lbl_backup),p10(logo.bin),p11(sp),p12(devtree),p13(devtree_backup),p14(bpsw),p15(boot),p16(recovery),p17(cdrom),p18(misc),p19(cid),p20(kpanic),p21(system),p22(prek),p23(pkbackup),p24(cache),p25(preinstall),p26(userdata)"
Edit: Milestone 2 is more like a Droid X than a Milestone 1, so look at that link thinking of it.
After depacking the 70.13 bootloader.sbf, I found these 3 files:
RAMDLD.smg ramdownloader
CG30.smg mbm
CG32.smg bploader
I think mbm is bootloader, bploader is baseband loader an RAMDLD is just the file that "talks" to the bootloader when flashing.
Try to flash Brazil 3.21.0 SBF or Argentina's 3.23.0 and see if bootloader downgrades.
-----------------------
For the guys with engi phones, maybe you have a different version of the bootloader (or had before flashing a SBF...) that could unlock (or brick) normal devices.
I'm gonna sleep now.
Sent from my Milestone 2 XDA App