Database Develop

[Q] One bricked when attempting a return to stock

Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.708.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Oops
(bootloader) imei: nothing to see here
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-14eb688c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Thanks for taking the time to read this, any pointers would be very much appreciated

I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.

kelvov said:
Hello there everyone, sorry to add another 'bricked' thread to the first page but it seems the more I try to fix my phone on my own, the deeper the hole I'm digging becomes.
About a week ago I installed Cyanogenmod via their installer. It was nice and straightforward but I soon began to miss Sense 5.5 so I set out to return my phone to stock. This was a few days ago and since then I have learned about flashing, rooting, fastboot etc., but I am now stuck where I cannot make it past the Cyanogenmod logo and I have absolutely no idea where to start fixing things. I can't make any progress as I do not have USB debugging mode enabled (nor can I enable it now) and I have no backup other than the automatic backup to Dropbox.
Below is my getvar output. Phone is 'TAMPERED' and 'UNLOCKED'. Oh, the phone is not rooted and was bought in Hong Kong but I use o2 in England. Please let me know If there is any more information I need to include.
Thanks for taking the time to read this, any pointers would be very much appreciated
Click to expand...
Click to collapse
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!

hp79 said:
I'm no expert, but maybe this can help.
Here's what I did with mine when I thought I bricked it. Keep in mind that I had a micro-USB to USB OTG cable. (costs less than $5)
Mine was bootloader unlocked, s-on but with hboot 1.55 or 1.54.
1. install TWRP recovery (openrecovery-twrp-2.6.3.3-m7.img) using fastboot.
2. Boot into TWRP recovery, then using OTG cable, mount a USB flash drive that has a installable zip image of the whole thing. I just used one from here:...
I got the "Download stock odexed 4.19.401.8" since I wanted to return it to stock like so I can return it.
I flashed it with that, and it would reboot into stock-like Android. I still had a bootloader from GoogleExperience version, and I accidentally did S-on before fixing these so I was screwed.
Anyways, that's how I got mine back to working state. After that, I couldn't get S-off (hboot 1.54) no matter what even using Rumrunner. Trying to get S-off again, I had to reflash the kernel with some other custom kernel, and then was able to do rumrunner to get s-off again. From that point, everything was easy, and I was able to reinstall real AT&T stock android using their RUU exe file. After that it installs OTA updates too.
Click to expand...
Click to collapse
Thanks for the info, will have to try it tomorrow after buying a cable
alray said:
Do you have a nandroid backup of your phone? Remove IMEI and S/N from your last post!!
Click to expand...
Click to collapse
Unfortunately no, I wrongly assumed a simple backup would have sufficed in the event anything went wrong. Never again. Oops, that for the heads up on that

You should be able to push ARHD 31.6 and be ok
sent from my mobile device

As if I'd never touched it

Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe

smartiejoe said:
Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
Click to expand...
Click to collapse
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI

