Related
In this day I am trying update my nexus one but when I try appear this sentence:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why??????
Anyone can help me????
Are you doing it via ota or via zip if your doing it by zip then try redownloading the file your's may be corrupted if it's via ota then you could just try via zip.
I have just try to do redownloading file zip but the sentence not chenge. Do you know why or what means it???
Sent from my Nexus One using XDA App
Try a different browser to download. Maybe z Firefox put Chrome of you're not already on those
Which carrier are you with, and where did you get your phone - it's possible that you have a carrier specific ROM...
Ski_55 said:
In this day I am trying update my nexus one but when I try appear this sentence:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why??????
Anyone can help me????
Click to expand...
Click to collapse
Are you running a custom recovery? Toggle off signature verification.
no, I have everything stock
Ski_55 said:
no, I have everything stock
Click to expand...
Click to collapse
If you are Vodafone, you are probably running a Vodafone "stock" ROM. You cannot use the update on a Vodafone ROM.
Go to Settings-->About phone. What Android version and what build number do you see?
Android version: 2.3.4
Build: GRJ22
But if I want root my nexus one, can I????
Sent from my Nexus One using XDA App
Ski_55 said:
Android version: 2.3.4
Build: GRJ22
But if I want root my nexus one, can I????
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Well, that looks stock. In the same area, what do you see under kernel version?
If you can't update, you can root by flashing an older shipped image like FRG83 (from here: http:/www.shipped-roms.com) and root that, then upgrade carefully so you do not loose root. You need to download the zip file, rename it to PASSIMG.zip, place it in the root of your sdcard, then boot into the bootloader. Otherwise, just unlock your bootloader, and things become much more simple, and you can have root on any build easily.
Applying the N1 OTA 2.3.6 (GRK39F) update via any recovery: Is this as simple as it sounds?
Download the package, rename to update.zip, copy to root of SD, boot into recovery and apply the update.zip from the SD card?
FYI - I'm using running stock 2.3.4 at the moment, but already unlocked my bootloader and flashed RA-passion-v2.2.1.
Wulfbane said:
Applying the N1 OTA 2.3.6 (GRK39F) update via any recovery: Is this as simple as it sounds?
Download the package, rename to update.zip, copy to root of SD, boot into recovery and apply the update.zip from the SD card?
FYI - I'm using running stock 2.3.4 at the moment, but already unlocked my bootloader and flashed RA-passion-v2.2.1.
Click to expand...
Click to collapse
Yes, it's that simple. However, you need to toggle signature checking in recovery before you apply the update.zip.
P.S. There is no need to rename it to update.zip
efrant said:
Well, that looks stock. In the same area, what do you see under kernel version?
If you can't update, you can root by flashing an older shipped image like FRG83 (from here: http:/www.shipped-roms.com) and root that, then upgrade carefully so you do not loose root. You need to download the zip file, rename it to PASSIMG.zip, place it in the root of your sdcard, then boot into the bootloader. Otherwise, just unlock your bootloader, and things become much more simple, and you can have root on any build easily.
Click to expand...
Click to collapse
I also tried to rotate but I can not downgrade to any previous fersione Android. Can you help me? If I can not unlock the bootloader to not lose the warranty.
With root permissions, then I can install any rom with "Rom manager" right?
Ski_55 said:
I also tried to rotate but I can not downgrade to any previous fersione Android. Can you help me? If I can not unlock the bootloader to not lose the warranty.
With root permissions, then I can install any rom with "Rom manager" right?
Click to expand...
Click to collapse
What is your main version? To find out, connect your device to your PC in fastboot mode, and type this into a terminal window:
fastboot getvar mainver
If it is higher than 2.18.1700.1, then you are out of luck, and there is no way to root without unlocking your bootloader. If it is lower or the same, then you CAN use a PASSIMG.zip file to downgrade to an earlier, rootable version of Gingerbread.
efrant said:
What is your main version? To find out, connect your device to your PC in fastboot mode, and type this into a terminal window:
fastboot getvar mainver
If it is higher than 2.18.1700.1, then you are out of luck, and there is no way to root without unlocking your bootloader. If it is lower or the same, then you CAN use a PASSIMG.zip file to downgrade to an earlier, rootable version of Gingerbread.
Click to expand...
Click to collapse
I don't understand where I must wrote "fastboot getvar mainver".
I Turn off my device
Turn on with power and trackball
Bootloader
fastboot
connect device to pc
and write "fastboot getvar mainver", but where????
Thank you so much
Ski_55 said:
I don't understand where I must wrote "fastboot getvar mainver".
I Turn off my device
Turn on with power and trackball
Bootloader
fastboot
connect device to pc
and write "fastboot getvar mainver", but where????
Thank you so much
Click to expand...
Click to collapse
On windows open your command prompt and navigate to wherever your fastboot executable is (you can use Windows Key + R and type in cmd and hit enter to open the command prompt).
bassmadrigal said:
On windows open your command prompt and navigate to wherever your fastboot executable is (you can use Windows Key + R and type in cmd and hit enter to open the command prompt).
Click to expand...
Click to collapse
I wrote in the prompt but it say that "fastboot is not eseguible"
I am not sure how well I understand the translation. What OS are you running? Because windows shouldn't complain about whether a file is executable or not.
Ski_55 said:
I wrote in the prompt but it say that "fastboot is not eseguible"
Click to expand...
Click to collapse
I think you have one of two possible problems: 1) you don't have the USB driver installed properly or 2) you are issuing the command in the same directory as the fastboot executable.
Sent from my Nexus One using Tapatalk
I found this guide http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/ what do you think?
Hi guys,
I am trying to flash stock firmware to my Moto G 4G using TWRP v2.7.1.0. I am able to detect my device and serial in CMD when I type "adb devices". However, when I try to sideload stock firmware my phone aborts the process saying "no MD5 file found"
I have also tried installing the firmware through mfastboot and get various errors relating to HAB Checks and primary_gpt.
I have checked my phone and I am using CID7 firmware only.
I am pretty much a noob to all this.
If anyone has any suggestions on how I could get my Moto G back up and running I would be over the moon!
Thanks for taking the time to read.
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
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
hydroman202 said:
I need assistance as the title says. First up my bootloader is not unlockable, (believe me I've tried) and here is my situation. I cannot flash the next OTA, because of failed error in recovery upon trying to install. There is no full firmware to reflash the device, only an OTA that I obtained (and yes it is completely for my phone model) (XT1925DL). I would sideload the OTA or apply it from sdcard in the recovery, however the device is not detected on Windows via adb or on linux, after hitting the sideload zip option, and Sdcard cannot mount. I get (sdcard failed to mount, E: installation aborted in recovery). If someone knows an option to maybe allow me to use the OTA file to repatch the system, without having to resort to the recovery mode, or adb sideload option, it would be appreciated if you could help.
Click to expand...
Click to collapse
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Ragarianok said:
Is it a TracFone? You're probably going to have to flash in Fastboot.
Download the most recent firmware here:
https://mirrors.lolinet.com/firmware/moto/ali/official/TRAC/
And use this guide to flash:
https://forum.xda-developers.com/moto-g6/how-to/guide-faster-updated-guide-to-root-t3914228
Click to expand...
Click to collapse
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
hydroman202 said:
I appreciate the response. Unfortunately that site is not up to date with the TracFone firmware. The latest official one I have. And I can't flash it unfortunately because I'm on a newer firmware and it throws security downgrade errors when I try. If I could figure out how to get recovery mode to show up on my pc I would be ok.... Then I would be able to apply the OTA I need for the next one to complete successfully.
Click to expand...
Click to collapse
Have you tried to run those Fastboot commands without:
Code:
[I]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/I]
Should work if you exclude those two; that's what I did to downgrade from Pie back to Oreo.
You could also try Lenovo Moto Smart Assistant.
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Ragarianok said:
I just realized that I totally misread your original post and, man, I feel like a total dummy.
Is the OTA currently on the root of your phone's internal storage?
If it's an actual update.zip file and it's in the root of your internal storage, you could try going into Settings/Apps & notifications/Apps info (tap the down arrow and select Show system)/Moto Update Services and make sure that Storage permission is toggled on. After that, try to perform an update.
I had a similar error when trying to sideload with ABD and update from SD in recovery, but it turned out that I was trying to update using full firmware.
Can you link the update file you have?
Click to expand...
Click to collapse
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
hydroman202 said:
Unfortunately I cannot not link it but the file size of the ota is roughly 1.47 GB. And the ota was a upgrade to pie. I'm still on that one. Needing to reflash it so I can correct a partition issue. That's preventing the next ota from succeeding. The reason the next one doesn't succeed is because it checks the modem partition and it unfortunately fails to verify it because I accidentally flashed the wrong one. The ota should patch the modem in the device now I'm thinking because the modem that is currently on the device is the one before the ota arrived. All other partitions are the ones meant for the current firmware.
Click to expand...
Click to collapse
Hm.
You could try to use the Lenovo Moto Smart Assistant. It has a Rescue option that returns the phone to stock firmware. It also has an Upgrade option; I've tried it but there aren't any updates for my phone. You could Rescuing and then Upgrading. Or you could Rescue and then try the OTA again.
The only downside is that everything on your phone's internal storage will be erased.
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 ?