yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] chakme:
Same Issue !!

I've got the same issue... it rebooted into the TWRP recovery, but the screen just freezed and touch didin't worked. Had to remove battery and reboot. After that, JWR66V was still there! And now, it doesn't prompt the update again. I'm thinking about flashing 4.3 again, root but not to install TWRP recovery, only 4.3 stock and root !! As [MENTION=3245894]dbenyakar[/MENTION] asked "any solution to this" ?

In time, mine is a Galaxy Nexus I9250...
[Nexus 7 General] GedBlake:
Hi, dbenyakar...

The reason why the OTA that updates from JWR66V to JWR66Y fails if you are rooted concerns a file call /system/etc/install-recovery.sh and the different way that root now works under Jellybean 4.3.

Root uses the file install-recovery.sh to launch sudaemon that provides root, and during the process of gaining root, this file is set as 'immutable' to prevent root from being accidently lost. But this also prevents the OTA from modifying it, including the setting of permissions during the last stage of the OTA... therefore the OTA fails. See also

this

.

There are several different ways this problem can be resolved...

1) There is a slightly modified version of the OTA

here

, which 'rems out' the setting of permissions for /system/etc/install-recovery.sh, and allows the OTA to successfully complete. This modified OTA can be flashed in TWRP and was the method I used to upgrade.

2) Before allowing the OTA, unroot by going to SuperSU>>settings>>Full Unroot. Allow the OTA, and then re-root by flashing

Chainfires SuperSu 1.51

in TWRP.

In any event, you'll probably need to re-root after the OTA anyway. I certainly had to.

Hope this helps.

Rgrds,

Ged.
[Nexus 7 General] threi_:
So based on that is this something that will occur every OTA (i.e. you will have to unroot every OTA to avoid problems)?
[Nexus 7 General] dbenyakar:
OK great. Thanks for that. Will try it tonight.

I tried to use the OTA Root Keeper to temporarily unroot my device, only to realize it does not support 4.3.

So I guess I will have to unroot, update and re-root using your method. No shortcuts here. Once the OTA Root Keeper application will be compatible with 4.3 then it will be easier.
[Nexus 7 General] GedBlake:
Hi, threi_...

It's speculation, obviously, as one cannot know the contents of future OTAs beyond the current one which updates to build JWR66V... but it seems likely you will have to unroot, and then re-root again after the OTA.

But there may be workarounds... as I've indicated in my previous post, somebody has already posted a modified version of the current OTA that skips setting permissions for install-recovery.sh, and allows the OTA to complete successfully.

And to elaborate on my previous comments, here's why...

Root modifies /system/etc/install-recovery.sh in order to launch the su root daemon, and it contains the following lines...

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older.
# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, but the
# installer will have done "chattr +i" on this file to prevent
# accidental modification and deletion. In your code, just search
# this file for "install-recovery-2.sh", and if present, write
# there instead.

/system/etc/install-recovery-2.sh

And during flashing Chainfires SuperSU root updater, the following operation is performed...

chattr +i /system/etc/install-recovery.sh

This 'locks' the file, using the +i flag ('immutable'), and prevents even system updates from modifying it.

You should be able to reverse this with...

su
mount -o rw,remount /system
chattr -i /system/etc/install-recovery.sh
mount -o ro,remount /system

...in Android Terminal Emulator, but you will need Busybox installed.

So it's probably just easier to unroot... allow the OTA as normal (or flash the OTA .zip in recovery)... and then re-root again. And I can't see this changing with future OTA's... but as I stated at the beginning of this post, this is just speculation on my part.

Rgrds,

Ged.
[Nexus 7 General] dobrun.franjo:
Hi. I am on 4.3 stock rooted with m kernel a61 and with advanced power menu mod and awesome beats. Cant update .read everything about this new update and also opened a thread but still cant find a way to update.flashing failed.tried full unroot and faild again.trid modified grouper.zip and that also failed.

Any ideas???
[Nexus 7 General] GedBlake:
Hi, dobrun.franjo...

Any modifications to system (including kernel) need to be removed before any OTA can proceed... and I suspect 'advanced power menu mod and awesome beats' have modified system.

This is because OTAs run a checksum on all files in system BEFORE 'patching' (meaning updating) them, to ensure they haven't been removed or changed in anyway. After all, an official OTA can't be expected to update files it has no knowledge of, that have been added by the user. If even one fails this checksum test, the OTA will abort, with no changes made.

So... remove advanced power menu, remove awesome beats and fastboot flash the factory stock kernel for Jellybean 4.3. Even then, there are no guarantees the OTA will work, without knowing (and being able to reverse) EXACTLY what files where changed as a consequence of your modifications... but it's worth a shot.

