Database Develop

IncS Boot loop Problem, Need HELP

Need help please!!!
I did a really bad mistake last week when I wanted to downgrade my HTC Incredible S to original ROM and now it loop on the HTC logo every 3 sec. Previously I installed iNcReDiBlESeNsEv4.0
ICS ROM and it worked like a charm. I just wanted to downgrade to orginal ROM so I execute the following RRU: RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe and this is where my nightmare begin. I’m now unable to access Recovery and stock on the HBOOT menu. I’m able to connect Fastboot and flash radio, flash recovery and boot but without success.
How could I make my recovery worked back and install ROM again? I really miss my Smartphone right now so please help a poor guy like me.
Here is the phone info:
fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.13.1002
(bootloader) version-baseband: 3805.04.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.46.669.1
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3212000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4098mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-8a731c6e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
From HBOOT menu:
-Revolutionary-
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.04.03.27_M
eMMc-boot
Apr 1 2011,18:34:39
Thanks in advance for your help!!!

No need to donwgrade if you have costum rom before. Just recovery with backup orig.rom
Sent from my HTC Incredible S using xda app-developers app

Thx for your answer,
How I do that? I'm not able to access recovery, it loop on the HTC logo when I select it from the HBOOT menu. I have a backup from clockwork that I did before doing my mistake but I don't know how to restore it.
Could I restore it from Fastboot?

Re install recovery change recovery to 4EXT, you can find thread on forum INC S. if you can access bootloader it will work flash recovery.img via CMD.
Sent from my HTC Incredible S using xda app-developers app

Link
http://forum.xda-developers.com/showthread.php?t=1136463
Sent from my HTC Incredible S using xda app-developers app

I tried to flash recovery using the following command:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
and the output was:
sending 'recovery' (3726 KB)...
OKAY [ 1.154s]
writing 'recovery'...
OKAY [ 0.756s]
finished. total time: 1.914s
But when I tried to access recovery from HBOOT menu, I always get the HTC logo loop. Do you have any idea why this happenning? I had 4Ext before, is-it could be the problem?
Thanks for your help

wesly.btm said:
Re install recovery change recovery to 4EXT, you can find thread on forum INC S. if you can access bootloader it will work flash recovery.img via CMD.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
I tried to flash recovery of 4Ext and clockwork without success, my phone is rebooting when I select recovery option. Any idea?

chris_Andrew said:
I tried to flash recovery of 4Ext and clockwork without success, my phone is rebooting when I select recovery option. Any idea?
Click to expand...
Click to collapse
OK, trying to absorb all the different things you have posted in different threads, so forgive me if ask something you already posted on a different thread.
You stated that you were running a custom ICS ROM prior to trying to flash a RUU, right?
Based on the getvar all info you posted, I would suggest you use this Bell Mobility RUU instead of the one you selected.
http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_199657_signed.exe
I would personally run the RUU without the phone connected and then extract the ROM.zip out of the %TEMP% directory and copy it to your sd card and rename it PG32IMG.zip.
Then boot into bootloder and let it flash it.
If that works, at least your phone should boot and then you could try flash either CWM or 4EXT recovery.

Thanks for your reply,
I already solved my problem last week end. After flashing recovery more then ten times and flashing radio with froyo and gingerbread without success during more then 5 hours, I fall on a post on xda saying that this is the latest ICS radio. I decided to give them a try and flash it using fastboot and guess what? My phone was able to boot and my recovery is now working.
I decided to stay with a custom Rom and try Nik Aura Rebirth Rom and I more then love it.
I'm so happy now and I will not retry to install RUU again .
Thanks everybody for your help and if someone have a similar problem don't hesitate to reply
Sent from my HTC Incredible S using xda app-developers app

chris_Andrew said:
I fall on a post on xda saying that this is the latest ICS radio. I decided to give them a try and flash it using fastboot and guess what? My phone was able to boot and my recovery is now working.
I'm so happy now and I will not retry to install RUU again
Click to expand...
Click to collapse
It shouldn't scare you off RUUs!
Sounds like your original problem was a bad/incorrect Radio Flash with the RUU.
What was your radio prior to the RUU?
Regardless, glad you solved it. Nothing more frightening than a potential brick!!

