My phone is S-OFF, if i want to unlock the bootloader and choose yes in the bootloader unlocking screen of the phone the phone does not reboot, i have to choose no i order to reboot the phone.
When i was S-ON that was not the case by choosing yes to unlock the bootloader it reboot automaticly.
Does any one knows why?
naelmnael said:
My phone is S-OFF, if i want to unlock the bootloader and choose yes in the bootloader unlocking screen of the phone the phone does not reboot, i have to choose no i order to reboot the phone.
When i was S-ON that was not the case by choosing yes to unlock the bootloader it reboot automaticly.
Does any one knows why?
Click to expand...
Click to collapse
why on earth you want to do unlock after SOFF ???
once you do unlock over SOFF ..if you relock you will have relocked rather than locked ..which you dont want that
if you are having trouble using fastboot flash commands (having error remote not allowed)
then you can just flash the juopunutbear HBOOT
here get the pyramid ICS one from this link
and flash the hboot using these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip jb_hboot.zip (ignore the progess bar on the screen)
fastboot reboot-bootloader
thats all ..you will have a complete unlocked hboot (pink *juopunutbear*)
then you can use the fastboot flash commands as usual
ganeshp said:
why on earth you want to do unlock after SOFF ???
once you do unlock over SOFF ..if you relock you will have relocked rather than locked ..which you dont want that
if you are having trouble using fastboot flash commands (having error remote not allowed)
then you can just flash the juopunutbear HBOOT
here get the pyramid ICS one from this link
and flash the hboot using these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip jb_hboot.zip (ignore the progess bar on the screen)
fastboot reboot-bootloader
thats all ..you will have a complete unlocked hboot (pink *juopunutbear*)
then you can use the fastboot flash commands as usual
Click to expand...
Click to collapse
Ok i just want to know why it is not rebooting after choosing unlock when it is s-off, and rebooting when it is s-on?
Hi folks,
My DS is currently running ViperSaga, and it's affected by a camera bug which is supposedly fixed by swapping my radio version (10.08.04_M) to the one from the ICU RUU. Since I'm S-ON (though htcdev-unlocked -- of course, I will do 'fastboot oem lock' before proceeding any further ) and would prefer to stay that way, I'll simply need to flash the entire ICS RUU in order to upgrade my radio. However, my USB connection is not 100%, and it has a tendency to drop out after the phone has been connected for a random number of minutes (the phone then goes into charge-only mode and is no longer seen by adb). Obviously, it would be bad if this happened while running the official RUU.
My first thought was to flash the RUU manually (fastboot erase cache, fastboot oem rebootRUU, fastboot flash zip rom.zip), and if the USB were to cut out, to simply reconnect and re-issue the fastboot flash zip rom.zip command. However, I did some Googling and found that there was another way, namely to put the rom.zip onto a mSD card renamed to PG88IMG.zip (the same way you S-OFF folks flash your radios ) and to let hboot do the upgrade all on its own.
My question is this: when upgrading hboot (as I will, from 2.00.0002 to 2.02.0002), you are often asked to flash the image twice if you do it via fastboot oem rebootRUU. (hboot pre-update! please flush image again immediately). Does the PG88IMG.zip flasher in hboot understand this and does it automatically flash itself a second time if needed?. I.e.: is it safe to upgrade hboot through PG88IMG.zip?
Sorry for the long post, but I wanted to make sure I'm as clear as possible as this is my main phone and I'd rather not brick it (though being able to take 5MP pictures on ViperSaga would be nice )
Thank you for your help!
I've decided to follow the following procedure:
1) reboot into Linux (USB seems more stable there)
2)
Code:
fastboot oem lock
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
(repeat last command because the flasher asked me to, as expected)
fastboot reboot-bootloader
3) Allow the system to boot, enable USB debugging, adb reboot-bootloader
4) re-unlock bootloader
5) flash recovery, boot.img, and ViperSaga
All is well
It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux
you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131
I have not updated it, will go and do that now,
Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...
Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how
s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also
Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed
`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.
hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything
DEAR ALL,
I have tried to put a rom in my htc oneE8. i lost every thing.
My htc only booting in recovery . if i tried to boot in system it hnged up at htc logo for more than 6 hours.
please i need simple steps to get my phone back.
my phone is htc one E8. single sim - S-off.
:
flash this ruu for single sim E8
https://mega.co.nz/#!LQoSWThK!yWhYVzz5K3yFQUgpI2hV1c9VlFfeAxW2sKs72wBaVYg
follow these instructions
1. Rename file to RUU.zip
2. Place it in adb folder
3. Reboot phone to fastboot mode
4. S On need to relock bootloader (fastboot oem lock) , S Off lock not needed
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Run the following commands from your adb folder:
6.fastboot oem rebootRUU
7.fastboot flash zip RUU.zip
8.fastboot reboot
re
its always give me remote eroor
Which recovery does it boot into, Stock/ TWRP? Could you post your exact model?
I have been in fast boot current bootloader screen is hboot 3.19.0.0000 radio 1.12.20.1211 and os 4.17.605.9
Im S-off unlocked
with TWRP 3.0.2.0 installed
DarkCodedDragon said:
I have been in fast boot current bootloader screen is hboot 3.19.0.0000 radio 1.12.20.1211 and os 4.17.605.9
Im S-off unlocked
with TWRP 3.0.2.0 installed
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24052804347819109
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
So from here do I just pick any 5.01 rom and flash with TWRP.?? And I do have to reflash SU after this correct?
I got updated rom , still need to check SU after rom loads thanks