Related
Have been getting this error of late after i run unrevoked, then when i go to recovery to flash rom i get this error...is there any solution to this, or is there a new version of unrevoked to solve this porblem? Im using unrevoked v3.32.
Thank you.
Phone details? recovery version? Which Rom?
davebugyi said:
Phone details? recovery version? Which Rom?
Click to expand...
Click to collapse
Unfortunately i gave the phone back to a friend who need help, so cant provide any info
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
lowkey1979 said:
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
Click to expand...
Click to collapse
Do you have a pvt4-desire? If, you have to flash amonra-recovery, because cwm is incompatible with pvt4-desires.
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
ghalalb said:
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
Click to expand...
Click to collapse
Can you tell me how to flash recovery with fastboot?
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
MatDrOiD said:
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
Click to expand...
Click to collapse
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
andrew21 said:
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
Click to expand...
Click to collapse
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
hi mates,
to flash recovery with fastboot need to be s-off.
the command are really simple.
boot in hboot, select fastboot (shoul see fastbbot usb on the phone screen)
open a command line
Code:
fastboot flash recovery c:/wheretefileis/yourecovery.img
MatDrOiD said:
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
Sir,
I tried this method but i get a "flash_image: not found". It seems like i don't have the flash_image command on my phone. I've looked everywhere to find a way to get that command and i found this - http://www.villainrom.co.uk/forum/s...)
finished. total time: 1.094s
Thank you sir
chage a sd card for try!
zk7513153 said:
chage a sd card for try!
Click to expand...
Click to collapse
Already did change the sdcard sir.
On another note, whenever i tried remounting the /system for RW access to copy flash_image, free space drops to Zero Kb. To isolate, i tried remounting to just Read access, free space remained the same. Anything I'm missing here, or do I really have to S-OFF my phone before I can make changes on my /system ?
Thank you very much.
nonofficialcover said:
I also tried flashing via ADB and I get this:
C:\fastboot flash recovery c:\recovery-RA-desire-v2.0.1.img
sending 'recovery' (3936 KB)...
OKAY [ 0.687s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.094s
Thank you sir
Click to expand...
Click to collapse
For this part I think you need to disable signature verification in recovery.
I was able to solve my problem after I did S-OFF.
Hi,
I'm trying to root my phone here, but I'm stuck when trying to flash my phone to hboot 1.39.
My CID number is HTC__Y13, so I know I have downloaded the correct one.
I'm following this guide:
http://forum.xda-developers.com/show...ostcount=29305
So when I try to flash I get this message:
C:\Android>fastboot flash zip 3.14.401.31.zip
sending 'zip' (12876 KB)...
OKAY [ 1.533s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 2.613s
Any help would be appreciated since I'm now unable to use my phone!
Thanks
So fastboot command
Fastboot getvar version-main
Gives you 3.14.401 ?
And you need to rename the 3.14.40.zip to just "firmware.zip"
Then :
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Mr Hofs said:
So fastboot command
Fastboot getvar version-main
Gives you 3.14.401 ?
And you need to rename the 3.14.40.zip to just "firmware.zip"
Then :
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Hi!
Thanks for your reply. I thing we're into something here.
I get: version-main: 3.20.401.1
What can I do about that?
Nothing you cant upgrade the hboot. You have the highest available. What do you want to achieve ?
Check the bootloader and read what your hboot number is !
Mr Hofs said:
Nothing you cant upgrade the hboot. You have the highest available. What do you want to achieve ?
Check the bootloader and read what your hboot number is !
Click to expand...
Click to collapse
I'm trying to root it and put in Android revolution HD 21.0
How can I check the bootloader? It's been a while since I've done this. I've allready unlocked the booloader via htcdev. no problem.
Hold the power button & volume down button in together until you see the bootloader.
You only need to flash a custom recovery, flash the boot.img from the new custom rom, perform a full wipe in recovery and then install the new rom.zip
Mr Hofs said:
Hold the power button & volume down button in together until you see the bootloader.
You only need to flash a custom recovery, flash the boot.img from the new custom rom, perform a full wipe in recovery and then install the new rom.zip
Click to expand...
Click to collapse
Ok. I'll try that again. I did it once or twice before, and was unable to get in to recovery mode afterwards. That's why I was following this hboot track now. But I'll give it a try. Thanks.
Damn.. same as last time. When I select "Recovery" from the bootmenu, I only get a icon of a phone with a red warning sign over it. And nothing else happends
I must be doing something wrong
You need to flash a custom recovery first. I think you stil have the stock one
http://db.tt/H7m4ffIP
Flash this one . Rename it to recovery.img
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Then enter the recovery.
YES!! thank you!!
No problem ! :thumbup:
roy-arne said:
YES!! thank you!!
Click to expand...
Click to collapse
Hmm, it aborts the installation at 30% when extracting files, or maybe just when it's done. And I'm thrown back to the main menu, without any error msg.
I ran a "Wipe Data /Factory Reset" before i ran the installation. "Clean to install a new ROM"
Then I ran the installation and selected full wipe there as well..
Any clues, or suggestions to where I can find a log?
EDIT: Log found:
I: Checking for extendedcommand & openrecoveryScript....
I: Skipping execution of extendedcommand, file not found....
I: skipping execution of OpenRecoveryScript, file not found.....
Not sure this has anything to do with the installation as it did not seem to match the log that it was tailing while installing but could be something.
I always wipe myself
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache,data,system
Then install the new rom.zip. did you check the download and MD5 checksum ? Maybe a bad download
I've downloaded the file one more time just to be sure.
Still same error. From the log:
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Warning: No file_contexts
I:device_recovery_start()
I:Cannot open /data/philz-touch/philz-touch_5.ini
Seems like it's not finding something / can't get access to something.
Maybe I'll try with an earlier build. This was obviously out yesterday.
Weird never had this with installing roms.
http://db.tt/t6RTcTwK
This one is a bit older.
You can use a different cwm non touch recovery, but......then the touch screen in the recovery won't work and also no touch in the aroma installer. Then you must navigate with the volume buttons and power button.
Mr Hofs said:
Weird never had this with installing roms.
http://db.tt/t6RTcTwK
This one is a bit older.
You can use a different cwm non touch recovery, but......then the touch screen in the recovery won't work and also no touch in the aroma installer. Then you must navigate with the volume buttons and power button.
Click to expand...
Click to collapse
Thanks. I'll try that. I flash that as recovery right?
Yes sir
I'm using this one too, never had an issue
Mr Hofs said:
Yes sir
I'm using this one too, never had an issue
Click to expand...
Click to collapse
Giving it a try. This one is touch as well, and seems newer than the first one you gave me?
Crap. same error. It just aborts at a random place in the installation
Try another rom !
Ow yeah sorry, I miss numbered my links there fore a moment.
Try this one then
http://db.tt/qRPa0buS
Completely non touch .....use the volume and power buttons to navigate
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
eggyfish said:
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
Click to expand...
Click to collapse
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
eggyfish said:
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
Click to expand...
Click to collapse
There is a newer version (2.8.7.1-CPTB-B1) which can be found in the beta version section here. Furthermore there is a stock backup provided in this thread that corresponds to your firmware version. Try to update TWRP and then to restore the backup.
Edit (Just to answer my own question from my previous post): The second Link provides a 1.40.401.8 RUU, too.
Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
and i still cant flash twrp
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
eggyfish said:
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
Click to expand...
Click to collapse
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
eggyfish said:
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
Click to expand...
Click to collapse
I actually don't see any error in that output. Everthing is the way it should be.
Flippy498 said:
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
I actually don't see any error in that output. Everthing is the way it should be.
Click to expand...
Click to collapse
hmm, thats strange as it didnt update, i get the same readout when i flash stock, but it stsys on twrp. sureley it cant be full as a ruu flash wipes your data, i think i'll try get a repair from htc, thanks for your help
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
nobody?? :'(
Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1
Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk
I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse
bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU
So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip
Hi guys!
My HTC one M9 was rooted, running Android 5.0.2 and i had Twrp recovery set up.
Since i was S-On and i'm a total noob/asshat i never tried to load any rom or mods onto my system =)
Now i wanted to try and get back to stock, so i could receive OTA updates, and after getting Nougat (even if i had to wait a long time for it), then i'd just root again and enjoy the lack of bloatware.
In this order i:
-Unrooted through the SuperSu
-Checked to see if it was unrooted using rootchecker
-Found my stock recovery mode here: http://forum.xda-developers.com/one...collection-t3132698/post61286815#post61286815
-Went to ADB, opened the command prompt
-Went to download mode
-entered fastboot flash recovery HIMA_UHL_Stock_Recovery_1.32.401.15.img
From there, i took my phone and on the phone itself tried to go to recovery mode to check..
The screen went black, it went to (the stock!!!) recovery mode, but now the system can't reboot.
I've seen the same question asked, but not for S-On phone or done in about the same way i did..
My info:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
There are recovery logs on my phone but they are very long and i honestly don't know how or if i can retrieve them through ADB, if any of you should think it necessary and can tell me what command to put in, i'll bring them up right away!
thanks alot for your time, i'm very sorry to bother you with this
Edit: after encountering the issue, i tried wiping the cache partition and factory reset options but to no avail.
flashed twrp recovery back in, no change.
So, you found the correct stock recovery in my thread and didn't read the warning above the download links? Since I'm currently revamping the thread, it would be nice if you could tell me why you didn't read it. Was it to small? Was the colour unreadable? (This is a serious question. I'm not making fun of you. I really need to know that for being able to improve the thread.)
Flash a 401 RUU. Instructions and download links can be found in the same thread.
Sent from my HTC One M9 using XDA Labs
*made mistake, please ignore*
Flippy498 said:
So, you found the correct stock recovery in my thread and didn't read the warning above the download links? Since I'm currently revamping the thread, it would be nice if you could tell me why you didn't read it. Was it to small? Was the colour unreadable? (This is a serious question. I'm not making fun of you. I really need to know that for being able to improve the thread.)
Flash a 401 RUU. Instructions and download links can be found in the same thread.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Sorry man.
You can see from the time it was between 3 and 4 AM =D
I read all your info, i just read it all again, but for some reason i didn't pay attention to
"Read the Backup or the RUU tab of my google sheet if you want to be able to receive and install OTAs, again.
Simply unrooting your device and reflashing the Stock Recovery is not enough due to the block-based OTAs."
I honestly have no *cursing* idea why that didn't register in my brain.
My apologies in any case. Your thread is fine, it's the most helpful i've come across for my phone in days.
I never flashed anything before, and i knew absolutely **** (not that i know alot right now =D but at least i'm learning). Without your thread, i'd probably still be looking.
i flashed the stock recovery (HIMA_UHL_Stock_Recovery_1.32.401.15) back on, got 1.32.401.15 Ruu from your thread
unfortunatly i don't have an SD card.
I tried flashing from platform tools the 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip file
but got this message:
C:\Users\pc\Desktop\platform-tools>fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SENSE
70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_4268
91_signed.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2189252987 is not a multiple of
the block size 4096
OKAY [ 1.053s]
writing 'zip'...
(bootloader) HOSD CL#506785
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.076s
i think the guy here http://forum.xda-developers.com/one-m9/help/urgent-help-bricked-htc-one-m9-t3138987
had the same issue so i'm trying to solve from here, and if not i'll go out and buy an SD card, though i don't know if that'll work, my computer doesn't see my phone at the moment
As written in my thread you can't flash M9 RUUs with fastboot. You need HTC_fastboot.
Sent from my HTC One S using XDA Labs
Flippy498 said:
As written in my thread you can't flash M9 RUUs with fastboot. You need HTC_fastboot.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So i tried, i changed adb fastboot to the htc_fastboot.exe and now i get this:
C:\Users\pc\Desktop\platform-tools>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_L50_S
ENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_
426891_signed.zip
sending 'zip'... (101066 KB) OKAY
sending time = 7.986 secs
writing 'zip'... (bootloader) HOSD CL#506785
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 9(s)
Okay! edit: i'm an idiot. i put things back in order, downloaded htc_fastboot from here: http://d-h.st/6LC (thanks brandon gunderson) and tried again.
Unfortunatly now i get this:
C:\Users\pc\Desktop\htc_fastboot>htc_fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SEN
SE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_42
6891_signed.zip
htc_fastboot wordt niet herkend als een interne
of externe opdracht, programma of batchbestand.
(it means: htc_fastboot is not recognized as an internal or external command, program or batch file)
still an idiot. No idea what's wrong
you said in the thread:
Important Notes:
I won't support flashing RUU.exe files or flashing RUU.zip files via HTC_fastboot in this thread. There have been too many reports of people having problems with these methods. Trying to find the reason for the problems can be quite frustrating and time-consuming. The SD card method on the other hand is much easier and less time-consuming than searching for user errors if the other methods fail.
If you only have a RUU.exe at hand you can extract the *.zip file using these instructions. Although they're a bit older they can still be used with M9 RUUs.
so i went to that other thread to find out how i could do it
Yeah, I wrote that part because of all the problems that arise most of the times if people try to flash RUUs via fastboot and all the risks that are connected with this method. As you can see your try isn't an exception.
The bootloader needs to be locked or re-locked if you use the HTC_fastboot method. However, I don't recommend doing so if you aren't 100% sure that you can flash the RUU without any issues afterwards. If your phone isn't completely stock your phone won't boot anymore after it got (re-)locked. That is a security feature that prevents the phone from getting bricked if anything is modified. You can't even enter TWRP, anymore, in that situation if it's installed. In addition it's impossible to re-unlock the bootloader if your phone is S-ON and the option "OEM Unlock" isn't activated in the developer options. (Sidenote: The option got introduced with firmware 2.x. So in your current situation re-locking is safe. However, as soon as you updated your phone to a higher firmware version you shouldn't do it unless you know that you have a working RUU at hand and you know that you are able to flash it.)
Flippy498 said:
Yeah, I wrote that part because of all the problems that arise most of the times if people try to flash RUUs via fastboot and all the risks that are connected with this method. As you can see your try isn't an exception.
The bootloader needs to be locked or re-locked if you use the HTC_fastboot method. However, I don't recommend doing so if you aren't 100% sure that you can flash the RUU without any issues afterwards. If your phone isn't completely stock your phone won't boot anymore after it got (re-)locked. That is a security feature that prevents the phone from getting bricked if anything is modified. You can't even enter TWRP, anymore, in that situation if it's installed. In addition it's impossible to re-unlock the bootloader if your phone is S-ON and the option "OEM Unlock" isn't activated in the developer options. (Sidenote: The option got introduced with firmware 2.x. So in your current situation re-locking is safe. However, as soon as you updated your phone to a higher firmware version you shouldn't do it unless you know that you have a working RUU at hand and you know that you are able to flash it.)
Click to expand...
Click to collapse
thank you very much man.
i know questions like this must annoy you, and i'm very sorry for bothering you. I'm learning though =)
At this point, after the failed attempts to flash, is it still possible for me to use an SD card? If so i'm going to get one right away.
My worry is, though, that since my phone doesn't register on my computer, how i'll get the file on the SD card... I'm thinking i'll pass by a friend, put it in his phone, load the file on the SD card, put the card in my phone again, change recovery back to twrp and try to flash from there?
Please read the instructions for the SD card method. Chances are high that it's not possible to copy the RUU onto the SD card while it's put into the phone. You probably need a SD card reader.
The SD card method is completely independent of the fastboot method. And as long as the fastboot method fails completely (as in your situation) chances are high that you can still recover your phone with the other method.
Sent from my HTC One S using XDA Labs
Flippy498 said:
Please read the instructions for the SD card method. Chances are high that it's not possible to copy the RUU onto the SD card while it's put into the phone. You probably need a SD card reader.
The SD card method is completely independent of the fastboot method. And as long as the fastboot method fails completely (as in your situation) chances are high that you can still recover your phone with the other method.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
things aren't going well for me today.
I have an SD adapter for micro SD that i can plug into my laptop. I renamed the Ruu zipfile "0PJAIMG.zip", that is the name (in the name i included .zip, that's supposed to be like that, no?)
I put off my phone, put the card in, rebooted to download mode.... Nothing.
tried to boot, it failed (of course), then i got the following menu:
Reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
i tried the "apply from sd card" option but it says:
fail to open file: /sys/devices/platform/android_usb/host mode
Wrtie host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
E: Find no match PARTITION for package path /sdcard/ptt.zip
E: unknown volume for path
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package...
E: failed to map file
i tried flasing from the twrp recovery (install, from SD card-. Received the following:
Updating partition details....
.... done
Full SELinux support is present.
Installing '/external_sd/0PJAIMG.zip.zip"...
Checking for MD5 file....
Skipping MD5 check: no MD5 file found
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/0PJAIMG.zip.zip'
Updating partition details...
... done
FAILED
the SD card is a 32GB Samsung SD card (MB-MC32D model), and it's FAT32
any idea what went wrong? (also, i seem to have hit my max "thank you!" 's i can give out today, i'll be sure to thank any replies that are left tomorrow!)
Fatimiyye said:
things aren't going well for me today.
I have an SD adapter for micro SD that i can plug into my laptop. I renamed the Ruu zipfile "0PJAIMG.zip", that is the name (in the name i included .zip, that's supposed to be like that, no?)
I put off my phone, put the card in, rebooted to download mode.... Nothing.
tried to boot, it failed (of course), then i got the following menu:
Reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
i tried the "apply from sd card" option but it says:
fail to open file: /sys/devices/platform/android_usb/host mode
Wrtie host_mode error
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
E: Find no match PARTITION for package path /sdcard/ptt.zip
E: unknown volume for path
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package...
E: failed to map file
i tried flasing from the twrp recovery (install, from SD card-. Received the following:
Updating partition details....
.... done
Full SELinux support is present.
Installing '/external_sd/0PJAIMG.zip.zip"...
Checking for MD5 file....
Skipping MD5 check: no MD5 file found
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/0PJAIMG.zip.zip'
Updating partition details...
... done
FAILED
the SD card is a 32GB Samsung SD card (MB-MC32D model), and it's FAT32
any idea what went wrong? (also, i seem to have hit my max "thank you!" 's i can give out today, i'll be sure to thank any replies that are left tomorrow!)
Click to expand...
Click to collapse
so yeah. I'm an idiot. thought i wasn't, but i am.
named it 0PJAIMG without the '.zip' at the back and worked fine. Hope i can install OTA's now
Fatimiyye said:
so yeah. I'm an idiot. thought i wasn't, but i am.
named it 0PJAIMG without the '.zip' at the back and worked fine. Hope i can install OTA's now
Click to expand...
Click to collapse
Yes, OTAs shouldn't be a problem now.
Well, we all make mistakes. You live and learn.
Flippy498 said:
Yes, OTAs shouldn't be a problem now.
Well, we all make mistakes. You live and learn.
Click to expand...
Click to collapse
Thank you very much for your help man =)
The whole thing is stock now, took hours to update it all but i'm on the latest update available here for marshmallow, so i'm quite pleased.
from what i've gathered it's not possible for me to flash Nougat without S-OFF so i'll very likely keep notes on how i did this, and either wait for nougat before re-rooting, or get S-OFF and hurt my (and maybe your) head again trying to get my phone the way i want it xD
cheers man! <3