I want to downgrade my bootloader so that TWRP will work again since I havent succeeded in getting it to work on the latest bootloader. However when I try to downgrade the bootloader fastboot gives me an "invalid bootloader" error.
nixcamic said:
I want to downgrade my bootloader so that TWRP will work again since I havent succeeded in getting it to work on the latest bootloader. However when I try to downgrade the bootloader fastboot gives me an "invalid bootloader" error.
Click to expand...
Click to collapse
As long as they are the same bootloader revision yes. Or if your bootloader is unlocked you can flash any firmware you like for your device
nixcamic said:
I want to downgrade my bootloader so that TWRP will work again since I havent succeeded in getting it to work on the latest bootloader. However when I try to downgrade the bootloader fastboot gives me an "invalid bootloader" error.
Click to expand...
Click to collapse
What firmware are you on now and what are you trying to downgrade to? You're being very vague in your question
Related
sorry it was a fail but will keep working
S-ON will not allow them to be flashed. Not even with a goldcard
HOW CAN WE DOWNGRADE THE BOOTLOADER. i can get teh RUUs to go but quits when it detects the bootloader.
malibu_23 said:
HOW CAN WE DOWNGRADE THE BOOTLOADER. i can get teh RUUs to go but quits when it detects the bootloader.
Click to expand...
Click to collapse
If Nand can be unlocked (S-OFF) then the bootloader can be downgraded but that's the initial hurdle is finding a way since the bootloader is encrypted
I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.
Did you flash a signed stock recovery before locking the bootloader?
reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s
touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification
touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.
i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards
blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.
khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Good evening,
I completed the HBOOT downgrade found in the developer forum with no issues. Once on 1.06, I attempted to unlock the bootloader and it did not work. The bootloader unlock screen appears but once the phone reboots the bootloader remains relocked. I ran two RUUs (1.09 and 1.14 respectively) but I am still plagued by the relocked bootloader. I noticed my device ID changes with each attempt. I read the entire downgrade forum but none of the solutions helped me. Please assist.
Thank you
chanoelmano said:
Good evening,
I completed the HBOOT downgrade found in the developer forum with no issues. Once on 1.06, I attempted to unlock the bootloader and it did not work. The bootloader unlock screen appears but once the phone reboots the bootloader remains relocked. I ran two RUUs (1.09 and 1.14 respectively) but I am still plagued by the relocked bootloader. I noticed my device ID changes with each attempt. I read the entire downgrade forum but none of the solutions helped me. Please assist.
Thank you
Click to expand...
Click to collapse
Em I'm sure you can't downgrade with a locked bootloader. The only thing that comes to mind is to keep trying, I had to do it a few times myself.
I completed the downgrade. I wish to unlock the bootloader. I flashed the RUUs to see if they would allow me to do so on a different HBOOT
chanoelmano said:
I completed the downgrade. I wish to unlock the bootloader. I flashed the RUUs to see if they would allow me to do so on a different HBOOT
Click to expand...
Click to collapse
I still don't see this is even possible without the bootloader being already unlocked.
My bootloader was unlocked before I downgraded. I had to lock it so that I could flash RUU. I am now having trouble unlocking it again.
chanoelmano said:
My bootloader was unlocked before I downgraded. I had to lock it so that I could flash RUU. I am now having trouble unlocking it again.
Click to expand...
Click to collapse
Why did you flash the RUU? there was no need for that. All I can say is keep trying. What was you Hboot before downgrading?
good luck mate i have the same problem and i can't do anything
My hboot was 1.14 I was having radio issues so I downgraded. Once on 1.06 I could not get my bootloader unlocked so I flashed RUUs to see if I could work from there.
Even now nothing has helped you?
I think you messed it up with running the RUU when there was no need too. Maybe try getting the JB OTA update and try again after.
Very well. Do you know where I can obtain the JB update? I
chanoelmano said:
Very well. Do you know where I can obtain the JB update? I
Click to expand...
Click to collapse
By running a RUU and just wait in till you get the update.
alexskin said:
good luck mate i have the same problem and i can't do anything
Click to expand...
Click to collapse
I continually flashed the unlock code and eventually I was able to unlock the bootloader.
my problem is that i can't get the token from htcdevs, i all ways get an error. i'll try with an old token and see if it works
Hello guys!
My story is short I had rooted and unlocked bootloader on Android 4.1.2. Then i want to update, so i get moonshine s-off, downgraded hboot, ran RUU and installed updates. Now i have 4.2.2 and sense 5 of course. And now is my problem. I don't have root! What should I do? I tried to flash twrp recovery by fastboot but i getting always the same failure:
FAILED (remote: not allowed). Every thoughts about it?
When you RUUed you had to relock your Bootloader
Unlock your bootloader again then either boot twrp recovery or flash it
Then flash root again
russellvone said:
When you RUUed you had to relock your Bootloader
Unlock your bootloader again then either boot twrp recovery or flash it
Then flash root again
Click to expand...
Click to collapse
I unlocked bootloader (by htcdev of course), then i flashed superuser. Should working fine, but Titanium Backup told me that don't have root rights...
PS. Of course, after unlock i flashed TWRP
PPS. Problem solved, just flashed SuperSU instead of superuser Big thanks!
Awesome
Hi,
I have little problem... I unlocked bootloader by HTCdev, S-offed by JuopunutBear 0.5b (with wire-trick) and install unbranded firmware RUU 3.32.401.5. Now I'd like to flash CWM recovery, but I receieve an error "writing 'recovery'... failed (remote: not allowed)"... I also tried to flash it by KGS Utility v8 and this didn't work for me. Can I unlock bootloader again by bin file generated by HTCdev? Somewhere who wrote that it possible to brick the phone, but few people did it and nothing happened. What can I do? Any ideas?
Greets.
caris said:
Hi,
I have little problem... I unlocked bootloader by HTCdev, S-offed by JuopunutBear 0.5b (with wire-trick) and install unbranded firmware RUU 3.32.401.5. Now I'd like to flash CWM recovery, but I receieve an error "writing 'recovery'... failed (remote: not allowed)"... I also tried to flash it by KGS Utility v8 and this didn't work for me. Can I unlock bootloader again by bin file generated by HTCdev? Somewhere who wrote that it possible to brick the phone, but few people did it and nothing happened. What can I do? Any ideas?
Greets.
Click to expand...
Click to collapse
actually why did you use a ruu.exe for flashing a custom recovery?
it was an unecessary step
nevermind
if you still are on S-OFF flash 3.33 iniversal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then you can install a custom recovery
another way is to install 4ext updater(link in my signature)
from the app download and install the latest version of 4ext recovery
edit: just to know when you are locked or relocked you are limited to some fastboot commands
I was flashed RUU because I wanted to delete Orange PL brand. Yep, I'm still on S-Off.
Can I flash by fastboot "PG58IMG 3.32 unlocked.zip" file (~14MB) to my firmware what I have now? It may unlock bootloader?
caris said:
I was flashed RUU because I wanted to delete Orange PL brand. Yep, I'm still on S-Off.
Can I flash by fastboot "PG58IMG 3.32 unlocked.zip" file (~14MB) to my firmware what I have now? It may unlock bootloader?
Click to expand...
Click to collapse
probably you can use it via fastboot command
but it would better to flash it directly from bootloader
I updated FW (PG58IMG.zip unlocked) via Bootloader, flashed CWM via fastboot tools and it works!
@rzr86, Thanks for advices. :good:
Greets.