Related
Hi please could somebody help me, I have a Desire S which I got on contract from 02 with a 02 branded rom on there originally and hboot 0.98.0002.
I had S-off, 4ext recovery, upgraded to hboot 2.00.0002 and a custom rom installed.
I have flashed a offical RUU RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe
and now I am stuck in hboot and it says **security warning** hboot version 0.98.000
I tried to flash the above o2 RUU again but it says bootloader version error, So I tried RUU 1.28, 1.47 and 2.10 with a gold card in the phone but the same error all the time.
I have also extracted the rom.zip from each of these and put it onto the goldcard renamed to PG88IMG.zip but then this says MAIN VERSION OLDER and will not flash.
Now I am really stuck on what I need to do, do I need to flash a 0.98.0002 hboot? as at the momment I have 0.98.000, if so how can I do this?
I have lost 4ext recovery, and back to S-On.
If anyone has any ideas I would be really grateful.
Thank you in advance
Cheers
edit: I think the bootloader I currently have on the phone 0.98.000 is incorrect ? , it should be 0.98.0000 or 0.98.0002? . As the hboot is S-ON is there anyway I can flash a hboot through using adb, or does it have to be S-OFF, if so is there anyway I can S-OFF in bootloader or fastboot alone, as I can't do anything else.
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
amidabuddha said:
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
Click to expand...
Click to collapse
Hi thanks for your reply, I currently have 0.98.000 hboot on the phone now which is S-ON. My gold card seems to be working as it doesn't say any CID errors.
How can I tell if my device is bricked?
I can only get into hboot, and fastboot/stock recovery. The phone won't do anything else and I can't flash any rom as it says about the bootloader version, but on the bootloader it says **security warning** at the top. Is there anyway I can flash a newer hboot? or won't it let me as it is S-ON, if its S-ON will I be able to flash a hboot or even 4ext recovery to flash a rom?
If so how can I s-off just using bootloader and fastboot?
I thought goldcard is only to bypass the CID checks so you can flash a debranded RUU.
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
amidabuddha said:
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
Click to expand...
Click to collapse
Hi, I have done the fastboot commands you said and below are the numbers I got:
fastboot devices - serial number which came up is: HT15NTJ00403
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Thank you for your help with this
Try to put last rom.zip on sdcard with PG88IMG.zip name from version 2.10.401.8 RUU and maybe you will have new hboot 2.00.2002 and then have to unlock hboot from http://htcdev.com/.
first_damned said:
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Click to expand...
Click to collapse
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
amidabuddha said:
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
Click to expand...
Click to collapse
Hi, I have tried RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe using the RUU on the laptop and tried extracting the rom.zip, renaming as PG88IMG.zip and flashing off sd card (goldcard), but the RUU said bootloader version error and flashing the PG88IMG.zip says main version older error.
There isn't a 2.10.401.4 version, but there is a
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed.exe
I would of thought the 2.10.401.8 should of worked?
also would I be able to flash a hboot being S-ON do you think?
I'm not sure how low my battery is also, If I plug it into the charger will it charge the phone on the bootloader do you know?
Thanks
All version info
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 38.03.02.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 11.10.401.4
INFOserialno: HT15NTJ00403
INFOimei: 356708041449842
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 3851mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
amidabuddha said:
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
Click to expand...
Click to collapse
Hi there, I have tried adb devices but it doesn't come up with my device which is strange. Maybe because my device is S-ON?
Do you think if I took it to a mobile repair shop and had it jtagged to restore original software would do the trick?
thanks
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
amidabuddha said:
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
Click to expand...
Click to collapse
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
first_damned said:
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
Click to expand...
Click to collapse
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
amidabuddha said:
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
Click to expand...
Click to collapse
I can't get adb to see the device, fastboot will do though but won't flash hboot, it says remote signature fail.
Looks like im going to have to send the phone off to be J Tagged. I have found a shop that does this for £24.99 and they know there stuff.
But if anyone has anymore ideas please let me know.
Thank you amidabuddha for your help, I will keep you updated on any progress.
Simon
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
poppy8x said:
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
first_damned said:
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
Click to expand...
Click to collapse
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
poppy8x said:
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
first_damned said:
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
Click to expand...
Click to collapse
Yeah. All worked. Look at my sig.
A month ago, i had "sercurity warning" too (i run RUU 1.48). Gold card coudn't do anything. And then i s-off by xtc-clip (in 5 mins)
Sry for my english bad.
Sent from my HTC Desire S using xda premium
how to know my desire s region?i from malaysia
dante0927 said:
how to know my desire s region?i from malaysia
Click to expand...
Click to collapse
it is recommended that you adjust the following two settings:
Settings->Applications->Development->USB debugging = TICK (Yes)
Settings->Power->Fast boot = UNTICK (No)
Install ADB/FASTBOOT on your PC (by following advice given in this thread http://forum.xda-developers.com/showthread.php?t=1272595 )
You should reboot the phone so that its in BOOTLOADER (fastboot) mode. ( Its a good idea to note the details on the initial bootloader coloured screen radio/hboot versions etc)
plug in USB cable from PC
and type the following into a CMD window the directory where adb/fastboot was installed
Code:
fastboot getvar cidnum
and the purpose of that is you'll get returned the region ie HTC__001
You'll find the code in the following list http://forum.xda-developers.com/attachment.php?attachmentid=994630&d=1334067717
I also suggest that you run this command
Code:
fastboot getvar all
which should return a greater amount of information.
You should then be able to determine your base ROM details and noting all the details in settings...about phone....software ....more
try it here: http://www.htc.com/cn/help/chat/click on the button at right, keyin IMEI, SN and verifying code, click on the green button, it will show you
ben_pyett said:
it is recommended that you adjust the following two settings:
Settings->Applications->Development->USB debugging = TICK (Yes)
Settings->Power->Fast boot = UNTICK (No)
Install ADB/FASTBOOT on your PC (by following advice given in this thread http://forum.xda-developers.com/showthread.php?t=1272595 )
You should reboot the phone so that its in BOOTLOADER (fastboot) mode. ( Its a good idea to note the details on the initial bootloader coloured screen radio/hboot versions etc)
plug in USB cable from PC
and type the following into a CMD window the directory where adb/fastboot was installed
Code:
fastboot getvar cidnum
and the purpose of that is you'll get returned the region ie HTC__001
You'll find the code in the following list http://forum.xda-developers.com/attachment.php?attachmentid=994630&d=1334067717
I also suggest that you run this command
Code:
fastboot getvar all
which should return a greater amount of information.
You should then be able to determine your base ROM details and noting all the details in settings...about phone....software ....more
Click to expand...
Click to collapse
after i type fastboot getvar cidnum,they show cidnum:11111111.it is mean wat?
You're super cid, which is like being region free
shrome99 said:
You're super cid, which is like being region free
Click to expand...
Click to collapse
it means all region of this rom oso can update over air?
No, you'll only recieve OTA updates to the version of the ROM your on, which also has a reigon Post the build no. of your ROM so that i can tell you what the reigon is.
Alternately, you're SuperCID, so you can probably flash the RUU of any region you want
Sent from a device waiting for Kernel 3, WAKE UP HTC
shrome99 said:
No, you'll only recieve OTA updates to the version of the ROM your on, which also has a reigon Post the build no. of your ROM so that i can tell you what the reigon is.
Alternately, you're SuperCID, so you can probably flash the RUU of any region you want
Sent from a device waiting for Kernel 3, WAKE UP HTC
Click to expand...
Click to collapse
my build no is 2.15.707.2
dante0927 said:
my build no is 2.15.707.2
Click to expand...
Click to collapse
Asia WWE
Sent from my HTC Desire S
amidabuddha said:
Asia WWE
Sent from my HTC Desire S
Click to expand...
Click to collapse
if got ics update, can i update via OTA?
just wondering my cid is 038 what region is my desire s from?
038 is the CID for India.
Sent from a device waiting for Kernel 3, WAKE UP HTC
Hello
My cidnum is HTC___Y13 wich mean is HTC-NOR
Then, wich rom i should install?
A fast reply will be very helpfully!!!Because i'm stucked in BOOTLOADER....
I think an European should do. Download a RUU, run it without device, when the first window appears, do not close it, search your C drive for rom.zip, copy it to another location and close the RUU window. Open the zip, you will see a file called android-info.txt. It contains all the CIDs. Check if yours is there. If yes use it
Sent from my HTC Desire S using xda app-developers app
Can't find out the cid for this phone if you have this sensation phone model
an yes i tried using adb but my computer will not reconginze my device even when i update the drivers
and i can't use CID Getter since im bootlooped.
So i guess this is my last resort.
If you have the CID num for HTC-Z710a
Model: PG58110
What's your bootloader info?
Sent from my sensational sensation 4g
LOL your not gonna find the cid from the information provided. Is your phone branded? Where did you purchase it? Can you access h boot to get to fastboot? Did you try using adb in fastboot? "fastboot getvar cid" is the command.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Rhiannon224 said:
LOL your not gonna find the cid from the information provided. Is your phone branded? Where did you purchase it? Can you access h boot to get to fastboot? Did you try using adb in fastboot? "fastboot getvar cid" is the command.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
I can get into fastboot i did try to use adb in fastboot did not work.
I bought my phone from Bell
Thanks for the reply
yahhboy said:
What's your bootloader info?
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO 10.14.9035.01_M
eMMC-boot
CID incorrect ATM i know how to fix (just delete img file) but i can't get a CID that is correct.
tom8907 said:
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
RADIO 10.14.9035.01_M
eMMC-boot
CID incorrect ATM i know how to fix (just delete img file) but i can't get a CID that is correct.
Click to expand...
Click to collapse
this wont give you cid ..afaik lot of ppl with different cid will have the same config...
go to fastboot on your mobile and connect it to pc..now your mobile screen should read "fastboot usb"
after this on your pc type "fastboot devices" this should give you your device serial number
after that type "fastboot getvar cid" ..this will give you your cid
ganeshp said:
this wont give you cid ..afaik lot of ppl with different cid will have the same config...
go to fastboot on your mobile and connect it to pc..now your mobile screen should read "fastboot usb"
after this on your pc type "fastboot devices" this should give you your device serial number
after that type "fastboot getvar cid" ..this will give you your cid
Click to expand...
Click to collapse
I have done that before.
"WAITING FOR DEVICE" error
im guessing since my phone cant connect with windows
tom8907 said:
I have done that before.
"WAITING FOR DEVICE" error
im guessing since my phone cant connect with windows
Click to expand...
Click to collapse
as you are bootlooping that is the only way to find your cid
try uninstalling htc sync and istalling them again..if that didnt work then follow the below steps
1.uninstall htc sync...
2.get these drivers universal naked divers
3.install them and try to find you device..it will mostly get detected ..as lot of ppl have success with those drivers
4.if your device was found...then try fastboot command again..
(this is the only other way left)
Does the pc detect your phone? You have a GB radio on ICS H boot. Have you tried flashing an ICS ROM for your h boot version?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Rhiannon224 said:
Does the pc detect your phone? You have a GB radio on ICS H boot. Have you tried flashing an ICS ROM for your h boot version?
Sent from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
Detects when i mount as USB in hboot
Is it possible to just keep downloading random firmware till one is compatible for my device?
tom8907 said:
Detects when i mount as USB in hboot
Click to expand...
Click to collapse
dude ..of course your device wil not be detected by adb ..when you are bootlooping...
the only way is to make fastboot (not adb) recognize your device
to do that ...you need to do what i told you 2 posts earlier
EDIT:
click on the IRC HELP CHANNEL in my sinature...and join it with a nickname..
we talk via IRC (group chat)
tom8907 said:
Is it possible to just keep downloading random firmware till one is compatible for my device?
Click to expand...
Click to collapse
Nooooo don't do that, flashing random firmwares is really risky even if you aren't supercided.
ganeshp said:
this wont give you cid ..afaik lot of ppl with different cid will have the same config...
go to fastboot on your mobile and connect it to pc..now your mobile screen should read "fastboot usb"
after this on your pc type "fastboot devices" this should give you your device serial number
after that type "fastboot getvar cid" ..this will give you your cid
Click to expand...
Click to collapse
I know I just wanted he could get into bootloader and that he was correctly soff
Sent from my sensational sensation 4g
I flashed a random firmwares and I finally got it working.
CIDnum is BM__001 thanks for your help guys
tom8907 said:
I flashed a random firmwares and I finally got it working.
CIDnum is BM__001 thanks for your help guys
Click to expand...
Click to collapse
Glad you got it.. But if you first found the cid.. That would have be pretty easy for you
Sent from my HTC Sensation XE with Beats Audio using xda premium
Finding out cid on HTC Sensation
I had the problems others were reporting - with fastboot not finding any devices and adb just saying 'waiting for device'. The solution for me was to run the commands as root (using sudo on Ubuntu Linux). So I found out my cid with the following steps:
1. Downloaded and unzipped the fastboot and adb programs for Linux from the download 'ADB-Linux.zip' at http://forum.xda-developers.com/showthread.php?t=1459767
2. Booted the phone into the bootloader (by holding the volume down key while turning it on). I had to take out the SD card for this as it was causing some program to automatically load.
3. Selected FASTBOOT on the bootloader.
4. Plugged in the USB cable to my computer. The red 'FASTBOOT' on the phone screen turned to 'FASTBOOT USB'.
5. Issued the following commands in Linux:
Code:
sudo ./fastboot devices
sudo ./fastboot getvar cid
Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
There is not compatible RUU for my one s so heres the steps I'm going to do ....
1) SuperCID My Phone Using This Tutorial
http://androidforums.com/one-s-all-things-root/690970-guide-supercid.html
2) Then Proceed With S-OFF using this tutorial
http://m.youtube.com/watch?v=fTp5uwURKdg
3) Relock Bootloader Using Hasoon2000's All in one toolkit and flash stock recovery (I Need Stock Recovery Image For Htc one s S4 Processor) I Will use this tutorial for steps 3/4
http://m.youtube.com/watch?v=SZuAjz4PIjU
4) Run The RUU (will I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ?)
I Also Need A RUU Which Is On JellyBean Not ICS
5)Unlock Bootloader and Root
Please can ou Anwser These Questions Please <3
ill I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ? I am currently branded to three uk
And can someone link me to stock recovery Image for htc one s S4 Processor
Is There Any JellyBean RUU if So Please Link me to them and tell me if I can use them after I have done SuperCID and s off
And let me know if there any problems in my method I am going to use
Thanks One S Community
Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.
rootrider said:
Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.
Click to expand...
Click to collapse
What should I change my CID to and will I be unbranded ? And can I use the ruu you provided the latest one .and I don't understand what you mean with the OTA Updates. I'm branded to three UK and for 8. Change T-MOB010 to 11111111 and save the file as mmcblk0p4MOD. Would I just find H3G and change it to 11111111
You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app
Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
k1llacanon said:
You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.
I'm going to run the ruu you provided me with will I have any problems with that and what should I change my CID To? Also I'm going to flash stock recovery and lock bootloader so there no probs
rootrider said:
Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.
Click to expand...
Click to collapse
Sorry for being a pain it's just I don't want to brick my phone and could you explain this as I don't understand it
view plaincopy to clipboardprint?
adb pull /sdcard/mmcblk0p4
and hit enter.
NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for offset 00000210 or 00000214 and you should see "T-MOB010" with your IMEI number after it.
NOTE: "T-MOB010" is the T-Mobile US version, depending on your carrier this will change, but it will still precede your IMEI. See the link at the end of this post for a list of other CID's.
MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type
view plaincopy to clipboardprint?
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
Shall I note the file size so if it. Example.txt(4642kb). I would note the file size and I would just change my CID to HTC__001 ?
And don't I need to get the fast boot files and softbin3 and stuff but the site doesn't provide me with anything could you link me to them ? I have literally no clue
And in HxD. editor will mine look like this http://dl.xda-developers.com/attach...3a77c716b8/51864687/1/0/8/2/7/9/0/hexedit.jpg
Wouldn't I change my CID To H3G__001 but I want to be unbranded
For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
ryanshew said:
For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple
Zaman-The-Man said:
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple
Click to expand...
Click to collapse
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or this link)
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps
usaff22 said:
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps
Click to expand...
Click to collapse
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS
Zaman-The-Man said:
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS
Click to expand...
Click to collapse
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)
usaff22 said:
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)
Click to expand...
Click to collapse
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?
Zaman-The-Man said:
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?
Click to expand...
Click to collapse
you shouldn't need to
usaff22 said:
you shouldn't need to
Click to expand...
Click to collapse
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks
Zaman-The-Man said:
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks
Click to expand...
Click to collapse
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2
usaff22 said:
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Alright so
1) Do SuperCID : 11111111
2) S - OFF
3 Do ' fastboot oem writecid HTC__001 '
4) Flash Stock Recovery
5) Run RUU
looks like I'm sorted
But can I ask what shall If my device doesn't match this PJ4010000.zip ?
You can forget step 4. It's not needed with S-off.
Verstuurd van mijn HTC One S met Tapatalk
Zaman-The-Man said:
Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Click to expand...
Click to collapse
Hi, I basically did the same thing as the OP. Deleted my backups by accident by choosing Factory Reset instead of Recovery. I think I am in an even worse position as I thought I had the right RUU as one point and needed to relock the bootloader. My bootloader screen looks like this at the moment.
------------------------------
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Can anyone tell me if this is a lost cause? Thanks.
This is the RUU I used -
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip.
Does anyone know if this is definitely the wrong one?
To all: Guys, no need to use S-Off for RUU. I DON'T KNOW WHO THE F*** CREATED THE PROCESS OF S-OFFING FOR RUUs AS WHEN I RESTORE STOCK LAST YEAR, IT WAS A SIMPLE BOOTLOADER RELOCK, AND RUU WE GO. IF WE S-OFFED, WE S-ON USING ONE-TOUCH STUFF.
To folaxstar: Well, you got as far as him. However, you got the COMPLETELY WRONG RUU. Technically, IT'S NOT AN RUU AT ALL. It is a Android 4.1 Sense 4.5/+ update for European unlocked HTC One S.
Do a "fastboot getvar cid" without the quotes (of course). You should get a CID that looks like the following: T-MOB010(T-Mobile US, as an example, it might not match what you got). Someone could determine the correct RUU.
I have to request for an RUU which is missing. Who can be approached in this regard?
Please, search before making questions. This has been asked thousands times.
link
nor-ric said:
Please, search before making questions. This has been asked thousands times.
link
Click to expand...
Click to collapse
Sorry for that but I think My question is incomplete.
The RUU is missing for JellyBean BM_001 (Bell Mobility). It has only got OTA and no RUU. I direly need it.
RUU VILLE o2_001 update problem
Current software (ICS 2.38.206.2) My problem is that after downloading the phone indicated JB (3.16.401.8) update software, I get the following error message:
Changing system version.
We determined that your phone is running a modified version. We can not update your phone so restore it to the original version for your protection.
Can you help me?
To my knowledge it was not modified by the device.
I'm waiting for their response.
Best regards.
eperjesi76 said:
Current software (ICS 2.38.206.2) My problem is that after downloading the phone indicated JB (3.16.401.8) update software, I get the following error message:
Changing system version.
We determined that your phone is running a modified version. We can not update your phone so restore it to the original version for your protection.
Can you help me?
To my knowledge it was not modified by the device.
I'm waiting for their response.
Best regards.
Click to expand...
Click to collapse
Well based on my reading here, I can say the following can be the reasons:
- Unlocked bootloader
- Phone Rooted
- Any of the bloatware removed/changed in the phone which came pre-installed.
khan.orak said:
Well based on my reading here, I can say the following can be the reasons:
- Unlocked bootloader
- Phone Rooted
- Any of the bloatware removed/changed in the phone which came pre-installed.
Click to expand...
Click to collapse
Bootloader mode, the display shows:
TAMPERED
LOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
50.02.16-RADIO-1.08es
OPEN DSP v29.1.0.45.0622
root nothing.
It find out something?
According to the CID number cidgetter HTC_032 but O2_001 is mentioned below.
The phone O2 and English, but independent.
Well?
eperjesi76 said:
Bootloader mode, the display shows:
TAMPERED
LOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
50.02.16-RADIO-1.08es
OPEN DSP v29.1.0.45.0622
It find out something?
According to the CID number cidgetter HTC_032 but O2_001 is mentioned below.
The phone O2 and English, but independent.
Well?
Click to expand...
Click to collapse
So it says tampered. That's why it isn't updating OTA.
It means either you have installed a custom recovery or you have rooted the phone.
The CID. well I'm not quite sure about that. I have little expertise in that area.
Where is O2_001 mentioned?
also depatib
khan.orak said:
So it says tampered. That's why it isn't updating OTA.
It means either you have installed a custom recovery or you have rooted the phone.
The CID. well I'm not quite sure about that. I have little expertise in that area.
Where is O2_001 mentioned?
Click to expand...
Click to collapse
top of cidgetter program writes htc_032
the following:
ro.aa.cidlist O2_001
ro.aa.maincid O2_001
ro.aa.project Ville_U_ICS_S
ro.build.fingerprint o2_uk/ville/ville/4.0.4
ro.carrier HTC EastEurope
ro.com HTC_032
ro.cwkey O2 001
etc. ..
eperjesi76 said:
top of cidgetter program writes htc_032
the following:
ro.aa.cidlist O2_001
ro.aa.maincid O2_001
ro.aa.project Ville_U_ICS_S
ro.build.fingerprint o2_uk/ville/ville/4.0.4
ro.carrier HTC EastEurope
ro.com HTC_032
ro.cwkey O2 001
etc. ..
Click to expand...
Click to collapse
No it's just the one at top marked RED. and it must be O2_001. So you have this CID. Get an RUU for this one.
khan.orak said:
No it's just the one at top marked RED. and it must be O2_001. So you have this CID. Get an RUU for this one.
Click to expand...
Click to collapse
Many RUU was tried, but each error (bootstrap error 140, 159 image error 155 unknown error ...) refers.
I tried EUREPO Cid_032 ruins but also not good.
The O2 ruins region code is not good.
eperjesi76 said:
Many RUU was tried, but each error (bootstrap error 140, 159 image error 155 unknown error ...) refers.
I tried EUREPO Cid_032 ruins but also not good.
The O2 ruins region code is not good.
Click to expand...
Click to collapse
well I am PMing you with a link. Try to follow that guide. and use the O2 RUU not any other.
khan.orak said:
well I am PMing you with a link. Try to follow that guide. and use the O2 RUU not any other.
Click to expand...
Click to collapse
I look forward
---------- Post added at 04:59 PM ---------- Previous post was at 04:26 PM ----------
eperjesi76 said:
I look forward
Click to expand...
Click to collapse
Unfortunately, I can not translate clearly.
The SDK is 500MB and windows command line I do not understand where you are
khan.orak said:
well I am PMing you with a link. Try to follow that guide. and use the O2 RUU not any other.
Click to expand...
Click to collapse
Sorry simply can not do anything.
The fastboot program does nothing, has no effect on the phone.
eperjesi76 said:
Sorry simply can not do anything.
The fastboot program does nothing, has no effect on the phone.
Click to expand...
Click to collapse
This is the method. You may want to find other guides on how to flash stock ROM. ADB and FastBoot are necessary and nothing is possible without it.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
This is the method. You may want to find other guides on how to flash stock ROM. ADB and FastBoot are necessary and nothing is possible without it.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I do not get the phone to fastboot USB connection is ok.
with plug.
The machine is not doing anything with the phone.
eperjesi76 said:
I do not get the phone to fastboot USB connection is ok.
with plug.
The machine is not doing anything with the phone.
Click to expand...
Click to collapse
You can also fastboot by All in one tool of Hasoon.
Oprn the tool, connect the phone with USB DEBUGGING ON, Press boot to Bootloader in the tool and follow instructions.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
You can also fastboot by All in one tool of Hasoon.
Oprn the tool, connect the phone with USB DEBUGGING ON, Press boot to Bootloader in the tool and follow instructions.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I used TWRP Recovery, I thought it would be easier. More rom.zip tried, but each one says the recovery that:
This operation may install Incompatible software and render your device unusable.
The Cid HTC_032 or O2_001 cause such a problem if you do not have the correct rom?
Watch it.
A cid is always 8 digits as far as i have seen.
Watch here also. http://forum.xda-developers.com/showthread.php?t=2139447
It probaly wont install because of custom recovery/ or incorrect cid
Check cid in fastboot to be sure.
Command: fastboot getvar all
If you unlock again. It might format the device again. (needed to install stock recovery)
Verstuurd van mijn HTC One S met Tapatalk