Hey everyone, (((((SOLVED)))))
so here is the situation.
-HTC One Bell Canada
-S on
-Twrp Recovery newest version
-No OS or backup (I accidentally deleted it)
-Windows 7 64bit
-I have fastboot files, adb files/sdk and the 3.23.666.1 Bell mobility RUU zip with no exe
I just want to get my phone back to stock then after i'll reroot and create a backup of stock so I won't have this happen again.
here is what's on my bootloader screen
Tampered
unlocked
hboot 1.55
I have tried a lot of the similar situation fixes on google and here but I couldn't find anything that has put me in a better place.
when I fastboot with
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
I tried to sideload with twerp and advanced then adb sideload and all I get is error/cannot flash zip.
Also tried installing rumrunner to get my s off but luck either.
I have also tried 4 other RUUs from htcdev and a few other places.
If there is any info you need please ask, thank you in advance.
You guys are my last hope....
christianpencz said:
Hey everyone,
so here is the situation.
-HTC One Bell Canada
-S on
-Twrp Recovery newest version
-No OS or backup (I accidentally deleted it)
-Windows 7 64bit
-I have fastboot files, adb files/sdk and the 3.23.666.1 Bell mobility RUU zip with no exe
I just want to get my phone back to stock then after i'll reroot and create a backup of stock so I won't have this happen again.
here is what's on my bootloader screen
Tampered
unlocked
hboot 1.55
I have tried a lot of the similar situation fixes on google and here but I couldn't find anything that has put me in a better place.
when I fastboot with
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
I tried to sideload with twerp and advanced then adb sideload and all I get is error/cannot flash zip.
Also tried installing rumrunner to get my s off but luck either.
I have also tried 4 other RUUs from htcdev and a few other places.
If there is any info you need please ask, thank you in advance.
You guys are my last hope....
Click to expand...
Click to collapse
Don't panic my friend, you just forgot to relock your bootloader first
Code:
fastboot oem lock
Why don't you just adb push a custom rom to your phone and flash that
Sent from my iPad using Tapatalk
Uxepro said:
Don't panic my friend, you just forgot to relock your bootloader first
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks Uxepro, but I have tried to flash with and without the bootloader unlocked. I get 2 different error messages, which I posted originally (12 signature verify and the 24 parsing android info fail).
If there is a step i'm missing could you tell me the step by step just in case I did something stupid.
christianpencz said:
Thanks Uxepro, but I have tried to flash with and without the bootloader unlocked. I get 2 different error messages, which I posted originally (12 signature verify and the 24 parsing android info fail).
If there is a step i'm missing could you tell me the step by step just in case I did something stupid.
Click to expand...
Click to collapse
To flash ruu with s-on you need 2 things:
Locked or relocked bootloader
Signed ruu (not decrypted)
Sent from my HTC One using xda app-developers app
christianpencz said:
I have .... the 3.23.666.1 Bell mobility RUU zip with no exe
Click to expand...
Click to collapse
1- Where did you get that from, link please
christianpencz said:
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
Click to expand...
Click to collapse
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
nateboi81 said:
Why don't you just adb push a custom rom to your phone and flash that
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
christianpencz said:
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
Click to expand...
Click to collapse
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/showthread.php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/stock-nandroid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
alray said:
To flash ruu with s-on you need 2 things:
Locked or relocked bootloader
Signed ruu (not decrypted)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thank you nobody said it clear to me like that. So is that why it says signature fail, caused it not a signed ruu?
Quote:
Originally Posted by christianpencz View Post
I have .... the 3.23.666.1 Bell mobility RUU zip with no exe
1- Where did you get that from, link please
Click to expand...
Click to collapse
1. http://www.htc1guru.com/dld/ota_m7_ul_jb43_sense50_mr_bm_3-23-666-1-1-29-666-17_r_release-zip/
Quote:
Originally Posted by christianpencz View Post
fastboot oem rebootRUU
then
fastboot flash zip ruu.zip
I get Error 12 signature verify fail when I try with relocked status
and with unlocked status I get 24 parsing android-info fail
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
Click to expand...
Click to collapse
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
Quote:
Originally Posted by christianpencz View Post
I really like the stock Sense OS. At the same time I love apps like greenify and titanium backup. I might try to flash one just in the mean time though.
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/show....php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Click to expand...
Click to collapse
I'll try that in the meantime. Thank you (I have to use my htc one s till I get my one back up and running lol great phone just not the same at all haha.)
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/st...oid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
Click to expand...
Click to collapse
I got mine from there too. But mine didn't work....can you give me the steps with the codes, maybe I missed something....I'm very new at this.
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.
nkk71 said:
1- Where did you get that from, link please
1. http://www.htc1guru.com/dld/ota_m7_ul_jb43_sense50_mr_bm_3-23-666-1-1-29-666-17_r_release-zip/
2- please copy/paste command prompt (all of it), not just the msg you get, everything from start to beginning
Click to expand...
Click to collapse
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
nkk71 said:
check @ClydeB1 index thread for all ROMs etc, http://forum.xda-developers.com/showthread.php?t=2438026
Lot's of Sense ROMs available, all of them good, some very close to stock, others with plenty of tweaks... you'll just have to read a bit, and try a few to see which one works for you.
I'm personally using ARHD 51.0 at the moment and loving it; but that is a personal choice.... you need to try a few to see what works for you
Click to expand...
Click to collapse
I'll try that in the meantime. Thank you (I have to use my htc one s till I get my one back up and running lol great phone just not the same at all haha.)
Emhalwis said:
Since you have twrp recovery, you can restore a nandroid backup http://www.htc1guru.com/downloads/stock-nandroid-downloads/ has a collection. these are stock backups, or any nandroid will work. Once the backup restored and the phone booted, go back to twrp and you can flash any rom if you want.
I had the same situation before and that's how I solved it, that if you prefer custom roms to just being stock.
Click to expand...
Click to collapse
I got mine from there too. But mine didn't work....can you give me the steps with the codes, maybe I missed something....I'm very new at this.
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.
christianpencz said:
2.
Code:
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.152s
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.046s]
finished. total time: 0.046s
C:\Fastboot>fastboot flash zip ruu.zip
sending 'zip' (1054139 KB)...
OKAY [ 54.199s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 175.630s
So if I get the stock/nandroid back up on my phone, does that mean when I flash a different rom I can use the backup to go back to stock?
Thanks for your help so far everyone I really appreciate it.
Click to expand...
Click to collapse
First off the file your using is not a RUU it's an OTA
OTA M7 UL JB43 SENSE50 MR BM 3.23.666.1-1.29.666.17 R Release
their not the same thing OTA is flashed with a stock recovery on a Stock phone.
The nandroid backup / restore is your best bet at this point
clsA said:
First off the file your using is not a RUU it's an OTA
OTA M7 UL JB43 SENSE50 MR BM 3.23.666.1-1.29.666.17 R Release
their not the same thing OTA is flashed with a stock recovery on a Stock phone.
The nandroid backup / restore is your best bet at this point
Click to expand...
Click to collapse
so should I do exactly the same thing and steps just use the nandroid file instead?
christianpencz said:
so should I do exactly the same thing and steps just use the nandroid file instead?
Click to expand...
Click to collapse
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
C:\fastboot>adb devices
List of devices attached
HT343******* recovery
C:\fastboot>adb push backup /data/media/0/TWRP/BACKUPS/HT343*******/backup
push: backup/firmware_3.62.401.1.zip -> /data/media/0/TWRP/BACKUPS/HT343******/
backup/firmware_3.62.401.1.zip
1 file pushed. 0 files skipped.
3881 KB/s (28795564 bytes in 7.245s)
Click to expand...
Click to collapse
I just used one file as an example .. you'll have many files in your backup
clsA said:
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
I just used one file as an example .. you'll have many files in your backup
Click to expand...
Click to collapse
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
alray said:
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
Click to expand...
Click to collapse
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
clsA said:
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
Click to expand...
Click to collapse
ok nmv I was a little confused and didnt read your previous post correctly
alray said:
Can we restore directly from a zip in twrp? Every time I did I extracted the zip before on my pc then pushed the .md5 and .win files in /TWRP/BACKUPS/HT*********/backup
Click to expand...
Click to collapse
clsA said:
no it has to be extracted like you said
I just pushed a zip as an example to show the full path needed
Click to expand...
Click to collapse
clsA said:
No .. you have to push the files to your phones sdcard, TWRP directory where your backups are stored and restore the backup
it will look like this without the *****
I just used one file as an example .. you'll have many files in your backup
Click to expand...
Click to collapse
I sort of understand what you guys mean.....if I change the name of zip file to like nanbackup does that matter?
I know almost nothing about this process, can you do it in code form and a bit simpler.....sorry I'm a bit noobish
christianpencz said:
I sort of understand what you guys mean.....if I change the name of zip file to like nanbackup does that matter?
I know almost nothing about this process, can you do it in code form and a bit simpler.....sorry I'm a bit noobish
Click to expand...
Click to collapse
if you extract the zip to a folder named "nanbackup'' and you move that folder in your adb/fastboot folder then i think the right command should be:
Code:
adb push nanbackup /data/media/0/TWRP/BACKUPS/HT********/nanbackup/
note the space between nanbackup and /data/......
and you should be able to see the backup in twrp after the push is completed
Maybe @CiSa can confirm that before you proceed...
alray said:
if you extract the zip to a folder named "nanbackup'' and you move that folder in your adb/fastboot folder then i think the right command should be:
Code:
adb push nanbackup /data/media/0/TWRP/BACKUPS/HT********/nanbackup/
note the space between /nanbackup and /data/......
and you should be able to see the backup in twrp after the push is completed
Maybe @CiSa can confirm that before you proceed...
Click to expand...
Click to collapse
thank you, so before I try this...what do i actually type where it says HT******
or how can I find out what to put?
Related
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.
How's it going guys,been stressing and working on my phone all day today.
i was running Bad boys rom,while runnning twrp
i flashed viper one,and phone kept booting up to the bootloader only and noticed that it was or tuned back into S-On.
i went back into recovery to try and flash back to bad boys rom,and the phone would boot up but had tons of FC's ,so i went back to recovery and erased everything off my phone and tried to install the rom once again,but noticed the roms were wiped off as well.
i can flash a recovery, im currentyl on twrp 2.6.3.0 ( openrecovery-twrp-2.6.3.0-m7wls.img)
all the drivers on the phone work,i know this because when i push a recovery it installs via adb,
but when i open up CMD and put in "adb devices" it throws "list of devices" but my phone serial code doesnt appear.
i tried adb pushing a rom via sideload on recovery but nothing happens ,now my phone wont boot up to anything,it stays in the white HTC logo screen unless i force it to go to bootloader.
its as if the whole system was wiped and it wont let me push anything.
info of the phone:
sprint htc one
current bootloader state : Tampered / Unlocked
S-ON
----
ps: i already tried putting it in fastboot mode and running a RUU but the RUU wont let me downgrade the system image,says the phone is currently in 4.0.xxx(kit kat) and i was trying to RUU to 3.xx, i thought this would work,but no go.
is my phone really bricked? i mean,i can access recovery but not push any files to flash via adb or sideload , any help guys? please.
EDIT:
like i said the phone is unlocked with S-ON
is there any way i can atleast reset the tampered notice and lock it back again ? ive searched all day and it seems the only way is through rumrunner or/and Revone , but those 2 options require the phone to be S-OFF,which im having issues setting it to since i cant get the phone to boot to anyhting.
::::::::::::::::::::SOLVED::::::::::::::::::::::
so the other twrp recoveries werent letting me sideload,i flashed recovery-clockwork-touch-6.0.3.1-m7wls.img , which then it let me flash via sideload,installed bad boys rom, it booted up but it would stay in the yellow sprint page,when i would push the power button it would let me see the taskbar and would give me FC's on the dialer,so i found the baseband/radio and flashed via sideload,and BOOM! got my phone working again lol.so stoked. thanks guys!
Look HERE
As for you being s-on again the only way that would happen is if you told it to by typing a command to change it.
Also adb devices work while booted to OS or recovery
fastboot devices works in fastboot
BD619 said:
Look HERE
As for you being s-on again the only way that would happen is if you told it to by typing a command to change it.
Also adb devices work while booted to OS or recovery
fastboot devices works in fastboot
Click to expand...
Click to collapse
while flashing the Firmware, it gives me this :
C:\Android>Fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (43373 KB)...
OKAY [ 3.991s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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: 9.898s
any further help ? :/
johndoehizzle said:
while flashing the Firmware, it gives me this :
C:\Android>Fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (43373 KB)...
OKAY [ 3.991s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(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: 9.898s
any further help ? :/
Click to expand...
Click to collapse
Which firmware are you trying to flash?
BD619 said:
Which firmware are you trying to flash?
Click to expand...
Click to collapse
ive tried about 2 different ones, the latest and one for 3.xx, tried them both and get fails but different error/ fail codes for each firmware
johndoehizzle said:
ive tried about 2 different ones, the latest and one for 3.xx, tried them both and get fails but different error/ fail codes for each firmware
Click to expand...
Click to collapse
Did you re-lock?
BD619 said:
Did you re-lock?
Click to expand...
Click to collapse
yeah i relocked / says tampered, i cant remember if when i relock,if it gives me any errors,tomorrow i will unlock it and relock it again and copy and paste the command prompt results, i really need to get my phone going,hopefully one of you guys can help me out,...i really appreciate the help , im broke as hell right now so any help i can get is really useful guys.
thanks alot
any more help please?
quick update: when i was trying to push the file/ sideload , i was hitting shift + right click to open up cmd,which when i put "adb devices" it wouldnt show me the phone being listed,so i when into Start,and looked up CMD and opened it up as an Admin , put the phone into sideload in recovery and it seems like its actually pushing the ROM ,hopefully this works, its at 72% right now. < fingers crossed>
hi guys
what slovw of this
unfortunately htc sense has stopped please help
htc one
after upatae Android_Revolution_HD-One_53.0 no imei basband known and make restart
nokia alkng said:
hi guys
what slovw of this
unfortunately htc sense has stopped please help
htc one
after upatae Android_Revolution_HD-One_53.0 no imei basband known and make restart
Click to expand...
Click to collapse
You will probably need to run a RUU to reset your phone. If you can not find a RUU, post a fastboot getvar all except for the imei and serialno so we can research it.
What custom recovery are you using?
majmoz said:
You will probably need to run a RUU to reset your phone. If you can not find a RUU, post a fastboot getvar all except for the imei and serialno so we can research it.
What custom recovery are you using?
Click to expand...
Click to collapse
hi bro
i used twrp
i will send my phone info and plz help me
Device Online Reading Info
MODEL :
NAME : M7
HBOOT : 1.57.0000
SERIAL : FA36KW905653
CID : HTC__038
MID : PN0710000
BUILD : 6.09.401.5
ANDROID : 4.4.3
IMEI : NULL
majmoz said:
You will probably need to run a RUU to reset your phone. If you can not find a RUU, post a fastboot getvar all except for the imei and serialno so we can research it.
What custom recovery are you using?
Click to expand...
Click to collapse
hi broooooo where are u
:crying:
nokia alkng said:
hi broooooo where are u
:crying:
Click to expand...
Click to collapse
Here is the stock rom 6.09.401.5 you will have to flash it in bootloader/FASTBOOT USB. Copy the file to your adb/fastboot folder and rename it rom.zip. Open a command window on that folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
NOTE: please delete your serial number in the previous post.
majmoz said:
Here is the stock rom 6.09.401.5 you will have to flash it in bootloader/FASTBOOT USB. Copy the file to your adb/fastboot folder and rename it rom.zip. Open a command window on that folder and type:
NOTE: please delete your serial number in the previous post.
Click to expand...
Click to collapse
hi bro
very thanx
and so sorry to late i wias busy
i wanna ask u plz
can i install this rom using twrp recovery
nokia alkng said:
hi bro
very thanx
and so sorry to late i wias busy
i wanna ask u plz
can i install this rom using twrp recovery
Click to expand...
Click to collapse
If you are S-OFF then you would flash it in fastboot. If you are S-ON then you will need to flash this nandroid backup in TWRP. You just need to extract the folder and place it in the folder with the rest of your TWRP backups. If you don't have any, then just get into TWRP and select Backup. Then just copy the file to the same folder as your last backup.
majmoz said:
Here is the stock rom 6.09.401.5 you will have to flash it in bootloader/FASTBOOT USB. Copy the file to your adb/fastboot folder and rename it rom.zip. Open a command window on that folder and type:
NOTE: please delete your serial number in the previous post.
Click to expand...
Click to collapse
bro steill
C:\Users\murissi\Desktop\fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\murissi\Desktop\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\murissi\Desktop\fastboot>fastboot flash zip rom.zip
sending 'zip' (1219890 KB)...
1 hur
majmoz said:
If you are S-OFF then you would flash it in fastboot. If you are S-ON then you will need to flash this nandroid backup in TWRP. You just need to extract the folder and place it in the folder with the rest of your TWRP backups. If you don't have any, then just get into TWRP and select Backup. Then just copy the file to the same folder as your last backup.
Click to expand...
Click to collapse
no bro its s -on
can u tech me how to make it s-off plz
nokia alkng said:
no bro its s -on
can u tech me how to make it s-off plz
Click to expand...
Click to collapse
Did you get the nandroid to work or did you try to flash ARHD 53.0 again? You also might try TWRP 2.6.3.3 it seems to work with most roms.
Here is firewater s-off it is the only free one that will work with your high hboot. If you get "whelp that sucks" message then firewater will not work for your phone. You then could try Sunshine S-OFF, however it will cost $25.
majmoz said:
If you are S-OFF then you would flash it in fastboot. If you are S-ON then you will need to flash this nandroid backup in TWRP. You just need to extract the folder and place it in the folder with the rest of your TWRP backups. If you don't have any, then just get into TWRP and select Backup. Then just copy the file to the same folder as your last backup.
Click to expand...
Click to collapse
broo stell like this
C:\Users\murissi\Desktop\fastboot>adb reboot bootloader
C:\Users\murissi\Desktop\fastboot> fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\murissi\Desktop\fastboot>fastboot flash zip rom.zip
sending 'zip' (1219890 KB)...
take more time what happen
nokia alkng said:
broo stell like this
C:\Users\murissi\Desktop\fastboot>adb reboot bootloader
C:\Users\murissi\Desktop\fastboot> fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\murissi\Desktop\fastboot>fastboot flash zip rom.zip
sending 'zip' (1219890 KB)...
take more time what happen
Click to expand...
Click to collapse
The rom will not flash properly since you are S-ON! You need to either apply the nandroid backup or a custom rom!
majmoz said:
The rom will not flash properly since you are S-ON! You need to either apply the nandroid backup or a custom rom!
Click to expand...
Click to collapse
good morning bro
good day
I'm very sorry I'm tired you a lot to me and I hope that a little to stell with me please
just i need the last The latter solution and conten
and what recomend md to do if you have any solution please tell me what to do
thanx
nokia alkng said:
good morning bro
good day
I'm very sorry I'm tired you a lot to me and I hope that a little to stell with me please
just i need the last The latter solution and conten
and what recomend md to do if you have any solution please tell me what to do
thanx
Click to expand...
Click to collapse
Download ARHD 81.0 to your phone
Flash TWRP 2.6.3.3 to your phone if not already on your phone
Boot into TWRP
Flash ARHD 81.0
In TWRP main menu select Backup
Stop here if you want and enjoy your phone.
S-OFF
-- Firewater
-- If it fails and you get the "whelp this sucks" msg then
-- Sunshine S-OFF
majmoz said:
Download ARHD 81.0 to your phone
Flash TWRP 2.6.3.3 to your phone if not already on your phone
Boot into TWRP
Flash ARHD 81.0
In TWRP main menu select Backup
Stop here if you want and enjoy your phone.
S-OFF
-- Firewater
-- If it fails and you get the "whelp this sucks" msg then
-- Sunshine S-OFF
Click to expand...
Click to collapse
hi bro
thanx
after flash rom with twrp after 1 mnt make restart and no imei and stell s-on:crying:
majmoz said:
Download ARHD 81.0 to your phone
Flash TWRP 2.6.3.3 to your phone if not already on your phone
Boot into TWRP
Flash ARHD 81.0
In TWRP main menu select Backup
Stop here if you want and enjoy your phone.
S-OFF
-- Firewater
-- If it fails and you get the "whelp this sucks" msg then
-- Sunshine S-OFF
Click to expand...
Click to collapse
so i flashed rom ystrday using fastboot
C:\android>adb reboot bootloader.
C:\android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\android>fastboot flash zip rom.zip
sending 'zip' (1219890 KB)...
OKAY [ 49.791s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 69.720s
C:\android>
but not sloved stell no imei
majmoz said:
Download ARHD 81.0 to your phone
Flash TWRP 2.6.3.3 to your phone if not already on your phone
Boot into TWRP
Flash ARHD 81.0
In TWRP main menu select Backup
Stop here if you want and enjoy your phone.
S-OFF
-- Firewater
-- If it fails and you get the "whelp this sucks" msg then
-- Sunshine S-OFF
Click to expand...
Click to collapse
cant get s off- becuse wifi on phone is stoped no imei
nokia alkng said:
so i flashed rom ystrday using fastboot
C:\android>adb reboot bootloader.
C:\android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\android>fastboot flash zip rom.zip YOU CAN NOT FLASH ROMs TO YOUR PHONE!!!
sending 'zip' (1219890 KB)...
OKAY [ 49.791s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 69.720s
C:\android>
but not sloved stell no imei
Click to expand...
Click to collapse
Just to be clear, where did it say to flash the rom in fastboot?
Originally Posted by majmoz View Post
Download ARHD 81.0 to your phone
Flash TWRP 2.6.3.3 to your phone if not already on your phone
Boot into TWRP
Flash ARHD 81.0 I should have said SELECT "install from sdcard"
In TWRP main menu select Backup
Stop here if you want and enjoy your phone.
S-OFF
-- Firewater
-- If it fails and you get the "whelp this sucks" msg then
-- Sunshine S-OFF
Click to expand...
Click to collapse
Did you make a backup as I instructed? If so, then copy the nandroid extracted folder to your phone in the same directory that backup is in /TWRP/BACKUP/<YOUR SERIALNO>/<NAME OF FOLDER>. Then boot into recovery and select Restore; you should see the extracted folder; select it. This will put your stock rom on your phone. If this doesn't restore your imei then you will need to return the phone to a service center.
majmoz said:
Just to be clear, where did it say to flash the rom in fastboot?
Did you make a backup as I instructed? If so, then copy the nandroid extracted folder to your phone in the same directory that backup is in /TWRP/BACKUP/<YOUR SERIALNO>/<NAME OF FOLDER>. Then boot into recovery and select Restore; you should see the extracted folder; select it. This will put your stock rom on your phone. If this doesn't restore your imei then you will need to return the phone to a service center.
Click to expand...
Click to collapse
hi bro
first happy day
how are u
plz
can u gave me that folder
nokia alkng said:
hi bro
first happy day
how are u
plz
can u gave me that folder
Click to expand...
Click to collapse
No, I can not.
I wanted tot post in the RUU post in the android development thread, but I wasn't allowed to...
I'm running Viper 6.2 on my htc one m7 with twrp 2.6.3 and I'm trying to update to the latest firmware so I can use viper 7.1. I'm trying to update tot he odified firmware, but don't mind if I have to do the full firmware. I just want the radios and functionality there and don't ind if I have to reflash twrp recovery.
I go through the instructions but I keep getting this error no matter what I try:
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.050s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot flash zip firmware.zip
sending 'zip' (44873 KB)...
OKAY [ 2.763s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.019s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot flash zip firmware.zip
sending 'zip' (44873 KB)...
OKAY [ 2.763s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.018s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>fastboot reboot
rebooting...
finished. total time: 0.042s
C:\Users\msing_000\Documents\HTC One Files\RED HTC ONE Root>
Click to expand...
Click to collapse
Can someone please help me through this?
Are you s-off?
Modified firmware = s-off
yes I am s-off
msingh95 said:
yes I am s-off
Click to expand...
Click to collapse
Could be a bad download.
Try a different USB port...USB 2 work best.
Try a different PC.
BD619 said:
Could be a bad download.
Try a different USB port...USB 2 work best.
Try a different PC.
Click to expand...
Click to collapse
So I checked again and I was wrong, I'm not S-Off...that was my other HTC ONE, I thought I'd done the same to this one.
But Now I'm having problems...I want to do a firmware update to fix Viper 7.0.1 issues with data/connectivity but it's still not letting me.
Will I be able to flash the updated firmware in the full version with S-On?
I've being running RumRunner all day on different computers and different usb ports...still no luck
msingh95 said:
So I checked again and I was wrong, I'm not S-Off...that was my other HTC ONE, I thought I'd done the same to this one.
But Now I'm having problems...I want to do a firmware update to fix Viper 7.0.1 issues with data/connectivity but it's still not letting me.
Will I be able to flash the updated firmware in the full version with S-On?
I've being running RumRunner all day on different computers and different usb ports...still no luck
Click to expand...
Click to collapse
Try Firewater for s-off.
Yes you can flash the Full Firmware while s-on but you will have to re-lock your bootloader to do so which means unlocking again and wiping your phone.
BD619 said:
Try Firewater for s-off.
Yes you can flash the Full Firmware while s-on but you will have to re-lock your bootloader to do so which means unlocking again and wiping your phone.
Click to expand...
Click to collapse
I tried firewater, but I don't understand how to push it to my phone...can I have some detailed help? the firewater page didn't help me much...
msingh95 said:
I tried firewater, but I don't understand how to push it to my phone...can I have some detailed help? the firewater page didn't help me much...
Click to expand...
Click to collapse
Put the firewater file in your adb/fastboot/platform tools folder, open a cmd window then copy and paste the commands on the firewater site.
BD619 said:
Put the firewater file in your adb/fastboot/platform tools folder, open a cmd window then copy and paste the commands on the firewater site.
Click to expand...
Click to collapse
everything worked out, got it all working, thanks!
Hi All,
Just wondering if anyone might have any other ideas for me, as I've reached the limit of my very limited skills.
I have an HTC one International, Australian Optus version.
It is running 7.21.980.5.
I don't know the history of this phone, but it came to me in a bootloop.
Phone was S-ON and untamptered.
I can boot into fastboot and RUU mode so can clear cache, flash zips etc.
I have now unlocked the bootloader and tried flashing every custom recovery version under the sun (and stock), as well as clearing cache everywhere and flashing stock boot.img
There does not seem to be an RUU available for this carrier (which would in theory get me out of this situation) and I can't get S-OFF to write superCID as the phone won't boot so can't use Firewater (it has HBOOT 1.66). The only full zips I can find are from nandroid backups, or Guru restores that require flashing the zip through recovery.
When I flash a recovery, it succeeds every time, but when I reboot for recovery, it has the white screen with 'entering recovery' for a few seconds, but then it reboots and tries to boot into normal mode again.
Anybody been able to get out of a similar situation, without flashing an RUU?
kamold said:
Hi All,
Just wondering if anyone might have any other ideas for me, as I've reached the limit of my very limited skills.
I have an HTC one International, Australian Optus version.
It is running 7.21.980.5.
I don't know the history of this phone, but it came to me in a bootloop.
Phone was S-ON and untamptered.
I can boot into fastboot and RUU mode so can clear cache, flash zips etc.
I have now unlocked the bootloader and tried flashing every custom recovery version under the sun (and stock), as well as clearing cache everywhere and flashing stock boot.img
There does not seem to be an RUU available for this carrier (which would in theory get me out of this situation)
Click to expand...
Click to collapse
Yes there is one but its only available at ir-file.com. File name is PN07IMG_M7_UL_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_425296_signed.zip
You'll need an account to download from this website which cost 15$, it take approx 1 day for your account to be active after payment. (I'm not affiliated with them btw). If you download the ruu please re-upoad on a free file hosting site like androidfilehost.com and share the link please so we can add it to the collection in the general section and help future user.
I can't get S-OFF to write superCID as the phone won't boot so can't use Firewater.
Click to expand...
Click to collapse
Anyway Firewater doesn't exist anymore, only way to s-off now in Sunshine S-OFF which cost 25 and still need the device to be booted anyway.
The only full zips I can find are from nandroid backups, or Guru restores that require flashing the zip through recovery.
When I flash a recovery, it succeeds every time, but when I reboot for recovery, it has the white screen with 'entering recovery' for a few seconds, but then it reboots and tries to boot into normal mode again.
Click to expand...
Click to collapse
Try unofficial twrp recovery by MDMower if it still doesn't work then you'll have to download that ruu from ir-file.com
Thanks very much for your reply @alray, I appreciate it!
Tried that TWRP, still the same issue. So I'll try and get hold of that RUU that you've posted and get back to you.
OK so I got the RUU, relocked the bootloader and tried to load it but I can't flash it. I get a 'could not allocate x bytes'.
I also can't do a fastboot erase userdata or internal (failed remote:not allowed).
I have a feeling that maybe the internal flash memory chip might be faulty.
unless anyone else has any other ideas?
kamold said:
OK so I got the RUU, relocked the bootloader and tried to load it but I can't flash it. I get a 'could not allocate x bytes'.
Click to expand...
Click to collapse
Can you post a screenshot of your command window, want to see everything from the beginning when you are trying to flash the RUU.
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.191s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot flash zip PN07IMG_M7_UL
_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_
425296_signed.zip
load_file: could not allocate 1639602889 bytes
kamold said:
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.191s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Software\htc\M7\One_All-In-One_Kit_v3.1\Data>fastboot flash zip PN07IMG_M7_UL
_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_
425296_signed.zip
load_file: could not allocate 1639602889 bytes
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash 7.xx.xxx.x RUU, get rid of this toolkit and use fastboot/adb directly from a command window.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_425296_signed.zip
htc_fastboot reboot
alray said:
You must use htc_fastboot.exe to flash 7.xx.xxx.x RUU, get rid of this toolkit and use fastboot/adb directly from a command window.
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Optus_AU_7.21.980.5_Radio_4T.35.3218.16_10.33Q.1718.01L_release_425296_signed.zip
htc_fastboot reboot
Click to expand...
Click to collapse
You sir are a gentleman and a scholar!
RUU loaded successfully.
Phone still bootloops though
Oh well.
kamold said:
You sir are a gentleman and a scholar!
RUU loaded successfully.
Phone still bootloops though
Oh well.
Click to expand...
Click to collapse
Is it bootlooping or stuck at htc white splash screen? First boot can take up to 10-15 minute and phone will stay at htc spash screen for that time.
Unfortunately if it still doesn't boot after flashing the ruu, its maybe an hardware problem.
Yeah I think it's hardware unfortunately. Starts and then reboots after about 20 seconds. Rinse and repeat.
I'll use the screen and housing and try and resurrect another phone.
Sent from my HTC One_M8 using Tapatalk
kamold said:
Yeah I think it's hardware unfortunately. Starts and then reboots after about 20 seconds. Rinse and repeat.
I'll use the screen and housing and try and resurrect another phone.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
would you mind sharing the ruu file. please...
rajivshahi said:
would you mind sharing the ruu file. please...
Click to expand...
Click to collapse
All the RUUs are here:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
kamold said:
All the RUUs are here:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
thanks a lot really appreciated.:good: