Related
Any news on when this is gonna come out so i can SBF fully back to stock any info would be appreciated thanks
You can do this currently by combining .320 and .340 SBF files. I have not heard anything yet on a full .340 being released.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
Isn't this essentially a full SBF?
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
It contains the system-only SBF, as well as individual patches for the bootloader, kernel, and baseband.
aohus said:
Isn't this essentially a full SBF?
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
It contains the system-only SBF, as well as individual patches for the bootloader, kernel, and baseband.
Click to expand...
Click to collapse
I dont think so. I believe a full sbf overwrites the full phone image from /* in other words there is more to the OS architecture than just /system.
If im incorrect, anyone that has more info/corrections, please feel free to chime in.
Sent from my DROIDX using XDA App
NotATreoFan said:
You can do this currently by combining .320 and .340 SBF files. I have not heard anything yet on a full .340 being released.
-----
Sent from my Droid X. Powered by Big Red, customized by NATF.
Click to expand...
Click to collapse
Could you explain this process? Im running rubiX Focused on my 2.3.15 version and from my understanding, having the newest system software would be beneficial in installing and using newer roms etc.
I have both a nandroid backup of my stock albeit rooted setup of 2.3.15, as well as the system 2.3.15 sbf. I also have the 2.3.32 sbf file. I realize that if I sbf back to a clean 2.3.15, I can just accept the OTA update to 2.3.34.
Two questions from here:
Which method for updating would be best? From the OTA update to 2.3.34 would I be able to sbf back to 2.3.32 or would i be stuck until a 2.3.34 full sbf is released?
Sorry in advance for jacking the thread
*bump* would like to know this as well.
ElephantGlue said:
Could you explain this process? Im running rubiX Focused on my 2.3.15 version and from my understanding, having the newest system software would be beneficial in installing and using newer roms etc.
I have both a nandroid backup of my stock albeit rooted setup of 2.3.15, as well as the system 2.3.15 sbf. I also have the 2.3.32 sbf file. I realize that if I sbf back to a clean 2.3.15, I can just accept the OTA update to 2.3.34.
Two questions from here:
Which method for updating would be best? From the OTA update to 2.3.34 would I be able to sbf back to 2.3.32 or would i be stuck until a 2.3.34 full sbf is released?
Sorry in advance for jacking the thread
Click to expand...
Click to collapse
Tge limitation on whether or not you can go back is based upon the version if the bootloader that the sbf wird I believe. I have not used anything above the 2.3.15 sbf so I'm not sure if the sbf you're speaking of includes a bootloader version
Sent from my DROIDX using XDA App
If you use your 2.3.320 SBF you said you have, you can then use this update: http://www.droid-life.com/2010/12/09/droid-x-2-3-340-system-sbf-released-for-2-3-320-leak-users/
It should get you fully updated to 2.3.340. It does involve flashing your phone twice, but after that you should be good (as far as I know with my still limited knowledge of these things...)
Can't you just flash the 2.3.13 sbf then get the OTA update again? Any risk in doing that?
TreyStyles said:
Can't you just flash the 2.3.13 sbf then get the OTA update again? Any risk in doing that?
Click to expand...
Click to collapse
I don't think you can flash 2.3.15 once you have passed 2.3.320 as your bootloader will have been upgraded.
I recently flashed a full SBF of 2.3.320, then the Kernel, Baseband and Bootloader zips, then the 2.3.340 SBF. Bam, I have a stock phone that looks like it just came from Verizon. Its got all the preinstalled apps, blur, etc... it's basically stock 2.3.340.
For about 30 seconds until I rooted it and loaded Fission 2.4.3 on it...
nvrmnd..........
jeftep said:
I don't think you can flash 2.3.15 once you have passed 2.3.320 as your bootloader will have been upgraded.
I recently flashed a full SBF of 2.3.320, then the Kernel, Baseband and Bootloader zips, then the 2.3.340 SBF. Bam, I have a stock phone that looks like it just came from Verizon. Its got all the preinstalled apps, blur, etc... it's basically stock 2.3.340.
For about 30 seconds until I rooted it and loaded Fission 2.4.3 on it...
Click to expand...
Click to collapse
I had done this also, but I couldn't see to stop the phone from booting into Clockwork on a battery pull.
Which SBF Do I need?
I just bought a DX and am coming from a D2. I know how to do everything but it is confusing finding out which SBF i need. I need to know which SBF, or SBF's i need to unbrick phone if need be. Info for phone is as follows.
Android Version 2.2.1
Official OTA 2.3.340 (Guy updated to 2.3.340 at Verizon Store before i left with it.)
Thanks for any help.
Problem solved thread can be closed.
Sent from my DROIDX using XDA App
Android Version 2.2.1
Official OTA 2.3.340 (Guy updated to 2.3.340 at Verizon Store before i left with it.)
Click to expand...
Click to collapse
I'm in the same boat willjohnson, which sbf was the correct one? TIA
If you are already on .340, you do not need anything more than the .340 System-Only SBF released by TBH. Until Motorola has a new update that modifies the bootloader, or other components, no ROM you install will change these.
Bricked DX
has anyone ever seen the following:
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Ive been trying to flash this thing back to stock after botching a tranquility install and rsd lite wouldn't recognize my phone, then i tried to flash it anyway using a .340 sbf and then this is what i ended up with.
Please let me know.
thank you
That is just the system sbf, you are flashing. You need to be flashing the full sbf 2.3.32, if you are on bootloader 30.04.
Update everyone! I just started a thread in Development subfroum about a full 2.3.340 update zip that can flashed as long as you can access clockwork recovery. I recommend checking it out and downloading the file for safe keeping. It was put together by Maderschramm.
Getting ready to upload the full 2.3.34 sbf from a verizon retail store. Not sure if it's safe to put the direct link here. If not, send me a pm, should have it up by tonight at the latest. this is the official sbf and can be used with rsd lite.
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.
Hi,
recently ive been flash my defy using sbf files 2.3.4 build number 4.5.1_128 UK Retail. but unfortunately im not to pay attention on remark section "No Downgrade, No Root, camera not working". but maybe there is other way how to downgrade the sbf files so i can used sbf 2.2.2 build number JRDNEM_U3_3.4.3-33-1.
thanks in advance.
follow this http://forum.xda-developers.com/showpost.php?p=15341774&postcount=8 and be sure ur phone is atleast 80% charged while downgrading, good luck
But keep in mind after following this down grade guide that you can not just flash any sbf you would like afterwards! This is a "dirty" method of downgrading back to eclair and then upgrading back to froyo! Now that you have flashed a full 2.3.4 sbf you are stuck with CG39 and CG31 at level 5. Since all froyo sbf's containg CG39 and CG31 at level 4 you can not flash to them afterwards. For example, after using this downgrade guide you decide you want to switch to stock nordic froyo, you must find a nandroid of nordic froyo and restore it with CWM. You will then need to flash a fixed sbf of nordic froyo with CG39.smg removed and CG31.smg replaced with the CG31.smg from the full 2.3.4 sbf. I hope this all makes sense!
Just because you downgrade does not magically reverse the fact that you've already flashed a level 5 Code Group set. The downgrade involves flashing a unique chinese eclair which also has a level 5 CG set which is why you can flash directly to it with sbf. To get to froyo, the guide has you root this eclair and restore a CEE froyo nandroid. It then has you flash a fixed sbf of CEE froyo. This fixed sbf is CEE froyo sbf that has been depacked, CG39.smg has been removed and CG31.smg has been replaced with CG31.smg from 2.3.4 sbf. It is then repacked and flashed as a fixed sbf
YOU ARE STILL AT LEVEL 5 CG39.smg and CG31.smg
So I can depack a stock froyo 2.2.1 sbf and replace its cg31.smg with cg31.smg from the full 2.3.4 sbf and fhis way have a froyo sbf with level 5 files?
Sent from my MB525 using XDA App
yes ive already do tutor from Mahersa, but what i mean is how to make it that i can flash with full sbf original again, because i need to take to motorola for warranty...
It is impossible, as the new CG version is permanently burned into the processor.
I definitely do not recommend doing this, but I suppose you can flash the old SBF and somehow break the CPU enough so that Motorola can't read the CG version,
Other than that there's nothing you can really do, as replacing the processor is basically impossible and will cost more money than buying a new phone.
ooo sh*T, is it really motorola technician will try to read the CG version? im thinking to flash with lower sbf until screen go blank, and will say to CS "i dont know why my phone goes blank like this" and hope will get replacement ..
anyway i got strange now after i follow Mahersa tutorial, now my Defy using CM7 but the strange is my internal storage only 128MB OMG where is the rest of my 2 GB
tnsantos said:
So I can depack a stock froyo 2.2.1 sbf and replace its cg31.smg with cg31.smg from the full 2.3.4 sbf and fhis way have a froyo sbf with level 5 files?
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
No because the froyo sbf contains cg39.smg at level 4. CG39.smg is the system code group. If you remove this code group you remove the froyo system. This is why you must restore a froyo nandroid, because that will overwrite the system without flashing CG39 thus maintaining it at a level 5
Sent from my MB525 using XDA App
zyxwvut said:
No because the froyo sbf contains cg39.smg at level 4. CG39.smg is the system code group. If you remove this code group you remove the froyo system. This is why you must restore a froyo nandroid, because that will overwrite the system without flashing CG39 thus maintaining it at a level 5
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Ok, got it. If at last we have a way of manually increment these numbers... But it won't solve OP's problem with warranty. How can I see the current level of these files on my system?
Sent from my MB525 using XDA App
maulpersonal said:
ooo sh*T, is it really motorola technician will try to read the CG version? im thinking to flash with lower sbf until screen go blank, and will say to CS "i dont know why my phone goes blank like this" and hope will get replacement ..
anyway i got strange now after i follow Mahersa tutorial, now my Defy using CM7 but the strange is my internal storage only 128MB OMG where is the rest of my 2 GB
Click to expand...
Click to collapse
solved. after all done reset to factory default setting-->privacy all my internal memory back to normal...
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!!!
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.