did you read the 1s post ????
you need to RELOCK the bootloader.
[TUT] How to upgrade HOX with a RUU(hboot.img, etc..) after installed a custom rom
- Thread starter GabrielSousa
- Start date
-
- Tags
- development
you need to RELOCK the bootloader.
Ok my bad i miss it.
But the question is, is possible i flash an europe RUU or run the RUU.exe from europe?
Cause with Asia_india i only get 1.28 at max.
Got it, so, to get the conclusions...
I can only do that when i got s-off to get SuperCID
am i Right ?
Well, with bootloader locked now i got
ERRO [140]: ERRO DA VERSÃO DO CARREGADOR DE BOOT
i'm with no luck! =[
ERRO [140]: ERRO DA VERSÃO DO CARREGADOR DE BOOT
i'm with no luck! =[
-1.unlock the bootloader again
-2.flash stock/original recovery (its on post #5)
-3.relock the bootloader
-4.run ruu file
flashed stock boot, stock recovery,
relocked
and still getting
ERRO [140]: ERRO DA VERSÃO DO CARREGADOR DE BOOT
=[
One should also be VERY careful that you have enough battery % left before you perform the RUU update. The software checks if your battery has sufficient voltage before it proceeds, otherwise it is impossible. And, if you have a custom ROM with a bootloader which has just been re-locked, you can get into trouble.
The reason is is that the phone will not boot into the custom ROM with a relocked bootloader, nor will your custom recovery (CWM or other) load and you will have no access to it in order to charge. You will be stuck in fastboot mode in which it's impossible to charge.
The following little script saved my ass when my battery was too low in order to even re-unlock the bootloader in order to get back into the custom ROM. (fastboot commands also check your voltage before it can perform a re-unlock).
Here's the script if you need to charge your battery if you're ever stuck in fastboot with a custom ROM, re-locked bootloader, and a low battery.
You need to create BATCH file that essentially reboots the phone every 6 or so seconds in order for the phone to turn off sufficiently long enough to accept a charge. (And, no, simply attempting to turn off the phone and plug it in turns on the screen in fastboot mode and it doesn't charge.) This was the ONLY way I could get enough charge to either re-unlock or perform an RUU update. Once your battery reaches around 1.68 V (1,680 mV), you should have enough charge to re-unlock it to charge normally the rest of the way so that you can again re-lock the bootloader and update with the RUU. Here is the script:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
The reason is is that the phone will not boot into the custom ROM with a relocked bootloader, nor will your custom recovery (CWM or other) load and you will have no access to it in order to charge. You will be stuck in fastboot mode in which it's impossible to charge.
The following little script saved my ass when my battery was too low in order to even re-unlock the bootloader in order to get back into the custom ROM. (fastboot commands also check your voltage before it can perform a re-unlock).
Here's the script if you need to charge your battery if you're ever stuck in fastboot with a custom ROM, re-locked bootloader, and a low battery.
You need to create BATCH file that essentially reboots the phone every 6 or so seconds in order for the phone to turn off sufficiently long enough to accept a charge. (And, no, simply attempting to turn off the phone and plug it in turns on the screen in fastboot mode and it doesn't charge.) This was the ONLY way I could get enough charge to either re-unlock or perform an RUU update. Once your battery reaches around 1.68 V (1,680 mV), you should have enough charge to re-unlock it to charge normally the rest of the way so that you can again re-lock the bootloader and update with the RUU. Here is the script:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Last edited:
flashed stock boot, stock recovery,
relocked
and still getting
ERROR[140]: BOOTLOADER VERSION ERROR
Please someone can help me ?
that was exactly where I get confused & thinking about..
How will we extract rom.zip & cook a stock rom to be flashed?!
for example my CID is : HTC__J15
And i have already used a week or two ago : "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" to get back to stock and wait for OTA... but now running ARHD like written in my sig.
now what will I do??
I am really curious about updating radio & hboot through OTA or RUU since Mike is still not very sure about if his ARHD already updated those or not...
http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
ATTENTION dont flash rom.zip on recovery.
you have to cook the rom.zip on dsixda
i will make for you a stock custom rom, for you to try, give me 1 or 2 days
okay I googled dsixda but now I am stuck....it appears to be a unix script :S is there anyway to run it from windows because I don't have access to linux atm....
do you have a custom kernel ?
did you flash the stock KERNEL ?
This sucks, anyway I got the rom.zip for my phone (cid vodap102) but inside was a text document which said the cid was vodap110 !?yeah, its a unix app
Guys does anyone know what is the RUU for VODAP102? I know it is vodafone Germany but finding it hard to figure out what is the original ruu file name from the shipped rom collection thread. Can someone please tell me what file I need to download for voda Germany?
Sent from my HTC One X using Tapatalk 2
Sent from my HTC One X using Tapatalk 2
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone