Hello, I did some not too intelligent things and I think my BL is now 7 (only working sbf I found was called DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf - though I'm on a green lense normal Defy). I then rooted/2ndInit and did the new_boostrap.zip/resize.zip for Quarx' newer 4.4 nightlies. Tried cm-11-20151105-NIGHTLY-mb52x for a while but couldn't unlock the SIM/change the baseband which is EPU93_0_U_00.60.93 (to EPU93_U_00.59.01 which is needed for softunlock?).
I now reverted back to an older build (4.4.2) via nandroid restore but the baseband is still 60.93 and I can't softlunlock the SIM here either (with lots of different zips from this thread and others)
Any ideas?
The only thing I can think of now is reflashing the sbf and then not getting the new_bootstrap but another older TWRP and trying to get some older nightly running with softunlock.
Any ideas would be greatly appreaciated ^___^
Related
Hello all!, how do I find out my bootloader version I have green lens defy and when I go onto bootloader it says 09.10? is there anyway to be certain what bootloader version I have?
Thanks
If you are on a green lense and haven't flashed a Defy+ stock ROM, you are either on CGXX version 3 if you are on Eclair (not very likely) or on CG version (the so called BL version) 4 if you are on Froyo.
Is there no other way to find out my bootloader version? because a bit ago I accidentally flashed Defy + SBF to my phone after that managed to recover it so is there a way I can find out what Im on right now? because every time I try and flash 2.2.2 Retail british it just says pass and keeps with white led light and then I have to reflash this eclair thing.
There is no way to tell by looking at the phone. You need to point the highest BL version ROM you have flashed, but if you have flashed GB stock ROM, you have to forget about your camera,
Thats the thing my battery and camera works fine? could I have BL5?
If you have ever flashed a GB stock ROM, you probably are on a BL 6 Chinese Froyo.
What SBF could I flash that wouldnt harm my phone to see if any work?
Questions go in the Q&A section
Dont know the previous history of my defy
Guys, I bought 2 defys(both red lenses) of ebay. Both came with miui 2.3.3 (android version 2.3.7) pre-installed, with second init. Kernel version is 2.6.32.9-gb08c3c8 [email protected] #1 Fri June 3 11:40:33 CST 2011.
Dont know what's the highest version sbf was installed by the previous owner. in the first defy, flashed stock froyo sbf, resulting into soft-brick. tried to bring it back to life by all the methods given here on forum, but all failed. Finally installed BL6 defy plus df-125 sbf, and phone is back to normal, rooted with superoneclick with second init working.
Dont want this to happen on my second defy.
Want to know which sbf to flash in the second defy without elevating the BL version. Any method to check the current BL version.
forthe said:
Guys, I bought 2 defys(both red lenses) of ebay. Both came with miui 2.3.3 (android version 2.3.7) pre-installed, with second init. Kernel version is 2.6.32.9-gb08c3c8 [email protected] #1 Fri June 3 11:40:33 CST 2011.
Dont know what's the highest version sbf was installed by the previous owner. in the first defy, flashed stock froyo sbf, resulting into soft-brick. tried to bring it back to life by all the methods given here on forum, but all failed. Finally installed BL6 defy plus df-125 sbf, and phone is back to normal, rooted with superoneclick with second init working.
Dont want this to happen on my second defy.
Want to know which sbf to flash in the second defy without elevating the BL version. Any method to check the current BL version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=11588065
Sent from my MB526 using xda app-developers app
cyrusct82 said:
http://forum.xda-developers.com/showthread.php?p=11588065
Read wiki: http://forum.xda-developers.com/wiki/Motorola_Defy
Click to expand...
Click to collapse
Thanks for the links. Have already read them when my first defy was soft bricked. The issue is it failed to boot even with bl5 sbfs. Had to flash a BL6 SBF to make it working. My second defy which is still on miui 2.3.3 needs tinkering. But for that I need a safe base rom sbf, don't know the present bootloader version, because I got it from someone with miui preinstalled.
Sent from my MB525 using xda app-developers app
There was some Chinese app for this, but I don't recall the name. You can check bl version by hit and trial, starting from 5, or to be safe from 4. At the point when you don't get the boot loader error, you will come to know about the current bl version
Sent from my MB526 using Tapatalk 2
hello,
When flashing ROM should we check previous OS baseband, kernel version and androidn version ?
I heard from my friend that you cannot flash older andriod version on previous version such as installing 2.3.3 on 4.1.2. Also, he said that baseband much match the new ROM otherwise the phone will be bricked. Is this true ?
mr.ab18 said:
hello,
When flashing ROM should we check previous OS baseband, kernel version and androidn version ?
I heard from my friend that you cannot flash older andriod version on previous version such as installing 2.3.3 on 4.1.2. Also, he said that baseband much match the new ROM otherwise the phone will be bricked. Is this true ?
Click to expand...
Click to collapse
Your mate doesn't know much. You can flash any firmware, old or new so long as it is for that phone.
You can also mix and match modems and kernels, also so long as they are for that phone model.
No phone I know of has gone from 2.3.3 to 4.1.2 unless the 4.1.2 was a custom firmware. Even so you could still flash it back to an older firmware in odin or even cwm recovery (depends).
It's quite rare that a modem will cause a problem but it has happened. For instance on the S3 the baseband was updated at one stage, so that using an older baseband on newer firmware resulted in no outgoing call sound. But that was an easy fix. Just needed to relash a newer modem.
I only know of one instance where flashing a certain kernel on a certain rom caused a complete brick. That was on the S2 with one firmware version I believe.
Finally, if you are thinking of flashing and don't have much experience, my advice is read read read until your eyes burn. This forum is a good starting point.
Sent from my GT-I9505 using xda premium
Hello there everyone,
I'm new here (mainly registered just to ask since no-one could help) and in need of some help.
I have a samsung galaxy GT-I9500 and I cannot upgrade above 4.4.2.
When flashing an AOSP roms or roms above 4.4.2 (eg. 4.4.4) my device seem to lose it signal in for of:
Baseband Unknown and Null IMEI.
I have tried flashing different modems and kernels with no effect, The only thing that seem to work is flashing stock 4.4.2.
Currently i'm on stock:
PDA: I9500XXUGNH4
CSC: I9500OJKGNI1
MODEM: I9500JKUGNH1
*I think the problem might be a the EFS partition formatting getting wrong partitioning (Again I have no technical idea what-so-ever)
Any help will be appreciated :^)
Thanks in advance,
Old Geezer
Old_Geezer said:
Hello there everyone,
I'm new here (mainly registered just to ask since no-one could help) and in need of some help.
I have a samsung galaxy GT-I9500 and I cannot upgrade above 4.4.2.
When flashing an AOSP roms or roms above 4.4.2 (eg. 4.4.4) my device seem to lose it signal in for of:
Baseband Unknown and Null IMEI.
I have tried flashing different modems and kernels with no effect, The only thing that seem to work is flashing stock 4.4.2.
Currently i'm on stock:
PDA: I9500XXUGNH4
CSC: I9500OJKGNI1
MODEM: I9500JKUGNH1
*I think the problem might be a the EFS partition formatting getting wrong partitioning (Again I have no technical idea what-so-ever)
Any help will be appreciated :^)
Thanks in advance,
Old Geezer
Click to expand...
Click to collapse
Maybe this problem is caused by an old recovery? How are you installing custom ROMs? Throug recovery? And if yes, which one are you using?
Tkkg1994 said:
Maybe this problem is caused by an old recovery? How are you installing custom ROMs? Throug recovery? And if yes, which one are you using?
Click to expand...
Click to collapse
I install roms thrugh Philz touch recovery and I make sure to erase everything (eg. cache system data etc.)
When checking my efs folder though I got bunch of files no Idea if they need to be there or not lol...
If on stock rom it works, then your partition is fine. Stay away from the /efs folder.
Try a different recovery / update your recovery. Try changing the modem.
If it still doesn't work then it's probably a bug in the rom.
Lennyz1988 said:
If on stock rom it works, then your partition is fine. Stay away from the /efs folder.
Try a different recovery / update your recovery. Try changing the modem.
If it still doesn't work then it's probably a bug in the rom.
Click to expand...
Click to collapse
I can't flash ANY 4.4.4 roms I don't talk about specific one, and as I mentioned I tried changing to all available modems.
As for recovery I use the latest philz touch and in TWRP it won't work either.
So it not the recovery fault.
Old_Geezer said:
I can't flash ANY 4.4.4 roms I don't talk about specific one, and as I mentioned I tried changing to all available modems.
As for recovery I use the latest philz touch and in TWRP it won't work either.
So it not the recovery fault.
Click to expand...
Click to collapse
That's because ANY 4.4.4 is based on CM. So if it's a bug in CM, then ANY 4.4.4 will have that bug.
You could try some older builds from CM and see if they work.
Lennyz1988 said:
That's because ANY 4.4.4 is based on CM. So if it's a bug in CM, then ANY 4.4.4 will have that bug.
You could try some older builds from CM and see if they work.
Click to expand...
Click to collapse
I saw other people with I9500 being able to flash those roms just fine, could it be MY phone have the problem in particular and if so what might it be..?
Hi everyone
i've been out of the loop for ages, and still rocking the ancient 4.3 rooted "root-de-la-vega" version
My questions are thus:
1- will updating to 5.0 OF1 via keys even work? or am i risking a brick/other fudge-up?
2- if the above is not supposed to work, what's the best way to go about this?
3- is it possible to use the wifi hotspot on the new OF1 build after rooting? i'm not a verizon client.
I searched the forums a lot, doesn't seem like anybody stayed on 4.3 for so long he'll have to do 4.3-->5 as well
Any answer is much appreciated. thanks
I can't tell you anything about Kies, sorry.
I unlocked my bootloader on 4.3 / MJ7 using the same binary from the bootloader unlock thread (@donc113's from post #318 or something) . It would probably work for you on your current ROM as well.
I kept the MJ7 firmware ( still have it! )
The M* series (MI9/MJ7/MJE) firmware will not boot the N* (4.4) or O* (5.0) stock ROMs. Similarly you have to use the TWRP -4.3 variant in the custom recovery for the same reasons if you retain M* series booting firmware.
Curiously, however MJ7 bootloader will boot the CM13 custom ROM, as will later bootloaders. I suppose that means the later bootloaders are backwards-compatible to the older DTB (Device Tree) meta data format used in booting 4.3 ROM kernels.
I am a VZW subscriber, so I don't know if there are issues using the CM13 ROM on other carriers.
good luck
PS CM13 has WiFi and USB hotspot/tethering built in. I would be using that ROM right now were it not for some GPS issues - the whole reason I stayed on rooted MJ7 for so long was because of the hot spot bug/"feature".
First of all hello to everyone!
I have quite weird problem:
I have my phone rooted and customized since day one - Installed KitKat, tried some launchers, unlocked UPSM and so on.
It ran flawlessly for nearly 4 years.
Recently, for no particular reason I decided to wipe&refresh it and maybe install some totally custom ROM.
NOW: I can install ROMS like Lineage 14.1, 15.1 or Resurrection Remix 6.0 and they run fine except (yes, You probably guessed it) they mess up baseband and IMEI.
I can still revert to original 4.4.2 stock ROM and both baseband and IMEI work fine so i'm not in any "brick panic"
The point is I still want to move to some custom ROM but can't sort out baseband-modem and IMEI problem.
I tried to flash several different modems to no avail - sometimes (totally randomly) IMEI showed up on first boot after flashing but was gone after reboot.
- On my current 4.4.2 stock, IMEI shows up correctly NO MATTER which modem version I flash (is it weird or normal or what?)
- none of modem versions work on Lineage OS nor RR
- SIM card works flawlessly on all other devices and on my current 4.4.2 ROM so it's not damaged.
Is it matter of proper custom ROM+MODEM combination or something else?
Can anyone help to sort it out?
What more information do You need?
Thanks in advance!
Flash the latest lollipop stock firmware to update your bootloader.
Yeah, meanwhile I did flash lollipop an hour ago and it works fine with IMEI and all.
Latest version I could find for my phone was Lollipop 5.0
How can I tell if bootloader is updated?
Can I Flash sole bootloader independently via Odin?
Mikuda said:
Yeah, meanwhile I did flash lollipop an hour ago and it works fine with IMEI and all.
Latest version I could find for my phone was Lollipop 5.0
How can I tell if bootloader is updated?
Can I Flash sole bootloader independently via Odin?
Click to expand...
Click to collapse
Yes you can. Go to this thread https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504
Thank You all for help and pointing to right direction!
Taking care of proper bootloader version was the key step that sorted things out.
Now I'm enjoying superlite bloatware free 8.1 oreo with LineageOS 15.1 on great 4 yrs old device.
And it works super smooth. Way better then original 4.4.2.
Now I'm being tempted to push the limits and try 9.0 Pie with LOS 16...
Whenever flashing a stock ROM with Odin, the stock ROM includes a bootloader and modem file.