Good luck.

Rgrds,

Ged.
[Nexus 7 General] NeoMagus:
As long as the new root process goes through the installrecovery.sh, correct

Supercurio has already said as long as it stays this way, OTA rootkeeper won't be possible anymore.
[Nexus 7 General] supercurio:
Yes however a method has been found for 4.3, so I'll look into that soon :)
[Nexus 7 General] khaytsus:
As the previous poster said, you screwed with system, OTA's won't work. Easiest way to update at this point IMO is to grab the YJWR66 factory image from Google and fastboot flash system, then re-root.
[Nexus 7 General] emameme:
Today I have update with OTA and same error appear.

Now I have unroot the nexus with supersu's app but how I can update it? It doesn't give any update now :(

Thx guys.

Inviato dal mio Nexus 7 usando Tapatalk 4
[Nexus 7 General] dbenyakar:
OK I did it your way. Thank you very much for that.

I had some problems with my SuperSU and could not access the SuperSU>>settings but eventually I managed to unroot the device and continue with the installation and re-root. :laugh:
[Nexus 7 General] tu3218:
I tried step one and it failed in twrp. I downloaded grouper for my WiFi version. Any ideas why it failed? Is it because I'm trying to flash over clean ROM 4?
[Nexus 7 General] khaytsus:
2000+ posts and you don't realize you can't flash a stock OTA over $randomrom ? Just wow.
[Nexus 7 General] tu3218:
Well its a small zip. Not a full ROM. So I figured it was just patching the updated files. Clean ROM is a pretty stock ROM so I was thinking it may have worked. Normally updates are full roms.
[Nexus 7 General] khaytsus:
Updates are never full ROMs, they're a set of patches against checksummed files. Any single checksum difference and it'll fail. IE: Modify the ROM in almost any way, you can't use OTAs.

When you're on a custom ROM, use the custom ROM updates as they come out, no real difference between modified stock and say Cyanogenmod in this respect.
[Nexus 7 General] tu3218:
Yeah you're right. Not sure what made me think it would work. I guess I was thinking it was modified, but its still just the stock ota with a slight adjustment to be installed properly on rooted devices.

It doesn't appear clean ROM will be updated as scott has ,moved onto the newer nexus 7. So I have to find out my next best move. I'm fine with stock, just getting there.
[Nexus 7 General] AidenM:
He should have either announced he is dropping support (is that in the thread?) or only provided basic bug fixes/otas like this.

All it takes is to patch the files the update would just manually and without any checks. As far as I know, updates this small are pretty much just replacing/adding on to older files.
[Nexus 7 General] tu3218:
Yeah, I'm not sure if he officially announced it or not. But the thread is extremely quiet and no one seems to be worried about the update. So not sure if people are going to another rom, device or what. I just want to update and get rid of the update notification lol
[Nexus 7 General] emameme:
Why OTA doesnt reappear after failure?

Inviato dal mio LG-P880 usando Tapatalk 4
[Nexus 7 General] dobrun.franjo:
Clear cache/data of Google Services Framework in SETTINGS/APPS

then u ll see it again :)
[Nexus 7 General] quizface:
it will in two or three days time
[Nexus 7 General] ngorar:
Hello Ged, I followed your 2nd option. My Nexus 4 finally updated to JWR66Y. Thanks a lot.

But after that, it is unable to re-root. I flashed UPDATE-SuperSU-v1.50.zip accidentally and then downloaded and flashed UPDATE-SuperSU-v1.51.zip. But it still doesn't work. Can you help?

Thanks in advance.

Tom
[Nexus 7 General] downwiththebanksters:
I'd actually like to do the opposite. I'd like to get rid of the nag "system update downloaded". How can I get rid of the notification please?
[Nexus 7 General] borekon:
Thanks, worked like a charm :good:
[Nexus 7 General] dobrun.franjo:
U can freeze google services framework
[Nexus 7 General] shawnbon206:
The handiest solution for this is just to update via fastboot. This solution will work no matter what, and it only updates your rom, and it leaves your /data and /recovery partitions untouched:

Download factory image and extract everything, including any .zip contained within the .tgz

1. From command line:

./flash-base.sh

fastboot flash boot boot.img

fastboot flash system system.img

fastboot erase cache

2. Press vol-down a few times until "recovery" is highlighted and then press power to reboot to it

3. Once your custom recovery has finished booting, simply flash superuser.zip

4. Select "reboot" from the main menu and allow it to disable stock recovery re-flash
[Nexus 7 General] choybel:
HI, could you please teach me how to do this step-by-step? Doing this could help me learn using fastboot and at the same time help me solve my current problem. I would definitely appreciate your help.

