Completely back to stock but no access to stock recovery anymore - HTC 10 Questions & Answers

Hi, I went completely back to stock with my relocked bootloader, super Cid and s-off HTC 10 two days ago. Everything went well, after flashing RUU I once tried if stock recovery was working- it was- and went, as last step, s-on again. After that I installed several OTA updates without any problems and am now on the latest version. So far so good, only strange thing (for me at least) is no access to stock recovery anymore. I wanted do perform a factory reset so I tried to boot into recovery via bootloader mode. But than I got a screen image with a tiny HTC 10 image and a red triangel with an exclamation point... I remember something like this from way back with my Galaxy S2 between flashing ROMs and firmware updates when there was no recovery at all...
But as I said- after flashing RUU stock recovery was fine and if there was something wrong with it wouldn't it be impossible to install OTA updates?
Does this has something to do with s-on?
By the way, I found the option to do a factory reset in the nougat settings, so this is solved, but this red triangel irritates me very much!
Any help would be great!
Thanks.
Sent from my SHIELD Tablet K1 using XDA-Developers Legacy app

ronnbon said:
Hi, I went completely back to stock with my relocked bootloader, super Cid and s-off HTC 10 two days ago. Everything went well, after flashing RUU I once tried if stock recovery was working- it was- and went, as last step, s-on again. After that I installed several OTA updates without any problems and am now on the latest version. So far so good, only strange thing (for me at least) is no access to stock recovery anymore. I wanted do perform a factory reset so I tried to boot into recovery via bootloader mode. But than I got a screen image with a tiny HTC 10 image and a red triangel with an exclamation point... I remember something like this from way back with my Galaxy S2 between flashing ROMs and firmware updates when there was no recovery at all...
But as I said- after flashing RUU stock recovery was fine and if there was something wrong with it wouldn't it be impossible to install OTA updates?
Does this has something to do with s-on?
By the way, I found the option to do a factory reset in the nougat settings, so this is solved, but this red triangel irritates me very much!
Any help would be great!
Thanks.
Click to expand...
Click to collapse
Please see steps in attachment

Thank you, did not exactly work like this- in download mode was no fastboot mode but via bootloader to recovery and than step 4+5 did the trick! Sorry, really did not expect this to be such a mundane answer....
Sent from my SHIELD Tablet K1 using XDA-Developers Legacy app

Related

[Q]Phone does not boot, can only go to bootloader

Hi guys,
So i researched a few days before trying to root, install a custom rom (LeeDroid) and flash a custom rom
I managed to do it yesterday and everything was working fine. It is a really great rom.
But today I powered down my DHD and I can't boot anymore. The phone keeps rebooting (it vibrates one time, i see the HTC green logo, then a black screen, vibrates and so on...). The only way to stop this process is to hold the vol- key wich takes me to bootloader (so it appears the phone is continuosly powering off and on)
I already tried and bootloader is working fine, but when a I try any option that requires a reboot, the phone starts this process of power up and down.
Does anyone have any idea of whats happening?
Thanks guys!
Did you perm root your phone?
You could try reinstalling the stock rom too.
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Yeah I permrooted it.
But, how can I install a new rom without recovery?
I thought that you already flashed LeeDroid, and if you did, you have ClockworkMod recovery. But if that is not the case, use a RUU.
jkoljo said:
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Click to expand...
Click to collapse
Sorry man... I overlooked this post...
To better describe what I did:
-Radio s-off
Eng S-off
Instaled Leedroid (followed every recomendation he did in the post)
Flashed the radio he suggested
Got the phone working, tested a little bit, charged and then I powered off
When powered on again I got this bootloop
______________________________________
So, do you still recomend RUU?
Can I find any guide here on XDA?
Thanks!
edit:Forgot to mention that I get the bootloop even if I choose recovery on bootloader
edit2:
So after I came home I found de RUU post.
So here are some questions:
Mosts of the RUUs are in .exe extension, so I think that's the ones I should be looking for.
Can I download any version?
I'm currently downloading de WWE Asia version since my phone came from India. Only English (india) was available from stock, but I will not try to do anything before I'm sure of what to do.
When I plug the usb cable the bootloader changes to USB bootloader (or something like that). From the little that I found aboutt RUU I should run with the phone on that condition. Is that correct?
Thanks again, and sorry for the constant editing
Really sorry for double posting, but I need to update.
I managed to install the RUU. The program worked fine and I got the confirmation of installed rom, but when the phone rebooted it got stucked on the bootloop again.
Can this be a hardware problem? Is there anything else that I can do having access only to bootloader?
Okay, it is a hardware problem. The RUU wipes everything clean and installs a new system, and as it does not seem to help, the problem is definitely in hardware side.
After I was almost giving up I tried a different version of the RUU and the phone booted!
I already rebooted it a few times and it seems ok.
Thanks for the help jkoljo!
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
jkoljo said:
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
Click to expand...
Click to collapse
I used the Asia_WWE_1.32.707.1
I was trying to use a 1.72 version and still got the bootloop, but the asia version worked just fine.
I´m really glad the phone is working now, the only downside is that I´m back to the stock rom.

