Related
My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?
Here is another thread that discusses a similar issue.
Hope it'll help.
http://forum.xda-developers.com/showthread.php?t=1056767
Sent from my G9 using Tapatalk
Pretendde said:
My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?
Click to expand...
Click to collapse
Hmmm. This is going to be hard to get out of as you upgraded your Hboot. Does the phone still register fastboot commands? Also what downgrade thread did you follow?
Sent from my HTC Sensation using Tapatalk
It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!
Pretendde said:
It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!
Click to expand...
Click to collapse
That's not what I mean, to unlock your bootloader you would have had to issue the command fastboot OEM unlock, or fastboot flash OEM unlock unlock_token.bin or something similar. These types of commands are the ones I'm interested in I want to see if you can flash clockworkmod recovery pal.
Sent from my HTC Sensation using Tapatalk
I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom
Pretendde said:
I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom
Click to expand...
Click to collapse
Ok so fastboot works, good good. Do you have clockworkmod recovery installed? If not follow my thread for rooting hboot 1.02.0000 and install clockworkmod but go no further.
Also just for your information the ruu will not install because of
1. Your honor is higher than the ones in the RUU,
2 your bootloader is unlocked.
We need to downgrade you to the WWE rom with hboot 1.01.0001 and hopefully that will restore your touch panel to working order
Sent from my HTC Sensation using Tapatalk
Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?
Pretendde said:
Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?
Click to expand...
Click to collapse
ok so what we want to do know is downgrade your hboot to 1.01.0001 so to do that we need your misc partition to be edited. as such i would like you to boot the phone into clockworkmod recovery and connect it to the pc with a usb cable. windows should install the drivers if it has not done so already.
next you will need to set up your command prompt for using adb/fastboot commands.
then we will pull a copy of your misc partition to your sdcard and then copy it into your windows adb folder.
then you will upload that image to me, i will make the necessary changes and then re-upload for you.
then you will flash it to the phone all going well, re-lock your bootloader and then downgrade your hboot and rom and hopefully regain touch input
then as an extra if you want to use a rooted version of that german ruu you were trying to flash i can make you a "safe to flash" version
ok, so....
step 1. Connect your wildfire up to your pc In clockworkmod recovery mode.
step 2. open a command prompt within your adb/fastboot folder. (the same one you used to flash clockworkmod recovery)
step 3. enter the following commands one at a time. copy paste is recommended.
Code:
adb shell
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
exit
adb pull /sdcard/misc.img misc.img
step 4. Upload this file to somewhere like dropbox or media fire and then send me a link to it.
in command prompt
su
/sbin/sh: su: not found
what i do wrong?
Pretendde said:
in command prompt
su
/sbin/sh: su: not found
what i do wrong?
Click to expand...
Click to collapse
OK just skip that and move onto the next bit.
Sent from my Nexus 7 using Tapatalk
I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before
Pretendde said:
I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before
Click to expand...
Click to collapse
okey dokey, here is your new misc image. extract it into your adb folder.
i have edited this so it will re-lock your bootloader automatically once you have flashed it. one problem solved
also download this package, it has some tools you will need and the WWE rom you need to flash
lastly we need to make a goldcard. this will be hard given that your touch screen is non-functional. as such you will need a different, working android phone and YOUR sdcard. this trick is sdcard specific so dont swap them about
ok once you are ready with the right stuff, do these steps.
step 5. now we need to make a gold card. if you already have one, you can skip this part. first using your working android phone, download and install Goldcard helper from the android market. Run the app and copy down your SD cards reverse cid. double check it
step 6. now go to this website here and enter in your reverse cid. it will then let you download a goldcard.img.
step 7. now go back to the package you downloaded earlier with the WWE rom (named 1.01.zip) in it and run the goldcardtool.exe, this will flash the goldcard to your sd card. Warning! this will format your card!! in order to achieve this you will have to mount the sdcard from clockworkmod recovery to the computer, use mount usb storage and not mount sdcard.
step 8. once that is done we are now ready for the final push
Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?
Pretendde said:
Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?
Click to expand...
Click to collapse
ok from here copy the Nmisc.img to your sdcard and do not rename it, leave it on the sd card within no folders.
then connect up the phone in clockworkmod recovery again, and mount the sdcard with mount sdcard and not usb mass storage.
lastly make sure that the 1.01.zip is in your adb folder.
issue the following commands.
Code:
adb shell
(your shell symbol should be a #)
flash_image misc /sdcard/Nmisc.img
exit
(now it should not be a #)
adb reboot bootloader
The phone should not reboot into bootloader and should say at the top locked OOW.
This is ok, if it does not say this then your misc image was not flashed.
if all is well issue these commands.
Code:
fastboot oem rebootRUU
fastboot flash zip 1.01.zip
This will state an error, and that it needs to be reflushed. this is what we want, if any other issue your goldcard may have failed.
repeat the last command to reflush.
Code:
fastboot flash zip 1.01.zip
(this will take a while.)
fastboot reboot
the phone should reboot into the WWE stock rom and hopefully your touch screen will be working again. if it is proceed to s-off with revolutionary here ignore all but revolutionary and then if you want the german ruu as a safe flash rom send me a link to the ruu and I will make it. but it make take a few days.
im at work atm so my replys will be delayed pal, good luck
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....
Pretendde said:
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....
Click to expand...
Click to collapse
Your gold card has failed. Format the sdcard and then reissue the fastboot commands.
Sent from my HTC Sensation using Tapatalk
Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error
Pretendde said:
Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error
Click to expand...
Click to collapse
Does your bootloader still say locked?
Sent from my HTC Sensation using Tapatalk
heavy_metal_man said:
does your bootloader still say locked?
Sent from my htc sensation using tapatalk
Click to expand...
Click to collapse
yes
*** locked (00w) ***
Hi All,
I am trying to unlock bootloader in htc desire 816, as i read from blogs i got a Unlock_code.bin file from HTC then i tried "fastboot flash unlocktoken Unlock_code.bin" after this it's gives a pop up in my htc phone with YES and ON option i select YES then phone goes to recovery mode and i received the following error :-
E: missing bitmap oem_unlock_bg
(Code-1)
E: missing bitmap oem_unlock_bg_yes
(Code-1)
E: missing bitmap oem_unlock_bg_no
(Code-1)
Write host_mode success
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
and i can see as "LOCKED" in the bootloader.
The issue is my HTC 816 keeping on rebooting automatically every 30 seconds( Don't know why) so trying to put custom ROM so that may be this issue can be resolved.
Please do HELP!
Thanks in advance.
arpitkatty said:
Hi All,
I am trying to unlock bootloader in htc desire 816, as i read from blogs i got a Unlock_code.bin file from HTC then i tried "fastboot flash unlocktoken Unlock_code.bin" after this it's gives a pop up in my htc phone with YES and ON option i select YES then phone goes to recovery mode and i received the following error :-
E: missing bitmap oem_unlock_bg
(Code-1)
E: missing bitmap oem_unlock_bg_yes
(Code-1)
E: missing bitmap oem_unlock_bg_no
(Code-1)
Write host_mode success
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
and i can see as "LOCKED" in the bootloader.
The issue is my HTC 816 keeping on rebooting automatically every 30 seconds( Don't know why) so trying to put custom ROM so that may be this issue can be resolved.
Please do HELP!
Thanks in advance.
Click to expand...
Click to collapse
try factory reset from recovery first
hisham_waleed_karam said:
try factory reset from recovery first
Click to expand...
Click to collapse
Thanks hisham, But nothing is working, neither factory reset nor any other option from recovery.
i don't get any error while doing wipe data/factory reset at last it says data wipe complete but when i reboot my phone everything is same. all my setting and apps are still installed.
According to me, the issue is "Whatsapp" app(may be some issue) because of this app my phone keeping restarting. I tried uninstalling in the 30 second window but when i uninstall it shows as uninstalled but as soon as my phone reboot and i check again whatsapp is there.
So no data is been deleted/uninstall.
Now any suggestion on this.
arpitkatty said:
Thanks hisham, But nothing is working, neither factory reset nor any other option from recovery.
i don't get any error while doing wipe data/factory reset at last it says data wipe complete but when i reboot my phone everything is same. all my setting and apps are still installed.
According to me, the issue is "Whatsapp" app(may be some issue) because of this app my phone keeping restarting. I tried uninstalling in the 30 second window but when i uninstall it shows as uninstalled but as soon as my phone reboot and i check again whatsapp is there.
So no data is been deleted/uninstall.
Now any suggestion on this.
Click to expand...
Click to collapse
be sure you have downloaded the right Unlock_code.bin file you received on email from htc dev site
If you have an SD card in remove it I had a similar rebooting issue and after I reset phone and put SD in it rebooted randomly 1 more time then stopped
Sent from my 710C using XDA Free mobile app
Benji90 said:
If you have an SD card in remove it I had a similar rebooting issue and after I reset phone and put SD in it rebooted randomly 1 more time then stopped
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for Reply!
No, i haven't placed any SD card. i don't know what to do now, as none of the thing is working out as first step is to unlock the phone and that is only not working so can't even go forward.
plz help me
i have a htc desire 816 and i had already rooted d phone. due to some reason i unrooted it, flashed stock recovery, and locked bootloader. i m on stock rom. after relocking i m not able to boot the os. i m stuck on bootloader. i can powerdown d device and access hboot. but now der s no recovery. if i try to flash any file, it s showing signature verification failed. i tried unlocking the device again using htcdev. if i give yes unlock in my mobile, it is showing entering recovery. what should i do now??? plz help me.
***software status: Modified***
***RELOCKED***
***security warning***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.0215
OpenDSP-v27.2.2.00546.0311
OS-
eMMC-boot 1536MB
Mar 20 2015,18:50:11.0
amrutha21 said:
i have a htc desire 816 and i had already rooted d phone. due to some reason i unrooted it, flashed stock recovery, and locked bootloader. i m on stock rom. after relocking i m not able to boot the os. i m stuck on bootloader. i can powerdown d device and access hboot. but now der s no recovery. if i try to flash any file, it s showing signature verification failed. i tried unlocking the device again using htcdev. if i give yes unlock in my mobile, it is showing entering recovery. what should i do now??? plz help me.
***software status: Modified***
***RELOCKED***
***security warning***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.0215
OpenDSP-v27.2.2.00546.0311
OS-
eMMC-boot 1536MB
Mar 20 2015,18:50:11.0
Click to expand...
Click to collapse
When you did this did you flash an ruu file ?
Sent from my 710C using XDA Free mobile app
Benji90 said:
When you did this did you flash an ruu file ?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
i tried doing it, but its giving data too long error. n i no that der s no os in d phone. but whichever rom i try to flash, its showing signature verification failure. stock ruu its showing data too long. can i no ver i can get other ruu??
Exact model but diff. problem
amrutha21 said:
i tried doing it, but its giving data too long error. n i no that der s no os in d phone. but whichever rom i try to flash, its showing signature verification failure. stock ruu its showing data too long. can i no ver i can get other ruu??
Click to expand...
Click to collapse
Same matching model but SIMM not working after flashing CM-12. Now need to install fresh Stockk firmware, but could't find exact stock firmware, thing which i downloaded seems like something else, there is 1 big (approx 1 GB) file but it shows header error. Please guide me to stock firmware of exact model as mentioned.
Hey i have to root my htc desire 816 indian varient plz tell me how to do that how to unlock the bootloader then root then flash twrp? Plz tell
same issue...
arpitkatty said:
Hi All,
I am trying to unlock bootloader in htc desire 816, as i read from blogs i got a Unlock_code.bin file from HTC then i tried "fastboot flash unlocktoken Unlock_code.bin" after this it's gives a pop up in my htc phone with YES and ON option i select YES then phone goes to recovery mode and i received the following error :-
E: missing bitmap oem_unlock_bg
(Code-1)
E: missing bitmap oem_unlock_bg_yes
(Code-1)
E: missing bitmap oem_unlock_bg_no
(Code-1)
Write host_mode success
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
and i can see as "LOCKED" in the bootloader.
The issue is my HTC 816 keeping on rebooting automatically every 30 seconds( Don't know why) so trying to put custom ROM so that may be this issue can be resolved.
Thanks in advance.
Click to expand...
Click to collapse
Please do HELP!
i have the same issue...i try factory reset but not working...and the crazy thing that all my info app etc is still on the phone after wipe data via stock recovery...i download RUU.zip and try to flash it via sd card
when he hav to restart first and continue install ruu its just feild and reboot into the os with all my info...any help guys?
Hello, I tried to update my phone to android 6.0.1, but after the update my phone stuck at htc logo for about 1 hour, so I decided to restart my phone to see what happen and now my phone stuck at black screen after htc logo.
Before update my device have already rooted with twrp recovery, so I tried to flash stock recovery back into the device. (I get the stock recovery file "recovery.img" by extract file "download/OTA_EYE_TUHL_L50_SENSE60_MR_hTC_Asia_WWE_2.19.707.5-2.19.707.3_release_468771.zip/firmware.zip/recovery.img" that I've download into internal memory when update my phone) I don't sure is it the cause of the problem. Then I flash the recovery.img to my phone by using newest windroid toolkit and install the update. First the update run smoothly but end up stucking at htc logo as I've told you before.
I am very beginner and I really have no idea what happen and how to fix my phone, please help me. Thank you very much.
Did you give it at least 10 minutes.?
Sae68 said:
Did you give it at least 10 minutes.?
Click to expand...
Click to collapse
Yes, I give it about 1 hr.
for additional detailed, I tried to boot into recovery mode and the screen show this message:
"E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/data/cwtemp/cwpg.zip
handle_cota_install: install cwpkg to /data/data/cwtemp/cwprop
Write host_mode success
handle_cota_install: No CW files. Skip cw installation."
and if I tried to "apply from sd card", the screen show this message:
"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"
Is this help you to easier recognize the problems? Sorry for my poor english...
I think you install wrong recovery,, try to flash correct one from boot-loader by using command "fastboot flash recovery xxx.img" , where xxx is recovery name placed in same fastboot driver folder.... then run this command "fastboot erase caches"...
Ba7rani said:
I think you install wrong recovery,, try to flash correct one from boot-loader by using command "fastboot flash recovery xxx.img" , where xxx is recovery name placed in same fastboot driver folder.... then run this command "fastboot erase caches"...
Click to expand...
Click to collapse
i am also facing same problem flashing 6 mm ota -error in/cache /recovery /block.map
desire eye cid htc--044 version 2.19.707.3? which is the correct stock recovery for this phone? link please help
hbrajhbh1 said:
i am also facing same problem flashing 6 mm ota -error in/cache /recovery /block.map
desire eye cid htc--044 version 2.19.707.3? which is the correct stock recovery for this phone? link please help
Click to expand...
Click to collapse
Go to boat-loader and give the details please...
Ba7rani said:
Go to boat-loader and give the details please...
Click to expand...
Click to collapse
thanks
bootloader details desire eye tuhl pvt ship. s-off unlocked .cid htc--044 . hboot 3.19.0.0000, 0s 2.19.707.3 radio 1.32.213311841.316 software status official please give recovery link?
hbrajhbh1 said:
thanks
bootloader details desire eye tuhl pvt ship. s-off unlocked .cid htc--044 . hboot 3.19.0.0000, 0s 2.19.707.3 radio 1.32.213311841.316 software status official please give recovery link?
Click to expand...
Click to collapse
I tried to find but couldn't ,, sorry...
Ba7rani said:
I tried to find but couldn't ,, sorry...
Click to expand...
Click to collapse
any how thanks for efforts
try when ever u find?
I'm facing the same problem as well. I followed the same exact steps OP used.
Right now, I'm trying to use an international stock ROM to restore to stock KitKat. Will update on how that's going once it's done downloading.
xIceArcher said:
I'm facing the same problem as well. I followed the same exact steps OP used.
Right now, I'm trying to use an international stock ROM to restore to stock KitKat. Will update on how that's going once it's done downloading.
Click to expand...
Click to collapse
How did it go? My phone is useless now, can't do much with it. Stock and Mods don't work.
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