Database Users

[Q] Verizon G-Tab Update - Effect on rooted tab?

If I do the Verizon update will it "unroot" my Tab? Will it screw anything up?
Thanks.

I'm not sure, I'm rooted and when I clicked to install the update, my tab did nothing. I know that doesn't help.

Same thing happened to me, there is another thread about this and there is a post of the update file, I ran that and it worked

robinsmy1 said:
Same thing happened to me, there is another thread about this and there is a post of the update file, I ran that and it worked
Click to expand...
Click to collapse
Do you have a link to that thread?
-- thanks, mike

Here is the dropbox link from the thread
http://dl.dropbox.com/u/11358417/fcaaa4b8ca18.htm
this is the thread
http://forum.xda-developers.com/showpost.php?p=12727936&postcount=7

robinsmy1 said:
Here is the dropbox link from the thread
http://dl.dropbox.com/u/11358417/fcaaa4b8ca18.htm
this is the thread
http://forum.xda-developers.com/showpost.php?p=12727936&postcount=7
Click to expand...
Click to collapse
Hmmm. When I click those links I get a bunch gobblygoop on my screen.
EDIT: Just read it needs to be opened in IE. Weird.

Yeah, I found it weird too.
I never tried from the Tab though, might work from there I guess
Update:tried from tab with Dolphin....same result as Chrome

Ok, so now it's on the Tab. How do I make the update do it's thing?

name it update.zip....put it in root of SD, reboot to recovery and choose install update.zip
At least that is what I did and it worked perfectly......do it at your own risk though.

robinsmy1 said:
name it update.zip....put it in root of SD, reboot to recovery and choose install update.zip
At least that is what I did and it worked perfectly......do it at your own risk though.
Click to expand...
Click to collapse
Dumb question: How do I boot to recovery?

Turn off....hold volume up while powering on
Volume down to install update.zip and press home. (after menu comes up)
Make sure you have decently full battery or on AC

Worked! Thanks!

Still can't copy/paste from the mail program.

Update
I zipped the file so it should be easier to dl. Try this link. If you are going to rename it unzip it first, then rename. It was originally a htm file in my cache folder but as above some have had success renaming and flashing it. I have not tried yet myself yet as I'd like to here from people who have root and bootstrapped ext filesystem. If you do let us all know your results. Cheers.
https://dl-web.dropbox.com/get/Public/fcaaa4b8ca18.htm.zip?w=64e40992

I put the update.zip on rapidshare for anyone who wants it
http://rapidshare.com/files/456489639/update.zip

So has anyone successfully updated that was rooted and running ext4?

Will it affect kernels or root access? If this gets rid of my of my kernel and won't allow to reflash ill be pissed! So if anyone has installed this please let me know. And if it's for the worst. Tell me how to get rid of the damn update icon!
Sent from my SCH-I800 using XDA App

coheirnt said:
Will it affect kernels or root access? If this gets rid of my of my kernel and won't allow to reflash ill be pissed! So if anyone has installed this please let me know. And if it's for the worst. Tell me how to get rid of the damn update icon!
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
Root was still there, and kernel build number did not change. the [email protected] did change.
I cannot guarantee that it will not affect kernel, but it did number change the build number so it suggests it did not

Firmware update downloaded.

I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?

I can't yet because of root. I need access to my computer.

crystalstylez said:
I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?
Click to expand...
Click to collapse
Installed it...

I got it also. 16gb u.s. Wifi version. it was installing & updating android apps as I left out for work.
Any changelog on what was changed or added?

I want to install it but will a root method be made for it. I am not near a computer to use the zedomax root method. Anyone had root while installing this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.

I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1

Downloading it now. Will install shortly.
Sent from my GT-N8013 using XDA Premium HD app
Edit:
Installed, must have wiped cache as all apps went through the updating process. No noticeable differences or problems. Seems to be a tick faster but that's probably just my perception.

I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.

californiarailroader said:
I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.
Click to expand...
Click to collapse
I hope one of the fixes is making bookmarks appear quicker in the stock browser.

cmunho said:
I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1
Click to expand...
Click to collapse
I wonder exactly which bugs. I hope that folder & keyboard bug got fixed. the one where they open by themselves when going to homescreen from certain apps or whatever. it was getting irritating having to constantly close them. Lol

Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
OK, as expected, lost root. Odin flashed the original cwm recovery back. reinstalled the original root file and and back to being rooted.
Still 4.0.4.

All you had to do was use voodoo ota rootkeeper to backup n restore root file. access to computer not needed.

I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks

vanillanesquik said:
I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks
Click to expand...
Click to collapse
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1

mitchellvii said:
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1
Click to expand...
Click to collapse
I used OTA rootkeeper as specified above. If that does not restore root I can re-do the Odin. Thanks

Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.

ye i just did it and i lost root but the first thing i noticed that is working faster. also the snote app was update you can upload your own template finally. when choosiing a background on the window pop up touch the little square image on the top right corner and it lets you choose from images in your gallery.

tmaurice said:
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.
Click to expand...
Click to collapse
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar

californiarailroader said:
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Click to expand...
Click to collapse
Thanks - I saw that link a couple of days ago, but didn't use it because it's the N8000 and we've got the 8013 here in the States.

[Q] Can you install the 4.1.2 OTA on an unlocked phone with CWM installed?

I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...

Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.

what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.

Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app

bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!

bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2

antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.

bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...

sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...

After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.

bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...

tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.

netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.

patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!

Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!

I'm not rooted and I keep getting Custom Status...why?

I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!

polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.

euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer

You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2

peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...

I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2

polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2

Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium

XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.

polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.

TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.

CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here

CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....

Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.

CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last

so far so good!!!:fingers-crossed:

polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...

joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!

Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[Q] OTA 4.3 Update + custom recovery + user stupidity

Hey!
So i've just received the update, and as per instructions i rebooted to install the update. But after rebooting, clockwork recovery appeared with the options of NO, NO, NO, etc, Yes install unknown ZIP, NO, etc. Because i was doing two other things at the moment (and i'm a moron) i've clicked Cancel and rebooted.
So now i'm still on 4.2.2 and when i click on "Check for system update" in setup it says "Up to date"
Am i totally screwed with the OTA update? I'll punch myself in the face if i have to do the update manually and resetup everything on my device <.<''
Thanks!

No, you're not boned. Try this.
http://www.droid-life.com/2013/07/25/android-4-3-update/

Rirere said:
No, you're not boned. Try this.
Click to expand...
Click to collapse
With the file from my /cache folder CWM gives Status 7 - Installation aborted. (i've moved the file to my "SD card")
As far as i saw, that might pop up if the ROM is not well done, but that is the file that i got from Google
So... any ideas how shall i proceed?

Sound Anarchist said:
Hey!
So i've just received the update, and as per instructions i rebooted to install the update. But after rebooting, clockwork recovery appeared with the options of NO, NO, NO, etc, Yes install unknown ZIP, NO, etc. Because i was doing two other things at the moment (and i'm a moron) i've clicked Cancel and rebooted.
So now i'm still on 4.2.2 and when i click on "Check for system update" in setup it says "Up to date"
Am i totally screwed with the OTA update? I'll punch myself in the face if i have to do the update manually and resetup everything on my device <.<''
Thanks!
Click to expand...
Click to collapse
If you don't want to do a manual update, you can either wait it out - the OTA will come back again eventually - or, you can take a look at system/cache and see the 4.3 update.zip, move it over to your root folder, then go into CWM recovery and install that.

mlj11 said:
If you don't want to do a manual update, you can either wait it out - the OTA will come back again eventually - or, you can take a look at system/cache and see the 4.3 update.zip, move it over to your root folder, then go into CWM recovery and install that.
Click to expand...
Click to collapse
Yep, did that Now i have another issue - see post above yours.

Hi, i'm having the same problem (kinda)
i am on stock rom, twrp recovery + multirom , timur's kernel.
i got the ota, said install, went to twrp, installed, but nothing happened. Now i am on 4.2.2, system says up to date.
i cant find update.zip anywhere.
can u help me?
Sent from my Nexus 7 using XDA Premium HD app

hamid_valad said:
Hi, i'm having the same problem (kinda)
i am on stock rom, twrp recovery + multirom , timur's kernel.
i got the ota, said install, went to twrp, installed, but nothing happened. Now i am on 4.2.2, system says up to date.
i cant find update.zip anywhere.
can u help me?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I think it's because you are not using stock kernel. As far as i've gathered from reading here, there is no trouble with custom recovery in general (it seems that sometimes there are issues - mine for example), but otherwise you should be stock: Google's ROM + kernel. If i was in your situation, i would flash the original kernel (you can extract it from the 4.2.2 release image). I'm not sure about multirom, you should research that.
As for my issue, after sleeping on it i think that i'll just wipe and flash the whole 4.3 image. After that i'll setup everything again.
Turns out, that the applications i need to backup data from are not so much, and i figured out where they keep the data i'm interested in. Also i want to see if wiping will help my memory issues (almost full device = slow as hell device).