[Q] please help me restore my One

Good day all
I have been running CM 10.2 on my One for some months. Recently its started playing up so ive decided to go back to stock.
Ive googled the process. Fastboot works OK and see's my One connected OK.
Im having issues figuring out what RUU I should be downloading. Initially I went for RUU_M7_U_JB_50_HTC_Europe_1.29.401.2
After a number of minutes it failed and said something like it cannot use this on my phone. My phone is a UK purchased unlocked device. Can anyone point me at the correct RUUI should download?

Looking at the fastboot screen I can see that my OS is 2.24.401.8
hboot is 1.54.0000
Please, any pointers to get a stock OS installed and my device booting again.

phupton said:
Looking at the fastboot screen I can see that my OS is 2.24.401.8
hboot is 1.54.0000
Please, any pointers to get a stock OS installed and my device booting again.
Click to expand...
Click to collapse
you won't get much help till you post your fastboot getvar all results
minus your serial no and IEMI

clsA said:
you won't get much help till you post your fastboot getvar all results
minus your serial no and IEMI
Click to expand...
Click to collapse
Thanks for the starter...
form-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 00000000000
(bootloader) imei: 0000000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s

phupton said:
Thanks for the starter...
form-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
finished. total time: 0.080s
Click to expand...
Click to collapse
You can flash this (compatible with your firmware, CID & MID): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
if you want to receive OTAs, you'll need to select "stock recovery" (which will overwrite custom recovery).

nkk71 said:
You can flash this (compatible with your firmware, CID & MID): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
if you want to receive OTAs, you'll need to select "stock recovery" (which will overwrite custom recovery).
Click to expand...
Click to collapse
Happy to go totally stock. Ive unlocked my bootloader again this morning. How would I flash the zip file you have directed me to download. Apologies for my newbie/dangerous ignorance...

phupton said:
Happy to go totally stock. Ive unlocked my bootloader again this morning. How would I flash the zip file you have directed me to download. Apologies for my newbie/dangerous ignorance...
Click to expand...
Click to collapse
by flashing it in custom recovery (CWM or TWRP), just like any custom ROM.

nkk71 said:
by flashing it in custom recovery (CWM or TWRP), just like any custom ROM.
Click to expand...
Click to collapse
My phone will only boot to fastboot at the moment. ITs partially bricked. Any pointers on how to get CWM installed?

phupton said:
My phone will only boot to fastboot at the moment. ITs partially bricked. Any pointers on how to get CWM installed?
Click to expand...
Click to collapse
If you have unlocked bootloaders then download twrp or cwm and rename to recovery put the file in the fastboot folder.
Then type fastboot flash recovery recovery.img
this will flash the custom recovery.
http://forum.xda-developers.com/showthread.php?t=2173863 - CWM
http://forum.xda-developers.com/showthread.php?t=2247900 - TWRP

khandelwalsiddharth said:
If you have unlocked bootloaders then download twrp or cwm and rename to recovery put the file in the fastboot folder.
Then type fastboot flash recovery recovery.img
this will flash the custom recovery.
http://forum.xda-developers.com/showthread.php?t=2173863 - CWM
http://forum.xda-developers.com/showthread.php?t=2247900 - TWRP
Click to expand...
Click to collapse
Thanks. I should be able to get a custom recovery sorted pretty quick. Can you just give me a bit of a pointer on the flashing of the stock rom mentioned earleir

phupton said:
Looking at the fastboot screen I can see that my OS is 2.24.401.8
hboot is 1.54.0000
Please, any pointers to get a stock OS installed and my device booting again.
Click to expand...
Click to collapse
bro hboot 1.54 isn't supported for RUU. u have 2 downgrade 2 hboot 1.44 to use the RUU. follow nkk71's post on returning to stock