alray said:
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
Click to expand...
Click to collapse
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(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: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s

smartiejoe said:
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(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: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.

alray said:
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
Click to expand...
Click to collapse
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.

smartiejoe said:
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
Click to expand...
Click to collapse
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.

S-OFF is a gift and should never be taken for granted. If you throw it away it may not be available to you again.
S-ON is an operation I would defer until I learned that I actually *need* to send in the phone to someone who cares if it is S-ON or not.
S-ON is always the last step in any "going back to stock " process, the very last thing before the phone leaves your possession. And even then the step is usually optional. Warranty repair people often don't care, eBay doesn't care, it's just really rare that there is *any* actual benefit.
Sent from my HTC One using xda app-developers app

alray said:
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
Click to expand...
Click to collapse
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible. Decent battery life, decent speed, and not too much hassle to return to complete stock if necessary.
I'll take your advice on what you think is best!

smartiejoe said:
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible.
Click to expand...
Click to collapse
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
smartiejoe said:
not too much hassle to return to complete stock if necessary.
Click to expand...
Click to collapse
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.

alray said:
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
Click to expand...
Click to collapse
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe

smartiejoe said:
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
Click to expand...
Click to collapse
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551

alray said:
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Click to expand...
Click to collapse
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?

smartiejoe said:
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
Click to expand...
Click to collapse
have you checked md5?
Maybe you could try another usb cable or another usb port

alray said:
have you checked md5?
Maybe you could try another usb cable or another usb port
Click to expand...
Click to collapse
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further

smartiejoe said:
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
Click to expand...
Click to collapse
Try another usb cable. You could also try the 1.28.401.7 ruu

alray said:
Try another usb cable. You could also try the 1.28.401.7 ruu
Click to expand...
Click to collapse
I just read somewhere that hboot 1.44 might be needed, and I have 1.54. So I shall flash 1.44 and see if it works then!
EDIT: When trying to flash hboot 1.44 it won't even send the 501kb zip file, even through a brand new usb cable. Updating drivers now to see if that works

Stock OTA does not find updates // broken stock recovery

hey guys,
i just wanted to go back to stock with my HTC ONE. I flashed the Guru Reset M7 3.62.401.1.zip on my device but now it won't find any system updates. Also the recovery seems to be broken. Even after flashing the recovery seperatly the phone only shows a red triangle when i try to enter the stock recovery.
It also does not find any updates with the SuperCID.
Do you have any idea how to fix that?
I have the international Version of the HTC ONE.
Thanks in advance!

Fabivons said:
hey guys,
i just wanted to go back to stock with my HTC ONE. I flashed the Guru Reset M7 3.62.401.1.zip on my device but now it won't find any system updates. Also the recovery seems to be broken. Even after flashing the recovery seperatly the phone only shows a red triangle when i try to enter the stock recovery.
It also does not find any updates with the SuperCID.
Do you have any idea how to fix that?
I have the international Version of the HTC ONE.
Thanks in advance!
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number, be sure to remove these two items before posting, there have been a lot of users on here lately looking for replacement imei numbers etc, I just had a PM asking me for one, with that info they could clone your phone.
next, are you sure the 401 ruu is yours, that's why I want your fastboot getvar all.
are you s-off ?
the red triangle is stock recovery.
if you are s-off, change your CID back to HTC__001, super cid is not in the 401 ruu's or OTA's

Seanie280672 said:
post your fastboot getvar all please without imei and serial number, be sure to remove these two items before posting, there have been a lot of users on here lately looking for replacement imei numbers etc, I just had a PM asking me for one, with that info they could clone your phone.
next, are you sure the 401 ruu is yours, that's why I want your fastboot getvar all.
are you s-off ?
the red triangle is stock recovery.
if you are s-off, change your CID back to HTC__001, super cid is not in the 401 ruu's or OTA's
Click to expand...
Click to collapse
thanks for your quick reply!
here is my getvar:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(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: 3741mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Fabivons said:
thanks for your quick reply!
here is my getvar:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(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: 3741mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Why not run this RUU it should put everything to stock since you are S-OFF?

majmoz said:
Why not run this RUU it should put everything to stock since you are S-OFF?
Click to expand...
Click to collapse
thanks fpr your help!
i tried to install the RUU but "fastboot.exe" crashes during the installation :/

Fabivons said:
thanks fpr your help!
i tried to install the RUU but "fastboot.exe" crashes during the installation :/
Click to expand...
Click to collapse
What exactly do you mean ? The RUU crashes in the middle of the installation ?

raghav kapur said:
What exactly do you mean ? The RUU crashes in the middle of the installation ?
Click to expand...
Click to collapse
This is waht happens

Fabivons said:
This is waht happens
Click to expand...
Click to collapse
the text says htc_fastboot.exe doesn't work anymore

Fabivons said:
the text says htc_fastboot.exe doesn't work anymore
Click to expand...
Click to collapse
Try uninstalling and reinstalling HTC Sync drivers. Or you can also try downloading the updated Android SDK and recreate the fastboot folder

raghav kapur said:
Try uninstalling and reinstalling HTC Sync drivers. Or you can also try downloading the updated Android SDK and recreate the fastboot folder
Click to expand...
Click to collapse
didn't change a thing :/
here is what i do:
0. deactivate anti- virus/firewall
1. start the RUU.exe
2. put my phone into fastboot mode
3. connect my phone via USB 2.0
4. start the flash progress
then after a few seconds htc_fastboot. exe crashes and the programm stops

Fabivons said:
didn't change a thing :/
here is what i do:
0. deactivate anti- virus/firewall
1. start the RUU.exe
2. put my phone into fastboot mode
3. connect my phone via USB 2.0
4. start the flash progress
then after a few seconds htc_fastboot. exe crashes and the programm stops
Click to expand...
Click to collapse
Which OS are you using ?

raghav kapur said:
Which OS are you using ?
Click to expand...
Click to collapse
windows 8.1 64bit

Fabivons said:
windows 8.1 64bit
Click to expand...
Click to collapse
Dont start the RUU first. First put the phone in fastboot mode, get the getvar to check if all's in order.
Once you getvar shows, it means the device is connected. After that, try the RUU
If still no luck, use RUU.zip

raghav kapur said:
Dont start the RUU first. First put the phone in fastboot mode, get the getvar to check if all's in order.
Once you getvar shows, it means the device is connected. After that, try the RUU
If still no luck, use RUU.zip
Click to expand...
Click to collapse
again no change... it always crashes within the first second
do you think it could work on ubuntu? i have a portable version! but my linux skill is -10.. do you think you could do that via temviever?

Fabivons said:
again no change... it always crashes within the first second
do you think it could work on ubuntu? i have a portable version! but my linux skill is -10.. do you think you could do that via temviever?
Click to expand...
Click to collapse
Im not sure that the portable version will work. Because even in Vmware, i couldnt get the adb drivers to work. Live CD would be a much better option IMO

raghav kapur said:
Im not sure that the portable version will work. Because even in Vmware, i couldnt get the adb drivers to work. Live CD would be a much better option IMO
Click to expand...
Click to collapse
sounds great! ...what is a Live CD and how does it work?

Fabivons said:
sounds great! ...what is a Live CD and how does it work?
Click to expand...
Click to collapse
A live CD is basically an OS running on a USB/CD. Instead of the portable version which runs within the Windows OS, you will boot directly from the USB containing Ubuntu. Nothing will happen to your existing Windows; once you're done with the RUU flashing process, just shut down the computer and unplug the USB
To get it running, download the Ubuntu image and click Download:
http://www.ubuntu.com/download/desktop/
Then, to prepare the bootable USB stick, this link:
unetbootin.net
Download that software. Choose the correct Ubuntu version and create the stick. Once you're done/ have doubts, let me know

raghav kapur said:
A live CD is basically an OS running on a USB/CD. Instead of the portable version which runs within the Windows OS, you will boot directly from the USB containing Ubuntu. Nothing will happen to your existing Windows; once you're done with the RUU flashing process, just shut down the computer and unplug the USB
To get it running, download the Ubuntu image and click Download:
http://www.ubuntu.com/download/desktop/
Then, to prepare the bootable USB stick, this link:
unetbootin.net
Download that software. Choose the correct Ubuntu version and create the stick. Once you're done/ have doubts, let me know
Click to expand...
Click to collapse
okay i'm as good as done.. what's next? ;p

Fabivons said:
okay i'm as good as done.. what's next? ;p
Click to expand...
Click to collapse
Cool. Now, you have to change the boot priority to the USB as first booting option. If you know how to do so, then proceed
If you don't, then there are two ways to depending on the pre-installed OS on your PC
Did your computer come with Windows 8/8.1 pre-installed or did it come with Win7 or older ?

raghav kapur said:
Cool. Now, you have to change the boot priority to the USB as first booting option. If you know how to do so, then proceed
If you don't, then there are two ways to depending on the pre-installed OS on your PC
Did your computer come with Windows 8/8.1 pre-installed or did it come with Win7 or older ?
Click to expand...
Click to collapse
i know how to change the priority
it's custom built
and i first installed windows 8.1 on it.

[Q] Not getting any signal

Hi, I have been reading this forum for 2 days straight trying everything and most of the things helped but now I am stuck.
My problem: I am trying to use the phone on Bell network. No signal, GSM status : Emergency Call Only. When I select Bell from network list it tells me that the SIM does not support the Network. If I put the same SIM in another phone it works and gets network.
My phone:
(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.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preffered Network Type : CDMA/EvDo/GSM/WCDMA/LTE auto
CWM: M7 TWRP Nandroid Backup CID BM___001 1.29.666.5
What I did:
1) Tried the tape method in case SIM card was not making proper contact with phone pins. (Than I realized that was nonesense since the phone was detecting my contacts...)
2) Flashed new firmware (6.06.401.1 came with radios nothing changed)
3) Installed the Bell Mobility Nandroid Backup (still nothing except I can now install the Bell applications from my SIM card)
I am looking for suggestions, ideas and possibly solutions. Any help is welcome!
Finxster

finxster said:
Hi, I have been reading this forum for 2 days straight trying everything and most of the things helped but now I am stuck.
My problem: I am trying to use the phone on Bell network. No signal, GSM status : Emergency Call Only. When I select Bell from network list it tells me that the SIM does not support the Network. If I put the same SIM in another phone it works and gets network.
My phone:
(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.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preffered Network Type : CDMA/EvDo/GSM/WCDMA/LTE auto
CWM: M7 TWRP Nandroid Backup CID BM___001 1.29.666.5
What I did:
1) Tried the tape method in case SIM card was not making proper contact with phone pins. (Than I realized that was nonesense since the phone was detecting my contacts...)
2) Flashed new firmware (6.06.401.1 came with radios nothing changed)
3) Installed the Bell Mobility Nandroid Backup (still nothing except I can now install the Bell applications from my SIM card)
I am looking for suggestions, ideas and possibly solutions. Any help is welcome!
Finxster
Click to expand...
Click to collapse
have you tried another sim in the HTC connected to a GSM network, I have a suspicious feeling you have a GSM phone there and Bell requires a CDMA phone, completely different partition layout.

