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.
Related
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!
Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.
i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.
Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.
gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.
Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.
If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.
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
I had used cm 10.1 for a year and one day I decided to flash slimbean 4.3 weekly 1.4. So I downloaded bootloader Z20i.zip and radio .84.zip and flashed via TWRP 2.6.3.0 and then wiped everything, flashed rom then gapps. I used the original kernel of rom. Everything seem to be fine and flawless. but one day my phone hanged and rebooted itself stucked at bootanimation. I tried to restart many times and it didnt success. So I decided to download factory image JWR66Y from google and run flash-all.bat via fastboot mode and then flash superSU via TWRP. Yeah..bootloop was gone. I used stock JWR66Y rom and kernel with root for a while and it happened again. One day my phone hanged and rebooted itself stucked at X animation. I tried to Wipe cache, davik, factory reset but it didnot success. So I tried to install cm10.2, PA3.99 (I have had installation zip file in my phone storage.) but it didnot sucess too. So I decided to flash stock Stock 4.2.2 JDQ39 image from google. thanks God my phone resurrected. But I dont want 4.2.2 anymore. I decide to try again with 4.3 stock JWR66Y. It happened bootloop same as above I described again. I have no idea anymore but I tried flash radio.48 via fastboot and finally my phone can use normally. Bootloop was gone away. Now I use Slimbean 4.3 weekly 1.6 original kernel with bootloader z20i and radio .48 without any bootloop.
So I think the problem for me is why radio .84 make my phone got bootloop.
Sent from my Nexus 4 using xda app-developers app
quirell said:
I had used cm 10.1 for a year and one day I decided to flash slimbean 4.3 weekly 1.4. So I downloaded bootloader Z20i.zip and radio .84.zip and flashed via TWRP 2.6.3.0 and then wiped everything, flashed rom then gapps. I used the original kernel of rom. Everything seem to be fine and flawless. but one day my phone hanged and rebooted itself stucked at bootanimation. I tried to restart many times and it didnt success. So I decided to download factory image JWR66Y from google and run flash-all.bat via fastboot mode and then flash superSU via TWRP. Yeah..bootloop was gone. I used stock JWR66Y rom and kernel with root for a while and it happened again. One day my phone hanged and rebooted itself stucked at X animation. I tried to Wipe cache, davik, factory reset but it didnot success. So I tried to install cm10.2, PA3.99 (I have had installation zip file in my phone storage.) but it didnot sucess too. So I decided to flash stock Stock 4.2.2 JDQ39 image from google. thanks God my phone resurrected. But I dont want 4.2.2 anymore. I decide to try again with 4.3 stock JWR66Y. It happened bootloop same as above I described again. I have no idea anymore but I tried flash radio.48 via fastboot and finally my phone can use normally. Bootloop was gone away. Now I use Slimbean 4.3 weekly 1.6 original kernel with bootloader z20i and radio .48 without any bootloop.
So I think the problem for me is why radio .84 make my phone got bootloop.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have the same exact problem! :crying:
Cannot update beyond 4.2.2. I have tried all the things that you seem to have tried but with absolutely no luck. And since there aren't many people with this problem, nobody has come up with a solution. It is extremely frustrating to see everyone else updating to to the latest firmware while we have to make do with the ancient 4.2.2
If anybody can think of anything which might help, please go ahead and share.(Cannot return the phone back to Google as I got it from another country)
Rekursion said:
I have the same exact problem! :crying:
Cannot update beyond 4.2.2. I have tried all the things that you seem to have tried but with absolutely no luck. And since there aren't many people with this problem, nobody has come up with a solution. It is extremely frustrating to see everyone else updating to to the latest firmware while we have to make do with the ancient 4.2.2
If anybody can think of anything which might help, please go ahead and share.(Cannot return the phone back to Google as I got it from another country)
Click to expand...
Click to collapse
Hi,
I just fixed a Nexus 4 with broken screen and fastboot flashed the latest 4.4.2 official ROM but I was stuck in bootloop on the 4 circles.
Then I flashed the 4.2.2 version and everything worked until I accepted the the 4.3 update (official OTA) and the phone was bootlooping again.
Then I found your posts and downgraded the radio .84 to .48 and android 4.3 finally booted successfully.
BUT, when trying to upgrade to 4.4 (from 4.3 with official OTA), I'm stuck again! And downgrading radio .97 to .48 does not work anymore...
I've found nothing like a software fix until now. People facing the same issues are mostly getting some replacement devices. Given that I replaced the screen myself, I'm not certain that they would give me a new one.
Any feedback from someone having the same issue?
neoantho said:
Hi,
I just fixed a Nexus 4 with broken screen and fastboot flashed the latest 4.4.2 official ROM but I was stuck in bootloop on the 4 circles.
Then I flashed the 4.2.2 version and everything worked until I accepted the the 4.3 update (official OTA) and the phone was bootlooping again.
Then I found your posts and downgraded the radio .84 to .48 and android 4.3 finally booted successfully.
BUT, when trying to upgrade to 4.4 (from 4.3 with official OTA), I'm stuck again! And downgrading radio .97 to .48 does not work anymore...
I've found nothing like a software fix until now. People facing the same issues are mostly getting some replacement devices. Given that I replaced the screen myself, I'm not certain that they would give me a new one.
Any feedback from someone having the same issue?
Click to expand...
Click to collapse
Yes.., I am joining your club. I have a same problem. I flashed 4.4 & 4.4.2 .., almost all sources and ended with four circle boot loop. Then flashed 4.2.2 and it was success. Did you people managed to flash Kit Kat ? Please anyone help us.
Please try these links...dont know whether it helps...I sold my phone., cant try..
http://forum.xda-developers.com/showthread.php?t=2529450
http://forum.xda-developers.com/showthread.php?t=2347060
Hope it helps someone.
richie16171 said:
Yes.., I am joining your club. I have a same problem. I flashed 4.4 & 4.4.2 .., almost all sources and ended with four circle boot loop. Then flashed 4.2.2 and it was success. Did you people managed to flash Kit Kat ? Please anyone help us.
Click to expand...
Click to collapse
richie16171 said:
Please try these links...dont know whether it helps...I sold my phone., cant try..
http://forum.xda-developers.com/showthread.php?t=2529450
http://forum.xda-developers.com/showthread.php?t=2347060
Hope it helps someone.
Click to expand...
Click to collapse
Hi, yes I finally found out that my proximity sensor was only disconnected (I forgot to reconnect it properly after the screen replacement). Then I managed to update my phone.
Found answers on this thread : http://forum.xda-developers.com/showpost.php?p=49141665&postcount=75
Sorry that you had to sell it...
neoantho said:
Hi, yes I finally found out that my proximity sensor was only disconnected (I forgot to reconnect it properly after the screen replacement). Then I managed to update my phone.
Found answers on this thread : http://forum.xda-developers.com/showpost.php?p=49141665&postcount=75
Sorry that you had to sell it...
Click to expand...
Click to collapse
You mean to say.,,you could flash 4.3 and your only problem to update kit kat.., because of the proximity sensor?
richie16171 said:
You mean to say.,,you could flash 4.3 and your only problem to update kit kat.., because of the proximity sensor?
Click to expand...
Click to collapse
Well, I meant I could get 4.3 to work after downgrading the radio file (baseband) to its previous version, otherwise I was stuck in bootloop in 4.3 already.
But I couldn't do the same operation after flashing 4.4 : even downgrading the radio to a previous version didn't get 4.4 to work.
Once I reconnected the proximity sensor, I could use any radio and was able to update from 4.2 to 4.3 and 4.4 or directly flashing the latest.
You can use the Androsensors app to see if your light and proximity sensors are working properly, the displayed values should change all the time. If they are not changing or if there is no value displayed, it means that your sensors are not working properly
I recently had some issues with my GPS so I used Odin to go back to stock firmware, everything was still ok after this and my GPS was back to working order. Then I used CF auto root to root my device again/use TWRP recovery. Then I flashed the latest PAC nightly and gapps with seemingly no problems. The phone worked fine for 2-3 days until one day when it was in my pocket I got a warning saying something along the likes of "SIM card has been removed. Reboot required." Rebooting would make the sim come back online momentarily until it would randomly come back up. There didn't seem to be any correlation with any new apps I had installed or things I did on my phone to cause this error. I thought perhaps it was the ROM so I tried reflashing (complete with factory wipe) and the problem still happened. I also tried wiping factory->system->cache&dalvik before reflashing..again it worked but only briefly. I tried going back to stock but it still happens. Right now I'm running task650s aokp and it still comes up..the sim works in other phones no problem. Any ideas on what might be going on/how to fix this issue?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Hello,
I appreciate there are a huge number of similar questions on this forum, but I have read a lot of them and cannot find a solution to the problem I have with my wife's Nexus 4. Hoping someone will be able to help...
Standard Nexus 4 8GB, running 4.3 OTA on Vodafone UK. Not rooted, unlocked, hacked or anything.
Yesterday it failed to make calls or pick up a network, so my wife shut it down and restarted it; since then it would not get past the X boot logo.
Tried the factory reset / cache wipe steps, many times to no avail.
Let the battery run down overnight, no change this morning.
Sideloaded the OTA from 4.3. to 4.4, accepted the code but would not boot, initially stuck at "Starting Apps" after optimising apps, then after reset stuck at 4.4 Circles logo.
Installed 4.4.2 via fastboot, after unlocked the bootloader, again installed OK but would not boot, as above.
Re-installed 4.3 via fastboot, as above, will not boot.
Now currently gone back to 4.4.2 factory image, still will not boot - sits on the circles boot logo for ever.
I am sure I have tried several different iterations to the above, the furthest I have got it "Starting Apps" screen, most common is X or Circles.
Anything else I can try before giving up?
Thanks in advance.
meepm33p said:
Hello,
I appreciate there are a huge number of similar questions on this forum, but I have read a lot of them and cannot find a solution to the problem I have with my wife's Nexus 4. Hoping someone will be able to help...
Standard Nexus 4 8GB, running 4.3 OTA on Vodafone UK. Not rooted, unlocked, hacked or anything.
Yesterday it failed to make calls or pick up a network, so my wife shut it down and restarted it; since then it would not get past the X boot logo.
Tried the factory reset / cache wipe steps, many times to no avail.
Let the battery run down overnight, no change this morning.
Sideloaded the OTA from 4.3. to 4.4, accepted the code but would not boot, initially stuck at "Starting Apps" after optimising apps, then after reset stuck at 4.4 Circles logo.
Installed 4.4.2 via fastboot, after unlocked the bootloader, again installed OK but would not boot, as above.
Re-installed 4.3 via fastboot, as above, will not boot.
Now currently gone back to 4.4.2 factory image, still will not boot - sits on the circles boot logo for ever.
I am sure I have tried several different iterations to the above, the furthest I have got it "Starting Apps" screen, most common is X or Circles.
Anything else I can try before giving up?
Thanks in advance.
Click to expand...
Click to collapse
Hmm heard of such issues in the past where nexus wont boot with 4.3 or 4.4 !! I dont know the exact reason of the problem but what I do know is a solution for the same !!
Download the Factory Image for 4.2 Jelly Bean and fastboot the same !! Mostly youll get back your phone in the working state albeit without being able to upgrade to 4.3 or 4.4 !! Have a good day ahead !! :good:
Hi,
Thanks for the reply - I have just reloaded 4.2.2 from scratch and it is working. I then tried the OTA 4.3 upgrade and it failed, as before "starting apps" for ever, reset never boots.
Returning to 4.2.2 worked again.
What is strange is that this handset worked with 4.3 for 3 or 4 weeks before the restart yesterday...
I also tried 4.3 with .48 radio but that still failed to boot.
Hopefully someone else has a clever idea or some information around how/why this occurs, as beyond there being an underlying hardware fault (all sensors seem with androsensor) it is not logical.
Thanks.