phupton said:
Thanks. I should be able to get a custom recovery sorted pretty quick. Can you just give me a bit of a pointer on the flashing of the stock rom mentioned earleir
Click to expand...
Click to collapse
Do one thing install a custom rom like ARHD etc. and then S-off your phone using rumrunner.

This is going to be one of those jobs that just fails and all I end up with is a bricked phone.
I am a mac user and was using a windows XP VM to communicate with me phone using fast boot... When I try to push a recovery image XP fails badly and reboots...
I can't boot camp my mac because I'm running without a CD drive and boot camp needs a CD drive before installation.
Any tips on how to get my phone sorted using a mac?

phupton said:
This is going to be one of those jobs that just fails and all I end up with is a bricked phone.
I am a mac user and was using a windows XP VM to communicate with me phone using fast boot... When I try to push a recovery image XP fails badly and reboots...
I can't boot camp my mac because I'm running without a CD drive and boot camp needs a CD drive before installation.
Any tips on how to get my phone sorted using a mac?
Click to expand...
Click to collapse
1- just use mac versions of fastboot & adb, i believe you can find them here: http://forum.xda-developers.com/showthread.php?t=2365506
(or google for them)
2- do you care about having your phone "out-of-the-box"? that entails much more work.Can you live with an UNLOCKED or RELOCKED bootloader, and possibly the TAMPERED sign?
3- if you don't care about ^^ (2), then just use the Guru Reset ROM, i linked before.
get adb and fastboot working on mac, then in bootloader/FASTBOOT USB:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb push <name of guru>.zip /data/media/0/
then in recovery choose "install" and select the Guru Reset ROM.

Ok so i reloaded the recovery image. Rebooted and hey presto Cyanogenmod 10.2 loaded again. Phone is now working BUT I would still like to go back to stock.
With that in mind I followed your instructions above and tried to load the Guru zip on to the SDCARD. The ADB process finishes and it says its copied the file over but I can never seem to find it whe i load the recovery and try to install from a zip file.
Questions. Am I right in thinking I can continue to load the Guru zip to attempt to get back to stock?
What am i doing wrong?

phupton said:
Ok so i reloaded the recovery image. Rebooted and hey presto Cyanogenmod 10.2 loaded again. Phone is now working BUT I would still like to go back to stock.
With that in mind I followed your instructions above and tried to load the Guru zip on to the SDCARD. The ADB process finishes and it says its copied the file over but I can never seem to find it whe i load the recovery and try to install from a zip file.
Questions. Am I right in thinking I can continue to load the Guru zip to attempt to get back to stock?
What am i doing wrong?
Click to expand...
Click to collapse
if your phone is booting up again
just copy the guru.zip to the phone storage from your mac
no need to "push" if your phone is booting up

To confirm, I am now copying the zip over.
Is there a chance of me bricking the phone again or will the Guru zip return the phone to stock and allow OTA updates?

phupton said:
To confirm, I am now copying the zip over.
Is there a chance of me bricking the phone again or will the Guru zip return the phone to stock and allow OTA updates?
Click to expand...
Click to collapse
yeah the Guru reset was designed to put the phone back to stock
it uses an Aroma installer .. choose Stock Recovery to be able to receive OTA in the future. but you won't be able to flash any custom roms or Root with the stock recovery

that seemed to do the trick. phone is back stock.
after initial setup t imediately downloaded and installed a small update. rebooted and then asked to download another 4.3 675mb big update. that one seemed to reset the devce to new again. after setup the 2nd time i can see it didnt work as the phone was as if i had just completed the guru install...
thoughts?

phupton said:
that seemed to do the trick. phone is back stock.
after initial setup t imediately downloaded and installed a small update. rebooted and then asked to download another 4.3 675mb big update. that one seemed to reset the devce to new again. after setup the 2nd time i can see it didnt work as the phone was as if i had just completed the guru install...
thoughts?
Click to expand...
Click to collapse
did the second update give an error or just didn't take ?

[Q] Error 171 on my htc one while running RUU

After months of thinking it through, i finally decided to give up on sense and try cyanogenmod... horrible desicion. I tried the installer and according to to the installer itself the install had concluded without error and all i had to do now was wait for my device to boot. When booting my device off andd after 5 minutes of beeing stuck in a bootloop, i realized that something had gone horribly wrong. I found many solutions online, but ended up narrowimg down to 2 options: wipe data/ factory reset and wipe dalvik through CWM or running a ruu to go bavk to stock and retry from there. Tried doing the wipe but i kept getting the error "Cant mount data" so i pretty much gave up on that option and went for running the RUU. Succesfully locked my bootloader again and all that was left for me to do was run the ruu and wait for my htc one to be running sense again! While going through the installer, i got an error at around the" 1/5" part of the ruu install (i used an exe) which said "error 171, check usb connection" and i also simultaniously got a pop up window that said "htc_fastboot.exe has stopped working" . At this point i really dont know what to do. PLEASE! Someone help me!

josevera30 said:
After months of thinking it through, i finally decided to give up on sense and try cyanogenmod... horrible desicion. I tried the installer and according to to the installer itself the install had concluded without error and all i had to do now was wait for my device to boot. When booting my device off andd after 5 minutes of beeing stuck in a bootloop, i realized that something had gone horribly wrong. I found many solutions online, but ended up narrowimg down to 2 options: wipe data/ factory reset and wipe dalvik through CWM or running a ruu to go bavk to stock and retry from there. Tried doing the wipe but i kept getting the error "Cant mount data" so i pretty much gave up on that option and went for running the RUU. Succesfully locked my bootloader again and all that was left for me to do was run the ruu and wait for my htc one to be running sense again! While going through the installer, i got an error at around the" 1/5" part of the ruu install (i used an exe) which said "error 171, check usb connection" and i also simultaniously got a pop up window that said "htc_fastboot.exe has stopped working" . At this point i really dont know what to do. PLEASE! Someone help me!
Click to expand...
Click to collapse
is your phone recognised by device manager? Are you using Windows and if so what version are you running?
Can you post a fastboot getvar all removing your serial number and imei please and let me know what RUU you are running?

stovie_steve said:
is your phone recognised by device manager? Are you using Windows and if so what version are you running?
Can you post a fastboot getvar all removing your serial number and imei please and let me know what RUU you are running?
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
im using windows 8 and the ruu is
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe

josevera30 said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
im using windows 8 and the ruu is
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
Click to expand...
Click to collapse
I think it's down to Windows 8 - fastboot isn't detecting the drivers Which is why it fails with error 171
Have you tried again with a Windows 7 PC?
I think there is a post on here about getting fastvoot drivers to work on Windows 8. I'll have a look

stovie_steve said:
I think it's down to Windows 8 - fastboot isn't detecting the drivers Which is why it fails with error 171
Have you tried again with a Windows 7 PC?
I think there is a post on here about getting fastvoot drivers to work on Windows 8. I'll have a look
Click to expand...
Click to collapse
Please help me! If you can find a fix, please do! i kind of hate the cyangenmod installer for getting me into this mess!! When i get back to stock i'll probably still try to put cyanogenmod on my htc one...

josevera30 said:
Please help me! If you can find a fix, please do! i kind of hate the cyangenmod installer for getting me into this mess!! When i get back to stock i'll probably still try to put cyanogenmod on my htc one...
Click to expand...
Click to collapse
Try this guide
http://forum.xda-developers.com/showthread.php?t=2232799

Followed the guide thoroughly but got this pop up window at the last step.