Seanie280672 said:
have you tried another sim in the HTC connected to a GSM network, I have a suspicious feeling you have a GSM phone there and Bell requires a CDMA phone, completely different partition layout.
Click to expand...
Click to collapse
I tried Rogers SIM and it worked one shot.

finxster said:
I tried Rogers SIM and it worked one shot.
Click to expand...
Click to collapse
also, another thing ive noticed, is the firmware you flashed is a 401 firmware, thats WWE Europe, not 100% sure if that maybe at fault
I believe someone recently had success flashing developer edition firmware and RUU on their device and they were on Bell.
I'll see if I can find the thread, EDIT: http://forum.xda-developers.com/htc-one/help/dpes-developers-edition-canada-t2851008
Its got to worth a try, and easy to do as your s-off.

Seanie280672 said:
also, another thing ive noticed, is the firmware you flashed is a 401 firmware, thats WWE Europe, not 100% sure if that maybe at fault
I believe someone recently had success flashing developer edition firmware and RUU on their device and they were on Bell.
I'll see if I can find the thread, EDIT: http://forum.xda-developers.com/htc-one/help/dpes-developers-edition-canada-t2851008
Its got to worth a try, and easy to do as your s-off.
Click to expand...
Click to collapse
Oh dayum that was fast. I am going to try it now and get back to you with results.
Crossing fingers, toes and everything else....
dam harf to ttpe lije ths...
uncrossing fingers....
BRB
EDIT: Changed CID, MID is the same... downloading firmware
EDIT2: Flashed firmware downloading RUU
sidequestion: the RUU name 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... wouldn't that also be Europe specific @Seanie280672?
Also, I see my HBOOT is now 1.56...

