Hi Everyone,
I am currently running android 4.3(JWR66v) I flashed it using fastboot, so it is clean.
After that I rooted it and installed CWM v6.3.6 and BusyBox pro.
That is the only changes I did to my device,everything else is stock.
2 day ago I got a system update notification, looking in the cache folder I found this :
"8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip"
I confirmed the reboot/Install but it failed with the classic (Status 7) I do not understand what is going on ?
Do I need flash my device again with a factory to get the update to install ?
I had the same setup since I bough this device last year and It had no trouble what so ever upgrading before(Unlocked+rooted+CWM)
This is supposed to be a nexus device but it sure doesn't act like one,
Can some one please help ?
Had the same problem going from 4.2.2 to 4.3. Same as you, stock rooted, but had TWRP as my recovery. I did go back to stock recovery, but no go. Ended up doing clean install. However, going from JWR66V to JWR66Y, I had no problem. Took OTA without even having to install stock recovery.
You must not be as stock as you think. My guess is you must have altered something in system that they are checking on. Hope someone with more knowledge is able to help you out because it is a PITA to have to clean install for every update. Good luck.
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
About a month ago I tried to update to Kit Kat OTA and my 2012 Nexus 7 seemed to update, but then got stuck in the new Google boot image with swirling circles.
I know I've been OTA updating every time it asked since I got it. I don't know which version or image is currently on there. I can't get past the swirling circles.
I know I have CM on there, but otherwise no mods, and other than a program (whose name I can't remember) that keeps root after an update, nothing else strange.
I tried using something called Nexus Root Toolkit as per a user in another forum, but that didn't go anywhere because after I installed the drivers, it says I don't have ADB or whatever. I have no idea what to do.
I never should have installed CM or rooted. So stupid
If anyone can help me get my Nexus 7 working again, it'd be greatly appreciated!!!!!!!!
So today my nexus 4 shut off at around 20 percent batter i didn't really think any of it because that happens often and i just reboot and its back on after charging it. This time however it was different it wouldn't boot it was just stuck on the paranoid android boot animation. I searched online and found out that clearing cache and data all that works so i tried it to no avail. I did the same this again but this time re flashed the rom and still nothing. I then pushed cm 11 into the nexus 4 flashed that rom and nothing. So then the last thing i though about was fully unrooting and going back stock with nexus root toolkit. I tried it and went through but then when good ol kitkat animation started it continued forever. Im out of options now and i don't even have custom recovery anymore what can i do.
I was running Paranoid Android build version 4.45 with hells core kernel.
EDIT---------------------------------------------------
I have clockwork mod recovery back up were do i go from here please help.
Please Help Thanks
skype:ApexDreamZ
So I've had my nexus 7 2013 (wifi) for a while and before Lollipop came out on the ota update I decided to flash it myself because I was a bit inpatient. Since then I've been flashing the images on my own, but I still get a message on the table about an update, but I can not update it through the tablet itself anymore even when I have the factory recovery and everything else is flash backed to stock. I would like to know if there is a solution to this problem as flashing everything back to stock has not worked. Thank you.