my mic isn't working and need to take in, I have a modified hboot, can I run stock RUU or do I need to revert my hboot? if so, does anyone have a link?
jpwhre said:
my mic isn't working and need to take in, I have a modified hboot, can I run stock RUU or do I need to revert my hboot? if so, does anyone have a link?
Click to expand...
Click to collapse
assuming you are s-off you can ruu any version you like, there are a few threads in the development section with some ruu's....but it will still show s-off, you can re-write the security flag with a fastboot command, I am sure a googel search will find the command...
flash recovery locked bootloader
mcerk02 said:
assuming you are s-off you can ruu any version you like, there are a few threads in the development section with some ruu's....but it will still show s-off, you can re-write the security flag with a fastboot command, I am sure a googel search will find the command...
Click to expand...
Click to collapse
thanks, going thru process of removing "relocked"
found these threads but for vzw and att
http://forum.xda-developers.com/showthread.php?t=2358738
http://forum.xda-developers.com/showthread.php?t=2475914
http://forum.xda-developers.com/showthread.php?t=2441299
download for flashing recovery on locked device comes with twrp for vzw and this command txt
modelid: PN0731000
cidnum: VZW__001
mainver: 1.10.605.8
btype:1
aareport:1
hbootpreupdate:3
I know if I change
cidnum to SPCS__001
mainver to 3.04.651.2 since that is the ruu I ran
and put a sprint twrp recovery in, I can flash the zip in bootloader, but I don't know if I change the modelid to pn072 or pn0721000
jpwhre said:
thanks, going thru process of removing "relocked"
found these threads but for vzw and att
http://forum.xda-developers.com/showthread.php?t=2358738
http://forum.xda-developers.com/showthread.php?t=2475914
http://forum.xda-developers.com/showthread.php?t=2441299
download for flashing recovery on locked device comes with twrp for vzw and this command txt
modelid: PN0731000
cidnum: VZW__001
mainver: 1.10.605.8
btype:1
aareport:1
hbootpreupdate:3
I know if I change
cidnum to SPCS__001
mainver to 3.04.651.2 since that is the ruu I ran
and put a sprint twrp recovery in, I can flash the zip in bootloader, but I don't know if I change the modelid to pn072 or pn0721000
Click to expand...
Click to collapse
You know we have a FAQ Guide for Sprint right?
Please don't mess with those links or you may end up with a shiny brick.
jpwhre said:
thanks, going thru process of removing "relocked"
found these threads but for vzw and att
http://forum.xda-developers.com/showthread.php?t=2358738
http://forum.xda-developers.com/showthread.php?t=2475914
http://forum.xda-developers.com/showthread.php?t=2441299
download for flashing recovery on locked device comes with twrp for vzw and this command txt
modelid: PN0731000
cidnum: VZW__001
mainver: 1.10.605.8
btype:1
aareport:1
hbootpreupdate:3
I know if I change
cidnum to SPCS__001
mainver to 3.04.651.2 since that is the ruu I ran
and put a sprint twrp recovery in, I can flash the zip in bootloader, but I don't know if I change the modelid to pn072 or pn0721000
Click to expand...
Click to collapse
Dont mess with links from verizon or att, not gonna end well, maybe a simpler way to accomplish your goal is to flash a stock rom, and flash a hex edited hboot, that is exactly what I did when I returned mine for repairs, its simple, a sprint tech wouldnt know the difference, if sending to HTC, I am sure they will know.... read this... http://forum.xda-developers.com/showthread.php?t=1786498 ....you can create an edited hboot to flash to your device, will be strictly cosmetic, and flash a stock rom, or a stock backup you may have made before you started modding.....a local sprint tech aint gonna know the difference.....
USB data will not work
I am S ON and my PC will not recognize by phone. I have win 8.1 using the updated universal naked drivers. My phone was recognized under this configuration for a couple months. I have tried several USB cords in different USB ports. I have tried three other computers. When I plug the phone into an outlet, I get a Slow Charge notification. When I try to run ADB Devices command on terminal after running ADB mode in TWRP I receive error: no Devices Found.
It seems obvious that I have a faulty USB port. Is there a way to return to stock without connecting to a computer and ridding TAMPERED from HBOOT? I just want to return to Sprint and see if one of the Techs can fix .
Thanks
Related
hi i have incredible s canadian version sasktel and i have try to install rom from ruu and i renamed it to pg32img.zip and i install from bootloader and when it finish the appear cid incorrect and failed and the device now is freezing on bootloader and it appear Security Warning and s-on and i cant use usb connection..how can i installed the orginal rom via memory card or what?
any body can help me??
hashnoz said:
hi i have incredible s canadian version sasktel and i have try to install rom from ruu and i renamed it to pg32img.zip and i install from bootloader and when it finish the appear cid incorrect and failed and the device now is freezing on bootloader and it appear Security Warning and s-on and i cant use usb connection..how can i installed the orginal rom via memory card or what?
any body can help me??
Click to expand...
Click to collapse
Before you attempted this, did you run AlphaRevX to gain S-OFF? Which RUU were you attempting to install? There was another thread about this 'Security Warning' on the HBOOT screen and I'm not sure the OP was able to get this resolved.
yes the phone was s-off but after i install the rom the phone back to s-onn now i cant connect via usb or connection just it appear 'Security Warning' how can install orginal rom?
hashnoz said:
yes the phone was s-off but after i install the rom the phone back to s-onn now i cant connect via usb or connection just it appear 'Security Warning' how can install orginal rom?
Click to expand...
Click to collapse
Here is the other thread about the Security Warning. You may want to read through it and see if any of the suggestions will work for you.
http://forum.xda-developers.com/showthread.php?t=1136041
The only way to get out of that is by flashing the stock RUU the phone came with. In your case it would have to be Sasktel and if that doesn't work because you receive the error "Main Version is Older!" then your screwed. Your going to have to wait until Sasktel or Bell releases their official gingerbread updates.
I am in the exact same boat as I am the composer of the thread from above lol.
Hi All My phone dead because I try to installed 2.30.405.1 from RUU extracted PG32IMG.zip. when phone is power ON top side write "Security Warning" MY Phone CID is HTC__038 (for Indian) but I had european Rom 2.12.405.7.
phone boot only fastboot and getvar /all info here
C:\fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.12.405.7
INFOserialno: HT15********
INFOimei: 35*************
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__038
INFObattery-status: good
INFObattery-voltage: 4168mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
I Installed 2.12.405.7 with goldcard. and new can't make goldcard because not ADB
I try add android_info.txt this text cidnum: HTC__038 but not worked
I hope I need Indian RUU Rom with CID: HTC__038 Or who know this Problem? and who can help me?
I had the same problem with my Bell IS, I just ran the ruu.exe from a Windows pc and it installed with no problems at all. Now I'm back to a stock rom, with no problems at all.
I am going to S-off and root again later, whenever a stable Rom comes round. If you don't have a stock RUU, you can get it on HTC'S website, if one for you carrier is available.
Sent from my HTC Incredible S using XDA Premium App
In official htc site can't find stock ruu installer for my IS with cid:HTC__038.
You can create a gold card and try flashing your original rom or the rom you were originally trying to flash on your phone.
Can you tell me were or how to make? I have not CID for Gold card
How to make w/o ADB and w/o XTC-Clip?
You can buy a card reader and try and make one that way. Then put the goldcard into the inc s.
Sent from my HTC Incredible S using XDA App
Have you tried to install the SaskTel ruu.exe gb upgrade from Windows?
If that won't work, then you will have to find the proper ruu for your phone and install via a pc.
Sent from my HTC Incredible S using XDA Premium App
sasktel ruu and zip file not worked - 'model id incorrect'
:-(
Try removing android.txt, leave it out and run ruu again.
It is pretty hard to brick a phone, it just takes some time and a lot of trying different things, but you should be able to succeed.
Sent from my HTC Incredible S using XDA Premium App
ste1164 said:
You can buy a card reader and try and make one that way. Then put the goldcard into the inc s.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
How to I do. I have card reader from my Laptop
budleyca said:
Try removing android.txt, leave it out and run ruu again.
It is pretty hard to brick a phone, it just takes some time and a lot of trying different things, but you should be able to succeed.
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Not worked
i need to bypass signature checking (it is my problem)
what i made:
first it boot in fastboot, then erase cache, boot ruu mode and
ran installer ruu 2.12.405.7 then i change android_info.txt
modelid: PG3213000
cidnum: HTC__038
mainver: 2.12.405.7
hbootpreupdate:13
made pack rom.zip and overwrite original rom.zip (temp folder)
but installer sad sending, cleaning user data, and checking signature and stoped - "incorrect signature"
what i must do?
kuba28ms said:
i need to bypass signature checking (it is my problem)
what i made:
first it boot in fastboot, then erase cache, boot ruu mode and
ran installer ruu 2.12.405.7 then i change android_info.txt
modelid: PG3213000
cidnum: HTC__038
mainver: 2.12.405.7
hbootpreupdate:13
made pack rom.zip and overwrite original rom.zip (temp folder)
but installer sad sending, cleaning user data, and checking signature and stoped - "incorrect signature"
what i must do?
Click to expand...
Click to collapse
The only way to by-pass the HTC signature check in RUU mode is if you have S-OFF (security off).
so no way to repair phone?
kuba28ms said:
so no way to repair phone?
Click to expand...
Click to collapse
Ok so I have gone back and reread your posts. I would suggest you go back and try flashing 2.30.405.1 instead of trying to go back to 2.12.405.7. According to your getvar output, the radio from the 2.30.405.1 has been flashed. It would probably help if you could make a gold card and then try flashing the 2.30.405.1 RUU. Or you can try it without a gold card.
Ok so long story short,, I think I messed my htc one pretty bad today.
1)I installed 1.28.401.7 update from this thread:http://forum.xda-developers.com/showthread.php?t=2305490 <----I changed the CID of the phone to 11111 when doing this
2)After that I installed the custom rom from trickdroid.
3)Then I installed the 30 steps volume or something and my phone would just freeze with the htc boot logo. After several on and off and still being freezed, I think I erased the current rom.
4)Then with NO rom on the phone , I changed the Model ID and basically here's my info from the txt that I filled in:
modelid: PN07120
cidnum:HTC__Y13 VZW__001
mainver: 1.28.401.7
btype:1
aareport:1
hbootpreupdate:12
I followed this guide to do the above steps
http://forum.xda-developers.com/showthread.php?t=2322820
Only after flashing that PN07120(model id found in the back of the phone) that I read on fastboot that the model number was PN0712000.
But still everything went fine and my phone was already unlocked and s-off before I changed CID and MID. My phone was now displaying HTC_001 and PN071000 as model.
After trying to reflash the 1.28.401.7 firmware, I had no luck...tried the:
RUU_M7_UL_JB_50_Cingular_1.26.502.12
RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3 but still no luck.
when I do adb devices, it doesn't find any device...after that I tried a fastboot command to relock the bootloader and it DID work. So fastboot is working. But nothing can be mounted while i'm in recovery e.g can't mound /sd card....etc
So I'm basically left with a phone with no rom, just bootloader(relocked) and recovery(cwm). Any help would be really appreciated. I'm quite stressed right now for having damaged my phone permanently and being such a noob .
About to go to bed, I'll try to flash via RUU.zip and will post tomorrow. if i get any success
Dude, you're messing around with incredibly sensitive partitions and parameters in a really haphazard way, I'm surprised your device isn't already bricked. However if you can use fastboot then you're phone is likely salvageable. You could try following this guide to push a ROM to your phone and flash that to get it running again. Is your phone now s-off?
Hello members of XDA,
I ran into a problem trying to restoring my Htc One back to sense version, it sais on the conversion thread that I should have a backup of my original Hboot, which I do not have. I don't know if that's a problem, i downloaded the 1.44 hboot as I guess that's the one I should use to get back to stock. As of now I have S off, and am on hboot 1.54 and on official GPE.
Now comes the part where I'm stuck, I do not know what kind of RUU I need to return to stock, I know I need the hboot 1.44 one but I don't want any problems with bloatware or flashing a wrong baseband etc. Can anyone point me in the right direction of the right RUU? To be sure I'm pasting a getvar all
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-OFF
serialno: xxxx
imei: xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: off
Stefan0vic said:
Hello members of XDA,
I ran into a problem trying to restoring my Htc One back to sense version, it sais on the conversion thread that I should have a backup of my original Hboot, which I do not have. I don't know if that's a problem, i downloaded the 1.44 hboot as I guess that's the one I should use to get back to stock. As of now I have S off, and am on hboot 1.54 and on official GPE.
Now comes the part where I'm stuck, I do not know what kind of RUU I need to return to stock, I know I need the hboot 1.44 one but I don't want any problems with bloatware or flashing a wrong baseband etc. Can anyone point me in the right direction of the right RUU? To be sure I'm pasting a getvar all
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-OFF
serialno: xxxx
imei: xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: off
Click to expand...
Click to collapse
well all your getvar really shows is yes you converted to GPE
what was the phone before you converted it ? CID - MID and version-main
clsA said:
well all your getvar really shows is yes you converted to GPE
what was the phone before you converted it ? CID - MID and version-main
Click to expand...
Click to collapse
Thank god I saved that all in a word document,
Well my Cid was HTC__E11 it is now supercid, the version main was 4.19.401.11
my model ID was and still is PN0710000
Stefan0vic said:
Thank god I saved that all in a word document,
Well my Cid was HTC__E11 it is now supercid, the version main was 4.19.401.11
my model ID was and still is PN0710000
Click to expand...
Click to collapse
Then download this
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
change you CID back with fastboot
fastboot oem writecid HTC__E11
here's the 1.44 hboot >> https://www.dropbox.com/s/xyqurk33yh409bi/orig_hboot_1.44.0000_M7_RUUmode.zip
flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip <name of hboot>.zip
fastboot reboot
then run the RUU .exe you should be back to almost stock
clsA said:
Then download this
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
change you CID back with fastboot
fastboot oem writecid HTC__E11
here's the 1.44 hboot >> https://www.dropbox.com/s/xyqurk33yh409bi/orig_hboot_1.44.0000_M7_RUUmode.zip
flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip <name of hboot>.zip
fastboot reboot
then run the RUU .exe you should be back to almost stock
Click to expand...
Click to collapse
Thank you so much,
Why do so many threads advice to run 1.44 RUU though? After this I will have 1.44 hboot with android 4.4.2?
Edit: Download is taking aprox 2-3 hrs. Is there any way I can download it a little bit faster?
Stefan0vic said:
Thank you so much,
Why do so many threads advice to run 1.44 RUU though? After this I will have 1.44 hboot with android 4.4.2?
Edit: Download is taking aprox 2-3 hrs. Is there any way I can download it a little bit faster?
Click to expand...
Click to collapse
try here
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
and no you have hboot 1.56 after the RUU step
the hboot 1.44 insures the RUU will work smoothly
it's also a vital step if you want to remove tampered and show locked instead of relocked
to return for repair
clsA said:
try here
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Click to expand...
Click to collapse
Saw you edited your post, thank you so much
Stefan0vic said:
I'll just keep my pc on for a bit Thank you so much for your help.
Just 1 more question, will my bootloader be updated with the RUU itself? I need the phone as much stock possible since I need to give it for warranty for camera replacement.
Click to expand...
Click to collapse
now we are getting somewhere
before running the RUU you have more work then
you have to remove the tampered flag and lock before running the RUU
use this tool to do both >> http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
from @nkk71 SuperGuide
Method 2: Guru Bootloader Reset, more automated, but may freeze
adb push Guru_Bootloader_Reset_1.0.zip /data/media/
in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"
go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
adb reboot bootloader
and confirm no TAMPERED and LOCKED status
Click to expand...
Click to collapse
clsA said:
now we are getting somewhere
before running the RUU you have more work then
you have to remove the tampered flag and lock before running the RUU
use this tool to do both >> http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
from @nkk71 SuperGuide
Click to expand...
Click to collapse
I dont have the tampered flag so i guess i dont have to do that,
I will use that to get my bootloader locked though, thank you. RUU is still downloading as we speak but I can almost run it
So its:
1. Flash hboot
2. lock bootloader
3. run RUU?
Help!! It returns me with an image fault!!
Error: 158 !
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Stefan0vic said:
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Click to expand...
Click to collapse
don't panic .. just use a different ruu
clsA said:
don't panic .. just use a different ruu
Click to expand...
Click to collapse
I'm trying, I just don't know which one since I can't find an RUU that matches my radio
Stefan0vic said:
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Click to expand...
Click to collapse
ERROR [110]: FILE OPEN ERROR
This error message indicates that the RUU lacks some specific files or they are damaged, so the RUU cannot continue with the update. You have to get the complete RUU package and try again.
ERROR [120]: MAIN BATTERY POWER
This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).
ERROR [130]: MODEL ID ERROR
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone.
Sent from my HTC One using XDA Premium 4 mobile app
I know what the error means, but I don't know what RUU I need, i thought it accepted everything since I was s off
Stefan0vic said:
I'm trying, I just don't know which one since I can't find an RUU that matches my radio
Click to expand...
Click to collapse
did you change your CID ?
if so put it back to supercid and try
also did you md5 check your download
did you flash the 1.44 hboot ?
RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1
File Size: 1.5 GiB - Downloads: 69507
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Comments: modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
after 69,000 plus downloads you think someone would report if it's a bad file
clsA said:
did you change your CID ?
if so put it back to supercid and try
also did you md5 check your download
did you flash the 1.44 hboot ?
after 69,000 plus downloads you think someone would report if it's a bad file
Click to expand...
Click to collapse
Yes I flashed the 1.44 HBOOT,
can I flash supercid with relocked bootloader?
I'll try another RUU in a bit. Does it matter that radio's dont match?
Stefan0vic said:
Yes I flashed the 1.44 HBOOT,
can I flash supercid with relocked bootloader?
I'll try another RUU in a bit. Does it matter that radio's dont match?
Click to expand...
Click to collapse
if you locked the bootloader all you can't do is flash a recovery (I think ? )
for a RUU all your really interested in is the x.xx.401.x part
clsA said:
if you locked the bootloader all you can't do is flash a recovery (I think ? )
for a RUU all your really interested in is the x.xx.401.x part
Click to expand...
Click to collapse
Tried another .401. ruu and its now giving usb error..
I have no idea what im doing wrong. Should HTC Sync be installed for this?
Stefan0vic said:
Tried another .401. ruu and its now giving usb error..
I have no idea what im doing wrong. Should HTC Sync be installed for this?
Click to expand...
Click to collapse
well if you flashed the 1.44 hboot your pc must work in fastboot
what state is the phone in when you run the RUU ? bootloader / recovery / Android OS ?
Hi,
I'm really stressing out right now because my HTC one is stuck in bootloader and i think i've tried everything.
Basically i thought it would be fun to root my phone (first time), i used the cyanogenmod installer. But i really did not like the looks of thing and actually wanted to go back to sense 6. Although i can't really remember what i actually did to remove CM, but i managed to. And now all i get is the fastboot/bootloader screen.
Adb won't recognize my phone, USB-debugging is turned off, S-ON, and bootloader is RELOCKED.
I have not flashed a recovery even though i did try to but failed.
I really have no clue what to do now.
Please is there still a solution or did i screw up my phone for good?
Thanks in advance, Giagi
Giagi said:
Hi,
I'm really stressing out right now because my HTC one is stuck in bootloader and i think i've tried everything.
Basically i thought it would be fun to root my phone (first time), i used the cyanogenmod installer. But i really did not like the looks of thing and actually wanted to go back to sense 6. Although i can't really remember what i actually did to remove CM, but i managed to. And now all i get is the fastboot/bootloader screen.
Adb won't recognize my phone, USB-debugging is turned off, S-ON, and bootloader is RELOCKED.
I have not flashed a recovery even though i did try to but failed.
I really have no clue what to do now.
Please is there still a solution or did i screw up my phone for good?
Thanks in advance, Giagi
Click to expand...
Click to collapse
first thing is first, get your bootloader unlocked again, you cant do anything to fix your phone before you do that, and that is why the recovery failed to install, once that is done, download and install TWRP recovery 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7 it has the best success rate, and flash it.
Fastboot commands are for when you are in the bootloader, ADB is only for when you are in recovery and in a ROM.
Once all that is done you will be able to push and flash any custom ROM.
ps, put USB debugging out of your mind, it has nothing to do with what you are trying to do.
Thanks for your respond. But as far as i can tell i either need to enable USB-debugging in order to unlock bootloader, or i need to do it via htcdev for which i need adb to recognize my phone. Or did i miss anything?
I did not use the htcdev method the first time so i do not have a token.
Giagi said:
Thanks for your respond. But as far as i can tell i either need to enable USB-debugging in order to unlock bootloader, or i need to do it via htcdev for which i need adb to recognize my phone. Or did i miss anything?
I did not use the htcdev method the first time so i do not have a token.
Click to expand...
Click to collapse
Do you have your USB drivers installed on your computer, can you post a screen shot of your device manager whilst your phone is plugged into the PC ?
USB debugging is only for when you are booted into a ROM, and as you don't have a working rom on your phone, it doesn't apply.
Are you S-OFF ?
If not then you will have to goto HTC Dev and follow their instructions on how to unlock your bootloader
Put your phone in bootloader mode, plug it into the PC, it will then say fastboot USB, not ADB USB, ie fastboot commands not ADB commands.
post your fastboot getvar all please.
Seanie280672 said:
Do you have your USB drivers installed on your computer, can you post a screen shot of your device manager whilst your phone is plugged into the PC ?
USB debugging is only for when you are booted into a ROM, and as you don't have a working rom on your phone, it doesn't apply.
Are you S-OFF ?
If not then you will have to goto HTC Dev and follow their instructions on how to unlock your bootloader
Put your phone in bootloader mode, plug it into the PC, it will then say fastboot USB, not ADB USB, ie fastboot commands not ADB commands.
post your fastboot getvar all please.
Click to expand...
Click to collapse
First of all, thank you so much! I've now been able to unlock bootloader and flash CWM.
But there's just one more thing, and i'm sorry but i'm very noob with this: How can i find and install the stock HTC ROM (sense 6)?
I downloaded Android Revolution HD 71.1 and installes the zip via CWM but it does not seem to work.
EDIT: Im an S-On
And as requested my getvar all:
Code:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.1540.9
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__E11
battery-status: good
battery-voltage: 4329mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Giagi said:
First of all, thank you so much! I've now been able to unlock bootloader and flash CWM.
But there's just one more thing, and i'm sorry but i'm very noob with this: How can i find and install the stock HTC ROM (sense 6)?
I downloaded Android Revolution HD 71.1 and installes the zip via CWM but it does not seem to work.
Click to expand...
Click to collapse
It doesn't work because you installed CWM, I said install TWRP recovery 2.6.3.3, most custom rom's require that recovery, it should also mention that in the original thread of the rom you flashed.
I will need your fastboot getvar all output in order to know what your stock rom is.
Seanie280672 said:
It doesn't work because you installed CWM, I said install TWRP recovery 2.6.3.3, most custom rom's require that recovery, it should also mention that in the original thread of the rom you flashed.
I will need your fastboot getvar all output in order to know what your stock rom is.
Click to expand...
Click to collapse
I'm sorry I meant TWRP. Got them confused. But i have installed TWRP.
Giagi said:
I'm sorry I meant TWRP. Got them confused. But i have installed TWRP.
Click to expand...
Click to collapse
You have developer edition on your phone ? 5.11.1540.9
did you put that on there yourself ?
Your CID-HTC__E11 states you should have WWE 401.
Just to confirm, could you tell me what it says in you bootloader beside os- ??????????
Seanie280672 said:
You have developer edition on your phone ? did you put that on there yourself ?
Just to confirm, could you tell me what it says in you bootloader besides os- ??????????
Click to expand...
Click to collapse
I did not put developer edition on my phone knowingly.
OS-5.11.1540.9
It used to be something else 5.11.401.10 i believe.
Giagi said:
I did not put developer edition on my phone knowingly.
OS-5.11.1540.9
It used to be something else 5.11.401.10 i believe.
Click to expand...
Click to collapse
yup 401 is your correct version for your CID, the strange thing is, you can only flash firmware if you are s-off, or if you had a lower firmware first.
this is your correct stock reset file, but I wouldn't flash it myself as your firmware doesn't match anymore: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
im sorry but I don't have any experience with dev edition firmware and not sure which ruu's etc you can flash, maybe one of the other senior members can guide you from here.
But if I was to be up front with you, especially with you being s-on, I would say you were stuck with custom rom's only now, as you cant back flash or flash the correct firmware without s-off.
Seanie280672 said:
yup 401 is your correct version for your CID, the strange thing is, you can only flash firmware if you are s-off, or if you had a lower firmware first.
this is your correct stock reset file, but I wouldn't flash it myself as your firmware doesn't match anymore: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Stock ROM version for these types:
modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
im sorry but I don't have any experience with dev edition firmware and not sure which ruu's etc you can flash, maybe one of the other senior members can guide you from here.
But if I was to be up front with you, especially with you being s-on, I would say you were stuck with custom rom's only now, as you cant back flash or flash the correct firmware without s-off.
Click to expand...
Click to collapse
And this one?: http://forum.xda-developers.com/showthread.php?t=2183023
I believe it's a custom ROM but i've not been able to get it to work.
Do you know of a way to revert back to the original OS? (preferable with S-On)
Giagi said:
And this one?: http://forum.xda-developers.com/showthread.php?t=2183023
I believe it's a custom ROM but i've not been able to get it to work.
Do you know of a way to revert back to the original OS? (preferable with S-On)
Click to expand...
Click to collapse
try fastboot erase cache and then try flash this one: http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
again make sure its with twrp 2.6.3.3
Seanie280672 said:
try fastboot erase cache and then try flash this one: http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
again make sure its with twrp 2.6.3.3
Click to expand...
Click to collapse
WOW, Thank you sooo much!!!
I'm running the ROM you sent and my htc backup is restoring my phone to it's original state.
I am so happy right now. I really appreciate your help.
I've donated you some money, it's not much and i'm sorry for that, but it's all i have on my paypal account currently.
Again, many thanks.
Giagi said:
WOW, Thank you sooo much!!!
I'm running the ROM you sent and my htc backup is restoring my phone to it's original state.
I am so happy right now. I really appreciate your help.
I've donated you some money, it's not much and i'm sorry for that, but it's all i have on my paypal account currently.
Again, many thanks.
Click to expand...
Click to collapse
Ive refunded it back to you, I don't expect donations for helping people out, I don't know where that button came from below my user name and don't know how to get rid of it.
Hit the thanks button is perfectly enough.
Seanie280672 said:
Ive refunded it back to you, I don't expect donations for helping people out, I don't know where that button came from below my user name and don't know how to get rid of it.
Hit the thanks button is perfectly enough.
Click to expand...
Click to collapse
Sorry, to bother you again, but it seems as if my problem is not completely resolved.
Every time i shut down my phone it goes into a bootloop, where it boots up, stay on for about 2 mins where it just works as normal, and then shuts down again. After which it reboots again and so on.
The first time this happened i did a factory reset and this seemed to work. But after i shut down my phone for a second time the problem appeared again. And i really don't want to reset it again.
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots
consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe