sd_shadow, on 26 March 2012 - 11:01 AM, said:
104 replies to this topic
#41 OFFLINE#42 OFFLINEPosted 26 March 2012 - 11:34 AM chetan.saraf, on 26 March 2012 - 11:02 AM, said:
shud i try this on my D2G..... you just have to wait till someone, finds something that works Edited by sd_shadow, 26 March 2012 - 11:35 AM. #43 OFFLINEPosted 26 March 2012 - 11:45 AM
What can it hurt, his phone is already dusted. Besides, how do you ever know enough if you don't try. That's how I learned, by trail and error till I did know enough.
Device - Droid X / ICS 4.0.3
#44 OFFLINEPosted 26 March 2012 - 12:07 PM
Is there any other way other than RSD to flash the SBF file....
#45 OFFLINE#46 OFFLINE#47 OFFLINEPosted 30 March 2012 - 02:09 PM Here is a link some people with the droid x did. Those who could downgraded, then were able to access moto servers to find an sbf. Does anybody know how easily this could be done for the d2g? Furthermore, does anybody know of a way to edit the sbf files? If we can, we maybe be able to manipulate one so that the bootloader reads it as a newer file. Does anybody have any suggestions? Also, if you really want to do some programming, you can go into Linux and sbf off a linux based system. It wasnt too bad. here is the link to it, which isnt too bad. It was easier for me to do this, because I already have a Linux based system, as well as my XP and 7 machines. #48 OFFLINEPosted 31 March 2012 - 06:53 AM fishj96, on 30 March 2012 - 02:09 PM, said: Here is a link some people with the droid x did. Those who could downgraded, then were able to access moto servers to find an sbf. Does anybody know how easily this could be done for the d2g? Furthermore, does anybody know of a way to edit the sbf files? If we can, we maybe be able to manipulate one so that the bootloader reads it as a newer file. Does anybody have any suggestions? Also, if you really want to do some programming, you can go into Linux and sbf off a linux based system. It wasnt too bad. here is the link to it, which isnt too bad. It was easier for me to do this, because I already have a Linux based system, as well as my XP and 7 machines. if u cud help.... this is what it says now D0.11 Err:A5, 70,70,00,1F MEM_MAP Blank Service Req'd Battery ok ok to program connect usb data cable #49 OFFLINEPosted 01 April 2012 - 11:27 AM
Yeah, that is the problem most people have experienced when downgrading after taking the 4.5.629 update. If you took the 4.5.608 update, you can download the 4.5.608 sbf here:
and flash it but otherwise you have to wait until somebody can get the .629 sbf, which could take 2 minutes, or 2 months, or 2 years. I really do not know. Motorolla likes to be evil and hold them. People get them by scanning moto servers and sometimes they might hit them. The 4.5.629 update fixed a lot of bugs, but to those of us that got it but did not want it, it screwed us over. #50 OFFLINEPosted 01 April 2012 - 04:52 PM
So, I have been doing some research, at this point the phone is mine, and I want to get it back up and running so I have a backup.
Anyway, I read somewhere that it MAY be possible to extract the sbf contents, put in a file for the newer bootloader, and then zip it back up without needing the contents of whatever 4.5.629 is. Essentially, one would be taking the .608 file, and updating it so that the bootloader on the phone reads it as a newer sbf, so it allows the installation. My question is this: I already have the files extracted from the .sbf, but what file should I replace to update the bootloader. If somebody is on 4.5.629 can you send me a copy of the build.prop if possible that would be great. Also if somebody can (AT THEIR OWN RISK) download, but not install the 4.5.629 update.zip found in /cache/fota/update.zip I have read that the cdt.bin file contains the bootloader update. What I am hoping to do, again, I am no expert, but I do have some programming experience, is to give the bootloader a false sense of 4.5.629. May be a long shot, and I would really appreciate some input before I possibly waste my time on this. Edited by fishj96, 01 April 2012 - 04:53 PM. #51 OFFLINEPosted 01 April 2012 - 07:35 PM
I like the way your thinking... I know someone who has tracked down the build.prop file,
here is his XDA profile his personal email fulvio.ac@gmail.com He has been looking for a solution for 3 weeks or so, and someone sent him the build.prop, and is also after the default.prop anf flex version, for some reason, all to be sent to Dark Cricket Here is the thread where all discussions have taken place #52 OFFLINEPosted 02 April 2012 - 08:09 AM fishj96, on 01 April 2012 - 11:27 AM, said:
Yeah, that is the problem most people have experienced when downgrading after taking the 4.5.629 update. If you took the 4.5.608 update, you can download the 4.5.608 sbf here: and flash it but otherwise you have to wait until somebody can get the .629 sbf, which could take 2 minutes, or 2 months, or 2 years. I really do not know. Motorolla likes to be evil and hold them. People get them by scanning moto servers and sometimes they might hit them. The 4.5.629 update fixed a lot of bugs, but to those of us that got it but did not want it, it screwed us over. 1. 2. 3. BTW i hav already flashed it with No. 3 file thnx #53 OFFLINEPosted 02 April 2012 - 08:38 AM
You should be able to flash with the .608 sbf only. The 608 update prevents earlier files from working. Make sure you unzip it first, then use rsdlite to flash it. It should work for the D2WE
#54 OFFLINEPosted 02 April 2012 - 08:52 AM fishj96, on 02 April 2012 - 08:38 AM, said:
You should be able to flash with the .608 sbf only. The 608 update prevents earlier files from working. Make sure you unzip it first, then use rsdlite to flash it. It should work for the D2WE #55 OFFLINE#56 OFFLINEPosted 02 April 2012 - 09:43 AM
I thought it was .608 that started it and the 629 really killed it. Nonetheless, you should be able to fix it with a .608 sbf flash IF you had not taken the .629 update. If that one does not work, google the 608 sbf and someone should have a working copy of it somewhere.
#57 OFFLINEPosted 02 April 2012 - 10:00 AM fishj96, on 02 April 2012 - 09:43 AM, said:
I thought it was .608 that started it and the 629 really killed it. Nonetheless, you should be able to fix it with a .608 sbf flash IF you had not taken the .629 update. If that one does not work, google the 608 sbf and someone should have a working copy of it somewhere. #58 OFFLINEPosted 02 April 2012 - 10:24 AM
no, you updated to 4.5.629 or your phone tried
autoupdate updates started 01 march Quote . i've flashed back and forth from 2.4.33 and 4.5.608 no problems and least with Edited by sd_shadow, 02 April 2012 - 10:27 AM. #59 OFFLINEPosted 02 April 2012 - 10:57 AM
listen guys i m very very new to android so please tel me if there id any way to fix the problem and if not how much time it wud take for new sbf to come... :-(
sd_shadow, on 02 April 2012 - 10:24 AM, said:
no, you updated to 4.5.629 or your phone tried autoupdate updates started 01 march if it was just .608 you could flash sbf i've flashed back and forth from 2.4.33 and 4.5.608 no problems and least with and guys i m very very new to android so please tel me if there is any way to fix the problem and if not how much time it wud take for new sbf to come... :-( #60 OFFLINEPosted 02 April 2012 - 11:12 AM
maybe months till someone finds it on moto server
4.5.608 update.zip came out in oct 2011 SBF wasn't found till Jan 2012 they only way to fix is SBF 1 user(s) are reading this topic0 members, 1 guests, 0 anonymous users |
||