Hi Guys...
My nexus 4 Stocked on logo last friday, I try to recovery, wipe cache, and nothing.
So I learn that some devices of Nexus 4 after update to 4.4 are having this problem.
By the way I try to flashtool on a 4.3 version, the system was installed, but I am still stocked on logo...
Anyone have any Idea, how I can fix this?
I have no access to adb, only by flashtool
here are the way that I installed the old stock version:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader D:\Nexus\SDK\android-sdk-windows\platform-tools\bootloader-mako-makoz20i.img
fastboot reboot botloader
fastboot flash radio D:\Nexus\SDK\android-sdk-windows\platform-tools\radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot bootloader
fastboot -w update D:\Nexus\SDK\android-sdk-windows\platform-tools\image-occam-jwr66y.zip
Thanks btw
Have you done a factory reset in the stock recovery?
Sent from my Nexus 5 using XDA Free mobile app
I tried to wipe cache and delete all user data, but nothing works.
I read on net that I have to be pressing the volume(-) button on google animation to make a factory reset, this never worked for me....
I was thinking in install a custom firmware to try to fix this...
Do I have to hcange the bootloader, or a stock bootloader will be enough...
for example I wanna try this:
[ROM] NEXUS 5 PORT 4.4.2 KOT49H odexed 10/12/2013
http://forum.xda-developers.com/nexus-4/development/rom-nexus-5-port-4-4-2-kot49h-odexed-10-t2507021
But the problem that as my nexus are not working I have no access to adb commands, so how I can fix that?
Just by now i was able to sideload to flash my phone
So I tried a old 4.2.2 google version.
But I have a failure:
" Signature verification failed"
Why this failure happens if I am using a oficial stock from google?
Dark_Hyoga said:
Just by now i was able to sideload to flash my phone
So I tried a old 4.2.2 google version.
But I have a failure:
" Signature verification failed"
Why this failure happens if I am using a oficial stock from google?
Click to expand...
Click to collapse
Are you trying to flash a rom in the stock recovery? It won't work, you need a custom recovery. You can try to install a custom recovery by flashing an image file in fastboot. Or you can flash the factory image in fastboot and start all over. I'm not sure what stage your device is on right now
Sent from my Nexus 5 using XDA Free mobile app
I installed the most old version 4.2.2 of stock version by flash mode, I dont know why, but on versions 4.3 and 4.4 the precess always stops on some part of the flastool.. thats why I try the sideload.
4.2.2 was ok,
now I finally get over the stuck logo and can access the phone, but the phone its nothing find the network, But I am still working on it.
Now I understand Why......
I lost my IMEi on the process
*#06# shows no IMEI...
Now I have to find a tool to burn the IMEI again...
Anyone knows some, I just find the OCtoplus, but I have to buy....
There is one free?
Related
Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help
So a week ago I flashed 4.4KK with fastboot no problem, restored TWRP, root and went on my merry way. Last night I decided to flash 4.4.2 and it all went pete tong. I went into fastboot and flashed 4.4 boot.img to restore stock kernel (I was on franco) and rebooted the phone to see if I could now update OTA. On reboot I got nothing but black screen but no worries and went back into fastboot to do a flash-all.sh. It went ok up to flash bootloader and I get the error
'writing bootloader...
FAILED (remote: invalid bootloader image)
archive does not contain boot.sig
recovery.sig
system.sig
Checking product: FAILED'
I then tried opening the zip and flashing each component seperately and can flash system, recovery, boot and userdata no problem.
It also will sideload to 100% fine but then just says failed. The problem seems to be with the bootloader-grouper-4.23.img?
No matter what I try it will have a black screen if I try to boot, though I can flash TWRP and go into that and if I reboot from there it says no OS loaded?
Can someone get me out of this mess, I really need my phone working before tomorrow!
Did you ever figure this out? Having the same issue...
carpel21 said:
So a week ago I flashed 4.4KK with fastboot no problem, restored TWRP, root and went on my merry way. Last night I decided to flash 4.4.2 and it all went pete tong. I went into fastboot and flashed 4.4 boot.img to restore stock kernel (I was on franco) and rebooted the phone to see if I could now update OTA. On reboot I got nothing but black screen but no worries and went back into fastboot to do a flash-all.sh. It went ok up to flash bootloader and I get the error
'writing bootloader...
FAILED (remote: invalid bootloader image)
archive does not contain boot.sig
recovery.sig
system.sig
Checking product: FAILED'
I then tried opening the zip and flashing each component seperately and can flash system, recovery, boot and userdata no problem.
It also will sideload to 100% fine but then just says failed. The problem seems to be with the bootloader-grouper-4.23.img?
No matter what I try it will have a black screen if I try to boot, though I can flash TWRP and go into that and if I reboot from there it says no OS loaded?
Can someone get me out of this mess, I really need my phone working before tomorrow!
Click to expand...
Click to collapse
You need to flash factory images for OCCAM which is for the nexus 4. You had downloaded wrong factory images, grouper, which are for the tablet Nexus 7 Jelly Bean version.
carpel21 said:
So a week ago I flashed 4.4KK with fastboot no problem, restored TWRP, root and went on my merry way. Last night I decided to flash 4.4.2 and it all went pete tong. I went into fastboot and flashed 4.4 boot.img to restore stock kernel (I was on franco) and rebooted the phone to see if I could now update OTA. On reboot I got nothing but black screen but no worries and went back into fastboot to do a flash-all.sh. It went ok up to flash bootloader and I get the error
'writing bootloader...
FAILED (remote: invalid bootloader image)
archive does not contain boot.sig
recovery.sig
system.sig
Checking product: FAILED'
I then tried opening the zip and flashing each component seperately and can flash system, recovery, boot and userdata no problem.
It also will sideload to 100% fine but then just says failed. The problem seems to be with the bootloader-grouper-4.23.img?
No matter what I try it will have a black screen if I try to boot, though I can flash TWRP and go into that and if I reboot from there it says no OS loaded?
Can someone get me out of this mess, I really need my phone working before tomorrow!
Click to expand...
Click to collapse
You can't update to the newest android if you are rooted...you need to restore back to stock android before updating..
Sent from my Nexus 4 using XDA Premium 4 mobile app
I suggest returning the phone to stock and starting over.
http://forum.xda-developers.com/showthread.php?t=2010312
taodan said:
You need to flash factory images for OCCAM which is for the nexus 4. You had downloaded wrong factory images, grouper, which are for the tablet Nexus 7 Jelly Bean version.
Click to expand...
Click to collapse
Please listen to this. If you continue in the wrong direction, you are only going to make things worse.
korockinout13 said:
Please listen to this. If you continue in the wrong direction, you are only going to make things worse.
Click to expand...
Click to collapse
Which information is wrong direction?
Hi
Please help! I unlocked the bootloader by using
fastboot unlock oem
after that I forgot to reboot and installed
fastboot flash recovery twrp.name.file
now I'm stocked at bootup and twrp is asking for password.
How can I fix this?
Could I flash the stock boot.img again?
ROM is stock OTA 4.4.2.
I know about flashing a factory image. I would like to find a way to save my data first, if possible.
Many thanks for your help!!!!!!!
C0qRouge said:
Hi
Please help! I unlocked the bootloader by using
fastboot unlock oem
after that I forgot to reboot and installed
fastboot flash recovery twrp.name.file
now I'm stocked at bootup and twrp is asking for password.
How can I fix this?
Could I flash the stock boot.img again?
ROM is stock OTA 4.4.2.
I know about flashing a factory image. I would like to find a way to save my data first, if possible.
Many thanks for your help!!!!!!!
Click to expand...
Click to collapse
Wipe cache from twrp, this is happened to me too But for the password i don't know...maybe reflash twrp, boot.img is the kernel so in my opinion flashing it wouldn't help you
Did you flash straight from 4.2.2 to after installing twrp? I did the same thing. I had to flash back to stock 4.2.2, install twrp, connect the phone to my computer, choose accept at RSA message, and fastboot flash to 4.4.2.
C0qRouge said:
Hi
Please help! I unlocked the bootloader by using
fastboot unlock oem
after that I forgot to reboot and installed
fastboot flash recovery twrp.name.file
now I'm stocked at bootup and twrp is asking for password.
How can I fix this?
Could I flash the stock boot.img again?
ROM is stock OTA 4.4.2.
I know about flashing a factory image. I would like to find a way to save my data first, if possible.
Many thanks for your help!!!!!!!
Click to expand...
Click to collapse
boot into bootloader and type :fastboot format data press enter and then : fastboot reboot .
it should boot now
Thanks
Sent from my Nexus 4 using xda app-developers app
Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L