Hi guys,
Android version 4.2.2 via OTA has been released. For folks like me who have not yet got it and are impatient here you go-
1.Upgrade Nexus 7 to 4.2.1 first [necessary].
2.Get the zip for 4.2.2 here.
Download
3.Boot Nexus 7 into bootloader.
[Power button + center of both volume buttons/volume down]
4.Select Recovery using volume up/down buttons.
5.Press Power button.
6.Wait till you get an android with a red exclamation.
7.Press power + volume up or any other combination till you get a menu.
8.Select update from ADB.
9.Open the folder where the downloaded zip is in the computer.
10.Right click with shift pressed and select open command window here.
11.Type without quotes "adb sideload 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip"
12.The nexus will flash it.
13.When it is complete wipe cache and dalvik.
14.Reboot and enjoy.
15.Hit thanks.
If you really cant get it to work download 4.2.1 Stock Rom and extract system.img from the zip inside the .gz.
If it still gives an error flash the complete 4.2.1 stock rom.
what a long filename to type
bradputt said:
what a long filename to type
Click to expand...
Click to collapse
Sorry it was named by google.
U can rename it if you want
Is there a rooted version?
tenyrnote said:
Is there a rooted version?
Click to expand...
Click to collapse
Get any custom recovery CWM/TWRP and flash this
file.
:good:
Remember to just backup ur data first just in case.
I installed TWRP after the last update and now I can't seem to boot into it to flash 4.2.2. I hold the buttons and get into the boot menu, select recovery and ok, but then it gives message "No Command". Any ideas on how to get back to TWRP or reinstall TWRP to be able to flash?
Liquidretro said:
I installed TWRP after the last update and now I can't seem to boot into it to flash 4.2.2. I hold the buttons and get into the boot menu, select recovery and ok, but then it gives message "No Command". Any ideas on how to get back to TWRP or reinstall TWRP to be able to flash?
Click to expand...
Click to collapse
I am attaching the stock recovery for 4.2.1. You can flash it using "fastboot flash recovery recovery.img" after installing it upgrade to 4.2.2 and then reflash TWRP.
Or you can use the Nexus Root Toolkit to do it automatically.:good::good::good::good:
Thanks for this - I can't get past step 6. I can get to the android with the red exclamation but no matter what I do next I just get a black screen.
What am I doing wrong?
Here is another way:
Stock rom, rooted, cwm recovery, supersu, ota rootkeeper. I downloaded the update to my pc and copied it to the N7 internal memory. Booted into cwm recovery, chose to 'install zip from sdcard', 'choose zip from sdcard', '0/', (selected the update), update. After the update finished and I chose to restart and said 'Yes' to disable flashing stock recovery (thus keeping cwm), then said 'Yes' to restoring root. After bootup, and the upgrading android process, I have root and cwm recovery.
I don't think you get the options to disable flashing stock recovery and keeping root if you don't have ota rootkeeper and maybe supersu. Superuser may work the same. The update seems good and fast. I wasn't having any problems before, so I don't know exactly what changed. All in all the manual update worked out well for me.
Chimera2345 said:
Thanks for this - I can't get past step 6. I can get to the android with the red exclamation but no matter what I do next I just get a black screen.
What am I doing wrong?
Click to expand...
Click to collapse
The order is -
First press the power button and then the volume up button. If this does not work try volume down but remember power button first.
If all fails try the steps by Groid.
Once I get to the "red exclamation" it shows "no command", if I hold power then up it reboots into what I understand is APX mode (APX device shows up in device manager)? If I hold power then down it reboots back into recovery mode. I'm new to the Nexus 7/Android, the device is stock with 4.2.1.
bradputt said:
what a long filename to type
Click to expand...
Click to collapse
In windows you can start typing a filename and then hit tab and it will finish it, very handy.
Sent from my Nexus 7 using xda app-developers app
What about the updated bootloader? Is there a way to flash it? Thanks
Chimera2345 said:
Once I get to the "red exclamation" it shows "no command", if I hold power then up it reboots into what I understand is APX mode (APX device shows up in device manager)? If I hold power then down it reboots back into recovery mode. I'm new to the Nexus 7/Android, the device is stock with 4.2.1.
Click to expand...
Click to collapse
Got mine working, it was all down to timing on the power+up buttons. Flashed to 4.2.2 now, thanks for the help.
hi all
when i flash the zip file to upgrade to 4.2.2 i've got error7
assert failed: apply_path_check ("/system/vendor/lib/hw/power.grouper.so
i've tried to put the original file from the factory image but no working the permission i've set is rw-r-r what is wrong ?
my bootloader is on the 4.13 version
and using TWRP
tanks all
EDIT: i've found a tool to extract the file from factory image and chmod 755 and is okay
ok so this is a weird one.
i am stock 4.2.1, rooted, stock recovery and had Beats audio installer from the play store installed and that was it.
i found the script from the beats audio thread that removes the files and then i uninstalled.
then I unrooted, copied the new ZIP ffile over to my internal SD card and temp booted into TWRP and flashed it.
it came back and said assertion error
and the file it failed on is:
/system/lib/SR_AudioIn.SO
i was missing this file (not sure why)
went to my Nexus 4 and found that file and copied it into dropbox and then coped it into my system folder and set the proper permissions on it and rebooted.
tried to flash again and iot keeps failing on this file even though it is present and set properly.
is it possible this file is different for the N4 than the N7 and i need the N7 specific one?
I'm getting assert failed on /system/app/CalendarGoogle.apk.... any clues what to do?
dalanik said:
I'm getting assert failed on /system/app/CalendarGoogle.apk.... any clues what to do?
Click to expand...
Click to collapse
supposedly if it assert fails that means either its missing or its damaged/modified.
you would want to use Root Explorer if you are rooted and browse out to /system/app and see if it exists and if not then replace it, set permissions and reboot and try again to flash.
nextelbuddy said:
supposedly if it assert fails that means either its missing or its damaged/modified.
you would want to use Root Explorer if you are rooted and browse out to /system/app and see if it exists and if not then replace it, set permissions and reboot and try again to flash.
Click to expand...
Click to collapse
It exists. But how to get that specific APK? Download whole ROM and extract somehow? And where?
dalanik said:
It exists. But how to get that specific APK? Download whole ROM and extract somehow? And where?
Click to expand...
Click to collapse
if yours exists then i guess you are in the same boat as me where mine says another file doesn't pass yet it exists.
im waiting to find out what to do on that one as well.
if you have the entire stock rom then you would extract the contents of that rom and then extract just the file and push it to your device either with ADB or root explorer copy/paste.
Related
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
On Google Play, SuperSU is updated, currently version 1.44. When launching SuperSU, it will ask to update SU Binary, choose to update normally.
This should work with TWRP but I don't have it.
I hope this will help.
I want to do a fresh install using the factory images for 4.3 (bootloader, radio, recovery etc)
Once I do that, can I just reinstall CWM then SuperSu to root just like I did using 4.2?
ohhdavid said:
I want to do a fresh install using the factory images for 4.3 (bootloader, radio, recovery etc)
Once I do that, can I just reinstall CWM then SuperSu to root just like I did using 4.2?
Click to expand...
Click to collapse
just use the nexus4 tool kit and use the factory images. Simple and quick
jboogie3 said:
just use the nexus4 tool kit and use the factory images. Simple and quick
Click to expand...
Click to collapse
I'll look into it, however, I usually prefer to do as close to stock install as possible with bare minimum 3rd party modification which is why I usually install factory images and then flash Su through cwm
Sent from my Nexus 4
ohhdavid said:
I'll look into it, however, I usually prefer to do as close to stock install as possible with bare minimum 3rd party modification which is why I usually install factory images and then flash Su through cwm
Sent from my Nexus 4
Click to expand...
Click to collapse
the toolkit just fastboot flashes the images for you... thats complete stock. then you can flash a custom recovery, then install su.
Thanks to the OP :thumbup: works a treat
Sent from my Nexus 4 using xda app-developers app
Le_Zouave said:
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
This should work with TWRP but I don't have it.
I hope this will help.
Click to expand...
Click to collapse
Awesome thanks, will try this later.
does this method erase everything on your phone?
clusterchuck said:
does this method erase everything on your phone?
Click to expand...
Click to collapse
No, nothing is erased and it even keep the custom recovery.
The first part is what I used to update to 4.2.2 and keep root and custom recovery. But with 4.3 update, root method seems to have changed, that's why I wrote this post.
Le_Zouave said:
If you have a stock 4.2.2 with root and clockwork mod recovery, it can be updated to 4.3, you will keep CWM recovery but lose root so here's what I did.
You need :
- Nexus 4
- 4.2.2 firmware (JDQ39)
- root with superSU
- Clockwork Mod Recovery
Download update JWR66V from JDQ39
Copy the zip file in the folder of your choice.
Shut down the Nexus 4
Boot into CWM Recovery : hold Volume Down and press Power, in the menu with the green "Start" choose "Recovery mode" with the volume and select with power, it will reboot in CWM Recovery
Then in CWM Recovery :
- Install Zip
- Choose zip from sdcard
- 0/
- go in the folder you copied the update and select it
- select Yes and wait
- go back and reboot
- on reboot it will ask to keep recovery and root, say Yes both. But saying no to keep root won't keep root...
So after a long reboot, the Nexus 4 is updated to 4.3, CWM recovery still here but no root binary.
Download the file on this link from SuperSU creator : Chainfire.
Flash it the same way as the update but when it will ask for keeping recovery, say No.
After reboot, you now have a Nexus 4 with 4.3 (JWR66V), root and CWM recovery.
This should work with TWRP but I don't have it.
I hope this will help.
Click to expand...
Click to collapse
There's a new su zip v1.43 it had just been released
From my BLACKED OUT N4
i got an error when attempting to install in cwm, something regarding a no file_context.
edit: it says error /sdcard/0/ ebc... (status 7)
Worked fine for me
Thanks! This worked perfectly for me. Haven't run into any trouble yet.
I missed "Flash it the same way as the update but when it will ask for keeping recovery, say No" before, now it works fine on my N4
Works fine on TWRP. Updater asks if we want to save root. I said, No. Nothing is asked or said about recovery but recovery (TWRP) is retained. After the update, I went back to recovery and flashed the recent 1.43 update from Chainfire. All went well. Soon thereafter, I was notified that SuperSU is now at version 1.44.
Everything is smooth so far.... One app that works with root is goofy now, but other than that, all is well.
Can someone tell me if using the first part of my method to keep the recovery (so not flashing Chainfire file) and updating to SuperSU 1.44 on google play is enough to get back root?
In my case I updated to SuperSU 1.44 and when I launched it, that asked me to update SU binary and choose between normal or CWM/TRWP method, I choose normal and it worked.
clusterchuck, I get that error too but it didn't blocked and all went fine. Is it a blocking error?
Le_Zouave said:
Can someone tell me if using the first part of my method to keep the recovery (so not flashing Chainfire file) and updating to SuperSU 1.44 on google play is enough to get back root?
In my case I updated to SuperSU 1.44 and when I launched it, that asked me to update SU binary and choose between normal or CWM/TRWP method, I choose normal and it worked.
clusterchuck, I get that error too but it didn't blocked and all went fine. Is it a blocking error?
Click to expand...
Click to collapse
as far as the "no context", i dont think its a blocking error, because once I got the update working, it still has that error message on there. But it turned out my problem was that I deleted some google apps (google plus, earth, etc), and i had completely forget about that. So i ended up having to flash the stock 4.2.2 again then installing 4.3 for it to all go smoothly.
Great , thanks for the post, I will check that this weekend.
Update error
I did some previous flashing with Google Edition camera apk's and whatnot but I believe I should have the stock camera/GoogleGallery.apk.
I perform the steps and it gives me a Status 7 error, with "GoogleGallery.apk" somewhere in there. So I flash the stock 4.2.2 google apps and try again, this time it gives me a BrowserProviderProxy.apk error, Status 7 as well.
Any help on this?
Perhaps your system apps have been modified before or your kernel have been flashed before. Safest method will be to use fastboot to upgrade.
clusterchuck said:
i got an error when attempting to install in cwm, something regarding a no file_context.
edit: it says error /sdcard/0/ ebc... (status 7)
Click to expand...
Click to collapse
Is it also working when coming from a custom kernel (e.g. franco)?
If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05
twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.
Yeah, they are pretty good about that. It may be nearing the last update for this version, though
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly
twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.
KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated
twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat
Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!
Did you do this with update 99 yet? Just came out today.
GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Hi, first of all, did you installed the recovery with: fastboot flash recovery recovery.img right??
If you did so, you just need to turn off your phone, hold volume up button and power button and wait until it enters to recovery mode. From there you can flash a new ROM if you have it on your SD card or internal storage.
sliker90 said:
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Click to expand...
Click to collapse
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
thanks to both of you guys!! i've solved with the solution in the second post, just deleting the "install-recovery.sh" script, i was going crazy!! i hope this post will help someone else!
PS: i don't understand why they do not put these solutions in the first posts in important threads like that one i've linked....
devilsking said:
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
Click to expand...
Click to collapse
I thought mythtools removed the .sh file by itself?
jaweinre said:
I thought mythtools removed the .sh file by itself?
Click to expand...
Click to collapse
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
devilsking said:
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
Click to expand...
Click to collapse
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
skeevydude said:
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
Click to expand...
Click to collapse
We are 2, never had problems
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
broken url
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.
Thank You it worked!
Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk
Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.
orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??
cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.
rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.
cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.
Is this working with
H960a
V20a-AME-xx??
1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka
asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.
Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.
i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft
my main reason for getting a pixel phone is so I could always be on the latest version of Android for security reasons. I know that OTA updates will not work as seamlessly when I'm rooted.
My question is, how can I update my phone while being rooted, and not losing any of my user data and media?
EDIT: Answer
How to sideload OTA and keep your user data/media!
download OTA image from
https://developers.google.com/android/ota
adb reboot recovery
The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
To enter sideload mode, select the option Apply update from ADB.
adb devices
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Assuming all goes well, it’ll soon run through “Installing update…” and 2 steps. If you grabbed the correct file for your phone, it should complete and finish properly by saying “Install from ADB completed with status 0.” This message will ONLY appear on your phone. On ADB, it will say "(~94%) adb: failed to read command: No error" This is normal!
reboot back into system to finalize update.
Re-Root
adb reboot fastboot
fastboot flash boot magisk_patched.img
xT29c said:
my main reason for getting a pixel phone is so I could always be on the latest version of Android for security reasons. I know that OTA updates will not work as seamlessly when I'm rooted.
My question is, how can I update my phone while being rooted, and not losing any of my user data and media?
Click to expand...
Click to collapse
Don't take my advice.
But, from the steps I was told to perform was :
From within magisk manager, restore images. Not complete uninstall. Afterwards, Don't reboot. Then, head over to the update section of settings and update. Then , pretty sure , install magisk again. Then, reboot.
When you say reinstall magisk again? Are you talking about the APK file or flashing the patched boot.image file?
when I go to the update section, it's not finding the November OTA that was just pushed out today. Am I able to side load the update with ADB and still retain all user data?
Did it myself. Here's my guide. Enjoy.
How to sideload OTA and keep your user data/media!
download OTA image from
https://developers.google.com/android/ota
adb reboot recovery
The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
To enter sideload mode, select the option Apply update from ADB.
adb devices
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Assuming all goes well, it’ll soon run through “Installing update…” and 2 steps. If you grabbed the correct file for your phone, it should complete and finish properly by saying “Install from ADB completed with status 0.” This message will ONLY appear on your phone. On ADB, it will say "(~94%) adb: failed to read command: No error" This is normal!
reboot back into system to finalize update.
Re-Root
adb reboot fastboot
fastboot flash boot magisk_patched.img
xT29c said:
Did it myself. Here's my guide. Enjoy.
How to sideload OTA and keep your user data/media!
download OTA image from
https://developers.google.com/android/ota
adb reboot recovery
The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
To access the recovery menu, hold the Power button and press Volume Up once. The recovery text menu will appear.
To enter sideload mode, select the option Apply update from ADB.
adb devices
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Assuming all goes well, it’ll soon run through “Installing update…” and 2 steps. If you grabbed the correct file for your phone, it should complete and finish properly by saying “Install from ADB completed with status 0.” This message will ONLY appear on your phone. On ADB, it will say "(~94%) adb: failed to read command: No error" This is normal!
reboot back into system to finalize update.
Re-Root
adb reboot fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Hi, thanks for the guide! When re-rooting, which image should I choose to patch in magisk? The old one, or the OTA image (is that a full image)?
Michael1200 said:
Hi, thanks for the guide! When re-rooting, which image should I choose to patch in magisk? The old one, or the OTA image (is that a full image)?
Click to expand...
Click to collapse
I used the old one. I believe the OTA does not change the boot.img file, since it isn't included in the download. If it did change it, I'm sure I would have semi-bricked my phone. lol.
xT29c said:
I used the old one. I believe the OTA does not change the boot.img file, since it isn't included in the download. If it did change it, I'm sure I would have semi-bricked my phone. lol.
Click to expand...
Click to collapse
Thanks, so basically re-rooting is the exact same procedure as rooting it the first time, right?
Michael1200 said:
Thanks, so basically re-rooting is the exact same procedure as rooting it the first time, right?
Click to expand...
Click to collapse
That's exactly right.
Never use OTA. I prefer use the full image for update without data loss. Little more commandes to type but it's better for me
nico22320 said:
Never use OTA. I prefer use the full image for update without data loss. Little more commandes to type but it's better for me
Click to expand...
Click to collapse
Please explain to yourself
xT29c said:
Please explain to yourself
Click to expand...
Click to collapse
look here https://www.youtube.com/watch?v=fYib1WNr2I8&t=32s
i always use this channel for my update. it's simple.
nico22320 said:
look here
&t=32s
i always use this channel for my update. it's simple.
Click to expand...
Click to collapse
No. I would like to know why you go through the trouble of flashing the entire factory image versus just the OTA file instead?
I do not know. since i got nexus 5, i've always learned how to update like this. moreover all the posts that I looked on the internet say that there is more risk to flash the OTA file than the factory image so..
That's it ?