Database Users

Unable to install 4.2.2 upodate

I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

Here is the error I am getting.
sent from my nexus 4 using google mind control

The OTA installer checks every single file it intends to patch before anything happens.
If a single file that is checked has been changed by even one byte, not one patch operation will occur.
The message you are getting means you did something to change or remove that file compared to how it was in the stock ROM.
Note that the installer halts on the first error of this type; there could be zero or many more of these errors awaiting you.
In short, OTAs are not meant for patching random non-Stock ROMs.

I installed beats from play store. Gutted. Just backing up all my data and gonna factory reset and try again
sent from my nexus 4 using google mind control

R: Unable to install 4.2.2 upodate
I had error 7 with TWRP recovery. Then I installed clockworkmod and it worked.
Nexus 7 3G - Tapatalk

Androll79 said:
I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phoneView attachment 1728828
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i have the same problem.but i flash stock recovery with WugFresh toolkit and wait until OTA update notification.and you will get your android running 4.2.2 version.

Odp: Unable to install 4.2.2 upodate
Guys, guys, guys. You need STOCK recovery for official updates.
Sent from my BMW E34 using XDA App

I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

There is modified OTA floating somewhere that skips check, worked for me since it reported that GoogleCalendar.apk was different than it should be....

Folks,
You need to stare at the actual error message.
If the failed assert() is complaining about a file (e.g. see the OP's 2nd image attachment) then THAT FILE IS THE PROBLEM. It means that it was altered or removed by a root-privileged operator from the way it was in the stock ROM.
If the failed assert is complaining about a build number, then it is possible that using a different recovery will allow the OTA to succeed.
So you have a couple of choices:
A) Go and find the stock version of the file and put it back into your ROM (with the correct file ownership and permission modes) and repeat the OTA install. Seems like a dumb idea though, as the installer stops on the first error encountered - you will need to keep repeating this process until you have restored all changed files. Could be only one file, could be a few, could be many. Note also that this applies to the boot image, too. Got a custom kernel? You'll need to put the stock boot image back in place, too.
B) Back up your apps using TiB or Carbon. While you are at it, take a nandroid backup too. Install the Factory 4.2.2 ROM, reinstall your fave custom recovery, and root the factory ROM. Boot it up, enter your Google creds, restore your apps & data (Carbon or TiB). Yep, you are gonna have to redo your homescreens. Big deal; that's something you would do anyway when hopping between ROMs (unless you have this covered already by using a non-stock Home/Launcher app which has its' own backup/restore capability)
C) Just wait a little bit - your ROM Dev will probably release a version based on 4.2.2. At that time you can do some stupid thing like overflashing the replacement ROM without wiping.
Unless you know exactly what you are doing, running a modified OTA with *all checks* suppressed is a seriously brain-dead idea. (Removing only the build version check should allow alternate recovery use - but for goodness sake, the OTA nukes the recovery anyway, so what's the big deal about putting the 4.2.1 stock recovery back in place ahead of the OTA?)
Look, running the Stock OTA is going to remove your recovery and very likely disable your root. You are going to need to put your recovery back and re-root anyway. Doing things the right way is barely more effort than what you are going to need to do the crufty way.
good luck

[Q] Is my phone completely bricked? Pixelated screen when I boot my rooted Defy XT

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Motorola Defy XT: So what does it mean when this is the only screen your rooted Defy XT can make??? Once i turn it on this the first and only thing that appears on the screen but after a few min. my phone starts being a phone and everything, well at least making all the sounds it used to and receiving messages still, but the screen is kaput. Is my phone Bricked for good? or is there anything I can do? Please someone help!!! :crying:

Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app

arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks for the response!
I've actually only just rooted my phone. I haven't put any rom on it. It is still running the factory gb on it. Only rooted it so that I could run a screen shot app on it, and was probably eventually going to rom it once I became a little more knowledgeable about doing so. But everything was working fine with the phone after rooting it, for about 2 weeks even, but yesterday I just pulled out my pocket after coming out of the grocery store, clicked it to unlock it and there was that screen. Tried everything to get rid of it, took the battery out, plugged it in the wall, my computer. Nothing. Weird thing is though, after 5 min of being on, it will continue being the phone that it is, making all its regular sounds and receiving messages and notifications, just with that pixelated screen, which leads me to believe that it might be a hardware/bios problem, or if phones even have bios. This is my first smart phone so I'm just really starting to get to know it. Again, appreciate all help given! Just bummed this phone I've had for a month has already crashed on me.

arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Also forgot to mention I tried a factory reset by memory but with no visual it's hard to see if I'm even doing anything.

Search for your stock from and flash it
You can also use the custom from like miui v5 for defy/defy+ http://forum.xda-developers.com/showthread.php?t=2232947
Do you have a cwm recovery? Or you have to use the fastboot method
Sent from my A11 using xda app-developers app

[Q] 8 or 16?

Well, I got my N4 3 days ago, but I recalled its a 16GB version, but now when I look back I only had 8gb?
Is there any way to identify which version am I in?
Or is there any chances that flashing stock recovery bootloader and system etc once using fastboot messed those up?
Because I'm using 4.3 this morning and I reverted earlier today.
Well, help please and thank you.

KiD3991 said:
Well, I got my N4 3 days ago, but I recalled its a 16GB version, but now when I look back I only had 8gb?
Is there any way to identify which version am I in?
Or is there any chances that flashing stock recovery bootloader and system etc once using fastboot messed those up?
Because I'm using 4.3 this morning and I reverted earlier today.
Well, help please and thank you.
Click to expand...
Click to collapse
The best way is check whats written on the box.
check in system>storage.

Box never really wrote anything.
There's only 5.6GB user available space.

Check the boot loader info I think it tells you which one you have. Also there's a bug when flashing stock images the 16gb shows as 8gb. A guide in Q&A has the fix
Sent from my Nexus 4 using xda app-developers app

KiD3991 said:
Box never really wrote anything.
There's only 5.6GB user available space.
Click to expand...
Click to collapse
You've got a 8gb nexus.
Sent from my Nexus 4 using xda premium

KiD3991 said:
Well, I got my N4 3 days ago, but I recalled its a 16GB version, but now when I look back I only had 8gb?
Is there any way to identify which version am I in?
Or is there any chances that flashing stock recovery bootloader and system etc once using fastboot messed those up?
Because I'm using 4.3 this morning and I reverted earlier today.
Well, help please and thank you.
Click to expand...
Click to collapse
If you are sure you bought a 16gb model this might be helpful:
http://forum.xda-developers.com/showthread.php?t=2033692
And my N4 box show which kind of storage i bought.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you boot to the bootloader it will say what version you have. If the bootloader say 16GB yet you only have 5.xGB free you probably need to do a full factory reset to get it to see all the storage. If the bootloader says 8GB then you're good as you are

The bootloader said I'm a mako 16gb alright.
Now on to , how to fix it. Will try what mini androidian said

That how-to he linked worked for me so it should work for you too.
Sent from my Nexus 4 using xda app-developers app

KiD3991 said:
The bootloader said I'm a mako 16gb alright.
Now on to , how to fix it. Will try what mini androidian said
Click to expand...
Click to collapse
WARNING: BACKUP DATA ALWAY the STEP 1
If you have custom recovery like CWM or TWRP just boot into it and wipe data and factory reset and reboot your phone.
If you have stock recovery just boot to recovery mode you will see an android buddy with a red mark on it just press the volume up + power button same time after while it will show up a list of option. Wipe Cache and factory reset then reboot your phone it should show up 12.9GB total free space on your phone now.

Thanks for the advice, I fixed it already.
Using the long method of clean wipes and reflashing everything, all I found is because I was once in 4.3 the radio is wrong and that might be it . ( although I do not see how it will affect)
In fact I'm always flashing rom to the fact that I don't have anything to lose.

[Q] Recovery data?

Ok so im running twrp 2.6 on beanstalk 4.3 and i went to make a back up and its showing me that wanting to back up system,data, and boot but whats got me is the data is 6266646mb what is that all about?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danebryan18 said:
Ok so im running twrp 2.6 on beanstalk 4.3 and i went to make a back up and its showing me that wanting to back up system,data, and boot but whats got me is the data is 6266646mb what is that all about?View attachment 2207641
Click to expand...
Click to collapse
i think that is all of your system data information (downloaded apps, passwords, pics, settings, etc). doing a factory reset/data wipe clear all of that.

jco23 said:
i think that is all of your system data information (downloaded apps, passwords, pics, settings, etc). doing a factory reset/data wipe clear all of that.
Click to expand...
Click to collapse
Ive tried everything full wipe,change recovery,flash differnt roms, even did a full format of internal memory and nothing chages I cant make any back ups now. Ive been up all night trying to fix it

danebryan18 said:
Ive tried everything full wipe,change recovery,flash differnt roms, even did a full format of internal memory and nothing chages I cant make any back ups now. Ive been up all night trying to fix it
Click to expand...
Click to collapse
i think I recall seeing some folks claim that they were having similar troubles with backing up 4.3 ROMs.

jco23 said:
i think I recall seeing some folks claim that they were having similar troubles with backing up 4.3 ROMs.
Click to expand...
Click to collapse
Well Im going to flash a 4.2 rom try that and see what happens. thanks for your imput

Well that didnt work.

danebryan18 said:
Well that didnt work.
Click to expand...
Click to collapse
hmmm... I was able to make several successful backups of 4.2.2 ROMs.
did you completely uninstall 4.3 and start from fresh? again, I read that some folks had trouble even getting back to stock or 4.2.2 from 4.3.
while I don't think there is an issue with TWRP, I would certainly post your question on that thread.

jco23 said:
hmmm... I was able to make several successful backups of 4.2.2 ROMs.
did you completely uninstall 4.3 and start from fresh? again, I read that some folks had trouble even getting back to stock or 4.2.2 from 4.3.
while I don't think there is an issue with TWRP, I would certainly post your question on that thread.
Click to expand...
Click to collapse
I just used matts tool and flashed back to stock and it fixed it all!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

danebryan18 said:
I just used matts tool and flashed back to stock and it fixed it all!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
great.
I would advise to create some nandroids of your fav 4.1.2 and 4.2.2 ROMs.

Ive flashed just about every rom for my M as it is just a play phone(no service lol) even unlocked it for other carriers and ive never had a problem like this. Well now that its fixed time to flash somemore 4.3's

5.0.2 - Experience and Discussion

Thought it would be good to have a thread dedicated to 5.0.2, instead of sifting through the 5.1.x Rolling Out and Stock OTA threads.
Got the prompt and updated this morning. Took about 10 minutes -- 3-4 minutes to install the updat and then a good 6-7 to go through app optimization (for 120+ apps).
Haven't had a chance to put it through its paces yet, but interested in what others experiences are. Improvement? Same old?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Screen flicker possibly gone? Was pretty bad before on mine, haven't had it since update now.

This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.

b1bub4bu said:
This will sound dumb probably: I am stock rooted with TWRP recovery. My N9 has a notification that update to 5.0.2 is available. As far as I know from reading guides and tutorials, I can't accept the OTA right? I have to manualy flash factory image? But how am I about to do that if the factory image for Wifi N9 5.0.2 isn't even available?
Thanks in advance.
Click to expand...
Click to collapse
You basically have two choices:
1) Flash the stock 5.0.1 system.img (this will install stock recovery) and boot.img, then vendor. Img then take the OTA.
2) Wait until Google posts the factory image.

Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
and if you have TWRP, then also recovery.img
once all these are stock, then you can take the OTA.
After the OTA, you can either reflash TWRP, or just simply fastboot boot it, then apply the latest SuperSU zip from chainfire's web site, and you'll be back to stock and rooted.

Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.