By the way, I have read this guide: http://xdaforums.com/showthread.php?t=1907796 but there it states that everything will be erased so I'm hoping to do your suggestion instead.
[Nexus 7 General] shawnbon206:
Ok I will try. The above was just an example. I will be more specific.

pre-reqs: 1. having adb and fastboot in your path

2. having adb/fastboot drivers installed on your os (if you're on windows)

3. having basic command line and file management skills

4. know how to get your device into fastboot or recovery modes

reliably

5. you have the latest flashable SuperSU.zip in the root of your /sdcard

6. you've made a nandroid backup first!!!

Notes: I am going to use tilapia as an example because that's what I have. if you have grouper, ignore the part about flashing the radio!

Flashing "bootloader" might give you an error if youre already on v4.23. Ignore it.

Flashing "system" takes a few minutes longer than everything else

Here we go:

1. download correct firmware for your device from here: https://developers.google.com/android/nexus/images#nakasi

2. extract all contents of nakasig-jwr66y-factory-bdbb7bd7.tar to an empty directory

3. extract image-nakasig-jwr66y.zip to the same directory. you should now have the following in a single directory:

android-info.txt boot.img radio-tilapia-1231_0.18.0_0409.img bootloader-tilapia-4.23.img recovery.img flash-all.bat system.img flash-all.sh userdata.img flash-base.sh

4. shift+right-click in this directory and "open command window here"

5. plug your device into your computer, enable adb, and issue "adb reboot-bootloader" command (no quotes) and your device will reboot to fast boot

6. issue all these commands

one-by-one

in the command window:

fastboot erase boot
fastboot erase system
fastboot flash bootloader bootloader-tilapia-4.23.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img

7a. At this point, if you don't already have a custom recovery installed you should install one e.g. "fastboot flash recovery recovery-clockwork-6.0.3.6-tilapia.img" (no quotes)

7b. Press Vol-Down two times. Your device should say "Recovery Mode" in red, press Power once to select and it reboot into recovery mode.

8. install zip>choose zip from sdcard>0/>UPDATE-SuperSU-v1.55.zip>Yes

9. ***Go Back***>wipe cache partition>Yes

10. reboot system now>Yes- Disable recovery flash

yer done
[Nexus 7 General] choybel:
So after several re-reading, I finally got a little sense of what to do, but I still don't understand what you meant by "./flash-base.sh" ...should this be input?If so, how or where? because I tried in adb command, but it says command is not recognized. Enlighten me please.

---------- Post added at 05:57 AM ---------- Previous post was at 05:34 AM ----------

Oh, okay...just a few questions...My device is already unlock so is it safe to skip oem unlock command? I have twrp already installed, what should I do after step 6?

________________

Now updated! So happy and thankful!
[Nexus 7 General] shawnbon206:
My apologies, flash-base.sh will only work on mac os or linux. This is why my second instruction set had more steps. You can also just open flash-base.sh in a text editor and read what it was supposed to do and do those steps in substitution.

Fastboot oem unlock command wont do anything if you're already unlocked, I put it in there to make the instructions generic. but no you don't need it if you're already unlocked.

You're welcome, thanks for reporting back that it worked! Any other corrections I need to make?
[Nexus 7 General] choybel:
It went well for me so I don't think there should be any more problems with others having similar cases. Once again thank you so much for the help!

...now for an off topic question, do you perhaps by chance know where I could find a tablet ui mod for this 4.3 stock ROM? The only one I could find so far is that of deodexed version.
[Nexus 7 General] shawnbon206:
Well, your stock rom would need to be deodexed first if i'm not mistaken, so you might as well just install the deodexed version. You can install that from recovery, without doing a factory reset, just clear your cache, and it will "update" your current installation. Do a nandroid backup first in case you hate the tabletUI or something goes wrong :)
[Nexus 7 General] choybel:
I know I'm going way off topic here, so please spare me this one more time. I have a few more questions.

1. Can i revert to odexed version after I flash to deodexed?

2. I just did a full backup on twrp before flashing the updated stock rom, so if I decide to make another backup when I flash to deodexed what will happen to my previous backup? Can I delete it or overwrite it with a new one?

3. Will my data remain after flashing to deodexed version?
[Nexus 7 General] shawnbon206:
well it's okay you're off topic because this thread is dead anyhow.

1. yes, just flash system and boot, and wipe cache. i'm not sure you even need to flash boot, but do anyways just in case.

2.your original backup will be dated. if you want to keep it you can rename the directory it's in and call it something memorable like "0901before_ota." then make a new backup and you can rename that one to "0903before_tabui." but you don't really need more than one, if you ever need to go back that far its almost always easier just to backup and start over from scratch. so in that case just delete the first one before you make another one (thats what I do)

3.yes as long as you don't do a factory reset, factory reset formats /data, /data is where your apps and settings are
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] matievan:
Hello xda-dev,