finxster said:
Oh dayum that was fast. I am going to try it now and get back to you with results.
Crossing fingers, toes and everything else....
dam harf to ttpe lije ths...
uncrossing fingers....
BRB
EDIT: Changed CID, MID is the same... downloading firmware
EDIT2: Flashed firmware downloading RUU
Click to expand...
Click to collapse
be sure to check the MD5 and file size of the RUU before flashing, and if the download is a little slow, you can try this link instead, same RUU:
http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353887_signed_3.exe
no, WWE means world wide English.

Seanie280672 said:
be sure to check the MD5 and file size of the RUU before flashing
Click to expand...
Click to collapse
File size is 1.5 gb.... How do I check MD5?

finxster said:
File size is 1.5 gb.... How do I check MD5?
Click to expand...
Click to collapse
MD5 Check http://forum.xda-developers.com/showthread.php?t=1135620
i'll keep my fingers crossed for you :fingers-crossed:

Seanie280672 said:
i'll keep my fingers crossed for you :fingers-crossed:
Click to expand...
Click to collapse
They match!
noob question here... What is the command for fastboot to run an exe?
Nvm... >.> figured it out...

finxster said:
They match!
noob question here... What is the command for fastboot to run an exe?
Click to expand...
Click to collapse
there isn't one.
plug your phone into the computer and make sure it says fastboot USB on the screen, then double click the RUU.exe file and it will launch, follow the on screen instructions, flashing takes quite a while, about 10 mins I think mine took, and at points it will look like its stuck, not very reassuring I know, it got stuck at 5% for me and then suddenly jumped to 95%, then seemed to sit there forever until it finally completed.
EDIT: is your Bell sim still in the phone ?

