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.
Related
Hi all,
On monday I was looking forward to download Froyo, and since then I live a nightmare. Everything starts cool, it downloaded, it installed itself, and when it restarted.... NIGHTMARE, it started to keep on restarting every two o three minutes after saying the system has a problem.
Since that moment I lost Wifi and mobile features, as well as SD-card reading posibilities.
What I found after some reboots is that I could get into the bootloader and select Recovery, and so I did... and I chose wipe data/factory reset. Everything got delete, and now I could see the screen when it loads (HTC Sense screen).
After this I have tried almost everything, a goldcard to copy a new update.zip file (but when I do it I got the following message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
And this had happen with any single update.zip file I found in these forums and others.
I have tried to use revoked3, and I got an error saying it can not keep on installed.
So... do i have a brick or does someone know how to fix this problem?
Thank you very much in advance for any piece of help.
Guillermo
did you update to the latest radio ?
hittori said:
After this I have tried almost everything, a goldcard to copy a new update.zip file (but when I do it I got the following message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
And this had happen with any single update.zip file I found in these forums and others.
I have tried to use revoked3, and I got an error saying it can not keep on installed.
Click to expand...
Click to collapse
I haven't used revoked recovery, but I know that ROM Manager recovery has an option to 'disable signature verification' (or similar wording) that should get rid of your verify option. As for the reboot loop, usually if you remove the SD card completely, and go into fastboot mode and wipe storage, you get booted up ok.
In my experience, its pretty near impossible to permanently brick an Android handset, so keep at it. You will get it working fully again in the end.
(I lost SD, BT and USB functionality in late July and had everything working again in 24 hours - after lots of panic and stress!).
Feel free to PM me if you get totally stuck.
When and how??
I think I did not, but I did not know I have to do it. I mean, my phone was working fine, I download FROYO, it crashs.... when should I put a new Radio????
Best regards
Solution at last
Thanks to dez_bordes, we found out that I have to use r6 method and it does works.
Thank you very much indeed.
Guillermo.
Welcome. hope you help me a job
I have HTC's Desire ROOT
The state of the machine is still up normally and works fine, but Andoid not get the memory card, no recovery
As children learn to bring the phenomenon known as USB-Brick, Brick SDCard. and on the forums have dealt with software Address. Today I read of your experience you should want to help
because no good at computer should not know
wish you a detailed step by step guide 1 is not?
bban hope this helps for me. tks you more
Hello All,
I have GPE version of GPad running Kitkat 4.4 Stock ROM. Last month I have used following link to enable chromecast mirroring. Due to the issues i have uninstalled superuser app and did factory reset. After that all well! I mean no issues with tablet.
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Yesterday I tried to sideload the GPE lollipop update but prompted with following error.
"/system/etc/audio_policy.conf" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
This morning I saw system update notification for Lollipop upgrade and opted to install it, but without any further msg during the system update it prompted with "Error!" After that I did factory reset. When it reboots starts optimizing 48 apps, but it prompts with following sequence of messages:
"Unfortunately sun beam has stopped. "
None of the apps loaded , no access to setting, just empty screen and on screen buttons at the bottom.
I spent quite some time looking around in xda to restore back to factory, none seems to work.
1. Tried flashing original stock .tot file, getting "Download user image is only available in the online environment!!
2. adb sideload, "/system/etc/audio_policy.conf" has unexpected contents
3. To Flash TWRP i am not getting access to setting to enable USB debugging.
Now i cant even put the G Pad in adb as i dont have access to settings to put in USB debug mode. vol down+power puts into bootloader, but cant access to adb commands.
Now I can only access to recovery and do sideload. but i am stuck with "/system/etc/audio_policy.conf" has unexpected contents error. Can someone share kitkat original version of audio_policy.conf? also how i can replace the exiting file as i dont have access to adb?
Greatly appreciate your help to bring back the G Pad.
regards
Raj
You can boot twrp from fastboot and flash either 4.4.4 or 5.0 back onto your tablet. Look at the thread in Android development for more details on flashing the stock images using twrp
Thanks! I was able to get back to kitkat with following method. I was able to flash recovery its now back to complete stock kitkat now.
http://forum.xda-developers.com/lg-...510-gpe-4-4-4-ktu84p-l002-stock-twrp-t2797883
After this I got system update notification to lollipop. Again got "Error!" msg during the install process.
I tried adb side load, got following error!
failed to verify whole-file signature
signature verification failed
installation aborted.
Any thought whats going wrong there?
My micromax android one phone is stuck during boot with micromax boot logo. It has 5.1.1 android version with build number LMY47V.
To recover this, I am trying to flsah rhe ROM with this OTA - d827aed7f4da8fcedfcd24c8d67e97977b610120.signed-sprout-mmx-ota-1783956.d827aed7.zip
But I am getting below error:
Can't install this package over newer build
E:Error in /sideload/package.zip
However, in file ..\d827aed7f4da8fcedfcd24c8d67e97977b610120.signed-sprout-mmx-ota-1783956.d827aed7\META-INF\com\google\android\updater-script, I removed the line which checks for newer build. But with that I am getting now following error:
E:Failed to verify whole-file signature
E: signature verification failed
IS there any way to avoid this signature problem.
Please help find OTA which could be flashed on my phone or any other suggestion.
I tried putting twrp recovery which requires device to be in debugging mode. Since my device is not booting to that stage, I skipped that part and tried if via other fastboot commands, it will be done or not. But this also fails as the device remains in default recovery.
I tried flashing through SP Flash tool also, but there it is not able to detect the device.
Please let me know if something else can be tried. Appreciate any help on this.
Hello,
i have a rooted HTC 10 (Magisk + phh root) and got the notification that an OTA update is available. I am currently on 1.90.401.5 and the update is for 1.95.401.3.
I believed that with the systemless root I can just flash the stock recovery from 1.90.401.5 and take the OTA, but apparently this is not the case. It downloads just fine, then the phone restarts as intended and starts to install. But at 20%-30% it changes into the standard splashup from recovery (the phone symbol with the exclamation mark in it) and does not respond anymore. Upon restart I can see that the update was not applied and it keeps asking me, if I want to update.
However I tried to manually install the OTA.zip in the stock recovery and this is the error I get when choosing the zip from SD card:
Code:
[...]
Verifying current system...
Package expects build fingerprint of htc/pmeuhl_00401/htc_pmeuhl:6.0.1/MMB29M/783302.5:user/release-keys or htc/pmeuhl_00401/htc_pmeuhl:6.0.1/MMB29M/797255.3:user/release-keys; this device has htc/pmeuhl_00401/htc_pmeuhl:6.0.1/MMB29M/761759.3:user/release
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
What are those numbers (761759.3) and does it makes a difference that there only stands user/release, while user/release-keys is required?
And how do I install this OTA without ditching magisk and my data?
The mostly likely cause is your system partition is still modified somehow, hard to say how exactly.
The best option would be to restore a system image if you made one earlier, or look for a stock ROM of your software version at forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297.
If all else fails you can use a RUU, but that would delete your data of course.
Thanks for your answer. I will try to flash a new system image
But can anyone tell me, what those numbers/paths mean? are those hashes of the system? or something else?
The CID is an identifier that changes by region & model, it needs to match your phone.
To find it out, Google 'adb getvar all' - I forget the exact steps but that's the important command.
No you got me wrong. I know of cid and mid. But the number 783302.5 is clearly NOT the cid. What is it?
Oh right, in the original error message. That most likely contains info on the exact differences the update found in the system partition. I don't know the exact details of how to decode that into anything meaningful unfortunately.
Ah, okay. Thank you!
I think if I now just flash a stock system.img of 1.90.401.5 I should keep my data and magisk (as magisk modifies the boot) and should be able to OTA update, right?
My pixel C has the issue today.
the robot was down. the system is 7.1.2beta
I was meet this issues last time. I was downloaded the OTA image,and use the "sideload " to save my pixel .its useful.
but today, when I downloaded the 7.1.2 OTA image and use the sideload. its unused
error tips as below
E:footer is wrong
E:signature verification failed
E:error :21
I try to downloaded again and again. even use my other laptop to do. also failed.please help me
I think that you downloaded the firmware image, and not the ota version. ( the first one requires fastboot and oem unlock ), the second adb sideload and tablet in recovery mode