Database Users

[Q] Nexus 4 boots with 4.2.2 (JDQ39 but no radio) but no new ROM, including stock

I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????

contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
doing a system wipe (factory reset) when you update from 4.2 tp 4.3..? also just reminding you 4.3 based roms need new radio and bootloader update.. but that radio also works with 4.2..

Same problem
contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4

Antonio0 said:
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4
Click to expand...
Click to collapse
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?

i dont think i have a solution
smoka206 said:
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?
Click to expand...
Click to collapse
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device

Antonio0 said:
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device
Click to expand...
Click to collapse
i have the same problem too.. can someone help please??

try this http://forum.xda-developers.com/showthread.php?t=2347060
http://forum.xda-developers.com/showthread.php?t=2453364

Slimbean 4.2.2 Build - media issues

Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance

Update: Any ROM I install... Phone and sounds do not work.

Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.

jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.

Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP

[Q] Very curious Problem. My Nexus4 only works with Stock 4.2.0

I borrowed my Nexus4 to my sis for a couple of days. When I set it up for her (after Factory resetting it from the Settings Menu) everything was working fine. Now that she gave me the phone back it was stuck in the boot screen. I also realized that she forgot to give me the SIM Card Holder back which is now in her wallet. She told me that the guys at the mobile phone operator removed her SIM Card without turning the phone off.
I tried flashing Stock Android Firmware a couple of times. I tried it with 4.3.0 and 4.4.0. It always got stuck in the Boot Animation. The only Firmware that boots up to Android is 4.2.0. Even when i do a regular OTA update to 4.3.0 it gets stuck in the Boot Animation.
Is it possible that the Nexus4 is not booting up without a inserted SIM card. I know this sounds stupid, but it is the only explaination i have.
Did someone else experience the same issues?
Update1
I found out, that it's also booting up from 4.2.1. then i got a regular 4.2.2 OTA update which worked too. now was stuck with "Starting apps" after upgrading to 4.3 via ODA Update. Restarting the phone got me stuck in the Boot Animation again. I think I'm gonna wait until i can test it with a Sim Card.

The Sim card has nothing to do with whether the phone boots up or not. You need to wipe the phone clean and flash the factory images. Report back after.
Sent from my Nexus 4 using Tapatalk

ragerino said:
I borrowed my Nexus4 to my sis for a couple of days. When I set it up for her (after Factory resetting it from the Settings Menu) everything was working fine. Now that she gave me the phone back it was stuck in the boot screen. I also realized that she forgot to give me the SIM Card Holder back which is now in her wallet. She told me that the guys at the mobile phone operator removed her SIM Card without turning the phone off.
I tried flashing Stock Android Firmware a couple of times. I tried it with 4.3.0 and 4.4.0. It always got stuck in the Boot Animation. The only Firmware that boots up to Android is 4.2.0. Even when i do a regular OTA update to 4.3.0 it gets stuck in the Boot Animation.
Is it possible that the Nexus4 is not booting up without a inserted SIM card. I know this sounds stupid, but it is the only explaination i have.
Did someone else experience the same issues?
Update1
I found out, that it's also booting up from 4.2.1. then i got a regular 4.2.2 OTA update which worked too. now was stuck with "Starting apps" after upgrading to 4.3 via ODA Update. Restarting the phone got me stuck in the Boot Animation again. I think I'm gonna wait until i can test it with a Sim Card.
Click to expand...
Click to collapse
Hey, I met the same problem, have you solved it? could you tell me how to solve that? that drive me crazy.

I have read some posts that anything newer than 4.2.2 won't boot if the imei is not being displayed properly by dialing *#06#.

Same issue
Hi
How did you resolve this as I am having the same issue and nothing is working? thanks

tpc74 said:
Hi
How did you resolve this as I am having the same issue and nothing is working? thanks
Click to expand...
Click to collapse
See if your IMEI and your baseband is getting displayed. Otherwise you might have to flash the baseband of your android version.

i have the same problem, i just dont know what to do, i tried the cyanogenmod, 4.4.0 , 4.4.2 , 4.4.4 and i just tried 5.0 and nothing works, just 4.2 , and i have no problems with the baseband :crying:

__bump

any solution? I have the same problem

Y not root it and use a custom rom...Chroma 6.0 Marshmallow rom is one of the best out there...any specific reasons for sticking with stock rom??
Sent from my Nexus 4 using Tapatalk

When I had this a flash a new modem radio and I was fine...