@Seanie280672 Yep bell sim still in phone. Installing now

finxster said:
@Seanie280672 Yep bell sim still in phone. Installing now
Click to expand...
Click to collapse
good, because during set-up it should detect your sim and ask you to select your operator, im hoping Bell is in the list.

Seanie280672 said:
good, because during set-up it should detect your sim and ask you to select your operator, im hoping Bell is in the list.
Click to expand...
Click to collapse
It prepared installation and when I agreed and clicked next... it closed... I was running it as admin....

finxster said:
It prepared installation and when I agreed and clicked next... it closed... I was running it as admin....
Click to expand...
Click to collapse
damn, I had that problem once, its not the RUU at fault, its your computer, this is how I fixed it, its a bit long winded and you have to restart your computer after each installation, you need to install all of them one at a time, or you can try another computer if you have one available.
http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555

I want to take a minute and thank you @Seanie280672!!! I am going to go ahead and try it... I do however have another pc next to me so I will try running the RUU from that one in the meanwhile.

finxster said:
I want to take a minute and thank you @Seanie280672!!! I am going to go ahead and try it... I do however have another pc next to me so I will try running the RUU from that one in the meanwhile.
Click to expand...
Click to collapse
your welcome, but don't thank me yet, its not worked yet, im just sharing my knowledge which ive learned from others on this great forum.

Seanie280672 said:
damn, I had that problem once, its not the RUU at fault, its your computer, this is how I fixed it, its a bit long winded and you have to restart your computer after each installation, you need to install all of them one at a time, or you can try another computer if you have one available.
http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555
Click to expand...
Click to collapse
So, I got it to run on my main PC but there is a dialog box that makes me skip all the steps... will try on the laptop
Same on my laptop... ARUWizard Click here to next dialog... and I can't do anything else... clicking ok until the program is killed

finxster said:
So, I got it to run on my main PC but there is a dialog box that makes me skip all the steps... will try on the laptop
Same on my laptop... ARUWizard Click here to next dialog... and I can't do anything else... clicking ok until the program is killed
Click to expand...
Click to collapse
ive never seen that error before, but this would maybe explain it: http://www.solvusoft.com/en/files/e...windows/htc/rom-update-utility/aruwizard-exe/

http://forum.xda-developers.com/showthread.php?t=2666090
He has the same issue, however I am in bootloader fastboot usb mode... and still nothing... should I try RUU mode?
@Seanie280672

finxster said:
http://forum.xda-developers.com/showthread.php?t=2666090
He has the same issue, however I am in bootloader fastboot usb mode... and still nothing... should I try RUU mode?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50739768&postcount=4

[Q] Back to stock

hi, im trying to get my htc one m7sprint back to stock. I haven't used it recently and am thus very confused on how to get back to stock recovery and rom.
heres's some information about the phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.0913_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.04.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Mod Edit
(bootloader) imei: Mod Edit
(bootloader) meid: Mod Edit
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4102mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mod Edit = removed sensitive material

