hello i need change cid to install another ruu romon my incredible s
because i got model id error when i install ruu..thanks
hashnoz said:
hello i need change cid to install another ruu romon my incredible s
because i got model id error when i install ruu..thanks
Click to expand...
Click to collapse
Changing the CID is not going to get you around the model id error. You need to be S-OFF and then you can manually edit the andrioid-info.txt and add the modelid to it.
i got s-off so now just i need change cid in android text
is it risk?
hashnoz said:
i got s-off so now just i need change cid in android text
is it risk?
Click to expand...
Click to collapse
Which RUU are you attempting to run? What you need to do is extract the ROM.zip from the RUU and then in the ROM.zip there is a file called android-info.txt that you need to edit and add a modelid= line to it for your modelid. Then you copy that ROM.zip file to your SD card and rename it PG32IMG.zip and reboot into bootloader and it will attempt to load the rom image.
Get into FASTBOOT USB mode and enter the following command and post the results:
fastboot getvar all
That will give us a true picture of what phone model you have and what you need to do.
Of course it is a risk. Especially considering even after you were told its the modelid that needed to be changed and you are still going on about the Cid.
i need to know what the risk if i add cid to rom.zip?
hashnoz said:
i need to know what the risk if i add cid to rom.zip?
Click to expand...
Click to collapse
The risk is that you are not understanding what you are being told to do. You will not solve our problem by changing the CID value.
The risk of modifying a ROM.zip with S-Off is that you cold flash one that is not compatible with your phone, thus the reason you were asked to run the Fastboot getvar all command so that we can help ou determine the correct RUU you should be working with.
i have incredible s for canadian
i need to install rom for another carrier...but i got model i error
error 130
hashnoz said:
i have incredible s for canadian
i need to install rom for another carrier...but i got model i error
error 130
Click to expand...
Click to collapse
Ok now we are getting some information that is useful. You will definitely need to modify the android-info.txt and add the line modelid=PG3212000 to the top of the file if you want to flash an official PG32IMG.zip file extracted from an RUU.
If you are S-Off why don't you install one of the stock, rooted ROMs in the Dvelpment section that were created from the WWE RUUs?
There is one based on WWE 2.30.405.1 which is the original GB/Sense 2.1 RUU and there is one based on WWE 3.08.405.3 which is the latest GB/Sense 3.0 RUU. I have installed and ran both of these on my Canadian IncS.
i edit the android.text but i cant install i have eng-soff what i need to do?
my incredible s AU....BM..i like install canadian rom through ruu but i cant
hashnoz said:
i edit the android.text but i cant install i have eng-soff what i need to do?
Click to expand...
Click to collapse
What error did you get? After you edited the android-info.txt file, did you then copy the ROM.zip file to your SD card and rename it PG32IMG.zip?
this not error just when checking the rom in bootloader didnt install anything
hashnoz said:
this not error just when checking the rom in bootloader didnt install anything
Click to expand...
Click to collapse
OK, in order to help us solve this, we need for you to post the contents of the android-info.txt that you modified and also from FASTBOOT USB mode, please run the following command and post the results:
fastboot getvar all
This will give us all of the details we need to assist you in getting straightened out.
Once again, since you are S-OFF you could simply go to the Development section and get the stock, rooted version of 3.08.405.3/Sense 3.0 ROM that you can simply flash from CWM Recovery and be done with it. You would still have S-OFF and root.
Related
please help me
how to downgrade 2.30.405.1 (with s-on) to 2.12.405.7 without xtc-clip
Sent from my HTC Incredible S using XDA App
kuba28ms said:
please help me
how to downgrade 2.30.405.1 (with s-on) to 2.12.405.7 without xtc-clip
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
You have posted a general question in the Developement forum. Anyway, it's not possible.
look at the bright side
I, too, mistakingly upgrade to 2.30.405.1. Looking forward to a way to be downgraded and S-off.
At the mean time, however, I made myself enjoin using better FM-Radio signal and much better image quality from camera in 2.30.405.1.
Note: my previous built was Gingerbread_S_HTC_WWE_2.12.405.7
it is possible to flash another RUU ROM using goldcard on a phone that comes with 2.30.405.1 ?
hussainmushahid said:
it is possible to flash another RUU ROM using goldcard on a phone that comes with 2.30.405.1 ?
Click to expand...
Click to collapse
No. You can't go 'backwards' with a Goldcard, just flash RUUs from different regions. If that were possible to do, then everyone on 2.30.405.1 would be able to downgrade and root easily and there wouldn't be any problems with it.
You have to flash the 2.12 Rom.zip via sd (gold) but change the 2.12 version number in the android-text to 2.30...worked for me...
TrippleT said:
You have to flash the 2.12 Rom.zip via sd (gold) but change the 2.12 version number in the android-text to 2.30...worked for me...
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but that will only work if you have S-OFF because by modifying the contents of the android-text file in the PG32IMG.zip file will invalidate the HTC signature and the HBOOT loader will fail trying to flash it an unsigned file.
tpbklake said:
Someone correct me if I'm wrong, but that will only work if you have S-OFF because by modifying the contents of the android-text file in the PG32IMG.zip file will invalidate the HTC signature and the HBOOT loader will fail trying to flash it an unsigned file.
Click to expand...
Click to collapse
I think that must be true, otherwise everyone would be doing it to get S-OFF!
doctorsax said:
No. You can't go 'backwards' with a Goldcard, just flash RUUs from different regions. If that were possible to do, then everyone on 2.30.405.1 would be able to downgrade and root easily and there wouldn't be any problems with it.
Click to expand...
Click to collapse
but you can flash a RUU of a different region and then use AlphaRevX to go S-OFF right? (sorry for asking a noob off-topic question)
hussainmushahid said:
but you can flash a RUU of a different region and then use AlphaRevX to go S-OFF right? (sorry for asking a noob off-topic question)
Click to expand...
Click to collapse
Not necessarily, it depends on the ROM you're currently running. For the most part you can use a gold card to flash an RUU that's the same version or newer than what you're running currently, which is useful to get a ROM that doesn't have the exploit patched that AlphaRevX uses. Some carrier's ROMs can't be flashed at all, no matter what, gold card or not. For example the latest Verizon Wireless ROM is completely locked down and can't be flashed/rooted/S-OFF'd without using an XTC Clip. Other carriers are better about leaving the ROM's alone. All you can do is try and see what happens.
TrippleT said:
You have to flash the 2.12 Rom.zip via sd (gold) but change the 2.12 version number in the android-text to 2.30...worked for me...
Click to expand...
Click to collapse
i tried it, creat gold card and extract rom.zip from 2.12 ruu and rename it to PG32IMG.zip an run bootloader. in hboot see this:
loading...PG32IMG.zip
when load complete:
checking...PG32IMG.zip
and after this step back to main hboot page and after reboot NO HAPPENS to my phone!!! my last rom is still alive you sure this way worked for you????
mhmb87 said:
i tried it, creat gold card and extract rom.zip from 2.12 ruu and rename it to PG32IMG.zip an run bootloader. in hboot see this:
loading...PG32IMG.zip
when load complete:
checking...PG32IMG.zip
and after this step back to main hboot page and after reboot NO HAPPENS to my phone!!! my last rom is still alive you sure this way worked for you????
Click to expand...
Click to collapse
Even with a goldcard, if you are S-ON and you modify the PG32IMG.zip by editting the android-info.txt file to change the version, you no longer have a HTC signature on the zip file and it will not flash. With S-ON you will not be able to flash a ROM that has a version number less than 2.30.xxx.x
Then have anyone known what "ROM that has a version number greater than or equal to 2.30.xxx.x" and can be S-off by "Alpharevx".
I also tried the same, even with a gold card. I think it worked for him because he is already S-OFF.
There is nothing we can do until a temp root method is found for 2.30. Or we could use an xtc clip to gain s-off.
if i use the clipm then will it be s-offed forever? or if u update hboot, then its fall back to s-on?
mrkekson said:
if i use the clipm then will it be s-offed forever? or if u update hboot, then its fall back to s-on?
Click to expand...
Click to collapse
The XTC clip will give you permanent S-OFF. Flashing a new HBOOT will not affect the S-OFF setting.
S-off + 2.30.405.1 = true
(if you are not monitoring the other thread)
a friend claims that the latest release(04pre3) NOW (did not before with earlier version) can S-OFF 2.30.405.1
http://revolutionary.io/
and other user writes:
AzizOnDeck said:
I can back that statement up! I'm currently S-OFF Running GB
Click to expand...
Click to collapse
finaly
Yea the incredible s can now be S-OFFed with the new 2.30.405.1 software version.
revolutionary this software can help you
Hai,
First... i'm from holland and sorry for my bad english!
My problem
I have a Incredible S made in Twaiwan and i search for a RUU that works!
I have try the follow one and comes a error 155.
Maby the wrong RUU?
I have try this one:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed
Can you help me please?
Thanks!
xander1986 said:
Hai,
First... i'm from holland and sorry for my bad english!
My problem
I have a Incredible S made in Twaiwan and i search for a RUU that works!
I have try the follow one and comes a error 155.
Maby the wrong RUU?
I have try this one:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed
Can you help me please?
Thanks!
Click to expand...
Click to collapse
The error 155 usually means that you are attempting to run a RUU on an unlocked HBOOT. You must relock the unlock boot loader and then you will be able to run the RUU. You may also need to create a goldcard to flash a WWE ROM on a Twaiwan IncS.
Ok how can i flash this goldcard?
xander1986 said:
Ok how can i flash this goldcard?
Click to expand...
Click to collapse
There is a process that turns your SD card into a goldcard so that you can flash RUUs from different regions. Once you make a goldcard, you can continue to use it as a normal SD card. Search xda for the procedure.
It's resolved! Thank you!
The thanks button is good for situations like these.
Hi, I bricked my htc incredible s.
After unbricking with jtag I have writed only bootloader with s-ON.
Recovery not working.
My phone has cid: BM___001 mid: PG3213000
I tried flash ruu rom from PG32IMG.zip i get a several errors
if i flash rom with PG3212000 i am geting wrong mid error
if rom cid not BM_001 i geting error wrong cid
if I manualy changin these parameter in android-info.txt i get signature error
tried flash from stock exe files like
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_release_199657_signed.exe
RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed.exe
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
same errors
port working not well
cant flash recovery, geting signature check error
What can I do?
Beneris said:
Hi, I bricked my htc incredible s.
After unbricking with jtag I have writed only bootloader with s-ON.
Recovery not working.
My phone has cid: BM___001 mid: PG3213000
I tried flash ruu rom from PG32IMG.zip i get a several errors
if i flash rom with PG3212000 i am geting wrong mid error
if rom cid not BM_001 i geting error wrong cid
if I manualy changin these parameter in android-info.txt i get signature error
tried flash from stock exe files like
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_release_199657_signed.exe
RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed.exe
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
same errors
port working not well
cant flash recovery, geting signature check error
What can I do?
Click to expand...
Click to collapse
Create a goldcard and then flash the RUU:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.480 2.30.0822U_3822.10.08.28_M_release_227170_signed.e xe
It is really strange that you have a PG3213000 but your CID is BM_0001 but a goldcard should allow you to flash the WWE RUU.
And another stupid question
If i make gold card with my another android phone (HTC Dream) do hi works in HTC Incredible S?
Beneris said:
And another stupid question
If i make gold card with my another android phone (HTC Dream) do hi works in HTC Incredible S?
Click to expand...
Click to collapse
Yes a goldcard is not specific to the phone it was created on. It is a special signature on the SD card that HTC is able to read.
Maked goldcard and same CID error
ht tp://img40.imageshack.us/img40/9578/ciderrorwithgoldcard.jpg
Any options?
Beneris said:
Maked goldcard and same CID error
ht tp://img40.imageshack.us/img40/9578/ciderrorwithgoldcard.jpg
Any options?
Click to expand...
Click to collapse
What procedure did you use to create the goldcard? It appears that the goldcard did not work.
You are trying to flash the 3.08.405.2 RUU, correct?
No, flashed this rom WWE_3.08.405.3, (3.08.405.2).
1. Inserted sdcard to htc derise hd
2. Unmounted from system
3. With GoldCardTool_0.0.5 readed card CID
4. From webpage with cid generated goldcard.img
5. And finaly with button [Load GoldCard.img] finished job
Cheked with DxH Hexeditor goldcard.img and SdCard first 170 lines the same.
another strange detail, nn the other side my phone model writed PG32120 but connsole said PG3213000
Beneris said:
No, flashed this rom WWE_3.08.405.3, (3.08.405.2).
1. Inserted sdcard to htc derise hd
2. Unmounted from system
3. With GoldCardTool_0.0.5 readed card CID
4. From webpage with cid generated goldcard.img
5. And finaly with button [Load GoldCard.img] finished job
Cheked with DxH Hexeditor goldcard.img and SdCard first 170 lines the same.
another strange detail, nn the other side my phone model writed PG32120 but connsole said PG3213000
Click to expand...
Click to collapse
OK, that is making more sense now. I was wondering how you had CID of BM_0001 with a PG321300 model. You need to flash this RUU:
http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_199657_signed.exe
On a side note, since you created it on a HTC Desire HD, did you use the right MMC value? You need to use MMC1 not MMC0.
Thanks a lot, my error was MMC0 value.
Now i maked right GoldCard.
Tried flash RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_ elease_199657_signed but after ZIP check, phone didn't done anything.
Second time flashed
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_release_199657_signed successful
One prob, wifi not working. Wifi wasn't worked and with others roms before brick.
Now in my settings showing Wifi mac address Unavailable
Do I missing wifi driver? I was told that wifi micro chip is new. (The man who writed a bootloader said to me)
I know that many people have had problems with 3.44 ruu not being available. I want to go back to the stock rom using the ruu but i can't seem to find it and when i try to use the latest available ruu it comes with a error bootlaoder version. Could someone please help me.
HTCdev
select 'vivid' and 'telstra' than 'find files' .
I think the first one is the one you are searching for, it says 3.44.841.3 in description.
Thats a kernel source file not the ruu
No RUU exists for 3.44. AFAIK, it was a kernel patch for a minor issue. Just flash the normal Telstra RUU, and try to OTA to 3.44.
You get error 140 when you use a earleir ruu
WildfireDEV said:
You get error 140 when you use a earleir ruu
Click to expand...
Click to collapse
Two things:
Make sure your bootloader is relocked.
Extract the rom.zip from the RUU (C:\Users\[YOU]\AppData\Local\Temp\{garbage numbers}), rename to PH39IMG.zip, paste on external SD's root, and reboot to bootloader. Accept update. Should not throw errors; I've used this method to downgrade countless times.
So I've asked this question before and I remember people telling me an RUU is capable of removing an HBoot and installing a new one under the conditions that the CID and MID are matching the RUU. My phone is S-On and my HBoot is GPE, but my CID and MID are T-Mobile and I want to return back to stock T-Mobile Sense 5. The new RUU has an HBoot higher than my 1.54 GPE HBoot so it should work... I haven't unlocked my phone through the HTCDev site, if that matters; I unlocked it through adb commands on GPE but I've tried relocking it via adb commands and I still get the error when I run the .exe file... My device is not recognized on HTC Sync Manager and there is no status bar on the "fastboot oem rebootRUU" menu like the instructions says there will... I tried flashing GPE recovery and even Sense 5 recovery; neither worked... I'm on ARHD 3.06.1700.10 ROM because I can't seem to flash stock ROM due to S-On... I'm starting to think that I get the error because of the GPE HBoot and S-On... Am I just screwed? Is it not possible to run an RUU if you have a different HBoot and S-On at the same time? Is it an issue with my drivers? Or is it because I haven't unlocked my device on the HTCDev site?
I'm sure it's due to you not having unlocked the phone
Vomers guide is very helpful
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Check this thread
Guich said:
Check this thread
Click to expand...
Click to collapse
Sorry about the late reply; since my phone is so messed up, I was trying to fix it with another route by doing Rumrunner S-Off first, but that isn't working out so well... So I'm back here trying to get past this error. The file in that thread cannot be used with my CID due to the .txt file inside the .zip file, and whenever I try to edit it with Notepad++ (the program that supposedly doesn't corrupt .txt files), it always corrupts the .txt file. Is it possible you or anyone (pretty please) could edit the .txt file inside the .zip file to have "T-MOB010" and send it to me somehow?
Edit: The download link is http://d-h.st/qfc by the way.
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!
alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.
alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!