Ok so the Defy is locked in the bootloader stuff, so we can't use our own kernels per se, and this is a new experience for me. What I want to know is how the SBF stuff works in conjunction with the kernel.
Story is, I MacGyver'd a Defy I bought cheap and revived. I flashed the first T-Mobile USA SBF listed in the SBF thread, got into 2.1 stock, OTA'd into Froyo and GingerBreak'd for root. 2nd init, ROM'd up with the wipes and flashies, and here we are. I'm currently testing CM10.
What I've noticed is my kernel version is different, comparing to screenshots. Could be Red Lens/+ users (I have GREEN lens) but some people have their build dates from Nov of 2011 and I'm in June of 2011.
What I'm thinking is, I should have used a different SBF due to the kernel difference? I'm in the USA so naturally I used the USA one that was listed. Should I use a different SBFs change the kernel? For better or worse? What do you guys recommend for myself?
captaincrook said:
Ok so the Defy is locked in the bootloader stuff, so we can't use our own kernels per se, and this is a new experience for me. What I want to know is how the SBF stuff works in conjunction with the kernel.
Story is, I MacGyver'd a Defy I bought cheap and revived. I flashed the first T-Mobile USA SBF listed in the SBF thread, got into 2.1 stock, OTA'd into Froyo and GingerBreak'd for root. 2nd init, ROM'd up with the wipes and flashies, and here we are. I'm currently testing CM10.
What I've noticed is my kernel version is different, comparing to screenshots. Could be Red Lens/+ users (I have GREEN lens) but some people have their build dates from Nov of 2011 and I'm in June of 2011.
What I'm thinking is, I should have used a different SBF due to the kernel difference? I'm in the USA so naturally I used the USA one that was listed. Should I use a different SBFs change the kernel? For better or worse? What do you guys recommend for myself?
Click to expand...
Click to collapse
Well June 2011 is latest one. I bought my phone in late July 2011 and it showed June 2011, so its OK.
Sent from my MB525 using xda app-developers app
Thanks for the reply. I'll ease on the what-if's for kernel stuff for now. Time to get CM10 smooth.
Related
Hey all,
my trusty froyo dx finally died on me, and today I received what looks to be a newer model dx. My questions are..
Are there any ways to tell what "gen" this new dx is? (subtle changes etc)
this device already came preloaded by Verizon with system 4.5.596, will i have any issues when I plan to root using z4?
Thanks a bunch
Yes, it won't work. If you want root, you have to SBF to froyo.
Are there any ways to tell what "gen" this new dx is? (subtle changes etc)
phillybizzle said:
Hey all,
my trusty froyo dx finally died on me, and today I received what looks to be a newer model dx. My questions are..
Are there any ways to tell what "gen" this new dx is? (subtle changes etc)
this device already came preloaded by Verizon with system 4.5.596, will i have any issues when I plan to root using z4?
Thanks a bunch
Click to expand...
Click to collapse
what makes it look like a "newer model".
It shouldn't be different? for the most part the droid X2 looks exactly like the droid X. so I don't think they would make changes to a phone that already has a successor
z4root will not work, you need to find a FULL sbf .340 stock and use RSDlite 4.8 and restore it to froyo. from there you can flash p3droid's rooted gb rom, which is essentially the same as the OTA
How do I root my Defy+? Also are the Defy+ roms compatible with the original defy roms?
Wondering the same thing.
Jades007 said:
How do I root my Defy+? Also are the Defy+ roms compatible with the original defy roms?
Click to expand...
Click to collapse
I have successfully rooted my defy + using doomlord's rooting tool.
URL
www.xda-developers.com/android/want-to-root-something-anything-try-doomlords-easy-rooting-toolkit/
My defy is a telstra branded unit running 2.3.6
I wouldn't bother with other roms just yet, mostly because of any telstra specific tweaks that you might lose, like nextG... Almost no other counties are using it, so any modded ROM based on a foreign ROM won't work without further tweaking. So bone up on how to get things working again should they break.
Once you've got the defy+ rooted you can remove the God awful telstraone app...it's pure poop. Just setup URL shortcuts to the services it tried to supply.
I'm on hols ATM and will try to cut out as much of blur as possible once i'm home.
Sent from my rooted defy+ 2.3.6 ;-)
i used SuperOneClick v2.3.1.0 and it worked whitout a problem
My response was more aimed at OP, and gauged by his avatar.
Telstra branded phones with 2.3.4, or once updated to 2.3.6, won't root with oneclick. Not the batch I experienced anyway.
NextG is a low freq variant of 3G chosen by telstra to cope with Australia's vast open spaces; hence they employ a custom production ROM. So what works in one country, on one carrier, won't necessarily work everywhere or any where else.
Sent from my rooted Defy+ 2.3.6 ;-)
i did it the way AzzA68 (thanks!), told everything ok with my new Defy+, it had the 2.3.5 with Telcel (Mexico)... greets
Mines rooted, i got Android 2.3.4.
Has anyone been able to get CWM working?
I'm not affraid to root defy+, it looks easy, but I can't find a good and functional guide, how flash CM or MIUI on Defy+
Some ideas?
Thanks guys
zugY said:
I'm not affraid to root defy+, it looks easy, but I can't find a good and functional guide, how flash CM or MIUI on Defy+
Some ideas?
Thanks guys
Click to expand...
Click to collapse
It's easy. Use SuperOneClick and as the name suggests it's just one click! The lastest version works on just about any android phone, including Defy+. - http://forum.xda-developers.com/showthread.php?t=803682
To install Cyanogenmod, there is a simple guide in a FAQ posted in the forum by one of the Dev's - http://forum.xda-developers.com/showthread.php?t=1065798
The way to install MIUI is basicly the same idea, except when it says to flash "update-cm-7.1.0-11-Defy-signed.zip"you flash the MIUI zip file instead.
SuperOneClick doesn't work with the defy+
Sent from my MB526 using XDA App
I've got a Defy+ running android 2.3.6. I'm planning to install MIUI on it, but I'm not sure if any of the rooting methods work with the .6 update of android :/
Some guys over at this thread tried to use DooMLoRD's easy rooting toolkit, but it doesn't seem to work for them either.
http://forum.xda-developers.com/showthread.php?t=1378668
Does anyone know a guaranteed safe way to root my phone which has been tried on 2.3.6?
fiskenigaten said:
Some guys over at this thread tried to use DooMLoRD's easy rooting toolkit
Click to expand...
Click to collapse
DooMLoRD and the latest version of SuperOneClick both use the same exploit (called zergrush). This appears to have been fixed in the latest versions of 2.3.6 shipping on the Defy+, hence no root for the moment.
fiskenigaten said:
Does anyone know a guaranteed safe way to root my phone which has been tried on 2.3.6?
Click to expand...
Click to collapse
Sorry, not at the present time. Just have to wait until someone finds another loophole that can be exploited, I guess. Might be worth keeping an eye on the main SuperOneClick thread for news - the dev does say on his blog that he's planning to focus on Motorola phones next. In the mean time I am looking forward (not much) to life with a non-rooted phone, depending on how mine comes back from UK repair agent (having managed to brick it by attempting to flash incompatible SBFs in the hope that one would then be rootable).
How are you supposed to make any kind of useful backups without ClockWorkMod and Titanium Backup?
Apparently SuperOneClick v2.3.3, releaed a few hours ago, has added a new exploit to root on "Motorola." Might be worth having another try with the latest version!
SuperOneClick Does work with my Defy+
SuperOneClick 2.3.3 worked fine rooting my defy plus.
Android 2.3.4
Retail GB version:- 45.0.82.MB256.Retail.en.GB
Kernel: 2.6.32.9-ga687192
Percz said:
Apparently SuperOneClick v2.3.3, releaed a few hours ago, has added a new exploit to root on "Motorola." Might be worth having another try with the latest version!
Click to expand...
Click to collapse
Yes! It worked perfectly on my mb256 2.3.6! Thanks, guys!
Latest version works fine
Sent from my MB525 using Tapatalk
I am preparing to move my defy to CM7.2 (or any custom rom) and I am currently stuck on Android 2.1.
I've read and researched everything about flashing and backup and what not... What I understand is:
1. If I flash a full SBF of a Android 2.2.x ROM, I won't be able to downgrade (I don't really need to as I am out of warranty anyways)
2. If I flash a FIXED SBF of 2.2.x or 2.3.x, I will need to also flash a nandroid backup. The problem is that I cannot find a pair of these to download (given all of the mediafire/etc links are now dead).
3. I really need a 2.3.x kernel to go to CM7 or CM9, most (all?) of these won't let me downgrade back to 2.2 (which if fine provided the 2.3.x stock rom I flash is rootable and will let me do wifi tethering).
My defy is green lens US Tmobile with Blur. I would probably be totally happy with a non-blur 2.2 or better rom. My motivation for this is that I need some apps that are 2.2+ :/
Thanks in advance for any help or guidance!!!
KevinAndEarth.com said:
I am preparing to move my defy to CM7.2 (or any custom rom) and I am currently stuck on Android 2.1.
I've read and researched everything about flashing and backup and what not... What I understand is:
1. If I flash a full SBF of a Android 2.2.x ROM, I won't be able to downgrade (I don't really need to as I am out of warranty anyways)
2. If I flash a FIXED SBF of 2.2.x or 2.3.x, I will need to also flash a nandroid backup. The problem is that I cannot find a pair of these to download (given all of the mediafire/etc links are now dead).
3. I really need a 2.3.x kernel to go to CM7 or CM9, most (all?) of these won't let me downgrade back to 2.2 (which if fine provided the 2.3.x stock rom I flash is rootable and will let me do wifi tethering).
My defy is green lens US Tmobile with Blur. I would probably be totally happy with a non-blur 2.2 or better rom. My motivation for this is that I need some apps that are 2.2+ :/
Thanks in advance for any help or guidance!!!
Click to expand...
Click to collapse
Yep what you told is pretty much correct! Just make sure you flash the correct SBFs (since it is greenlens).. And you may request to whoever uploaded to reupload the files.
For point 3.) CM7 and CM9 are available for Froyo kernel too.(And those are more frequently updated) So you can do a 2.2 SBF flash.
Moreover should you flash a fixed SBF you can always downgrade...
Happy flashing
you are awesome at answering my questions again! thanks =)
I now remember that CM7 + 9 can work with the froyo kernel, is there any reason to go to GB? I want to take this step by step... first is to get a working 2.2 version (deblured, since I am out of the country and had problems getting blur to reregister last time).
is there really any reason to go back to 2.1 if I go to 2.2?
i'll go beg on the ROMS thread to see if I can get one. Thanks!
Since you have a green lens (SOC) you should stay on the Froyo kernel. Do not go with the Gingerbread kernel because you won't be able to use your camera (except for the Greenbread mod, if I'm not mistaken, but you should stay away from it since it's a fix for a problem not an improvement).
I don't see any reason to go back to 2.1, especially because 2.2 was officially released and is covered by warranty. Since using ICS I won't even go back to 2.3 .
Trimis de pe Defy CM9
KevinAndEarth.com said:
you are awesome at answering my questions again! thanks =)
I now remember that CM7 + 9 can work with the froyo kernel, is there any reason to go to GB? I want to take this step by step... first is to get a working 2.2 version (deblured, since I am out of the country and had problems getting blur to reregister last time).
is there really any reason to go back to 2.1 if I go to 2.2?
i'll go beg on the ROMS thread to see if I can get one. Thanks!
Click to expand...
Click to collapse
Welcome Good to know I could be of help..
vap_66 said:
Since you have a green lens (SOC) you should stay on the Froyo kernel. Do not go with the Gingerbread kernel because you won't be able to use your camera (except for the Greenbread mod, if I'm not mistaken, but you should stay away from it since it's a fix for a problem not an improvement).
I don't see any reason to go back to 2.1, especially because 2.2 was officially released and is covered by warranty. Since using ICS I won't even go back to 2.3 .
Trimis de pe Defy CM9
Click to expand...
Click to collapse
Ya even I feel the same! Since it is green lens better not go to GB. What is the need when you have so many option of ROMs (just get an awesome CM7 nightly or CM9!)..
So now all I need to do is find a good deblured android 2.2 SBF =)
my defy was flashed with defy+ sbf with kernel version 2.6.32.9-ge281b6e. i hate it cause my battery wont work i need to use desktop charger since battery cant be recognize by the phone and the status is "?". also camera is not working.
i tried to flashed it with different sbf's found in this forum but none of it work! after flash phone wont boot unlike when you flash it with my current firmware.
i want at least to have my battery back to normal also camera if possible. i tried flashing it with other defy rom but i always got stuck. it seems that ICS was installed but the phone wont load it.
is there anyway to get back to my original firmware? or any upgrades that can fix this. please help.
Reply!
Hey there!
Before you do anything, you gotta root your phone. Then install 2ndint to get recovery mode menu. Only from there can you successfully flash roms and get it to work.
i have the same prob.
i can flash any rom for defy+
my phone is defy green.
i flash dfp 4.5.1-231 (bootloader 7)
my battery and camra not work.
any solution ?
Help
The bootloader is locked !!!
Hi ...
Is almost impossible to downgrade from 2.3.6 to 2.2.
Motorola Defy with green lens work just with 2.2. With "update" the camera will NOT work more and until now is not possible to downgrade !!!
All this, because Motorola don't want to unlock the bootloaders. I personally I have this problem and now am nervous on Motorola...
Most of HTC's and Samsung's have unlocked bootloaders. In this conditions, I wil not buy more Motorola.
gorillaz07 said:
my defy was flashed with defy+ sbf with kernel version 2.6.32.9-ge281b6e. i hate it cause my battery wont work i need to use desktop charger since battery cant be recognize by the phone and the status is "?". also camera is not working.
<snipped>
is there anyway to get back to my original firmware? or any upgrades that can fix this. please help.
Click to expand...
Click to collapse
If you want any help, we need to know your build number (not kernel). We can then find out what bootloader version you have (6 or 7). If you are on bootloader6 you can downgrade to froyo with a workaround, but on bootloader7, you're stuck.
Sent from my MB526 using Tapatalk 2
im on bootloader 9 i think
Root then install a rom..it's gonna work fine
Sent from my MB526 using Tapatalk 2
gorillaz07 said:
im on bootloader 9 i think
Click to expand...
Click to collapse
You're not on bootloader 9.10. That's not what we're talking about. If you find your build number under system settings -> about phone, we'll try to find out what firmware you flashed to find out what "e-fuse level" you're on. Or just give us a link to the sbf you have flashed.
pjgowtham said:
Root then install a rom..it's gonna work fine
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
No, we're talking about kernels here. If he is a green lens user on 2.3.6 kernel his camera will not work. He needs to downgrade to froyo. This is only possible on bl6. He can't flash a froyo kernel over bl6 or bl7 without flashing a special sbf.
Ya we can't downgrade..it's not possible..but that special sbf s not there too..an i rite?
Sent from my MB526 using Tapatalk 2
i flash dfp 4.5.1-231 on green lens (bootloader 7)
my battery and camra not work.
any sbf for downgrade to froyo ?
jalal-jap said:
i flash dfp 4.5.1-231 on green lens (bootloader 7)
my battery and camra not work.
any sbf for downgrade to froyo ?
Click to expand...
Click to collapse
Nope, sorry. No going back from there
theres rooting for bl7s i think...so the only solution would be using custom roms
Sent from my MB526 using Tapatalk 2
He can root, he can flash custom ROM's, but the only kernel he can use is the GB kernel, so camera won't work (he has green-lensed camera) and if he tries to flash a Froyo kernel, he will end up with a BL error.
Oh..i didn't know that...thanks auris...that's because I'm safe on Froyo and i haven't tried bl7 in practical..
Sent from my MB526 using Tapatalk 2
I just will my battery back and charge.
yes im on bootloader 9.10 no hopes then to downgrade?
gorillaz07 said:
yes im on bootloader 9.10 no hopes then to downgrade?
Click to expand...
Click to collapse
Bootloader 9.10 is not the same as the bootloader version, my friend (yes, it is confusing). If you de-pack an sbf , you'll find a lot of images for different partitions of your phone. The images are all called CG__.smg where __ is a number, e.g. CG31.smg or CG39.smg. Most of these images are signed by motorola with a special version number (e.g. 6 or 7 on defy+ roms).
Our TI Omap processor has an e-fuse built into it which is some sort of a flash counter. It doesn't count how many times you flash, but the level of the CG__.smg you have flashed onto your device. If you flash an sbf with a CG31 (the bootloader) on version 7, you'll never be able to flash a CG31 lower than 7. Motorola increases this number for every update they make, to ensure that a user always uses the latest motorola software. This means it is impossible for let's say a defy+ user on 2.3.6 to downgrade to 2.3.5.
everybody has bootloader 9.10 (EDIT: Most do, but I've seen 90.73 and some others as well), but it has been re-signed and made only to accept the newest kernels, so your green lens is stuck without camera. Only the latest Motorola sbfs are bootloader7 (as of june 2012)
yeah i figure that our cause in flashing you will see codes and code 39 takes time i guess we cant help but wait, thanks guys if theres any solution pop out hope someone will keep us up to date. thanks!!!
fiskenigaten said:
Bootloader 9.10 is not the same as the bootloader version, my friend (yes, it is confusing). If you de-pack an sbf , you'll find a lot of images for different partitions of your phone. The images are all called CG__.smg where __ is a number, e.g. CG31.smg or CG39.smg. Most of these images are signed by motorola with a special version number (e.g. 6 or 7 on defy+ roms).
Our TI Omap processor has an e-fuse built into it which is some sort of a flash counter. It doesn't count how many times you flash, but the level of the CG__.smg you have flashed onto your device. If you flash an sbf with a CG31 (the bootloader) on version 7, you'll never be able to flash a CG31 lower than 7. Motorola increases this number for every update they make, to ensure that a user always uses the latest motorola software. This means it is impossible for let's say a defy+ user on 2.3.6 to downgrade to 2.3.5.
everybody has bootloader 9.10 (EDIT: Most do, but I've seen 90.73 and some others as well), but it has been re-signed and made only to accept the newest kernels, so your green lens is stuck without camera. Only the latest Motorola sbfs are bootloader7 (as of june 2012)
Click to expand...
Click to collapse
Thanks.
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Auris 1.6 vvt-i said:
He can root, he can flash custom ROM's, but the only kernel he can use is the GB kernel, so camera won't work (he has green-lensed camera) and if he tries to flash a Froyo kernel, he will end up with a BL error.
Click to expand...
Click to collapse
Thanks.
Hello, I recently tried to get a custom recovery on my phone. tar yielded `bad magic` on the archive and the installation failed.. I thought nothing was actually changed on my phone, but when I did a reboot my phone didn't start back up. It's in a boot-loop. I tried clearing cache, data, and everything else but it's stuck. I'm convinced I need to reflash a stock ROM.
My only problem is I can't tell which ROM I need. I wasn't careful enough to write down the exact version numbers of everything for my MB525. I just know this:
It's a red-lense model.
Came with Android 2.1, but later upgraded to 2.2 (via the built-in carrier provided software update method)
The carrier for it is T-Mobile US.
I checked the list ( droid-developers.org/umts_jordan/list.php) , but there are two firmwares listed for T-Mobile US. I'm really afraid of getting a higher version that what I was at because of the whole fixed-system partition bit explained in the beginners guide. So I'll ask here before I break my phone. Basically, I want to eventually get CM running on it and such, but I want to always be able to fall back to the version of Android 2.2 that I was running previously.
Basically, which ROM is the one I need to get my phone booting again?
T-Mobile_MB525_6.19.0_1FF.zip - this one is CG39.smg version 2, so this one should be an Eclair.
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf - this one is CG39.smg version 4 - therefore - Froyo.
If you have previosly been on Froyo, don't try to flash the Eclair, or you'll end up with a BL error.
That worked! That's the one I figured I should use, but the version number on it is `6` unlike every other version 4 CG which is `3.4`.
Now that I got a good ROM to fallback on, time to get a custom recovery and try some custom ROMs
Actually, that version is Android 2.1. The firmware version is "2.1-Update1"
It worked for my phone anyway though. Not quite sure how.
Weird! Its CG39 version is 4, therefore I assumed it was Froyo... Didn't know there was a version 4 Eclair...
Sent from my MB526 using XDA
Auris 1.6 vvt-i said:
Weird! Its CG39 version is 4, therefore I assumed it was Froyo... Didn't know there was a version 4 Eclair...
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Is that an other downgrade sbf like bl6 froyo?
sent from my Defy+