Database Develop

[GUIDE] Install any Gingerbread RUU on Canadian IS!

INTRODUCTION
As I promised in my last guide, I have played around with the RUUs in an attempt to bypass the "Model ID Incorrect" error, and have successfully installed the Optus 2.3.3 RUU on my Bell IS!
WHAT IS REQUIRED?
-a S-OFF'ed IS (doesn't need to be radio S-OFF'ed)
- That's it! A goldcard MAY also be required(it wasn't for me, but people are reporting they still get CID errors).
INSTRUCTIONS
Follow this guide until the 4th bullet under "How to install the Gingerbread update if you're S-OFF" but copy the rom.zip to your Desktop instead of your phone.
Extract rom.zip into your Desktop and open the new "rom" folder
First of all, you should now see 12 files in this folder. Delete the file "hboot_1.13.0000_CRC_8a731c6e_0401.img"... (This is mandatory! You MUST delete this file for the update to succeed! You may flash it on after installing the RUU if you wish, but you will lose S-OFF if you do not have radio S-OFF.)
Now open "android-info.txt" in wordpad or another similar text editor... The use of notepad is discouraged.
Now this is where the magic happens.
Change the line "modelid: PG3213000" to "modelid: PG3212000" (This will fix the "Model ID Incorrect" error)
[Optional] If you would like to flash the RUU without using a gold card then:
Add the following lines after "cidnum: OPTUS001":
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Now click "File" -> "Save".
Now Select all the files in the rom folder(Ctrl + A), right click on one of the file and select "Send to" -> "Compressed (zipped) folder" and rename the folder to PG32IMG.zip.
Return to this guide and follow the rest of the bullets under "How to install the Gingerbread update if you're S-OFF"
Enjoy your gingerbread RUU

Excellent tutorial, but would you help me with another issue?
I am running CyanogenMod 7 (2.3.4) on my Incredible S and I can't make calls because I can't hear or speak anything.
Now, I did that change to the script and I got past Model ID issues, but now it is saying my CID is incorrect??

IXXBC said:
Excellent tutorial, but would you help me with another issue?
I am running CyanogenMod 7 (2.3.4) on my Incredible S and I can't make calls because I can't hear or speak anything.
Now, I did that change to the script and I got past Model ID issues, but now it is saying my CID is incorrect??
Click to expand...
Click to collapse
Did you add the lines:
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111

a better way
this way works with every BRANDED IS (including canadian bell vr)
after using alpharevx to achieve s-off
u will want to install recovery next (just like any other tutorial tells you), but branded IS will always get a CID-incorrect
inorder to fix this, create a goldcard by following this link
wiki.cyanogenmod.com/index.php?title=Howto:_Create_a_Goldcard
except when you are on step 3, use this command instead
cat /sys/class/mmc_host/mmc2/mmc2:*/cid
USING MMC1 or MMC0 will never work!!!
using your goldcard, you will bypass all the cid incorrect problems
then you can use your gold card to flash recovery / radio
cheers

IXXBC said:
Excellent tutorial, but would you help me with another issue?
I am running CyanogenMod 7 (2.3.4) on my Incredible S and I can't make calls because I can't hear or speak anything.
Now, I did that change to the script and I got past Model ID issues, but now it is saying my CID is incorrect??
Click to expand...
Click to collapse
you will need to flash a new radio, under CM7 post he should have told you to flash a new radio. After flashing the new radio no audio bug will go away

Insufficient storage available after rooting!
Please ignore this post.

Hi
I followed all your instructions:
Downloaded : RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed
Then romved the hboot file
Updated android_info.txt to:
modelid: PG3212000
cidnum: OPTUS001
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
hbootpreupdate:13
mainver: 2.12.980.2
Zipped into the PG32IMG.zip file.
Uploaded to my sd card
Rebooted my phone in the bootloader...
But I get "CID incorrect"
What could I be doing wrong?
Then I checked XDA and found how to get my CID this is what I got:
C:\Users\fabian\Desktop\CWM>adb shell getprop ro.cid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
BM___001
How can I fix this?
Thanks.
Thanks.
My phone info:
vivo pvt ship s off lr
hboot 1.09.0000
Radio-38.02.01.17_m
eMMC-boot
Feb 11 2011 11:52:44

