Ok so I have a one s tmobile us.
I have re-locked and reverted it all back to stock hoping the last update was jelly bean.
And after all that and getting the OTA, well to say the least i was pissed to see it wasnt.
So now here we go.
I did all the reading i could find.
I am going to
UNlock, reroot, and then s-off and super cid to the HTC_001.
then hope that if what i read is right i can do a check software update.
And it will pull down the HTC jelley bean right?
Or what do I need to do?
I'm not worried about warranty since i use family mobile which is walmart t-mobile who dont offer me a warranty any since i brought my own phone.
Also question 2 is will I have any radio or wifi issues by doing any of this presuming I read right and all I have to do is the 4 steps i mentioned above.
Thank you for any input on the question.
I will gladly donate to you for some help in getting it done.
I don't use wifi calling so i dont care about that feature and i live here in the us.
Thank you again.
Tim
Unlock the bootloader and then reroot in the exact same way that you did previously. Then you will need to SuperCID. This involves pulling a file called mmcblk0p4, hex editing partition 210's 5th to 12th characters to HTC__001. Do the following in cmd:
adb shell
su
dd if=dev/block/mmcblk0p4 of=/sdcard
exit
adb pull /sdcard/mmcblk0p4
Look in your adb folder and find the file. Hex edit it with the above instructions. If your CID is not where I originally said it was, then just look for T-MOB010 and overwrite it. Then you need to save the file with MOD at the end, to make sure that you can revert if it goes tits up. Make sure the file is the exact same size as the original. Then you need to tell the phone that the modded file is the new one. Push the modded file onto the SD Card through ADB. Then type:
adb push mmcblk0p4MOD/sdcard
adb shell
su
dd if=/sdcard/mmclbk0p4MOD of=/dev/block/mmcblk0p4
exit
adb reboot bootloader
When rebooted, type:
fastboot oem readcid
You should get cmd telling you that it is HTC__001. Successful. If not, just repeat the process (although, if you **** it up, you probably will have a brick)
You do not need to S-Off to get the OTA update. S-Off has no impact on OTA whatsoever. If you really want to S-Off, then Google "FacePalm S-Off HTC One S"
Just reboot your phone, go into settings, about phone, software updates, check now. The 4.1.1 OTA should be there.
Sent from my One S using xda premium
Thank you im doing it as we speak. Only reason I was going to S-off is when i try to do it using the one click it said you need s-off so im trying your way as I type.
dd if=dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ # dd if=dev/block/mmcblk0p4 of=/sdcard
dd if=dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ #
Sorry, you have to put another forward slash at the end of the file location, should have added that, sorry
Sent from my One S using xda premium
Help!!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tim>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard
dd if=/dev/block/mmcblk0p4 of=/sdcard
/sdcard: cannot open for write: Is a directory
1|[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/
dd if=/dev/block/mmcblk0p4 of=/sdcard/
/sdcard/: cannot open for write: Is a directory
1|[email protected]:/ #
I got it but heres the weird thing my cid reads as HTC_0010? did I need to put 1 under score or 2 underscores for the cid? HTC_001 or is it HTC__001
dd if=/dev/block/mmcblk0p4/ of=/sdcard/
Try that. If that doesn't work, put mmcblk0p4 on the end of sdcard.
Sent from my One S using xda premium
Ok so
HTC__001
it has to be 8 characters its 2 underscores. seperating the HTC and the 001
Ok so heres what i did,
I unlocked again using the onclick newest one.
Then using One click again I changed recovery to the TWRP for S4 of course.
Then finished rooting by install all su binaries.
Changed cid so it now shows HTC__001.
But when i went to the software updates button just now it didnt pull the JB 4.1.1
Grrrrr.
Do i need to change the rom to a different rom?
im on 2.35.531.12 710RD factory tmobile rom.
Do i need to change something else to get my HTC JB 4.1.1 whatever it is?
Try running at HTC__001 RUU. You'll have to relock beforehand though.
Sent from my One S using xda premium
Shoot wouldnt know where to find the us htc__001 ruu do you?
If you Google HTC One S RUUs you should get two or three pages that offer them
Sent from my One S using xda premium
i just don't know which one to use for me . I'm on tmobile network and i am in the us can you possbly point me in the right direction? also you have paypal?
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
So i dont know if this the newest one and if i will have radio or wifi issues with it...
Hey thanks a lot. Your post helped me as well... Thank you.
Sent from my One S using xda premium
It is the newest one (JB is a hint if you look through the name). And yes, there are radio issues. A few people (including me) have got issues with connecting to 3G or HSPDA/HSPA. It will upload data fine but does not download. You have to connect to GPRS, EDGE or HSPDA+/HSPA+.
Sent from my One S using xda premium
Kyle thanks man,
So after all is said and done.
I did do S-off and i dont regret it as I am hboot 1.4
Anyway I changed my cid too 11111111 but then when i was eading and reading and reading and reading i saw that using 11111111 is a guaranteed BRICK!!
So I used the HTC__001 and still had no luck to get the ruu to run. Ill post the ruu log file here but more or less it is *****ing about signature.
If im not mistaken, If i was able to get it to install i can always flash my radio thus fixing any wifi issues.
I did get the trickdroids newest 9.0 to load and then flashed the 9.1 update
Then i flashed the wifi partitions with no issues.
But im curious of what cid you have and where you live that you were able to get that ruu to work for you?
I love s-off though now i can flash any radio, any hboot and so on.
As a side note before the wifi partitions flash wifi would not work kept getting authentication erro.
After connects immidiately, has better range then my stock tmous 2.35.12 whcih was the newest with all updates.
And i get a full 24mbit steady on heavy downloads.
I am curiously wanting to see how the wwe would run but HTC__001 keeps giving bad sgnature error.
Tim2246 said:
But im curious of what cid you have and where you live that you were able to get that ruu to work for you?
Click to expand...
Click to collapse
Maybe this is the answer to your problem
( running latest wwe ruu on your tmobus phone)
http://forum.xda-developers.com/showthread.php?p=39724350
Sent from my VILLE using xda app-developers app
Related
If you want to check if your phone has a SuperCID but don't have access to a computer to run the fastboot commands you can do so from your phone with the following procedure.
Verifying SuperCID
I got the information for this from the HTC Vision wiki entry:- http://forum.xda-developers.com/wiki/HTC_Vision
I'm sure there is information about gfree in another post but I can't find it to credit anyone. If you know more about it let me know and I'll put the credits in here.
Ok, to verify that SuperCID was applied download the gfree_verfiy.zip file attached, extract and then use a root file explorer (e.g. ES File Explorer) to move the file to /data/local/tmp. When the file has been moved amend it's permissions to:-
User r/w/e
Group r/w
Other r/w
After you do this open Terminal and type the following:-
Code:
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
You should get the following returned:-
Code:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
If it says @CID: 11111111 then you have set SuperCID successfully.
When you are finished start the interface layer again by typing:-
Code:
start ril-daemon
Didn't work for me.
CID Getter still says mine is TELST001
sromer said:
Didn't work for me.
CID Getter still says mine is TELST001
Click to expand...
Click to collapse
I'm not sure, but I would asume the CID Getter app would just get the CID of the current ROM you are using (the same as typing 'getprop ro.cid' into Terminal). The CID of your ROM and the CID of your phone are not the same. You need to use the method above to get the CID of your phone or alternatively you can use the fastboot commands from an adb connection.
waltsalt said:
I'm not sure, but I would asume the CID Getter app would just get the CID of the current ROM you are using (the same as typing 'getprop ro.cid' into Terminal). The CID of your ROM and the CID of your phone are not the same. You need to use the method above to get the CID of your phone or alternatively you can use the fastboot commands from an adb connection.
Click to expand...
Click to collapse
I followed all the instructions, but after i enter
Code:
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
i get
Code:
gfree verify_cid returned:
@CID: TELST001
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
So it hasn't changed like i should have.
I have no idea why it isn't working.
@sromer - I see, I'm at work at the minute but when I get home I'll run through things on my phone again to check if the attached file, etc. are all doing as they should. The original post is here - http://forum.xda-developers.com/showthread.php?t=1192630 - and this has a link to the file hosted on Multiupload. You could try working through the instructions there. If you do, let me know how you get on.
If it has worked for anybody else can you let me know?
waltsalt said:
@sromer - I see, I'm at work at the minute but when I get home I'll run through things on my phone again to check if the attached file, etc. are all doing as they should. The original post is here - http://forum.xda-developers.com/showthread.php?t=1192630 - and this has a link to the file hosted on Multiupload. You could try working through the instructions there. If you do, let me know how you get on.
If it has worked for anybody else can you let me know?
Click to expand...
Click to collapse
I just tried the one in that thread too and i get the same result.
It says it's worked but my CID stays the same.
Might just have to wait until tomorrow and try it on my pc
I have a really dumb question, but im pretty new to the Sensation, but not android....
Since this is the general section and its related to this thread, ill ask it here.
Why do I need SuperCID and what does it do? Does it have anything to do with flashing ICS firmware or roms? Im still on 2.3 roms as i have not figured out if I need to flash firmware or Hboot (dont even know the difference) to go from 2.3 roms to ICS roms....
SuperCID allows you to flash ROMs from any region e.g. a T-Mobile ROM from the US can be flashed onto a European handset. Without SuperCID this is not possible.
Sent from my HTC Sensation using XDA App
Aren't you supossed to do this while in fastboot?
Sent from my HTC Sensation XE with Beats Audio using XDA App
kboater said:
Why do I need SuperCID and what does it do? Does it have anything to do with flashing ICS firmware or roms? Im still on 2.3 roms as i have not figured out if I need to flash firmware or Hboot (dont even know the difference) to go from 2.3 roms to ICS roms....
Click to expand...
Click to collapse
Yes you will have to perform one of the SuperCID procedures ( there are several ways to do it ) before you can flash the ICS firmware.
OK, I put my phone back to the HTC__001 CID and reworked through these steps. Setting SuperCID from the phone isn't working for me either. I thought it had worked for me previously but I must have done the fastboot SuperCID procedure back in the days when I unlocked the bootloader so then when I checked if this procedure had worked it looked like it had!
I shall update this post to that effect.
The instructions for verifying the CID are still applicable and definitely work. It means you can check if you have SuperCID on your phone before flashing the new ICS firmware (for those that don't have easy access to a computer).
hey before i go ahead i'd like to know if i need to do a nandroid backup? i tried it once but it said gfree_verify not found ? does that mean after setting the perms i need to reboot and then go ahead whit terminal? lol any risks doing the following? sorry new phone kinda scared
Anyone ?
Sent from my HTC-Z710a using xda premium
The process itself is not that risky, BUT given you've tried once with no joy I'd say better safe than sorry. If all goes to plan you're good, but you never know what you might do accidentally when things start to deviate from the script
More experienced/confident operators might disagree but I tend to err very much on the side of caution. You only sacrifice a bit of time and some SD card space and it could save you much more time and stress later on.
"Better to be looking at it than looking for it!"
goatee84 said:
The process itself is not that risky, BUT given you've tried once with no joy I'd say better safe than sorry. If all goes to plan you're good, but you never know what you might do accidentally when things start to deviate from the script
More experienced/confident operators might disagree but I tend to err very much on the side of caution. You only sacrifice a bit of time and some SD card space and it could save you much more time and stress later on.
"Better to be looking at it than looking for it!"
Click to expand...
Click to collapse
Yeah so im about to do a backup whit cwm but idk i hear alot that cmw isn't stable and things like that is that true ?
Sent from my HTC-Z710a using xda premium
For the time I used CWM I had no problems with it, I suppose everyone's opinion of something is based on their personal experience with it.
Having said that I've been using 4ext recovery for a good while now and can highly recommend it, it has a great touch interface and I've had zero problems with it.
There are also plenty of apps available that allow you to do nandroid backups and the like from within the app, you set up what you want to do and the app does the rest (reboot into recovery, perform backup, reboot phone for example), for me I feel like it adds another element of risk so I prefer to do it manually from recovery. The attraction I suppose is the easier interface of a purpose built app but with something like 4ext you have a perfectly good touch interface to use anyway and provided you know what you're doing you should be fine
http://forum.xda-developers.com/showthread.php?t=1377759 if you want to have a look for yourself and see if you like it.
goatee84 said:
For the time I used CWM I had no problems with it, I suppose everyone's opinion of something is based on their personal experience with it.
Having said that I've been using 4ext recovery for a good while now and can highly recommend it, it has a great touch interface and I've had zero problems with it.
There are also plenty of apps available that allow you to do nandroid backups and the like from within the app, you set up what you want to do and the app does the rest (reboot into recovery, perform backup, reboot phone for example), for me I feel like it adds another element of risk so I prefer to do it manually from recovery. The attraction I suppose is the easier interface of a purpose built app but with something like 4ext you have a perfectly good touch interface to use anyway and provided you know what you're doing you should be fine
http://forum.xda-developers.com/showthread.php?t=1377759 if you want to have a look for yourself and see if you like it.
Click to expand...
Click to collapse
Thanks alot for the info and having older version of cmw shouldn't make issues whit flashing roms ?
Sent from my HTC-Z710a using xda premium
To be honest, I'm not sure with CWM, maybe someone with more experience with it can answer that.
I do remember someone using 4ext had an issue due to somehow falling back to a beta version during install and the fix ended up being to just install the newest version and all was well. It's somewhere on xda if you have a search (sorry don't have time to have a look for you) I actually came across the problem myself but had already read that thread and caught it before it caused any issues for me.
Again, I can't answer that for CWM but it might be something to be aware of?
Sent from my HTC Sensation Z710 using XDA
goatee84 said:
To be honest, I'm not sure with CWM, maybe someone with more experience with it can answer that.
I do remember someone using 4ext had an issue due to somehow falling back to a beta version during install and the fix ended up being to just install the newest version and all was well. It's somewhere on xda if you have a search (sorry don't have time to have a look for you) I actually came across the problem myself but had already read that thread and caught it before it caused any issues for me.
Again, I can't answer that for CWM but it might be something to be aware of?
Sent from my HTC Sensation Z710 using XDA
Click to expand...
Click to collapse
No worries thanks alot for the help mate !
Sent from my HTC-Z710a using xda premium
Hi, I realize I will get a lot of flame for this, but how do I know if my AT&T One X is S-off?
See, I'm trying to flash this custom boot screen from here (http://forum.xda-developers.com/showthread.php?t=2173665) and the requirements say I must be S-off and have an unlocked bootloader.
I know for sure my bootloader is unlocked (via the HTCDev method). I also read some places that S-off means your bootload is locked? So kind of confused here.
Thanks very much XDA geniuses!!!!
toughtrasher said:
Hi, I realize I will get a lot of flame for this, but how do I know if my AT&T One X is S-off?
See, I'm trying to flash this custom boot screen from here (http://forum.xda-developers.com/showthread.php?t=2173665) and the requirements say I must be S-off and have an unlocked bootloader.
I know for sure my bootloader is unlocked (via the HTCDev method). I also read some places that S-off means your bootload is locked? So kind of confused here.
Thanks very much XDA geniuses!!!!
Click to expand...
Click to collapse
Reboot into boot loader. It'll either say S-On or S-Off.
Okay, I've done that and it says I'm S-On.
What are the benefits of S-Off and any cons? Thanks given
System write protection is turned off. Reduces chance of bricking with ruu and allows you to change things like hboot and splash screen without the need for them to be signed. It's good to have if you're knowledgeable enough to read and follow instructions.
Sent from my One X using xda app-developers app
toughtrasher said:
Okay, I've done that and it says I'm S-On.
What are the benefits of S-Off and any cons? Thanks given
Click to expand...
Click to collapse
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Thug_4_Life said:
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
exad said:
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
Click to expand...
Click to collapse
Lol I remember what happened when I flashed Sense5 rom specifically for Evo 4g lte.
Sent from my HTC One X using xda app-developers app
S-off if you need it... If not play it safe.
Sent from my HTC One X using xda app-developers app
Thug_4_Life said:
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
Click to expand...
Click to collapse
For some reason, these two just seem to coincide the hell out of each other someone explain
T4L, I've followed the steps on that thread you pointed me to, but I'm stuck on step 7, inputting this to the command prompt:
adb shell chmod 744 /data/local/tmp/soffbin3
See, I read one of the posts in there that says I can use the files from Hassoon's all in one tool and just point the command prompt there, however when I type in "adb shell chmod 744" itdoesn't do anything. Then when I type in anything else after "adb shell chmod 744" it says error: cannot find device.
What do?
toughtrasher said:
For some reason, these two just seem to coincide the hell out of each other someone explain
T4L, I've followed the steps on that thread you pointed me to, but I'm stuck on step 7, inputting this to the command prompt:
adb shell chmod 744 /data/local/tmp/soffbin3
See, I read one of the posts in there that says I can use the files from Hassoon's all in one tool and just point the command prompt there, however when I type in "adb shell chmod 744" itdoesn't do anything. Then when I type in anything else after "adb shell chmod 744" it says error: cannot find device.
What do?
Click to expand...
Click to collapse
What rom are you using? a root access request pops up on your phone screen after, did you grant root?
exad said:
What rom are you using? a root access request pops up on your phone screen after, did you grant root?
Click to expand...
Click to collapse
I am using CleanROM 6 R2. It didn't pop up anything after step 7
toughtrasher said:
I am using CleanROM 6 R2. It didn't pop up anything after step 7
Click to expand...
Click to collapse
pastebin your cmd please
Make sure you're plugged into a USB 2 port, not USB 3. Anytime I get that error, it's cause I forgot to plug it in the right one.
Sent from my One X using xda app-developers app
Thanks for all your responses, guys! Really appreciate it.
I've succesfully got s-off thanks a lot to beaups! Very great person.
Now for some theming...
Hello,
This might be a repetitive question but I couldn't find an exact answer.
Through the research I've done, so far I know that I should S-off my device first and then update my RUU to get android 4.3 on my device.
I am S-on and on hboot 1.11. Using clean rom right now. I'm a noob in this and have no idea abt details.
I bricked my phone once and don't want to do it again.
So, For S-off should I follow facepalm method and then should I update my RUU?? The cingular one??
Also, if anyone has a video on s-off it would be great. I can follow it easily.
Thanks. Any help will be appreciated.
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
timmaaa said:
You have it right. Get s-off first, then run the RUU. The facepalm method is the only method for s-off and you don't really need s video, you just need to follow the instructions, it's very easy. If you're with at&t then the Cingular RUU is the right one for you. After the RUU you'll need to flash TWRP recovery again.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
saagar_mistry said:
Thanks for the quick reply. I'm with Rogers. Live in canada. I guess they're both the same right??
And after I run RUU, is my phone still going to be rooted or do I have to do all that again?
Also, I found this link online to run RUU, http://www.youtube.com/watch?v=SZuAjz4PIjU
Can you please check and tell me, if I should do the same or not? Go to fastboot and command prompt stuff??
One more thing. S-off says I need superCID? I have no idea what that is. How do I check for that?
Sorry for all the questions but I can't lose the phone again.
Thanks again.
Click to expand...
Click to collapse
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
For superCID, first go into bootloader and run.
fastboot oem readcid.
Tell us what it says.
Sent from my HTC Evita with XDA Premium 4
RollTribe said:
To run the RUU, all you need to do is plug in you s-off'd phone and run it. No additional steps are required.
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
saagar_mistry said:
I tried the S-off method but got error 99 instead of error 92.
I think I don't have supercid. Any idea how I should install that!???
Click to expand...
Click to collapse
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
RollTribe said:
Try this.
fastboot oem writecid 11111111
Sent from my HTC Evita with XDA Premium 4
Click to expand...
Click to collapse
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
saagar_mistry said:
It shows read failed. too many links.
Also shows no device attached. My usb is attached. I'm in bootloader and it shows fastboot usb.
Still shows no device attached.
Click to expand...
Click to collapse
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
exad said:
Super CID. Use ADB.
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
If you don't follow procedure or try things without knowing the current state of your phone, you're on a fast track to a second brick. I am only warning you because you seem to care whether you brick or not.
Click to expand...
Click to collapse
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
saagar_mistry said:
Thanks for the reply!
And yes I don't want to brick it again. I'll leave the phone as it is. I don't think I should proceed with S-off. I downloaded the ADB bundle stuff but gonna stop here. lol.
Anyways. Thanks a lot for help, all of you guys!
Click to expand...
Click to collapse
S-Off isn't so difficult, but at least you know where to draw a clear line on when to stop messing with the phone, unfortunately a lot of people don't really know when they are in over their heads.
As long as you can read and follow directions you will be ok. I suggest reading material on what you are doing to your phone, and if what you're doing is beneficial for it. If you read and don't understand then wait until you do so you don't brick your phone.
Sent from my HTC One X using xda app-developers app
hi guys, im not new to this, and i have a good understanding of adb and fastboot. i have just purchased a htc one xl (telstra) im running Hboot 2.15 and have unlocked bootloader via htc dev, installed TWRP ver; 2.6.0.0, rooted via flashing superSU and am currently running stock android ver 4.2.2 htc sense 5.0. i sim unlocked it so i could run my vodafone sim, and radio is working fine but i think the telstra RUU isnt allowing the sims internet conectis-on, therefore i am deciding to flash another rom. i first tried flashing pacman rom unsuccessfully but have yet to flash the boot.img as i havent got S-OFF and figure it wont allow writing to that partition yet, i have had alot of problems rewriting the CID for superCID, have tried many methods including xfactor and manually via fastboot and have been unsucessfull thus far, i understand that its not possible to downgrade Hboot unless S-off is achieved, alas facepalm is not possible unless superCID is achieved, and i cannot rewrite the CID manually or using any scripts i have found, is my Hboot version the problem or is there something im missing here?
help would be much appreciated
Have you tried the hex edit method?
Sent from my Evita
Yeah it returns with an error in adb, system mounted read only, and its deffinatly rooted so I'm not sure how to make system readwrite
Sent from my Wildfire S A510e using xda app-developers app
It would seem there s no sure fire way around this. Unless someone can help me figure out the read only issue in adb using the hex edit method
Sent from my Wildfire S A510e using xda app-developers app
hex edit progress
ok so i fixed the problem by uninstalling htcsync and re installing adb and fastboot via sdk tools, i got the file pulled from my phone and hex edited it, from cid; TELST001 to cid; 11111111 and pushed the file back onto my phone as per instructions, yet when i reboot into bootloader and do fastboot oem readcid it still comes back TELST001. somehow the phone knows what is happening and is changing the hex back to original form..??
ok scratch that, it actually never pulled the file from my phone, that was a file leftover from some script that didnt work, it had a cid of telus001 and my cid reads telst001 so i know that wasnt my file, the adb shell is able to read my phone but not ble to take the mmcblk0p4 file, so when i enter the command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 i get 2.0 records in 2.0 records out 1024 bytes transferred at <40960> bytes. so im guessing it was successful, yet when i check my sd root the file is nowhere to be seen!? where am i going wrong here
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
argh
O..K so i rebooted the one xl ad the file was there, i copied to desktop, hex edited, and did dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 to push the file back. read as successful in adb, so i did reboot fastboot and fastboot oem readcid, CID READS TELST001 STILL i must be retarded or something
timmaaa said:
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
Click to expand...
Click to collapse
ok thanks man, ill give it a go now
st3wy said:
ok thanks man, ill give it a go now
Click to expand...
Click to collapse
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
st3wy said:
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
Click to expand...
Click to collapse
i even tried doing echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and still get INFOcid: TELST001
is it possible that my cid is stored somewhere other than mmcblk0p4 or mmcblk0p5??
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
timmaaa said:
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
Click to expand...
Click to collapse
sounds about right, i did read about this. so im guessing because i used temp root to spoof cid and unlock bootloader using the unlock code from that process, that there is no way to 'officially' relock the bootloader, and start the whole process again using a different method, say for instance using adb.. and thus getting bootlocker unlocked without spoofed cid and temp root possibly resulting in the ability to obtain supercid and full root? i have got supersu flashed through recovery.. but yeah obviously having serious issues with supercid atm.. thanks so much for your help this far man came a long way this arvo, just cant see the light at the ed of the tunnel... its like if i was able to flash Hboot i may be able to get around, but that requires s-off, which reuires super cid, which requires different Hboot lol
you wouldnt happen to know anyone else that might be able to brainstorm on this would you? although from looking at the threads youve made, it seems your possibly THE most educated person on this matter... idk might just have to wait for a dev to look into this and find a loophole. im not that good unfortunately. again, thanks for your help man. if you do get any ideas dont hesitate to post em up on this thread. cheers.
I'm definitely not the most educated person in this kinda stuff, I just read a lot on here and remember the ins and outs of this device. Finding a loophole around this is something that the HTC experts would have to work on, people like beaups, jcase, those kinda guys. Like I said though I'm not even sure if what I said is what's stopping you, I could be completely wrong.
Sent from my Evita
well, ive had one thaught that might be a stupid one but possibly one of the only things i am yet to try.. if i go through with the s-off and see if it works, although my phone is reading cid it may actually have supercid because like i say, its been successful in adb just hasnt returned a supercid through the fastboot commands, i guess the only question is will i brick my device if i follow through with s-off when i dont have supercid or will it just fail and all will be gravy
is there anyway to get them in on this thread so they know where im up to, or would i have to PM them exclusively and explain all over again
btw i think your right, system is read only. thats why the pushes arent working, even though they say they are in adb, either that or the phones cid and the RUU's cid are different and fastboot oem readcid is reading softwares cid and not the phones cid?
either way im going to drink a beer and go outside for a while, thanks again timmaaa, i didnt expect anyone to reply to this thread for a good while. like i said if u happen to have contact with the devs or anyone else that might be able to help, id be stoked. cheers bro and peace out!
You can try SuperCID but it just won't work. You can try contacting them and pointing them to this thread, but I think they're pretty busy guys so I don't know if they'll be able to help. The CID that shows up when using the fastboot command is definitely the phone CID and not the software CID.
Sent from my Evita
My friend has give me his vzw m8 with a cracked and non working screen (lcd is too, broken, no display whatsoever) to stock up to return.
However, he needs to have s-on. I have just flashed the 0P6BIMG ruu via fastboot. I'm having difficulty understanding how to finish up the phone. From what I can tell from reading, it's still S-OFF after flashing this ruu. What else should i know for returning the phone?
http://forum.xda-developers.com/showthread.php?t=2745257
This may or may not help you lol hopefully it does though.
Sent from my HTC6525LVW using Tapatalk
mfungah said:
My friend has give me his vzw m8 with a cracked and non working screen (lcd is too, broken, no display whatsoever) to stock up to return.
However, he needs to have s-on. I have just flashed the 0P6BIMG ruu via fastboot. I'm having difficulty understanding how to finish up the phone. From what I can tell from reading, it's still S-OFF after flashing this ruu. What else should i know for returning the phone?
Click to expand...
Click to collapse
as suggested in the above post, in the thread it explains, that after you flash the RUU,
You must first RE lock the bootloader
this is done by this method:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recommend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked (if you can still see on the screen?)
Then you may do "fastboot oem writesecureflag 3" to put S-ON
andybones said:
as suggested in the above post, in the thread it explains, that after you flash the RUU,
You must first RE lock the bootloader
this is done by this method:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recommend you copy/paste this)
Click to expand...
Click to collapse
So at the moment I need to figure out how to obtain su, at least shell then. Seeing as I just flashed the ruu and the LCD is completely black/blank, do you have any suggestions?
And thank you very much for the detailed reply step by step.
Also, it's probably helpful to mention that I am still in fastboot mode from flashing the RUU.
mfungah said:
Also, it's probably helpful to mention that I am still in fastboot mode from flashing the RUU.
Click to expand...
Click to collapse
if the RUU took as successful then you should reboot it to the new RUU ROM (should take about 5 mins, since you can't see.. plug cable into computer and once you can access SD-Card you are booted, you should be able to then get an su in a cmd prompt. from what I've read the RUU has supersu icon so it should have root? not positive but doing this will absolutely not hurt, you would only not be able to get SU privs to turn the flag back to S-ON. if you get su, great you should then be good to go.
I don't know but you may even be able to do fastboot devices then echo, BUT do NOT try that yet anyway as I don't know what will happen, if you do it, it's at own risk.. since going back for refurb, i don't really think a brick would matter though.
andybones said:
if the RUU took as successful then you should reboot it to the new RUU ROM (should take about 5 mins, since you can't see.. plug cable into computer and once you can access SD-Card you are booted, you should be able to then get an su in a cmd prompt. from what I've read the RUU has supersu icon so it should have root? not positive but doing this will absolutely not hurt, you would only not be able to get SU privs to turn the flag back to S-ON. if you get su, great you should then be good to go.
I don't know but you may even be able to do fastboot devices then echo, BUT do NOT try that yet anyway as I don't know what will happen, if you do it, it's at own risk.. since going back for refurb, i don't really think a brick would matter though.
Click to expand...
Click to collapse
That's correct andy....The ruu I made does have su. I'm not sure how he would be able to answer the su prompts for adb access though. Maybe hdmi out?
For what it's worth this device is pretty hard to truly brick. I tried once to help brick one and even with bootloader wiped it still went straight to ruu mode.
Sent from my SM-T320 using Tapatalk
I suppose that adb debugging isn't enabled by default, I'm booted up but that's about it. Any specific information that could be helpful or as I'm assuming, theres nothing much i can do except fastboot to S-ON. I mean it is getting sent in, I just really hope it gets accepted.
He got a new device for him all sorted out. I really appreciate your time and help, I did find your step by step very easy to understand.