Related
Hello all,
After many months of excitement, Motorola Canada released Froyo(2.2.1) for the Telus Moto Milestone. Through all of this, it seems like I've gotten the DSI and kernel errors. The 4 capacitative keys take a while to respond (3 times before they work), and my keyboard and contacts/messaging are all screwed up, color-wise.
I was looking at rooting following this guide (http://forum.xda-developers.com/showthread.php?t=983516) but do not know if the vulnerable sbf's would be able to work now that I have 2.2.1.
Also, I have been told that FroyoMod is a very stable Froyo ROM, which I was looking to customize with a Gingerbread theme that he has released (http://forum.xda-developers.com/showthread.php?t=815595). Will I be able to follow the same tutorial to revert back to stock 2.1 then apply the official Moto update (in case I need to return it for servicing)?
I've heard rumors of people bricking their phones after applying faulty radios after flashing a custom ROM. Will I need to worry about applying the proper radio? Or is fairly painless to do?
What happens if I brick my phone if I apply a wrong radio?
Sorry for all these questions, I'd like to make this entire process as easy as possible and I've never rooted a phone before!
Thanks in advance!
skadude66 said:
Hello all,
After many months of excitement, Motorola Canada released Froyo(2.2.1) for the Telus Moto Milestone. Through all of this, it seems like I've gotten the DSI and kernel errors. The 4 capacitative keys take a while to respond (3 times before they work), and my keyboard and contacts/messaging are all screwed up, color-wise.
I was looking at rooting following this guide (http://forum.xda-developers.com/showthread.php?t=983516) but do not know if the vulnerable sbf's would be able to work now that I have 2.2.1.
Also, I have been told that FroyoMod is a very stable Froyo ROM, which I was looking to customize with a Gingerbread theme that he has released (http://forum.xda-developers.com/showthread.php?t=815595). Will I be able to follow the same tutorial to revert back to stock 2.1 then apply the official Moto update (in case I need to return it for servicing)?
I've heard rumors of people bricking their phones after applying faulty radios after flashing a custom ROM. Will I need to worry about applying the proper radio? Or is fairly painless to do?
What happens if I brick my phone if I apply a wrong radio?
Sorry for all these questions, I'd like to make this entire process as easy as possible and I've never rooted a phone before!
Thanks in advance!
Click to expand...
Click to collapse
1. The sbf will still work, sbfs replace everything...so version does not matter
2. Radios are not such a big deal on milestone, they an be easily swapped from AOR ( if you mean basebands, i dont know of any radio files other than this)
3. You can usually reflash older sbfs, unless bootloader changed
Sent from my Milstone running CM7
Caz666 said:
1. The sbf will still work, sbfs replace everything...so version does not matter
2. Radios are not such a big deal on milestone, they an be easily swapped from AOR ( if you mean basebands, i dont know of any radio files other than this)
3. You can usually reflash older sbfs, unless bootloader changed
Sent from my Milstone running CM7
Click to expand...
Click to collapse
So I will be able to use the 2.1 sbf for Canada over the 2.2.1 official Moto update that I have right now?
How would I swap the basebands and I'm guessing AOR is OpenRecovery? How would I do that.
Does anybody know if the bootloader for 2.2.1 changed?
Thanks!
skadude66 said:
So I will be able to use the 2.1 sbf for Canada over the 2.2.1 official Moto update that I have right now?
How would I swap the basebands and I'm guessing AOR is OpenRecovery? How would I do that.
Does anybody know if the bootloader for 2.2.1 changed?
Thanks!
Click to expand...
Click to collapse
1. I dont know if you can resinstall 2.1 on top of 2.2, you should...but i have never tried. At wore, you could use one of the 2.1 based roms in the dev section...i wont be the official version, but it will be eclair.
2. AOR is Androidiani open recovery...it is a different version or openrecovery with a bit more options. There is a change baseband submenu that lets you install the baseband files for each country.
Sent from my Milstone running CM7
People are saying that the bootloader is different between 2.1 and 2.2.1, so I think I might wait and see what others think before I try and root it. Thanks for your help!
any luck since then to root your Milestone from 2.2.1?
i was thinking since the razr ics update will have a signed kernel and it will be able to pass through the bootloader if we could use the razr ics update(since its like our roms all cross platform due to same processor,resolutions) and mod it a little so there is no 4G or webtop and change the device name to D3/solana then flash it as an update instead of a zip in recovery/fastboot like as if it was an OTA update that we sideload. we may have to return to stock to do this, or use otaroot keeper? i dont know if it will need to be re signed after changing things. but since this is an official kernel and the zip has a path motorola made it may get passed our bootloader if the unlock process is the same for all phones.
also maybe someone with a RAZR can use adb and see the commands during the update process to see if the phone spits out any lines of code when it opens the bootloader to replace the kernel?
I'm guessing it won't work as the kernel is signed only for that device and not the d3. Not to mention hw differences.
Sent from my XT862 using xda premium
the cameras are the same, they both have the same processors just razr is .2 ghz faster and running a little version different, the way they use the camcorder is the same, and the way they run flash player/hardware accelleration is the same. if we can trick the GB kernel to run the roms we have now then tricking the phone to use the razr kernel could be easy given we can get it passed the bootloader securely. once its passed the BL hashcode can get codecs to take a little easier since we will have the ability to run the DEV- ION drivers instead of getting ducati to decode and re code them for the GB kernel.
this may be worth a try instead of everyone saying "oh that wont work," then waiting god knows how long until hash gets the codecs to work, or motorola might just update up in 3-6 months. it might be a sloppy thing but it may work
double post
I doubt it'll work. The keys used to sign the Droid 3's kernel and the Razr's kernel are different. It would be just as hard (and really, afaik, impossible) to get our devices to run the Razr's kernel than it would be for us to get it to run any other kernel we can make/compile.
Sent from my XT862 using XDA
Keep brow beating Motorola, they "promised" unlock, blah, blah, blah
If we don't push though you'll never get anything.
im hoping hashcode gets the codecs working by may/june, if not then ill just go pick up a used D4/razr since they should be 100% on it by then or maybe a gnex off CL for 300 i really want to keep the d3 though.
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
saintlikesniper said:
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
This what will likely happen
Sent from my XT862 using xda premium
I could be mistaken here, but it is my understanding that the kernel acts as a sort of intermediate between the phone's hardware and OS. Seeing as how the RAZR lacks a physical keyboard, there could likely be some very pertinent information missing in it's kernel that is needed in order for the D3 keyboard to be usable. If this is the case, we would probably be better off attempting to utilize an ICS leak for the D4.
Sent from my DROID3 using Tapatalk
Full disclosure: I'm not a dev. My eyes glaze over the second someone mentions compiling or code.
That being said, I feel that at this point, maybe these types of off-the-wall ideas might be valuable. Even if the OP wasn't 100% on the right track, maybe that will light a fire in a more capable person's head.
mikedyk43 said:
I could be mistaken here, but it is my understanding that the kernel acts as a sort of intermediate between the phone's hardware and OS. Seeing as how the RAZR lacks a physical keyboard, there could likely be some very pertinent information missing in it's kernel that is needed in order for the D3 keyboard to be usable. If this is the case, we would probably be better off attempting to utilize an ICS leak for the D4.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
see thats the thing, our ICS roms werent programmed to utilize a hard keyboard either (sourced on the Gnex) so we can have that fixed. what im getting at is the razr, bionic, D4 and D3 run the same OMAP 4430 processor with the same efuse so it should be the same key for the bootloader. when we package the signed bootloader with either a modded RAZR rom to remove 4G and webtop and/or rename the phone id then resign it OR package the signed kernel in our ics roms then *flash as a manual update* it may get passed the bootloader. since the EFUSE looks for official firmware, the razr ics rom is signed by moto and the kernel has the efuse keys attatched (for OMAP 4430) so it may let it in. we would need root access in the rom to do changes (freeze/delete webtop) etc. we also need to wait for a reliable flashable zip of the razr rom since the only way to get it is a fatal way(cheesecake). BUT this is the deal, if we do this this will totally take you off the upgrade path if there is even one anymore, so an SBF back to 2.3.4 will need to happen in case of anything.
Tyfighter said:
Full disclosure: I'm not a dev. My eyes glaze over the second someone mentions compiling or code.
That being said, I feel that at this point, maybe these types of off-the-wall ideas might be valuable. Even if the OP wasn't 100% on the right track, maybe that will light a fire in a more capable person's head.
Click to expand...
Click to collapse
hashcode is more than capable of doing this its just a matter of if hes brave enough to try since hes tried everything else and we havent heard anything about codecs in awhile.
A few things
1). Signed. This means you can't edit it, change it, modify it or do anything with it...and it has to be signed for your device. Razr kernel will not be usable, nor will a Droid 4 when it comes out later.
2). Our D3 ICS CM9 rom is not built off the GNex ROM, it's built from source (AOSP) modified by CyanogenMod team and then further modified by Hashcode. Hashcode is modifying it to work with the D3 Gingerbread Kernel and that is why the hardware keyboard works.
3). Unless Motorola releases an ICS kernel/Rom for the D3.....OR Motorola releases an unlocker for the bootloader......the best will see is a modified source built ROM running on the stock Gingerbread kernel.
I'm not going to list someone hacking/cracking the D3 bootloader signing key, etc.... While it's entirely possible.......the Droid 2, Droid X have still not been cracked....and they've been out how long now?
We can run something like Hashcode's CM9 ICS and enjoy it and hope that Hashcode can get as much out of it as possible.......running on top of the Gingerbread kernel.....other than that it's just going to be hoping/waiting for Motorola to do something.
T
saintlikesniper said:
It may work if we package the kernel into the ICS rom by hash or flash it separately. But who knows how much work it may take for that to happen. Also some DROID 3s may not be able to run that .2ghz faster so we have to tone that back. It maybe be simpler to port over razr ICS codecs
Sent from my DROID3 using XDA
Click to expand...
Click to collapse
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Willis111 said:
T
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Click to expand...
Click to collapse
i dont understand why we cant completely wipe the phone of the data/rom AND bootloader and create a custom bootloader.
I think that would be eFuse and harder than it sounds entirely. Again may be easier to port razr codecs when it becomes available. Which should be soon according to speculation
Sent from my DROID3 using XDA
Willis111 said:
T
The problem we run into (i messed with this idea a bit) is that /boot wont allow unsigned code, the file containing the kernel needs to be flashed to /boot and is signed by motorola so it cant be tampered with and is also signed with a product code allowing it to only be flashed on that model. We cant changed the model # in the file without altering the signature so the phone wont accept the flash anyways. As for flashing it along with hashcodes rom, i think thats what theyre trying to do with kexec (this seems to be the most likely way we have to get custom kernels running on any bootloader locked phones). The problem with kexec (it's an app that loads you into an alternate kernel after the first kernel has booted, it's like a handover) is that our kernels have to have kexec support compiled into them right now by motorola for it to work(not sure theyve done this). Really, without a bootloader unlock or kernel upgrade by motorola (meaning ics and a 3.0+ kernel signed for our phones) i think we're stuck with what we're doing atm.
Perhaps we could do something like move the /boot partition to somewhere else but i imagine it's been tried and moving /boot to a partition on internal storage or something probably just causes the phone to not boot at all.
Click to expand...
Click to collapse
We actually don't need Motorola to have compiled kexec in (fully, at least. I think there has to be some basic support there, which there might be). As long as we can load kernel modules (which I believe we can) we could create our own and run that. The problem with kexec, though, is that it drops kernel communications with the radio for long enough for the radio to think the phone has shut down or errored or something, and it will shut itself off. So, upon loading into the new kernel, the phone will have no radio, and the only way to reinitialize it is to go through the bootloader process again, which would mean we couldn't have an unsigned kernel. It would be nice if there was a way to communicate to the radio that the kernel wasn't actually shutting off yet or if there was a way to reboot the radio after switching kernels, but sadly there isn't (as far as I know).
I say we all put our computing power together to crack Motorola's private key that they signed the kernel with, [email protected] style.
</semi-sarcasm>
Edit: Okay, actually being productive here... is the radio image signed? Because we could use kexec to load a new kernel, but modify the radio code so that it doesn't assume something horrible has happened when the kernel stops communicating with it.
ssinisterss said:
i dont understand why we cant completely wipe the phone of the data/rom AND bootloader and create a custom bootloader.
Click to expand...
Click to collapse
Because even a fully wiped phone will only accept files that are signed by motorola.
I believe the only way we can see a custom kernel is using the method some guy (i forgot who) has been able to kinda do. He's on the Razrs forums and he was able to get a custom kernel running on his phone. Unfortuantly this kernel can only use 1 out of the 2 cores, so it is not done yet. From what I remember he gets the phone to boot with the stock kernel and then has his kernel installed over it. I think the boot up process takes a little bit longer but it is a small price to pay for customization.
Flashing the Razrs ICS is futile. The only thing we can do is maybe kang some prop settings and apks. That's about it. We'd have a better chance with the Bionic, but it's still unlikley it will help anything.
I've hacked my bionic for tmobile. If i install a custom rom, will i need to re hack it using radiocomm, etc?
Custom ROM's (in almost all cases) are merely edits to the /system partition of your phone. They do not make changes to the NVRAM portion of your phone where the baseband processor reads for network communication.
However, there is a small chance that the build.prop of the new ROM will need to be re-edited to enforce GSM mode for the phone.
I have a droid 3, Rooted, Currently Running on Stock Rom, Unlocked, Currently using AT&T..
Last Night I've tried putting Custom Roms in it. I've used safetrap recovery. It worked, but no signal...
From what I understood, safetrap allows you to have something like a multiboot rom or something..
these are the roms I've tested: droidforums.net/forum/steel-droid/193454-official-thread-steel-droid-3-15-2013-its-jellybean-time.html
both the roms for d3...
If I;m missing something, please let me know.. I'm getting really frustrated..
Thanks
Patrick
greedness said:
I have a droid 3, Rooted, Currently Running on Stock Rom, Unlocked, Currently using AT&T..
Last Night I've tried putting Custom Roms in it. I've used safetrap recovery. It worked, but no signal...
From what I understood, safetrap allows you to have something like a multiboot rom or something..
these are the roms I've tested: droidforums.net/forum/steel-droid/193454-official-thread-steel-droid-3-15-2013-its-jellybean-time.html
both the roms for d3...
If I;m missing something, please let me know.. I'm getting really frustrated..
Thanks
Patrick
Click to expand...
Click to collapse
I have the same issue, i remember hearing someone say they managed to get their phone working on att by modifying build.prop, but after i looked into it and even did something (didnt notice any change) i had no change.
greedness said:
I have a droid 3, Rooted, Currently Running on Stock Rom, Unlocked, Currently using AT&T..
Last Night I've tried putting Custom Roms in it. I've used safetrap recovery. It worked, but no signal...
From what I understood, safetrap allows you to have something like a multiboot rom or something..
these are the roms I've tested: droidforums.net/forum/steel-droid/193454-official-thread-steel-droid-3-15-2013-its-jellybean-time.html
both the roms for d3...
If I;m missing something, please let me know.. I'm getting really frustrated..
Thanks
Patrick
Click to expand...
Click to collapse
You must put in a modified build.prop after flashing the ROM if you're currently using the XT883 radio for AT&T. The radio does not get touched, you just need to push or copy the modified build.prop. You can copy the one from your stock rom to use and it should work fine, I run Maverick 4.0 with GSM mod.
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
It may have been flashed to the 883 radio. I would do a complete SBF.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
I have sbf'ed the phone, but it hasn't fixed the problem. I have installed the 833 radio previously and made sure I have pushed the build.prop into the system folder still without luck of fixing the problem. After a little more research, could the EFS folder be corrupt/deleted causing the problem?
Skreelink said:
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
Click to expand...
Click to collapse
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
dinosaur swagg said:
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
Click to expand...
Click to collapse
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
htsebar meafure
Skreelink said:
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
Click to expand...
Click to collapse
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
dinosaur swagg said:
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
Click to expand...
Click to collapse
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Skreelink said:
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Click to expand...
Click to collapse
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
dinosaur swagg said:
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
Click to expand...
Click to collapse
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Skreelink said:
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Click to expand...
Click to collapse
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
dinosaur swagg said:
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
Click to expand...
Click to collapse
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Skreelink said:
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Click to expand...
Click to collapse
Okay so I have the 883 modified build.prop. Do you happen to have or know where/how I can get the stock build.prop?