Google just came out with a new update (JRO03D). Using the following method, you can apply it to your Nexus 7 and keep CWM and root.
Pre-requisites: Stock JRO03C Build. CWM Recovery. Root. NO CUSTOM ROMS. NO CUSTOM BUILD.PROP.
Step #1 - Backup your su app (root) with Voodoo OTA Rootkeeper.
Step #2 - Download http://core.routed.com/update.zip and put it in your /sdcard
Step #3 - Install update.zip via CWM.
Step #4 - Reboot tablet, and restore root via Voodoo.
Step #5 - Enjoy latest Google update!
My earlier version tried to keep the 'su' file suid-exec root, but that seemed to have caused failures for people, so I took that part out. I'll look into why in the morning. But for now, the above steps do work fine.
IF YOU TRIED MY EARLIER VERSION AND IT FAILED AT THE UPDATING OF PERMISSIONS, BACKUP ROOT AND INSTALL THIS FILE: http://core.routed.com/fix.zip
Thanks.
I think I should point out that this would probably not be a good idea to flash if you are using a custom ROM, since it's a bunch of patch files to the various applications on the device, which might differ depending on the ROM you are using. It should only be used on the stock ROM (outside of custom recovery and/or root).
It didn't work for me, and it aborted. Now my WiFi doesn't work and I dong know hot to fix it. I'll try in the morning.
Sent from my Galaxy Nexus using xda app-developers app
ridiculousnicholas said:
It didn't work for me, and it aborted. Now my WiFi doesn't work and I dong know hot to fix it. I'll try in the morning.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Where did it fail? I installed it on mine (prior to posting this) and it worked perfectly. If it failed at the very beginning, you probably had validation enabled. Try disabling it and reapplying the update.
ALSO, make sure you had already applied the first update! The one that should have popped up when you first powered the device on. The above update I made is for the SECOND one, not the first. ie: JRO03C -> JRO03D. If yours is not the former, do not apply this, as the patching could fail.
I do not know. Do you think its because I have a custom kernel?
Sent from my Galaxy Nexus using xda app-developers app
ridiculousnicholas said:
I do not know. Do you think its because I have a custom kernel?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Possibly, but I don't think so. This doesn't change the kernel, only update a bunch of system apks, libraries and a few other files. Do you remember how far it got before it failed? It should have given a step-by-step update in the CWM logs:
ui_print("Verifying current system...");
ui_print("Removing unneeded files...");
ui_print("Patching system files...");
ui_print("Unpacking new files...");
ui_print("NOT Unpacking new recovery...");
ui_print("Symlinks and permissions...");
ui_print("Patching remaining system files...");
Click to expand...
Click to collapse
Also, check your "About" page to see what build you are currently on.
There's been about 30 people who have downloaded this so far. Any other feedback?
The symlinks I believe and I am on jrO03c
Sent from my Galaxy Nexus using xda app-developers app
ridiculousnicholas said:
The symlinks I believe and I am on jrO03c
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Did you have root before the update? How about after?
ridiculousnicholas said:
The symlinks I believe and I am on jrO03c
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Ok, I figured out the problem. Here is the fix for you:
First, make a backup of your root. Use Voodoo OTA Rootkeeper.
Then, apply this via CWM:
http://core.routed.com/fix.zip
That will fix your permissions and wifi should work now. I'm going to update the OP now .
phonic said:
Ok, I figured out the problem. Here is the fix for you:
First, make a backup of your root. Use Voodoo OTA Rootkeeper.
Then, apply this via CWM:
http://core.routed.com/fix.zip
That will fix your permissions and wifi should work now. I'm going to update the OP now .
Click to expand...
Click to collapse
Hey guys, I'm about to go through rooting my Nexus 7. Its my first root, hell this is my first android tablet. What changes should i make, if any, based on the info in this thread, to the "How to Root Your Nexus 7 For idiots who have never Rooted anything before and have never owned a Android device before July 13th and want to be sure they do it properly without screwing anything up and keeping their files intact Guide 2.0" that i am hoping to find somewhere on this site (feel free to give suggestions for this as well but im pretty sure i saw a good thread). Ive already updated to the second 4.1.1 update today. thanks
Thanks for the files and easy instructions. :good:
Just a note if you modified your build.prop to enable the table UI you must restore your original for this to work.
The first time I tried it failed due to the build.prop differences. I quickly restored my original and reapplied with no issues.
TerryNova said:
Thanks for the files and easy instructions. :good:
Just a note if you modified your build.prop to enable the table UI you must restore your original for this to work.
The first time I tried it failed due to the build.prop differences. I quickly restored my original and reapplied with no issues.
Click to expand...
Click to collapse
Thanks for the update, and glad it worked!
btw, I did mention the "no custom build.prop" in my pre-requisite list
Related
Noob here. I've searched the forums and have tried to piece together what I need to know for what I would like to do. I think I have a general understanding, but was hoping someone could verify or clarify.
I've got a Nexus 1 running 2.3.3. Never been rooted. All OTA updates.
What I would like is to root it so that I can delete crap like Facebook and Amazon and make room on the built-in memory. I don't want to unlock the boot-loader, and I don't want to flash custom ROMs. I do want control of what is stored where, the ability to move things to SD (even if they aren't marked for that (and yes, aware that that can cause problems sometimes)), and the ability to run Titanium backup.
As I understand it, all of that can be done with just root permission. But it seems that simple root for the N1 under 2.3.3 isn't available. Can anyone comment?
Thanks,
DT
Depends what you call simple...
Since you don't want to unlock the bootloader, you can try using the passimg method to revert to an earlier build of android, and then use any "simple root" available.
Unfortunately, a small percentage of users don't seem to be able to use the passimg method, and if you get an "main version is older" error, then it means you are among them...
Passimg method can be found in the wiki, under the unroot/restore guide (passimg method, using FRG33):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA Premium App
Good luck rooting, without trying to unlock the bootloader. It's simply not available atm I belive. Any particular reason you don't want to unlock the bootloader, beside the warranty?
root without unlocking bootloader
I'm still coming up to speed on this, so it's quite possible that I don't understand all the subtleties.
What I want to do is uninstall space-wasting preinstalled junk, and to run Titanium backup. I'm not interested (for now) in custom ROMs. I think I want to avoid unlocking the bootloader both for the warranty (a minor issue), convenience (another minor issue that could be overcome...), and because I want to retain as much of a "stock" device as possible, mostly to allow for future OTA updates. From what I've read, it sounds like a root would accomplish all that. Hence I'd rather avoid all the additional complications if a simple root were in fact available.
Thanks for the help,
DT
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Sent from my Nexus One using XDA Premium App
efrant said:
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Click to expand...
Click to collapse
Totally agree. If you check the threads that were active during the OTA onslaught, many people could not install stock Gingerbread due to removing stock system apps (Facebook, Amazon, Twitter, etc...)
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
danger-rat said:
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Thanks for the info. I hadn't thought about the OTA being affected by removal of unwanted programs.
DT
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
efrant said:
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Click to expand...
Click to collapse
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
danger-rat said:
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I was just asking if anyone has done this (or does this), as I would certainly love to remove apps, as long as I can install future updates as they become available. (Doing that is beyond my knowledge...) I like my stock ROM, and I would certainly remove certain apps if I know someone would provide a "modified" update.zip for a stock ROM that doesn't check if Amazon, etc are installed.
What I don't want is to flash a new ROM every time an update came out...
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Restoring a NAND backup is essentially the same thing as flashing a new ROM, which is what I don't want to be doing. What would be good is to be able to install a modified/repacked/whatever-you-want-to-call-it OTA update file that has the check (which checks to see if apps are installed) disabled.
If it is just a line in a script that needs to be removed in an OTA, so that it will flash (with a custom recovery of course) with Amazon removed, it is surely doable, no? If it is doable, I am surprised that no one has done it for any of the updates... (at least I haven't seen any).
albundy2010 said:
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, but my question was: is it possible to modify an OTA zip file in such a way that it disables checking for installed apps like Amazon?
This would be helpful, and I had never thought of it until danger-rat mentioned it, but I may have misunderstood his post - he was probably talking about just flashing a new ROM, but that is not what I am interested in.
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
That sounds like a good idea.
This is what I'd like to do as a test:
1) Restore a stock Froyo ROM
2) Remove the Amazon.apk (and possibly others) from my ROM and save it somewhere (and whatever other files would be needed).
3) Create an update.zip file that would place the Amazon.apk file back to the correct directory in a stock ROM (i.e., odexed).
4) Flash that update.zip
5) Flash the Gingerbread OTA and see if it works.
Would you be able to point me to a guide on how to create a flashable zip? Again, I would need to be able to do this for an odexed ROM.
Thanks.
EDIT: Nevermind. I found it here: http://www.londatiga.net/it/how-to-create-android-update-zip-package/
ameedi600 said:
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I agree this is what I did had no problems at all
POST REMOVED.
I'd like to apologize for posting this update which had previously been available to soak test members and not in wide release. The file was not altered in any way or distributed with any intent of causing harm to Motorola or Verizon.
It was a bad judgment call in posting it for others to use. I was excited at the prospect of bug fixes and feature improvements to what is an otherwise fantastic phone.
That is all. Nothing to see here. Move along.
so have you flashed it?
Does it fix any of the known issues like camera app and so forth
So what exactly is this? A leaked OTA essentially?
So after looking through this file, I placed it on my sdcard, and patched through recovery (power + x).
I was basically reset to stock:
- De-rooted
- Made sure I had all my bloatware back
- Wiped user/cache (this was probably unnecessary but i was all messed up from doing the OTA hacking anyway)
The patch has fixes for many items:
- BP upgrade for the Radio
- Talk2 for Video
- Boot.img patch
- Recovery.img patch
- Various patches to alot of system files
- And some stupid bloatware patches as well.
User's beware if you also want to patch this file. Be sure to be as close to stock as you can get.
scottml said:
So after looking through this file, I placed it on my sdcard, and patched through recovery (power + x).
I was basically reset to stock:
- De-rooted
- Made sure I had all my bloatware back
- Wiped user/cache (this was probably unnecessary but i was all messed up from doing the OTA hacking anyway)
The patch has fixes for many items:
- BP upgrade for the Radio
- Talk2 for Video
- Boot.img patch
- Recovery.img patch
- Various patches to alot of system files
- And some stupid bloatware patches as well.
User's beware if you also want to patch this file. Be sure to be as close to stock as you can get.
Click to expand...
Click to collapse
Were you able to re-root after flashing?
Sent from my DROID3 using XDA App
scottml said:
So after looking through this file, I placed it on my sdcard, and patched through recovery (power + x).
I was basically reset to stock:
- De-rooted
- Made sure I had all my bloatware back
- Wiped user/cache (this was probably unnecessary but i was all messed up from doing the OTA hacking anyway)
The patch has fixes for many items:
- BP upgrade for the Radio
- Talk2 for Video
- Boot.img patch
- Recovery.img patch
- Various patches to alot of system files
- And some stupid bloatware patches as well.
User's beware if you also want to patch this file. Be sure to be as close to stock as you can get.
Click to expand...
Click to collapse
This sounds like the OTA that is being pushed to D3 owners that are in Motorola's soak group. Radio fixes and whatnot for battery life purposes. I could be wrong though.
buckmarble said:
Were you able to re-root after flashing?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
this is the real question that matters atm until we have a custom recovery.
buckmarble said:
Were you able to re-root after flashing?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Million dollar question. I want the updated gtalk when I get my replacement D3 tomorrow. I'll be completely stock so I'll be good to go on this as long as the same root exploit exists. I can't imagine they had time to remove it though.
You can re-root using the same exploit.
Androidsims said:
Million dollar question. I want the updated gtalk when I get my replacement D3 tomorrow. I'll be completely stock so I'll be good to go on this as long as the same root exploit exists. I can't imagine they had time to remove it though.
Click to expand...
Click to collapse
Done lol, I just took the apk out of the update and installed right over the existing. You also need the libtalk_jni.so from there and out it in the syste/lib folder and you are all set new gtalk with video
So I have another question, if all that is modified is that fact that it has been rooted, what is wrong with flashing this while rooted? Wont it just unroot us at worse and we will have to reroot? Just trying to understand.
Sent from my DROID3 using XDA App
Has anyone tried flashing this while rooted? With no other mods.
Sent from my DROID3 using XDA App
buckmarble said:
Has anyone tried flashing this while rooted? With no other mods.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Just did. You will need to reroot.
Will this fix a softbrick if you can get into recovery? Any thoughts?
I would imagine the update would fail. If you modified the phone to the point of bricking, I doubt the update would run.
Works great. Already seems faster. Battery reports less for cell standby and phone idle. Either the reporting is better or they fixed the issue.
Sent from my DROID3 using Tapatalk
buckmarble said:
Has anyone tried flashing this while rooted? With no other mods.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I've been trying for a while to get this flashed. Even went so far as to reinstall bloat that I had deleted before to see if that would work and it's giving me the same error every time.
I have some really good news, I soft bricked my phone a little while ago because I was an idiot with deleting my apps. I needed my phone and was going to activate the insurance and pay the deductible when I figured I might as well try this. I wiped the cache and data and applied this through the recovery mode and My phone is fully operational now. I can access my contacts, texts, setup accounts and not one force close yet. Now for disclosure I am probably very lucky this worked for me, try at your own risk. I am way to scared to try and delete apps again until I get a proper backup or I see enough people try it themselves with no issues. But to OP... Thank you very much you just saved me $100
edit: Found one glitch, dont know if its my specific phone or not. But if wifi is on and you receive an e-mail the notification light will not go on, if wifi is off it will... Very minor bug though.
So won't this update be available automatically? How does it work with motorola?
So I must be an idiot or something. I put the file on the root of the sd card and then booted into recovery. It gave me an error. Said can not mount sdcard file or directory doesn't exist.
Sent from my DROID3 using XDA App
First connect to WiFi and make sure you can access the web.
Next put the N4 into airplane mode.
Then go to Settings > Apps > All > Google Services Framework > Clear data
Take the N4 out of airplane mode and let it connect to WiFi.
After a few minutes, you will be prompted to install the OTA update.
If you are not prompted within 10 minutes, open the dialer and force a "checkin" by typing: *#*#2432546#*#*
After "checkin succeded" message, you should be prompted to install the update.
Enjoy!
Doesn't work for me.
Sent from my Nexus 4 using Tapatalk 2
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
albundy2010 said:
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
Click to expand...
Click to collapse
http://www.androidpolice.com/2012/11/27/manual-download-android-4-2-1-update-jop40d-for-the-nexus-4/
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
bline007 said:
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
"Easy" is a relative term. Not everyone here, especially in the "General" forum is comfortable yet with flashing alternative recoveries or using abd, etc. This is meant for the novice and/or purist who does not want to alter the phone in order to receive and apply the update. This method does in fact work. Quite often the device is ready to receive the update, but the built in automatic & manual checkin fails to trigger the process. Clearing the GSF data forces the device to initiate it almost immediately, as opposed to waiting an undetermined amount of time for the device to resolve the issue on its own.
My advice to the audience who this is intended for: If this did not work for you now, try it again in a few hours or tomorrow, I assure you it will be much faster than waiting for it to happen naturally. In fact, to prove my point further, go ahead and try the manual checkin (under settings > about phone > system updates) first, each time, before you try this. You'll eventually see what I mean. FYI - Every Nexus device has behaved this way.
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Girn said:
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you changed your build.prop it will fail. U need to have stock build.prop.
I see your point skillllz
Sent from my Nexus 4 using xda premium
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Girn said:
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try wiping cache and dalvik then flash. It worked first time for me. Some custom Roms change build prop. I'm on stock rom
Sent from my Nexus 4 using xda premium
Thanks! Worked perfectly (on 1st try) to get 4.2.0 on my Galaxy Nexus finally.
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Worked here. Thanks.
Sent from my Nexus 4 using xda app-developers app
Girn said:
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That means you removed genie widget.odex . put the file back or any other that you deleted and it will go through. I deleted currents, books, earth, genie, videos and a few more and it failed on the update and its because you have to have the same build prop or same apps back
Sent from my Nexus 4
worked a charm for me! thanks
Don't work for me
Worked. Thanks.
Sent from my Nexus 4 using xda app-developers app
You only need to clear data of google services framework, then check for updates. Rinse and repeat until it works - usually 1-5 times.
All those other steps aren't necessary.
bline007 said:
If you changed your build.prop it will fail. U need to have stock build.prop.
Click to expand...
Click to collapse
For those who have altered build.prop, any way to fix beside completely going back to the original Google ROM img?
Worked for me thanks.
As I have CWM, CWM asked if I want to flash untrusted update - I said yes. After isntall, I rebooted back to Recovery (as it said something about restoring stock recovery while installing update). CWM was still there. I told CWM to reboot and it said 'you may have lost root'. I selected yes to fix root and it rebooted. all seems fine now.
Worked nicely!! Thanks
keep in mind before anyone updates to the official jb. i suspect the official release will be patched to not allow us to return to ics. if you keep root after the update good but if you some how break root there might no be a way to get it back as of now! so be cautious before you accept update. we should at least wait for an official jb fxz if you plan on keepng root this way if you mess something up at least you will have a working phone back without root of course. again i dont know they will patch the official release to prevent downgrade but lets find out for sure to be on the safe side. i dont think were gonna get dan to make us a jb root method right away soon.....
It could be considering its small size. Those who have updated to JB OTA should install safestrap and make a backup.
cmvienneau said:
keep in mind before anyone updates to the official jb. i suspect the official release will be patched to not allow us to return to ics. if you keep root after the update good but if you some how break root there might no be a way to get it back as of now! so be cautious before you accept update. we should at least wait for an official jb fxz if you plan on keepng root this way if you mess something up at least you will have a working phone back without root of course. again i dont know they will patch the official release to prevent downgrade but lets find out for sure to be on the safe side. i dont think were gonna get dan to make us a jb root method right away soon.....
Click to expand...
Click to collapse
This exactly what that was, I am no longer able to downgrade to 4.0.4 using the Atrix Utility. No biggie for me though, I'm rooted with SS3, and I have backups!
Sent from my MB886 using xda app-developers app
I tried to apply update on jb leak no go... Just a heads up. Still have root. On leak.
Sent from my MB886
I'll try Flashing through Motorola online hope it works
Sent from my MB886 using xda app-developers app
huatz84 said:
It could be considering its small size. Those who have updated to JB OTA should install safestrap and make a backup.
Click to expand...
Click to collapse
That's not the official one... A leak update for a leak update is not the official OTA. The official package (if for some reason it is 98.4.20) will be the size of at least the 2 leak update.zips together. It is not a 10 MB change from ICS to JB. It's a 10 MB change from JB leak to JB leak.
mattlgroff said:
That's not the official one... A leak update for a leak update is not the official OTA. The official package (if for some reason it is 98.4.20) will be the size of at least the 2 leak update.zips together. It is not a 10 MB change from ICS to JB. It's a 10 MB change from JB leak to JB leak.
Click to expand...
Click to collapse
Yeah..this ota is just a minor update over the leak. I think I should change my siggy after all..
Sent from my MB860 using Tapatalk 2
Hello friends!
I've got AT&T Atrix HD with JB leak installed, with uncomplete root (root is present but any app cannot access root!), and yesterday I've received software update (98.4.20.en.US).
Tell me please - can I flash back to ICS, or somehow in another way gain root access??
Ramonsterator said:
Hello friends!
I've got AT&T Atrix HD with JB leak installed, with uncomplete root (root is present but any app cannot access root!), and yesterday I've received software update (98.4.20.en.US).
Tell me please - can I flash back to ICS, or somehow in another way gain root access??
Click to expand...
Click to collapse
I haven't tried going back to ics. But,I believe this ota block us going back. I think someone at Moto seeing what we've done here.
Sent from my MB886 using Tapatalk 2
huatz84 said:
I haven't tried going back to ics. But,I believe this ota block us going back. I think someone at Moto seeing what we've done here.
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
I can confirm that this OTA does block you from going back too ICS. Lucky for me, I have backups, and i kept root, so I can go back by restoring one of my backups. But I think this leak OTA is pretty good, so I'm not to upset.
Sent from my MB886 using xda app-developers app
PeteSeiler2010 said:
I can confirm that this OTA does block you from going back too ICS. Lucky for me, I have backups, and i kept root, so I can go back by restoring one of my backups. But I think this leak OTA is pretty good, so I'm not to upset.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Just sent you a PM
I second PeteSeiler2010's confirmation. I installed this update and tried going back to ICS with both RSD Lite and the Atrix utility.Neither worked. Luckily though, I too had made a backup with SS3 and was able to revert back and get root again.
Nate3D said:
I second PeteSeiler2010's confirmation. I installed this update and tried going back to ICS with both RSD Lite and the Atrix utility.Neither worked. Luckily though, I too had made a backup with SS3 and was able to revert back and get root again.
Click to expand...
Click to collapse
Unfortunately, I do not have any ICS backups for my phone, I must have named a JB backup as and ICS thats all I can think of...anyway, I too and hoping someone can upload an ICS backup somewhere so I too have the ability to go back to ICS if need be. Sorry for the false hope!
If any one has a backup off ICS, I would be happy to upload it my dropbox site so we all would have that to fall back on.
Sent from my SGH-I897 using xda app-developers app
PeteSeiler2010 said:
If any one has a backup off ICS, I would be happy to upload it my dropbox site so we all would have that to fall back on.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Just to clarify for Pete.
We don't want your information stored on your phone.
1) Restore back to ICS using the "restore function" in SS3/TWRP
2) Do a Factory Data Reset in settings.... privacy..... Factory Data Reset (this will wipe all personal info from the phone).
3) After you've done a Factory Data Reset, do a backup in SS3/TWRP.
4) Zip up the folder that has the backup you just performed, and upload it to a file server somewhere.
5) Post the link in this thread.
6) Be a Hero!
ATGAdmin said:
Just to clarify for Pete.
We don't want your information stored on your phone.
1) Restore back to ICS using the "restore function" in SS3/TWRP
2) Do a Factory Data Reset in settings.... privacy..... Factory Data Reset (this will wipe all personal info from the phone).
3) After you've done a Factory Data Reset, do a backup in SS3/TWRP.
4) Zip up the folder that has the backup you just performed, and upload it to a file server somewhere.
5) Post the link in this thread.
6) Be a Hero!
Click to expand...
Click to collapse
Yeah, thanks ATGAdmin for clarifying...we don't want your information, just the clean, wiped ICS backup. If anyone has one they would like to share to help bail a few of us out, it would be most excellent!
Has anyone JUST flashed the ICS system.img.ext4 and boot.img manually, wiped data, and attempted to boot?
mattlgroff said:
Has anyone JUST flashed the ICS system.img.ext4 and boot.img manually, wiped data, and attempted to boot?
Click to expand...
Click to collapse
You mean flash them through Fastboot?
Sent from my SGH-I897 using xda app-developers app
PeteSeiler2010 said:
You mean flash them through Fastboot?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Yes.
Code:
fastboot flash system system.img.ext4
fastboot flash boot boot.img
mattlgroff said:
Yes.
Code:
fastboot flash system system.img.ext4
fastboot flash boot boot.img
Click to expand...
Click to collapse
I'm at work for 3 more hours, so maybe someone else can try it. If not, I will when I get home.
Sent from my SGH-I897 using xda app-developers app
OTA [UNTESTED] [NAKASI-wifi only!]
NO GUARANTEE IF IT WILL WORK BUT NO HARM IN CHECKING THE FILES!:laugh::victory:
I WILL NOT BE RESPONSIBLE IF IT BRICKS YOUR DEVICE!!!
One Person reports it to be working.... thats good news
http://android.clients.google.com/p....signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip
LINK CREDITS-StannyG
Downloading. Wish me luck
CheCorchete said:
Downloading. Wish me luck
Click to expand...
Click to collapse
Best of Luck!! Be Really careful!! IT may not work~!
CheCorchete said:
Downloading. Wish me luck
Click to expand...
Click to collapse
How was your luck??
Seems like my pc is missing a driver, lol. But android police make a wonderfull guide with link to the ota http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
It works, got the link this am from the original post, rebooted in cmw, flashed it, over my stock rooted nexus 7. At first lost root, but found a beta of superuser flashed that with cwm and all of back to normal. Now I am running 4.3 rooted stock Rom...
Sent from my Nexus 7 using XDA Premium HD app
mk69 said:
It works, got the link this am from the original post, rebooted in cmw, flashed it, over my stock rooted nexus 7. At first lost root, but found a beta of superuser flashed that with cwm and all of back to normal. Now I am running 4.3 rooted stock Rom...
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I try to flash the zip through cwm and keep getting an error...
assert failed: apply_patch_check
instalation aborted...status 7 ...
E: error in (filename.zip)
anyone knows what´s going on? already downloaded the zip many times
i´m on stock rooted 4.2.2 LOCKED bootloader (motochopper root method)...maybe something about the bootloader?
mtdelnero said:
I try to flash the zip through cwm and keep getting an error...
assert failed: apply_patch_check
instalation aborted...status 7 ...
E: error in (filename.zip)
anyone knows what´s going on? already downloaded the zip many times
i´m on stock rooted 4.2.2 LOCKED bootloader (motochopper root method)...maybe something about the bootloader?
Click to expand...
Click to collapse
I used nrt to root my n7, I am not sure about the method you used. Also if you changed any build prop parameters, or any stock system apps, you must revert back to the original files before this ota update will work. The update will check your n7 to see if there were any mods to the original stock files. If you can't revert back to know what was changed then you may have to do a full flash of 4.2.2 then flash the update...
Try to write down the error message when you try to flash the update, that may give you some clues...
Sent from my Nexus 7 using XDA Premium HD app