This may be a lame post, but I keep seeing people talk about how roms will not work if you used unrevoked. I don't understand why there would be a difference. If you root, install a Engineering SPL and a recovery image....after that you flash with whatever you want. Why on earth would it matter? Once you have an Engineering SPL, and your system partition is writable, you can wipe the whole phone and put what ever you want on...why on earth would it matter if you used unrevoked??
Am I missing something? Are people just assuming that you aren't fully rooted?? If so they should really be more clear.
root yes but unrevoked doesnt unlock nand
Maybe I misunderstood, I thought NAND was locked by the HBOOT and I thought that by replacing your SPL with the Engineering SPL you were changing the HBOOT version, thus unlocking NAND.
I don't think Toast's root process does this. I thought it was the same as unrevoked and simply gave your root access to user space on the os via su. I thought that regardless of which version you used to gain your root, you still had to use Toast's unlock nand process to load the Engineering SPL and gain full nand r/w and load a permanent recovery image.
I think this is just a misunderstanding from most people about os level root vs engineering SPL/nand unlocking. If so, I wish people would just start referring to it in their ROM posts as "you must have unlocked nand or be running the engineering SPL" vs tying that in with root, as it's pretty confusing. Maybe I'm wrong though, I haven't had my evo long and alot of my knowledge about root/SPL is from my previous experience with my mt3g.
Thanks
if you just run unrevoked you don't get unlocked nand, so you flash the engineering spl and you get unlocked nand so your not running "just" unrevoked, lots of people run unrevoked and never flash the engineering spl but they think they can run anything and everything, then they are surprised when they can't ... try just running unrevoked without unlocking nand and see what happens. if everything works properly let us know. Unrevoked just opens a hole while in HBOOT as soon as HBOOt is closed poof no more hole. so yes you can flash while the whole is open then try to read write to the /system and see what happens. Sorry this was a jumble ....
I had so many issues after running Unrevoked and even Simpleroot. It was my first experience with flashing new ROMs on any Android phone so I wanted to do it the "easy" way to save time.
The funny part is that I wasted so much time trying to get things working that the 20 minutes I spent doing it all from scratch were no big deal. Wish I had done it that way from the start.
Once I went through the 2 part method posted on this forum I have had no issues that weren't just related to unsupported features.
neodorian said:
I had so many issues after running Unrevoked and even Simpleroot. It was my first experience with flashing new ROMs on any Android phone so I wanted to do it the "easy" way to save time.
The funny part is that I wasted so much time trying to get things working that the 20 minutes I spent doing it all from scratch were no big deal. Wish I had done it that way from the start.
Once I went through the 2 part method posted on this forum I have had no issues that weren't just related to unsupported features.
Click to expand...
Click to collapse
Toasts?
I am pretty sure I want Amon-Ra...and not clockwork though. Hmm.
Sorry, yes it was Toast's method. All of the simplified versions gave me issues where certain things weren't done properly and since I hadn't done it manually with any kind of real feedback it caused issues down the line. I had to start over from the beginning to get things all working properly. Not sure where I screwed up but Toast's method fixed it.
I also use Amon RA's recovery. Only thing about that is that ROM updater that comes with Fresh's ROM doesn't want to work without Clockwork. I'll probably just delete it.
Related
I have the Android Dev Phone 1 and I had just gotten through rooting it following the wiki's instructions, I wanted to try to install Hero with the Rosie UI so I was following these directions to then flash it:
http://forum.xda-developers.com/showpost.php?p=3816278&postcount=3
But I was in the process of doing that, I had two micro SD cards with the proper updates on each, and when it came time to switch the cards(I didn't hit any buttons or anything by accident) I switched them, hit Alt +X, nothing happened. Nothing. I tried it a few more times and still nothing. All other combos of letters and trying to get it to respond in any way did nothing. So I pulled the battery out and now I cannot get past the G1 screen. It won't do the boot where you hit the camera button and power or the home + power boot. It just sits at the black screen with the G1.
I tried getting the ADB devices to recognize it and no dice. I can't get it to do anything other than go to the black screen. I tried searching the forum and I scoured google but all the things I could find were where you could get some kind of input beyond the screen.
I'm kinda mad as I just got this phone and paid $450 some bucks for it, can someone help me out? I'm on Vista X64 and Ubuntu X64. Thanks in advance to anyone who can help me unbrick my $450 paperweight.
you need to update the from the original recovery, which im guessing you still have to swithch to one of these. http://forum.xda-developers.com/showthread.php?t=455860 then you can update to the SPL H
Hard SPL is the recommended one. Which in turn will give you the list feature Alt-x
Truculent said:
I have the Android Dev Phone 1 and I had just gotten through rooting it following the wiki's instructions, I wanted to try to install Hero with the Rosie UI so I was following these directions to then flash it:
Click to expand...
Click to collapse
So is your phone a "PVT" or "DVT"? If it's a DVT and you tried to install Haykuro's SPL 1.33.2005, then you are almost certain to have a paperweight. I believe it's mostly consensus that the DVT phones brick if you go to that SPL. There are a bunch of threads here on it.
Truculent said:
I have the Android Dev Phone 1 and I had just gotten through rooting it
Click to expand...
Click to collapse
Aren't ADPs rooted out of the box?!
You have to install the new SPL and JF's recovery image before you to to Hero/Rosie.
ADP's certainly do provide root out of the box, so no need to go to the trouble.
@Truculent:
Sounds like this is what happened;
1) installed rc29 for tmobile branded dream (mistake),
2) rooted that and probably installed some older radio image (or left original radio),
At this point, though you wasted time and risked screwing it up, you were probably still OK. The fact that you would even attempt the previous steps says something though...
3) reversed the sdcards and accidentally installed SPL before radio upgrade.
Its bricked and nothing you can do for now. Most likely this will require a physical disassembly and reprogramming to repair.
Honestly, anybody who could make a bonehead move like rooting a prerooted device by installing a root-locked firmware shouldn't be messing with SPLs. In other words, you deserve what you got. Particularly since you DONT NEED the modified SPL for what you were attempting! There's a system/apps to SD approach to fitting it with the standard disk layout.... which you could have stepped to *directly* from a stock ADP1 without ANY risk of bricking.
lbcoder said:
ADP's certainly do provide root out of the box, so no need to go to the trouble.
@Truculent:
Sounds like this is what happened;
1) installed rc29 for tmobile branded dream (mistake),
2) rooted that and probably installed some older radio image (or left original radio),
At this point, though you wasted time and risked screwing it up, you were probably still OK. The fact that you would even attempt the previous steps says something though...
3) reversed the sdcards and accidentally installed SPL before radio upgrade.
Its bricked and nothing you can do for now. Most likely this will require a physical disassembly and reprogramming to repair.
Honestly, anybody who could make a bonehead move like rooting a prerooted device by installing a root-locked firmware shouldn't be messing with SPLs. In other words, you deserve what you got. Particularly since you DONT NEED the modified SPL for what you were attempting! There's a system/apps to SD approach to fitting it with the standard disk layout.... which you could have stepped to *directly* from a stock ADP1 without ANY risk of bricking.
Click to expand...
Click to collapse
I thought it was rooted when I bought it, but I was not able to install programs that needed root. They told me I needed root. I'm kicking myself right now. But yes, that sounds like what I did. This is my first time of doing anything with cell phones, I'm trying to learn. I didn't see anything regarding the ADP's so I figured the T-mobile G-1's were the same, my fault. I spent hours reading this forum and the wiki and didn't see anything concerning this kind of thing.
Is there any way I can do the disassembly and reprogramming? I did DD-WRT stuff on my routers, is there a way to JTAG or something similar to these phones? Oh, and this is a PVT phone.
Root is hidden from programs for security reasons (keep programs from going nuts and messing up your system), but a little bit of "adb shell" would show it to you.
I really doubt that PVT or DVT matters. The distinction was guessed at by trying to follow the pattern of bricking BEFORE it was determined that the radio version was the common factor. Even then, there was really no conclusive info showing that DVT boards were more prone to bricking, I think there was a sample of about 14 devices bricked back then, of them 6 were PVT and 8 were DVT.... you see how weak the evidence is? It would make a statistician cringe. See this: http://forum.xda-developers.com/poll.php?do=showresults&pollid=1523 - only the number of PVT bricks has increased because everyone got scared of trying to write the bootloader to DVTs, but you can see that there are some DVTs that flashed fine. 2 at least.
As for hooking up a jtag... there was someone looking into that, but I haven't heard of any repair procedures yet. Note that though it hasn't been done yet, there is no question that it is possible since the chips must have been programmed by some means initially.
So I guess it really is easy to brick a MT3G - can't fastboot, can't enter recovery.
Just stays on the MT3G boot screen.
I've tried all the boot key combinations, does anyone have any magic solutions that may work?
It was rooted just fine (from the first day rooting was discovered, using the gold card method). Tried to upgrade to a CyanogenMod, and somehow messed things up. I suspect I screwed up when I flashed the radio.
Hmph.
Why did you flash a "new" radio...?
The radio that comes standard as a packaged feature for the T-Mobile USA version of the HTC Sapphire (MT3G) is 2.22.19.26I - there was NO NEED for that adjustment. I'm not suggesting that flashing a new radio is what corrupted your device, but it certainly could have contributed to the eventual cause.
The One-Click Root Method is the safest way (until patched via Google 1.6 build - also known as Donut) to ROOT your MyTouch. I've used that for three various Android devices, all of which functioned properly immediately after. No flashing of upgraded radios, SPLs, etc.
Finally, from the beginning - as any ROM flasher should know, you SHOULD HAVE backed up your STANDARD, T-MOBILE PROVIDED, Cupcake v1.5 build using NANDROID from the Recovery image. If that is the case, restore those settings and start all over with the "rooting" process using the One-Click method via the Recovery Flasher application.
Good luck.
damn i think i brick my phone after loading a radio ugh it sux
Again.
Tobi87 said:
damn i think i brick my phone after loading a radio ugh it sux
Click to expand...
Click to collapse
Re-read what I posted previously.
The MyTouch comes standard with the latest radio and and SPL (even if considered PERFECT) doesn't prevent you from running any of Cyanogen's latest builds. I don't see why you thought that flashing a "new" radio was going to do something special. As for the "Gold Card" method...I don't see why you didn't think to try the easier, safer, much less work type of method. THE ONE-CLICK ROOT METHOD!
Hello all,
Here's what happened - I DL'd the app 'ROM Manager' from the Android Market, installed and allowed this app to be the recovery for my MT3g (non-Fender and non-headphone jack version).
Suffice it to say that the ROM Manager app jacked up my phone... none of their items worked for me. I uninstalled the ROM Manager and now when I tried to go to recovery mode (power + Home) I get nothing but stuck on the MT splash screen
My phone is rooted, originally ran the recovery-RA-dream-v1.6.2 recovery and am currently running a 2.1 ROM.
I have tried to redo the flashrec-1.1.3x and this does not work.
Where do I go from here? I'd like to be able to partition my new 8GB SD card and I can't even do that...
Thanks in advance.
If your phone is rooted, can't you just flash the previous working recovery via fastboot again?
-------------------------------------
Sent via the XDA Tapatalk App
You should be able to put the recovery image on your sd card and use the flash_image command from the terminal right? thats what i did
Mod. edit: not dev related, moved to general
twigster said:
If your phone is rooted, can't you just flash the previous working recovery via fastboot again?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Just to let you know, it is possible to root a mytouch without ever having installed an SPL that allows flashing though fastboot. I know from personal experience that the one-click flashrec method does this
adavis159 said:
Just to let you know, it is possible to root a mytouch without ever having installed an SPL that allows flashing though fastboot. I know from personal experience that the one-click flashrec method does this
Click to expand...
Click to collapse
I know, thats what I did as well.
But since then, till the date I changed to an engineering SPL, im pretty sure I have always done the subsequent changes to my recovery and spl using fastboot, even after starting with the 0010 SPL (which was at the time a problem SPL) and using flashrec to change the recovery before installing my first non stock rom, being cyanogen 4.x.x, still with the 0010 SPL.
I do know that it only became necessary for me to change my SPL when I wanted to try new radio ROMs (subsequently moved back, and took the chance to move to the 2010 engineering SPL) Before that I was actually too scared to change the SPL because of the brick threats.
I used the cursorsense rom thread instructions on how to change the radio and spl, and it worked great.
Maybe, so far, I have been lucky not to brick my phone. But I have always followed well documented threads on the dev section and so far so good, not excluding one or two times when I thought I had made a nice brick, but just persevered.
Fastboot is your friend, and so is XDA if you are nice to it and the good people who frequent it.
If you look through the threads, and in the development section, there are alot of areas where they give the commands necessary for a variety of actions, and peoples responses on whether it works.
I don't yet believe in the programs created to do everything for you, nothing against the devs, who are all great, just not quite happy enough with comments posted to try them out yet.
(I think my response was little longer than needed) ;-)
Thanks for the info guys...
Problem was I could not boot into fast boot - the recovery was not there.
What I ended up doing was unrooting then rerooting my phone, reloaded my ROM and went on from there...
That might have been the long way of doing things but it all worked out well.
Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Whiterin said:
Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Click to expand...
Click to collapse
I guess that I should be moving this to General since this is a Q&A and not a means to simplify what you are trying to accomplish.
Moving to:
Magic General
Discussion about the T-Mobile myTouch 3G, HTC Magic (general Q&A, tips & tricks)
Wow, do I know how you feel.... I recently got a Vibrant (galaxy s). So sine I got a new phone I unrooted my MT3g and sent it in on warranty since it was kinda scratched, so I can give it to my wife. Well with my first phone I was able to do the on click root since it came originally loaded with cupcake.... Well as it turns out if it comes pre loaded with donut you can't downgrade any more...lol So I had to do the gold card method.....it sucked.....
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Whiterin said:
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Click to expand...
Click to collapse
No, its not.... A good example is to root the vibrant you just flash a update.zip file...lol. But the sapphire/magic/mytouch is a great phone with allot of development support. But from what I understand one of the hardest roots..
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Whiterin said:
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Click to expand...
Click to collapse
the CID error tells me your gold card creation failed.
Check the process description at theunlockr.com. that worked for me.
My first mistake was formatting FAT and NOT FAT32. It must be formatted FAT32.
I used a 2GB PNY and it works great.
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Yes, the zeros are critical but as I recall theunlockr link above (paste and cut) takes care of that for you. The gold card is the hard part to get right.. The rest is very straightforward.
Thanks for the input guys. Going to try a few more things.
Alright. Following the instructions. Step by step, I am still getting "CID Incorrect! Update Fail!"
This is very frustrating as there isn't any reason it shouldn't be working...
Darklordzim said:
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Click to expand...
Click to collapse
Not to thread jack, you know you can use any GoldCard with any phone, as long as it was made properly.
Any ideas on why this one isn't working then? Saying "Incorrect CID" when I try to flash anything with it.
Not sure. I know it took me 3 tries to get mine working right.
Sent from my HTC Magic using XDA App
UPDATE: The HTC Developers official unlock does not seem to allow the flashing of most, possibly all custom ROMs. The best advice is to re-lock the bootloader using the official tool, and then use the Advanced Ace Hack Kit to root and S-OFF your phone.
I've seen quite a few threads in Q&A recently where people have used the official bootloader unlock at the HTCDev website, then tried to flash a custom ROM and got stuck. The most common problem seems to be that they get stuck in the bootloader, or they flash a ROM but it hangs at the splash screen.
The best advice so far seems to be to flash a stock ROM, re-lock the bootloader, and then use the Advanced Ace Hack Kit to get S-OFF and root in the "usual" way. However one poor guy couldn't even get that far and ended up sending his phone off to HTC, although I think he tried running the AAHK without re-locking his bootloader first.
I'm not an expert on what the official unlock does and how it differs from our usual S-OFF methods. The HTC website indicates that their unlock lifts security on the boot, recovery and system images, but not on radio or sim-locks. To me that sounds enough to flash a custom ROM, but I'm not an expert and clearly a lot of people are having trouble.
I think it might be helpful to have a warning here on the DHD forums - if you want to unlock your phone, use the AAHK or any of the similar tools here. Don't use the HTCDev unlock method - at least until we better understand what's causing people these problems.
If anyone understands the technical differences between the HTC tool and the Radio S-OFF methods, or what's causing people to have these problems, please explain here so we can all understand it better! I'm slightly worried when trying to help people with advice, because if I get it wrong I might make things worse for them. And I don't really want to use the HTCDev tool myself to experiment.
If the HTC unlock itself is fine, but people are doing something wrong after using it, then perhaps once we know what that is, it can be put in a sticky? Or if the best advice is to avoid the HTC unlock method altogether, perhaps that should be stickied instead? (Or is there already a warning up that I've missed?)
It would be good if we as a community could come up with some clear advice, and maybe save people a lot of stress and hassle.
Yes, as a clueless person I would really welcome any expert guidance on this, I want to install other ROMs and if I can do it via 'official' methods all the better.
I experienced this exact same problem. I was expecting that unlocking meant getting root access but obviously this was not not the case so then I used the Ace Hack Kit which got stuck at flashing the ROM for downgrade. It showed the message in a quick flash (I had to record the screen it to see it) stating that the zip file content was not correct. Luckily the guys at the IRC help channel pointed me directly to the cause... the bootloader was unlocked and re-locking it would solve it.
Unfortunately the 'fastboot oem lock' method did not work right away. I re-installed HTC-sync (removed it before according Ace guide) and this got it working again so that I could re-lock. After this the whole Ace procedure worked fine and I now have root.
My advise would be to at least include a line on re-locking before start in the EFFEN manual and ensure that HTC-sync is installed for the relock (and remove it afterwards of course)
Thanks pamarama, that's exactly the kind of info I was hoping for regarding HTC Sync.
Do you know if AAHK also requires a working ROM on the phone before you start?
Some people don't have a working ROM, so I've been recommending that as well as re-locking the bootloader, they flash an RUU so there's a bootable ROM on the phone before they try AAHK.
Hi preacher65,
I honestly don't know if a working rom is required. I guess that the AAHK experts would be able to answer this question. I had a working rom at least but I can imagine that in order to do the downgrade the only thing that needs to be intact is the data that triggers AAHK to do the downgrade. If that flash succeeds you should have a working rom again.
From reading other threads, what I think the issue is that one simply can't install a rom. After flashing a rom one has to install a new boot image to actually get it to boot
The problem with HTC Dev unlock is that it doesn't allow boot.img to be flashed in any mode other than fastboot.
You can flash a custom rom, but then have to extract the boot.img from the zip and flash it via fastboot. Thats why everyone gets stuck on splash screen.
-Nipqer
pamarama said:
Hi preacher65,
I honestly don't know if a working rom is required. I guess that the AAHK experts would be able to answer this question. I had a working rom at least but I can imagine that in order to do the downgrade the only thing that needs to be intact is the data that triggers AAHK to do the downgrade. If that flash succeeds you should have a working rom again.
Click to expand...
Click to collapse
Thanks - I think you might need a working, rooted ROM to get SHIP S-OFF. At least you did in the days before the AAHK. Not sure if that works any differently. I'll check the manual to see if explains how it works.
marsdta said:
From reading other threads, what I think the issue is that one simply can't install a rom. After flashing a rom one has to install a new boot image to actually get it to boot
Click to expand...
Click to collapse
Thanks, I think you're right. The HTC unlock says it unlocks the boot image, but it does seem as if people aren't able to flash a boot image as part of the ROM. Possibly due to most ROMs having custom kernels, perhaps?
I believe that all the developer opened firmwares still have restrictions in place, someone correct me if I'm wrong but that is generally what happens when a hardware manufacturer releases an unlocked bootloader. Your best bet is to use the Advanced Ace Hack kit then use Android Terminal Emulator to flash your bootloader with the ENG S-OFF version. Then you have complete control and freedom in your device.
I would type up all the specifics but there are many guides on the subjects above.
MP2E said:
I believe that all the developer opened firmwares still have restrictions in place
Click to expand...
Click to collapse
Thanks, I'm sure you're right. What I'm really trying to find out is what those specific restrictions are - or failing that, just come up with a solid, workable solution for those people who have already tried the HTC unlock and are now stuck.
So far the solution seems to be to re-lock the bootloader and then use the AAHK. But some people I've tried to help in Q&A have been unable to flash a PD98IMG.zip or RUU, even after re-locking, to get a stock ROM back on their phone so they could run the Hack Kit.
FWIW my own phone was rooted over a year ago, using Visionary and running sfjuocekr's scripts inside Android Terminal Emulator to fhash hboot and CWM manually from the command line. Which is why I'm not very familiar with what the AAHK needs to run, but I assume it needs a working ROM to get Radio S-OFF.