Related
I've read that if you are using a stock rom and updated to 3.70.651.1 OTA then you don't have the ability to root. Is that true or am I just not understanding what I've read? I'd like to root to take advantage of wifi tethering for free. Also, if I'm free to root, any recommendations for which ROM to use would be appreciated.
Thanks
Nope I'm pretty sure you are good to go. Click me for some quick info I dug up
Best ROMs in my opinion:
Fresh: Sense
Myn's: Sense
CyanogenMod: AOSP
Well...according to this thread, [ROOT][GUIDE] HBoot 2.02/2.10 S-OFF - Got the Game Upset Edition - Updated 12.16.10, it states that if have the newest radio (2.15.00.11.19), it will not work although some have claim they could.
You can root your phone now and then just flash a rooted stock ROM or a custom ROM based on build 3.70.651.1.
You can, they posted a new method tonight....but theres only been one success for someone on 0004 hardware.
Fresh: Sense
Myn's: Sense
CyanogenMod: AOSP
Thanks. I'll check these out. I'll also check out each of the threads posted above, but I guess I'm still a little confused. It seems like you're all saying that it can be done, just with varying levels of success. I have the latest radio (2.15.00.11.19) so it seems like that may limit my options, correct?
Yeah, unfortunately that's just how it is. Take Unrevoked 3.21 for example. It was suppose to be a simple one click method to root the EVO but if you go look at their thread, at least half the people who used it were able to run it succcessfully with no problems at all and the other half ran into some kind of issues.
Well the thread title basically says it all.
Does it matter in any way,which recovery I use?
I'd like to flash the latest cyanogen,as that was the latest rom I had on my pulse before getting the desire and I'd really like to use it again.
Phone info:
S-ON
PVT4
Erasesize 40000
Latest radio
Root and SU is working fine so far and I currently have amon-ra v2 on it.
Is there anything that I should read or look out for before starting to flash cyanogen,or any other rom,for that matter.
I know...this has probably been answered before,but you guys really have a huge amount of info here and it's kinda hard to really find the necessary answers.
So thanks in advance for any answers...
If you read the s-off thread about PVT-4 new (40000) devices, it specifically suggested to flash the modified 2.5.1.3 clockwork image with unrEVOked as a temporary fix... so, if i were you, i would have gone with what was recommended.
Sent from my HTC Desire using eMIUI
MasDroid said:
If you read the s-off thread about PVT-4 new (40000) devices, it specifically suggested to flash the modified 2.5.1.3 clockwork image with unrEVOked as a temporary fix... so, if i were you, i would have gone with what was recommended.
Sent from my HTC Desire using eMIUI
Click to expand...
Click to collapse
That's what I've done, although I've had problems flashing a couple of ROMs with the modified CWM for PVT4 40K devices. It has been suggested that I switch to Amon Ra but I can't find anything specific for the PVT4 devices so I'm staying put for now. LeeDroid ticks all the boxes at the moment.
Well, i know oxygen, reflextsense, and miui also work for pvt-4 (40000) devices, could try one of those if you like
I think you may like miui but like you said, its about personal preference
Sent from my HTC Desire using eMIUI
Well in that thread:
http://forum.xda-developers.com/showthread.php?p=10148951#post10148951
I also did read that someone recommended amon-ra regarding the 4000 devices,so I flashed that.
But no problem,I'll switch to the clockworkmod version that's been posted over there.
Bummer that I jumped on the desire wagon a little late,so that I now have one of these devices, where you have to be a little more careful then usual.
Do you know,if cyanogen is one of the roms that I should be able to use,or should I rather stick to the ones you mentioned,for now?
[armitage] said:
Well in that thread:
http://forum.xda-developers.com/showthread.php?p=10148951#post10148951
I also did read that someone recommended amon-ra regarding the 4000 devices,so I flashed that.
But no problem,I'll switch to the clockworkmod version that's been posted over there.
Bummer that I jumped on the desire wagon a little late,so that I now have one of these devices, where you have to be a little more careful then usual.
Do you know,if cyanogen is one of the roms that I should be able to use,or should I rather stick to the ones you mentioned,for now?
Click to expand...
Click to collapse
I cannot say for sure friend, maybe just stick with the ones we know are certain to work. Have you tried asking in the Cyanogen ROM thread?
Not yet,will have a look at the thread later on,maybe it has been mentioned there already.
Thanks for your help.
[armitage] said:
Not yet,will have a look at the thread later on,maybe it has been mentioned there already.
Thanks for your help.
Click to expand...
Click to collapse
Oks, good luck
Re-using my thread here, cause even though the original question has been answered,my new question is still pretty much the same.
Anyway...I red a lot about this in the clockworkmod and amonra thread but didn't really find a real answer.
Problem is that many people wrote that they have problems with all clockwork versions above 2.5.0.7 cause they were never really meant for the desire.
Few guys mentioned problems with usb after restoring a backup,some lost the sd-ext and so on.
So my question is...Is there actually anyone,with a pvt4 erasesize 40k device,that has either used clockworkmod or amon-ra, to successfully create and restore a backup of their rom,without any problems?
An answer would be really appreciated,cause I would really love to have a backup of my rom,that I could actually use,without any problems,if something would go wrong.
bump......
I´ve such a device (PVT4 with erasesize 40000) and had no problems using amon-ra to create a nandroid backup and restore that backup. tested it several times.
FYI: cyanogenmod 6.1 and leedroid 2.3 worked without any problems.
my device has s-off due to alpharev 1.8 but currently there are no modified partition layouts available for the devices with new nand layout.
Thanks a lot mate,that's really good to know.
I did find the 2.0 thread but heard a lot about a 2.0.1 version beeing available.
I'm guessing you have amon-ra 2.0 or 2.0.1 installed?
If 2.0.1 could you maybe give me a link to that one?
Thanks...
I´m currently using amon-ra v2.0.1 but have no idea what´s the difference to v2.0.
I´ve not enough posts to post outside links
-> sent you a pm with the link from where i´ve downloaded amon-ra v2.0.1
Thanks...
Guess I can tag this thread as "solved" now.
I've been trying to flash the CDMA Wildfire's SPL (from this post: http://forum.xda-developers.com/showpost.php?p=11712773&postcount=1) onto my Alltel Wildfire. Since there's no custom recovery (yet), I traced the steps from here and modified my misc and cache partitions manually on my PC, then flashed them with flash_image. Unfortunately, it's not working.
I thought I might be doing something wrong, so I pulled out my old CDMA Hero and tried the exact same thing, but it worked on the Hero. What am I doing wrong? Is it because the rom is designed for Verizon, or did HTC just remove that update functionality? Any suggestions, hints, etc. are greatly appreciated.
EDIT: I just looked back at the post, and the rom isn't "designed" for Verizon, xHausx just said "Verizon's version of the Wildfire", referring to CDMA as opposed to GSM. My bad.
Wow. Nothing? I'm just looking for suggestions or opinions. I'm willing to try anything
Depending on how much spare time I get today, I might try reversing the stock recovery to see if there's anything in there related to flashing the bootloader. I'll post back if I find anything.
im going to try getting s off on this wildfire bee cdma. i will let you no what i find.
oostah said:
im going to try getting s off on this wildfire bee cdma. i will let you no what i find.
Click to expand...
Click to collapse
Awesome! Just thought I'd share some of my failed attempts to speed things up:
I replaced the public key with the test key in the stock recovery's /res/keys file, then tried a write_firmware_image. Didn't work.
I replaced the kernel in the boot.img with the bootloader, and set the load address to 0 ("jumpspl style"). Didn't do anything noticable (stayed on Alltel logo).
Another thing I noticed is my Bee's model number is PD0610000, and the one in the rom above is PD0611000. I don't know if there's anything significant in that, but between that and the massive difference in hboot versions, I'm afraid to try and flash that rom. Luckily, I found the alltel one here: h**p://u.115.com/file/t5f03f513d (can't link, even though I did before. hmm...). Someone would need to make some S-OFF patches, though, since it's a SHIP SPL.
I also thought about a unrEVOked forever style "radio hack" (for lack of a better term), but I'm not sure how to proceed down that road.
Good luck to ya
Isaac356 said:
Awesome! Just thought I'd share some of my failed attempts to speed things up:
I replaced the public key with the test key in the stock recovery's /res/keys file, then tried a write_firmware_image. Didn't work.
I replaced the kernel in the boot.img with the bootloader, and set the load address to 0 ("jumpspl style"). Didn't do anything noticable (stayed on Alltel logo).
Another thing I noticed is my Bee's model number is PD0610000, and the one in the rom above is PD0611000. I don't know if there's anything significant in that, but between that and the massive difference in hboot versions, I'm afraid to try and flash that rom. Luckily, I found the alltel one here: h**p://u.115.com/file/t5f03f513d (can't link, even though I did before. hmm...). Someone would need to make some S-OFF patches, though, since it's a SHIP SPL.
I also thought about a unrEVOked forever style "radio hack" (for lack of a better term), but I'm not sure how to proceed down that road.
Good luck to ya
Click to expand...
Click to collapse
i have two of these bee's i have one rooted but no recovery. so i was looking to see if i can get s off. but i should be able to spend mo time on them now.
bump for this thread. Is there any S-off available now for HTC Bee? I need it so bad. Thanks
Sorry for the near-necropost
Okay guys. It's not my main phone, so it's not a priority. But this is the only phone I have that I haven't been able to customize.
I'm very familiar with dirty root methods, I have a rooted/S-OFF'd Tb that I did by hand. If anyone knows/has the files I need to get a dirty S-off, I'd be more than happy to try and do this, and I'll post my results (best scenario, a guide) afterward.
Anyone? Please?
All the best,
-HG
motoyola said:
bump for this thread. Is there any S-off available now for HTC Bee? I need it so bad. Thanks
Click to expand...
Click to collapse
Re: bump Im looking for the same thing.
still nothin?
Any progress in rooting this? Any available RUU? Thanks!
HalosGhost said:
Okay guys. It's not my main phone, so it's not a priority. But this is the only phone I have that I haven't been able to customize.
I'm very familiar with dirty root methods, I have a rooted/S-OFF'd Tb that I did by hand. If anyone knows/has the files I need to get a dirty S-off, I'd be more than happy to try and do this, and I'll post my results (best scenario, a guide) afterward.
Anyone? Please?
All the best,
-HG
Click to expand...
Click to collapse
Do you still want to work on this phone? I have the Alltel and C Spire RUU but don't where to start.
Hi HalosGhost,
I really don't know which files you need, but I'm willing to send you whatever you told me to send you (from the phone), I'm able to have root access, and also I have a "backup" (since this "bee" doesn't have a way to backup the actual ROM) that I found in a chinese site: RUU_Bee_Alltel_WWE_1.07.671.2_Radio_1.00.00.1001_NV_Alltel_2_60_NoCNV_release_152081_signed.exe[/URL] (referenced by Isaac356, I tested and I did a successful re-flash to my cell) and I know it has the damn'd lock AKA nand lock, so I was unable (and as far as I understand, no1 has) to flash it because this one is preventing us from doing it.
If anybody has another tip I missed please say it now.
So, what you need, buddy?
NOTE: Grrr! I need it to take out the link: so I post it here: http: // u.115.com/file/t5f03f513d
PS, I missed to mention that I tried the GoldenCard creation but all I tried did NOT work
any news about this? I tried using HTCDEV to gain S-off but still no luck. It Just updated my hboot.
Hopefully this hasn't been covered. I wasn't able to find anything after half a day of searching.
My questions is regarding setting up DZ hboot on a G2. From what I've read this is necessary on some (seems like most) ROMs due to the size limitation of /system (particularly Sense ROMs).
Is there any reason necessarily to stay at a G2 hboot if I can deal with /data size restrictions. I'd like to switch over to a few other ROMs that require it, however, I wouldn't necessarily want to keep switching back and forth if I don't have to. A few particular scenarios come to mind.
1) I create a backup of my current CM7 backup and would like to go back to it after running a sense based ROM that require DZ hboot. Am I required to restore the G2 hboot before restoring?
2) If I didn't want to remove the DZ hboot, can I just do a clean CM7 install over it?
3) Is there anything in particular that requires the DZ hboot? Does this only change the hboot? I thought I had seen somewhere that it changes radio and radio needs to be reflashed to G2 (I'm new to radio flashing and haven't read up enough on it yet).
I guess I am just trying to understand the dependencies of ROMs and hboot. Any thoughts or references would be most welcome. Thanks.
If you flash the DZ hboot you will be able to restore any nandroid backups you made before changing hboot's. All roms will work on the DZ hboot cm, sense, miui and aosp.
You will only ever need to change hboot's if you need to go back to stock for warranty purposes.
If you follow the guide on www.virtuousrom.com to change hboot's it will change your radio, but if you successfully mange to flash the hboot you will pretty much know the procedure for flashing radios.
Do Androids dream of electric sheep?
Thanks CJ. That gives me answers to most my questions, time for a little more reading.
Quick question however, is the zip method for flashing radios preferred, or fastboot and setup the img? Especially after switching the hboot as the proccess sounds the same.
Or is the process of naming PC10 etc zip files the way of tricking the bootloader into using those files?
biohazrd51 said:
Thanks CJ. That gives me answers to most my questions, time for a little more reading.
Quick question however, is the zip method for flashing radios preferred, or fastboot and setup the img? Especially after switching the hboot as the proccess sounds the same.
Or is the process of naming PC10 etc zip files the way of tricking the bootloader into using those files?
Click to expand...
Click to collapse
Sorry for the late reply, had a busy few days. Either method is good but check the md5sum before flashing radios.
Sent from my HTC Vision using XDA Premium App
Hello everybody,
as the title suggests: (Why) should I update my hboot?
Yes, I've searched, yes I've read. I'm sure I could find the concise answer if I invested several hours of reading various highly informative threads, but maybe somebody can put it down in a few, easy to understand sentences, or point me to a post / wiki entry where it's explained concisely?
My situation: I have the HTC One X (Tegra 3 version), rooted, S-ON, with the 0.43 hboot at the moment. I have installed several ICS sense roms in the past, and am currently running JB (4.1) AOSP (/CM/PA/...) roms. This all works nicely, but I really don't understand all the talk about different hboot versions, needed RUUs, etc.
So I have several more detailed questions:
If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Is it correct that once upgraded, I have no option whatsoever to downgrade?
What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
Sorry for the flood of questions. As you can see, I really tried to find the answers. In some cases I'm rather sure of what I think, but some questions leave me baffled. At the moment it seems to me that I have to decide between either a Non-Sense JB, or a Sense JB, but I cannot switch between them (and retain all functionality of my phone).
Thanks in advance,
Thor
if you upgrade it, you will be able to flash jb based roms, as you already know, there are jb roms out, which boots on any version of hboot, some dont, thats why you need to upgrade, for example, im running the blade rom v3.0.0 which its great, but i couldnt flash if i didnt upgrade the hboot.
pull.me.under said:
Hello everybody,
as the title suggests: (Why) should I update my hboot?
Yes, I've searched, yes I've read. I'm sure I could find the concise answer if I invested several hours of reading various highly informative threads, but maybe somebody can put it down in a few, easy to understand sentences, or point me to a post / wiki entry where it's explained concisely?
My situation: I have the HTC One X (Tegra 3 version), rooted, S-ON, with the 0.43 hboot at the moment. I have installed several ICS sense roms in the past, and am currently running JB (4.1) AOSP (/CM/PA/...) roms. This all works nicely, but I really don't understand all the talk about different hboot versions, needed RUUs, etc.
So I have several more detailed questions:
If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Is it correct that once upgraded, I have no option whatsoever to downgrade?
What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
Sorry for the flood of questions. As you can see, I really tried to find the answers. In some cases I'm rather sure of what I think, but some questions leave me baffled. At the moment it seems to me that I have to decide between either a Non-Sense JB, or a Sense JB, but I cannot switch between them (and retain all functionality of my phone).
Thanks in advance,
Thor
Click to expand...
Click to collapse
here are some good news ,some new Non-Sensed Roms like 4.2.1 AOKP beta release are able to run on all HBoots and there is also Trip's ROM which works for Hboots also ,so with no time all Hboots will be able to run at all kinds of ROMS over there for HOX ,
Have you come across the following site...i guess it explains pretty well..If it doesnt solve ur curiosity, u can ask it here..!! Every1s here to help..!!
http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html
^ I read that site a few days ago and it was the best explanation I've see.
sent from my highgrade HTC one x
pull.me.under said:
Hello everybody,
as the title suggests: (Why) should I update my hboot?
Yes, I've searched, yes I've read. I'm sure I could find the concise answer if I invested several hours of reading various highly informative threads, but maybe somebody can put it down in a few, easy to understand sentences, or point me to a post / wiki entry where it's explained concisely?
My situation: I have the HTC One X (Tegra 3 version), rooted, S-ON, with the 0.43 hboot at the moment. I have installed several ICS sense roms in the past, and am currently running JB (4.1) AOSP (/CM/PA/...) roms. This all works nicely, but I really don't understand all the talk about different hboot versions, needed RUUs, etc.
So I have several more detailed questions:
If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Is it correct that once upgraded, I have no option whatsoever to downgrade?
What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
Sorry for the flood of questions. As you can see, I really tried to find the answers. In some cases I'm rather sure of what I think, but some questions leave me baffled. At the moment it seems to me that I have to decide between either a Non-Sense JB, or a Sense JB, but I cannot switch between them (and retain all functionality of my phone).
Thanks in advance,
Thor
Click to expand...
Click to collapse
[*]If I got it right, I need a newer hboot version to run Sense JB Roms - correct?
Yes perfectly right.
[*]To upgrade to a newer hboot version, I need to download the correct RUU and install this, correct?
Yes, that is ONE OF THE methods to do it. Another method is, you can use this tool. (It doesn't require you to relock you phone)
[*]How do I find the "correct" RUU? And am I right that the RUU is an offical exe file, installing the Stock Rom on an unlocked phone only (meaning I have to relock first)?
First, head over here and check whether your CID has received the JB update (upgraded hboot). If it hasnt then you will have to wait.
If it has then you can search for your RUU.
[*]Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Nope, it will ONLY cause a problem with the non-sense ROMS that were built on the older base , i.e. the ones running android 4.1.2 , newer ROMS like android 4.2.1 builds will work perfect, and that too only gps is a problem. Also, most of the devs have found the patch to fix this problem.
[*]Is it correct that once upgraded, I have no option whatsoever to downgrade?
yes, that is correct.
[*]What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
There is no such relation. The only relation is that the kernels wont work only, i.e. the kernels built on the older source code wont work at all on the upgraded hboot. And there are no custom JB kernels as of yet as HTC hasnt released the source code yet.
Hope this helped.
anks257 said:
[...]
[*]Is it correct that hboot version more current than my original, never updated one will cause problems (GPS, direct wifi, volume, bt, ...') with basically ALL Non-Sense roms?
Nope, it will ONLY cause a problem with the non-sense ROMS that were built on the older base , i.e. the ones running android 4.1.2 , newer ROMS like android 4.2.1 builds will work perfect, and that too only gps is a problem. Also, most of the devs have found the patch to fix this problem.
[...]
[*]What is the interaction between the hboot and the installed kernel - do some kernels work better with certain hboot versions?
There is no such relation. The only relation is that the kernels wont work only, i.e. the kernels built on the older source code wont work at all on the upgraded hboot. And there are no custom JB kernels as of yet as HTC hasnt released the source code yet.
Hope this helped.
Click to expand...
Click to collapse
Thanks for this VERY helpful reply! What I don't understand about the two points I've quoted: You say that most of the devs have found fixes so that 4.2.1 roms run perfectly, but at the same time that there are no custom JB kernels. I thought the gps problem had to be fixed in the kernel? But that's probably just my misassumption.
Even if my phone hadn't hadn't just badly broken, I'd stick to the old hboot for a while longer then. I don't want to switch to JB 4.2.1 yet, as there seems no way to get pdroid running on that.
Thanks for taking the time to answer (this goes to all of you who replied)!
Thorsten
What they mean is that they have patched the ramdisk in the 4.2 ROMs to work with the older 4.1 kernel's that we do have the sources for
Sent from my HTC One X using xda app-developers app