josevera30 said:
Followed the guide thoroughly but got this pop up window at the last step.
Click to expand...
Click to collapse
Does fastboot work normally or does it only fail when running an RUU, if that's the case uninstall HTC Sync if you have it installed. But leave drivers installed. HTC sync is known to cause problems with RUU's
But there is no RUU that will work for you since your device is s-on and on the latest firmware. Downgrading is not possible with s-on. At this point the best you can hope for is to flash a custom rom. At least you can get the phone booting that way.
Do if adb/fastboot is working normally just push a Rom and install it. If you can't get adb/fastboot working on your Windows 8 pc try my mini guide here to create a bootable Linux pen drive.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Does fastboot work normally or does it only fail when running an RUU, if that's the case uninstall HTC Sync if you have it installed. But leave drivers installed. HTC sync is known to cause problems with RUU's
But there is no RUU that will work for you since your device is s-on and on the latest firmware. Downgrading is not possible with s-on. At this point the best you can hope for is to flash a custom rom. At least you can get the phone booting that way.
Do if adb/fastboot is working normally just push a Rom and install it. If you can't get adb/fastboot working on your Windows 8 pc try my mini guide here to create a bootable Linux pen drive.
Click to expand...
Click to collapse
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!

josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
You can't use this RUU on your phone because its an older version. You need s-off to flash lower version RUU. You will need to either s-off your phone or restore it using a nandroid backup of 6.07.1540.1 or flash another custom rom like Danny suggested above. Look in this thread: http://forum.xda-developers.com/showthread.php?t=2355992 you might found a nandroid backup of that version. If you can find it just tell me and I'll upload mine for you. I also have the stock recovery for that version if needed.
to install cyanogenmod you need a recovery with block:by-name support like newer version of TWRP.
http://wiki.cyanogenmod.org/w/Install_CM_for_m7
http://wiki.cyanogenmod.org/w/HTC_fstab_updates

josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
Download the latest CWM recovery and flash it with fastboot. http://downloadandroidrom.com/file/HTCOne/recovery/M7CWM/recovery-clockwork-touch-6.0.4.8-m7.img
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Download CM11 here. Rename the file to rom.zip and place it in your fastboot folder on your pc.
http://downloadandroidrom.com/file/HTCOne/M7/roms/CM11/cm-11-20140624-NIGHTLY-m7.zip
Also download gapps rename it to gapps.zip and place it in your fastboot folder.
http://downloadandroidrom.com/file/gapps/PA/pa_gapps-stock-4.4.3-20140608-signed.zip
Boot your phone to cwm recovery and connect usb. Do a factory reset then in the command window type
Code:
adb push rom.zip /sdcard
Wait for the push to compmete
Code:
adb push gapps.zip /sdcard
again wait for completion, it's normal for the command window to appear unresponsive until the push completes.
Now use cwm to install the Rom.zip followed by gapps.zip.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
Any update?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Any update?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
He also asked me (via PM) a TWRP nandroid backup of stock 6.07.1540.1 which I have uploaded for him yesterday.
No update yet, still don't know if the OP will flash the rom or restore the nand but I think he wants to flash the rom (but have the nand just in case).

alray said:
He also asked me (via PM) a TWRP nandroid backup of stock 6.07.1540.1 which I have uploaded for him yesterday.
No update yet, still don't know if the OP will flash the rom or restore the nand but I think he wants to flash the rom (but have the nand just in case).
Click to expand...
Click to collapse
Lol, he was also pm me, last I herd he was having trouble pushing the cm11 Rom. After successful push the Rom was still not on the device.
I instructed him to use "mount usb storage" in cwm. Not heard anything since
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Solved!
Thank you so much for your help! I did a wipe data/ factory reset and used sideload to push and install cyanogenmod! Thanks for your help :good:

josevera30 said:
Thank you so much for your help! I did a wipe data/ factory reset and used sideload to push and install cyanogenmod! Thanks for your help :good:
Click to expand...
Click to collapse
Thanks for the update, good to know you got it sorted
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[SOLVED] flash firmware FAILED (remote: 12 signature verify fail)

Hello everyone,
I'm :
-S-on
-Tampered
-Unlocked/relocked ( it depends)
-SuperCID(OLD s-off)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34JW901775
(bootloader) imei: ***********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I reseted my phone with the gurureset to stock, but my phone bricks everytime I run an OTA
I wanted to update it manually the firmware so I can run an updated ruu on it "from here : the 7.19.401.2"
I tried everything but every time it fails and it gives me :
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 21.793s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 83.634s
Please help ?

