I just spent way too much time trying to figure this out. Today the mic on my one shat the bed, so I was attempting to return to stock to get a replacement. I am running the 1.31 software and foolishly tried to run back to 1.29. I am relocked, I have access to fastboot but nothing pass security verification. I've tried recoveries, my unlock time bin, and anything else I could throw at it. Nothing works. I always get the FAILED message. I am S ON, and security warning at the header of my boot loader screen. I can't get it to be recognized be adb either. Man would I love some advice to get past this. Please.
Sent from my Nexus 7 using xda app-developers app
Your good don't worry. Download a recovery from the dev section. Rename it something easy like recovery.img and place it in the same folder as your ADB (if you don't have ADB keep reading down to the bottom then come back and flash your recovery). Open a command prompt on your computer and cd to your adb dir. Connect phone in fastboot to computer and type fastboot flash recovery recovery.img (or whatever you named it. Then from recovery follow the guide for 1.31 RUU which I will link below.
Now to RUU follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
You will see this message (failed) ignore it and flash the RUU anyway.
~ # ←[6necho "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
warning: seek lseek64 failed
12+0 records in
12+0 records out
12 bytes (12B) copied, 0.007263 seconds, 1.6KB/s
~ # ←[6n
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
It was lots of fun typing all of this on my phone.
Sent from my HTCONE using xda app-developers app
I can't get anything including recovery to flash. It all says Failed. Here's a pic of ,e trying to fastboot flash TWRP.
Sent from my Nexus 7 using xda app-developers app
ajd88 said:
I can't get anything including recovery to flash. It all says Failed. Here's a pic of ,e trying to fastboot flash TWRP.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Check PM
I think I got it. I had to re unlock the boot loader with a new token. I was trying to unlock with my old bin file. Thank you for helping me out much appreciated. Wasted way to many hours on this.
Sent from my Nexus 7 using xda app-developers app
Hit me up if you need anything else
ajd88 said:
I think I got it. I had to re unlock the boot loader with a new token. I was trying to unlock with my old bin file. Thank you for helping me out much appreciated. Wasted way to many hours on this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No worries, hope you get it sorted.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
It was lots of fun typing all of this on my phone.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I bet it was!! I wouldn't have tried that. More power to ya!! You are PRO!
Still getting
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
Im not stuck like I was I can get into recovery and boot, but everytime I try to Ruu I get this crap. I am Soff and have oem relocked everytime before attempting RUU. This sucks.
ajd88 said:
Still getting
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
Im not stuck like I was I can get into recovery and boot, but everytime I try to Ruu I get this crap. I am Soff and have oem relocked everytime before attempting RUU. This sucks.
Click to expand...
Click to collapse
Every time I got that message it was due to a bad or wrong choice in RUU files. I would try fastboot flashing this RUU.zip. Hopefully that will work for you. I have written up all the steps to follow that work for most people here. You are already past the tricky part.
Good luck.
MrFixit007 said:
Every time I got that message it was due to a bad or wrong choice in RUU files. I would try fastboot flashing this RUU.zip. Hopefully that will work for you. I have written up all the steps to follow that work for most people here. You are already past the tricky part.
Good luck.
Click to expand...
Click to collapse
That Zip file got me a little farther, still stuck though.
sending 'zip' (1029700 KB)...
OKAY [ 48.045s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 54.880s
Are you running the RUU from your PC?
bigdaddy619 said:
Are you running the RUU from your PC?
Click to expand...
Click to collapse
Yes I am. Running windows 8. I have never had issues before doing stuff like this. I'm stumped.
Edit: Think I'm good now.
ajd88 said:
That Zip file got me a little farther, still stuck though.
sending 'zip' (1029700 KB)...
OKAY [ 48.045s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 54.880s
Click to expand...
Click to collapse
When you get the please flush message you IMMEDIATELY run the exact same command again!!
Everything will work fine after that.
MrFixit007 said:
When you get the please flush message you IMMEDIATELY run the exact same command again!!
Everything will work fine after that.[/
Your right thats what I did. All good now. Thank you.
Click to expand...
Click to collapse
Related
Hi All,
I am trying to get my phone back to stock and trying to flash RUU zip via fastboot, however i am getting the below error, could you please help me understand what the error means :
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>fastboot flash zip rom.
zip
sending 'zip' (1029979 KB)...
OKAY [ 59.742s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 186.470s
Thanks a lot
Could anyone please help me with this?
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
well so i guess there is no way currently to go back to stock with 1.544 hboot. I checked the RUU has my model id but i am s-on , so i guess i have nothing left but to sulk
gunnyman said:
It means you are trying to flash either the wrong RUU or you're trying to downgrade from a higher firmware version. That won't work without s off
Click to expand...
Click to collapse
Do you know if there is anyway for me to go 100% stock with a 4.1.2 RUU , when i am on 4.2.2 with 1.544 hboot with s-on?
No not possible.
Hello i want to load an rom. I was comming from stock.
I did not made a backup.
the Phone is Tamperd and unlocked
But s-on
That is the problem. I cann't flash rom's
Also it is impossible to go back to stockrom.
I have tried all the rom's i could find.
I just bought my Phone two days ago.
I am very ......:crying:
Please help me
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-V26.120.274.0202
eMMC-boot
May 3 2013, 17.22.59
I am using all in one toolkit.
Trying to s off by using revone, it is going wrong on setting permissions.
revone v0.2.1
revone failed (error code = 1)
Please help
Very vague there... do you have a custom recovery? How are the roms failing to install?
Sent from my Nexus 10 using Tapatalk 4
roluc said:
Hello i want to load an rom. I was comming from stock.
I did not made a backup.
the Phone is Tamperd and unlocked
But s-on
That is the problem. I cann't flash rom's
Also it is impossible to go back to stockrom.
I have tried all the rom's i could find.
I just bought my Phone two days ago.
I am very ......:crying:
Please help me
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-V26.120.274.0202
eMMC-boot
May 3 2013, 17.22.59
Click to expand...
Click to collapse
I would download the RUU for your phone which has the old Hboot 1.44 or older only. Relock your phone and then flash the RUU to it. In the bootloader as long as you see fastboot USB all you need to do is open up an adb console on your computer and type fastboot oem rebootruu and it will reboot to the HTC logo. Run the RUU.exe from your computer and wait 10 minutes. That will take you back to stock and start over.
If you do not have the android SDK I recommend you download and install it so you have an arsenal of tools to work with.
http://developer.android.com/sdk/index.html
a step forwarts
Thank's relock is ok.
when i flash the ruu is start doing things i didn't see before.
At the end its going wrong. see below
sending 'zip' (1010379 KB)...
OKAY [ 33.245s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 142.087s
When if flush again the same problem.
Is it possible that the cid have to be canged?
...
(bootloader) cid: HTC__102
OKAY [ 0.016s]
finished. total time: 0.016s
Please help me
I have added info.
If you need more i will try to provide it.
Ronald
Hello all of you out there.
I am happy again.
After the de relock i have tried a lot.
Finally i succeeded.
I have downloaded an zip file:RUU_Downgrader_1.27.531.11-1.27.531.8.zip
I downloaded an rom with same radio as on the Phone.This was an zip file.
I have renamed it to: rom.zip and placed it in the map where i unzipped the ruu downgrader,
Run it and the Phone is starting up again.
At this moment i the htc software is upgrading.
Oh no it is stuck in an bootloop.
Hboot is now 1.54 and the radio is changed.
Hope it wil start again.
The Phone stays in an bootloop.
What should i do now.
searching voor an ruu and try to install?
Factory reset?
Please help me
Did you figure it out
Did you happen to figure out how to fix your phone? Just curious
chaley80 said:
Did you happen to figure out how to fix your phone? Just curious
Click to expand...
Click to collapse
No, it is still a big problem.
Only the boatloader fucntion.
The want boot in recovery.
Please help
roluc said:
No, it is still a big problem.
Only the boatloader fucntion.
The want boot in recovery.
Please help
Click to expand...
Click to collapse
Did you flash recovery via fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
Android The Greek said:
Did you flash recovery via fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No i used an all in one kit.
Is it better to do it with fastboot.
What do i heb to do?
I have fastboot.exe. and adb.exe
Greetings
roluc said:
No i used an all in one kit.
Is it better to do it with fastboot.
What do i heb to do?
I have fastboot.exe. and adb.exe
Greetings
Click to expand...
Click to collapse
You need to delete any folders or files for cwm. The go to twrp website and download the latest m7 recovery img. Follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2173870
[RECOVERY][8/30/2013]TWRP v2.6.1.0
Sent from my HTC One using XDA Premium 4 mobile app
I have a US AT&T HTC ONE M7 that shipped to me.
I unrooted it fine using htcdev and getting the unlock_code.bin. Then I uploaded a recovery TWRP just fine and got in there and saw that it worked fine. Rebooted into normal and copyed the Revolution HD zip to my phone, but reading the thread it said that i needed to update my firmware.
I followed the guide it refferenced http://forum.xda-developers.com/showthread.php?t=2183023
To here http://forum.xda-developers.com/showthread.php?t=2182823
And it said to do the command to get your cid, which I did and got idnum: CWS__001
So I looked and found that I needed to get firmware.zip from 1.29.206.11
But the link on that page takes you to a firmware of 3.06.1700.01 or something close to that. I didn't notice the numbers were different so I did the flash with fimware 3.06.1700.01 instead of the 1.29.206. 11.
Booting the phone does nothing, it sits on the HTC one screen with Beats audio. Also the AT&T chimes no longer chime when on that page and then it just sits there. When booting with the down volume button I get a black screen instead of white screen. With a dead android on the bottom instead of the 3 little androids dancing (or whatever they are doing).
I was able to get recovery back and boot into recovery but I am not sure what to do.
WIth finding instructions I have tried to download a stock RUU which I found here.
http://forum.xda-developers.com/showthread.php?t=2428276
But without any instructions to use it. I assume you need to run it from TWRP recovery but I cannot get the computer to recognize the phone anymore as a drive in order to put the RUU on the phone
I just got this phone today and wanted to root it right away and I think I broke it already.
PLEASE HELP
Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly I have no idea what that means. I have seen S-off and s-on but I am still a n00b. I have also edited my post above as I was able to get recovery installed again. It didn't before because I had relocked it and I unlocked it again
Now the issue is that I cannot get my computer to recognize the phone as a drive to put the RUU on it
Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can get into that fastboot/bootloader but then what? I am here and again - it is a black screen with a dead android on the bottom which is not the same as the white screen I had before. Which clearly tells me something is wrong.
How do I load a stock kernel? Again, I have no access to the filesystem to put files onto the phone, only have access to using the commands like fastboot
I found a file on the internet
RUU_M7_UL_JB_50_Cingular.exe
Which i guess is for AT&T even thought it haven't been Cingular for years. And I go into this which says it is the HTC Android Phone ROM update utility 2.0.4.2013. Say yes to everything. It says it is going to go from 3.06.1700.10 to image version 1.26.502.12
Which is also an issue I think because the guide I found this on said that these numbers should be the same. This goes back to me flashing the 3.06.1700.10 instead of the correct firmware. I tell it to do it's thing but it errors out.
It says it will take about 10 minutes, so I wait - after about 5 minutes I get an error error [155] the ROM update utility cannot update your android phone. Please get the correct ROM update ulitity and try again.
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried another firmware from that page I referenced in the OP for "x.xx.401.x - World Wide English (WWE)"
http://forum.xda-developers.com/showthread.php?t=2182823
Which came out as 2.24.401.1 and when flashing it gives me the error. failed (remote: 41 model id check fail)
I also tried to get kernels from htcdev.com/devcenter/downloads
Downloaded 1.26.502.12 and 1.26.502.10 from this page and neither worked. Giving me the error failed (remote: 12 signature verify fail)
Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dirtbikerr450 said:
Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
I googled S-OFF and I am not S-OFF, my top of my phone says S-ON. I followed a guide to root my phone which the last step was to install SuperSU and it worked fine. SuperSU worked fine as well so I thought I was rooted. I don't know if I was S-OFF before I flashed the firmware that caused this whole thing or not.
AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app
AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
CoryTallman said:
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s
crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
OK Update. I was able to flash the boot after unlocking my phone again:
fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.048s
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.912s]
writing 'boot'...
OKAY [ 0.612s]
finished. total time: 1.529s
So I got that part done. I downloaded the tool and couldn't get that portion of your instructions to work. If you have the time, I installed teamviewer and set it up in my firewall so I would like to give that a try. Never used it before but I am desperate.
EDIT AGAIN: OK I got the ALL IN ONE Tool working. Apparently that doesn't run correctly if its in a folder that has a space in it. I changed the folder name that all this stuff was in to just one word no space and got it working:
sending 'boot' (5794 KB)...
OKAY [ 0.914s]
writing 'boot'...
OKAY [ 0.614s]
finished. total time: 1.530s
However the phone still doesn't boot - it still has no sound on the AT&T part of booting and then the next screen just sits there and does nothing
EDIT 2: OHHHHHHHHHHHH Light bulb went off. By AHRD you meant ARHD - meaning the custom ROM. Sadly - I never got this custom ROM installed. I was following the instructions on that site on what I needed:
Code:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
[B]Firmware package from here (recommended but not needed for now)[/B]
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
It said recommended but not needed for now. I thought it was best to do it and that's what got me in the mess. The ROM on the phone is still whatever came from the factory.
AMDZen said:
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s
Click to expand...
Click to collapse
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.
crushalot said:
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.
Click to expand...
Click to collapse
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:
AMDZen said:
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:
Click to expand...
Click to collapse
Glad your back up.
crushalot said:
Glad your back up.
Click to expand...
Click to collapse
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?
AMDZen said:
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?
Click to expand...
Click to collapse
Just that you can't gain s-off until a new hack is discovered for hboot 1.54. Also I am not sure if it will allow you switch back to the HTC firmware (as opposed to the Google Edition which is an unbranded bootloader) when a new base is release since you have s-on. Shouldn't be a big deal. You will probably be able to run most roms on that firmware for a long time.
Hello all,
I am having trouble trying to restore my AT&T HTC One M7 back to being functional again. The phone was soft-bricked "somehow" by my ex-wife and have been trying to restore it for the past few months. I have done alot of searching and tried many options but nothing is working so far.
The phone had never been rooted and has no custom roms on it. After it was soft-bricked, I was able to get it unlocked at one point, but stupidly enough I followed some wrong advice on how to proceed from there and relocked the phone. Now I cannot unlock it again in order to try to put TWRP or recovery on the phone to get it working again.
So far I have tried the following approaches to this issue:
1)I tried going through the HTC dev site steps to get a unlock code, but nothing happens on the phone screen even after getting a successful notice in CMD screen. (I tried both the original code and getting a new code)
2)Every time I try to flash it on there also I get signature failures in CMD and nothing happens on the phone.
3)I also tried running a stock RUU app, but after the process beings the final update, I get a usb cable error saying it is unplugged when it is not.
Thanks in advance for any suggestions.
To me that sounds like it might be a corrupt boot loader. You could also try to gain s-off and flash a recovery that way. Rumrunner works well: http://rumrunner.us
If you can s-off it then you can flash an hboot image which should fix the issue. Just go to the hboot section on the rumrunner website. Then install TWRP etc....
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
MarkBell said:
Your bootloader needs to be locked in order to run the RUU. Boot to bootloader screen and make sure you are in Fastboot. If on Windows, ensure you have adb installed correctly. Open command prompt on Windows with phone connected and type 'Fastboot relock oem'. This should relock the bootloader. From there, you need to make sure you have the correct RUU for your firmware, boot the phone to the main bootloader screen and run the RUU. Let me know if you need more details.
Click to expand...
Click to collapse
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
I love Xda, and plan to become more involved. My thinking is he is likely flashing the wrong RUU. If there is a mistake to be made, I've made it.
---------- Post added at 07:47 PM ---------- Previous post was at 07:37 PM ----------
And sorry about screwing up that Fastboot command. Lol. Posting too early in the day I guess. Lol. It is indeed Fastboot oem lock. I skimmed over the fact he can't unlock the bootloader. Sorry.
clsA said:
Thanks for sticking around and helping others
The correct command to lock the bootloader is fastboot oem lock. but he says he can't unlock his bootloader so I doubt that's the problem.
@Squirrelsquisher what is the software version on the phone
3.xx.502.x / 4.xx.502.x / 5.xx.502.x ?
you can use a fastboot command to get the info
fastboot getvar all
you can post the result here or just give me your version number as you have AT&T I already know you MID and CID
Click to expand...
Click to collapse
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Squirrelsquisher said:
The software version on the phone is 4.18.502.7 and I made sure to get the same version RUU because I read I cannot use a lesser version than the phone. Also, my phone is also not unlocked, it is relocked currently. When I ran the RUU, it was processing just fine and didnt get a wrong version error. The only error I got was the crazy usb cable error because it was connected just fine.
Click to expand...
Click to collapse
You can flash just the firmware zip
It's on my android file host
I'll post the link when I get to my PC
MarkBell said:
Try using a different USB cable. Make sure it's not one of those cheap ones from ebay. I've had issues with those before. Use your stock usb cord if you can. Let me know if you try that and it still doesn't work. Also try a different USB port on your computer. For some reason, port 2 tends to work best for most people is what I've read.
Click to expand...
Click to collapse
I tried again using different USB ports and different cables with the same error result. Both cables that I used are stock HTC One cables that came with this problem phone and my newer M8 version.
The RUU I have been trying is:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
MarkBell said:
Did you have sense 5.5 or had you upgraded to Sense 6 before? If you upgraded look for the RUU made for your software version with Sense 6. You may also try a newer RUU version. Just don't try an older one.
Click to expand...
Click to collapse
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Squirrelsquisher said:
I didn't get any version errors during the update and I have not seen any RUU out there with sense 6 that doesn't require S-off.
Click to expand...
Click to collapse
MarkBell said:
Have you tried the first one on this list? http://forum.xda-developers.com/showthread.php?t=2428276
---------- Post added at 03:19 AM ---------- Previous post was at 03:15 AM ----------
Also. Make sure you check the MD5 of everything you download. I've heard of people downloading corrupted RUUs using Google Chrome. Try another browser. Any other one besides the one you have been using and check the MD5.
Click to expand...
Click to collapse
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
http://www.androidfilehost.com/?fid=23329332407580581
I meant that download specifically thinking along the lines of a bad file/download. clsA is very good and I recommend following any advice he gives.
clsA said:
He said in both post #6 and #9 that that is the RUU he's trying
Here's the firmware from the OTA try flashing it then the RUU
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
Squirrelsquisher said:
Could you be a little more specific on the steps involved in that? Because I tried straight flashing that file and it said it could not load.
Click to expand...
Click to collapse
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
nkk71 said:
In these situations, it's usually best to always post a "fastboot getvar all" excluding IMEI, possibly a screenshot of bootloader, and a copy/paste of your command prompt output.
the way to flash firmware is:
fastboot oem rebootRUU
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip
fastboot flash zip ATT_OTA.4.18.502.7.firmware.zip <- yes twice!!, first will say failed flush again, second one should report success
fastboot reboot-bootloader
Click to expand...
Click to collapse
I attached a screenshot of the getvar results before attempting those steps you posted.
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
Squirrelsquisher said:
I attached the results of the steps you posted that I should use. Since the results says it failed, I did not run the RUU afterwards.
Click to expand...
Click to collapse
oh crap, just saw your screenshot
are you using a USB3 port?
nkk71 said:
getvar looks ok (well, more or less), what says "it failed"?
example of a copy/paste of a command prompt output:
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
sending 'zip' (1033216 KB)...
OKAY [ 41.559s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
[B][COLOR="Red"]FAILED (remote: 90 hboot pre-update! please flush image again immediately)[/COLOR][/B]
finished. total time: 43.118s
^^ as expected "flush again"
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot flash zip <myfirmwarezip>.zip[/COLOR][/B]
< waiting for device >
sending 'zip' (1033216 KB)...
OKAY [ 41.912s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
......
......
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
[B](bootloader) ...... Successful
OKAY [200.187s]
finished. total time: 242.101s[/B]
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.037s
---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------
oh crap, just saw your screenshot
are you using a USB3 port?
Click to expand...
Click to collapse
My PC does not have USB3 ports, only USB2. I don't see how the speed of the transfer would affect the process though?
Hello Guys,
Sorry to bother again but I think I messed up bad, I accidently did this some how,(attached file) can you help me with it ?
todorov.drago1 said:
Hello Guys,
Sorry to bother again but I think I messed up bad, I accidently did this some how,(attached file) can you help me with it ?
Click to expand...
Click to collapse
That used to happen to me with some versions of TWRP. Which one do you have?
donkeykong1 said:
That used to happen to me with some versions of TWRP. Which one do you have?
Click to expand...
Click to collapse
TWRP v2.8.7.0.. is it because of that, that I cannot flash the RUU.zip from fastboot ?
When I try to flash it a second time it just stays there for 2 hours and nothing.
todorov.drago1 said:
TWRP v2.8.7.0.. is it because of that, that I cannot flash the RUU.zip from fastboot ?
When I try to flash it a second time it just stays there for 2 hours and nothing.
Click to expand...
Click to collapse
2.8.7.0 works fine for me. Can you go to bootloader menu and do factory reset from there? Then go to recovery and try again
donkeykong1 said:
2.8.7.0 works fine for me. Can you go to bootloader menu and do factory reset from there? Then go to recovery and try again
Click to expand...
Click to collapse
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
todorov.drago1 said:
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
Click to expand...
Click to collapse
Why not just flash the RUU that @alray mentioned in your other thread. I think your initial flash problem was because you didn't use htc-fastboot. The download link is in the "How to flash" instructions for the Lolipop ruu collection in the general thread.
mb_guy said:
Why not just flash the RUU that @alray mentioned in your other thread. I think your initial flash problem was because you didn't use htc-fastboot. The download link is in the "How to flash" instructions for the Lolipop ruu collection in the general thread.
Click to expand...
Click to collapse
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
todorov.drago1 said:
When I try to do this, it gives me this /attached file/, and then after some second It reboots.
Keep in mind that I don't have installed OS on that phone.
Click to expand...
Click to collapse
That's recovery. I ment bootloader. Press power+vol down, and you will get in bootloader menu. From there make a factory reset
todorov.drago1 said:
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
Click to expand...
Click to collapse
I think when others have seen this @alray and others suggest it could be adb drivers (make sure you have most current) and tray another usb cable and \or port. I know it worked the first time, sort of as it usully restarts automatically. But worth a try.
donkeykong1 said:
That's recovery. I ment bootloader. Press power+vol down, and you will get in bootloader menu. From there make a factory reset
Click to expand...
Click to collapse
Well, when I go to the bootloader and press factory reset I sends me to the recovery. I think that was normal. Is it not ?
mb_guy said:
I think when others have seen this @alray and others suggest it could be adb drivers (make sure you have most current) and tray another usb cable and \or port. I know it worked the first time, sort of as it usully restarts automatically. But worth a try.
Click to expand...
Click to collapse
I'll try with a different usb cable and different port, and ill get back to you. Thanks for the help fellas.
todorov.drago1 said:
Yeah, I did that and this was outcome:
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 41(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.867 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device SH39JW901074...
^C
C:\Users\Drago Todorov\Downloads\fastboot-win>
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 35(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 34(ms)
C:\Users\Drago Todorov\Downloads\fastboot-win>fastboot flash zip RUU.zip
sending 'zip'... (50228 KB)
And it stays like this forever (2hours) and nothing. That's why I asked for your help.
Click to expand...
Click to collapse
Wait just a moment. I didn't see this post of yours. When fastboot prompts you to "flush image again immediately" what steps exactly do you do? Please describe it in your own words. I think I know what the problem is [emoji6]
todorov.drago1 said:
I'll try with a different usb cable and different port, and ill get back to you. Thanks for the help fellas.
Click to expand...
Click to collapse
Do you have HTCsync installed on your pc? If so uninstall it. Leaving only the HTC drivers installed. Reboot your pc and flash the RUU again.
HTCsync can cause ruu's to stall like that :good:
Sent from my SM-T230 using Tapatalk
donkeykong1 said:
Wait just a moment. I didn't see this post of yours. When fastboot prompts you to "flush image again immediately" what steps exactly do you do? Please describe it in your own words. I think I know what the problem is [emoji6]
Click to expand...
Click to collapse
Thanks mate for the help, i flashed it correctly. I just switched the usb's and it went on with the install.
And now can i ask you somethink else, after the install my phone says there is no IMEI num and doesnt exept my sim card can this be fix or is it hardware problem, it worked before tho?
todorov.drago1 said:
Thanks mate for the help, i flashed it correctly. I just switched the usb's and it went on with the install.
And now can i ask you somethink else, after the install my phone says there is no IMEI num and doesnt exept my sim card can this be fix or is it hardware problem, it worked before tho?
Click to expand...
Click to collapse
Sorry mate, I really can't help you with that. I never encountered that issue, so everything I say would be guessing, and potenetial fixes might ruin your phone. Sorry again [emoji20]
donkeykong1 said:
Sorry mate, I really can't help you with that. I never encountered that issue, so everything I say would be guessing, and potenetial fixes might ruin your phone. Sorry again [emoji20]
Click to expand...
Click to collapse
Nah Dude you did alot for me for it im am thankful alot. ill just have to take it to a GSM service to fix it then :angel:
todorov.drago1 said:
Nah Dude you did alot for me for it im am thankful alot. ill just have to take it to a GSM service to fix it then :angel:
Click to expand...
Click to collapse
Check your baseband as well. Unknown IMEI and baseband is a known issue. Unfortunately if flashing the ruu doesn't help its most probably a hardware problem. ?
Sent from my HTC One using Tapatalk
?
I'm trying to flash recovery.img with fastboot and it is downloaded, but when it starts to write
it says Failed (remote not allowed.) Any hints? Thanks
halloj said:
I'm trying to flash recovery.img with fastboot and it is downloaded, but when it starts to write
it says Failed (remote not allowed.) Any hints? Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?