Database Develop

[Q] I need help about turning back to the default ROM.

Hi everybody!
My IS has been unlocked from htcdev.com and currently uses Jelly Bean ROM form Nik. So unhappy that there's a problems with my camera and I need to maintain it, just bought it 10 days ago. So I wanna back to the origin ROM. I have read many topics but there's no topic about it in this HTC IS tab. I have known that:
+ Download the ROM ( RUU of something like that, I know what it really is) has radio the same with the one appears in the boot-launcher mode.
+ Flash ROM by using .exe may brock the phone .
+ We must use another way. And I don't know how to do this. Just like we must unrar the .exe, use .img and re-lock the phone or un-root.
Anybody who knows clearly about this problems pls give me some advice.
Thanks for advance. :fingers-crossed:
I'm so sorry if this is about spamming but I'm now so stressful (.

why dont you install Nik's Project X v4.1? that is a good ICS sense 4 rom. Camera and video and everything else works properly in that ROM.

abc_8989 said:
Hi everybody!
My IS has been unlocked from htcdev.com and currently uses Jelly Bean ROM form Nik. So unhappy that there's a problems with my camera and I need to maintain it, just bought it 10 days ago. So I wanna back to the origin ROM. I have read many topics but there's no topic about it in this HTC IS tab. I have known that:
+ Download the ROM ( RUU of something like that, I know what it really is) has radio the same with the one appears in the boot-launcher mode.
+ Flash ROM by using .exe may brock the phone .
+ We must use another way. And I don't know how to do this. Just like we must unrar the .exe, use .img and re-lock the phone or un-root.
Anybody who knows clearly about this problems pls give me some advice.
Thanks for advance. :fingers-crossed:
I'm so sorry if this is about spamming but I'm now so stressful (.
Click to expand...
Click to collapse
You simply need to locate the RUU that matches the one you had when you unlocked your phone at HTCDEV.com.
Then relock the bootloader and run the RUU and you should be good to go.
If you put the phone in FASTBOOT USB mode and then enter and post the results of this command:
fastboot getvar all
we can help you identify the RUU you should use.

I'm Asian and here my radio : 3831.18.00.11_M. There are 2 files in the filefactory folder, the follow link RUU out there. I downloaded WWE one.
SO I must put the .exe file into the folder which I created for unlocking phone?

tpbklake said:
You simply need to locate the RUU that matches the one you had when you unlocked your phone at HTCDEV.com.
Then relock the bootloader and run the RUU and you should be good to go.
If you put the phone in FASTBOOT USB mode and then enter and post the results of this command:
fastboot getvar all
we can help you identify the RUU you should use.
Click to expand...
Click to collapse
Sry to interrupt.
Please tell me which RUU do I need ?
Mine is as follow.
version: 0.5
version-bootloader: 2.02.0002
version-baseband: 3831.18.00.11_M
version-cpld: None
version-microp: None
version-main: 2.32.1010.1
serialno: HT18KTD01750
imei: 358000042821874
product: vivo
platform: HBOOT-7630
modelid: PG3213000
cidnum: HTC__A07
battery-status: good
battery-voltage: 4132mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d41e50e7
hbootpreupdate: 12
gencheckpt: 0
thank u.

OMG... I don't know how to collect all of this info. I unlocked phone at Fastboot, the same hbooy with you. But what do u mean about which ROM I need? I think that one phone has olny one RUU. Sr for my english if it too meaning.

abc_8989 said:
I'm Asian and here my radio : 3831.18.00.11_M. There are 2 files in the filefactory folder, the follow link RUU out there. I downloaded WWE one.
SO I must put the .exe file into the folder which I created for unlocking phone?
Click to expand...
Click to collapse
No, you can now execute this file from any directory. It is a program that will guide you through the process of flashing this ROM.

Sorry dude. Why don't you simply flash We Want ICS by Nik?
It will be as having a rooted phone with the stock rom, ICS/Sense 3.6.
It's the simplest manner and the ROM wont let you disapponted...
Sent from my Incredible S using xda app-developers app

But I want to come back to the default ROM because my camera has been broken and I need to maintain it at HTC. They will not maintain it if it is a rooted and unlocked phone.

When you say your camera is broken do you mean physical damage?
If your camera isn't working on the current JB ROM, thats a knows issue.
Even I would suggest flashing Nik's We Want ICS. It is like an optimised version of the stock. Most chances are that your camera should work. Flashing it should be easy-peasy. If your camera still doesn't work we could help you revert to Stock.

My advise is to flash a rom that has working camera drivers such as Project x4.1.
If the camera still not works properly lock your phone and install the RUU you need.

Yes, Its a physical damage. And I need to maintain it at HTC service. That's why I need to go back to the default ROM.

tpbklake said:
You simply need to locate the RUU that matches the one you had when you unlocked your phone at HTCDEV.com.
Then relock the bootloader and run the RUU and you should be good to go.
If you put the phone in FASTBOOT USB mode and then enter and post the results of this command:
fastboot getvar all
we can help you identify the RUU you should use.
Click to expand...
Click to collapse
abc_8989 said:
Yes, Its a physical damage. And I need to maintain it at HTC service. That's why I need to go back to the default ROM.
Click to expand...
Click to collapse
So you never did respond with this information to help you pick the correct RUU. Must have gotten lost in all of the 'why not flash a custom ROM' posts, huh?

abc_8989 said:
Yes, Its a physical damage. And I need to maintain it at HTC service. That's why I need to go back to the default ROM.
Click to expand...
Click to collapse
Sorry to say you but when you give ur phone to HTC guy they will know that your warranty is void because even if you flash ruu and lock ur bootloader again u will see the the status "RELOCKED" instead of "LOCK" in hboot mode.
Sent from my HTC Incredible S using xda premium

OMG, so soooooo sad about that (. Thank all you guys for helping me, but there's still a way for me to install ROMfor mr to sell the phone for the "comfortable" price?

bhaumik555 said:
Sorry to say you but when you give ur phone to HTC guy they will know that your warranty is void because even if you flash ruu and lock ur bootloader again u will see the the status "RELOCKED" instead of "LOCK" in hboot mode.
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
That's not always true. Unless you take it to them with a software issue they generally dont bother with checking hboot and stuff.
I got my Incredible S repaired (it had a malfunctioning earpiece) even if my hboot said Relocked.

Hi! i did the fastboot getvar all, anyone can help me, what RUU do i need?
(i wast stock rom too)
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.
(bootloader) version-baseband: 3831.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: HT12VTD11274
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

szuladam said:
Hi! i did the fastboot getvar all, anyone can help me, what RUU do i need?
(i wast stock rom too)
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.
(bootloader) version-baseband: 3831.18
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: HT12VTD11274
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Never show your IMEI number while posting info about your phone.:angel:

abc_8989 said:
Hi everybody!
My IS has been unlocked from htcdev.com and currently uses Jelly Bean ROM form Nik. So unhappy that there's a problems with my camera and I need to maintain it, just bought it 10 days ago. So I wanna back to the origin ROM. I have read many topics but there's no topic about it in this HTC IS tab. I have known that:
+ Download the ROM ( RUU of something like that, I know what it really is) has radio the same with the one appears in the boot-launcher mode.
+ Flash ROM by using .exe may brock the phone .
+ We must use another way. And I don't know how to do this. Just like we must unrar the .exe, use .img and re-lock the phone or un-root.
Anybody who knows clearly about this problems pls give me some advice.
Thanks for advance. :fingers-crossed:
I'm so sorry if this is about spamming but I'm now so stressful (.
Click to expand...
Click to collapse
Hi. I'm an Asian user. So what seems to be the problem?
I'm quite confused here, so help me out. From what I understand here, your camera is broken after flashing Jelly Bean ROM. May I know, what kind of damage are you facing? Is it the camera software or the physical itself?
If it is the camera software problem, I supposed your device is not S-OFF yet, therefore some features may not be available for S-ON user.
If so, I suggest you to get your device S-OFF first and try re-flashing the ROM. You can find the tutorial inside this forum on how to get our device S-OFF.
But if you don't want to get your device S-OFF, I suggest you to flash the .img file inside the Jelly Bean ROM file using fastboot command.
But if it is the physical damage, I suggest you to flash this RUU in fastboot, you can google it since I forgot where I downloaded it before:
RUU_VIVO_ICS_35_S_hTC_Asia_WWE_4.10.707.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266513_signed.exe
Hope this helps.

I think you just flash ARHD 4.0 mate,it's base on stock ROM with alot of enhanced feature. Almost everything work,even Wifi Hotspot. After a long long way with every ROM for IS,i always return to ARHD
Sent from my HTC Incredible S

Looking to go back to stock ROM

Hello,
i purchased a HTC One 1 year ago and installed the CyanogenMod on it and i did forget to backup my stock ROM, i was looking around the forums for the stock ROM to install back on the phone because i'm having issues with the CyanogenMod installed right now.
I do have a HTC One (m7ul) with CyanogenMod version 11-20140104-SNAPSHOT-M2-m7ul on it, my original carrier was SFR (Vodafone-France).
I did have find this link: http://forum.xda-developers.com/showthread.php?t=2428276 who sent me to this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-163-2-zip/ i'm not sure if it is the "stock rom" for the phone and if it is, how to do the things to go back to stock?
May i have some help please?
Thanks and sorry for my bad english.

Yeeshak said:
Hello,
i purchased a HTC One 1 year ago and installed the CyanogenMod on it and i did forget to backup my stock ROM, i was looking around the forums for the stock ROM to install back on the phone because i'm having issues with the CyanogenMod installed right now.
I do have a HTC One (m7ul) with CyanogenMod version 11-20140104-SNAPSHOT-M2-m7ul on it, my original carrier was SFR (Vodafone-France).
I did have find this link: http://forum.xda-developers.com/showthread.php?t=2428276 who sent me to this: http://www.htc1guru.com/dld/guru_reset_m7_2-24-163-2-zip/ i'm not sure if it is the "stock rom" for the phone and if it is, how to do the things to go back to stock?
May i have some help please?
Thanks and sorry for my bad english.
Click to expand...
Click to collapse
please post a "fastboot getvar all" (excluding IMEI and s/n)
PS: why would you want to go back to stock anyway? custom ROM = :victory:

nkk71 said:
please post a "fastboot getvar all" (excluding IMEI and s/n)
PS: why would you want to go back to stock anyway? custom ROM = :victory:
Click to expand...
Click to collapse
C:\androidsdk\sdk-tools>fastboot getvar all
< waiting for device >
(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.163.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
I do want to go back to stock rom because of having a lot of issues with CyanogenMod right now and i don't know any other good rom, and probably to resell the phone in the futur

Yeeshak said:
C:\androidsdk\sdk-tools>fastboot getvar all
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.63.163.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP203
I do want to go back to stock rom because of having a lot of issues with CyanogenMod right now and i don't know any other good rom, and probably to resell the phone in the futur
Click to expand...
Click to collapse
Here's a great index thread of ROMs, guides, etc: http://forum.xda-developers.com/showthread.php?t=2438026 (credits to @ClydeB1)
I'm personally using ARHD 51.0 (credits to @mike1986.), running super smooth; but that's a personal choice, try out some of the ROMs available to see what you like, they're all excellent.
If you want to go back to 100% stock, you're going to need to S-Off, and you can check my guide (in my signature) on how to do it.
But if you're keeping the phone for now, just use one of the ROMs in the index thread. (in my opinion)

nkk71 said:
If you want to go back to 100% stock, you're going to need to S-Off, and you can check my guide (in my signature) on how to do it.
Click to expand...
Click to collapse
I think i do want to go 100% stock for now, do your guide helps to do it or only to go s-off?
I'm a little lost after reading your guide, i'm pretty new to this world of android and i can't find where to go usb debug and adb commands won't work

Yeeshak said:
I think i do want to go 100% stock for now, do your guide helps to do it or only to go s-off?
Click to expand...
Click to collapse
to be able to go back to 100% stock, you need to downgrade -> to downgrade you need S-Off
maybe best for you (at least, at the moment), is to just install the stock rom you mentioned ( http://www.htc1guru.com/dld/guru_reset_m7_2-24-163-2-zip/ )
my guide ( http://forum.xda-developers.com/showthread.php?t=2541082 ) is about returning to stock, not about S-Off, but you can't use it until you get S-Off.
I personally would give ARHD http://forum.xda-developers.com/showthread.php?t=2183023 (maybe 31.6 if you don't want to TRY the latest) a try.

nkk71 said:
to be able to go back to 100% stock, you need to downgrade -> to downgrade you need S-Off
maybe best for you (at least, at the moment), is to just install the stock rom you mentioned ( http://www.htc1guru.com/dld/guru_reset_m7_2-24-163-2-zip/ )
my guide ( http://forum.xda-developers.com/showthread.php?t=2541082 ) is about returning to stock, not about S-Off, but you can't use it until you get S-Off.
I personally would give ARHD http://forum.xda-developers.com/showthread.php?t=2183023 (maybe 31.6 if you don't want to TRY the latest) a try.
Click to expand...
Click to collapse
Is there a way to talk with you directly on IRC or something for furter advice/help?

Yeeshak said:
Is there a way to talk with you directly on IRC or something for furter advice/help?
Click to expand...
Click to collapse
actually, i'm about to shut down. peut etre demain....

nkk71 said:
actually, i'm about to shut down. peut etre demain....
Click to expand...
Click to collapse
It's ok, i'll give you my mail on a private message and we'll talk when you have time if it's ok? Thank you so much for your time Bonne nuit !

Yeeshak said:
It's ok, i'll give you my mail on a private message and we'll talk when you have time if it's ok? Thank you so much for your time Bonne nuit !
Click to expand...
Click to collapse
Merci, et a toi
Sent from my HTC One using Tapatalk

Problem
I have a serious problem. I tried to install the Cm. First i tried with the install app. Then i tried to flash it and the problem came. The tutorial said that wipe 1. system 2. cache 3. dalvik. I wiped all of them and tried to flash cm but it faile. It said "error executing updater binary in zip ' /sdcard
Error flashing zip ' /sdcard/cm-10.2.1-m7ul.zip". I have a nandroid backup but it's made with cwm and now when i have no OS what to do ? Please help

Update recovery
sent from my mobile device

Why does my phone bootloop when I install a kernel?

I'm S-Off, running a rooted version of 4.4.3 with Sense 6.0. For whatever reason, I can't get kernels to work for me. I've tried ElementalX (specifically the Verizon version) as well as teaMSeven, and they both make my phone bootloop on the HTC Logo screen. Why is it doing this? Like I said, I'm S-off and rooted. I'm installing kernels that are listed as supporting my ROM. (stock, rooted 4.4.3) What the heck is the problem?
I have a Nandroid backup, so recovering my device isn't an issue. I'm just really aggravated that I'm not able to flash a different kernel.

DrFeelgood246 said:
I'm S-Off, running a rooted version of 4.4.3 with Sense 6.0. For whatever reason, I can't get kernels to work for me. I've tried ElementalX (specifically the Verizon version) as well as teaMSeven, and they both make my phone bootloop on the HTC Logo screen. Why is it doing this? Like I said, I'm S-off and rooted. I'm installing kernels that are listed as supporting my ROM. (stock, rooted 4.4.3) What the heck is the problem?
I have a Nandroid backup, so recovering my device isn't an issue. I'm just really aggravated that I'm not able to flash a different kernel.
Click to expand...
Click to collapse
So its safe to assume your phone is Verizon but Can you please post a getvar all.
As far as I can see the Verizon Elemental x Kernel only supports 4.4.2 Sense 5.5 so that's probably your issue. Can you provide a link to the Kernel your trying to flash.
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
So its safe to assume your phone is Verizon but Can you please post a getvar all.
As far as I can see the Verizon Elemental x Kernel only supports 4.4.2 Sense 5.5 so that's probably your issue. Can you provide a link to the Kernel your trying to flash.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Okay, I think you're right about Elementalx. However, the teaMSeven Kernel says it works with Sense 6/Android 4.4.3, so I'm really confused about that one. How do I obtain my phone's getvar?

DrFeelgood246 said:
Okay, I think you're right about Elementalx. However, the teaMSeven Kernel says it works with Sense 6/Android 4.4.3, so I'm really confused about that one. How do I obtain my phone's getvar?
Click to expand...
Click to collapse
reboot in bootloader/fastboot mode:
Code:
fastboot getvar all

DrFeelgood246 said:
Okay, I think you're right about Elementalx. However, the teaMSeven Kernel says it works with Sense 6/Android 4.4.3, so I'm really confused about that one. How do I obtain my phone's getvar?
Click to expand...
Click to collapse
Connect fastboot usb in the bootloader. And in the fastboot command window type
Code:
fastboot getvar all
Although looking at the teamseven thread that kernel is for GSM phones.
Verizon use CDMA so it probably not compatible with your device. Unless I missed it in there I haven't read the entire thread. :good:
Edit:- using the search box in the teamseven thread turned up this
[quote name="nprez" post=51673515]Hello, and thank you for all the great work. I'm on verizon, running Stock 4.4.2, 3.11.605.1, sense 5.5, rooted, S-OFF. I flashed the appropriate version of the kernel and ended up in a boot loop, tried clearing cache and dalvik several times, and also reflashed the recovery with no joy. I checked the MD5, and download is all good. Restored my backup of the stock kernel and all good. Any tips? I'd really love to use this kernel. Thanks[/QUOTE]
This is for the international m7, it will not work with Verizon.
Click to expand...
Click to collapse
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
Connect fastboot usb in the bootloader. And in the fastboot command window type
Code:
fastboot getvar all
Although looking at the teamseven thread that kernel is for GSM phones.
Verizon use CDMA so it probably not compatible with your device. Unless I missed it in there I haven't read the entire thread. :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Dammit. Maybe it's just bad luck that I managed to miss important information twice. I'll have to try a kernel that 100% certainly supports my ROM and device. (although the teamseven post showed up in the Verizon HTC One section of the forum)
Although I did produce a getvar.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3AGS908421
(bootloader) imei: 990004282576317
(bootloader) meid: 99000428257631
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

[Q] Allllrighty then - no touchscreen after firmware flash

So it's been a good few days with my M7 given to me by a friend. I am totally new at the whole custom ROM thing but had no problems with root, unlock, s-off, etc. but took me many hours as I've rarely used Cmd functions. Still have stock 4.1.2 sense 5.0. Time to move forward so ..... downloaded TWRP and ROM Installer, etc. Decided to update firmware next as some ROMs need later and lost touchscreen function. No other issues, boots fine into whatever and recovers into TWERP with full function of touchscreen. Should I flash older firmware or can I loaded newer ROM through TWERP to get back in the game ? need to answer calls and texts at some point soon !

biggerdog said:
So it's been a good few days with my M7 given to me by a friend. I am totally new at the whole custom ROM thing but had no problems with root, unlock, s-off, etc. but took me many hours as I've rarely used Cmd functions. Still have stock 4.1.2 sense 5.0. Time to move forward so ..... downloaded TWRP and ROM Installer, etc. Decided to update firmware next as some ROMs need later and lost touchscreen function. No other issues, boots fine into whatever and recovers into TWERP with full function of touchscreen. Should I flash older firmware or can I loaded newer ROM through TWERP to get back in the game ? need to answer calls and texts at some point soon !
Click to expand...
Click to collapse
If you have Stock 4.1.2 rom and the latest firmware that's almost certainly your problem. But rather than flashing older firmware why not flash a newer rom ?

Danny201281 said:
If you have Stock 4.1.2 rom and the latest firmware that's almost certainly your problem. But rather than flashing older firmware why not flash a newer rom ?
Click to expand...
Click to collapse
Exactly what I was intending to do anyway which was reason for firmware upgrade (guess I put the cart before the horse 1) , can I do this through TWRP ? Do I download said ROM on my laptop and copy to directory on phone then load through TWRP ? Thanks for your help. As i stated , this is all new territory to me ....... any guidance appreciated (or links to assist) thanks.

biggerdog said:
Exactly what I was intending to do anyway which was reason for firmware upgrade (guess I put the cart before the horse 1) , can I do this through TWRP ? Do I download said ROM on my laptop and copy to directory on phone then load through TWRP ? Thanks for your help. As i stated , this is all new territory to me ....... any guidance appreciated (or links to assist) thanks.
Click to expand...
Click to collapse
Can you post the out put of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
What sort of rom are you looking for Stock or Custom?

Danny201281 said:
Can you post the out put of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
What sort of rom are you looking for Stock or Custom?
Click to expand...
Click to collapse
give me few minutes , I have not decided on a rom , just wasn't getting OTA updates from ATT so figured I'd take matters into my own hands ! Kinda wanted sense 6 , other than that , open to suggestions .........

Here we go :
(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:
(bootloader) imei:
(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: 4218mV
(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
all: Done!
finished. total time: 0.068s

biggerdog said:
Here we go :
(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:
(bootloader) imei:
(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: 4218mV
(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
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
Ok start with this http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_84.0.zip
Android Kitkat 4.4.3 Sense 6
Download the rom and put the file in your fastboot folder on your PC and rename it rom.zip. Boot to TWRP recovery (2.6.3.3 Recommended) and connect your usb cable. Check adb is working with
Code:
adb devices
If you get the expected out put
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete. Factory reset and install the rom from TWRP

Gotta ask a quick question , just curious. I cannot download the rom onto PC then drag to folder on the phone then install through TWRP ? Not questioning method and advice given , just thinking as I have no experience and seems like it would do the same, but I wouldn't know ! I will proceed through command prompt as recommended for now .....

biggerdog said:
Gotta ask a quick question , just curious. I cannot download the rom onto PC then drag to folder on the phone then install through TWRP ? Not questioning method and advice given , just thinking as I have no experience and seems like it would do the same, but I wouldn't know ! I will proceed through command prompt as recommended for now .....
Click to expand...
Click to collapse
Yes with TWRP 2.8.4.0 you can just copy the file to the phone in windows .. no need to push as TWRP supports MTP now

clsA said:
Yes with TWRP 2.8.4.0 you can just copy the file to the phone in windows .. no need to push as TWRP supports MTP now
Click to expand...
Click to collapse
Awesome. As stated, all was well until flashing firmware 6.06.401.1 which may have been too big of a jump for my stock 4.1.2. The flash showed successful and went fine but I've read elsewhere that I should have been "relocked" before flashing , then unlocked after ? I am not seeing this step on all instructions ( I followed this : http://forum.xda-developers.com/showthread.php?t=2485651 ) Also didn't verify model ID (PN0712000) , may need to find a different firmware and re-flash ? Never got errors , just lost touch screen (which sounds common). Thanks all , hittin' the sack as this download from Android Rev is taking forever (need a torrent) ! Goodnight and thanks for feedback to come (something to look forward to in the AM).

biggerdog said:
Awesome. As stated, all was well until flashing firmware 6.06.401.1 which may have been too big of a jump for my stock 4.1.2. The flash showed successful and went fine but I've read elsewhere that I should have been "relocked" before flashing , then unlocked after ? I am not seeing this step on all instructions ( I followed this : http://forum.xda-developers.com/showthread.php?t=2485651 ) Also didn't verify model ID (PN0712000) , may need to find a different firmware and re-flash ? Never got errors , just lost touch screen (which sounds common). Thanks all , hittin' the sack as this download from Android Rev is taking forever (need a torrent) ! Goodnight and thanks for feedback to come (something to look forward to in the AM).
Click to expand...
Click to collapse
Well you could always change your CiD to Dev Edition and flash the Dev Edition firmware. And no you do not need to relock your bootloader to flash firmware, That is only for S-on users. Your phone is s-off :good:
The problem with the touch screen will be the big gap between firmware and rom. think of it like using Window 8 with Windows 95 Drivers

Danny201281 said:
Well you could always change your CiD to Dev Edition and flash the Dev Edition firmware. And no you do not need to relock your bootloader to flash firmware, That is only for S-on users. Your phone is s-off :good:
The problem with the touch screen will be the big gap between firmware and rom. think of it like using Window 8 with Windows 95 Drivers
Click to expand...
Click to collapse
Would you have a "how to" link on the steps to do this that you trust ? I'm sure I could search as well but want to proceed correctly as I'm about there !

biggerdog said:
Would you have a "how to" link on the steps to do this that you trust ? I'm sure I could search as well but want to proceed correctly as I'm about there !
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11

clsA said:
look here
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Thanks all - everything up and running. Didn't go developer but may consider if there are any real advantages (I would assume only if running stock, correct ?) Not sure when they'll be releasing Lollipop for this M7 but supposedly soon

RUU is not working for my M7.

I have an AT&T M7 flashed with Cyanogenmod 10 that I would like to restock. I've tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2, but that is not working.
I mean it starts to run and then after asking for aproval it desapears.
I also tried the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2, and this one runs but at the end it says that is not compatible with my phones firmware.
This is the phone info:
M7_UL PVT SHIP S-OFF RH
CID-CWS_001HBOOT-1. 56. 0000
RADIO-4T. 24. 3218. 09
OpenDSP-v32. 120. 274. 0909
OS-4. 18. 502. 7
eMMC-boot 2048MB
Jan 28 2014, 09: 32: 41. 0
What is the simpliest way to go back to stock?
Thanks in advance.
Getvar:
fastboot getvar all
(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: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(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: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s

chiquito3 said:
I have an AT&T M7 flashed with Cyanogenmod 10 that I would like to restock. I've tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2, but that is not working.
I mean it starts to run and then after asking for aproval it desapears.
I also tried the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2, and this one runs but at the end it says that is not compatible with my phones firmware.
This is the phone info:
M7_UL PVT SHIP S-OFF RH
CID-CWS_001HBOOT-1. 56. 0000
RADIO-4T. 24. 3218. 09
OpenDSP-v32. 120. 274. 0909
OS-4. 18. 502. 7
eMMC-boot 2048MB
Jan 28 2014, 09: 32: 41. 0
What is the simpliest way to go back to stock?
Thanks in advance.
Getvar:
fastboot getvar all
(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: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(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: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Click to expand...
Click to collapse
you need to downgrade your hboot to 1.44 to flash 1.26.502.12

alray said:
you need to downgrade your hboot to 1.44 to flash 1.26.502.12
Click to expand...
Click to collapse
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.

chiquito3 said:
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
Click to expand...
Click to collapse
use the 1.44 hboot from the .401 version.

chiquito3 said:
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
Click to expand...
Click to collapse
Did you check the md5 of the 4.15.502.7 ruu you downloaded?
Also if you have HTCsync installed then uninstall it. Doesn't do any favours when using ruu's :good:

I've downloaded the file from 2 different sources and the resilt is the same.
Sent from my SM-G900T using Tapatalk

chiquito3 said:
I've downloaded the file from 2 different sources and the resilt is the same.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Is the RUU quiting after you accept the license agreement , if so, its a windows error not an RUU error, read and do the fix below:
http://forums.androidcentral.com/htc-evo-4g-lte/363796-can-t-install-4-3-ruu-windows-7-8-1-a.html
post 18 fixed the problem for me, you need to download and install all one at a time with a reboot in-between each one, do not use windows update to update any of them.

Seanie280672 said:
Is the RUU quiting after you accept the license agreement , if so, its a windows error not an RUU error, read and do the fix below:
http://forums.androidcentral.com/htc-evo-4g-lte/363796-can-t-install-4-3-ruu-windows-7-8-1-a.html
post 18 fixed the problem for me, you need to download and install all one at a time with a reboot in-between each one, do not use windows update to update any of them.
Click to expand...
Click to collapse
Seems that you are right. I tried all the suggestions here but none of them worked on my PC. So Idecided to try on my laptop. The thing is that the RUU did run well but unfotunately it ends with an error 170 usb connection error.
The laptop recognizes the phone well so I cant understand the reason for the error.

chiquito3 said:
Seems that you are right. I tried all the suggestions here but none of them worked on my PC. So Idecided to try on my laptop. The thing is that the RUU did run well but unfotunately it ends with an error 170 usb connection error.
The laptop recognizes the phone well so I cant understand the reason for the error.
Click to expand...
Click to collapse
make sure the computer recognises the phone whilst the phone is both booted and in the bootloader with fastbootUSB showing on the phone screen.

Seanie280672 said:
make sure the computer recognises the phone whilst the phone is both booted and in the bootloader with fastbootUSB showing on the phone screen.
Click to expand...
Click to collapse
Ok guys I did it thanks to your help.
Now what is the prefered rooting method and should I take the OTA or not?

chiquito3 said:
Ok guys I did it thanks to your help.
Now what is the prefered rooting method and should I take the OTA or not?
Click to expand...
Click to collapse
yes take the OTA's, if you dont like the new Lollipop you can always just flash the RUU again to get back to the older versions as your s-off.
after you've done the OTA's, to root, just flash twrp recovery: http://dl.twrp.me/m7/twrp-2.8.5.0-m7.img and then flash the superSU zip from within TWRP recovery: http://download.chainfire.eu/696/SuperSU, complete root setup once the phone has started back up by opening superSU from your app drawer.

Seanie280672 said:
yes take the OTA's, if you dont like the new Lollipop you can always just flash the RUU again to get back to the older versions as your s-off.
after you've done the OTA's, to root, just flash twrp recovery: http://dl.twrp.me/m7/twrp-2.8.5.0-m7.img and then flash the superSU zip from within TWRP recovery: http://download.chainfire.eu/696/SuperSU, complete root setup once the phone has started back up by opening superSU from your app drawer.
Click to expand...
Click to collapse
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.

chiquito3 said:
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
Click to expand...
Click to collapse
There is no lollipop for at&t yet, should be released soon
http://www.htc.com/us/go/htc-software-updates/#device-content

chiquito3 said:
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
Click to expand...
Click to collapse
alray said:
There is no lollipop for at&t yet, should be released soon
http://www.htc.com/us/go/htc-software-updates/#device-content
Click to expand...
Click to collapse
Yes during the Uh Oh announcement / interview they said they were shooting for an April 1'st update for AT&T M7

clsA said:
Yes during the Uh Oh announcement / interview they said they were shooting for an April 1'st update for AT&T M7
Click to expand...
Click to collapse
And I'm longing for that moment! Thanks again.
Since I did change the stock recovery to TWRP just for rooting the phone, could I still take the OTA upgrade or does it have to be done manually?
I also installed Xposed Framework and some HTC Modules.

chiquito3 said:
And I'm longing for that moment! Thanks again.
Since I did change the stock recovery to TWRP just for rooting the phone, could I still take the OTA upgrade or does it have to be done manually?
I also installed Xposed Framework and some HTC Modules.
Click to expand...
Click to collapse
you will have to return the phone to full stock to take an OTA update

clsA said:
you will have to return the phone to full stock to take an OTA update
Click to expand...
Click to collapse
I did something bad to the phone and would like to go back to stock can I use the RUU again and how? Because I tried and it gives a fastboot error a few seconds after starting. The RUU is actually a downgrade.
I was trying to mod the Weather widget to transparent and I ended without the widget and the phone goes to black and takes too long to come back to light the screen.
the error is htc.fastboot.exe has stopped working

chiquito3 said:
I did something bad to the phone and would like to go back to stock can I use the RUU again and how? Because I tried and it gives a fastboot error a few seconds after starting. The RUU is actually a downgrade.
I was trying to mod the Weather widget to transparent and I ended without the widget and the phone goes to black and takes too long to come back to light the screen.
the error is htc.fastboot.exe has stopped working
Click to expand...
Click to collapse
you can use my Guru_Reset to return to stock 5.x
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
If you want to keep custom recovery choose no to stock recovery during install and yes to Root

clsA said:
you can use my Guru_Reset to return to stock 5.x
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
If you want to keep custom recovery choose no to stock recovery during install and yes to Root
Click to expand...
Click to collapse
Thanks again for your reply!
How do I flash this one? can it be done through costum recovery?

chiquito3 said:
Thanks again for your reply!
How do I flash this one? can it be done through costum recovery?
Click to expand...
Click to collapse
Yes you flash it in TWRP same as a rom