aresguerrero said:
Hi
I followed all your instructions:
Downloaded : RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed
Then romved the hboot file
Updated android_info.txt to:
modelid: PG3212000
cidnum: OPTUS001
cidnum: HTC__622
cidnum: HTC__038
cidnum: HTC__001
cidnum: HTC__044
cidnum: 11111111
hbootpreupdate:13
mainver: 2.12.980.2
Zipped into the PG32IMG.zip file.
Uploaded to my sd card
Rebooted my phone in the bootloader...
But I get "CID incorrect"
What could I be doing wrong?
Then I checked XDA and found how to get my CID this is what I got:
C:\Users\fabian\Desktop\CWM>adb shell getprop ro.cid
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
BM___001
How can I fix this?
Thanks.
Thanks.
My phone info:
vivo pvt ship s on lr
hboot 1.09.0000
Radio-38.02.01.17_m
eMMC-boot
Feb 11 2011 11:52:44
Click to expand...
Click to collapse
This method will only work if you have s-off, not s-on. You need to run AlphaRevX to gain s-off and then you can flash a new ROM.

Hi sorry for the confusion, I did S-OFF my device with AlphaRevX and installed CMW... I just copied and old txt file with the word S-ON on it.
Any ideas? By the way, what does CID stand for?

Excellent tutorial

This is beyond fantastic. I have had my phone in Hboot-Fastboot with a boot loop for 4 days and counting. It was so bad to the point where my GF was almost ready to buy me a new Sensation 4G off kijiji!
Regardless this is great news, I will try it out the minute I am home from work.
FINGERS CROSSED!
-----UPDATE-----
I followed the instructions front to back. Archived all of the ROM contects, made deletion of Hboot file in rom. Changed cid numbers. Renamed the archive as PG32IMG.zip after formatting my SD card. Went to hboot on my DincS, and it said image not found. Found it odd since it worked yesterday when I used a differend PG32IMG batch, it failed but it made it past the reading cycle before the update.
Any thoughts?

Hi guys
I really need your help here. Please
I've been able to:
S-Off using alpharevx.
Install CWM.
Root my device.
And even flash it with a Saskatel Froyo ROM.
I downloaded the OPTUS, Vigin and Europe ROMS, and every time tried flashing I get.
Model ID incorrect.
Then I found this thread
http://forum.xda-developers.com/showthread.php?t=1145541
Explaining this issue. I
unziped the files,
removed the booter file,
modified android.txt and added the lines described.
However, when I try flashing the ROM, I get a CID incorrect!!!!!!!!!
I really want to get GB, how do I overcome this?

@aresguerrero, is it really needed to double post?

Just loaded all files as described in tutorial. I am getting CID incorrect.
Just to clarify my Dincs is stuck in a bootloop. I have no backups, no custom firmware.
This is what my phone is showing:
---AlphaRev---
VIVO PVT SHIP S-OFF RL
HBOOT-1.09.1000
RADIO- 3005.04.03.22_M
cMMC-boot
Fed 11 2011, 11:52:44
HBOOT
CID incorrect!
Update Fail!

@ Thumper0G
I get the same CID Incorrect, the only ROM I've been able to flash is the one from Saskatel.
Keep me updated, I've looked a lot trying to find a solution.
Bye

aresguerrero said:
@ Thumper0G
I get the same CID Incorrect, the only ROM I've been able to flash is the one from Saskatel.
Keep me updated, I've looked a lot trying to find a solution.
Bye
Click to expand...
Click to collapse
Ran the RUU file and lost my S-OFF. so basically now im completely fugged!!!

Thumper0G said:
Ran the RUU file and lost my S-OFF. so basically now im completely fugged!!!
Click to expand...
Click to collapse
You are in the same boat I have been for two weeks now. If only Bell were to release their Gingerbread update and all problems would be avoided .

