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
Ok i can enter to the bootloader, and also to the recovery, but! when i flash a rom it cant boot on ! i got stucked after the HTC Logo. Also tried to to flash PD98IMG from hboot without succes and the same thing with RUU, in HBOOT the RUU software says that my battery is 30% or less and i have to chargue it, but is full! so have to enter in fastboot mode and it pass that step then it chargue the ruu but then it send an error that the image restore from ruu cant be completed.
Btw: S-on AND unlocked bootloader
i red about flash the boot.img from the ROM zip in fastboot? it work? how do i do it?
Killerin said:
Ok i can enter to the bootloader, and also to the recovery, but! when i flash a rom it cant boot on ! i got stucked after the HTC Logo. Also tried to to flash PD98IMG from hboot without succes and the same thing with RUU, in HBOOT the RUU software says that my battery is 30% or less and i have to chargue it, but is full! so have to enter in fastboot mode and it pass that step then it chargue the ruu but then it send an error that the image restore from ruu cant be completed.
Btw: S-on AND unlocked bootloader
i red about flash the boot.img from the ROM zip in fastboot? it work? how do i do it?
Click to expand...
Click to collapse
extract the boot.img file from the zip (do not extract the zip) to your PC desktop, then boot the device in fastboot usb and in a CMD session in the PC (located in the desktop folder) type:
Code:
fastboot flash boot boot.img
then when you get the OKAY, type:
Code:
fastboot reboot
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
i have htc one xl evita stuck on this build for devloper purpuse only i download xl tool and flash recovery twm 2.5.0 and come in recovery mode i flash cm 10.1 but now i want go to stock rom i dont found stock rom for same cid so i want super cid but i have s-on i want to s-off in cm 10.1 and twm 2.5.0 only working other recovery not working
Get rid of the toolkit, it's flashed an unusable version of TWRP that's full of bugs, and it'll only cause more problems. Download the latest version of TWRP here:
http://techerrata.com/file/twrp2/evita/openrecovery-twrp-2.8.5.0-evita.img
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC), connect your phone in fastboot mode (reboot to bootloader, connect usb cable, "fastboot usb" should now be displayed on the screen), open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0-evita.img
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have a good recovery version go and download the Kickdroid XL 5.0 ROM from here:
http://forum.xda-developers.com/showthread.php?t=2400766
Install that ROM with TWRP. Now you can go and get s-off here:
http://Rumrunner.us
Now you can flash whatever you like. But Kickdroid is actually a pretty good ROM, very close to stock but with some optimisations.
Transmitted via Bacon
thanks i s-off using rumrunners and flash with latest android 4.2.2
I've got a BIG problem with my new Pixel 5. I've successfully rooted it and had it operating for a day.
I then decided to boot into recovery mode just to see what the new stock recovery looks like (I used to use TWRP.).
BIG MISTAKE!
All I got was the error icon that I've seen in the past meaning that no recovery image is available. OK, so I try to just try to do a simple reboot. I'm taken back to the same place.
Now I try to reload Android. No luck! I'm stuck on:
"Device product is 'unknown'"
Update requires 'bramble'.
HELP!!!!
In the file android-info.txt, what would happen if I patched the line
require board=bramble
to
require board=unknown
Did you figure this out? I'm facing the same issue with my Pixel 5.
Edit: I figured it out. If you are having an issue with the 'flash-all.bat' command like we were, you just need to manually push the individual files and it should boot you back up into stock.
Run these commands:
1. fastboot flash bootloader <bootloader image file>
2. fastboot reboot-bootloader
3. fastboot flash radio <radio image file>.img
4. fastboot reboot-bootloader
5. fastboot update <image zip file>.zip
6. fastboot reboot
All of the reboot-bootloader commands may be redundant but it worked for me. It booted me into stock, verified I was unrooted with Root Checker, then proceeded to reboot back into the bootloader and 'fastboot flashing lock' to re-lock my bootloader and wipe the device.