I'm having trouble finding somebody else with a similar situation as mine:

So I picked up my new I337 from Costco this week. While using it throughout the week, I was very unfortunate as to allow the MF3 update from ATT to successfully update on my device. (This is the part where I cry because I can't install GE or custom bootloaders)

While doing some more research, I finally used this method to get root access after which I got Titanium Backup to remove the stock ATT bloatware.

I then proceeded to carefully un-install about a dozen or so applications most of which were ATT garbage.

Now maybe I uninstalled something crucial, or maybe certain applications need the ATT bloatware to run correctly, but my problem now is that Music and S-Voice both crash moments after starting them, so I would like to re-install my OTA MF3 update.

I understand that I have no shot downgrading or installing custom boot loaders at the moment, but I know that the MF3 rom seems to be available here.

Is there any risk in me getting Odin and attempting to install the rom using down+home+power way? (Sorry don't know the name for this procedure yet.)

I have come to peace with being stuck on MF3, but at the same time I would like to regain full functionality of my S-Voice and Music.

How would I go about safely re-installing my OS?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Doymecca:
Using titanium backup, set both programs to be user apps, reboot, and switch back to system apps. Worked for me with Svoice, Smusic, and a few other programs. No more "Unfortunately xxxx has stopped" messages.

EDIT: This should be the link for the original thread about this problem.

http://xdaforums.com/showthread.php?t=2282959
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] matievan:
Thank you so much, Doymecca.

This works for me... to an extent. S-Voice will only continue to run if I keep it as a user app.

Still no luck with the Stock Music player.

Will check the other threat now for a solution regarding a complete OS wipe.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Doymecca:
Have you tried wiping your dalvik cache yet?

EDIT: Here us a thread about wiping dalvik

http://xdaforums.com/showthread.php?t=1752390
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] matievan:
I have tried wiping the "cache partition" as well as "wipe data/factory reset" from the stock recovery boot menu with no result.

Also I'm not sure, but I don't think I can wipe the Dalvik without a custom bootloader?? (Even after reading around, I don't understand the difference between Dalvik and what I have tried.)

EDIT: I really think, the reinstall would be my best option. I'm most curious to know if I'm at risk of bricking my device if I try to restore the MF3 rom from the earlier thread.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] HiTideBlastoise:
I could be wrong but I don't think you could flash that without a custom recovery.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Doymecca:
Apparently I cannot post outside links...

Google what is dalvik cache, also check out system tuner app in the play store, this app has a feature for wiping your dalvik cache along with a ton of other things.

I also would not risk a flash.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Just so its clear, you can NOT flash the rom in your link. Luckily, you won't be able to since you don't have a custom recovery. Trying to put a recovery on and flashing that rom could cause irreparable damage to your phone. You're mf3 and are severely limited to what you can do.

If you continue to mess with tibu, freeze the apps, don't delete them. That way if you mess something up you can get them back
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] mg2195:
You extract the contents of that ROM, and a manually add in the missing apps until your problem dissapears (will prob have to change permissions on each added app to "rw-r-r" and reboot for apps replaced apps to take effect)

That should work...and next time use titanium back up to actually back up, than freeze apps reboot see if there's any problems...if none than uninstall
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] matievan:
Thanks for the quick replies, everyone. I appreciate your help.

After much more research, I do see that there is no MF3 factory image available yet. I guess I wait til then.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Agent:
Just to add to their arguments, absolute no flashing with odin on the MF3. Period. You will definitely mess something up. I'm thinking you altered the system recovery by getting rid of some stuff. You are going to have to wait until the devs come out with something.
[myTouch 4G Q&A, Help & Troubleshooting] tonyMEGAphone:
the waiting game

At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.

Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.

WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.
[myTouch 4G Q&A, Help & Troubleshooting] tonyMEGAphone:
Funny stuff

Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.

I just don't want to use the CM ROM...

I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.

Hope this is a comedy for someone.
[myTouch 4G Q&A, Help & Troubleshooting] tonyMEGAphone:
only other link

I've found on the issue I have.

http://xdaforums.com/showthread.php?t=1148057
[myTouch 4G Q&A, Help & Troubleshooting] tonyMEGAphone:
Non-Stop ROMS

1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.

2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging

3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...

4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.

I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time

I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.

Oh here is another dead end I've found... http://xdaforums.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...