Develop Bugs

Update to android 4.2.2

Hello,
I am currently running android 4.1.1 with software number; 3.14.401.31.
When I check for updates it shows the software update: 3.20.401.1 (35.66 MB).
When I press install now my phone reboots itself and starts in recovery mode.
When it's loaded it shows the following error:
E: unknown volume for path [INTERNALSDCARD: Download/OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.1-3.14.401.31_R_release_314818virsindn3qwws1r3.zip]
E: Can't mount INTERNALSDCARD: Download/OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.1-3.14.401.31_R_release_314818virsindn3qwws1r3.zip
Installation aborted.
Ofc I can download the OTA zipfile from the internet, but then I have the following problem; when I connect my phone to usb:
My own pc cannot find my phone. When I try to connect my phone to an other pc, it also cannot find my phone.
Hope someone can help me out.
Not unimportant: I have rooted my phone and I have unlocked the bootloader.
Maybe I have to relock the bootloader at first?

Veldscholte said:
Hello,
I am currently running android 4.1.1 with software number; 3.14.401.31.
When I check for updates it shows the software update: 3.20.401.1 (35.66 MB).
When I press install now my phone reboots itself and starts in recovery mode.
When it's loaded it shows the following error:
E: unknown volume for path [INTERNALSDCARD: Download/OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.1-3.14.401.31_R_release_314818virsindn3qwws1r3.zip]
E: Can't mount INTERNALSDCARD: Download/OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.20.401.1-3.14.401.31_R_release_314818virsindn3qwws1r3.zip
Installation aborted.
Ofc I can download the OTA zipfile from the internet, but then I have the following problem; when I connect my phone to usb:
My own pc cannot find my phone. When I try to connect my phone to an other pc, it also cannot find my phone.
Hope someone can help me out.
Not unimportant: I have rooted my phone and I have unlocked the bootloader.
Maybe I have to relock the bootloader at first?
Click to expand...
Click to collapse
if you have SU binaries etc in system then install from market or so voodoo keeper then save root and uninstall root binaries then go to fastboot flash stock recovery for your base number like 3.14.401.31...you can get it if you search then relock bootloader and download and install the ota

Are you on stock recovery ?
To receive and successfully install OTA updates you need:
Unlocked or Locked bootloader - doesn't matter
Rooted or Not Rooted - doesn't matter
STOCK ROM
STOCK KERNEL
STOCK RECOVERY
If you have there 3 things than you should be able to install OTAs with no problems

get stock recovery for your particular CID from "Nandroid Backup Collection" thread and flash it in fastboot command prompt. i've gone through this exercise recently.

or you can get your stock recovery from here as well....
http://forum.xda-developers.com/showthread.php?t=1957376
just find your cid, download and extract recovery.img

Problem installing Viper10 5.7 Magisk

Tried to post this to the thread but I'm under the 10 post limit, so it redirected me here. I have a Sprint HTC 10 with S-off thanks to sunshine. I did the RUU to start clean as I was coming from a non-magisk version of Viper on the old radio. Succesfully got back to stock with updated radio and still mainted S-off. Installed magisk 11.6, and it shows properly rooted (green checkmarks across the board)
Downloaded the magisk version of Viper10 5.7 zip to my external SD card. Using the latest version of TWRP i tried to install Viper10, but I get an error:
-Creating /cache/magisk.img with size 320M
-Mounting /cache/magisk.img to /magisk
-Copying files
-Setting permissions
-Unmounting partitions
Updater process ended with ERROR: 2
Error installign zip file '/external_sd/Viper10_5.7.0_MAGISK.zip'
Updating partition detials...
...done.
Tried installing the zip via Magisk, seems to load, asks me to reboot, but when I reboot I'm still on stock android. I goto my modules section and the only module showing is viper10rom with (no info provided) for the details under the rom.
Any help would be greatly appreciated. Thank you.

Did you check the md5 of your download?
can you pull the /tmp partition and the the installation in twrp and upload it?

j to the 4n said:
Did you check the md5 of your download?
can you pull the /tmp partition and the the installation in twrp and upload it?
Click to expand...
Click to collapse
I did, matched up. I even downloaded it again. I ended up running out of time to be messing with it and did a full install, not a magisk load. The full rom loaded fine.

Am I okay or is there more I should do?

(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.

WutUpCuuuz said:
(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
Click to expand...
Click to collapse
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Sent from my 2PS64 using Tapatalk

WutUpCuuuz said:
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Click to expand...
Click to collapse
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??

Tarima said:
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Click to expand...
Click to collapse
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Sent from my 2PS64 using Tapatalk

WutUpCuuuz said:
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Click to expand...
Click to collapse
If you're not sure you ever had s-off, then you didn't have it. S-off is a separate procedure, not be confused with bootloader unlocking or rooting.
If the ruu didn't run, most likely you tried one made for another mid/cid, or the software version was older than what you had already on your phone. Make sure both of these are corrected and report back if it works. And yes the ruu.exe would work, but the two points I just mentioned need to be taken into account.

Double checked that it was the correct RUU... still correct as far as I can tell. Rebooted to download mode, didn't see it on the SD. Renamed the RUU to 2PS6IMG.exe, still didn't see it. ??? I'm stuck, my PC isn't here with me so I can't try it that way.

Help with flash stock rom

Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?

z3dulik said:
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
Click to expand...
Click to collapse
Just nuke it with flash-all.bat May factory image. You can boot TWRP and flash the R OTA as well.

I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
When I turn it on i have an alert "your device is corrupt."

z3dulik said:
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
Click to expand...
Click to collapse
I would extract the factory image, fastboot erase user data then update bootloader, radio and vendor on both slots(reboot bootloader after each flash) then flash-all or fastboot update with the Taimen file that contains the vendor image
It's a bit longer of a process but it works.

Tried too, same thing. Looks like it's something related to recovery. Can't write to

z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
Swap slots and flash to both
Sent from my Pixel 4 XL using Tapatalk

Managed to flash twrp on boot_a

z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
I've got out of this before
Boot TWRP
Format data
Pop in an otg with stock OTA hit mount go back and hit mount then it'll appear as auto-1 in TWRP and flash the OTA
It works if you need to go back to previous month or Android version. Just make sure both slots are the same after you boot

OTG not recognised
/vendor error
also the factory images are missing from here? https://developers.google.com/android/images
I can see only OTA

fixed with factory android 10 april. thanks all for help

Question Nokia G10 recovery from failed Android 13 sideload update

Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.

dkmoore said:
Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.
Click to expand...
Click to collapse
You should not have done that.
Nokia does not allow sideloading on this device. Please check your PM.