hamid_valad said:
Hi, i'm having the same problem (kinda)
i am on stock rom, twrp recovery + multirom , timur's kernel.
i got the ota, said install, went to twrp, installed, but nothing happened. Now i am on 4.2.2, system says up to date.
i cant find update.zip anywhere.
can u help me?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Me too,but i'm using stock kernel...
Sent from my Sony Xperia™ sola using XDA Premium

I got error when flashing...
Anyone please help...
Sent from my Sony Xperia™ sola using XDA Premium

Ben Ling said:
I got error when flashing...
Anyone please help...
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
Yup, thats like mine.
mine says xt9ime.apk missing, and the numbers are different!
Sent from my Nexus 7 using XDA Premium HD app

Ben Ling said:
I got error when flashing...
Anyone please help...
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
i found a way, trying right now!!! if it works, i'll let u know!
Edit 1: Failed
Edit 2: Use it, maybe it helps u
BACK UP FIRST!!!!! I DO NOT TAKE ANY RESPONSIBILITY, my device got into X mark, nothing happened.
open the zip file, go to META-INF--> com --> google --> android, copy the updater-script to your desktop, then delete it from the zip archive
open the file on your desktop with notepad
search for "systemui" or what ever your problem is
delete the whole line. starting with "set_progress" ending with "));"
in my situation it was:
"set_progress(0.448070);
assert(apply_patch_check("/system/app/SystemUI.apk", "cca620c865fb91868a3afc70f005c93dc44beb60", "3c7b5c2e77cd9296276f9e7c372f298d1913644a"));"
then search again and you will find another like bellow:
"set_progress(0.451753);
assert(apply_patch_check("/system/app/SystemUI.odex", "7ad50dd5929e3d681f4d11199fe852c1ad620ad5", "1a424ccaa5cd08e82feec972649b42aec4b8a512"));"
then again:
"set_progress(0.481089);
apply_patch("/system/app/SystemUI.apk", "-",
cca620c865fb91868a3afc70f005c93dc44beb60, 1471663,
3c7b5c2e77cd9296276f9e7c372f298d1913644a, package_extract_file("patch/system/app/SystemUI.apk.p"));"
and the last one:
"set_progress(0.484752);
apply_patch("/system/app/SystemUI.odex", "-",
7ad50dd5929e3d681f4d11199fe852c1ad620ad5, 503088,
1a424ccaa5cd08e82feec972649b42aec4b8a512, package_extract_file("patch/system/app/SystemUI.odex.p"));"
save and copy the new file to the previous location.
then install the new file.
hope it helps.
let me know if it worked.

hamid_valad said:
i found a way, trying right now!!! if it works, i'll let u know!
Edit 1: Failed
Edit 2: Use it, maybe it helps u
BACK UP FIRST!!!!! I DO NOT TAKE ANY RESPONSIBILITY, my device got into X mark, nothing happened.
open the zip file, go to META-INF--> com --> google --> android, copy the updater-script to your desktop, then delete it from the zip archive
open the file on your desktop with notepad
search for "systemui" or what ever your problem is
delete the whole line. starting with "set_progress" ending with "));"
in my situation it was:
"set_progress(0.448070);
assert(apply_patch_check("/system/app/SystemUI.apk", "cca620c865fb91868a3afc70f005c93dc44beb60", "3c7b5c2e77cd9296276f9e7c372f298d1913644a"));"
then search again and you will find another like bellow:
"set_progress(0.451753);
assert(apply_patch_check("/system/app/SystemUI.odex", "7ad50dd5929e3d681f4d11199fe852c1ad620ad5", "1a424ccaa5cd08e82feec972649b42aec4b8a512"));"
then again:
"set_progress(0.481089);
apply_patch("/system/app/SystemUI.apk", "-",
cca620c865fb91868a3afc70f005c93dc44beb60, 1471663,
3c7b5c2e77cd9296276f9e7c372f298d1913644a, package_extract_file("patch/system/app/SystemUI.apk.p"));"
and the last one:
"set_progress(0.484752);
apply_patch("/system/app/SystemUI.odex", "-",
7ad50dd5929e3d681f4d11199fe852c1ad620ad5, 503088,
1a424ccaa5cd08e82feec972649b42aec4b8a512, package_extract_file("patch/system/app/SystemUI.odex.p"));"
save and copy the new file to the previous location.
then install the new file.
hope it helps.
let me know if it worked.
Click to expand...
Click to collapse
ok,i'll try...but why do i need to change to apk.p?
---------- Post added at 12:41 PM ---------- Previous post was at 12:10 PM ----------
Can anyone provide me system/bin/app_process from Nexus 7 3G?

