Related
Hello,
i downloaded the mr2 http://forum.xda-developers.com/showthread.php?t=1160346&highlight=ota+mr2 i downloaded and installed, after verifying the md5, i dropped the file onto the root sd card and then i rebooted with hboot, which i believe is when the phone is off and i power it on holing down the power and down volume buttons, after the radio was installed i got no signal, how can i fix this problem?
You're unrooted on stock?
mattsonhistb said:
You're unrooted on stock?
Click to expand...
Click to collapse
I'm rooted, rooted with a guide here on xda forums and it was a successful root and i had signal, now i wanted to get bamf and i need mr2, after i installed the radio i had no signal at all
You need a ROM that's compatible with that radio.
Sent from my ADR6400L using XDA Premium App
setexascustoms said:
You need a ROM that's compatible with that radio.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
i got signal now, i went ahead and installed bamf along with the radio, which gave me no signal, the reasoning was because i saw another thread about someone was asking if they should install the radio first, or the ROM first, then later they said they got it to work....well MINES WORKS NOW!!!
Well i had BAMF and it was working fine and all, then it just froze...ok i just rebooted and it was fine, and again it froze and i had to remove batter. So i decided to go back to when i originally rooted the phone, which has the mr2 radio, and since it is what causes me to have no signal. How do i remove the mr2? me taking a wild guess, would i need to flash PG05IMG_mr1_upgrade? http://forum.xda-developers.com/showthread.php?t=996616
problem is fixed now, i went ahead and flashed PG05IMG_mr1_upgrade from the link and it works fine now, for some reason mr2 does not allow me to get signal at all
Quick question. I couldn't find the answer searching. I am upgrading from bamf 1.6.3 to 1.8.6 and will also be upgrading to the mr2 radio. Should I flash the Rom and then the radio? Or vice versa? Thanks.
Flash the ROM first. You won't have service. Then flash the radio from bootloader.
Really, though, it doesn't matter. The thing to avoid is getting into a bootloop where the ROM won't boot completely, but the radio is still named pg05img.zip on the root of your sdcard, so you can't get into recovery and fix the ROM.
As far as I'm aware, the only side effect of having a mismatched radio/ROM combo is that you'll have no service. Can someone verify this?
Ok Thanks guys. I have everything downloaded currently and on the root of my sd card. So going to flash the rom, then rename radio file, and flash the radio.
Ok, I flashed rom then radio and everything looked good. I did a restart after restoring everything with titanium backup and now its stuck on the Thunderbolt screen. What should I do? It's been like this for 15 minutes.
coder_t2 said:
Ok, I flashed rom then radio and everything looked good. I did a restart after restoring everything with titanium backup and now its stuck on the Thunderbolt screen. What should I do? It's been like this for 15 minutes.
Click to expand...
Click to collapse
If everything went well before TB, reflash, and don't restore any system apps. Some suggest not using TB to restore data either. Makeva nandroid before restoring anything.
Sent from my ADR6400L using XDA Premium App
Did you restore system data too? sometimes that can bugger things up. I usually only restore system settings that are in green, if any.
You can always just wipe and reflash the rom.
Ok. I just pulled out the battery and rebooted and all was fine. I did restore system settings that were in green. So I guess that may have been it.
Sent from my ADR6400L using XDA App
I would like to add that's the H BOOT not CWM. I know its common sense for some but Ive seen this cause issues in some of the other threads.
After sometime my cell phone is rebooting all times.
If it goes idle and I press the button to wake it, it reboots.
I've used some custom roms including CM7.
After I restored to my original firmware which is Claro Brazil, it keeps rebooting all time .
Anyone know what can I do? I even sent it to motorola and they don't do a thing. All they say is that it don't have any defect .
Thank you
Jayson
Did it start rebooting after you after you restored to the original firmware,
or did you restore to the original firmware to try to fix the reboots?:
blingmaster said:
Did it start rebooting after you after you restored to the original firmware,
or did you restore to the original firmware to try to fix the reboots?:
Click to expand...
Click to collapse
I restored to original to try to fix and it keeps rebooting.
I've flashed that build of ICS of dev thread and it seems to be rebooting less times.
How did you flash the rom?
Are you using romracers recovery?
Did you do a full wipe before flashing the rom?
You might make sure you have romracers latest recovery,
and then run this script for a full wipe:
http://forum.xda-developers.com/showthread.php?t=1421261&highlight=moto-fastboot+script
and then load a new rom and see if that fixes it.
You can also flash the Kernel and the radio too.
blingmaster said:
How did you flash the rom?
Are you using romracers recovery?
Did you do a full wipe before flashing the rom?
You might make sure you have romracers latest recovery,
and then run this script for a full wipe:
http://forum.xda-developers.com/showthread.php?t=1421261&highlight=moto-fastboot+script
and then load a new rom and see if that fixes it.
You can also flash the Kernel and the radio too.
Click to expand...
Click to collapse
First I installed IHOP_Bell.sbf with sbf_flash to be able to unlock with moto-fastboot. After that did install CWM.
All my roms are installed with CWM with its cache/data and stuff wipe.
How can I know the right kernel and radio for me?
Same for me. I think this is a radio issue, where can we find lastest radio? Do we need to flash it like rom via RR CWM?
Thanks.
I get random reboots all the time. I was thinking it was a problem with wireless or bluetooth... Last time it rebooted was this morning, I docked it before going to bed, and 5 minutes later i hear the double-ding of it mounting internal storage at boot. At the time it wasn't running anything but the dock-widget clock.
I've had it reboot while on the bus listening to music with the phone in my pocket, I've had it reboot while docked and sitting idle, but youtube and flash are the real killers while actually using the phone, for me at least.
I find it reboots less if I leave wireless and bluetooth off, but what is the good in that?
I've had the random reboots probably since I upgraded to gingerbread, but even moreso after Bell 2.3.6 OTA.
I wonder if there is a way to prevent it from rebooting, so we can see what actually causes it to spontaneously reboot.
Im getting random reboots too, but figured it was from the build of CM7 i'm running (23-Nov. Was thinking of doing a full wipe then reload sometime this week. will report my results.
Hi!
Same thing happened to me. What I did was, I flashed to a different radio for it to be fixed. The stock doesn't seem to work on mine and I can't have signal reception.
Sent from my MB860 using XDA App
I'm also getting reboots when I'm not on wifi.... Sometimes takes 15 mins once I'm not on wifi using 2.3.6 bell with latest radio.
Sent from my MB860
try wipeing data cache and dalvic with fastboot then flash a rom
thats the "cleanest way to install
ltdanno360 said:
try wipeing data cache and dalvic with fastboot then flash a rom
thats the "cleanest way to install
Click to expand...
Click to collapse
I've already did it without success.
Now I'm trying this new Radio:
http://forum.xda-developers.com/showthread.php?t=1175750
N_01.100.00R
because I'm pretty sure it is a Radio issue.
I previously had N_01.95.00R wich seems to be an Asian Radio that probably (hopefully) doesn't work properly here.
I will tell you if it will fix the problem.
Hi there,
I also have random reboots on my Atrix.
Till now, I tried to change rom, recovery, reset data factory, use no apps, etc. But it never worked, and the reboots are still happening without any logical explanation.
I'm also thinking about a Radio problem, mine is : N_01.100.00R
I'll try changing it this evening, maybe it will fix things.
I'm trying a new radio too.
It didn't reboot yet.
jaysonsantos said:
I'm trying a new radio too.
It didn't reboot yet.
Click to expand...
Click to collapse
Which one? Please, tell us!
Just had my second reboot in 5 minutes with N_01.100.00R...
Basically, it happens only in 3G and never in 2G, so I really think this is a radio issue, but I can't find alternatives...
-Fra- said:
Which one? Please, tell us!
Just had my second reboot in 5 minutes with N_01.100.00R...
Click to expand...
Click to collapse
Mine is a brazilian version, I'm using N_01.31.00R.
Maybe you should try Bell GB Version which is in dev forum.
jaysonsantos said:
Mine is a brazilian version, I'm using N_01.31.00R.
Maybe you should try Bell GB Version which is in dev forum.
Click to expand...
Click to collapse
Thank you!
Now I'm trying with N_01.07.05P...
Have you check your battery contact?
Sent from my HTC Hero using XDA App
Mine atrix also reboots, but it has stock 2.3.4. Suggestions?
Sent from my HTC Tattoo using Tapatalk
roflestomp said:
/thread
change radio to N_01.77.36P.
I bet most you're reboots are withing 1 minute of loosing data connection over 3g/4g. Use this radio and I haven't have had one reboot with both blur based roms and currently cm7.
Click to expand...
Click to collapse
Do you have any link to this radio?
Now with N_01.07.05P I had 2h and 16 min. without reboots, but if it will fail again I will try your one!
Thank you.
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!