Only Have Access to Bootloader (HBOOT & Fastboot)

Hi there,
The other day I decided to S-OFF, root, and flash a custom ROM on to my HTC Desire handset. It all seemed to go perfectly well. I could access HBOOT, Fastboot, Recovery (4EXT), and I could boot into the custom ROM. It worked absolutely fine for approximately 24 hours. Then, the phone restarted and I can't get past the splash screen.
I am able to access the Bootloader (HBOOT, Fastboot etc.) but I cannot boot into the ROM or into Recovery.
I followed the instructions (step 2) found here: http://forum.xda-developers.com/showthread.php?t=1275632&highlight=can+t+get+past+hboot
I've tried using Method 1 and Method 2. And, although the process appears to be successful (according to Android Flasher's and cmd's response) but I'm still unable to get past the splash screen or access the recovery.
I thought that perhaps it did work fine and that it was just the recovery image I was using so I downloaded the latest Clockwork Mod Recovery image from their website. Unfortunately, this hasn't made any difference.
I used Fastboot to wipe the userdata, system, recovery, and cache but this has still not made a difference.
Does anyone have any ideas or is it busted?
Would flashing a RUU potentially resolve the issue (although, ideally, I don't want to do that and it would be a last resort).
Many thanks in advance.
This problem didn't appeared on its own, did it?
Probably you did something wrong. I suggest you to use RUU and start all over again.
Remember to downgrade your hboot first
Sent from my HTC Desire using xda app-developers app
paolo-red1 said:
This problem didn't appeared on its own, did it?
Probably you did something wrong. I suggest you to use RUU and start all over again.
Remember to downgrade your hboot first
Click to expand...
Click to collapse
Hi paolo,
Well, as I explained, it did all appear to be fine. I didn't do anything else to the phone when it started rebooting. But, clearly, something has gone wrong somewhere.
I've downgraded the HBOOT, and used the RUU. It looks to be sorted now.
Thanks for your help.
Glad that you solved your problem. Cheers

4.0.4 OTA update problem

I tried all day to update my One X to 4.0.4.The phone was rooted but stock.Tried putting the stock recovery, but a red triangle appears in recovery, after that i tried locking the bootloader , but with no succes. I don't know what i'm doing wrong.Please help..
deusexisagod said:
I tried all day to update my One X to 4.0.4.The phone was rooted but stock.Tried putting the stock recovery, but a red triangle appears in recovery, after that i tried locking the bootloader , but with no succes. I don't know what i'm doing wrong.Please help..
Click to expand...
Click to collapse
Sounds a bit of a mess. If I were you I would run the RUU to get back to stock, update OTA and then re-root again.
dr9722 said:
Sounds a bit of a mess. If I were you I would run the RUU to get back to stock, update OTA and then re-root again.
Click to expand...
Click to collapse
I am having the same problem. Tried all day yesterday. Also tried installing the RUU and that failing install as well for me. I have another thread with some details of the error I get in recovery. Basically Here is the info
Get the details of install
Gets downto verifying current system...
Assert failed: apply patch check /system /app/7digital3.apk
E:error in //internal_sdcard/download/ota (file)
Status 7
Installation aborted
So was there a problem with htc servers corrupting the downloads yesterday. Just a question when I see two now with the same issue in updating.
Have the same problem with OTA update from 1.29.401.12 to 2.17.401.12 fail.
Have tryed to remove CID check as have worked with earlier OTA, that dosnt work on this.
RUU also fail with aborted installation as mention over here, but I have had error with all RUU since I got One X 6 monts ago.
Same here, i tried to change name update.zip,asserts but it doesnt work.It says "assert failed: check_cid(get prop("ro.cid"),......."
I think its because u guys remove the bloatware from the system. Ota update need the bloatware even if u r rooted
Sent from my HTC One X using xda app-developers app
Just run your stock rom, flash your stock recovery. You can enter recovery when you see the phone & red triangle just push vol up + power button. You see some errors also. No problem. It's because stock recovery can not mount your sd !
Just boot into your stock rom with stock recovery, bootloader can stay UNLOCKED.
update your phone with the software update program and it should update fine, did this myself last night. After that you can flash the custom recovery and run a custom rom again if you want.
Verstuurd van mijn HTC One X
Can't get OTA to (re)install itself on HTC One X
MarcelHofs said:
Just run your stock rom, flash your stock recovery. You can enter recovery when you see the phone & red triangle just push vol up + power button. You see some errors also. No problem. It's because stock recovery can not mount your sd !
Just boot into your stock rom with stock recovery, bootloader can stay UNLOCKED.
update your phone with the software update program and it should update fine, did this myself last night. After that you can flash the custom recovery and run a custom rom again if you want.
Verstuurd van mijn HTC One X
Click to expand...
Click to collapse
Hi, there I have an HTC One X, relocked, with RUU put back on, but it is the last OTA: OTA_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10-1.26.707.4_release_2571341oc2x91f61pch2z9
That caused the problems as FOTA. My touchscreen now randomly does not accept any inputs.
All because the FOTA was applied while loading the battery, stupid of me of course but s..t happens,right.
So all I want to do now is applying last OTA again. Read all forum updates, but no real solution.
Tried the above, put the ota on de sdcard, even renamed it to update.zip and also on card, but when in stock recovery none of the options seem to pick it up or work.
The RUU succesfully applied was:
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
And yes it was bought in Singapore:angel:
I could unlock it again and I tried running Maximus V2.2 but the same annoying touchscreen problem.
And yes i tried the option not to go to sleep when loading on charger but didn't help either.
Who can help, or do I wait for the FOTA of Jelly Bean coming this month from HTC (or so it is stated on many websites)?
Thanks for any help in advantage!:good:
TRobdeV said:
Hi, there I have an HTC One X, relocked, with RUU put back on, but it is the last OTA: OTA_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10-1.26.707.4_release_2571341oc2x91f61pch2z9
That caused the problems as FOTA. My touchscreen now randomly does not accept any inputs.
All because the FOTA was applied while loading the battery, stupid of me of course but s..t happens,right.
So all I want to do now is applying last OTA again. Read all forum updates, but no real solution.
Tried the above, put the ota on de sdcard, even renamed it to update.zip and also on card, but when in stock recovery none of the options seem to pick it up or work.
The RUU succesfully applied was:
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
And yes it was bought in Singapore:angel:
I could unlock it again and I tried running Maximus V2.2 but the same annoying touchscreen problem.
And yes i tried the option not to go to sleep when loading on charger but didn't help either.
Who can help, or do I wait for the FOTA of Jelly Bean coming this month from HTC (or so it is stated on many websites)?
Thanks for any help in advantage!:good:
Click to expand...
Click to collapse
hi i have a similar issue how did u manage to sought the problem of screen

[Q] Nexus 7 (2013) fails OTA update to 5.01 with Android Error

My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.

Unable to Install OTAs After Returning To Stock

Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
Click to expand...
Click to collapse
I have the same problem
I actually was about to start a new thread near exact to yours.
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
Click to expand...
Click to collapse
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I don't want to flash it manually, and I want it to be able to install OTAs normally because I'm trying to sell it to a friend and don't want them to constantly to be seeing a "Update Available" notification that wont go away.
Nothing? No ideas? ......Anyone?
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I tried this using ADB sideload, got "signature error"??

Categories

Resources