After I updated my nexus 10 to the Android 4.3 (JWR66V) from a request on the device, all seem'ed normal, until I reset the device. After resetting my nexus 10, the device would turn on the screen and turn off the screen non stop never booting. I tracked the bug down to the (recovery.img ) file used in the update. After downloading Android 4.3 (JWR66V) I modified the ( image-mantaray-jwr66v.zip ) with 7zip replacing recovery.img with the recovery.img from Android 4.2.2 (JDQ39). If you don't know how to do this then please ask for help, I will reply or some one else might reply to you're questions. I sure hope they find this bug and fix it for us, but right now I'm getting the word out, there is a problem and it need's to be reported and fixed manualy. Thank you.
JasonMatthewRaub said:
After I updated my nexus 10 to the Android 4.3 (JWR66V) from a request on the device, all seem'ed normal, until I reset the device. After resetting my nexus 10, the device would turn on the screen and turn off the screen non stop never booting. I tracked the bug down to the (recovery.img ) file used in the update. After downloading Android 4.3 (JWR66V) I modified the ( image-mantaray-jwr66v.zip ) with 7zip replacing recovery.img with the recovery.img from Android 4.2.2 (JDQ39). If you don't know how to do this then please ask for help, I will reply or some one else might reply to you're questions. I sure hope they find this bug and fix it for us, but right now I'm getting the word out, there is a problem and it need's to be reported and fixed manualy. Thank you.
Click to expand...
Click to collapse
Did you check your MD5 checksums after downloading? Honestly just sounds like you got a bad recovery.img more than anything else.
I hope it's just a bad download, but, here is why I think it's not.
My nexus 10 updated on it's own, then, I reset the device & it went in an on off loop.
I downloaded the nexus 10 restore after that, and, had the same looping issue after running it too.
The only way I found out there was a bug is after a reset, so, you wont notice until it's to late.
I know how to run fastboot & how to use the nexus 10 restore, replacing recovery.img solved my problem.
If I had faster internet I would download again, I have max 110kbs download speed.
If no one else is having there device loop on and off after the update then reset than it might have just been a bad download two times in a row.
Please let me know if you're nexus 10 works after the new update and a reset, I'm hoping this is just an issue I have.
Thanks.
Related
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Godders11 said:
I have a new 2013 Nexus 7 running stock Android 4.3, not rooted or any of that jazz.
I’ve received a system update a couple of times and when I’ve gone to install it I just get an unspecified error when installing (I get a picture of the android bot laid on its back with an exclamation mark in a red triangle and not text other than “error”). I have to hold the power button down for some time to switch the tablet off and then it restarts fine but without the update applied (build is JWR66N, I assume this is the OTA JSS15Q update).
Tonight I did a factory reset, got the update pretty soon afterwards and exactly the same thing happened.
Any ideas? I’m an Android newb so I don’t really want to get into flashing images just yet (but will give it go if there are no other options).
Click to expand...
Click to collapse
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Many thanks, I'll give that a try.
sfhub said:
You are suffering from the corrupted /system problem.
Use this post to install JSS15Q.
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Click to expand...
Click to collapse
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
doggie123 said:
That worked fine, although only at the 2nd try!
Not sure if it is related to what you said, but the first try got stuck at erasing 'system'. That step should take milliseconds, instead it hung for 10+ minutes...
Decided to reboot, back to recovery (all it would do at that stage) - and then it worked. So thanks, and a reminder to never give up
Click to expand...
Click to collapse
Hmm, I wasn't expecting that to happen, just expecting some file corruption to be overwritten, but it looks like you potentially had some bad sectors in the eMMC as well that got blocked out automatically by the erase.
This reminds me of the eMMC problem we had on Samsung where they changed wipe data to do a secure erase and that triggered an eMMC bug that left people with megabytes of unusable sectors.
If I were you, I would only run my system using a JSS15Q kernel because that has the fixes for the type of issue your unit seems susceptible to.
http://forum.xda-developers.com/showthread.php?p=44954087#post44954087
Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.
Yeah I have the latest OTA also, but I am still having the same issue!!
StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.
Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:
Hey everybody,
i wanted to update my rooted N4 with twrp from 5.1.0 tp 5.1.1. So i thought i just flash bootloader.img, radio.img, boot, system, recovery and cache.img from 5.1.1 factory image on top of my existing 5.1.0 setup. After that i reflashed twrp and rerooted with CF-auto-root. I gues that's where it went wrong. After that i got stuck in a bootloop. So i decided to restore my nandroid backup. Doesn't work. Can't mount cache and ends the data restore with error 255. That sucks. So i decided to flash the 5.1.0 factory image. So i flashed it with flash-all.bat in fastboot. Now it should be good to go, but i'm still stuck in a boot loop. The 4 colored dots are flying around for hours. Whats am i supposed to do?
Haalp!!
Thanks a lot
I had thamt proble so i finally booted into the bootloader using the press Volume Down and power button the did a recovery and let it reboot and everything worked fine after that....
Nexus GPF Lollipop Troubleshooting Guide & Tips
Scenario #1: For Folks that have received the OTA prompt, but the device seems to be “hung” in a bootloop state:
Please be ready to wait 30 minutes for the L installation to finish updating. Please do not interrupt the OTA mid-process.
If that doesn’t help, please see recommendations within Scenario #3
Scenario #2: For Folks that have received the OTA prompt, downloaded it and had it say “Failed”:
Is your bootloader unlocked? Are you rooted? There is some information that’s floating around that says an unlocked bootloader is causing issues. I, nor Google for that matter, can confirm the issue being related to that, I'm just here to try and help those having OTA issues. If you do have an unlocked bootloader, please try locking it, and accepting the OTA that way.
If you’re looking for ways to relock: a google search would yield similar results to this or there are toolkits that can help with relocking (Wugfresh for Example), however *tinker at your own risk, we are not suggesting this as the preferred method, just giving you options*
Scenario #3: “I still have not received the L OTA update! When will I be able to download it for my Nexus xxx”
Please be patient as the Android 5.0.1 Lollipop OTA update is still rolling out to all Nexus owners (for example, the factory images for the Nexus 4 & 6 just popped up). Depending on where you are located in the world, you should be receiving the notification soon.
For those trying to remember how to check for the update: Settings > About phone > System updates. We’re all guilty of checking at least several times a day, don’t fret, it will show up .
Wanna know how the rollouts work while you’re waiting? There's a good article on Android Central that explains how and why the OTA works. Owners of Nexus devices should periodically check the system updates as Google handles rollouts across devices differently.
I hope that helps
Let us know how you do
Blacksmith5 said:
I had thamt proble so i finally booted into the bootloader using the press Volume Down and power button the did a recovery and let it reboot and everything worked fine after that....
Click to expand...
Click to collapse
Thanks for ya help. But what exaclty do you mean by "did a recovery" in bootloader?
Thanks
Okay, never mind. I just interrupted the bootloop as i did a hundred times before. Now it restarted within seconds. Computers are weird people.
Wipe the cache in Recovery.
This fixed my boot loop on a dirty flash to 5.1.1.
Bootloop following contact with water? Or recent update?
Hello,
Here is my story : end of last wwek, my phone fall in a small amount of water (1cm) on the top (jack side). I wiped it very fast and use it for the next 30 min, everything is good. and then i let it 2 hours (charging or not i don't remember, i don't know if it can matter). After that i find it bootlooping was there an update, end of last week? Anyway i let it in that state at least 30 min and even more and then tried to restart it not better. I also tried a wipe cache and after that a factory reset, nothing...
Yersterday back to home, i tried to flash the 5.0.1 factory image ( didn't want to take the 5.1, because i feared a possible bad update on the image maybe) nothing better, even worst because after after some time of bootlooping, i've got the red light flashing :/
Same goes for the 4.4 flash but small miracle, it's working 4.2.2... During all those tries, i did some oem lock and unlock before and after each flash.
So my phone is working with the first version of android available, which is not the best.... I also tried the OTA update to the 4.3 and i also got stuck to a bootloop
So after that long story (sorry), I defer to your expertise because i don't know what else to do.
Please help :/
I just installed the lastest version of cyanogen and it's working well...
Still no idea whats happening there?
Seems to be a real big question i ask you there, but i continue my thinking on my side.
I dont like the idea, but it light be a hardware problem... Maybe a failing memory slot, or an unused component until then.
So it brings me 2 questions : how and where could i find logs after a failed update?
And how could i efficiently test my hardware CPU, RAM, as we can do on a computer?
Thanks in advance, any idea, help, joke are welcome
Hey so when I received my phone I set up everything like normal person does on the latest OTA(at that time 4.5.2) and removed encryption,today I decided to install latest OTA but for some reason after flashing full zip in twrp it refuses to boot,all I can see is OnePlus logo
Does anyone else have same issue or atleast know what can be the problem ?
I even tried to look on the log but I didn't see anything
Log is here
Edit1: I tried to do a lot of backups/restore and my phone now refuses to boot even from backup that was working before..
Edit2: Going into bootloader and using fastboot format userdata made me install latest ota
twrp problem, seem still to be bit buggy
Hastaloego said:
twrp problem, seem still to be bit buggy
Click to expand...
Click to collapse
I have no idea what the issue was I'm thinking it was something to do with encryption but I'm not sure