Database Develop

[SOLVED] No imei and ROM install seems incomplete

Hi all,
First, i would like to apologize for my poor english.
Then, i have some problems with my HTC M7.
Yesterday, when i woke up, my phone was shut down. I thought that i had no battery anymore. (i had less than 10% when i went to bed so, it's possible).
Well, plug my phone in the charger, and wait... and, when he booted, i could not use my phone as usually: no PIN code, no ability to make phone call... After a few minutes, i saw that the IMEI zone was empty.
I was not worrying, and though that a simple cache cleearing could help me... Well, it was not...
Now, i'm not able to use my phone AT ALL.
He's rooted, S-OFF, and i tried to install 3 or 4 different roms but same problem.
The ROM install has some difficulties to be finished: in fact, on each rom i tried to install, i have now the same problem;
-> No IMEI
-> When i want to compose a phone number, the dialer does not appear
-> A message "com.htc.htcdialer isn't responding" appears every minute...
I tried to install another dialer, same problem...
I'm really lost.
hope that somebody could help me?
Regards,
Cyril
PS: For information, after the incident, my phone was not rooted anymore and was S-ON, i don't know if it was already the case before the incident...

UPDATE: Finally, i succeed to install a rom.
Everything works fine now, but still no imei present...

This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.

Slim Shady said:
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Click to expand...
Click to collapse
Hi,
I've just started to work, but i will send you these informations as soon as possible.
Thanks a lot.

Slim Shady said:
This is a firmware problem. It seems your firmware has corrupted.Best way is download a RUU for ur phone and just flash it.K ur s-on>can u get me a getvar all.
access ur bootloader select fastboot and then type " fastboot getvar all " without quotes.
Click to expand...
Click to collapse
Re Slim Shady,
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm not sure about what to do.
May i have to switch on s-on? Or relock the bootloader?
I don't really know how to install a new firmware...

an idea?

Leodagan said:
Re Slim Shady,
Here are the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm not sure about what to do.
May i have to switch on s-on? Or relock the bootloader?
I don't really know how to install a new firmware...
Click to expand...
Click to collapse
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .

Slim Shady said:
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Click to expand...
Click to collapse
just a quick note, he's s-off, personally I would go with a 1.xx ruu (except 1.20.xxx.x)

Slim Shady said:
first please edit ur post and remove the imei and serial no from the post.Regarding ur problem download and flash this RUU http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Start the ruu and follow instructions like any windows application.If u have any questions feel free to ask .
Click to expand...
Click to collapse
Done for IMEI and Serial NO, thx.
I've started to download it.
nkk71 said:
just a quick note, he's s-off, personally I would go with a 1.xx ruu (except 1.20.xxx.x)
Click to expand...
Click to collapse
Ok, so have i to switch on s-on?
Also, have i stay on unlocked mode?
Thanks guys, really.

Guys,
I tried to install the RUU but it failed:
Update from 3.62.1700.1 to 4.19.401.9, i click on next, then next, then a message (in french so i translate to you):
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
Then, i can only click on ReadMe or Recovery, but nothing relevant after that.

Leodagan said:
Ok, so have i to switch on s-on?
Click to expand...
Click to collapse
Nooooo, do not go s-on!!

nkk71 said:
Nooooo, do not go s-on!!
Click to expand...
Click to collapse
Ok, i haven't done that, thanks ^^
So, now i'm stucked, i don't know what to do. Try another ruu?
I'm actually downloading RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe, is it ok?

Well, it's not ok, with this rom too i can't update my phone...
Maybe should i have to find a 3.62 RUU in order to update?

Leodagan said:
Well, it's not ok, with this rom too i can't update my phone...
Maybe should i have to find a 3.62 RUU in order to update?
Click to expand...
Click to collapse
What do you mean, can't update... you mean the ruu isn't working?
if so, then get this one: ruu_m7ul_1.28.401.7.zip
AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
then (after making sure MD5 is correct), rename the file to ruu.zip, and:
In bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
there is no need to relock bootloader or anything else with S-OFF (and stay S-OFF, don't even think about S-On!!)
if you want to see what kind of output to expect, check my guide http://forum.xda-developers.com/showthread.php?p=47794257&postcount=8 (post 8) which has a some visual feedback of what to expect. (disregard the guide, i'm just linking it for you to get an idea of what kind of output to expect)
Oh and you cannot do this on Win 8.1!!! http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 FAQ#1

nkk71 said:
What do you mean, can't update... you mean the ruu isn't working?
Click to expand...
Click to collapse
Yep, same message than the other ruu:
Update from 3.62.1700.1 to 1.2*******, i click on next, then next, then a message :
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
I'll try your last post, i let you know when finished.

Leodagan said:
Yep, same message than the other ruu:
Update from 3.62.1700.1 to 1.2*******, i click on next, then next, then a message :
The update tool cannot update the android phone,
Please obtain the right update tool and try again.
I'll try your last post, i let you know when finished.
Click to expand...
Click to collapse
HELL YES IT WORKS!!!
Thank you thank you !!
(well for the moment i'm in 4.1.2, i will wait a moment before flashing a new recovery, a new rom and all the stuff :laugh::laugh::laugh

Leodagan said:
HELL YES IT WORKS!!!
Thank you thank you !!
(well for the moment i'm in 4.1.2, i will wait a moment before flashing a new recovery, a new rom and all the stuff :laugh::laugh::laugh
Click to expand...
Click to collapse
and IMEI, baseband etc are all working again?

Yep, all is functional again... thanks again !

Leodagan said:
Yep, all is functional again... thanks again !
Click to expand...
Click to collapse
:good: :good: my pleasure.
BTW, if you going for 4.4 ROMs, use TWRP: get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
PS: for future reference about s-off vs s-on, check here http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 (under Not so FAQ #2)
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

Done.
Thank you again, guys.

[Q] M7 RUU failed stuck on RUU Boot

Hi, I bought a used m7 which was rooted and tried to return to stock. However the RUU installer failed and im now stuck with in bootloader which says TAMPERED and RELOCKED
here is 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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXX
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3887mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Can anyone tell me which ruu installer i should use or give any other suggestions?
Thanks

zirbenaum said:
Hi, I bought a used m7 which was rooted and tried to return to stock. However the RUU installer failed and im now stuck with in bootloader which says TAMPERED and RELOCKED
here is 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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXX
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3887mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Can anyone tell me which ruu installer i should use or give any other suggestions?
Thanks
Click to expand...
Click to collapse
do you know how to use adb and fastboot, also do you have drivers installed on your computer ?

Seanie280672 said:
do you know how to use adb and fastboot, also do you have drivers installed on your computer ?
Click to expand...
Click to collapse
yes i have drivers installed and i got the this info with fastboot. adb doesn't seem to recognize the phone though.

zirbenaum said:
yes i have drivers installed and i got the this info with fastboot. adb doesn't seem to recognize the phone though.
Click to expand...
Click to collapse
adb wont work in the bootloader, heres where the fun starts:
ADB commands only work in a booted rom or in a custom recovery, they don't work in the bootloader
Fastboot commands only work in the bootloader, they don't work in a booted rom or recovery.
phew.....glad we got that bit out of the way
first thing is first, can you start downloading this, its your reset rom file, but the servers are a little slow, that's why I say start, when its finished downloading, rename it to rom.zip for ease, and put it in the same folder on your computer where adb and fastboot files are please, heres the file: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
whilst that is downloading, you will need to goto HTC Dev and unlock your bootloader, just follow the instructions they give you, its a piece of cake, and as you already have adb and fastboot, you wont need to download the 3 files later on that they tell you to download: http://www.htcdev.com/bootloader/
your flags will then turn to UNLOCKED and TAMPERED, this is normal, nothing to worry about.
report back when done.

Seanie280672 said:
report back when done.
Click to expand...
Click to collapse
Ok i unlocked the bootloader and the phone booted! whew
Thank you so much!
It is till in rooted state tough but i guess it's better than bricked.

zirbenaum said:
Ok i unlocked the bootloader and the phone booted! whew
Thank you so much!
It is till in rooted state tough but i guess it's better than bricked.
Click to expand...
Click to collapse
the phone booted ? lol, that's strange, we're not finished yet lol, strange that it didn't boot whilst relocked but booted whilst unlocked.

Seanie280672 said:
the phone booted ? lol, that's strange, we're not finished yet lol, strange that it didn't boot whilst relocked but booted whilst unlocked.
Click to expand...
Click to collapse
Well I am not complaining The download takes more than two hours. What should i do after it is done?

zirbenaum said:
Well I am not complaining The download takes more than two hours. What should i do after it is done?
Click to expand...
Click to collapse
you could try one of the alternative links on that site, however, if your happy with your phone the way it is now then you wont need that file.
just scroll down the page a little and theres 2 alternative download links.

the ksn
Seanie280672 said:
you could try one of the alternative links on that site, however, if your happy with your phone the way it is now then you wont need that file.
just scroll down the page a little and theres 2 alternative download links.
Click to expand...
Click to collapse
I was hoping to get it in vanilla state but after this nightmare maybe it is better to leave it as it is until ive done some more research

zirbenaum said:
I was hoping to get it in vanilla state but after this nightmare maybe it is better to leave it as it is until ive done some more research
Click to expand...
Click to collapse
whats vanilla state ?, sorry im not familiar with that term, guess we can both teach each other something here

shall
Seanie280672 said:
whats vanilla state ?, sorry im not familiar with that term, guess we can both teach each other something here
Click to expand...
Click to collapse
Its software that is not customized. Wikipedia says:
Computer software, and sometimes also other computing-related systems like computer hardware or algorithms, is called Vanilla when not customized from its original form, meaning that it is used without any customizations or updates applied to it.
http://en.wikipedia.org/wiki/Vanilla_software
Maybe actual vanilla would be stock android without any htc customizatios though.

zirbenaum said:
Its software that is not customized. Wikipedia says:
Computer software, and sometimes also other computing-related systems like computer hardware or algorithms, is called Vanilla when not customized from its original form, meaning that it is used without any customizations or updates applied to it.
http://en.wikipedia.org/wiki/Vanilla_software
Maybe actual vanilla would be stock android without any htc customizatios though.
Click to expand...
Click to collapse
ahh I see, now that's where we were heading originally, to get pure stock rom you will need to download that file I linked you too earlier, and as your phone is booting now, just copy the file to your internal storage not into the adb and fastboot folder.
i'll tell you what to do next if you want to proceed.

Seanie280672 said:
ahh I see, now that's where we were heading originally, to get pure stock rom you will need to download that file I linked you too earlier, and as your phone is booting now, just copy the file to your internal storage not into the adb and fastboot folder.
i'll tell you what to do next if you want to proceed.
Click to expand...
Click to collapse
well the download is going to take forever and it is already 1 am here so maybe i have to do this some other time. But you can give the instuction and i'll do this later.
You have been very helpful, thank you again.

zirbenaum said:
well the download is going to take forever and it is already 1 am here so maybe i have to do this some other time. But you can give the instuction and i'll do this later.
You have been very helpful, thank you again.
Click to expand...
Click to collapse
when the file has finished downloading, check the MD5 and file size before copying it to your phone, just to make sure its not corrupt.
then what you will have to do, is copy that file you are downloading to your internal storage, then reboot your phone to the bootloader and plug it into the computer,. make sure it says fastboot usb on the screen.
then download this file: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
and put it in the same folder as adb and fastboot on your computer, open a command window (CMD) in that folder by holding control + shift + right mouse click in any white area of that folder and select open a command window here, then type the following commands one at a time, wait for each command to finish before issuing the next.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
once that is done, unplug your phone and enter recovery using the volume buttons to navigate and the power button to select.
when in recovery goto wipe and just swipe to factory reset, do not advanced wipe.
when done, goto install and in the list it gives you, select the file you downloaded and copied to your internal storage, swipe to begin the install, follow the instructions, and when it gives you the options, select yes wipe data, yes install stock radio and yes install stock recovery.
once installation is complete, it will ask you to reboot, when you select reboot, if the screen goes black (this doesn't always happen, most times it reboots without any problems), just hold down the power button until the lights on the bottom flash 10 to 15 times and then the phone will boot to full stock rom with OTA ability.
I know this sounds long and confusing, but you will see as you go along its easy, just don't skip any steps.
if you have any problems, just report back here, but if you follow my instructions it should run like clockwork.

Download official ruu from here http://www.htc1guru.com/downloads/ruu-file-downloads/ check the CID ... CID codes are given vit RUU .yrs is HTC_Y13 So try yur cid supported ruu. bootloader must b locked.

No OS, S-ON need desperate help

I need really bad help with my phone, it's s-on i cant install any roms and i cant restore from a backup anymore, i have twrp installed as of now, I have tried every method for getting s - off in the past but that was with a custom crappy rom so it didnt work.
Att htc one m7 32gb please add me on skype, i need direct help and i cannot just waiting on somebody to reply to this thread, please i seek desperate help my skype name is rtorr724, please i need someone that knows a lot about android and could help me fix this problem.
i can give you any other info you may need on skype to help me fix my problem. thanks.

rtorr724 said:
I need really bad help with my phone, it's s-on i cant install any roms and i cant restore from a backup anymore, i have twrp installed as of now, I have tried every method for getting s - off in the past but that was with a custom crappy rom so it didnt work.
Att htc one m7 32gb please add me on skype, i need direct help and i cannot just waiting on somebody to reply to this thread, please i seek desperate help my skype name is rtorr724, please i need someone that knows a lot about android and could help me fix this problem.
i can give you any other info you may need on skype to help me fix my problem. thanks.
Click to expand...
Click to collapse
Reboot into fastboot mode.
Hold Power + Volume Down until, select Fastboot.
Run this command:
Code:
fastboot getvar all
We can then get the CID/Model and Fastboot version so you can use an RUU to recover the device.

DennisBold said:
Reboot into fastboot mode.
Hold Power + Volume Down until, select Fastboot.
Run this command:
Code:
fastboot getvar all
We can then get the CID/Model and Fastboot version so you can use an RUU to recover the device.
Click to expand...
Click to collapse
I did not know what to look for so i just copy nd pasted all of it
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 000000000
(bootloader) imei: 0000000000
(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: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

rtorr724 said:
I did not know what to look for so i just copy nd pasted all of it
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
you can use that RUU to restore your phone: http://www.htc1guru.com/2014/03/att-ruu/
with s-on you must have a locked or re-locked bootloader use it.
and btw, remove imei and serialno from your above post.

alray said:
you can use that RUU to restore your phone:
with s-on you must have a locked or re-locked bootloader use it.
and btw, remove imei and serialno from your above post.
Click to expand...
Click to collapse
I install it through sideload correct?
also what could someone do with my imei and serialno?

rtorr724 said:
I install it through sideload correct?
Click to expand...
Click to collapse
No its an .exe file. You must launch that executable using a windows pc with the phone connected to it and booted in bootloader mode.
also what could someone do with my imei and serialno?
Click to expand...
Click to collapse
Someone could use it to clone your phone.

alray said:
No its an .exe file. You must launch that executable using a windows pc with the phone connected to it and booted in bootloader mode.
Someone could use it to clone your phone.
Click to expand...
Click to collapse
Well thank you for telling me about it I wouldn't have wanted that to happen.
The download is pretty slow so when its done ill post back here with my results

rtorr724 said:
Well thank you for telling me about it I wouldn't have wanted that to happen.
The download is pretty slow so when its done ill post back here with my results
Click to expand...
Click to collapse
ok, also make sure to check that the MD5 value of your downloaded file will match the value given on the website.
should be: 5f121d72b8fa3f6f1704588467752605
you can use winMd5 program to check the value.

alray said:
ok, also make sure to check that the MD5 value of your downloaded file will match the value given on the website.
Click to expand...
Click to collapse
The program failed to work and got error 155, the md5 value matched and my phone just went to a black htc screen.
Like i said before if someone could add me on skype so it would be easier to help that would be great
rtorr724 <- skype

rtorr724 said:
The program failed to work and got error 155, the md5 value matched and my phone just went to a black htc screen.
Like i said before if someone could add me on skype so it would be easier to help that would be great
rtorr724 <- skype
Click to expand...
Click to collapse
is your bootloader locked or unlocked?

alray said:
is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked

rtorr724 said:
unlocked
Click to expand...
Click to collapse
so go back and read post #4 again...

alray said:
so go back and read post #4 again...
Click to expand...
Click to collapse
._. im really stupid xD
so what do i do now?

rtorr724 said:
._. im really stupid xD
so what do i do now?
Click to expand...
Click to collapse
relock the bootloader and run the ruu....
to lock the bootloader:
Code:
fastboot oem lock

alray said:
relock the bootloader and run the ruu....
to lock the bootloader:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks so much! but how do i get unlocked again?

rtorr724 said:
Thanks so much! but how do i get unlocked again?
Click to expand...
Click to collapse
you can unlock again the same way you did the first time, using the unlock_code.bin you have received from htcdev.com. if the unlock code you already have doesnt work anymore, request a new unlock code by submitting you identifier token again.

alray said:
you can unlock again the same way you did the first time, using the unlock_code.bin you have received from htcdev.com. if the unlock code you already have doesnt work anymore, request a new unlock code by submitting you identifier token again.
Click to expand...
Click to collapse
I have one last problem, i got s-off and everything and now im trying to get cm12 5.0 and everytime i try to install it, it returns with the error
E:Error in /data/media/0/cm.zip
(Status 0)
Installation aborted.
And above that it says a bunch of stuff of failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory
and then it says the same thing for the unmount

rtorr724 said:
I have one last problem, i got s-off and everything and now im trying to get cm12 5.0 and everytime i try to install it, it returns with the error
E:Error in /data/media/0/cm.zip
(Status 0)
Installation aborted.
And above that it says a bunch of stuff of failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory
and then it says the same thing for the unmount
Click to expand...
Click to collapse
Which recovery are you using?

DennisBold said:
Which recovery are you using?
Click to expand...
Click to collapse
TWRP and CWM i get an error for both, i think its because when I wipe data/factory reset it gets rid of systtem

rtorr724 said:
TWRP and CWM i get an error for both, i think its because when I wipe data/factory reset it gets rid of systtem
Click to expand...
Click to collapse
I was more or less asking for your preference.
Your phone has partitions of memory which hold data, and when you update or install a custom ROM, the recovery utility mounts the partitions so they can be accessed to write and read data. Android does this every-time you turn on your phone. Formatting a partition doesn't delete it, it simply removes everything. CyanogenMod incorporated "block by name" mounting. Which basically makes it easier to mount partitions without being device specific.
Try this version of TWRP: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.7.1.1-m7.img
Anything above 2.7.1.1 should work, anything below will not.
For ClockWorkMod anything above 6.0.4.8 will work.

[Q] No SO, Drivers Problems, PLEASE HELP

Hi I'm going crazy right now, I really need some help, here's the history:
Today I bought a htc one m7 from a girl and when she was restoring it I saw that it was with a custom recovery, I didnt care about it becouse anyway I was going to install it some day. After that I went home and started searching some lollipop rom.
Well I downloaded it and copied it to the internal storage, I was ready to flash so I did it.
After flashing the rom it begins to bootloop, so I thougt "ok, it maybe need just a wipe" so I wiped it, as it didnt solved the problem I wiped again but this time with all boxes checked, after that y realized that I was wiping EVERYTHING (It happened before in a nexus 5 and 4).
Ok, I thought f**k it, I'll push the files with adb and problem solved, but when I conected the phone to the pc it has now driver problems, I cant get adb to work, neither fasboot, I installed and uninstalled al drivers I found on the internet, I really dont know what else to do.
If I conect the phone with the pc in fastboot mode in devices manager it says that the usb device ist recognized and something like that there is an error with the number.
And when I conect it in recovery mode it says "one" with the exclamation symbol, I red a lot of posts about how to solve it, but when I force install the drivers nothing happens.
Help me please, I dont know what more to do. And sorry about my english
If you need some information/pictures, just ask for it
Im new with this phone and I have no idea what to do

nachoy9 said:
Hi I'm going crazy right now, I really need some help, here's the history:
Today I bought a htc one m7 from a girl and when she was restoring it I saw that it was with a custom recovery, I didnt care about it becouse anyway I was going to install it some day. After that I went home and started searching some lollipop rom.
Well I downloaded it and copied it to the internal storage, I was ready to flash so I did it.
After flashing the rom it begins to bootloop, so I thougt "ok, it maybe need just a wipe" so I wiped it, as it didnt solved the problem I wiped again but this time with all boxes checked, after that y realized that I was wiping EVERYTHING (It happened before in a nexus 5 and 4).
Ok, I thought f**k it, I'll push the files with adb and problem solved, but when I conected the phone to the pc it has now driver problems, I cant get adb to work, neither fasboot, I installed and uninstalled al drivers I found on the internet, I really dont know what else to do.
If I conect the phone with the pc in fastboot mode in devices manager it says that the usb device ist recognized and something like that there is an error with the number.
And when I conect it in recovery mode it says "one" with the exclamation symbol, I red a lot of posts about how to solve it, but when I force install the drivers nothing happens.
Help me please, I dont know what more to do. And sorry about my english
If you need some information/pictures, just ask for it
Im new with this phone and I have no idea what to do
Click to expand...
Click to collapse
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone

clsA said:
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
Click to expand...
Click to collapse
Wow THANKS A LOT, I was doing something like that when installing drivers but not that, now I have adb working.
I dont want to do anything more wrong, can you tell me wich file to flash over TWR to get it working? my fastboot shows:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.44.0000
RADIO-A1.14.3250.13
OpenDPS-v26.120.274.0202
eMMC-boot
May 3 2013,19:16:59:-1
I cant post the getvar becouse I have windows 8.1 and as I saw, fastboot comands doesnt works with windows 8.1 if I have HBOOT-1.44

clsA said:
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
Click to expand...
Click to collapse
I used my grandmas PC
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot devices
HT36KW908410 fastboot
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------
(bootloader) imei: ------
(bootloader) meid: ------
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s

nachoy9 said:
I used my grandmas PC
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot devices
HT36KW908410 fastboot
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------
(bootloader) imei: ------
(bootloader) meid: ------
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
Click to expand...
Click to collapse
I would use this first
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe

clsA said:
I would use this first
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Click to expand...
Click to collapse
how does it work? I have to put the phone on fastboot mode or in a custom recovery for adb comands?

nachoy9 said:
how does it work? I have to put the phone on fastboot mode or in a custom recovery for adb comands?
Click to expand...
Click to collapse
just leave the phone plugged into the PC and in Fastboot USB mode on the bootloader screen
then run the RUU

clsA said:
just leave the phone plugged into the PC and in Fastboot USB mode on the bootloader screen
then run the RUU
Click to expand...
Click to collapse
Just made it, thanks a lot, do you know how to install updates now? becouse it doesnt find any OTA

nachoy9 said:
Just made it, thanks a lot, do you know how to install updates now? becouse it doesnt find any OTA
Click to expand...
Click to collapse
are you on the AT&T network ?

clsA said:
are you on the AT&T network ?
Click to expand...
Click to collapse
No, Im from Uruguay (South America)

nachoy9 said:
No, Im from Uruguay (South America)
Click to expand...
Click to collapse
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11

clsA said:
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Ill do it, THANKS A LOT

clsA said:
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Sorry Im bothering you again, but I tryed to install that RUU and it says that there is an error with the image version or something like that

nachoy9 said:
Sorry Im bothering you again, but I tryed to install that RUU and it says that there is an error with the image version or something like that
Click to expand...
Click to collapse
Did you change your CID?

clsA said:
Did you change your CID?
Click to expand...
Click to collapse
Yes

nachoy9 said:
Yes
Click to expand...
Click to collapse
your on 3.x 502 AT&T
try the 4.X.1540 DE RUU here >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
If it gives you an error flash this firmware then the RUU
https://www.androidfilehost.com/?fid=95887005526790121
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot

clsA said:
your on 3.x 502 AT&T
try the 4.X.1540 DE RUU here >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
If it gives you an error flash this firmware then the RUU
https://www.androidfilehost.com/?fid=95887005526790121
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Ok, ill try and tomorrow I tell you if it worked, thanks

HTC One m7 sprint Bricked??

Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.

Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!

yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.

so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk

Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.

murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.

xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.

murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk

Alright, thanks for the help!

I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery

raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....

alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy

raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.