Easiest way would be to RUU...they can be found in Android Development, use 3.04.651.2 or higher.

when you say use 3.04 or higher could you tell me if this would work?
http://forum.xda-developers.com/showthread.php?t=2250904
I don't see a version number in this one

amskhan1 said:
when you say use 3.04 or higher could you tell me if this would work?
http://forum.xda-developers.com/showthread.php?t=2250904
I don't see a version number in this one
Click to expand...
Click to collapse
That one is older(version 1.29.651.10) then what you are currently on...so no you cannot use it.
This one matches what you are currently on.
http://forum.xda-developers.com/showthread.php?t=2508907
The higher the number the newer it is.
They can all be found HERE.

Hi, im having trouble running the ruu i'm getting the 170 error and my phone is still in fastboot usb mode. also when i try to reboot the phone into normal android it goes straight into bootloader. Do you know how to solve these problems? i found this information online, but i don't know how to get the drivers considering my phone is stuck in fastboot and isnt rebooting
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error

amskhan1 said:
Hi, im having trouble running the ruu i'm getting the 170 error and my phone is still in fastboot usb mode. also when i try to reboot the phone into normal android it goes straight into bootloader. Do you know how to solve these problems? i found this information online, but i don't know how to get the drivers considering my phone is stuck in fastboot and isnt rebooting
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
Click to expand...
Click to collapse
Try installing HTC Sync Manager it will install drivers needed.
Once it's installed you no longer need it so you can uninstall from your PC if you wish.

BD619 said:
Try installing HTC Sync Manager it will install drivers needed.
Once it's installed you no longer need it so you can uninstall from your PC if you wish.
Click to expand...
Click to collapse
thanks

Hey im, still getting error 170, with ruu version 2.0.5.2013. I already installed htc sync manager. I get to the part where it says verifying info on your pda phone.... please wait.
but after that it says error 170, usb connection error.
My phone is tagged with ****tampered*** , relocked, and security warning
Do you have any suggestions. (I have another htc one if i need to install some driver on my pc.
When i start my phone it only boots into bootloader. do i need an os on the phone for this?

amskhan1 said:
Hey im, still getting error 170, with ruu version 2.0.5.2013. I already installed htc sync manager. I get to the part where it says verifying info on your pda phone.... please wait.
but after that it says error 170, usb connection error.
My phone is tagged with ****tampered*** , relocked, and security warning
Do you have any suggestions. (I have another htc one if i need to install some driver on my pc.
When i start my phone it only boots into bootloader. do i need an os on the phone for this?
Click to expand...
Click to collapse
Only other things I can suggest are...
Make sure you are using the latest RUU.
Try a different cable OEM is best.
Try a different USB port (USB2 work the best).
Try a different PC.

BD619 said:
Only other things I can suggest are...
Make sure you are using the latest RUU.
Try a different cable OEM is best.
Try a different USB port (USB2 work the best).
Try a different PC.
Click to expand...
Click to collapse
kk thnx I'll try it

another question
amskhan1 said:
kk thnx I'll try it
Click to expand...
Click to collapse
I finally got the ruu to recognize my device, but it says from image version(3.04.651.2) to : image version then its just blank.
Is there supposed to be something there?

amskhan1 said:
I finally got the ruu to recognize my device, but it says from image version(3.04.651.2) to : image version then its just blank.
Is there supposed to be something there?
Click to expand...
Click to collapse
Yeah the version number of the RUU you are trying to flash.
Maybe you are using an older RUU?

I think i was using the 3_04_651_2 one that you suggested.

amskhan1 said:
I think i was using the 3_04_651_2 one that you suggested.
Click to expand...
Click to collapse
That one should work just fine...did you proceed and get an error or just stop when you saw the missing version?

BD619 said:
That one should work just fine...did you proceed and get an error or just stop when you saw the missing version?
Click to expand...
Click to collapse
I just stopped when i saw a missing version, didn't know if it would break the phone, so i should continue?

amskhan1 said:
I just stopped when i saw a missing version, didn't know if it would break the phone, so i should continue?
Click to expand...
Click to collapse
Yeah give it a shot.