Database Develop

[Q] Help with going back to stock Ruu

I am going to have to send my HTC one M7 back for service, (seems to be always dropping the connection when i am talking..
so my stock rom that the tel. came with is: 4A.14.3250.13 ( see below)
My problem is that I can not find the RUU for this > 1.29.401.13 if I understand going back to stock correctly I will have to have this same rom to install the RUU.. is this true?
if so , can someone send me a link to the actual file I can not fine it anywhere, and when i try to install RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4.exe
it will not install the RUU. as it is not the same as the tel came with..
can anyone help me so that I can use a stock RUU so i can get my tel. completely stock
Dont know if it makes any difference now.. but i have updated to 4.2.2 and also wiped my sd card as stated to do when going from 4.2.1 to 4.2.2
can anyone help me please?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-main: 1.29.401.13
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good

atm you can't flash any ruu.
Because you have 1.29.401.13 version main, and all ruu are 1.29.401.1 or 1.29.401.7

mojolive said:
I am going to have to send my HTC one M7 back for service, (seems to be always dropping the connection when i am talking..
so my stock rom that the tel. came with is: 4A.14.3250.13 ( see below)
My problem is that I can not find the RUU for this > 1.29.401.13 if I understand going back to stock correctly I will have to have this same rom to install the RUU.. is this true?
if so , can someone send me a link to the actual file I can not fine it anywhere, and when i try to install RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4.exe
it will not install the RUU. as it is not the same as the tel came with..
can anyone help me so that I can use a stock RUU so i can get my tel. completely stock
Dont know if it makes any difference now.. but i have updated to 4.2.2 and also wiped my sd card as stated to do when going from 4.2.1 to 4.2.2
can anyone help me please?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-main: 1.29.401.13
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
Click to expand...
Click to collapse
Download the stock ROM from mike1986 and follow his return to stock thread, you'll then be on 1.29.401.16 (unless he only has 2.17.401.1 available now). That's your only option unless someone has a Nandroid of 1.29.401.13

[Q] Firmware and S-OFF

I'm using an AT&T and I'm looking to get S-OFF but I'm having issues with it and failing after pouring 8 times. I've tried it several times with no success. Now I had a stock AT&T ONE, not a GPE, but I flashed a signed, 3.06.1700.10 firmware, which I'm now on. I'm stuck because I can't update my firmware and cannot get S-OFF.
I'd like to figure out how I can get S-OFF or update my firmware and try another version of rumrunner.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3XXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXXX
(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: 4243mV
(bootloader) partition-layout: Generic
(bootloader) security: on
Click to expand...
Click to collapse

Goatshaver said:
I'm using an AT&T and I'm looking to get S-OFF but I'm having issues with it and failing after pouring 8 times. I've tried it several times with no success. Now I had a stock AT&T ONE, not a GPE, but I flashed a signed, 3.06.1700.10 firmware, which I'm now on. I'm stuck because I can't update my firmware and cannot get S-OFF.
I'd like to figure out how I can get S-OFF or update my firmware and try another version of rumrunner.
Click to expand...
Click to collapse
Did you meet all the requirements in this page?
http://rumrunner.us/instructions/

Prash8429 said:
Did you meet all the requirements in this page?
http://rumrunner.us/instructions/
Click to expand...
Click to collapse
All but USB 2.0. I tried using this ROM first, 3.06.1700.10 - Stock HTC Google Play Edition v1.1, but I had problems with it failing on the ADB. So I flashed ARHD 4.1 GE ROM and didn't have any ADB issues but it would just go through the pours and tell me to try again.
Someone mentioned udating the firmware to 3.07.1700.10 but I can't do that as it doesn't appear to be a signed firmware.

I've achieved S-OFF.
I was on firmware 3.06.1700.10. Flashed ARHD 4.1 GE ROM and used the Rumrunner for firmware 3.07.1700.10 and had no problems at all. Worked the first time through.

[Q] Help with SIM unlock AT&T HTC One (paying for help)

Hello,
I recently got HTC One locked to AT&T network and bought code online but it didn't work. I also made sure SIM card was active and had positive amount, not locked by PIN or PUK, phone is not stolen or blacklisted. Did factory reset and tried again but no luck..
First I tried it on stock phone:
- Android 4.1.2,
- Baseband version 4A.14.3250.13_10.33.1150.01L,
- Build number 1.26.502.10 CL166754 release-keys
Then I followed this guide [Tutorial] Root, Unlock, Recovery and flashing a Custom ROM ... unlocked bootloader, flashed CWM recovery, installed stock rooted 1.26.502.15 Android 4.1.2. I did not install custom rom/kernel.
Tried unlocking with code but again, no luck.
After that I followed this guide [GUIDE] How to Return to 100% Stock ... I got S-Off with revone, restored using a RUU.exe, removed Tampered.
Atm this is info from bootloader:
Code:
(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: HT34NWxxxxxx
(bootloader) imei: 3544390xxxxxxxx
(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: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Do I have to relock bootloader and try applying the code again?
Please help me solve this problem. I'm willing to donate 20$, to whoever help me solve problem.
Should I try updating 4.4.2 zip OTA and then applying the code? Will that help anyhow?

Tswigly said:
Hello,
I recently got HTC One locked to AT&T network and bought code online but it didn't work. I also made sure SIM card was active and had positive amount, not locked by PIN or PUK, phone is not stolen or blacklisted. Did factory reset and tried again but no luck..
First I tried it on stock phone:
- Android 4.1.2,
- Baseband version 4A.14.3250.13_10.33.1150.01L,
- Build number 1.26.502.10 CL166754 release-keys
Then I followed this guide [Tutorial] Root, Unlock, Recovery and flashing a Custom ROM ... unlocked bootloader, flashed CWM recovery, installed stock rooted 1.26.502.15 Android 4.1.2. I did not install custom rom/kernel.
Tried unlocking with code but again, no luck.
After that I followed this guide [GUIDE] How to Return to 100% Stock ... I got S-Off with revone, restored using a RUU.exe, removed Tampered.
Atm this is info from bootloader:
Code:
(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: HT34NWxxxxxx
(bootloader) imei: 3544390xxxxxxxx
(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: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Do I have to relock bootloader and try applying the code again?
Please help me solve this problem. I'm willing to donate $$ to whoever help me solve problem.
Should I try updating 4.4.2 zip OTA and then applying the code? Will that help anyhow?
Click to expand...
Click to collapse
Why did you started a new thread? You already have one here with the exact same info...
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer. (Also refer to Rule 16)
Click to expand...
Click to collapse
Unfortunately I'm not familiar with the process of sim-unlocking, but i'm sure you'll receive help soon. You can bump your thread once a day if it get to far in the queu, no need to start additional ones.

alray said:
Why did you started a new thread? You already have one here with the exact same info...
Unfortunately I'm not familiar with the process of sim-unlocking, but i'm sure you'll receive help soon. You can bump your thread once a day if it get to far in the queu, no need to start additional ones.
Click to expand...
Click to collapse
Well I wanted to delete the first thread using the delete/button but it was too late until I realized I can't do that

[Q] Will Flashing RUU Over Sim Unlocked Sprint 510 Re-Enable The Lock? [A] No it wont

Hello,
I bought an Unlocked Sprint Desire 510 from eBay here in India. It works good with my CDMA Network Sim card but last night out of no where Hands Free Activation Popup started to show up. Also there's a new Update out for this model. So I was thinking of flashing the latest RUU.
But my concern is that will it re-lock the device for Sprint or I will still be able to use My Indian RUIM?
Extra Info :
Bootloader Menu shows :
Tampered, Unlocked and S-ON.
HBOOT-3.19.0.0000
RADIO-1.46.40.0721
There's also an option named SIM Lock. What is it for?
It will be very helpful if you can help me find the best solution.
Thanks in advance.

SArnab©® said:
Hello,
I bought an Unlocked Sprint Desire 510 from eBay here in India. It works good with my CDMA Network Sim card but last night out of no where Hands Free Activation Popup started to show up. Also there's a new Update out for this model. So I was thinking of flashing the latest RUU.
But my concern is that will it re-lock the device for Sprint or I will still be able to use My Indian RUIM?
Extra Info :
Bootloader Menu shows :
Tampered, Unlocked and S-ON.
HBOOT-3.19.0.0000
RADIO-1.46.40.0721
There's also an option named SIM Lock. What is it for?
It will be very helpful if you can help me find the best solution.
Thanks in advance.
Click to expand...
Click to collapse
I definitely wouldn't risk it. More than likely, with this phone, you'll be locked down again

My Experience
CSP III said:
I definitely wouldn't risk it. More than likely, with this phone, you'll be locked down again
Click to expand...
Click to collapse
Thanks for replying. I went against the odds and flashed the RUU risking to lock down the mobile.
But, you know what? It didn't get locked.
Instead it fixed few of the broken parts:
1. Selfie Camera is now detected by Camera Apps (Stock and Custom) and works too. It didn't worked out of the box(as stated by eBay.in seller).
2. Move to SD Card works now for apps that support it.
3. Better Battery Life than before.
So, All who bought this mobile from eBay India for Reliance CDMA network, go forward and flash latest stock RUU and enjoy Front Cam, Move to SD and better Battery.
But keep few things in mind:
1. You will have to flash Stock recovery first.
2. Than Re-lock the bootloader.
3. Flash the RUU.
4. Boot into Bootloader/Fastboot and unlock bootloader again.
5. Flash/Boot-into TWRP recovery and MOUNT /system.
6. Navigate to /system/apps/and rename HTCSetupWizard.apk to HTCSetupWizard.apk.bak and HTCSetupWizard.odex to HTCSetupWizard.odex.bak .
* The above step is needed to bypass Hands-Free-Activation and complete the boot process.
7. You may even root the ROM if you want to by flashing Super-SU-Vxx.zip .
Now you are good to go.
If you just booted to TWRP in step 5, you may now even Flash it if you like to. But that would stop you from Updating through OTA.
Also Note that when an OTA Update arrives after this before starting the update process, use any root explorer file manager app and rename the files to original state from step 6, and once OTA gets installed follow from Step 4 Again. If you had Flashed TWRP than you will need to re-flash Stock recovery before you can install OTA Update.

Hey does anyone know where I can find the RUU for my device.I have been searching for days.!
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
That's my phone's info. If anyone had any links I would really appreciate it

Sorry for the late response... haven't come here in awhile. This is what I have that may be of use to you; at least the radio version starts with 1.101.1372.19. Good luck!
https://mega.nz/#!aZxGXCqL!n91Un39iK2c1JUemAfrBYbItnaEHAYhcAIPOLwFPn-U https://mega.nz/#!bQx0nTjL!3W89qbflxnQhE8fr_QnJMBFAO3aCHKcdkegFtxQ6tuY https://mega.nz/#!aNZnkSJI!g5BMc3C4iyRabfOSPhOwR3jMM9cQ954NJJzGYUv3OOA https://mega.nz/#!SNQVBIqD!4Ltublqj77Kmpjvdp8WcNWEijrgfxMT7ZpPzFAVsAHs
Dopekyd said:
Hey does anyone know where I can find the RUU for my device.I have been searching for days.!
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA49GY405962
(bootloader) imei: 123456789231654
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
That's my phone's info. If anyone had any links I would really appreciate it
Click to expand...
Click to collapse

Old Firmware on My HTC One (M7) Would Love to Update Please Help

Hey gang,
I have a HTC One (M7) with very old firmware (Build: 5.11.401.10 CL334166) and running 4.4.2 using a custom ROM (ARHD 71.1). I want to update my firmware to the most current but am uncertain of the following items:
1. Can I update my firmware in one go (i.e. my current to latest) or do I have to flash each successive update?
2. All in handset or do I have to use ADB?
3. Can I do it without wiping data?
Thanks for any help anyone can provide.

satsubatsu347 said:
Hey gang,
I have a HTC One (M7) with very old firmware (Build: 5.11.401.10 CL334166) and running 4.4.2 using a custom ROM (ARHD 71.1). I want to update my firmware to the most current but am uncertain of the following items:
1. Can I update my firmware in one go (i.e. my current to latest) or do I have to flash each successive update?
2. All in handset or do I have to use ADB?
3. Can I do it without wiping data?
Thanks for any help anyone can provide.
Click to expand...
Click to collapse
You want to update the firmware only or you also want to update the software (rom stock/custom) at the same time?
Post the output of "fastboot getvar all" (remove imei/sn before posting)

alray said:
You want to update the firmware only or you also want to update the software (rom stock/custom) at the same time?
Post the output of "fastboot getvar all" (remove imei/sn before posting)
Click to expand...
Click to collapse
I'll be paying close attention to this thread, because I'm a knucklehead who NEVER updated his firmware since he got the phone from AT&T around the time of the Boston bombing, but has repeatedly flashed updated ROMs (currently on ARHD 31.5), and when I tried 93.0 this weekend, a number of issues came up, so I went back to 31.5, and figured I need to do the right thing and update my firmware before trying 93.0 again.
So, I've got the same question #1 (Can I update my firmware in one go (i.e. my current to latest) or do I have to flash each successive update?) as the OP, with the added bonus of not being sure what my current firmware is.
Here's my output:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(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: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))

pierceheart said:
I'll be paying close attention to this thread, because I'm a knucklehead who NEVER updated his firmware since he got the phone from AT&T around the time of the Boston bombing, but has repeatedly flashed updated ROMs (currently on ARHD 31.5), and when I tried 93.0 this weekend, a number of issues came up, so I went back to 31.5, and figured I need to do the right thing and update my firmware before trying 93.0 again.
So, I've got the same question #1 (Can I update my firmware in one go (i.e. my current to latest) or do I have to flash each successive update?) as the OP, with the added bonus of not being sure what my current firmware is.
Here's my output:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(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: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Bootloader 1.44 + the AT&T CID (CWS__001) suggest a 1.xx.502.x firmware. The best solution imo would be to achieve S-OFF so you can flash the 7.19.401.2 firmware and you'll be able to use recent custom roms.

alray said:
Bootloader 1.44 + the AT&T CID (CWS__001) suggest a 1.xx.502.x firmware. The best solution imo would be to achieve S-OFF so you can flash the 7.19.401.2 firmware and you'll be able to use recent custom roms.
Click to expand...
Click to collapse
Thanks - is it normal for (bootloader) version-main: to be blank?

pierceheart said:
Thanks - is it normal for (bootloader) version-main: to be blank?
Click to expand...
Click to collapse
Its not normal but its not really important. Its a bug caused by some old TWRP version (can't remember which one exactly) which erase the version number.