Hey all. I wanted to get something going here on this. I've been trying all sorts as I'm sure other have.
I've tried pushing a modified mmcblk0p4 to dev/block folder but on closer inspection there's files perhaps controlling that file in platforms and deeper.
I've attached my zip file to flash in recovery for push modified mmcblk0p4 and p4 to the phone.
Please note it doesn't work! It doesn't seem to harm anything so don't worry but it simply doesn't write.
So having said all this. Has anyone got any idea how the files are controlled? Maybe one of the loop files tells the other files what they should be? Or could there be hidden files.
Anyway devs please feel free to have a look at my zip and maybe someone with a bit more knowhow might be able to mod it to function
Link to zip attempt here = http://d-h.st/mkh
Sent from my Tricked out 'One'
Found another file containing CID and also my origional stock software number. mmcblk0p19. It allowed me to change the CID in this file and it stuck. But it has effected nothing currently. Going to look deeper and see what else might be there.
Sent from my Tricked out 'One'
The War Horse said:
Found another file containing CID and also my origional stock software number. mmcblk0p19. It allowed me to change the CID in this file and it stuck. But it has effected nothing currently. Going to look deeper and see what else might be there.
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
awesome! keep us posted
The War Horse said:
Hey all. I wanted to get something going here on this. I've been trying all sorts as I'm sure other have.
I've tried pushing a modified mmcblk0p4 to dev/block folder but on closer inspection there's files perhaps controlling that file in platforms and deeper.
I've attached my zip file to flash in recovery for push modified mmcblk0p4 and p4 to the phone.
Please note it doesn't work! It doesn't seem to harm anything so don't worry but it simply doesn't write.
So having said all this. Has anyone got any idea how the files are controlled? Maybe one of the loop files tells the other files what they should be? Or could there be hidden files.
Anyway devs please feel free to have a look at my zip and maybe someone with a bit more knowhow might be able to mod it to function
Link to zip attempt here = http://d-h.st/mkh
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
Unfortunately I won't be able to help you on this as I'm a bit of a noob :silly:. Just here to express my encouragement for your endeavours as I stand to benefit if you succeed as I am porting ORANG001 which I suspect will be right at the bottom of the pile update wise.
Perhaps some genius will crack the s-off riddle for this device which is hopefully more likely as this is running on qualcom . If I can be of any assistance in testing I would gladly help for what it's worth. Good Luck. :good:
Found more files but still no SuperCID. Wondering if there's some hidden files at work here...hmm
Sent from my Tricked out 'One'
It's already known that the CID partition is write protected, you need to find out how to bypass the protection
Sent from my HTC One using Tapatalk 2
superchilpil said:
It's already known that the CID partition is write protected, you need to find out how to bypass the protection
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
That is right. I have been trying to figure out how to write to that partition but i think im not that smart... I was thinking if anyone tried similar method to Facepalm S-OFF from HOX forums. I bet if we can somehow semi-brick the phone then it would open partitions for writing. JET used the same approach to downgrade HBOOT which is protected in S-ON
igagnidz said:
That is right. I have been trying to figure out how to write to that partition but i think im not that smart... I was thinking if anyone tried similar method to Facepalm S-OFF from HOX forums. I bet if we can somehow semi-brick the phone then it would open partitions for writing. JET used the same approach to downgrade HBOOT which is protected in S-ON
Click to expand...
Click to collapse
Facepalm takes advantage of supercid, so for that to work we would need to figure this out first
The semi brick was caused by flashing an evo lte p4 (extended partition table I believe) and no the HBOOT wasn't write protected so that's how it worked, but the signature was checked so you could only write a hboot from HTC.
So I doubt that would work, if I remember correctly the write protection is brought on early in the boot process, and to disable it you had to do some sort of power cycle without rebooting the phone
Sent from my HTC One using Tapatalk 2
superchilpil said:
Facepalm takes advantage of supercid, so for that to work we would need to figure this out first
The semi brick was caused by flashing an evo lte p4 (extended partition table I believe) and no the HBOOT wasn't write protected so that's how it worked, but the signature was checked so you could only write a hboot from HTC.
So I doubt that would work, if I remember correctly the write protection is brought on early in the boot process, and to disable it you had to do some sort of power cycle without rebooting the phone
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I'll be hunting until I find that file.
Does anyone know the order of boot?
Sent from my Tricked out 'One'
superchilpil said:
Facepalm takes advantage of supercid, so for that to work we would need to figure this out first
The semi brick was caused by flashing an evo lte p4 (extended partition table I believe) and no the HBOOT wasn't write protected so that's how it worked, but the signature was checked so you could only write a hboot from HTC.
So I doubt that would work, if I remember correctly the write protection is brought on early in the boot process, and to disable it you had to do some sort of power cycle without rebooting the phone
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I said that hboot was write protected and to unprotect it they had to semi-brick it using corrupted p4 partition. So YES, hboot is write protected during normal boot cycle, and when they introduced corrupted partition and semi-bricked the device, it disabled write protection on hboot.
Sorry if my english is confusing, its not my first language.
It's power on write protection. It doesn't get any earlier in the boot process than that.
P4/5 are your cid partitions. Anyother references to cid in other partitions are only that, and changing them will not change device cid.
Sent from my HTCONE using Tapatalk 2
18th.abn said:
It's power on write protection. It doesn't get any earlier in the boot process than that.
P4/5 are your cid partitions. Anyother references to cid in other partitions are only that, and changing them will not change device cid.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Man!
There still has to be some way to disable it though.....Must figure this one out!!!
Just had a go at something a bit different.
Managed to write Goldcard.img to mmcblk0 and it seems to have stuck. BUT.....Nothing's changed lol, and I attempted an RUU I knew shouldn't work....and it didn't.....So....I dunno....Anyone got any Ideas?
There is always an exploit. I'm not saying the write protection means it's impossible.
HTC doesn't use gold cards anymore.
Sent from my HTCONE using Tapatalk 2
18th.abn said:
There is always an exploit. I'm not saying the write protection means it's impossible.
HTC doesn't use gold cards anymore.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
No gold cards? Ah man!!
Yeh how can that even be?
Yeh there's gotta be a way. Hopefully some epic dev will already be on their way to finding it!!
I'm going to keep on playing until I either kill my phone and end up claiming on the insurance, I find a way or someone else does lol!
The War Horse said:
No gold cards? Ah man!!
Yeh how can that even be?
Yeh there's gotta be a way. Hopefully some epic dev will already be on their way to finding it!!
I'm going to keep on playing until I either kill my phone and end up claiming on the insurance, I find a way or someone else does lol!
Click to expand...
Click to collapse
If you're not a dev you're way on your way to becoming one, persistence like that is a virtue.
Appreciate your efforts sir.
What about Alpharev and unrEVOked? They were responsible for S-Off on the Sensation and such, i haven't heard anything but they may be looking into it too.
either way, good luck.
dladz said:
If you're not a dev you're way on your way to becoming one, persistence like that is a virtue.
Appreciate your efforts sir.
What about Alpharev and unrEVOked? They were responsible for S-Off on the Sensation and such, i haven't heard anything but they may be looking into it too.
either way, good luck.
Click to expand...
Click to collapse
Cheers. I'm actually loving the phone and for once have only really rooted it etc just because and not really for any gain but I can't help but want to try and help 'crack the nut' as it were....I doubt I will manage it though as I think it seems a bit above my skills but it's all worth a shot.
The War Horse said:
Cheers. I'm actually loving the phone and for once have only really rooted it etc just because and not really for any gain but I can't help but want to try and help 'crack the nut' as it were....I doubt I will manage it though as I think it seems a bit above my skills but it's all worth a shot.
Click to expand...
Click to collapse
Being a dev myself (not android - mostly just web stuff for work), it always seems like things are "above my skills" until I figure it out. Like the above poster said, persistence is all that is needed. We have "bang head here" signs at my office for a reason
The War Horse said:
Cheers. I'm actually loving the phone and for once have only really rooted it etc just because and not really for any gain but I can't help but want to try and help 'crack the nut' as it were....I doubt I will manage it though as I think it seems a bit above my skills but it's all worth a shot.
Click to expand...
Click to collapse
Yea i'm not even trying m8, i'd break something, i keep meaning to get into this dev lark but you need a lot of knowledge and a lot of people don't realise that.
If it were windows then lol, i'm in there but android has always been a bit of a hard nut to crack for me.
I've got some basic knowledge on the OS and the background workings but not nearly enough to make my own rom. One day i'll research it but at the moment with my life i have no time for anything let alone developing.
---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------
scotty2hotty1125 said:
We have "bang head here" signs at my office for a reason
Click to expand...
Click to collapse
I like that
scotty2hotty1125 said:
Being a dev myself (not android - mostly just web stuff for work), it always seems like things are "above my skills" until I figure it out. Like the above poster said, persistence is all that is needed. We have "bang head here" signs at my office for a reason
Click to expand...
Click to collapse
Haha yeh definitely. It's all about trying and trying and sooner or later you suddenly know what's going on....at least with that little bit anyway haha!
dladz said:
Yea i'm not even trying m8, i'd break something, i keep meaning to get into this dev lark but you need a lot of knowledge and a lot of people don't realise that.
If it were windows then lol, i'm in there but android has always been a bit of a hard nut to crack for me.
I've got some basic knowledge on the OS and the background workings but not nearly enough to make my own rom. One day i'll research it but at the moment with my life i have no time for anything let alone developing.
---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------
I like that
Click to expand...
Click to collapse
Yeh I didn't touch anything until I dabbled with a ROM for the DHD. I didn't do much dev work but I took a ROM and then tweaked it a bit. If you google enough you soon figure out how to do the odd bit here and there. Wish I had more programming knowledge but I suppose everyone's gotta start somewhere!
Related
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Taco991 said:
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Click to expand...
Click to collapse
No worries I would be more than happy to provide one after I get home from work
smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Don't know what you are disappointed about. S-OFF stands for security being off. This may sound bad, but from a developer perspective, it's pretty good. If you have true S-OFF like you claim you do, you can flash ROMs, kernels, radios, etc... in a recovery with no issues at all; regardless of what hboot or custom recovery you have. Unlocked means that you can flash custom recoveries and such using fastboot, which is what you want. To sum it up, S-OFF is good; many devs are trying to get S-OFF, but NONE can figure it out. Just be happy about it.
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Closed Source Project said:
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Click to expand...
Click to collapse
Actually I think since he has s-off I think he can make it say whatever he wants.
Once you get the photo up PM me so I can help you out :laugh:
Taco991 said:
Once you get the photo up PM me so I can help you out :laugh:
Click to expand...
Click to collapse
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Where's the S-OFF lol? And yes I think you can do that. It's PD some numbers IMG.zip..
smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Facepalm. You do NOT have S-OFF, What the hell made you think you did. This is normal... Wow. You need to install a custom recovery to flash zips, by the way.
Hey easy on him, he was just mistaken. OP, do you need me to show you how to go back to stock?
smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
You would do better to change thread title...
Hunt3r.j2 said:
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
Click to expand...
Click to collapse
Look at a couple post above urs he doesn't have soff
Sent from my HTC VLE_U using xda premium
Hey everyone,
I am looking to start an unbricking project, to help people that are bricked with QHSUSB_DLOAD message, seeing if the Sensation method will work, just with a One S HBOOT file instead of the Sensation HBOOT one.
So I'd like to ask if anyone knows where I can find the HBOOT.nb0 files starting from 1.06 to 1.13? If you have them, could you please upload any that you may have.
Thanks,
usaff22
Sent from pixels to more pixels
here are some
These are the hboots 1.06, 1.13 and 1.14, extracted them from the 1.53, 1.78 and 2.31 RUUs.
-Jobo
touch of jobo said:
These are the hboots 1.06, 1.13 and 1.14, extracted them from the 1.53, 1.78 and 2.31 RUUs.
-Jobo
Click to expand...
Click to collapse
Thanks. I'll start working on it.
Sent from pixels to more pixels
usaff22 said:
Thanks. I'll start working on it.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Keep us updated
D3LTA said:
Keep us updated
Click to expand...
Click to collapse
No problem.
Sent from pixels to more pixels
Ok, I will be PM'ing people if they wish to try the method and report back to me.
I'm like HTC - I send OTA's out in batches, if something goes wrong, pull the update
Sending out a second batch of PMs
Project discontinued due to lack of interest.
Unfortunately no one replied or even sent a PM back saying they couldn't do it. If anyone wants to try it, fire me a PM and I might be able to do something.
Edit: Why the 1 star rating? This forum amazes me sometimes. I sent many PMs and no one was interested. That's not my fault.
usaff22 said:
Project discontinued due to lack of interest.
Unfortunately no one replied or even sent a PM back saying they couldn't do it. If anyone wants to try it, fire me a PM and I might be able to do something.
Edit: Why the 1 star rating? This forum amazes me sometimes. I sent many PMs and no one was interested. That's not my fault.
Click to expand...
Click to collapse
PM sent , hope this project will continue
What exactly are we testing? Ability to flash HBoot?
Ability to flash HBOOT, ability for the phone to be recognized via USB in EHostDL mode.
Sent from my locked, tampered ville
Hi,
can you please send me an update about whether you could manage to fulfill this project?
I have hard bricked my OneS's hboot image..
and stuck currently w/o getting any response from the phone, not even a charging flash
usaff22 said:
Ok, I will be PM'ing people if they wish to try the method and report back to me.
I'm like HTC - I send OTA's out in batches, if something goes wrong, pull the update
Click to expand...
Click to collapse
g.i. said:
Hi,
can you please send me an update about whether you could manage to fulfill this project?
I have hard bricked my OneS's hboot image..
and stuck currently w/o getting any response from the phone, not even a charging flash
Click to expand...
Click to collapse
http://unlimited.io/qhsusbdload.htm might help ya
thanks, but no. tried it.. its not good for my problem
who wants to help me save my brick? its along the same lines as what the op was looking at. i was in the middle of attempting to downgrade my hboot, my son whacked my laptop with a full bottle of water and caused my laptop to reboot. fortunatley, ive been able to somewhat get my one s back up and running. i need a good p4 (partition 4) from a one s to try. if i can get that, im pretty sure my phone will be back up and running, with a downgraded bootloader. if anyone could dump mmcblk0p4 for me i would be very grateful...
mikeyinid said:
who wants to help me save my brick? its along the same lines as what the op was looking at. i was in the middle of attempting to downgrade my hboot, my son whacked my laptop with a full bottle of water and caused my laptop to reboot. fortunatley, ive been able to somewhat get my one s back up and running. i need a good p4 (partition 4) from a one s to try. if i can get that, im pretty sure my phone will be back up and running, with a downgraded bootloader. if anyone could dump mmcblk0p4 for me i would be very grateful...
Click to expand...
Click to collapse
I've already tried what you're gonna try and it doesn't work. But here is my p4 anyways, I changed some digits from the IMEI so you're gonna have to edit it and put in your own.
https://dl.dropbox.com/s/ibb9cmo4y9j9x86/p4%20-%20Copy.img?dl=1
dc211 said:
I've already tried what you're gonna try and it doesn't work. But here is my p4 anyways, I changed some digits from the IMEI so you're gonna have to edit it and put in your own.
https://dl.dropbox.com/s/ibb9cmo4y9j9x86/p4%20-%20Copy.img?dl=1
Click to expand...
Click to collapse
no problem, thanks. what did you try?
mikeyinid said:
no problem, thanks. what did you try?
Click to expand...
Click to collapse
Can't quite recall off the top of my head, I do remember trying to get someone elses P4 to downgrade also. Are you gonna try to get a older RUU to work by changing the main version?
dc211 said:
Can't quite recall off the top of my head, I do remember trying to get someone elses P4 to downgrade also. Are you gonna try to get a older RUU to work by changing the main version?
Click to expand...
Click to collapse
no. im bricked right now, just trying to recover. but the one x and evo lte have a downgrade method that im almost positive will work on the one s also.
mikeyinid said:
no. im bricked right now, just trying to recover. but the one x and evo lte have a downgrade method that im almost positive will work on the one s also.
Click to expand...
Click to collapse
Good luck then. Hope it works for you.
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK
Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2
Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101
I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL
rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.
igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium
Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes
Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....
So I am a noob to HTC phones. I understand what S-Off is but I am not entirely sure what I could with my phone with it that I can't do now. I am trying to understand whether I should go through the process since there is always the risk of bricking. Thanks!
I have no idea what S-Off is :/ i need some enlightenment
Sent from my One XL using Tapatalk
S-Off is the main thing that allows u 2 root yr phone...
Sent from my GT-I9300 using xda app-developers app
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
mrjayviper said:
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
Click to expand...
Click to collapse
I did do that. It said that I could flash ROMs, Radios, stop my bootloader from saying unlocked. Most of this things with the exception of the last I can already do. I was just wondering if there is something that I could be missing out from. Thanks!
Contrary to popular belief, s-off actually has very little to do with your phone being rooted. S-OFF stands for Security-Off, which basically allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions.
Very simply put, that's what it is. There is a lot more to it that you guys can probably look up. For a user on an hboot below 1.14 it really doesn't do all that much, but it's very useful for devs and people post-hboot 1.14
I'm not totally sure what it will do for us, but it was easy enough for me to go through with it, took about 5 minutes if you've already got ADB/Fastboot set up.
I heard it could take away that stupid red paragraph when I boot and that was all I needed to hear haha
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
I know I sound like a broken record but
I'd love to see someone create a dual boot program for our phone.
Sent from my HTC One XL
BobbyDukes707 said:
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
Click to expand...
Click to collapse
You got to wait for the new tools to be released. Nothing happens automatically AFAIK.
You can flash ROMs on newer hboot without fastboot
Sent from my One X using Tapatalk 2
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
31ken31 said:
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
Click to expand...
Click to collapse
Things will come, just have to give the devs a chance since we just got s-off.
SouL Shadow gave an excellent response to the question here:
http://forum.xda-developers.com/showpost.php?p=38169711&postcount=2462
But as already indicated, things will come in the future, it really doesn't gain much at the moment. Especially for those still on pre-1.14 hboot (and can already flash radios, kernels from recovery).
i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk
People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk
scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.
dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2
I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.