Dammit, Now I tried the : htc_fastboot flash zip RUU.zip
RUU.zip = PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
Everything is OKAY! The progress finished on terminal, and the bar below HTC SILVER LOGO stuck on 95%
Then I rebooted the phone : fastboot reboot
Then it stuck on the bootloader/fastboot
I repeated the same op many times without success... I even tried to install twrp recovery but once I go into it brings me back to the fastboot..
HELP PLEASE

PLEASE HELP! I tried almost everything
I flashed many custom recoveries and stock/signed ones
I flashed The ZIP many times
Everything I try it gets me back to the fastboot with "Active cmdline overflow!"

xsodia said:
PLEASE HELP! I tried almost everything
I flashed many custom recoveries and stock/signed ones
I flashed The ZIP many times
Everything I try it gets me back to the fastboot with "Active cmdline overflow!"
Click to expand...
Click to collapse
active command line overflow is because you have flashed a rom not compatible with your phone. We see this problem often when ppl flash DLX rom on their M7. The partition of the DLX and M7 are not the same so when flashing the rom, it will corrupt your MISC partition. Flashing a ruu will not fix that problem since the MISC partition is not included in the RUU, its a unique partition for each device. This can be repaired by flashing a 'genric" MISC partition using a recovery made for this situation (the noBCB recovery).
Everything explained in this thread: http://forum.xda-developers.com/showthread.php?t=2739126

I followed the instructions but unluckily, entering the recovery didn't work and brings me always to the fastboot screen, what to do ?

Please help

xsodia said:
Please help
Click to expand...
Click to collapse
If you want help from me, quote my posts otherwise I don't receive any notifications.
xsodia said:
I followed the instructions but unluckily, entering the recovery didn't work and brings me always to the fastboot screen, what to do ?
Click to expand...
Click to collapse
Tried CWM 6.0.2.8? and 6.0.4.9-noBCB ?
This guide is the only method available to fix your phone.

alray said:
If you want help from me, quote my posts otherwise I don't receive any notifications.
Tried CWM 6.0.2.8? and 6.0.4.9-noBCB ?
This guide is the only method available to fix your phone.
Click to expand...
Click to collapse
I just tried the two recoveries you just mentioned, both of them didn't work :/

xsodia said:
I just tried the two recoveries you just mentioned, both of them didn't work :/
Click to expand...
Click to collapse
Well I really don't know. This is the only known fix for "active cmd line overflow". Do you know what file you have flashed exactly before this error?

alray said:
Well I really don't know. This is the only known fix for "active cmd line overflow". Do you know what file you have flashed exactly before this error?
Click to expand...
Click to collapse
I don't remember, I had this problem for about a year ago... When I tried to update to lollipop with the ruu mentioned above it stopped entering even the recovery!
The problem now is that I have to access recovery with my new hboot :/

