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.
Folks,
I recently purchased a preowned HTC One M9 in good shape. The phone does not appear to have been rooted, s-offed or any such thing. It looks bone stock. It currently has Android 6.0 on it. and software number 3.39.531.41
It has been over a month since t-mobile has rolled out the nougat update for the HTC One-M9 and I have not received any update on the phone. I constantly keep checking if the phone has an update available but the phone always says no update available. I gave up on the OTA being rolled out for the phone so I downloaded the Nougat RUU which is 4.27.531.6 .
When I follow the procedure for installing the update I got a signature error 132 . Now I know that error shows up when the phone is rooted or is s-off or any such thing but my phone seems to be completely stock. Does anyone know why I cant install the RUU or receive OTA updates to Nougat for my phone?
I think I figured it out. I contacted T-Mobile support who told me to contact HTC since the HTC servers are responsible for pushing out updates. So I contacted HTC customer support and shared my IMEI with the representative. She looked up some information on the HTC database using the IMEI number and told me that my phone was a store demo phone and that demo phones are blocked from receiving updates from the HTC servers. Oh well.
Hello,
Just got the same phone with same error. If someone provides me with 0PJAIMG.ZIP, I can test and see how it goes. So far update from phone >> didn't work; RUU update >> didn't work. same error
Thanks
I had the same problem some time a go what you have to do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA. But my receives the OTA alright but could neither install that or RUU
amptronic said:
I had the same problem some time a go what you have do is to check if its relock and has stock recovery. If yes first flash 3.39.531.41 RUU before you can flash the 4.27.531.6 or the OTA.
Click to expand...
Click to collapse
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
dohcvtec said:
So it has to be locked with stock recovery? Then flash ruu 3.49 ad then the newest version?
Thanks
Click to expand...
Click to collapse
did it work?? I'm having same problem..
smilesintears77 said:
did it work?? I'm having same problem..
Click to expand...
Click to collapse
Did anyone get any solution for this error? I am having the same issue
Thanks
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i think first decrypt RUU then manually flash whole Nougat ROM.
vbcomer said:
Did anyone get any solution for this error? I am having the same issue
Thanks
Click to expand...
Click to collapse
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
m_abbas25 said:
i found a way i have demo set when i use 4.27.531.6 RUU its saying signature error so this is what i did
i download OTA from link here http://fotadl-az.htc.com/secure/OTA_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6-3.39.531.41_release_497409trrpztkwvabkx6lv.zip
after that i just boot into recovery mode and then select an opton Updae via ADB
rename file to OTA.zip then open command prompt located to where file is and then run below command
adb sideload ota.zip
let the process finish it will take a while. especially when HTC logo appears it took 5 min but i finally have nougat
for detail how to apply OTA here is link http://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/
Click to expand...
Click to collapse
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
vbcomer said:
Hi,
Thanks for the info. However, I couldn't get into the recovery mode. Either from bootloader -> "Boot to recovery mode" or via command "adb reboot recovery", after the phone reboots, the screen will show a phone icon with triangle. Then after awhile the phone will restart normally. I can't get to step to do sideload the zip file.
I also put the above ota.zip on a micro SD card and load the card in the phone, then boot to download mode. In that mode, it shows the following 2 lines:
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
Where do I find that missing file?
Thanks
Click to expand...
Click to collapse
I think your recovery file is damaged. Thou i am novice in this but i think you should run RUU of existing rom it may repair your recovery then try this method.
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
vbcomer said:
OK,
I found the 0PJAIMG.zip for version 3.39.531.7 in this forum "https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022"
I put that on my SD card and was able to update the phone from Lollipop to Marshmallow.
However, after that update, the phone still won't update from Marshmallow to Nougat using the file RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6 downloaded from htc website nor the OTA.zip downloaded from this thread. The phone keeps having the same Error [132] Signature Error. Or it won't go into the Recovery mode to do sideload of the OTA.zip. If the original Recovery file (from Lollipop) was bad/corrupt, wouldn't the Marshmallow update correct/fix that file?
So, do we have any other idea to upgrade the phone from Android 6.0 to 7.0? Does anyone have a 0PJAIMG.zip for 7.0?
Thanks
Click to expand...
Click to collapse
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Ok. I was able to install 3.39.531.41. I will try the OTA now
m_abbas25 said:
In order to OTA to work which is in this forum you have to be in 3.39.531.41 first find RUU of this version run it then go for OTA.
Noted that you wont be able to update from marshmallow to nougat using RUU you have to use OTA but for that you must be in version 3.39.531.41 .
Click to expand...
Click to collapse
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
2. Try to download the 0PJAIMG for 4.27 (Nougat) and install from sd card. I did find the file from AndroidFileHost website, but the phone gave error when it tried to load the zip file from download mode:
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
Do you have a reliable source for the OPJAIMG file for Nougat?
I did a research on the 12 RU_ZIP_ERROR and found an instruction for AT&T from developer Blueberry who suggested "If you're on Marshmallow base, first of all you need to upgrade your firmware and then flash this 0PJAIMG zip file via download mode in otherwise you'll be getting "12 RU_ZIP ERROR" during the flash process. No Wipe Firmware Link: https://www.androidfilehost.com/?fid=745425885120692233"
The above was for AT&T but I found the no_wipe zip for TMobile, however, I don't know how to upgrade the firmware on my phone using one of these files
the firmware no_wipe files are here:
https://www.androidfilehost.com/?w=files&flid=134381
The file I downloaded is "firmware_tmous_4.27.531.6_NoWipe.zip", but like I said above, I don't know how to update the firmware.... Can someone give me some directions?
Update: I renamed the file "firmware_tmous_4.27.531.6_NoWipe.zip" to "0PJAIMG.zip" and tried to update from download mode, but the phone gave error: 8 RU_SIGNATURE_FAIL.
Another research indicated that since the phone is S-ON and Locked, these firmware wouldn't install because they were not signed. Where can I find signed firmware for this phone?
Thanks
Click to expand...
Click to collapse
I don't know much now but we can try RUU of 3.39.531.41. It should solve your recovery. But the question is where you can download that?? Try finding a link mean while i am uploading it to my google drive then i will share link. Since i am in third world country it will take time. I will update you as soon as it is uploaded
vbcomer said:
I updated to version 3.39.531.41 but I am still unable to get to Recovery mode on my phone. It keeps showing the red triangle with exclamation mark.
So, is that correct that I am now having two choices (besides obviously stay with Marshmallow)
1. Need to somehow fix the recovery mode on the phone? It is a demo unit so I don't know if that has anything with the recovery not working
Thanks
Click to expand...
Click to collapse
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Thank you much! I will try everything you suggested now. I really appreciate your help!
dbs25 said:
To continue on to recovery mode, try this:
" If a device with a red triangle and exclamation point appears, Hold Power while pressing and releasing Volume Up to continue."
As for the 3.39.531.41 RUU, put the zip from this link into your external SD then boot into fastboot/download mode. From that point on the phone should automatically recognize the .zip and install from there.
https://www.androidfilehost.com/?fid=24438995911969398,
Click to expand...
Click to collapse
I downloaded the RUU from above link [https://www.androidfilehost.com/?fid=24438995911969398], but after installing, the phone went from 3.39.531.41 back to 3.39.531.7. Was the above zip file really the 531.41 version?
I tried to reinstall the 0PJAIMG for 531.41 downloaded earlier, but the phone said signature error.
I tried to install using the OTA zip from this link [http://fotadl-az.htc.com/secure/OTA_...kwvabkx6lv.zip] from Recovery mode but the phone said "E3001: Package expects build fingerprint of htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.41:user/release-keys or htc/himaul_tmous/htc_himaul:7.0/NRD90M/869604.6:user/release-keys; this device has htc/himaul_tmous/htc_himaul:6.0/MRA58K/690290.7:user/relea
E:Error in /sideload/package.zip (Status 7)
Installation aborted
You have any idea to go back to 531.41? Since the OTA message seemed to indicate it expected a 531.41 version?
Thanks
Ok. I was able to get back to 3.39.531.41 by getting the 0PJAIMG from AndroidFileHost.
After that, I went to Recovery Mode (using pwr + vol up after seeing the red triangle), chose Apply Update from SDCard, selected the OTA file for 4.27.531.6. This time It didn't give any error, at the end it appeared to get stuck for a long time at the line Script Succeeded Result was [/preload]. After about an hour, I turned off the phone and on again, now it is stuck at HTC logo splash screen.
Questions here:
1. Was the phone really stuck at the "script succeeded" line?
2. Didn't I wait long enough?
3. What should I have done at that time when it stopped at that "script succeeded" line?
4. What should I do at this splash screen? It has been like that for the last 10 minutes
Thanks
Hello everyone, I am trying to install the latest Global dev ROM on my Mi8.
I bought the phone from Gearbest and it arrived with the latest Russian stable ROM and unlocked bootloader.
The thing is I think the person who did all the above messed something up because I can't install the ROM I want using the standard procedures with TWRP, XiaomiMiTool or Mi Flash.
TWRP
When I try to install TWRP (version 918), when I reboot with the reboot command and use the flash command, I see some random errors (couldn't get max-size report for example) or the command does nothing, so I am not able to install it.
XiaomiMiTool
The program recognises the phone, I select the global dev rom, it makes its checks, then it tries (failing of course) to unblock the already unblocked bootloader and I cannot proceed any farther
Miflash
Booted the phone in fastboot, found in the program list, check "clean all" only, when I click flash the phone goes into a black screen with a "press any key to shutdown" in the top left corner of the screen
Any advice on how to resolve any of these problems please? Maybe something got corrupted like the boot.img or recovery.img?
I can provide with some screenshoots and photos and list of commands I was using if it's going to be of any help
Thanks
Install adb and flash it through.
krepsz said:
Install adb and flash it through.
Click to expand...
Click to collapse
Flash what? The recovery? I've tried that already The ROM? I need TWRP first
https://www.xda-developers.com/how-to-install-twrp/
krepsz said:
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Thank you for this, but this is the same guide I followed.
After I use the flash command either nothing happens or I get an error.
The image below is after I waited 5 mins
OK.I recommend you TWRP 3.2.2-0711 wzsx150 from LR.TEAM linkhttps://forum.xda-developers.com/mi-8/how-to/recovery-twrp-3-2-2-0703-t3812600
,and also i recommend you insted of Global rom the EU rom.Its many language included and have better performance and camera.
I resolved this problem changing pc with USB 2.0 ports.
Hi guys.
Trying to sort this one out once and for all.
Just got a notice that 11.0.5.0.QFKEUXM are ready for downloading. The problem is that i'm running with unlocked bootloader and rooted. So every time it try to update it will just get stuck at the custom recovery.
Trying to flash the downloaded OTA via TWRP gives me -Zip file is corrupt.
Manually downloaded the recovery rom via getdroidtips but that gives me same error message.
Trying to find a fastboot rom of 11.0.5.0.QFKEUXM but that seems impossible.
So what's the best options here? Just wait untill someone release the fastboot one? Or is there any other safe way to flash and keep all the data?
Cheers
SGT John Doe said:
Hi guys.
Trying to sort this one out once and for all.
Just got a notice that 11.0.5.0.QFKEUXM are ready for downloading. The problem is that i'm running with unlocked bootloader and rooted. So every time it try to update it will just get stuck at the custom recovery.
Trying to flash the downloaded OTA via TWRP gives me -Zip file is corrupt.
Manually downloaded the recovery rom via getdroidtips but that gives me same error message.
Trying to find a fastboot rom of 11.0.5.0.QFKEUXM but that seems impossible.
So what's the best options here? Just wait untill someone release the fastboot one? Or is there any other safe way to flash and keep all the data?
Cheers
Click to expand...
Click to collapse
I'll give you the links from the official download site.
In theory you should be able to update using the recovery ROM in TWRP, if I remember correctly the OTA ROM doesn't work in TWRP.
Get the latest recovery ROM from here
https://c.mi.com/oc/miuidownload/detail?device=1700361
Haven't checked what version is currently available, but you can always get the latest fastboot ROM from here. If it's not the latest, then wait a couple of days for it to appear. I think it normally gets updated at the same time as the recovery ROM is released, but couldn't say for definite.
https://c.mi.com/oc/miuidownload/detail?guide=2
Scroll through the list in section 2
For some reason they appear as a blank page on a mobile browser, so if viewing on your phone you will need to change the browser to view in desktop mode.
Robbo.5000 said:
I'll give you the links from the official download site.
In theory you should be able to update using the recovery ROM in TWRP, if I remember correctly the OTA ROM doesn't work in TWRP.
Get the latest recovery ROM from here
https://c.mi.com/oc/miuidownload/detail?device=1700361
Haven't checked what version is currently available, but you can always get the latest fastboot ROM from here. If it's not the latest, then wait a couple of days for it to appear. I think it normally gets updated at the same time as the recovery ROM is released, but couldn't say for definite.
https://c.mi.com/oc/miuidownload/detail?guide=2
Scroll through the list in section 2
For some reason they appear as a blank page on a mobile browser, so if viewing on your phone you will need to change the browser to view in desktop mode.
Click to expand...
Click to collapse
Thanks. Found the fastboot version on the second link. Gonna bookmark that one
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 ?