Related
Hey guys,
I've just tried updating my Nexus 7 to 4.1.2 OTA, after the download was installed it tried to reboot and it's just hanging on the Nexus logo boot screen. I've tried to boot in to recovery mode but I just get the little android with the red exclamation mark triangle.
My device is not rooted and was previously running completely stock firmware 4.1.1, never tweaked at all.
Any ideas would be very helpful - apologies if this is a glaringly obvious fix, I haven't searched much as I'm posting from my phone.
Many Thanks
I am having the same problem but mine is rooted. So I was probably thinking I was having the problem cos it's rooted.
Sent from my Nexus 7 using xda app-developers app
venturion said:
Hey guys,
I've just tried updating my Nexus 7 to 4.1.2 OTA, after the download was installed it tried to reboot and it's just hanging on the Nexus logo boot screen. I've tried to boot in to recovery mode but I just get the little android with the red exclamation mark triangle.
My device is not rooted and was previously running completely stock firmware 4.1.1, never tweaked at all.
Any ideas would be very helpful - apologies if this is a glaringly obvious fix, I haven't searched much as I'm posting from my phone.
Many Thanks
Click to expand...
Click to collapse
Do you have the 4.2.1 bootloader? or it might not work.
Don't think so, it's completely standard. Been updated from 4.1.0 to 4.1.1 when I bought it, since then only change to the firmware I've made is today downloading 4.1.2.
Did you do a manual update or was it system self prompted update?
I was notified that an update was available by my device. I pressed install now, it downloaded and the device rebooted and started installing it. Then it triedvto boot back up and failed.
if this happened and you did NOT root or unlock the bootloader, then you are eligible for a replacement. go to the store you have bought it from and ask for a replacement unit. if you did unlock the bootloader, then you have to boot into bootloader and use this tool and select 9 after installation. it should return your device to stock, providing you can still boot into bootloader. good luck!
Billchen0014 said:
if you did unlock the bootloader, then you have to boot into bootloader and use this tool and select 9 after installation. it should return your device to stock, providing you can still boot into bootloader. good luck!
Click to expand...
Click to collapse
I'm in this boat, unlocked bootloader, and had this porblem. What tool are we speaking of?
Billchen0014 said:
if this happened and you did NOT root or unlock the bootloader, then you are eligible for a replacement. go to the store you have bought it from and ask for a replacement unit. if you did unlock the bootloader, then you have to boot into bootloader and use this tool and select 9 after installation. it should return your device to stock, providing you can still boot into bootloader. good luck!
Click to expand...
Click to collapse
I was hoping that wouldn't be the case to be honest and that I'd be able to fix it myself, ah well. Thanks a lot for your help
Just so everyone knows, I took my tablet back and got a new one, which when updated broke again. I got a third tablet and contacted Google directly, they told me they can't really help but try updating again, which I did and bricked my 3rd device in a row. When I called Google again they said I need to speak to Asus (regarding this issue with Android software) in terms of getting another replacement. Which means I'll be left without a device until they replace it!
Wow, the same problem as I had.
My brand new, stock nexus 7 (4.1.1) informed me there was an update so I allowed it to install it.
It was connected to the PC during the whole process.
It installed the update, but got stuck on the boot screen (the X logo). It took too long so I suspected something went wrong...
In a few minutes I was forced to learn how to do a forced restart, enter the recovery menu, etc.
But sadly nothing helped, as it ALWAYS ended up showing that X logo and would not go further. So I decided for a drastic measure and wiped the device (reset to factory settings). Unsurprisingly, it then booted fine and the new update was there.
Of course I lost all my game saves and other data... Really pissed off, but decided to swallow it for the time being.
If this happens at the next update, I'll definitely say goodbye to the Nexus. Would be a shame though, as it's a lovely device, very handy.
Just for the record, I live in the EU and the device was bought in a brick and mortar shop, and it had 4.1.1 installed.
bangawasawa said:
Wow, the same problem as I had.
My brand new, stock nexus 7 (4.1.1) informed me there was an update so I allowed it to install it.
It was connected to the PC during the whole process.
It installed the update, but got stuck on the boot screen (the X logo). It took too long so I suspected something went wrong...
In a few minutes I was forced to learn how to do a forced restart, enter the recovery menu, etc.
But sadly nothing helped, as it ALWAYS ended up showing that X logo and would not go further. So I decided for a drastic measure and wiped the device (reset to factory settings). Unsurprisingly, it then booted fine and the new update was there.
Of course I lost all my game saves and other data... Really pissed off, but decided to swallow it for the time being.
If this happens at the next update, I'll definitely say goodbye to the Nexus. Would be a shame though, as it's a lovely device, very handy.
Just for the record, I live in the EU and the device was bought in a brick and mortar shop, and it had 4.1.1 installed.
Click to expand...
Click to collapse
Hi. Slightly off topic, but maybe worth mentioning : I have exactly the same problem with the 4.1.2 OTA update of the Nexus S.
What did you do, reset to factory settings?
Sent from my Nexus 7 using xda app-developers app
bangawasawa said:
What did you do, reset to factory settings?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, but I had some difficulties doing it, couldn't even tell you exactly how I managed to.
I'm really disappointed by this OTA update, it shouldn't be more complicated than flashing an alternative ROM.
Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
Hey,
So I received the Nexus 10 this morning, signed into my Google account, downloaded a few app updates, then it said the 4.2.2 update was ready. I let it install and reboot, but ever since touch is not working at all on the device. It boots fine, but it won't unlock as it doesn't register the touch.
I've used the Recovery menu to restore it to factory defaults, which it did, but touch still doesn't work (I can't change language etc). I've downloaded the official 4.2.2 ROM, the SDK, installed the USB drivers, but ADB Devices doesn't find it. I guess this is because I can't enable Debugging Mode.
Can anyone offer some advice? Yes, I could return the tablet to Google, but I head back to the Middle East in a few days and I should imagine the turn around time will be much longer than that.
I'm happy to install any custom kernel, recovery mode etc. to try and restore it. When booted, Windows Explorer will allow me access.
I've Googled as much as I can, but most things rely on being able to enable the ADB link.
Many thanks.
You dont need ADB to install the stock firmware, it uses Fastboot. See here:
http://nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
EniGmA1987 said:
You dont need ADB to install the stock firmware, it uses Fastboot. See here:
http://nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
Click to expand...
Click to collapse
Thank you for your help. Although the above process did re-flash the tablet with the downloaded 4.2.2 firmware, the touch screen is still not accepting any input.
Google only host the 4.2.2 image on their site, but the post here: http://forum.xda-developers.com/showthread.php?t=2003731 has the 4.2 version. I shall download that and try again.
Sinker_UK said:
Thank you for your help. Although the above process did re-flash the tablet with the downloaded 4.2.2 firmware, the touch screen is still not accepting any input.
Google only host the 4.2.2 image on their site, but the post here: http://forum.xda-developers.com/showthread.php?t=2003731 has the 4.2 version. I shall download that and try again.
Click to expand...
Click to collapse
4.2 downloaded and flashed; still no joy.
I guess this will have to go back to Google / Samsung. I don't know what the 4.2.2 update did, but it appears to have completely killed the touch screen!
Sinker_UK said:
Hey,
So I received the Nexus 10 this morning, signed into my Google account, downloaded a few app updates, then it said the 4.2.2 update was ready. I let it install and reboot, but ever since touch is not working at all on the device. It boots fine, but it won't unlock as it doesn't register the touch.
I've used the Recovery menu to restore it to factory defaults, which it did, but touch still doesn't work (I can't change language etc). I've downloaded the official 4.2.2 ROM, the SDK, installed the USB drivers, but ADB Devices doesn't find it. I guess this is because I can't enable Debugging Mode.
Can anyone offer some advice? Yes, I could return the tablet to Google, but I head back to the Middle East in a few days and I should imagine the turn around time will be much longer than that.
I'm happy to install any custom kernel, recovery mode etc. to try and restore it. When booted, Windows Explorer will allow me access.
I've Googled as much as I can, but most things rely on being able to enable the ADB link.
Many thanks.
Click to expand...
Click to collapse
Sorry for not providing any help, however it's a bit strange that flashing a firmware break the screen.
I just received my tab yesterday then flash 4.2.2 OTA without any issues
FredC94 said:
Sorry for not providing any help, however it's a bit strange that flashing a firmware break the screen.
I just received my tab yesterday then flash 4.2.2 OTA without any issues
Click to expand...
Click to collapse
Please don't worry about not providing any help; I appreciate that this one is an oddity. I was just hoping that the OTA had goosed the drivers or some-such, and that re-flashing it would help, but alas no.
Grab the original stock image 4.2.1 and try flashing back to that. Never heard of this before!
brees75 said:
Grab the original stock image 4.2.1 and try flashing back to that. Never heard of this before!
Click to expand...
Click to collapse
Well, as above, I tried the original 4.2 and that didn't work. I haven't seen the 4.2.1 image anywhere, but can't believe that would make a difference when the other two haven't. I've also just tried a touch-based recovery and that also doesn't respond to touches (TWRP). Oh well. :crying:
I'm at a loss of what to do now so will have to send it back. Pity, it was great when it did work!
Thanks for all the help.
I've contacted Google Play. They went through a reset then agreed to replace it. Will return it as faulty for a refund, and purchase another to save time. 32GB this time, seeing as they are now in stock!
Sent from my GT-N7000 using XDA Premium HD app
Phewwwww...scary...The 4.2.2 has been sitting on my task bar forever now but I am still resisting actually installing it. This thread might scare me away even more...Why fix things if they are not broken.
A better topic for your post: "My touch screen happened to stop working after I installed the 4.2.2 OTA" .. but it may not have caused it.
Hardware can break at any time.
I'm holding off on letting 4.2.2 install itself because I read that it breaks Adblock in Firefox. Not sure what 4.2.2 will do for me, but I want Adblock to work!
Edit to add: also just read the thread here about 4.2.2 causing sloooow scrolling problems in Firefox. So if you use Firefox, don't let 4.2.2 install!
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
It would have saved you a lot of problems of you had of done it manually, without a toolkit
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk
Same problem !
saber13 said:
There is nothing that I can find that pertains to problems with installing Kitkat factory image 4.4 on my nexus 4 so I will state my problem with the hope of some insight.
I have a Nexus 4 that I have decided to sell and as a precautionary measure had decided to flash a fresh copy of Android version 4.3 last week to ensure all files were deleted. I used Nexus root toolkit and all went smoothly.
As the phone has not yet sold, I decided that I would update the currently OS to the latest version 4.4 kitkat to make it more appealing to buyers so I went back to Nexus Root Toolkit and went through the standard procedure of selecting my device and OS, etc. The phone is unlocked. I had no backup and went ahead and told the software to write over version 4.3 with 4.4. I thought all was going well, but the install was too short and didn't work with a message telling my to try "Force Flash" mode. So I tried again using force flash mode and this time the install took longer and the phone rebooted multiple times, only this time the phone wouldn't fully boot. It only boot loops now.
-I can put the phone into fastboot mode.
-The computer can communicate with the phone via USB cable.
-All info such as product name, variant, HW version, etc. is showing in fastboot mode.
I am unable to use Nexus Root Toolkit to fix my phone with or without using Force Flash mode.
I can't mount the phone and the computer can not detect the ADB at all.
Can anyone please tell me what I can do to fix my phone? Are there any other alternatives to flashing a fully functioning version of 4.4 Kitkat?
I have been at this for hours and I can seem to get anywhere with it. Is the phone destroyed?
Any help would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
---------- Post added at 01:19 PM ---------- Previous post was at 01:02 PM ----------
priyab said:
I have the same problem ! I have tried everything as you mentioned above. Additionally using the ADB I installed everything using the flash-all.bat and everything went well, however my phone is still in bootloop. Have you find a solution ? Please share if you have ... Thank you so much for posting the issue !
Click to expand...
Click to collapse
Hey the flash-all.bat worked !!!! .. I just waited for like 15 mins after the flash-all.bat was done and viola! its back
This is great find
Those who face this issue can go to safe mode and backup their data while on boot screen just keep pressing up and down volume button for some time phone will get into safe mode and can be backed up.
Hi everyone...
I have an awkward issue here with my Nexus 4...
It is in an eternal loop in bootlogo 5.1.1
I already did anything I found in Google search
Flashed ALL firmwares stock, tried some Cyanogenmod and nothing!
I already used simple .bat/.sh in stock folder, used Nexus Toolkit with bricked/bootloop ticked, SkipSoft Tookit and even a tutorial saying to use LGNPST to flash a developer version... this last one worked... but like said in tutorial, the rom is encrypted and the user can do nothing! After that, flashed stock rom and still got stucked in logo!
I did not say, but yes.. I always run ALL wipes
I do not know what else I can do! The phone seems to work normally. I can entry,
download mode, fastboot, recovery but system..
Any ideas?
Thanks for now and sorry about english!
Are you flashing the userdata.img file?
yes and no!
The same result... =/
After flashing userdata.img in fastboot, are you going into recovery using the power and volume buttons to perform a factory wipe?
yes... I already did that too!
Today in the morning, I installed a developer version 4.2 through LGNPST... The phone worked, but it is a old version, I want the last one 5.1.1 and I got the problem that internal memory shows 8GB instead of 16GB...
And I could not resolv this, even reading tutorials from xda forum
If anyone could give me a BIN file of 5.1.1 to use in LGNPST...
no one???
I'm facing the exact same issue, here my post
http://forum.xda-developers.com/nexus-4/help/nexus-4-stuck-animation-android-t3419997
Did u solved it?
No man...
unfortunately I ditched the device!
I've installed Android 4.2.2 and block OTA updates rooting the device, the problem is internally in the device, maybe is a hardware problem, I already made a test of the sensors and none works, for know I'm gonna use it just for phone calls and wapp...
thanks for answer....