xsodia said:
I don't remember, I had this problem for about a year ago... When I tried to update to lollipop with the ruu mentioned above it stopped entering even the recovery!
The problem now is that I have to access recovery with my new hboot :/
Click to expand...
Click to collapse
you should have fixed that before updating
have you tried flashing the [various] recoveries to the kernel partition, it worked for a few (but it also didnt work for quite a few)
Code:
fastboot flash boot <name of recovery>.img
fastboot reboot
^^ upon reboot it will try to boot into recovery (since it's now in the kernel partition, but if it still can't enter custom recovery,

nkk71 said:
you should have fixed that before updating
have you tried flashing the [various] recoveries to the kernel partition, it worked for a few (but it also didnt work for quite a few)
Code:
fastboot flash boot <name of recovery>.img
fastboot reboot
^^ upon reboot it will try to boot into recovery (since it's now in the kernel partition, but if it still can't enter custom recovery,
Click to expand...
Click to collapse
I will try! If it fails ? What I'm gonna do ? :/

nkk71 said:
you should have fixed that before updating
have you tried flashing the [various] recoveries to the kernel partition, it worked for a few (but it also didnt work for quite a few)
Code:
fastboot flash boot <name of recovery>.img
fastboot reboot
^^ upon reboot it will try to boot into recovery (since it's now in the kernel partition, but if it still can't enter custom recovery,
Click to expand...
Click to collapse
It didn't work dude, please help !!

xsodia said:
It didn't work dude, please help !!
Click to expand...
Click to collapse
not sure i can, sorry, i'll send you a PM tomorrow with "an idea"
if you want to test it... doubt it will work, could even brick your device.... but who knows

nkk71 said:
not sure i can, sorry, i'll send you a PM tomorrow with "an idea"
if you want to test it... doubt it will work, could even brick your device.... but who knows
Click to expand...
Click to collapse
Let's try it anyway ..

Im still waiting help please

xsodia said:
Im still waiting help please
Click to expand...
Click to collapse
you have mail, dont know if it will work or not, but give it a try
Let me know how it goes & good luck!!

nkk71 said:
you have mail, dont know if it will work or not, but give it a try
Let me know how it goes & good luck!!
Click to expand...
Click to collapse
sorry for bumping, but YAY
thread can be marked [SOLVED] i believe :victory:

Thanks man

[SOLVED] Can anyone help me fix my htc one m7?

I recently acquired an htc one m7. i decided it would be cool to root it and put a custom rom ( i have had experience in this i have done it on my s3 my galaxy tab 2.0 and a galaxy express) so i unlocked my bootloader, flashed a custom rom and rooted my device and i decided (stupidly) to erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching. i tried to gain s-off but with every solution i need to be booted up but i dont have an os so i cannot. i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors. i tried fastboot flashing it but it wont verify it. i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either. i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit. this did not work. ive tried different recovery (but not different versions of these recoveries) everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.

sethdrak3 said:
(...)erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching.
Click to expand...
Click to collapse
This is the most common situation here, no worries, it can be fixed easily.
i tried to gain s-off
Click to expand...
Click to collapse
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
but with every solution i need to be booted up but i dont have an os so i cannot.
Click to expand...
Click to collapse
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors.
Click to expand...
Click to collapse
What is the error exactly? What is your TWRP recovery version? What rom exactly?
i tried fastboot flashing it but it wont verify it.
Click to expand...
Click to collapse
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either.
Click to expand...
Click to collapse
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit.
Click to expand...
Click to collapse
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
Click to expand...
Click to collapse
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?

alray said:
This is the most common situation here, no worries, it can be fixed easily.
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
i thought i heard somewhere you needed s off to flash roms
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
What is the error exactly? What is your TWRP recovery version? What rom exactly?
my twrp is v2.6.0.1 and im trying to flash cm12
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i understand this now i was trying ever possibility and how do you get to RUU mode?
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35XW916185
(bootloader) imei: 354439055703575
(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: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
output from command "fastboot getvar all"
@alray
thank you for all your help. btw the toolkit is very useful for small things like writing new recoveries it makes it easier plus sometimes its less problematic
Click to expand...
Click to collapse

sethdrak3 said:
i thought i heard somewhere you needed s off to flash roms
Click to expand...
Click to collapse
No, you only need an unlocked bootloader + custom recovery installed.
my twrp is v2.6.0.1 and im trying to flash cm12
Click to expand...
Click to collapse
TWRP 2.6.0.1 is really outdated. Latest official version is 2.8.6.0 or (2.8.6.4 unofficial) and since 2014-05-01 you need at least twrp 2.7.0.8 to flash Cyanogenmod
i understand this now i was trying ever possibility and how do you get to RUU mode?
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
but it won't help flashing roms, only for signed RUU and Signed firmware same or newer version that match your CID, MID and base version( x.xx.502.x) so 3.17.502.3 or above
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
If you want to flash CM12, update your recovery.
You might want to read this, this and this
TWRP can be downloaded from here and here

thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.

sethdrak3 said:
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
Click to expand...
Click to collapse
you're welcome, that's one example why we are not suggesting to use any toolkits.
can you edit your title to "[SOLVED] Can anyone help me fix my htc one m7?" (go to your first post, click "edit" then click "go advanced" change your title and click "save changes) thanks