ClaudiuJer said:
You are in the same boat I have been for two weeks now. If only Bell were to release their Gingerbread update and all problems would be avoided .
Click to expand...
Click to collapse
Well here is the problem. I am stuck in a boot loop. Even though the RUU.exe says that the update has installed and my android is ready to use, I am still in a bootloop.
Yes this is awesome that the phone updated for once. PROBLEM> NO S-OFF and BOOTLOOP is still going on...
I am sooooo stuck.
NOW, here's a question. Would my phone be ok to send in for service now that the S-OFF is gone and it's back to S-ON or is my warranty no good.
Can I make a goldcard even though my droid is unusable?
if not can I use my gf's Incredible S. its the same phone, and carrier.

I've used this ROM to get gingerbread 2.3.
aresguerrero said:
Hi guys
I downloaded the OPTUS, Vigin and Europe ROMS, and every time tried flashing I get.
Model ID incorrect.
Then I found this thread
http://forum.xda-developers.com/showthread.php?t=1145541
Explaining this issue. I
unziped the files,
removed the booter file,
modified android.txt and added the lines described.
However, when I try flashing the ROM, I get a CID incorrect!!!!!!!!!
I really want to get GB, how do I overcome this?
Click to expand...
Click to collapse

@ ClaudiuJer
It occurs to me that:
You can get an XTC clip and get rid of the S-ON (Hardware)
Then flash the Saskatel 2.2 ROM as I did.
Hope that helps...

Which RUU , URGENT

Hi,
I am on Vodafone Germany. I have to send my Phone for repair. I need to unroot and get rid sign of TAMPERED.
I have read that i need to install RUU at the end. I have not able to find VODA Fone CID VODAP102 RUU.
I have install CWM and the back of CWM Nandroid Backup / CID VODAP102 / 1.29.161.7 but I am not able to get rid of TAMPERED message.
Kindly help and point me to right RUU.
Regards
Zeeshan

any body`? any idea ?

Tampered means you have a custom recovery installed. If you install the stock HTC One recovery, that tampered sign is supposed to go away.
http://forum.xda-developers.com/showthread.php?p=38504123
Just flash the stock recovery in fastboot and update us with the result.
All the RUUs available are found here:
http://forum.xda-developers.com/showthread.php?t=2207874
I'd be lying if I said I know which one you're supposed to install, sorry.

do s-off with supercid and you can install any ruu then you can relock bootloader and s-on and it wont say relocked on bootloader screen just dont mess with h-boot and s-on you will brick

Even after installing Stock Recovery, it still says TEMPERED.
If lock the bootloader it say Relocked otherwise unlocked.
If i change CID then It will be no longer Vodp102 ??
What to do next

That is more info
(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.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35EW902807
(bootloader) imei: 354436052324686
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4046mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.049s

you can change cid back. just use a ruu that has the same version that is available for your phone now
(bootloader) version-main: 1.29.161.16 this is what you should look for as far as the ruu

skinsfanbdh said:
you can change cid back. just use a ruu that has the same version that is available for your phone now
(bootloader) version-main: 1.29.161.16 this is what you should look for as far as the ruu
Click to expand...
Click to collapse
So if i get you correctly,
I Change CID to SUPERCID
then I can install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
and then after installation my phone will be like complete FACTORY RESET with everything like not TEMPERED or RELOCKED etc ??
After that without root, i can still change CID ??

herzlich said:
So if i get you correctly,
I Change CID to SUPERCID
then I can install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
and then after installation my phone will be like complete FACTORY RESET with everything like not TEMPERED or RELOCKED etc ??
After that without root, i can still change CID ??
Click to expand...
Click to collapse
you will still be s-off so yes you can change cid back and yes you can use commands to lock bootloader and it will say locked and same thing for tampered.

skinsfanbdh said:
you can change cid back. just use a ruu that has the same version that is available for your phone now
(bootloader) version-main: 1.29.161.16 this is what you should look for as far as the ruu
Click to expand...
Click to collapse
As I was now trying to download RUU but there is none for 1.29.161.16 .
Any idea now ?

herzlich said:
As I was now trying to download RUU but there is none for 1.29.161.16 .
Any idea now ?
Click to expand...
Click to collapse
just download the closest one if there isnt one for your carrier then thats the best you can do. unless you can find a nandriod from vadafone or whatever carrier you have

You could try to install a Nandroid back up of a Vodafone Germany Firmware
http://www.handy-faq.de/forum/htc_o...rom_wiederherstellen_via_nandroid_backup.html
Scrolling down a little there is a link to the Vodafone Nandroid Back Up 1.29.....
You find all Info you need, German Forum with several active xda members there.
After that you can flash the stock recovery, lock the bootliader and then S-on, if I am not mistaken.
Good luck
Sent from my HTC One using xda premium

hardstuffmuc said:
You could try to install a Nandroid back up of a Vodafone Germany Firmware.
http://www.handy-faq.de/forum/showthread.php?t=
Here you find all Info you need, German Forum with several active xda members there.
After that you can flash the stock recovery, lock the bootliader and then S-on, if I am not mistaken.
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
im pretty sure that will work. why exactly are you going back to stock. if you dont mind me asking

I just had to change the link to the correct thread in that forum, sorry for confusion.
Correct one again:
http://www.handy-faq.de/forum/htc_o...rom_wiederherstellen_via_nandroid_backup.html
Sent from my HTC One using xda premium

skinsfanbdh said:
im pretty sure that will work. why exactly are you going back to stock. if you dont mind me asking
Click to expand...
Click to collapse
I am having HISSING sound on 3G/UMTS/4G connections. on GPRS or GSM it works fine.
Vodafone will replace the set. For that I need to undo all these stuff.
I have tried that backup with CWM. I will try from German Forum now , let see.

herzlich said:
I am having HISSING sound on 3G/UMTS/4G connections. on GPRS or GSM it works fine.
Vodafone will replace the set. For that I need to undo all these stuff.
I have tried that backup with CWM. I will try from German Forum now , let see.
Click to expand...
Click to collapse
what rom are you on?

skinsfanbdh said:
what rom are you on?
Click to expand...
Click to collapse
I am not using any custom rom. I just rooted my phone and CWM touch recovery rest everything is default. So it is Stock customized version of Vodafone.

Then you should try first with a Custom ROM. See if that takes care of the hissing.
Try for example InsertCoin 1.0.8
http://forum.xda-developers.com/showthread.php?t=2279766
Do first Nandroid Backup of your current rooted stock Vodafone ROM, then flash IC 1.0.8 (that definitely has no hissing and is also based on 1.29 so no hassle with SDcard backing up and moving stuff around which you have to do with a ROM based on 2.17)
Then you know for sure!
Sent from my HTC One using xda premium

hardstuffmuc said:
Then you should try first with a Custom ROM. See if that takes care of the hissing.
Try for example InsertCoin 1.0.8
http://forum.xda-developers.com/showthread.php?t=2279766
Do first Nandroid Backup of your current rooted stock Vodafone ROM, then flash IC 1.0.8 (that definitely has no hissing and is also based on 1.29 so no hassle with SDcard backing up and moving stuff around which you have to do with a ROM based on 2.17)
Then you know for sure!
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Is there an easy way to do Nandroid backup other then this
http://forum.xda-developers.com/showthread.php?t=1818321 ???
I want to try the ROM you suggested.

Yes, of course!
Have the .zip of the InsertCoin 1.0.8 on your SDcard.
Boot up into your recovery, either CWM or TWRP, and select BackUp, then let it run, takes a few minutes.
Then do a factory reset/wipe cache, select then Install zip from SDcard, choose InsertCoin.zip and follow the instructions.
Use vol +/- and Power Buttons in Aroma Installer rather than touchscreen as Aroma freezing issues. Then finally boot up and see if you still have the hissing.
Sent from my HTC One using xda premium
---------- Post added at 06:57 AM ---------- Previous post was at 06:52 AM ----------
herzlich said:
Is there an easy way to do Nandroid backup other then this
http://forum.xda-developers.com/showthread.php?t=1818321 ???
I want to try the ROM you suggested.
Click to expand...
Click to collapse
Just a Nandroid on your fone within your recovery is fine. The instructions in that thread there needs some adb knowledge.
After you did a nandroid (= back up) you can copy it to your computer. Takes only a few moments
Sent from my HTC One using xda premium

[q] htc one bicked - start up loop (cant find ruu file)

I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921

abreu6 said:
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
Click to expand...
Click to collapse
There is an RUU for your One. The only issue is that ur S-ON and the RUU is for a lower firmware version than the one you have. To flash the RUU, you will have to downgrade your firmware, which needs S-OFF
Post the output of your getvar all. It'll help a lot
And do u have custom recovery?? What exactly did you do which bricked the phone ??

raghav kapur said:
There is an RUU for your One. The only issue is that ur S-ON and the RUU is for a lower firmware version than the one you have. To flash the RUU, you will have to downgrade your firmware, which needs S-OFF
Post the output of your getvar all. It'll help a lot
And do u have custom recovery?? What exactly did you do which bricked the phone ??
Click to expand...
Click to collapse
Hello, Thanks for helping out. I have a taiwan build of the phone, for some reason I got the message prompt to upgrade to kitkat and sense 5.5 ( the release isnt officially out in my region) I'm thinking I got it because of the firmware build of my phone, once i tried to upgrade thats where the stall happened.
To get S-Off i need to root my phone from my understanding is this correct ? I dont have a custom recovery will post the get var here.
Thanks again.

Since you bricked your phone, I'm going to safely assume you were at least on an unlocked bootloader. If that's the case, you can download the TWRP recovery image onto your PC and boot into it off your phone with the fastboot command "fastboot boot (recovery name).img". Once there, you can go to TWRP's advanced settings and turn on ADB sideload to install a ROM. After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON). That should get your phone back on.
My friend did the same thing the other day and that was how I got theirs working again.
Sent from my HTC One using xda app-developers app

decayer177 said:
"fastboot boot (recovery name).img".
Click to expand...
Click to collapse
That only works on hboot 1.44, "fastboot boot ...." was patched/broken after 1.44.
decayer177 said:
After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON).
Click to expand...
Click to collapse
That's not needed on the M7, it'll get flashed automatically during the install even with S-On.

decayer177 said:
Since you bricked your phone, I'm going to safely assume you were at least on an unlocked bootloader. If that's the case, you can download the TWRP recovery image onto your PC and boot into it off your phone with the fastboot command "fastboot boot (recovery name).img". Once there, you can go to TWRP's advanced settings and turn on ADB sideload to install a ROM. After that's done, go back into fastboot and flash the boot.img from the ROM separately before booting the ROM for the first time (since you're S-ON). That should get your phone back on.
My friend did the same thing the other day and that was how I got theirs working again.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help, no its locked and not tampared. I'm guessing i do all of the above but unlook my bootloader first.

abreu6 said:
Thanks for the help, no its locked and not tampared. I'm guessing i do all of the above but unlook my bootloader first.
Click to expand...
Click to collapse
Which RUU file do you recommend I can downgrade to. The version I have is 3.63.709.3 is there a site with ruu files. I have the latest ota file from the htc website, is the ruu file in there ?
Will try the procedure today and re post here.

abreu6 said:
I'm a complete newbie to this XDA so would appreciate any help possible.
My HTC One is Bricked and wont go beyond the HTC logo screen.
I've look at all the different forums and threads and I cant find one particular thread to guide me through the process.
The simplest way I can tell to get my phone back to stock without rooting and doing s-off is to use a ruu file, but I cant find one any where for my phone.
Can anyone help or point me in the right direction:
MEID PN0711000
HTC_621 (TW)
3.63.709.3
HT3AJW906862
356376050293921
Click to expand...
Click to collapse
Here's a copy of my getvar, -
Version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.213263.04
version-cpld: None
version-micorp: None
version-main: 3.63.709.04
version-misc: PVT SHIP S-On
serialno:HT3AJW906862
ProductL m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC_621
battery-status: low
battery-voltage: 3475mV
partition-layout: Generic
security: on
build-mode:SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-a448e85a
hboottpreupdate: 11
gencheckpt: 0
i tried to get my phone fixed but because its cross region nothing htc can do, and cost is as much as value of the phone. Will try all the tips here and repost. Thanks for everyone's help. Really appreciate it, this is a great forum
If anyone else has any other suggestions let me know.

nkk71 said:
That only works on hboot 1.44, "fastboot boot ...." was patched/broken after 1.44.
That's not needed on the M7, it'll get flashed automatically during the install even with S-On.
Click to expand...
Click to collapse
Yup the fastboot thingy doesnt work, anyother way i can use twrp if this is required. Unlocked my boot loader, are there any short cuts in this. Cant I just unlock, s-off and download any of the latest ruu files to bring my phone back to life ?

abreu6 said:
Yup the fastboot thingy doesnt work, anyother way i can use twrp if this is required. Unlocked my boot loader, are there any short cuts in this. Cant I just unlock, s-off and download any of the latest ruu files to bring my phone back to life ?
Click to expand...
Click to collapse
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!

nkk71 said:
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
Click to expand...
Click to collapse
will do, didnt realize i did that, thanks !

nkk71 said:
not right now, too sleepy, but i highly recommend you (and everybody else that quoted you) edit your posts and remove IMEI ... that information should NOT be shared publicly!
Click to expand...
Click to collapse
All removed, when i do the fastboot devices, the scrambled reply comes up which means im connected, but getvar all brings back nothing. I worried I may have done something wrong. Thanks

HTC one bricked
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA34MW909277
INFOimei: 354439059885634
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 3882mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
please help me out. I am using custom rom now .... no network .... no baseband. i am also confused that ruu is for me... i tried one but failed

[Q] GPe to Sense

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 ?

Bricked HTC One or hardware problem? S-ON, UNLOCKED.

Hello, my phone was booting to bootloader, or to CWM recovery only.
i think there is some hardvare error because recovery cant mount any partitions.. but it can be some kind of BRICK. here is what i have in my phone.:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
and here is getvar:
PHP:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34HW91****
(bootloader) imei: 35443**********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
ive get it like this, but with error message "Active Cmdline Overflow" and fixed it by using this guide,, than my phone started to boot but it boots infinitely a.k.a. hang on white HTC POWERED BY ANDROID logo... thats all iwe goot...
i have tried to flash this stock RUU.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
but it always end up with ERROR that this is wrong ruu file... but CID in GETVAR shows HTC__001 so this firmware fits...
i still can enter or flash recovery, now im on CWM v6.0.2.8
when im tryin for egsample WIPE DATA i get many errors like this:
PHP:
-- Wipping data...
Formatting /data
Error mounting /data!
Skipping format. . .
Formatting /cache...
Formatting /sd-ex...
Formatting /sdcard/ .android_secure!
Error mounting /sdcard/ .android_secure!
Skipping format...
Data wipe complete.
and i cant change my cid to supercid 11111111 i get some king of java card error... maybe because im S-On..
any help?

It looks like the ruu you are trying to flash is an older version than what is on your phone. Only way to downgrade is with s-off.
If you are on 6.x.x.x firmware, I don't think there is an ruu out yet for s-on phones.
Have you tried flashing stock recovery img and factory reset? It sounds like your partitions are messed up. I don't know if a stock recovery reset will fix that issue, but it is worth a shot. Only other method to fix partition errors is with an ruu
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
It looks like the ruu you are trying to flash is an older version than what is on your phone. Only way to downgrade is with s-off.
If you are on 6.x.x.x firmware, I don't think there is an ruu out yet for s-on phones.
Have you tried flashing stock recovery img and factory reset? It sounds like your partitions are messed up. I don't know if a stock recovery reset will fix that issue, but it is worth a shot. Only other method to fix partition errors is with an ruu
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
ok, i search an internet for what OS version i have because i dont know, not bootloader screen nor getvar showed it,
but depending on what RADIO and HBOOT and CID i have,
i find out that my os version should be 5.11.401.10
so i downloaded stock recovery for this and flashed,, and done a factory reset,,,
But nothing changed at all, only recovery..
i still have same bootloader and getvar results..
what more i should try ?
by the way, i cant s-off becaue my phone wont boot OS,, it shows that there is no os,,

If you are on 5.11.401.10, have you tried finding an ruu for that version? It seems that is your only hope.
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
If you are on 5.11.401.10, have you tried finding an ruu for that version? It seems that is your only hope.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
find out only .zip so far, but its OTA zip. i dont even know how to flash ota zips when im s-on... so since this is OTA there is no chance to get an .exe ....?
EDIT. it seems that i was trying to flash .zip tht ws only less than 100mb, now i find out OTA almost 700mb zipped.. ok will download and try now...
http://www.htc1guru.com/dld/ota_m7_...19-401-11_release_372404wj19h95c0x6oa19n-zip/

Uzephi said:
If you are on 5.11.401.10, have you tried finding an ruu for that version? It seems that is your only hope.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
ok, i cant flash OTA,, i get many errors of cant mount cache... so i need to find how to fix it...
maybe somebody know for what version RUU.exe is this OTA made ? 5.11.401.10 or what ruu.exe can be newer than this ota? so i can try older or newer ruu.exe

dainius87 said:
ok, i cant flash OTA,, i get many errors of cant mount cache... so i need to find how to fix it...
maybe somebody know for what version RUU.exe is this OTA made ? 5.11.401.10 or what ruu.exe can be newer than this ota? so i can try older or newer ruu.exe
Click to expand...
Click to collapse
you can't flash OTAs and there are no RUUs available at the moment above 4.xx, so with S-ON, you can't use RUU.
in either case, if you have now fixed the "Active Cmdline Overflow" error then you need to update recovery.
use TWRP 2.6.3.3 (or possibly 2.8.0.1) and follow instructions here: http://forum.xda-developers.com/showthread.php?t=2228274&page=3
in particular Point D, about truly formatting /data /system and /cache, once you format those, and reboot to recovery, you should be able to access the partitions again, then push or sideload a ROM as mentioned in Point E

nkk71 said:
you can't flash OTAs and there are no RUUs available at the moment above 4.xx, so with S-ON, you can't use RUU.
in either case, if you have now fixed the "Active Cmdline Overflow" error then you need to update recovery.
use TWRP 2.6.3.3 (or possibly 2.8.0.1) and follow instructions here: http://forum.xda-developers.com/showthread.php?t=2228274&page=3
in particular Point D, about truly formatting /data /system and /cache, once you format those, and reboot to recovery, you should be able to access the partitions again, then push or sideload a ROM as mentioned in Point E
Click to expand...
Click to collapse
Done everything except install rom otg... what ROM i have to chose? because i cant install those:
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.zip
and
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
so what file i should chose?

dainius87 said:
Done everything except install rom otg... what ROM i have to chose? because i cant install those:
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.zip
and
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
so what file i should chose?
Click to expand...
Click to collapse
neither, the first one is a decrypted RUU.ZIP which is lower than your current version so you can't flash that
the second is an OTA (Over The Air) update <- an update expect a certain version to already be on the phone, eg you cannot apply a Windows 8.1 patch on Windows XP
get yourself a ROM from: http://forum.xda-developers.com/htc-one#romList
the Development section, General section or wherever, and push it, then install it.
if you just want stock 5.11.401.10, you can find it here: http://forum.xda-developers.com/showthread.php?t=2759000

nkk71 said:
neither, the first one is a decrypted RUU.ZIP which is lower than your current version so you can't flash that
the second is an OTA (Over The Air) update <- an update expect a certain version to already be on the phone, eg you cannot apply a Windows 8.1 patch on Windows XP
get yourself a ROM from: http://forum.xda-developers.com/htc-one#romList
the Development section, General section or wherever, and push it, then install it.
if you just want stock 5.11.401.10, you can find it here: http://forum.xda-developers.com/showthread.php?t=2759000
Click to expand...
Click to collapse
ok, no custom roms vorked until i tested ViperOne, this one worked perfectly,, now i will go back to 100% stok after i will s-off..
thank you!