I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Kyuubi10 said:
You soft-bricked your unit.
Find an RUU for the firmware version your phone originally had, make sure your CID and MID match the ones for the RUU was created for.
NEVER flash RUU for different firmware without being S-OFF. Always confirm that CID and MID of the RUU match your CID and MID. ALWAYS!
Click to expand...
Click to collapse
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
nerodarknight said:
I managed to get around that by flashing a custom ROM, happily running Viper MM ROM. FYI, I changed the CID and MID because I'm S-OFF but it does not seems to work. I'm rocking the Viper MM ROM until I can get my hand on a RUU for my variant and hopefully by that time I will be rocking Nougat, Japan carriers tend to take a long time with their update.
Click to expand...
Click to collapse
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Kyuubi10 said:
Cool, sounds like you are sorted.
Well, regarding your firmware and cid/mid...it seems to me then that regardless what you set your cid/mid to your device has some significant hardware differences that make it impossible to boot the firmware of another variant.
Shame really, not much you can do in that case.
Click to expand...
Click to collapse
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
nerodarknight said:
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got after the backup restore failed. If possible can you explain what does it mean?
Click to expand...
Click to collapse
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Kyuubi10 said:
Ok, so either you run out of space on system partition, or you have corrupted filesystem.
If you don't mind starting from scratch, you could try formatting system partition.
Not sure what file system Android uses, i believe EXT3 or 4. (if anyone else knows, feel free to help).
But you could try that, then run the restore again
Click to expand...
Click to collapse
Doesn't not seems to work, formatted the system partition but it still failed
If this is any help, I successfully converted it to WWE but since I got a bug with the service : LTE (data) is good but no call or text whatsoever so that's why I'm trying to convert back, flashed the firmware zip and then restore back up. The firmware zip worked out fine but the restore always failed. To add to that, when I'm on WWE firmware I can restore the WWE firmware backup just fine.
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
nerodarknight said:
I found out that some how I shrank the system partition so that's why it is not able to fit the back up, is there anyway to reverse this at all?
Click to expand...
Click to collapse
I believe TWRP should be capable...
Google for a guide.
nerodarknight said:
I made a foolish attempt of converting my HTC 10 au kddi (japan) to US Unlocked for to get the Nougat update. I tried to use a RUU exe file but it came back with a error ( not a major error, it seems as it wouldn't even flash the file and state wrong model something). Of course, I have 2 back up on the ready. One for the stock of stock and the other after receiving the first and only OTA. However, both seems to failed after around 80% and after that the system partition become unmounted and it shown an error saying Failed to mount /system (Invalid Argument). I still have access to the download, RUU, bootloader and recovery mode but cannot seems to get the back up working. Any idea of why is appreciate.
Click to expand...
Click to collapse
I have the same problem this happened after I formatted the date to blink rom
How can I solve this problem after I tried to install the rom maximos hd and I did not succeed I returned my bachup from the stock more now this giving error in the horade do the same I am with bild 2.41.401.3 cid HTC__M27 mid 2PS62000
Can someone help me please ???
Related
I am a newly registered user, but I have been actively reading the forums for the past few months.
I have a factory unlocked M8 (cid BS_US001) that I have been experimenting with. I have unlocked the bootloader, S-OFF, flashed the recovery with TWRP, and installed a few custom ROMs (ViperOneM8, ARHD, stock GPE). I have had no issues (thanks to all of the helpful posts on the forum) until today.
I decided that I wanted to go back to my stock ROM, so I loaded up TWRP, performed a factory reset, and attempted to restore my original backup. The restore failed during the system restore, and here's the relevant part of the recovery log:
Code:
tar_extract_all(): calling tar_extract_file(t, "//system/media/audio/notifications/")
item name: '/system/media/audio/notifications/'
dir
==> extracting: //system/media/audio/notifications/ (mode 40755, directory)
mkdir(): No space left on device
FAILED RESTORE OF FILE i: //system/media/audio/notifications/
E:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/FA43RWM01711/original/system.ext4.win000'
I:Error extracting '/external_sd/TWRP/BACKUPS/FA43RWM01711/original/system.ext4.win000' in thread ID 0
E:Error extracting split archive.
I:extractTarFork() process ended with ERROR=255
I:Failed to reset capabilities of /system/bin/run-as binary.
I noticed the line about "No space left on the device", so I formatted the internal storage and tried again. This time, it created the notifications folder, but failed on the next file:
Code:
tar_extract_all(): calling tar_extract_file(t, "//system/media/audio/notifications/Amaranth.flac")
item name: '/system/media/audio/notifications/Amaranth.flac'
reg
==> tar_extract_regfile(t=0x1401b8, realname="//system/media/audio/notifications/Amaranth.flac")
==> extracting: //system/media/audio/notifications/Amaranth.flac (file size 73305 bytes)
FAILED RESTORE OF FILE i: //system/media/audio/notifications/Amaranth.flac
E:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/FA43RWM01711/original/system.ext4.win000'
I:Error extracting '/external_sd/TWRP/BACKUPS/FA43RWM01711/original/system.ext4.win000' in thread ID 0
E:Error extracting split archive.
I:extractTarFork() process ended with ERROR=255
I:Failed to reset capabilities of /system/bin/run-as binary.
I noticed that both of these errors seemed to be a problem with extracting the system.ext4.win000 file. I was able to find another TWRP backup of the stock ROM for my device, so I tried that and got the same error. I then tried reinstalling ARHD. The install seemed to complete, but after rebooting the device, it booted back into the TWRP recovery after the splash screen. The only way I've been able to get the device working was to flash the GPE RUU from adb.
Any ideas as to why I'm having these issues? I've searched the forums and Google and can't find an answer.
Well. A simple "fastboot erase cache" may have fixed it but now you have changed the partitions from flashing gpe ruu. You need to flash sense ota firmware to fix partitions, then format data and try again. Follow the guide on getting back to sense from gpe conversion.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
an0ther said:
Well. A simple "fastboot erase cache" may have fixed it but now you have changed the partitions from flashing gpe ruu. You need to flash sense ota firmware to fix partitions, then format data and try again. Follow the guide on getting back to sense from gpe conversion.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's exactly what I needed. Thanks!
So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back
redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Did you fastboot erase cache before installing TWRP, as I suggested?
Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.
It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
should be in Q&A mate
I have requiested the mods to move this
So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.
tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode
UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...
Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...
hi
my GF phone suddenly displayed message and asked me to enter password to decrypt your data , and so i did. It then told me that my password was right, but the data was corrupt, and presented me a button to reset my phone. The button redirected me to recovery and automatically attempted to wipe /data and then re-mount it, but the wipe failed. I rebooted again with the same issue, same failed attempt to wipe. I went to install the zip again, and this time do a full wipe, but it was unable to mount my phone's storage nor my SD card. I am not able to mount either at all now.
the phone is s-on and locked , and i dont have any chance to unlock bootloader because oem unlock is turned off
is there anyway to repair partition and install a new rom without using any custom recovery ???
I assume a RUU could help you. Try this link.
Edit: Here you can find even more RUUs
Go to download mode and check your CID, that should help you know what RUU is correct for your device
rzarectha said:
I assume a RUU could help you. Try this link.
Edit: Here you can find even more RUUs
Go to download mode and check your CID, that should help you know what RUU is correct for your device
Click to expand...
Click to collapse
The first thread you linked is outdated and the links are broken. Best solution would be looking at the sticky threads here in the general section.
Sent from my HTC One M9 using XDA Labs
if ruu doesnt work, go to download mode and try fastboot format <partition> . I think i had something similar and that was how I solved it.
Flippy498 said:
The first thread you linked is outdated and the links are broken. Best solution would be looking at the sticky threads here in the general section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i try to flash ruu through fastboot and get this error :
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
after that i run Ruu.exe procedure , the phone stuck in rebooting to bootloader and pc does not recogonize it , somehow i manually reboot phone to bootloader but i got the error phone is at low 30% battery .
what should i do now ??
Adromir said:
if ruu doesnt work, go to download mode and try fastboot format <partition> . I think i had something similar and that was how I solved it.
Click to expand...
Click to collapse
the phone didnt allow me to do it because the bootloader is locked !!! and i dont have chance to unlock it ,since the oem unlocking is turned off
mikakachi said:
i try to flash ruu through fastboot and get this error :
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
after that i run Ruu.exe procedure , the phone stuck in rebooting to bootloader and pc does not recogonize it , somehow i manually reboot phone to bootloader but i got the error phone is at low 30% battery .
what should i do now ??
Click to expand...
Click to collapse
For starters, charge your phone. I can't remember what the minimum threshold is, but there's a safety measure that requires a minimum battery level to avoid the phone turning off in the middle of delicate software operations.
You mention flashing the ruu via flashboot. Have you looked into applying the ruu via the SD card method? That may serve you better.
computerslayer said:
For starters, charge your phone. I can't remember what the minimum threshold is, but there's a safety measure that requires a minimum battery level to avoid the phone turning off in the middle of delicate software operations.
You mention flashing the ruu via flashboot. Have you looked into applying the ruu via the SD card method? That may serve you better.
Click to expand...
Click to collapse
no i did not tried it ! how can i do that ?
mikakachi said:
no i did not tried it ! how can i do that ?
Click to expand...
Click to collapse
Read the instructions in the thread I've mentioned in my last post.
the phone stuck in reboot to bootloader mode and failed to flash from sd card ! i try to install rom from stock recovery and i got this error :
E:failed to setup expected mounts for install; aborting Installation aborted.
E:failed to mount /devlog (invalid argument).. try emmc mount
E:can't find device node for mount point /devlog
.
.
.
.
E:mount /cache fail, format it and mount again
E:failed to mount /cache (invalid argument).. try emmc mount
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