Related
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...
Hi! Android noob here (as if you haven't heard this enough...) First of all, I tried to do the right thing and searched through the forum quite extensively, but either this problem was not described earlier, or I missed it. Anyway... If I posted a new topic inappropriately, I apologize and ask the mods to merge it into some existing thread you find suitable for this.
I have a Canadian IncS (was originally on Bell). Here are the current vitals:
Revolutionary S-Off
Revolutionary CWM v4.0.1.4
BlackRose HBOOT
VIVO PVT SHIP S-OFF RL
HBOOT-2.02.0002
RADIO-3831.18.00.28_M
eMMC-boot
Jun 02 2012,00:00:54
No Nandroid backups (Duh! My fault, I know). Previously, I managed to flash this ROM and the updated radio to the phone, and was running it wor some time. It was working, but with some stability issues. Being not sure whether the problem was with my device or the ROM, I decided to give another ROM a try. So, I flashed this ROM. Once rebooted after flashing, I ended up in a boot loop. Booted into Recovery, wiped the cache, rebooted, and got stuck on a white HTC screen. Did some digging, and it looked like it was a known issue listed under solved problems. Fair enough. Tried manually flashing boot.img from a PC (fastboot flash boot boot.img), as recommended, but the process got stuck in the "writing" phase. After waiting about half an hour, I had to pull the battery. Then I tried to flash the old ROM again, since I knew for sure it was working for me. Got the same result -- white HTC screen. Knowing that there was one suggested step for this ROM in particular in case of problems, and having done it in the past, I tried flashing the lib.img (fastboot flash lib lib.img) as described here. Guess what? It also got stuck in the "writing" phase...
After some more reading, I understood there were compatibility problems with some ICS kernels, and decided it would be easier to flush some GB ROM to see if it makes a difference. This ROM was my choice. Same result -- first, reboot loops after flashing, then the white HTC screen after wiping cache from Recovery...
I also tried using the official RUU, but couldn't get past the stage when it reboots the phone to a bootlader -- the phone hangs, the RUU is waiting for a bootloader, and manual restart into HBOOT or FASTBOOT and reconnecting the phone to a PC doesn't help...
So, as it stands right now, I have a "semi-bricked" device that I can boot into HBOOT or Recovery, but I can't flash anything from the PC ("sending" always completes successfully, but "writing" always hangs). I know for a fact this was working earlier, since I did use this procedure to flash the lib.img for the last ROM that worked on my phone, and also for flashing BlackRose HBOOT and the radio. All my last attemts to flash three different ROMs so far have been unsuccessful. I haven't got any other errors or diagnostic messages like vibrating 7 times, etc., so I hope (?) the hardware is not the problem. My first question: how badly is it screwed up? Second question: any bright ideas how to fix this? Any help would be greatly appreciated -- either a direct answer, or a kick in the rear in the right direction, if this has been discussed before. I may have done some stupid things (admittedly, I am one of those noobs that know enough to be dangerous, but still have very little clue what they are doing), but I hope to get it in the working state, and I will be more careful before messing around with it next time...
kt-Froggy said:
Hi! Android noob here (as if you haven't heard this enough...) First of all, I tried to do the right thing and searched through the forum quite extensively, but either this problem was not described earlier, or I missed it. Anyway... If I posted a new topic inappropriately, I apologize and ask the mods to merge it into some existing thread you find suitable for this.
I have a Canadian IncS (was originally on Bell). Here are the current vitals:
Revolutionary S-Off
Revolutionary CWM v4.0.1.4
BlackRose HBOOT
VIVO PVT SHIP S-OFF RL
HBOOT-2.02.0002
RADIO-3831.18.00.28_M
eMMC-boot
Jun 02 2012,00:00:54
No Nandroid backups (Duh! My fault, I know). Previously, I managed to flash this ROM and the updated radio to the phone, and was running it wor some time. It was working, but with some stability issues. Being not sure whether the problem was with my device or the ROM, I decided to give another ROM a try. So, I flashed this ROM. Once rebooted after flashing, I ended up in a boot loop. Booted into Recovery, wiped the cache, rebooted, and got stuck on a white HTC screen. Did some digging, and it looked like it was a known issue listed under solved problems. Fair enough. Tried manually flashing boot.img from a PC (fastboot flash boot boot.img), as recommended, but the process got stuck in the "writing" phase. After waiting about half an hour, I had to pull the battery. Then I tried to flash the old ROM again, since I knew for sure it was working for me. Got the same result -- white HTC screen. Knowing that there was one suggested step for this ROM in particular in case of problems, and having done it in the past, I tried flashing the lib.img (fastboot flash lib lib.img) as described here. Guess what? It also got stuck in the "writing" phase...
After some more reading, I understood there were compatibility problems with some ICS kernels, and decided it would be easier to flush some GB ROM to see if it makes a difference. This ROM was my choice. Same result -- first, reboot loops after flashing, then the white HTC screen after wiping cache from Recovery...
I also tried using the official RUU, but couldn't get past the stage when it reboots the phone to a bootlader -- the phone hangs, the RUU is waiting for a bootloader, and manual restart into HBOOT or FASTBOOT and reconnecting the phone to a PC doesn't help...
So, as it stands right now, I have a "semi-bricked" device that I can boot into HBOOT or Recovery, but I can't flash anything from the PC ("sending" always completes successfully, but "writing" always hangs). I know for a fact this was working earlier, since I did use this procedure to flash the lib.img for the last ROM that worked on my phone, and also for flashing BlackRose HBOOT and the radio. All my last attemts to flash three different ROMs so far have been unsuccessful. I haven't got any other errors or diagnostic messages like vibrating 7 times, etc., so I hope (?) the hardware is not the problem. My first question: how badly is it screwed up? Second question: any bright ideas how to fix this? Any help would be greatly appreciated -- either a direct answer, or a kick in the rear in the right direction, if this has been discussed before. I may have done some stupid things (admittedly, I am one of those noobs that know enough to be dangerous, but still have very little clue what they are doing), but I hope to get it in the working state, and I will be more careful before messing around with it next time...
Click to expand...
Click to collapse
First thing I would do is to upgrade your recovery image. You are using CWM 4.0.1.4 which is rather old. I would suggest using 4EXT Touch recovery. If you are unable to flash the recovery image in FASTBOOT USB mode, you can always do it using a PG32IMG.zip file from the SD card in HBOOT mode.
After that, I would try flashing any of the ROMs you mentioned again.
tpbklake said:
First thing I would do is to upgrade your recovery image. You are using CWM 4.0.1.4 which is rather old. I would suggest using 4EXT Touch recovery. If you are unable to flash the recovery image in FASTBOOT USB mode, you can always do it using a PG32IMG.zip file from the SD card in HBOOT mode.
After that, I would try flashing any of the ROMs you mentioned again.
Click to expand...
Click to collapse
tpbklake -- thanks very much for the response! In fact, I was thinking about doing just what you are suggesting, but so far I have been unable to find the actual image file for the 4EXT recovery, so I can flash it from the SD card -- it seems that it is supposed to be installed using an updater app from a working phone, which is out of the question in my case... Did I not look good enough, and is this image available somewhere?
Thanks again!
P.S.: OK, I must have been blind... I looked again, and found the link to the recovery.zip in the 4EXT thread. So, do I just rename it to PG32IMG.zip, or is there more to it than that?
kt-Froggy said:
tpbklake -- thanks very much for the response! In fact, I was thinking about doing just what you are suggesting, but so far I have been unable to find the actual image file for the 4EXT recovery, so I can flash it from the SD card -- it seems that it is supposed to be installed using an updater app from a working phone, which is out of the question in my case... Did I not look good enough, and is this image available somewhere?
Thanks again!
P.S.: OK, I must have been blind... I looked again, and found the link to the recovery.zip in the 4EXT thread. So, do I just rename it to PG32IMG.zip, or is there more to it than that?
Click to expand...
Click to collapse
The zip file needs to contain to 2 files, one is the recovery image (.img file) and the other needs to be a android-info.txt. If you have upgraded your radio, then if you look in the radio zip file there should be one there.
kt-Froggy said:
tpbklake -- thanks very much for the response! In fact, I was thinking about doing just what you are suggesting, but so far I have been unable to find the actual image file for the 4EXT recovery, so I can flash it from the SD card -- it seems that it is supposed to be installed using an updater app from a working phone, which is out of the question in my case... Did I not look good enough, and is this image available somewhere?
Thanks again!
P.S.: OK, I must have been blind... I looked again, and found the link to the recovery.zip in the 4EXT thread. So, do I just rename it to PG32IMG.zip, or is there more to it than that?
Click to expand...
Click to collapse
extract it and install the recovery img in fastboot
tpbklake said:
The zip file needs to contain to 2 files, one is the recovery image (.img file) and the other needs to be a android-info.txt. If you have upgraded your radio, then if you look in the radio zip file there should be one there.
Click to expand...
Click to collapse
So... Is it OK to just take the android-info.txt from the radio zip file? Is it not customized for a particular image file being installed? Sorry if this is a stupid question -- it just seems strange to me, and I'd like to be sure... This is what's inside this file that I have in the radio zip:
modelid: PG3212000
modelid: PG3213000
cidnum: 11111111
cidnum: BM___001
cidnum: HTC__001
cidnum: HTC__032
cidnum: HTC__038
cidnum: HTC__044
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__304
cidnum: HTC__405
cidnum: HTC__621
cidnum: HTC__622
cidnum: HTC__A07
cidnum: HTC__E11
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__Y13
cidnum: HTCCN701
cidnum: KT___901
cidnum: OPTUS001
cidnum: OPTUS002
cidnum: VZW__001
mainver: 1.36.405.1
hbootpreupdate:13
DelCache:1
Also, As I read in some other topic, I have to pack the files into zip with no compression, correct?
naathaanb96 said:
extract it and install the recovery img in fastboot
Click to expand...
Click to collapse
If I understand correctly, you are suggesting installing it using "fastboot flash recovery recovery.img" command from a PC, correct? That's exactly what I can't do, as described in my first post, and I am looking for a way to do it on the phone directly...
kt-Froggy said:
So... Is it OK to just take the android-info.txt from the radio zip file? Is it not customized for a particular image file being installed? Sorry if this is a stupid question -- it just seems strange to me, and I'd like to be sure... This is what's inside this file that I have in the radio zip:
modelid: PG3212000
modelid: PG3213000
cidnum: 11111111
cidnum: BM___001
cidnum: HTC__001
cidnum: HTC__032
cidnum: HTC__038
cidnum: HTC__044
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__304
cidnum: HTC__405
cidnum: HTC__621
cidnum: HTC__622
cidnum: HTC__A07
cidnum: HTC__E11
cidnum: HTC__J15
cidnum: HTC__M27
cidnum: HTC__Y13
cidnum: HTCCN701
cidnum: KT___901
cidnum: OPTUS001
cidnum: OPTUS002
cidnum: VZW__001
mainver: 1.36.405.1
hbootpreupdate:13
DelCache:1
Also, As I read in some other topic, I have to pack the files into zip with no compression, correct?
If I understand correctly, you are suggesting installing it using "fastboot flash recovery recovery.img" command from a PC, correct? That's exactly what I can't do, as described in my first post, and I am looking for a way to do it on the phone directly...
Click to expand...
Click to collapse
Yes, just create a new zip file with this android-info.txt and the 4EXT recovery.img file from the original zip file.
OK, thanks for confirming! I will try this tonight and post an update.
Well, there has been some development on the issue, and I am afraid it's bad news for me... First of all, I managed to upgrade the recovery to CWM 5.0.2.0, but the 4EXT refused to install no matter what I tried. Long story short, I successfully installed the Nik_IncredibleS_TriNiTy_SensationXL ROM from the updated recovery. However, because of several issues I ran into in the process, I did some more reading here on the forum, and found quite a bit of info regarding the eMMC chip failures that affect IncS among some other models. There are several threads about the issue, and they all have links to each other -- if anyone is interested in the details, search for "fried eMMC". For example, the first post here has some info confirmed by an HTC support staff. Or, here is another thread.
Anyway... I am almost certain I've got this problem, based on the symptoms and on the general info I found so far. My phone seems to be working now (has been up for several hours, and through a couple of reboots). I will see where is goes from here. I won't be doing any mods on this device for the time being. The replacement part (eMMC chip) is available online just for $20 or so. However, even though I've got some quite serious experience in electronics, soldering small BGA-type chips at home is not a trivial task, so I am not sure if I would really consider it. And replacing the board in the service centre is just too expensive...
tpbklake, thank you for prompt replies! Even though the original problem is not resolved, my phone is alive (for how long is another question), and I still learned a thing or two...
Hi i am trying to get my phone HTC desire C back to stock from Slim-Sense-v1 i downloaded CID getter from the playstore and found i have htc_001 but cant seem to find the latest ruu for it anywhere
tried the various methods on these forums however non have been successful i managed to unlock and flash using Desire_C_All-In-One_Kit_v1.0 so im a complete noob to these but would greatful if some kind chap would be able to help me .
wub901 said:
Hi i am trying to get my phone HTC desire C back to stock from Slim-Sense-v1 i downloaded CID getter from the playstore and found i have htc_001 but cant seem to find the latest ruu for it anywhere
tried the various methods on these forums however non have been successful i managed to unlock and flash using Desire_C_All-In-One_Kit_v1.0 so im a complete noob to these but would greatful if some kind chap would be able to help me .
Click to expand...
Click to collapse
www.htcruu.com - look for Golf
Thats where you can find everything you need.
been there done that
yep ive been there downloaded two ruu,s and tried all the steps mentioned from about 4 tutorials and still no luck
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
are the two i tried but they didnt work tried flash the system.img but that was too big according to cmd prompt
wub901 said:
yep ive been there downloaded two ruu,s and tried all the steps mentioned from about 4 tutorials and still no luck
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
are the two i tried but they didnt work tried flash the system.img but that was too big according to cmd prompt
Click to expand...
Click to collapse
Install it from pc.
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app
hutchinson epgoice
SO im g uessing nobody knows how to return this phone to stock ?
wub901 said:
SO im g uessing nobody knows how to return this phone to stock ?
Click to expand...
Click to collapse
Fist put supercid, then soff then install Thu from pc isn't so difficult. Then relock to son
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app
PopaStefanx said:
Fist put supercid, then soff then install Thu from pc isn't so difficult. Then relock to son
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app
Click to expand...
Click to collapse
Erm i h ave s on as there isnt a way to turn it off i have tried using the tutorials i have tried installing boot.img rocovery.img which goes fine but when i try to install the system.img through adb it tells me the files is too large
i have tried relocking the bootloader which works and using RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_1 0.11.98.09_1.06.98.13M2_release_265825_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10. 11.98.09H_1.06.98.13M2_release_295101_signed
and they both tell me that they are the wrong version and give me an error
PopaStefanx said:
Fist put supercid, then soff then install Thu from pc isn't so difficult. Then relock to son
Inviato dal mio HTC Sensation XE with Beats Audio Z715e usando XDA Premium HD app
Click to expand...
Click to collapse
Clearly Mr Spark here should read deeper into the forum for this device, ^__^ No S-Off im afraid.
wub901 said:
Erm i h ave s on as there isnt a way to turn it off i have tried using the tutorials i have tried installing boot.img rocovery.img which goes fine but when i try to install the system.img through adb it tells me the files is too large
i have tried relocking the bootloader which works and using RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_1 0.11.98.09_1.06.98.13M2_release_265825_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10. 11.98.09H_1.06.98.13M2_release_295101_signed
and they both tell me that they are the wrong version and give me an error
Click to expand...
Click to collapse
I found that happened with me, have you tried to let it run through the standard way of installing the software instead if using CMD based commands?
a reasonably intelligent reply would be nice seeing as i have tried installing t he ruu from a pc seeing as its an exe file!
wub901 said:
a reasonably intelligent reply would be nice seeing as i have tried installing t he ruu from a pc seeing as its an exe file!
Click to expand...
Click to collapse
Hey a little respect here.... I can understand that trying to restore to stock and it not going your way it can be stressful and frustrating.
When troubleshooting , you have to make sure you do everything to try and find the resolution
Im sorry bud, but when it comes to restoring to stock, we are a bit unlucky at the moment, some devices will go back, some wont.
Why do you want to go back to stock?
because i am trying to sell the phone i have tried the guide you have mentioned i have tried fastboot boot.img and recovery.img and relocking bootloader and then running the ruu and get a wrong version error i have tried changing from slim sense v1 to nameless and then unlocking bootloader and reflashing the boot & recovery.img and still not joy.
i have tried fastboot flashing the system.img but get that it is too large the ruu,s that i have used are RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
i got this phone from phones4u my hboot is 128.0000 and my radio is 1.06.98.13M2
error 130 model id error
ok so tried installing recovery.img worked
using nameless rom v7
removed supersu
relocked bootloader following fkofilee,s guide and get error 130 model id error from both ruu files
wub901 said:
because i am trying to sell the phone i have tried the guide you have mentioned i have tried fastboot boot.img and recovery.img and relocking bootloader and then running the ruu and get a wrong version error i have tried changing from slim sense v1 to nameless and then unlocking bootloader and reflashing the boot & recovery.img and still not joy.
i have tried fastboot flashing the system.img but get that it is too large the ruu,s that i have used are RUU_GOLF_U_ICS_40A_HTC_Europe_2.00.401.2_Radio_10.11.98.09H_1.06.98.13M2_release_295101_signed
and
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.4_R_Radio_10.11.98.09_1.06.98.13M2_release_265825_signed
i got this phone from phones4u my hboot is 128.0000 and my radio is 1.06.98.13M2
Click to expand...
Click to collapse
who are you trying to sell it too?
to a shop who most probably wont buy it with a custom rom on it
wub901 said:
to a shop who most probably wont buy it with a custom rom on it
Click to expand...
Click to collapse
They will, they mostly wont check ha, my advice to you is (After having the same problem) Install a Custom Rom That Isnt Like Nameless Or Has A Custom boot Animation That Appears To Obvious.
Yeah thats an idea but its not really solving my problem of getting it back to stock is it ?
anyway i was having a google and thought i may work putting the rom file on the sd card and renaming the zip to PL01IMG.zip well hboot read the file and checked it then gave me a model id error so is there anyway i can change the model id in to ruu zip to match the phone ?
wub901 said:
Yeah thats an idea but its not really solving my problem of getting it back to stock is it ?
anyway i was having a google and thought i may work putting the rom file on the sd card and renaming the zip to PL01IMG.zip well hboot read the file and checked it then gave me a model id error so is there anyway i can change the model id in to ruu zip to match the phone ?
Click to expand...
Click to collapse
If the cid doesn't match it won't let you do it and there's no way of changing it. There is another way tho you could extract the Rom.zip from the ruu get the system and boot img and use the android kitchen to build it into a flashable zip then use cwm to flash back to stock then just flash back the stock recovery.
Sent from my HTC Desire C using xda app-developers app
andrewtjb said:
If the cid doesn't match it won't let you do it and there's no way of changing it. There is another way tho you could extract the Rom.zip from the ruu get the system and boot img and use the android kitchen to build it into a flashable zip then use cwm to flash back to stock then just flash back the stock recovery.
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
ok the cid id HTC_001 which is in the android-info.txt of the rom
modelid: PL0110000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__016
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__A48
hbootpreupdate:13
mainver: 1.45.401.4
DelFat:1
DelCache: 1
but there must be a way to change to model id of the zip file to match the phone surely as for android litchen il give that a go what would be good is if we had a stock ROM we could just flash through CWM then just flash the boot and recovery .
wub901 said:
ok the cid id HTC_001 which is in the android-info.txt of the rom
modelid: PL0110000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__016
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__A48
hbootpreupdate:13
mainver: 1.45.401.4
DelFat:1
DelCache: 1
but there must be a way to change to model id of the zip file to match the phone surely as for android litchen il give that a go what would be good is if we had a stock ROM we could just flash through CWM then just flash the boot and recovery .
Click to expand...
Click to collapse
Not That simple my friend, sorry , ive tried to do everything to my old desire C , and it didnt work.
oh guys,come on, i say somebody should make a backup on CWM,of his original stock,upload it on the net,and everybody who wants a original stock can get it
Sent from my HTC Desire C using xda premium
Hello every one
After several requestes here it is the Original STOCK file to flash the Eurpean HTC One M8 from the RUU BACK TO STOCK
You can flsh throu fastboot or change the name of the file to 0P8BIMG.zip and put it in SDCard and load Bootloader
S-Off is Required with Eurpean CID
0P8BIMG_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.18.401.3_Radio_1.101.1102.19.1017_10.26.4149.00L_release_402779_signed.zip
https://drive.google.com/file/d/0B17smFr95pled3lCT19UOG1ZV3c/view?usp=sharing
Go into fastboot
type
fastboot oem rebootRUU
fastboot flash zip zipfile.zip
modelid: 0P8B20000
modelid: 0P8B23000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__032
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__A48
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
Thank you for sharing!
Which firmware version is this? I am assuming its 1.16.401.2 (and not 2.16.401.1, 2.18.401.3 or 2.19.401.1)?
As the name of the file states, it should be 2.18.401.3.
Gesendet von meinem HTC One_M8
ahhh yes, you are right...
- is there a RUU.exe version of this as well?
- and is the S-Off method SunShine or has something else come up?
Thank you...
If I flash this, am I back to stock recovery then? Btw can I flash this without being s-off?
Sent from my GT-I9505 using XDA Free mobile app
File seems to broken, neither fastboot or TWRP will flash it.
Rename the file to 0P8BIMG.zip and put it on root of the sdcard.
Boot in bootloader and it will update the software.
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
S-Off is Required with European CID
djluisbento said:
Hello every one
After several requestes here it is the Original STOCK file to flash the Eurpean HTC One M8 from the RUU BACK TO STOCK
You can flsh throu fastboot or change the name of the file to 0P8BIMG.zip and put it in SDCard and load Bootloader
S-Off is Required with Eurpean CID
0P8BIMG_M8_MINI_UL_K44_SENSE60_HTC_Europe_2.18.401.3_Radio_1.101.1102.19.1017_10.26.4149.00L_release_402779_signed.zip
https://drive.google.com/file/d/0B17smFr95pled3lCT19UOG1ZV3c/view?usp=sharing
Go into fastboot
type
fastboot oem rebootRUU
fastboot flash zip zipfile.zip
modelid: 0P8B20000
modelid: 0P8B23000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__032
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__J15
cidnum: HTC__A07
cidnum: HTC__A48
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
Click to expand...
Click to collapse
Dear djluisbento
You write S-Off is Required with European CID, OK, but first of all, I should be able, to set my htc One mini2 (CIDNUM VODAP110) S-Off!
Don't know how yet? Any idea???
Greetings and thanks for an answer!!!
JAS
Johann A. Sutter said:
Dear djluisbento
You write S-Off is Required with European CID, OK, but first of all, I should be able, to set my htc One mini2 (CIDNUM VODAP110) S-Off!
Don't know how yet? Any idea???
Greetings and thanks for an answer!!!
JAS
Click to expand...
Click to collapse
Hello, try the root ninja
http://theroot.ninja/
djluisbento said:
Hello, try the root ninja
http://theroot.ninja/
Click to expand...
Click to collapse
Dear djluisbento
Nada, tried it and get answer:
"At this time we do not Support your device, SORRY!"
Any other idea who does and how?
Thanks
JAS
Johann A. Sutter said:
Dear djluisbento
Nada, tried it and get answer:
"At this time we do not Support your device, SORRY!"
Any other idea who does and how?
Thanks
JAS
Click to expand...
Click to collapse
I hope that it said that.
At the moment is not possível to soff this model.
we have to wait
djluisbento said:
I hope that it said that.
At the moment is not possível to soff this model.
we have to wait
Click to expand...
Click to collapse
Dear djluisbento
Thank you, but Sorry, I don't understand your Statement.
You mean, we have to wait, but on what/whom do we have to wait?
Who is probably able to solve this problem and how works the announcement to the owners of this devices??
Namely before this devices are old and replacement is scheduled???
Johann A. Sutter said:
Dear djluisbento
Thank you, but Sorry, I don't understand your Statement.
You mean, we have to wait, but on what/whom do we have to wait?
Who is probably able to solve this problem and how works the announcement to the owners of this devices??
Namely before this devices are old and replacement is scheduled???
Click to expand...
Click to collapse
Good afternoon,
The s-off, unlock the equipment to change any file type or rom / bootloader.
It is currently not possible to unlock this equipment to modify the bootloader since there is not much development for this equipment.
djluisbento said:
Good afternoon,
The s-off, unlock the equipment to change any file type or rom / bootloader.
It is currently not possible to unlock this equipment to modify the bootloader since there is not much development for this equipment.
Click to expand...
Click to collapse
OK, I understand, that there is not much development for this Equipment, but have you any idea, where I can inform myself about the state of
eventually activations about development/developers for this Equipment???
I read much about the same wishes of a lot of other fellow sufferers in Internet Forums and I'm quite shure, that I'm not the only one in the
western hemisphere who likes to have soon success to be free, to decide, what he can do with his own property.
HTC indeed does not help you, on the contrary, they help you namely to unlock the bootloader and thats it!!! Whatfore???
So, in a manner of speaking, they gave you a nice car but they deny to give you gasoline to drive with it!!!
Think it's time to give up all endeavours, waisted to much time already http://cdn3.xda-developers.com/images/smilies/crying.gif and change to another product!!!
Thanks a lot
JAS
Right now I am on CM12 and I accidentally deleted my stock backup. Now if I want to go back what are the exact steps?
Please help me here. I don't want to mess this up.
djluisbento said:
Hello, try the root ninja
http://theroot.ninja/
Click to expand...
Click to collapse
Dear djluisbento
Finally success > the developers of "Sunshine" worked it out, my HTC One mini2 is S_OFF!
Thanks to all
JAS
Johann A. Sutter said:
Dear djluisbento
Finally success > the developers of "Sunshine" worked it out, my HTC One mini2 is S_OFF!
Thanks to all
JAS
Click to expand...
Click to collapse
Thanks. Glad to Know.
Hi Dear, ho can I do S-Off on my HTC One mini 2? I'd like to return to Stock ROM, but I don't know how do I bring the system in S - OFF...thantk you
Shikaiya said:
Hi Dear, ho can I do S-Off on my HTC One mini 2? I'd like to return to Stock ROM, but I don't know how do I bring the system in S - OFF...thantk you
Click to expand...
Click to collapse
You must flash a stock backup, then try sunshine for s-off
Mr
Hi All
I have a problem with this Ruu 0P8BIMG i cannot copy to SD card nor can i flash it on device
i have downloaded it three times and still no joy not sure what to do as zip extractor on the site just hung forever
Thanx in advance
Here you have philz touch recovery ported from YUREKA . Its full working and I prefer this one instead to CWM, because it´s more modded.
Put the zip in the root of your microsd, boot into bootloader and Update will automatically start
DeviceTree : https://github.com/joker2910/android_device_htc_a11ul
EDIT : Attached new , fresh compiled Recovery + my device_tree, used for compiling Philz recovery
greeneyes2910 said:
Here you have philz touch recovery ported from YUREKA . Its full working and I prefer this one instead to CWM, because it´s more modded.
Put the zip in the root of your microsd, boot into bootloader and Update will automatically start
Click to expand...
Click to collapse
You're doing a fantastic job. Keep up the good work! ?
Sent from my 0PCV1 using XDA Free mobile app
Thanks for recovery,working perfect on my phone
Is the board name "msm8916" the sufficient compatibility factor to apply this corectly?
(CPU-Z says my board name is msm8916, however
There is nowhere in the CPU-Z reports about "A11UL" - but HBOOT reports it.)
greeneyes2910 said:
Put the zip in the root of your microsd, boot into bootloader and Update will automatically start
Click to expand...
Click to collapse
Is this instruction referring to CWM already installed? (I don't have it yet.)
How to evoke bootloader afterall? When pressed volume down & Power then HBOOT starts but unfortunatelly it reports:
"CID incorrect"
The zip file has been placed in the root of the SD card - as you suggested. What is wrong?
ioy said:
Is the board name "msm8916" the sufficient compatibility factor to apply this corectly?
(CPU-Z says my board name is msm8916, however
There is nowhere in the CPU-Z reports about "A11UL" - but HBOOT reports it.)
Is this instruction referring to CWM already installed? (I don't have it yet.)
How to evoke bootloader afterall? When pressed volume down & Power then HBOOT starts but unfortunatelly it reports:
"CID incorrect"
The zip file has been placed in the root of the SD card - as you suggested. What is wrong?
Click to expand...
Click to collapse
It seems you have not an European 64Bit Desire. So you have to unzip first andy modify the android info to match your cid. Zip again & try then
Working, good job.
greeneyes2910 said:
It seems you have not an European 64Bit Desire. So you have to unzip first andy modify the android info to match your cid. Zip again & try then
Click to expand...
Click to collapse
You probably mean the file android-info.txt with the content:
Code:
modelid: 0PCV20000
cidnum: HTC__001
cidnum: HTC__031
cidnum: HTC__102
cidnum: HTC__Y13
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__002
mainver: 1.51.401.1
btype:1
aareport:1
DelCache:1
hbootpreupdate:13
What to write in? How to find CID of my phone? It is apparently msm8916 as (CPU-Z reports) and "A11UL" (as HBOOT says so), besides TheDreamer kernel works on it.
I've got it from T-Mobile in the European Union country. Where to get CID from within this phone?
or just unzip the file and using fastboot flash it to your phone, which is how I did it. Works a treat.
Burtrum, hope the compatibility's proven sufficently to rely on this version of recovery as working well with my phone after using the "brut force" you suggesting
do you have to be rooted on the 64 BIT first? because i just unlocked my boot loader
ioy said:
Burtrum, hope the compatibility's proven sufficently to rely on this version of recovery as working well with my phone after using the "brut force" you suggesting
Click to expand...
Click to collapse
Lol. If I do have an issue I'll use the same method to put CWM back on there. But that is the method I've used with my Incredible S, HOX and now this phone
It's ok, the "simple CID getter" told me what the CID was and this putted to android-info.txt yielded perfectly working recovery now
Thank you!
Flashed via fastboot, works a charm. Thank you soooo much!! Now we just need some x64 roms! :0)
is anyone able to make a 64bit back up.
im stuck in limbo at the moment with my fone its unlocked rooted and has this recovery on it but no OS due to a mistake i made .
Maybe this Recovery would work well with yet-unexisting modded 64bit ROMs updates.
However HTC has just released update of its stock 64bit ROM (which is reported to work smoother than previous one) and this Recovery doesen't allow for doing the update.
So where to get the 64 bit STOCK recovery back from?
OR maybe you would propose any trick to overcome this obstacle without touching the PhilzTouchRecovery please?
(When manually chosen OTA_xxxxxx.zip it complains about not finding /system/build.prop )
Works great thank you, now all we need is some roms
Beshnazzle said:
now all we need is some roms
Click to expand...
Click to collapse
Yes, we wait for them patientlessly! :-/
And the stock recovery one could extract from OTA_*****.zip update file. It's simple, just unzip.
ioy said:
Yes, we wait for them patientlessly! :-/
Click to expand...
Click to collapse
Well, me and you could team up and try to port a 32 bit on to our one? idk how but i found a tutorial on it
Okay so ive been trying to get the ROM files from my device by using "Clone ROM to update.zip" within Philz CWM but the /system file named "system.ext4.tar" wont extract i get This Message for some reason and i dont know what to do.
Beshnazzle said:
Okay so ive been trying to get the ROM files from my device by using "Clone ROM to update.zip" within Philz CWM but the /system file named "system.ext4.tar" wont extract i get This Message for some reason and i dont know what to do.
Click to expand...
Click to collapse
Hello,
I don't know what that "Clone ROM to update.zip" is, but I can help you to simply extract system.ext4.tar. I don't know how to do it in Windows without Cygwin but if you use that program or Linux you can type:
Code:
tar -xvf system.ext4.tar
in a terminal and it will extract your whole system to the folder you are in. This is a very quick and easy way to obtain /system.