Sound Anarchist said:
Yep, did that Now i have another issue - see post above yours.
Click to expand...
Click to collapse
Hey,
Sorry saw that you did a clean re-install already.
I had the same problem as you. What I did was to flash TWRP (unlike CWM it allows you to ignore the verification error) and tried to take the update again. That still failed however, because I apparently had an edited debuggerd file (happens if you use the Stickmount app). I downloaded a stock one from this thread, replaced it in system/bin, and re-flashed 4.3. Finally worked.
I then re-rooted by flashing the latest SuperSU in TWRP.

Are you replacing the 'debuggerd' file within the 4.3 zip update? Or the file on the Nexus 7 before the 4.3 is flashed?
I've tried updating 4.3 using the OTA 4.3 zip & TWRP & my nexus 7 is currenly stuck the the 'X' boot logo.

hamid_valad said:
i found a way, trying right now!!! if it works, i'll let u know!
Edit 1: Failed
Edit 2: Use it, maybe it helps u
BACK UP FIRST!!!!! I DO NOT TAKE ANY RESPONSIBILITY, my device got into X mark, nothing happened.
open the zip file, go to META-INF--> com --> google --> android, copy the updater-script to your desktop, then delete it from the zip archive
open the file on your desktop with notepad
search for "systemui" or what ever your problem is
delete the whole line. starting with "set_progress" ending with "));"
in my situation it was:
"set_progress(0.448070);
assert(apply_patch_check("/system/app/SystemUI.apk", "cca620c865fb91868a3afc70f005c93dc44beb60", "3c7b5c2e77cd9296276f9e7c372f298d1913644a"));"
then search again and you will find another like bellow:
"set_progress(0.451753);
assert(apply_patch_check("/system/app/SystemUI.odex", "7ad50dd5929e3d681f4d11199fe852c1ad620ad5", "1a424ccaa5cd08e82feec972649b42aec4b8a512"));"
then again:
"set_progress(0.481089);
apply_patch("/system/app/SystemUI.apk", "-",
cca620c865fb91868a3afc70f005c93dc44beb60, 1471663,
3c7b5c2e77cd9296276f9e7c372f298d1913644a, package_extract_file("patch/system/app/SystemUI.apk.p"));"
and the last one:
"set_progress(0.484752);
apply_patch("/system/app/SystemUI.odex", "-",
7ad50dd5929e3d681f4d11199fe852c1ad620ad5, 503088,
1a424ccaa5cd08e82feec972649b42aec4b8a512, package_extract_file("patch/system/app/SystemUI.odex.p"));"
save and copy the new file to the previous location.
then install the new file.
hope it helps.
let me know if it worked.
Click to expand...
Click to collapse
Hmm ... you are preventing the update of the SystemUI.apk? Even if your modification will work, you will have a 4.3 base system with a 4.2.2 SystemUI running ...

AndDiSa said:
Hmm ... you are preventing the update of the SystemUI.apk? Even if your modification will work, you will have a 4.3 base system with a 4.2.2 SystemUI running ...
Click to expand...
Click to collapse
Yup. Also u can just delete the verification part!
Sent from my Nexus 7 using XDA Premium HD app

That's clear for me, but you are not only deleting the verification part, but the update for the SystemUI.apk, too ...
Sent from my Nexus 7 using xda app-developers app

cmberry20 said:
Are you replacing the 'debuggerd' file within the 4.3 zip update? Or the file on the Nexus 7 before the 4.3 is flashed?
I've tried updating 4.3 using the OTA 4.3 zip & TWRP & my nexus 7 is currenly stuck the the 'X' boot logo.
Click to expand...
Click to collapse
I replaced the file on the Nexus 7 (in system/bin) before flashing 4.3.