Had a weird problem this morning, I'll give you a quick rundown 1st.
nexus 7 32 gb unit, rooted on 4.1.2, got the ota update to 4.2 kept root
no problem. Got the ota for 4.2.1 again kept root with no problem.
Been running a few days with no problems.
This morning when I woke it got the message google process gapps force close.
rebooted it and the same thing. had an update from the play store but couldn't get in
would just flicker for a sec. every time I hit the play store button.
Had a backup of 4.2 I made just before the update, tried to get into recovery and just
got the android on his back with the red triangle. re-flashed recovery (twrp) flashed my
4.2 backup now everything is fine. Sorry about the long post, just trying to find out why I
lost my gapps and recovery for no reason, didn't change anything or upgrade anything.
Just running stock rooted.
I have the system update for 4.2.1 but I'm not sure if I should update it.
Again, sorry for the long post, just looking for some feedback.
Thanks
Hi,
I have an unrooted, stock Nexus 4. I received the 4.3 update and installed it... but now I keep getting "System update downloaded".
I've tried letting it install a couple of times now but it keeps happening.
I am actually running 4.3. Build number is JWR66V.
Any ideas?
Thanks
So I finally got the 4.3 update. My phone was all ready to install the update so I tapped update and install and started to reboot and install like normal. As it was installed in the stock recovery, all of the sudden it displays the message "error!". Then it reboots back into the same version of android and a few days later, it says it need to update to 4.3 and the cycle starts again. Any one know what is going on? Thanks
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
My nexus 4 was rooted a while back before I got the OTA 4.3 android update via system update. Everything went fine then with that download. I was a bit anxious to get the 4.4 kit kat release and having seen it appear in system update 2 days ago I decided I was gonna download it yesterday and I did. After it finished the phone restarted and then was stuck in an infinite loop. I had no backup and so I decided to wipe; after which I had no operating system. I downloaded the
factory rom image of 4.4 (stock_mako_KRT16S.zip),
radio (cwm-radio-mako-m9615a-cefwmazm-2.0.1700.97.zip)
and bootloader (KK_4-4_BOOTLOADER.zip)
I flashed the radio first then then bootloader and both fine, then when it was turn for the factory rom it said error extracting file.. the dreaded status 7 error.
Anyways, I figured since it wasn't working I'd just go for a custom rom and I had rasbeanjelly on my phone from back when I rooted but never got around to flashing. So I thought I would try it and it flashed along with the gapps 4.3 but I've had several huge glitches such as the phone moving slowly and missing important google apps such as camera and such.
So I was up all night trying to figure out how to go back to stock rom and do a recovery and everything I tried was no luck. Kept running into the status 7 error. Watched a few videos that suggested I get Wug's Nexus Root Toolkit to unroot and then lock my bootloader and then flash a stock recovery. It didn't work because I realised one severe difference.
MY NEXUS 4 HAS A NEXUS 7 BUILD NUMBER.. I googled the internet and nothing..
Anyways. Says android 4.3
Build: JSS15Q
rasbeanjelly build: fri aug 23 2013 (probably old)
I just wanna know how I can get back to stock.
And I lost my root privileges as well when I flashed rasbean.
Any other information can be provided. THANKS MUCH.