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)?
Related
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.
Instructions for obtaining the rights to the .244. This method seems to work for many and has been confirmed over at a private forum.
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash this Recovery to your device.
4. Download the System only Rom and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded System only Rom file and flash it in CWM recovery.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
thanks for the info.
can you please put screen shot tutorials or video tutorials for this?
i'm newbie @ flashing and rooting.
don't know where can i find recovery for xperia zr.
akash4357 said:
Instructions for obtaining the rights to the .244. This method seems to work for many and has been confirmed over at a private forum.
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash Recovery.
4. Download and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded file.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
Click to expand...
Click to collapse
So are you now using this rooted 4.2.2? No more bootloop?
I haven't tried it yet as I'm out right now. But people at the other forum say that it's working and they have root access.
Sent from my C5503 using Tapatalk 2
akash4357 said:
I haven't tried it yet as I'm out right now. But people at the other forum say that it's working and they have root access.
Sent from my C5503 using Tapatalk 2
Click to expand...
Click to collapse
with locked or unlocked bootloader?
i'm wating unlocked one.
@akash4357 Which recovery would that be?
Thanks akash4357, appreciate your efforts however I have a couple questions though.
akash4357 said:
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash Recovery.
4. Download and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded file.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
Click to expand...
Click to collapse
6. when you wrote "search for the previously downloaded file", do you mean I should install the .zip file from SD card?
9. How can you flash the recovery if you will not have root access? Or recovery can still be installed with out root?
---------- Post added 7th August 2013 at 12:13 AM ---------- Previous post was 6th August 2013 at 11:50 PM ----------
Noonski said:
@akash4357 Which recovery would that be?
Click to expand...
Click to collapse
Here you go Boss, this is the one i am using, just made a thread about it. Not sure which Recovery is being used in the instructions on this thread however.
http://forum.xda-developers.com/showthread.php?p=44361947#post44361947
WOW
akash4357 said:
Instructions for obtaining the rights to the .244. This method seems to work for many and has been confirmed over at a private forum.
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash Recovery.
4. Download and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded file.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
Click to expand...
Click to collapse
well... it was a real pain in the a** but it worked!
gmengass said:
Thanks akash4357, appreciate your efforts however I have a couple questions though.
6. when you wrote "search for the previously downloaded file", do you mean I should install the .zip file from SD card?
9. How can you flash the recovery if you will not have root access? Or recovery can still be installed with out root?
---------- Post added 7th August 2013 at 12:13 AM ---------- Previous post was 6th August 2013 at 11:50 PM ----------
Here you go Boss, this is the one i am using, just made a thread about it. Not sure which Recovery is being used in the instructions on this thread however.
http://forum.xda-developers.com/showthread.php?p=44361947#post44361947
Click to expand...
Click to collapse
for number 6, he means to flash the file you have downloaded on step 4. for number 9, you already have root access on that point given that you have followed all preceding instructions. The file you flashed on step 6 is the pre-rooted system partition of the 244 firmware, that is why on step 8 he indicated that you should not include flashing of the system part.
offtopic: now that there is a root method for xperia ZR, I will be buying it in the coming weeks. =))
Now it all seems to work fine so far. But what still hold me back is the pre-rooted zip file with the system partition from an unknown source. I always run custom ROM on my Android phones but usually they're from the developer directly. Flashing zip files downloaded from these Russian websites seem a bit risky. Anyone knows more about the source of it?
itandy said:
Now it all seems to work fine so far. But what still hold me back is the pre-rooted zip file with the system partition from an unknown source. I always run custom ROM on my Android phones but usually they're from the developer directly. Flashing zip files downloaded from these Russian websites seem a bit risky. Anyone knows more about the source of it?
Click to expand...
Click to collapse
It's a very trusted private forum. Why would i post something from somewhere that I don't trust?
Moreover Root on 4.2.2 is now active!!
itandy said:
So are you now using this rooted 4.2.2? No more bootloop?
Click to expand...
Click to collapse
Yes no more bootloops! Rooted and everything is fine :good:
akash4357 said:
It's a very trusted private forum. Why would i post something from somewhere that I don't trust?
Moreover Root on 4.2.2 is now active!!
Click to expand...
Click to collapse
Seems like I'm also going to flash it soon. Thanks! :laugh:
I can confirm the method working.
@akash4357 I took the liberty of adding a few more links and words to your description.
I also don't get the reboots I had on the .310 rom with SuperSU while deleting System apps using Titanium Backup.
request :/
can you guys make a flashable rooted zip of the 4.2.2 firmware please? i was deleting some bloatware and looks like i did something wrong and got a bootloop for some reason. Now i had to wipe data and everything, even the internal storage was formatted when wiping data!!! Reinstall the firmware and lost root, so ill have to do it all over again for the love of god, please!:crying:
zytres said:
can you guys make a flashable rooted zip of the 4.2.2 firmware please? i was deleting some bloatware and looks like i did something wrong and got a bootloop for some reason. Now i had to wipe data and everything, even the internal storage was formatted when wiping data!!! Reinstall the firmware and lost root, so ill have to do it all over again for the love of god, please!:crying:
Click to expand...
Click to collapse
The file zr244-system-supersu.zip is already a flashable zip of system partition with busybox, su and Superuser.apk. So you might find your missing files there or flash it for the whole system partition.
also..
itandy said:
The file zr244-system-supersu.zip is already a flashable zip of system partition with busybox, su and Superuser.apk. So you might find your missing files there or flash it for the whole system partition.
Click to expand...
Click to collapse
Also i forgot to mention that i was unable to enter recovery. It turned on the green led and i tried with both volume up and volume down and it didnt work several times.
Noonski said:
I can confirm the method working.
@akash4357 I took the liberty of adding a few more links and words to your description.
I also don't get the reboots I had on the .310 rom with SuperSU while deleting System apps using Titanium Backup.
Click to expand...
Click to collapse
Thanks for the edit! You saved me some time.
Are you by any chance planning any ROM development for the ZR?
Just followed the instructions and upgraded to 4.2.2 with root. Data is preserved and so far everything seems fine. Finally see lockscreen widgets again!
is anyone able to get into recovery? pressing up or down during the green light doesnt do anything. the only way i can access recovery is to reflash it every time.
Is it possible for me to install the binary su and the superUser apk myself with stock ROM and recovery so I can still get the OTA updates? I have S-OFF with revone currently on android 4.2.
Thanks
leo.sutton said:
Is it possible for me to install the binary su and the superUser apk myself with stock ROM and recovery so I can still get the OTA updates? I have S-OFF with revone currently on android 4.2.
Thanks
Click to expand...
Click to collapse
Yes its possible. In fact, last time I used to install binary and apk on top of stock ROM. I flash it from here:
http://androidsu.com/superuser/
petalyaa said:
Yes its possible. In fact, last time I used to install binary and apk on top of stock ROM. I flash it from here:
http://androidsu.com/superuser/
Click to expand...
Click to collapse
So where do I need to push su and the apk? I thought su needed to be in the system partition which I can't access.
leo.sutton said:
So where do I need to push su and the apk? I thought su needed to be in the system partition which I can't access.
Click to expand...
Click to collapse
You need root to install SU afaik
leo.sutton said:
So where do I need to push su and the apk? I thought su needed to be in the system partition which I can't access.
Click to expand...
Click to collapse
Follow these steps :
1) Download SU binary+APK and put it in the sdcard. The downloaded file is a flashable zip.
2) Unlock bootloader (Can be done using HTCDev)
3) Flash custom recovery
4) Enter recovery then flash the zip file you just put in step 1.
5) Wait till it finish flashing, then reboot, you should be rooted now.
petalyaa said:
Follow these steps :
1) Download SU binary+APK and put it in the sdcard. The downloaded file is a flashable zip.
2) Unlock bootloader (Can be done using HTCDev)
3) Flash custom recovery
4) Enter recovery then flash the zip file you just put in step 1.
5) Wait till it finish flashing, then reboot, you should be rooted now.
Click to expand...
Click to collapse
Okay, thanks, but its not possible with stock recovery? I thought your first answer indicated it was.
leo.sutton said:
Is it possible for me to install the binary su and the superUser apk myself with stock ROM and recovery so I can still get the OTA updates? I have S-OFF with revone currently on android 4.2.
Thanks
Click to expand...
Click to collapse
As far as I know, you just have to flash your stock recovery whenever you want to do ota updates. I converted my one to a developers edition a while back and whenever an ota update came out, i would flash my recovery, update, then put twrp back on. It never gave me any trouble because of my root.
an0ther said:
As far as I know, you just have to flash your stock recovery whenever you want to do ota updates. I converted my one to a developers edition a while back and whenever an ota update came out, i would flash my recovery, update, then put twrp back on. It never gave me any trouble because of my root.
Click to expand...
Click to collapse
Aaah, sorry for the confusion, i mean on stock ROM and not recovery. I'm not really sure if its possible to flash the superuser zip in stock recovery or not. I think its not possible. If you want official OTA, if im not mistaken, it doesnt really matter which recovery you're on. Just use twrp and flash the superuser zip and you're good to go..
petalyaa said:
Aaah, sorry for the confusion, i mean on stock ROM and not recovery. I'm not really sure if its possible to flash the superuser zip in stock recovery or not. I think its not possible. If you want official OTA, if im not mistaken, it doesnt really matter which recovery you're on. Just use twrp and flash the superuser zip and you're good to go..
Click to expand...
Click to collapse
You have to have stock recovery to get a true ota update. That is how it updates. If you download an ota update, first thing it does is go into recovery to flash it. It will end up going into your custom recovery and just sitting there. Your phone firmware and hboot must match the one of the current rom, but it has to have stock recovery to do the actual update. First time it boots after ota, you may loose your su, but just put custom recovery back on and flash it real quick and you should be good to go then you can flash back to stock recovery and twrp should fix your root if it has a problem. I hope this helps. You know you can just download the updates and flash them yourself too. Btw, newest 3.22 rom sucks! It has many problems that are all over the forums. Proximity sensor has gone to hell, and your messages contact pictures disappear every time you get a new text.
an0ther said:
You have to have stock recovery to get a true ota update. That is how it updates. If you download an ota update, first thing it does is go into recovery to flash it. It will end up going into your custom recovery and just sitting there. Your phone firmware and hboot must match the one of the current rom, but it has to have stock recovery to do the actual update. First time it boots after ota, you may loose your su, but just put custom recovery back on and flash it real quick and you should be good to go then you can flash back to stock recovery and twrp should fix your root if it has a problem. I hope this helps. You know you can just download the updates and flash them yourself too. Btw, newest 3.22 rom sucks! It has many problems that are all over the forums. Proximity sensor has gone to hell, and your messages contact pictures disappear every time you get a new text.
Click to expand...
Click to collapse
Okay, thats new for me, never know that we need to be on stock recovery for official update.
That's why I never wait for OTA.. I used ROM in this forum and so far I never have any issue that U mention above..
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
egwktm said:
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
Click to expand...
Click to collapse
You have to "Full unroot" in SuperSU settings and restore the stock recovery. Otherwise OTA will fail. After the OTA is installed, You can easily return to TWRP and flash SuperSU.
okay thanks! also instead of twrp could I use chainfire again?
Unfortunately, i tried to install OTA and now every time i turn on my phone it reboots and tries to install 5.02 only to get an error and it stays at twrp menu. So what can i do now?
lol after many reboots phone decided to tell me that update was unsuccessful so it works again.
more details pls for a beginner
I made the same mistake trying to flash OTA 5.02 over rooted device 4.4.4 . I got out of the loop by moving the download zip from system/cache to external sd...
just wanting to make sure I do all the right things and in order:
so in Super SU I go the FULL UNROOT
how do I then restore stock recovery?
Once I I have restored it what are the steps for the zip and install via stock recovery?
sorry about the boring questions - it's still a bit of a jungle for a beginner
egwktm said:
okay thanks! also instead of twrp could I use chainfire again?
Click to expand...
Click to collapse
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
dpdp73 said:
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
Click to expand...
Click to collapse
No
doppelhelix said:
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Click to expand...
Click to collapse
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone? Some people therefore recommend the Chainfire CF-Auto-Root instead.
So after unlocking bootloader can I flash TWRP in fastboot mode and superSU afterwards without those kind of problems?
Wolfcity said:
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone?
Click to expand...
Click to collapse
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
doppelhelix said:
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
Click to expand...
Click to collapse
Thx a lot for your explantion.
This was one of the things that irritated me right from the start when I was checking out the possibilities of custom recovery/root within 5.0.
I heard about the file-renaming thing but didn´t realize that superSu will do the job too and that it is a Nexus "feature" at all.
Helped me very much!