I had a similar issue as you. Could not get past 4.2 version. Although I could get up to 4.3 by flashing an older modem radio after flashing the stock 4.3 image.
My issue was a broken proximity sensor. Any other version past 4.2 would not get past boot animation because the proximity sensor was not working (properly). I did a RMA and they changed the proximity sensor. After that, I could update all the way to 4.4 without issue. Still working today!
It's just a suggestion, but could you check if your proximity sensor is working on the 4.2 build? https://play.google.com/store/apps/details?id=ctsr.android.SensorTest&hl=en can help.
Or you could let someone call you and see if the screens turns off when you put the phone up to your ear and lights up again when you put it away from your ear.

[Q] Strange issue: Nexus 4 bootloops with all 4.3/4.4 builds. Sort of fine on 4.2

Nexus 4 completely stock (never rooted, never unlocked running stock 4.4.2) suddenly refused to boot up and got stuck at 4 spinning circles one fine day when I tried to reboot it (coz changing SIMs).
Factory reset, cache/data wipe did not work. So unlocked bootloader to be able to flash factory images and no build/version of 4.3 or 4.4 worked. 4.2 works but boot time is an abnormal 100+ seconds, but otherwise is fine. If however I update from 4.2 to 4.3, it goes back to bootlooping.
Its almost as if the phone is now suddenly incompatible with 4.3 and 4.4.
I read all relevant threads online on XDA and elsewhere and this doesn't seem like those issues. The sensors are all functioning and there are no loose cables since I used a sensor app and all sensors are giving readings (including proximity). Also tried to downgrade radio version from .84 (of 4.3 and above) to .48 (of 4.2) to see if it makes it work it did not. Then I tried upgrading the radio of a working 4.2 install from .48 to .84 and that din't break it. So radio version is not the issue here either.
Completely flummoxed..

*bump*

Back to stock rom, hanging when placing call, no sound etc.

Hi there
I have recently picked up my old S4 since my OPO screen broke. I was annoyed with the buggy CM 12 nightly it was running and tried installing the newest CM 13 nightly. It gave me no signal and I decided to try to revert to stock, following the guide Unroot/Unbrick, Flash official stock firmware on S4. Applying the I9505XXUAMDE_I9505OXXAMD8_NEE 4.2.2 stock rom through ODIN was a breeze but after booting i realized it had no sound.
Also placing or receiving calls makes the phone hang, even occasionally reboot, and sometimes a window with "android.phone.. app" or "process system is not answering" appears. For example also not possible to record video.
I did both factory reset and wipe cache in bootloader, but when wiping cache I get the lying down android with red exclamation mark for a few seconds then reboot.
I then tried to reflash above stock rom with repartition (pit file) and the problem remains.
I dont suppose it is a hardware problem since it started after I flashed new rom. It seems like some audio related software issue that I cant seem to get rid of - can anyone help or should I just give up and get another phone?
Thanks in advance, sorry for the long post

Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?

Pwnycorn said:
Try flashing a newer ROM.
The guide used is pretty old I guess and should be used only as reference.
What was the initial stock ROM your device had?
Click to expand...
Click to collapse
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?

fiedes said:
I already tried rerooting and flashing back to both CM 10.2 and newest CM 13 nightly from philz touch recovery. Both with the same problem when placing or receiving a call. But sound was working..
I don't know the exact stock rom the phone came with but seem to recall it was 4.2.2 as I have installed now.
Is there anything else that can be flashed back to original? I read several posts talking about a modem reflash for fixing audio issues but I suppose the stock rom should contain the modem info already..?
I specifically went for the oldest rom, since the guide said that once stock 4.3 is flashed you cant revert due to new bootloader. And I was hoping to revert to being able to use OTA updates since I plan on gifting the phone to an even more tech illiterate than myself.. Is that going to be a problem if I just flash for example the newest 5.0.1 stock rom?
Click to expand...
Click to collapse
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.

Pwnycorn said:
Downgrading causes problems in the first place, that is why it is recommended to flash the same software as it originally had.
As long as your status says "official" in download mode, you should be able to still get updates. Although who knows for how long.
I also recommend using the latest TWRP recovery. PhilZ and CWM are outdated and can cause problems with newer ROMs.
Click to expand...
Click to collapse
I will try to install TWRP and the newest stock firmware and see what happens. Thanks

Ok, upgraded to latest stock rom and everything works!
No idea what was wrong specifically though.. Thanks for the help!