Ive tried the ota 3 times now and every time it 'errors' in recovery while flashing, I'm flabber gasted this is how Google now treats its nexus customers.

Ok I'm going to update my vendor
if any one wants it just tell me

Something else ... if you attempt the OTA once, you're done ... you can't re-attempt it unless you reflash back to original 5.0.1 stock.
It checks System first, and updates it ...
Then it checks Vendor, and updates it ...
Then it checks the boot image, and updates it.
So you you fail the vendor test, it's already updated System, and it won't run again.
You have to reflash system.img, vendor.img, AND boot.img before you can try again.
A much smarter method would have put the three verification steps one after the other, but obviously Google did not write the script that way.

Roxas598 said:
Can't say i've seen much of a difference
then again the update was only 23MB. What Google are thinking atm I'd love to know.
Click to expand...
Click to collapse
I think it's just some bug fixes. This is the only Nexus not moved to 5.1.1 by now, it's also the only Nexus using the K1 chipset. Not sure if the two are related, but it seems reasonable that they are running into some nVidia issues. 5.1.1 isn't out for the Shield tablet either.

ok guys updated to 5.0.2 just to get the vendor.img. it was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79

_litz said:
Actually, you will need to flash three things from the LXR22C 5.0.1 factory zip ...
system.img
vendor.img
boot.img
.
Click to expand...
Click to collapse
I appreciate this. Coming from Nexus 6, vendor.img doesn't exist.
And on Nexus 6 when flashing the stock system.img it checks recovery and if not stock will automatically flash recovery.img. Is Nexus 9 the same?

