Related
I have a somewhat unique situation that I haven't been able to peace together after 6 days of searching threads. Any insight would be greatly appreciated!!
My elderly mother bought an EVO recently after I bought one and some idiot talked her into running the 3.30 RUU on an EVO with software 3.26.651.6, baseband 2.15.00.07.28, and hardware ver 3. This also upgraded her HBOOT to ver 2.02. From my thread searching, it seems that 3.30 isn't intended for EVO's with HW ver 3 and may impact the phone's performance and/or battery life. I do believe that there was an OTA for her phone for 3.29.651.5.
I am wondering if it is possible to downgrade her HBOOT and sw back to 3.26.651.6 and the corresponding HBOOT version? I would then want to apply the OTA to update to 3.29.651.5, where she should be. She NEEDS to have a stock phone . From searching threads it appears that I need to root her phone using the 'like a boss" method and then run the RUU 3.26.651.6. However, I am unable to find the stock 3.26 recovery img needed. I do have the stock 3.30 recovery img but am reluctant to use a different recovery img.
Help please, if you can!
A little direction if you can...
Anyone? Just looking for a little direction here. Also, trying to follow the rules and keep this out of the dev section...
Not a noob to rooting, just to the EVO. Rooted my old hero and flashed a few diff roms...just want to make sure I have the right info and am prepared before I start rooting the phone. I really have searched MANY threads and I feel confident about rooting the phone via "Like a boss" and illogos's updates but I didn't find anything about successfully un-rooting to a pre 3.30 software version.
Can I just run the RUU for 3.26xxx after rooting? I'm assuming that will be fine with S-Off and an older hboot.
So I first followed these instructions to use Unrevoked to root my girlfriend's new phone, as this was how I rooted my phone:
http://theunlockr.com/2010/07/20/how-to-root-the-htc-evo-4g-unrevoked-method/
Unrevoked said it was triumphant, but when I rebooted into my bootloader, and selected fastboot -> recovery I just got a black screen with a red triangle. Apparently, there's no nandroid loaded on my phone.
So I proceeded to follow Toast's 2 part guide here:
Part 1: http://forum.xda-developers.com/showthread.php?t=718889
Part 2: http://forum.xda-developers.com/showthread.php?t=701835
Apprehensive about not being able to perform a nandroid backup, I proceeded anyways, but when I tried to create /data/flash_image I received an error: permission denied. So I'm positive I don't have root either.
So I went to this tutorial believing that I probably had a newer version (even though my notification bar is telling me I need to download the mandatory update) and followed these directions:
http://forum.xda-developers.com/showthread.php?t=718889
I repeated my previous steps, but was still no closer. Finally, I went to these directions:
http://forum.xda-developers.com/showthread.php?t=690762
but when I tried to update using the pc36img file, after it finished checking the file it said "Main version is older! Update fail! Do you want to reboot device?"
So I'm pretty much stuck. What can/should I do?
e:
Sprint HTC Evo 4G
Supersonic EVT3 Ship S-On
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
Well, you need to figure out what version the phone is in the bootloader as in what hboot version.. And also you need to see what hardware version. You are trying to use methods that WILL NOT work on a new Evo.
Yellowcard8992 said:
Well, you need to figure out what version the phone is in the bootloader as in what hboot version. And also you need to see what hardware version. You are trying to use methods that WILL NOT work on a new Evo.
Click to expand...
Click to collapse
Pretty much what this guy said.
You're going to need to use the new method for the 2.02 HBOOT since S-ON is present. If S-OFF was present you'd obviously be ready to go to flash a custom recovery and flash your ROM of choice.
Here's a guide to get your S-OFF with 2.02, follow it to the "T": http://forum.xda-developers.com/showthread.php?t=829045
Once you've got S-OFF and a custom recovery loaded, you'll just have to flash a ROM. Personally, I'd recommend Myn's Warm 2.2 RLS4. It's the fastest ROM I've used and looks/works the best, imo.
Yellowcard8992 said:
Well, you need to figure out what version the phone is in the bootloader as in what hboot version.. And also you need to see what hardware version. You are trying to use methods that WILL NOT work on a new Evo.
Click to expand...
Click to collapse
cosine83 said:
Pretty much what this guy said.
You're going to need to use the new method for the 2.02 HBOOT since S-ON is present. If S-OFF was present you'd obviously be ready to go to flash a custom recovery and flash your ROM of choice.
Here's a guide to get your S-OFF with 2.02, follow it to the "T": http://forum.xda-developers.com/showthread.php?t=829045
Once you've got S-OFF and a custom recovery loaded, you'll just have to flash a ROM. Personally, I'd recommend Myn's Warm 2.2 RLS4. It's the fastest ROM I've used and looks/works the best, imo.
Click to expand...
Click to collapse
Like all any other nerd in this forum on a thought about "How do I root this phone?" - Check the fkn specs of the phone to root with the instructions that has the details of your phone ONLY...gosh jeez peeoople where did we go wrong here?
Bad luck you wrote the wrong root method on a new females phone. >_<
Make sure you find out the Hboot version and the S-OFF has to be there for your phone to be flashed with a new rom / kernel for use.
What everyone said, but in case you don't know. To check your Hboot version boot to the bootloader (power on + vol down) to check your version.
cosine83 said:
Here's a guide to get your S-OFF with 2.02, follow it to the "T": http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
This is what I needed, thanks. Sorry, but it had been since the EVO launched since the last time I had to unlock one, sorry I wasn't completely versed in the nuances of hboot versions and the appearance of S-On. I'm glad someone was nice enough to simply post the correct guide.
Hi, I am have just got my HTC Desire Z/Vision and I am very new to rooting.
I checked on a lot of thread on how to root, s-off the phone before I can install custom ROM.
Some of the tread mention that I need to do firmware downgrade if my device has firmware version higher than 1.34, but I am not sure on my version and therefore I include my information below.
What is the easier way to root my phone?
If I use gfree, do I need to downgrade my firmware? Is there any side effect when I downgrade my firmware?
If I use VISIONary, do I need to downgrade my firmware?
Do I need to do S-Off in order to install custom ROM? or is rooting enough?
Hell a lot of question but I hope you guys can help me out with it.
Android version: 2.2.1
Baseband version: 12.28e.60.140fU_26.04.02.17_M2
Kernel version: 2.6.32.21-g6e170e7
Build number: 1.82.707.1 CL317545
Software number: 1.82.707.1
cruxiality said:
Hi, I am have just got my HTC Desire Z/Vision and I am very new to rooting.
I checked on a lot of thread on how to root, s-off the phone before I can install custom ROM.
Some of the tread mention that I need to do firmware downgrade if my device has firmware version higher than 1.34, but I am not sure on my version and therefore I include my information below.
What is the easier way to root my phone?
If I use gfree, do I need to downgrade my firmware? Is there any side effect when I downgrade my firmware?
If I use VISIONary, do I need to downgrade my firmware?
Do I need to do S-Off in order to install custom ROM? or is rooting enough?
Hell a lot of question but I hope you guys can help me out with it.
Android version: 2.2.1
Baseband version: 12.28e.60.140fU_26.04.02.17_M2
Kernel version: 2.6.32.21-g6e170e7
Build number: 1.82.707.1 CL317545
Software number: 1.82.707.1
Click to expand...
Click to collapse
First, welcome to the boards, it's always nice to welcome people into the world of rooting and flashing (the android kind!).
To start, you will have to get ADB installed and working. To do this, download the Android SDK from here: http://developer.android.com/sdk/index.html . make sure you have the Java SDK and JDK installed as well as the Android SDK requires that as a requirement.
Based on your information, you have the 1.82 system software and will need to downgrade. I am not 100% sure if this guide will be applicable to you since it was written for the 1.72, but look at this guide here: http://forum.xda-developers.com/showthread.php?t=905261
The above guide will help you in downgrading to 1.34, gaining root with gfree/rage, SIM-Unlock and S-OFF, installing ClockWordMod (a.k.a CWM) and flashing a new and shiny ROM for you.
I can completely understand how confusing alot of these guides can be, I spent about 3 hours trying to do the same thing as you a month ago. A year ago, I did the same thing with my old HTC Hero! So if you have any questions, just ask away. XDA is a great community.
Have fun
Thank you for your reply. It does help me to go through the right direction.
Understood that I need to downgrade my build to 1.34, but is there any major difference between my current build and the older build?
After following the guide to downgrade and install CWM, will it also allow me to backup my current official ROM?
As I love HTC Sense too much such a pity that I need to let it go. I am thinking of flashing back to the official ROM when I have the need to.
XDA is indeed to a great community. Great helps from great people
cruxiality said:
Thank you for your reply. It does help me to go through the right direction.
Understood that I need to downgrade my build to 1.34, but is there any major difference between my current build and the older build?
After following the guide to downgrade and install CWM, will it also allow me to backup my current official ROM?
As I love HTC Sense too much such a pity that I need to let it go. I am thinking of flashing back to the official ROM when I have the need to.
XDA is indeed to a great community. Great helps from great people
Click to expand...
Click to collapse
There are alot of fixes and improvements that HTC made between the 1.34 version and the newest 1.84 version. Those would be found with HTC in their changelogs. Also, each of these upgrades breaks the root access that the devs have created. Similar to that of iOS breaking each jailbreak method with each new version of iOS that is released (you will understand this analogy if you have an iPod Touch or something along those lines).
After gaining root, SIM-Unlock and S-OFF, installing CWM would allow you to perform a NANDroid backup (an EXACT image of your current installed ROM) so that you can go back to it at a later time.
If you are like myself (and seems that you are) you love how HTC's Sense overlay works and it just gets you. Keeps things simple while being infinitely customizable. When you do get around to flashing, I would recommend Virtuous as your ROM of choice. It is what I am running right now with no ill effects. The link to Virtuous is in my signature below.
If this is your first time flashing a custom ROM on an Android device, I can promise you that you will NEVER have a reason to go back to the stock ROM unless your phone is damaged physically and needs warranty repair. Even then, it is sometimes cheaper and easier for you to order the parts online and DIY your repairs (did it for my brother's BB Storm when he broke the screen).
Going back to my Hero, I have the stock Android 1.5 image saved somewhere, but I have never had to go back to it. Always found another newer/better custom ROM to flash. With my current DZ, I was fortunate enough to have stumbled onto Virtuous.
Have fun!
Yes, you're right. I like HTC Sense so I don't know if I will get used to the custom ROM without it.
I have checked on the Virtuous ROM previously and I will give it a try.
Yes, I saw plenty of decent ROM, they have nice UI but as you know first time rooting does give me goosebumps.
Will try it and I hope everything goes smooth.
Thanks a lot for your kind explanation, it does save me time in putting up all the pieces together
I bumped into a problem as I try to downgrade my firmware.
I followed the guide on this thread http://forum.xda-developers.com/showthread.php?t=905261 and I encountered error on step 11, when the phone goes into bootloader mode and tries to scan PC10IMG.zip file that I copied into the SDCard.
It said 'CID' incorrect!, Update Fail!
Anybody knows why I might have this issue? Is this because of the firmware difference as mentioned by Athrun88?
cruxiality said:
I bumped into a problem as I try to downgrade my firmware.
I followed the guide on this thread http://forum.xda-developers.com/showthread.php?t=905261 and I encountered error on step 11, when the phone goes into bootloader mode and tries to scan PC10IMG.zip file that I copied into the SDCard.
It said 'CID' incorrect!, Update Fail!
Anybody knows why I might have this issue? Is this because of the firmware difference as mentioned by Athrun88?
Click to expand...
Click to collapse
As stated in the thread you are using to downgrade, your CID must be one of the following:
g4rb4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Click to expand...
Click to collapse
IF its not in the above list you must make a gold card first then use the thread that you listed to downgrade. To check your CID run the following commands:
check with:
Code:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
There is a link in the thread you listed on how to make a gold card. The method you are trying is comfirmed to also work with 1.82. So the reason you are having problems is NOT because your on 1.82 firmware, more than likely your CID is not listed above. Solution = GOLDCARD.
Thank you for the reply.
I have looked into the Goldcard method (http://forum.xda-developers.com/showthread.php?t=832503) and actually spent my time trying to accomplish the result.
Part 1 and part 2 are pretty straightforward but now I bumped into another problem when I tried to do part 3 as it requires me to have root access to execute the command.
I have tried to get the root access by following methods from different threads such as using rage (http://forum.xda-developers.com/showthread.php?t=834228).
For this method, I tried to do temp root and I am stucked on step 5. After launching 'Terminal Emulator' and running 'rage'. I can't seem to run the 'Terminal Emulator' again. When I launched it, it Force Closes. Tried to launch it again, my phone just displayed black screen and keys doesn't seem to be responding not till I off and on the phone (not reboot).
I also tried to use Visionary too but doesn't seem to have any luck.
Is there any other method I can try to get the root access?
Another question is after I followed Part 1 of the steps in http://forum.xda-developers.com/showthread.php?t=832503, when I boot up my computer, I can't seem to go to Windows. I am sure I selected physical disk instead of logical disk but I don't know why this happen. Anybody encounter the same problem?
I'm currently in the situation of wanting to root and S-off my Desire Z in order to update, either to official or (more likely) Virtuous ROM.
However before I do so I have a couple of questions.
1) How do I back up everything on my phone? I know my contacts and calendar will be fine as they are from my google account, also my email will be ok as that is also my google account. Photos etc I can just copy to my PC but what about all the apps I've installed, and my progress in them, my pair bluetooth devices, my wifi access points, my mesage apn settings etc etc?
I have tried Titanium Backup but not having paid for the full version, the info it gives you is a little limited so i'm not sure what it's backed up etc?
2) I currently have root via using Visionary, do I need to unroot and then go through the process with all the adb stuff? Also, will i need to uninstall the SuperUser I have installed?
3) I think my ADB is setup as I managed to get it to boot the phone into the bootloader, but when Itried to check my INFOCID using
Code:
fastboot oem boot
I got an error message saying that fastboot was not a recognised function (or something similar to that) Is this a problem?
ANy help really really appreciated as I am a total newb with Android but would love to move to a more up-to-date software version as I am currently on 1.34.
Thanks in advance.
valve90210 said:
I'm currently in the situation of wanting to root and S-off my Desire Z in order to update, either to official or (more likely) Virtuous ROM.
However before I do so I have a couple of questions.
.......................... lots of questions...............
ANy help really really appreciated as I am a total newb with Android but would love to move to a more up-to-date software version as I am currently on 1.34.
Thanks in advance.
Click to expand...
Click to collapse
You could wait until HTC releases a OTA update for your phone. Or as a alternative and avoiding being impatient, you could do a lot of reading and learning on this site to apply a custom rom. It is not that difficult at all, but do not expect a step by step walking trough the minute you ask for something here.
HLeenders said:
You could wait until HTC releases a OTA update for your phone. Or as a alternative and avoiding being impatient, you could do a lot of reading and learning on this site to apply a custom rom. It is not that difficult at all, but do not expect a step by step walking trough the minute you ask for something here.
Click to expand...
Click to collapse
Wow, thanks for your helpful post...
I've done loads of reading on the forum and have gone rather round in circles. I think I know what I'm doing but seeing as someone else who is new to it had posted a thread I thought I'd also ask a couple of questions that I had which were pertinent to the discussion, to firstly find out for myself and secondly to help anyone else that might be finding the thread otherwise useful.
I think I have sorted the abd problem I was having, it seems that various tools have moved to different folders in the latest version of the android sdk so when I was trying the "fastboot" line it was nt findint fastboot.exe as it was in a different folder.
Secondly I'm fairly happy to give the gfre stuff a whirl but before I do I just wanted a little confirmation about backing everything up...not a huge ask really and fairly essential I would say!
valve90210 said:
Wow, thanks for your helpful post...
I've done loads of reading on the forum and have gone rather round in circles. I think I know what I'm doing but seeing as someone else who is new to it had posted a thread I thought I'd also ask a couple of questions that I had which were pertinent to the discussion, to firstly find out for myself and secondly to help anyone else that might be finding the thread otherwise useful.
I think I have sorted the abd problem I was having, it seems that various tools have moved to different folders in the latest version of the android sdk so when I was trying the "fastboot" line it was nt findint fastboot.exe as it was in a different folder.
Secondly I'm fairly happy to give the gfre stuff a whirl but before I do I just wanted a little confirmation about backing everything up...not a huge ask really and fairly essential I would say!
Click to expand...
Click to collapse
You can use Astro File Explorer to back up your apps, Call Logs Backup and SMS backup will backup the sms threads and call logs or if you want to spend a couple of bucks Root explorer works well for me also. Once you have CWM you can make a Nandroid backup and will have an exact image of you phone at that point in time that you can go back to. I am waiting for my DZ to arrive and currently using an Inspire and 2 Captivates that other than minor differences in the procedures the backup maintenance is the same. The problem is that if you downgrade to a rom that allows CWM you cant back up the existing newer one. There are copies of it out there though. Just be careful if trying to go back to it and read carefully as I understand there are possible problems going back if the correct procedures are not followed. Good luck to you and as the previous poster stated about educating yourself, I fully agree. Read until you understand then read again to make sure you are not missing something. Follow directions EXACTLY and it usually avoids problems.
Sorry I see you are on 1.34 which I think means that once you get S-Off and root you can download rom manager from the market, install clockworkmod and you will be good to go with Nandroid backups.
Hello there,
I am new to modding android devices so i just have a few questions to ask about my HTC Desire HD and installing (flashing?) the JellyTime (ROM?) software onto my phone.
I've read through lots of posts but there quite a bit of terminology that gets flung around which im not understanding but i think i know what i have to do.
But my main question are, since I'm running Android 2.3.5 Sense 3.0 rooting my phone has become quite hard for me as every program i look at says I need to downgrade. I read [How to] ROOT without the Hack Kit and I'm guessing "IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:" applys to me.
But when i go to this post i have no idea whats going on or what a gold card is or what its supposed to do.
So as im a complete noob and i have sort of tried on my own i was hoping if anyone could lead me through what im meant to do to get my Stock DHD to the stage where its running JellyTime android 4.2.2?
I also found a download for AAHK which has been removed by its developer as far as i know and i dont know what XDA's rules are if i was to repost the download link. The problem with the AAHK is that its requires a downgrade of my phone and when it tries to do that it needs to download a RUU(???) which was hosted on the developers site which is now removed and it returns errors for the RUU
Kirity said:
Hello there,
I am new to modding android devices so i just have a few questions to ask about my HTC Desire HD and installing (flashing?) the JellyTime (ROM?) software onto my phone.
I've read through lots of posts but there quite a bit of terminology that gets flung around which im not understanding but i think i know what i have to do.
But my main question are, since I'm running Android 2.3.5 Sense 3.0 rooting my phone has become quite hard for me as every program i look at says I need to downgrade. I read [How to] ROOT without the Hack Kit and I'm guessing "IF YOUR BUILD VERSION IS NOT SUPPORTED TO UPDATE THEN:" applys to me.
But when i go to this post i have no idea whats going on or what a gold card is or what its supposed to do.
So as im a complete noob and i have sort of tried on my own i was hoping if anyone could lead me through what im meant to do to get my Stock DHD to the stage where its running JellyTime android 4.2.2?
I also found a download for AAHK which has been removed by its developer as far as i know and i dont know what XDA's rules are if i was to repost the download link. The problem with the AAHK is that its requires a downgrade of my phone and when it tries to do that it needs to download a RUU(???) which was hosted on the developers site which is now removed and it returns errors for the RUU
Click to expand...
Click to collapse
What does make you think that your build is not supported? The hack kit is retired and unsupported, are you going to repost and support a tool that might leave you with a brick? Even you have all the files needed by the kit to work?
I suggest that you do some more research before doing anything to your device. Read the guide in my signature and visit the Ace Think Tank thread.
glevitan said:
What does make you think that your build is not supported? The hack kit is retired and unsupported, are you going to repost and support a tool that might leave you with a brick? Even you have all the files needed by the kit to work?
I suggest that you do some more research before doing anything to your device. Read the guide in my signature and visit the Ace Think Tank thread.
Click to expand...
Click to collapse
Because the program in your root guide said that my software version is not supported, I have skimmed through the guide and I will read it properly on the weekend.
Why would it brick my device it has worked on all the device that used to use it? as I have read it used the be the go to tool for root and S-OFF. I thought the developer just didn't like the scene anymore are removed all his work i thought i still worked but the downloads where hard to find.
Could you please tell me if i can run JellyTime on my device?
Also reading your guide i didnt understand the information about rooting where you talked about S-OFF wont be needed to run CWM recovery as i read somewhere that CWM recovery needed to have S-OFF to work.
Thanks for your help.
Kirity said:
Why would it brick my device it has worked on all the device that used to use it?
Click to expand...
Click to collapse
It hasn't worked on all the devices. It was the go-to tool for S-Off, but read back through the forums; many people (usually those who did not read well) have run into problems and needed support. And if you post it for others in a responsible manner, you need to support that possibility.
Kirity said:
Also reading your guide i didnt understand the information about rooting where you talked about S-OFF wont be needed to run CWM recovery as i read somewhere that CWM recovery needed to have S-OFF to work.
Click to expand...
Click to collapse
You don't need S-Off to install a custom recovery.
glevitan said:
What does make you think that your build is not supported? The hack kit is retired and unsupported, are you going to repost and support a tool that might leave you with a brick? Even you have all the files needed by the kit to work?
I suggest that you do some more research before doing anything to your device. Read the guide in my signature and visit the Ace Think Tank thread.
Click to expand...
Click to collapse
____________
My phone says my build(ROM) version is 3.12 but the hboot program says its 3.13
the root kit wants me to update but the ROM updaters says updating from 3.13 to 3.13 but the phone still says 3.12 ????
__________________
I ran the ROM updater outside of the ace root kit. Now it realises that the ROM is still 3.12... But not when i try to update the ROM it returns error 191????
Thanks for the help
I used the HTCDev procedure to unlock the bootloader (updating my hboot to the .29 version going from the .27 version), I then installed CWM. From there I flashed a CM10 ROM selecting the zip from the SDcard in recovery, then the last step was running the command "fastboot flash boot boot.img" after extracting the boot.img file from the ROM file.
I have no real use for root or anything, I just wanted jellybean, and it's well worth it.
Install download oneclick root and your problem will be solved.
Sent from my Desire HD using xda app-developers app
MisterBuggie said:
I used the HTCDev procedure to unlock the bootloader (updating my hboot to the .29 version going from the .27 version), I then installed CWM. From there I flashed a CM10 ROM selecting the zip from the SDcard in recovery, then the last step was running the command "fastboot flash boot boot.img" after extracting the boot.img file from the ROM file.
I have no real use for root or anything, I just wanted jellybean, and it's well worth it.
Click to expand...
Click to collapse
I'm currently running 2.00.0029? But at the top it says *** LOCKED (OOW) *** ??
Do i not need an unlocked bootloader to get jellybean on my phone?
Kirity said:
What defines a unlocked boot loader? how do I find out. I'm currently running 2.00.0029? But at the top it says *** LOCKED (OOW) *** ??
If this is an unlocked bootloader can you walk me through getting jellybean on my phone?
This would be awesome! thanks a bunch.
Click to expand...
Click to collapse
Read the Ace Think Tank linked in my signature. You are not unlocked, but you can use the Tank-linked Easy Ace Root Tool to do so. As for a tutorial on flashing custom ROMs, the Think Tank has links for that too; no need for a separate walkthrough reinventing the wheel.
nothing works....
bananagranola said:
Read the Ace Think Tank linked in my signature. You are not unlocked, but you can use the Tank-linked Easy Ace Root Tool to do so. As for a tutorial on flashing custom ROMs, the Think Tank has links for that too; no need for a separate walkthrough reinventing the wheel.
Click to expand...
Click to collapse
Hi yeah as talked about above and in another post i have use the easy ace root tool but it requires me to upgrade my hboot and/or software. I'm running software 3.12.405.1 but I need to be running 3.13.000 apparently. It automatically downloads HTCDev's RUU but every time i run it it gives me the error 191 ROM not supported.
I have tried all variants of the RUU from the HTCDev website for my phone even for the wrong carries all give the same error.
I read somewhere that i may need a Goldcard since i carried out an OTA update on my phone and its tied to an orange (ee) contract?
However the goldcard generating website is now offline due to hackers and they said they are shutting down and the only person i could find who said they could generate goldcards (geene pool) isnt responding to my PM.
so I'm all out of luck.
Kirity said:
Hi yeah as talked about above and in another post i have use the easy ace root tool but it requires me to upgrade my hboot and/or software. I'm running software 3.12.405.1 but I need to be running 3.13.000 apparently. It automatically downloads HTCDev's RUU but every time i run it it gives me the error 191 ROM not supported.
I have tried all variants of the RUU from the HTCDev website for my phone even for the wrong carries all give the same error.
I read somewhere that i may need a Goldcard since i carried out an OTA update on my phone and its tied to an orange (ee) contract?
However the goldcard generating website is now offline due to hackers and they said they are shutting down and the only person i could find who said they could generate goldcards (geene pool) isnt responding to my PM.
so I'm all out of luck.
Click to expand...
Click to collapse
Ah. Then yes, you are just out of luck. I know that there's a way to generate a goldcard yourself instead of having Gene Poole do it (I believe by using a specific ActivePerl version, a specific Crypt SSLeay module, and the goldcard generating script) but I haven't had the inclination to do it myself. If you really want it you could give that a shot.
bananagranola said:
Ah. Then yes, you are just out of luck. I know that there's a way to generate a goldcard yourself instead of having Gene Poole do it (I believe by using a specific ActivePerl version, a specific Crypt SSLeay module, and the goldcard generating script) but I haven't had the inclination to do it myself. If you really want it you could give that a shot.
Click to expand...
Click to collapse
Erm on the off chance i tried unlock my phone again and i think its worked!!!!! this is amazing!!!
just a question can I change the SDcard in my unlocked phone or will it affect the boot loader?
Kirity said:
Erm on the off chance i tried unlock my phone again and i think its worked!!!!! this is amazing!!!
just a question can I change the SDcard in my unlocked phone or will it affect the boot loader?
Click to expand...
Click to collapse
Yes you can.
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2