Related
Hi There...
i recently got a new HTC Desire... And I want to root it...
But I have hit a problem, my desire is apparently PVT 4 (40000)... which means i cant use the regular unrevoked....
It would be of great help if you post a walkthrough guide of root and installing Oxygen/CM7 ....
Thank you very much
what makes you think that you can't use it?
rooted mine without problem.
wrong section btw...
Maybe search read and post in the right section this has all been posted already
ieftm said:
Boot your phone in fastboot mode,
this should say something like this in the top line:
BRAVO PVT4 SHIP S-ON.
This seems to apply to -NEW- PVT4 devices only.
Apparently there are some older ones named PVT4 as well.
Check using the following:
cat /proc/mtd (from adb shell or terminal emulator)
Erasesize will say either 20000 or 40000, whereas the last one identifies your device as being PVT4 New. This has a different NAND chip, which uses a bigger pagesize and changed partition offsets.
Tools will need to be adjusted to work with this change (for example, ClockWorkmod, AlphaRev, and some custom ROMs.)
Check out AlphaRev 1.8 at http://alpharev.nl , that should install HBOOT S-OFF for these PVT4 new devices now too
Click to expand...
Click to collapse
vmax007 said:
Hi There...
i recently got a new HTC Desire... And I want to root it...
But I have hit a problem, my desire is apparently PVT 4 (40000)... which means i cant use the regular unrevoked....
It would be of great help if you post a walkthrough guide of root and installing Oxygen/CM7 ....
Thank you very much
Click to expand...
Click to collapse
Just run unrevoked, but chooce a custom recovery like the latest CWM 3.0.0.5-r3 or AmonRa 2.0.1..This should be in the Q&A section
is someone gonna post a guide to flashing new roms on the sensation , im getting one when they come out and im coming from an HD2,just wondering if the procedures are basically gonna be the same for the sensation as the HD2 as far as hspl 3 etc.....that is once the bootloader problem is woked out,been waiting for this phone for a long time and if it suks i will have no problem going back to my incredible hd2
I expect flashing on the Sensation will be like most other HTC Android devices. Get it permarooted, unlock the bootloader, flash a recovery like CWM, then flash the ROM zip.
tigerz0202 said:
is someone gonna post a guide to flashing new roms on the sensation , im getting one when they come out and im coming from an HD2,just wondering if the procedures are basically gonna be the same for the sensation as the HD2 as far as hspl 3 etc.....that is once the bootloader problem is woked out,been waiting for this phone for a long time and if it suks i will have no problem going back to my incredible hd2
Click to expand...
Click to collapse
Flashing Android devices is nothing like flashing the HD2. I have three HD2's and 2 MT4G and it is night and day difference...except for the Recovery part if you are using MAGLDR for your HD2.
I am looking closely at the Sensation.
Flashing the Sensation will not require anything like HardSPL. Android users do not even know what HardSPL is.
To flash the Sensation we will first have to unlock the bootloader, get some kind of root access(whether that is permanent or not remains to be seen) and finally flash a recovery of some sort from which you can flash a new ROM in the .zip format.
So yeah, nothing like the initial flashing of Android to the HD2.
Thanks for the replies, well I hope the bootloader gets cracked but I just gotta give the sensation a try with the hardware upgrades over the hd2
I have been using HTC Touch Diamond2, I'm gonna get a HTC SEnsation once it comes out. After reading the guides on HTC Desire HD for flashing, I realised it is completely different.
I suggest reading all the guides thoroughly before flashing.
I am also nervous about flashing cause it is my first time flashing an android phone. And Its a new phone, hopefully I dont screw up.
deepakmk said:
I have been using HTC Touch Diamond2, I'm gonna get a HTC SEnsation once it comes out. After reading the guides on HTC Desire HD for flashing, I realised it is completely different.
I suggest reading all the guides thoroughly before flashing.
I am also nervous about flashing cause it is my first time flashing an android phone. And Its a new phone, hopefully I dont screw up.
Click to expand...
Click to collapse
I can't help but think you're jumping the gun. We don't know how locked/unlocked the Sensation will be (once unlocked by HTC, if that happens). If it's made radio S-OFF before shipping or by an official FOTA update or RUU for those already shipped, it will most likely be just a matter of installing ROM Manager from the Market, clicking the 'Install ClockWorkMod Recovery' button, and then using CWM to install any ROM you like from your sdcard. That's a very low risk procedure that's almost impossible to screw up.
We're going to have to wait for the bootloader to be unlocked. We'll probably see a CWM Recovery a little after and a temp root solution for those unfamilliar with fastboot.
Wrong section btw ;p
Sent from my HTC Vision
dazweeja said:
I can't help but think you're jumping the gun. We don't know how locked/unlocked the Sensation will be (once unlocked by HTC, if that happens). If it's made radio S-OFF before shipping or by an official FOTA update or RUU for those already shipped, it will most likely be just a matter of installing ROM Manager from the Market, clicking the 'Install ClockWorkMod Recovery' button, and then using CWM to install any ROM you like from your sdcard. That's a very low risk procedure that's almost impossible to screw up.
Click to expand...
Click to collapse
Over here in singapore, the phone is yet to be released. I heard 18th June for my carrier. I guess it should be S-Off. Or maybe the new batch released. I've never had any experience in flashing a rom on android phones.
I have it now for one week. I have to say sense 3.0 is so nice! For now I miss root only because of titanium backup and deleting vodafone crap... The original rom feels real nice and battery seems ok
Swyped from my HTC Sensation Z710e using XDA App
deepakmk said:
Over here in singapore, the phone is yet to be released. I heard 18th June for my carrier. I guess it should be S-Off. Or maybe the new batch released. I've never had any experience in flashing a rom on android phones.
Click to expand...
Click to collapse
Once it's fully developed someone will post a guide. As long as you read and follow directions exactly... rooting and ROM'ing is easy. 99% of phones that get accidentally bricked are probably because the user didn't read and do everything exactly.
Until that day enjoy Sense 3.0.
I think flashing should be similar to any android device.. copy the rom.zip into sd card and flash via recovery.. before that we need :
1. Rooting of Sensation
2. A compatible recovery
he he
compiling the recovery shouldnt be that hard colockworkmod has a guide i will try to port once we get the sensation running
JonSolo said:
Flashing Android devices is nothing like flashing the HD2. I have three HD2's and 2 MT4G and it is night and day difference...except for the Recovery part if you are using MAGLDR for your HD2.
I am looking closely at the Sensation.
Click to expand...
Click to collapse
This is because hd2 is not a real Android device. Remember when you bought it and there was an OS on it called windows 6.5 all real android devices are similar.
Thank devs for making hd2 run Android. Still considered by me to be the best and most flexible phone out there
nickyg008 said:
Thank devs for making hd2 run Android. Still considered by me to be the best and most flexible phone out there
Click to expand...
Click to collapse
+10
My HD2 will still be up and running something even after I get the Sensation and the Hercules.
My mate just received his Sensation yesterday and is already keen to root/S-Off etc. so I am doing some reseacrh for him. I have the good ol' Desire, which I have done a lot of work with, so pretty familiar with modding that particular phone. The Sensation is entirely new territory for me, however...
I've read and understand the S-Off/CWM/CID thread http://forum.xda-developers.com/showthread.php?t=1192300 , all looks pretty straight forward and simple.
- Since mates phone is already unlocked, is the SuperCID install required to flash custom ROMs?
- Is there a program similar to AndroidFlasher for Desire available for the Sensation? I found this an easy way to update HBoot tables and other things on my Desire. And if not, what is the recommended method to install these?
- For Desire, HBoot.img's can be found at alpharev.com...where do I find CM7/r2 or data++ type tables for Sensation?
- With a Desire that is S-Off, it's highly recommended to update radio's using Android Flasher or fastboot terminal to push the radio.img, since flashing a .zip through cwm can cause bricking. Is this the case with Sensation, or is it OK to just flash the .zip?
...more Q's as I think of them...
If figure that this would be the place to ask these questions considering that there is no general HTC forum on this board and that I expect a decent amount of conversation about hboot and S-OFF to converge here. My questions are about the boot process and the specifics about how the RTOS that operates the baseband runs on HTC's new devices.
1: I have learned that on most phones, the baseband processor and the application process boot and operate independently of each other. If I am correct, HTC is using Qualcomm's Snapdragon SoC in its newest devices, which includes a higher level of integration between the baseband and application processors. They may even be indistinguishable as far as I know. hboot is not verified by the hardware but verifies any updates to itself, as far as the Flyer is concerned. Knowing that S-OFF allows for the loading of custom radio firmware implies that hboot verifies the baseband's software, and therefore is the absolute root of trust of trust on HTC's devices. What mechanism allows the baseband software and the Linux kernel to run side-by-side without interfering with the other's processes? The only way I can see this working is if a hypervisor is running on the device or the baseband has more privileges.
2: Revolutionary changes S-ON to S-OFF whereas Unrevoked could only patch one of the bootloaders (I think) to ignore secuflag because secuflag was inaccessible. This appears to contradict the statement in the above paragraph that hboot is the root of trust and loads both the baseband firmware and the application firmware. Which is it or is there something I am missing?
3: What is the difference between hboot and the SPL (Secondary Program Loader, I believe. Think HSPL.)?
Sent from my DROID2 GLOBAL using XDA App
I am bumping this thread.
Another bump.
And another one.
Your best bet would be asking Agrabren on twitter. He's been working on getting S-OFF before we got Revolutionary to give the S-OFF. If you look at he EVO 3D forums, there was a lot of chatter and PDF files on how everything was linked together. Since the EVO 3D and Sensation are pretty much the same except the Ram and 3D features, it's the same work.
Edit:There was also an PDF file with the schematics of everything on the motherboard and how everything connected, what booted what. I'll try to find it and I'll private message it to you and post on this thread.
Also, on HTC devices as far as I know, the Radio is the trust of everything, It controls everything on the device. Ever since the G2 was released (this is when they introduced some heavy duty locks and wasn't easy as previous devices), I've also been following up on how everything is controlled on these phones. During the 2 months that it took devs to gain S=OFF, I've read IRC logs and tried everything and got a good idea of how everything works.
But here's what I know. Once the radio is S=OFF then we have *COMPLETE* control over our phones. With the bootloader S=OFF and radio S=OFF, we can still flash recovery, different ENG bootloader but cannot flash any unsigned radio images.
When the phone boots up though, I know the first thing that is booted is the radio, then bootloader, kernel, and OS. (I might have missed one or two more things that's also booted and checked).
The bootloader also checks kernel, and system partition if they are signed with HTC's private keys. If the system partition is changed on a device with S=ON, the system will be changed the way it was back from the factory, this is the reason we have temp root.
Also the baseband has it's own processes in Android and Android will never allow you to modify the radio while it's booted.
Through my conversations with globatron, I was under the impression hboot was the root of trust.
Does anyone else care to comment?
Edit: I have seen some custom radios for HTC's Android phones. What the mechanism is, I don't know.
Yes,I'm follow u
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
that's an interesting question.. i'll have to follow and do some research on it myself
That's more in-depth than I know. What I *do* know is that the s-off flag is kept in the NVRAM. Who reads it and uses it? Probably the radio first.
EDIT: Definitely the radio first, because if you flash an ENG bootloader then go back to S-ON, it bricks the device.
Is that because the radio boots first?
Yes, as agabren pointed out, the radio sets the security keys. If you have a S-off radio then you're pretty much free.
That's also why most devs attack the radio first to gain FULL control of the device.
Even if the bootloader sstates its locked, only the bootloader is, not the radio.
The radio is the most important. The best thing you could do is search for the G2 s-off irc logs. There's a website (I forgot) by a dev that mapped out everything. How everything works on HTC devices. I'll try to find it.
Sent from my HTC Sensation Z710e using XDA App
I has been hoping that hboot was first. I don't like the baseband-application architecture. I don't like designs with two or more independent systems. Just a matter of taste (as dumb as that sounds).
I have another question: does the radio boot hboot or are the two processes started separately at boot time?
Sent from my DROID2 GLOBAL using XDA App
xdviper said:
Yes, as agabren pointed out, the radio sets the security keys. If you have a S-off radio then you're pretty much free.
That's also why most devs attack the radio first to gain FULL control of the device.
Even if the bootloader sstates its locked, only the bootloader is, not the radio.
The radio is the most important. The best thing you could do is search for the G2 s-off irc logs. There's a website (I forgot) by a dev that mapped out everything. How everything works on HTC devices. I'll try to find it.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Hi,
I own a HTC Sensation, but the bootloader shows UNLOCKED, S-ON and hboot 1.23.0000. I wanted to get the S-OFF. Can you help me? Or wait for the new issue in the Revolutionary?
Thanks
djnero666 said:
Hi,
I own a HTC Sensation, but the bootloader shows UNLOCKED, S-ON and hboot 1.23.0000. I wanted to get the S-OFF. Can you help me? Or wait for the new issue in the Revolutionary?
Thanks
Click to expand...
Click to collapse
Start a new thread. I am really sick of replies that have nothing to do with the topic.
djnero666 said:
Hi,
I own a HTC Sensation, but the bootloader shows UNLOCKED, S-ON and hboot 1.23.0000. I wanted to get the S-OFF. Can you help me? Or wait for the new issue in the Revolutionary?
Thanks
Click to expand...
Click to collapse
You need to flash an older h boot, 1.17, however, if you used HTC unlock method I am not sure about s off using Revolutionary, it used to not be possible. IDK, maybe it's changed now.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Does the NVRAM reside on a separate chip?
Yesterday, I was given a Wildfire S to put on a custom ROM. It was actually my younger sister's and while she was perfectly happy with it performance wise, the internal memory's a joke - some 150 MB!!
So i promptly proceeded to amaze her with the flamboyant show of HTC Dev unlock, followed by rooting and CWM recovery. Then i downloaded a ROM with A2SD built in, placed it on the sd card, partitioned the sd card to support an A2SD partition and a linux swap partition, and flashed the zip after a full wipe. After flashing the new ROM, i was all but ready to flash boot.img from fastboot, i decided to scare her by trying to boot without that and get the phone to hang on the splash screen, then extort a treat from her to get it to boot!!
That's when it hit me in the nuts. It booted! So i attributed it to the ROM being a Sense ROM, able to run on the stock kernel - so i went and checked the phone info - and there it was - a custom kernel!! The same that was included in the ROM zip.
This got me thinking - is it only us that have to flash the boot.img separately? Why can the WFS guys flash custom kernels from recovery itself? I thought the HTC Dev Unlock method prevents you from writing to the boot partition??!!
Maybe Tectas can shed some light on this - I see you're also a WFS guy. Any thoughts on this guys?
EDIT : I'm so sorry this got posted in the Themes and Apps section. Have requested it be moved to the General Section. Goofed up with the tabs on my browser and ended up creating this thread in the wrong section. Sorry guys!!
Was it S-on?
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
suku_patel_22 said:
Was it S-on?
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
Click to expand...
Click to collapse
Yes - stock S-On to begin with.
And then HTC Dev Unlocked
That's strange then
did you use 4ext?
Edit: saw you already mentioned cwm
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
suku_patel_22 said:
That's strange then
did you use 4ext?
Edit: saw you already mentioned cwm
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
Click to expand...
Click to collapse
I would have used 4EXT in the blink of an eye - problem is, 4EXT doesn't support the Wildfire S currently. The currently supported devices are : HTC Sensation / XE, Incredible S / 2, Desire Z / G2, Desire S, Desire, Desire HD, Inspire 4G, myTouch 4G, Nexus One, Thunderbolt, Evo 3D GSM / CDMA, Amaze
Back to topic : anyone else used any other HTCDev Unlocked device who can flash kernels from recovery?
I'm more or less a wfs guy^^
My gf got one and i take care of their index thread, but i'm pretty less active there since my 2. girly was born.
Also hers is xtc s-offed, because there was no htcdev unlock when she got it and she doesn't let me play that much with it.
I wonder that it was flashed from cwm directly without fastboot, but there are 2 possibilities coming to my mind how this could be possible.
1. Their cwm is an unofficial implementation made by alquez as far as i know, could be that he already made what madmaxx is atm working on.
2. Because the wfs isn't a popular device and they even needed a petition to get at least the htcdev method to unlock their bootloader aside from xtc (for sure only at gsm devices, the wcdma wfs has other possibilies to unlock), htc could have given them a little goody and removed the /boot restriction for recovery.
No matter which case fits, there are many devices needing to flash the boot.img when htcdev was used (i.e. the htc one x also has this restriction at recovery).
Tectas said:
I'm more or less a wfs guy^^
My gf got one and i take care of their index thread, but i'm pretty less active there since my 2. girly was born.
Also hers is xtc s-offed, because there was no htcdev unlock when she got it and she doesn't let me play that much with it.
I wonder that it was flashed from cwm directly without fastboot, but there are 2 possibilities coming to my mind how this could be possible.
1. Their cwm is an unofficial implementation made by alquez as far as i know, could be that he already made what madmaxx is atm working on.
2. Because the wfs isn't a popular device and they even needed a petition to get at least the htcdev method to unlock their bootloader aside from xtc (for sure only at gsm devices, the wcdma wfs has other possibilies to unlock), htc could have given them a little goody and removed the /boot restriction for recovery.
No matter which case fits, there are many devices needing to flash the boot.img when htcdev was used (i.e. the htc one x also has this restriction at recovery).
Click to expand...
Click to collapse
That's the thing... the CWM recovery I used was downloaded and flashed using ROM Manager... so it's the original one by koush. I really don't see why HTC would do something like give the WFS an unlocked boot while deny it on other devices....? There must be something else to it.
The last thing I am willing to believe is that HTC took pity on the WFS owners and did this as a kind gesture. HTC is a corporation - a device manufacturing machine.... and just like any other, it may be good at what it does, but it does not have a heart. None of them does.
enigmaamit said:
That's the thing... the CWM recovery I used was downloaded and flashed using ROM Manager... so it's the original one by koush. I really don't see why HTC would do something like give the WFS an unlocked boot while deny it on other devices....? There must be something else to it.
The last thing I am willing to believe is that HTC took pity on the WFS owners and did this as a kind gesture. HTC is a corporation - a device manufacturing machine.... and just like any other, it may be good at what it does, but it does not have a heart. None of them does.
Click to expand...
Click to collapse
Could for sure be something else behind it.
Never wanted to say they would have done it as a kind gesture (i totaly agree that such a corporation got no heart at all), more to calm them down and keep them up buying htc products, because there where many disappointed wfs users (the petition they made even where featured at the xda portal).
If this is the case why the /boot partition got no write restrictions, i guess it's related to marketing not kindness.