When will my Nexus 9 LTE Model get this?

USBhost said:
ok guys updating to 5.0.2 just to get the vendor.img was hard lol
well here it is for every one that wants it
here is it
MD5sum dae0d789680948890d2bc84989bf3f79
Click to expand...
Click to collapse
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...

stadicon said:
Thanks for that! Have you tracked the vendor partition changes? What could it solve and what not...
Click to expand...
Click to collapse
I was going to
But got lazy

The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?

stadicon said:
The 5.0.2 image is out: https://dl.google.com/dl/android/aosp/volantis-lrx22l-factory-62276615.tgz.
Sorry, UsbHost... ?
Click to expand...
Click to collapse
I know man I'm crying inside

Ok so I got my ota update and downloaded it. Now my Nexus 9 keeps trying to come on,then saying android updating apps, then shutting off and restarting , and then repeats the same thing ! I never rooted or flashed anything ! Its completely stock ! WTH ! Help !!!!!!!

Update showed up when I turned mine on, ended up bricking my device.
Would show the spinning balls and nothing else, tried wiping cache, factory reset and still ended up at the spinning balls. Google sent me a new one, but I really wish I could just return the stupid thing.
I'll never buy another "premium" Nexus tablet again, the only way I buy another is if they give us another Nexus 7 like device.

I'm doing a factory reset .It seems it still on android deleting screen for 10 min already. Is it frozen ??