Hello I have followed all the steps but keep getting the same message "module failed to load'. I have attached a screenshot. Could someone please help me out? any help would greatly be appreciated.
Are you trying to re root? Its weird that it lists faux's kernels...what exactly have you done and are trying to achieve?
thanks for you quick response. I am rooted already. Im actually interested in the sim unlock as I will be going overseas soon. I just bought the phone from someone and it was rooted already. Im guessing he was running a custom kernal? Could this be the issue?
Am wondering if it already being rooted with gfree would cause this problem-am unsure. Do you know which version of hboot you have? .86 or .85? If its the eng .85, boot into it and go to system info and see if it says cid-111111 or something like that..if you have .86, try to search your sd card for "part7" (without quotes) as this file would have been created if they used gfree in the first place. If you have either (or both) than you likely are rooted with gfree and are already sim unlocked. Maybe someone else knows some commands through terminal emulator or adb that can tell you if a phone has sim unlock.
So doing a search in that thread for "module failed", came across a few posts of people saying you had to be running the stock rom for gfree to unlock everything...do you know what rom is currently installed?
Related
alot of people got off track in my last thread so i'm going to make this crystal clear.
i bought a my touch 3g
it came with 32B
this means i cannot currently just flash my phone to root. i get an error stating "Main version is older"
everything i have read states the gold card method does not work anymore.
here is what i need: to flash the "sappimg" to my phone thus having root, can anyone on all of xda help me? please. i need custom roms.
you can hit me up on g talk I'm not good at it but I can try to help you
sn is joseberrioramirez
trexxcrap2 said:
alot of people got off track in my last thread so i'm going to make this crystal clear.
i bought a my touch 3g
it came with 32B
this means i cannot currently just flash my phone to root. i get an error stating "Main version is older"
everything i have read states the gold card method does not work anymore.
here is what i need: to flash the "sappimg" to my phone thus having root, can anyone on all of xda help me? please. i need custom roms.
Click to expand...
Click to collapse
I'm having the same problem, but it has nothing to do with the fact you have a 32B board. My last MT3G was a 32B, rooted with ease. However, T-mobile just sent me a replacement under warranty. Still a 32B, but with a different SPL. Its a perfected SPL 1.33.0007. I have not been able to root this yet and I've tried every method possible. The goldcard method is supposed to be the only way to root this as of right now, but it didn't work for me. I tried multiple SD cards and converted them to goldcards. I tried multiple SAPPimg files. Both zip and nbh files. No go. Some have claimed to have rooted this SPL but never seem to give much information as to how they did it, which makes me wonder. Anyway, check your SPL, post your specs on here and I'll let you know what can be done.
I have rooted that spl
if you want help PM me.
shadow_wing said:
if you want help PM me.
Click to expand...
Click to collapse
I PMed you, any help would be GREATLY appreciated.
here is the sappimg i used(since no1 ever posts it)..aslo when makin ur gold card go 4rm line 0000 to 0170 that is what really messes up the card if done wrong!! if u need a link to the post let me know..i will help as much as i can
P.S. sdcard must be inside phone to get the info you need to make the goldcard.
Edit: where should i upload it?
check theunlockr.com
they have step by step instruction as to how root and flash your phone. They also have videos in case you are not sure if you are doing it right or wrong.
PermROOT said:
Hello Phateless do you remember me? lol I am always on diff name so ya.
But yes PD15IMG.zip is not the golden solution to everything. It all depends on how you originally rooted your MT4G as VISIONary+ (TempROOT) and root.sh (PermROOT). In that case your S=OFF security off flag is dependent on the eng hboot which was pushed to /dev/block/mmcblk0p18 during PermROOT.
Now since its not true security off once you have newer radio. You try to run PD15IMG.zip (Sense 2.2.1 Rom/Radio 26.03.02.26_M) after the first update which is stock hboot you would be locked due to it changing S=ON thus on next step it will fail due to the image being older than originally on which is currently flashed which would be the radio. In this case your in a point where you shouldn't be as you can be locked out and no way to reroot. which I am working on finding. This also goes for gfree radio s=off.
If you do want to go back download PD15IMG.zip (stock radio 26.03.02.26_M) and then flash it once that is done then you can revert back to stock rom/radio using standard PD15IMG.zip (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Keep in mind unless the new PD15IMG.zip is out you can't revert it back if your locked out due to source being outdated than current image.
Click to expand...
Click to collapse
--------------------------
Found this post here in THE Bible. Trying to understand exactly what it means.
What is he saying here?
Can someone put this into noob terms please?
THANK!!!
I am not sure how to explain it furthermore as when I posted that it was clear to everyone, but ill try to simplify.
The original stock rom that came with our device was 2.2.1S and later we had GB2.3.X port and we mostly switched. Then came the radio rom which I hope I don't need to explain what the image does. So the standard stock radio that came with our device was 26.03.02.26_M. So later on as Panache came out we had leak to other radios which user could flash, thus changing it from stock radio to leaked radio. I hope it make sense up to there.
Now keep in mind we have 2 type of root meth as one is via TempROOT/PermROOT as I explained before via VISIONary+ which just push the eng_hboot and gives the illusion of S=OFF but the true security is not off as that is only done if you do the other rooting meth which is PermaROOT which disables the radio security completely.
Now the problem few users faced was when they flashed the leaked radio and they wanted to revert back to stock rom/radio via PD15IMG.zip for our MT4G (IDD15000). The installation would fail only for folks who had root via PermROOT as they never had true S=OFF thus once the eng_hboot is replaced with stock bootloader the security is disabled thus user can't complete the second part of the process which would be flashing the radio. So only solution was that they first revert back to stock radio or wait for newer radio because the source of the image inside PD15IMG.zip was older than the radio.img that was already flashed inside user's MT4G.
I hope it explains if not well IDK how to explain any better man :O
So if I'm understanding this all correctly, how I find out if this will affect me?
Where and what information should I provide you in order to find out if this will happen to me as well.
I'm getting ready to send my phone in for an exchange and was looking to flash PD15IMG.zip before doing this when I came across this post.
I rooted my phone with Visionary R14 and Terminal Emulator.
What other info do you need? Please let me know. Thank you.
At this point it wont affect you as thats obsolete due to TMoUS releasing newer stock rom/radio for our MT4G few months ago as Panache radio leak is older than the current stock rom/radio. As its GB2.3.4S which comes with the newest radio which is newer than any radio you flash. So the source of the PD15IMG.zip if you have the newest one then it will always be newer or equal to the radio.img already in device and it means in simple term it will flash the 2nd part. I hope it make sense as it should not affect anyone now. Even if it does all they have to do is run the current new PD15IMG.zip and it will fix the issue which user faced few months back.
nguyendqh said:
So if I'm understanding this all correctly, how I find out if this will affect me?
Where and what information should I provide you in order to find out if this will happen to me as well.
I'm getting ready to send my phone in for an exchange and was looking to flash PD15IMG.zip before doing this when I came across this post.
I rooted my phone with Visionary R14 and Terminal Emulator.
What other info do you need? Please let me know. Thank you.
Click to expand...
Click to collapse
If this is all about going back for an exchange, i recently did just this. Please see my post on the topic: http://forum.xda-developers.com/showthread.php?t=1241740
If all you did was the temproot/permaroot method via visionary+, and not the gfree method (gfree is actual s=off), then I believe some of the steps may be different. Specifically, you may be able to skip the whole bit about turning s=on again.
So which is it?
So rooted via Visionary R14 and being on Virtuous Unity (newest update)
I should be able to flash PD15IMG.zip from this link here: http://forum.xda-developers.com/showthread.php?t=863899
and have no problems yeah?
Sorry for all the questions. But yeah I'm only half to 75% following what you're saying.
I'm not advanced yet. =(
Thanks for the help again though.
Keep in mind PD15IMG.zip is the default system file for our device which is checked on the bootloader as our device ID is PD15000 thus getting the PD15IMG name. So PD15IMG.zip can be multi files as we have 2 of them 1 is 2.2.1 and newest one is 2.3.4 just look in the dev section you will find the newest PD15IMG.
http://forum.xda-developers.com/showthread.php?t=1059347
NEW-PD15IMG: PD15IMG_Glacier_Gingerbread_S_TMOUS_2.19.531.1_Radio_12.58.60.25_26.11.04.03_M_release_200756_signed
nicholasb said:
If this is all about going back for an exchange, i recently did just this. Please see my post on the topic: http://forum.xda-developers.com/showthread.php?t=1241740
If all you did was the temproot/permaroot method via visionary+, and not the gfree method (gfree is actual s=off), then I believe some of the steps may be different. Specifically, you may be able to skip the whole bit about turning s=on again.
So which is it?
Click to expand...
Click to collapse
I did not use the gfree method.
AggNA said:
Keep in mind PD15IMG.zip is the default system file for our device which is checked on the bootloader as our device ID is PD15000 thus getting the PD15IMG name. So PD15IMG.zip can be multi files as we have 2 of them 1 is 2.2.1 and newest one is 2.3.4 just look in the dev section you will find the newest PD15IMG.
http://forum.xda-developers.com/showthread.php?t=1059347
NEW-PD15IMG: PD15IMG_Glacier_Gingerbread_S_TMOUS_2.19.531.1_Radio_12.58.60.25_26.11.04.03_M_release_200756_signed
Click to expand...
Click to collapse
Thanks for all the help bro. I really really appreciate it.
Love all the help that the XDA community provides.
this guy definitely knows what he's talking about, provided help for me in the past
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.
S=off and run the gfree under terminal emulator
error popped and I have no idea about it, hope anyone out there can't gimme some suggestion
http'colon'//i46'dot'tinypic.com/11wave64.jpg
http'colon'//i48'dot'tinypic.com/2dhwmxt.jpg
I'm sorry I can't post any pic directly due to I'm a newbie
http://i46.tinypic.com/11wave64.jpg
http://i48.tinypic.com/2dhwmxt.jpg
There you go.
You aren't running stock, rootedfroyo. I believe gfree is supposed to run on the stock, rooted froyo ROM. I may be wrong though.
Anybody want to help us out?
So should i recover to stock and try gfree under it?
Hi Gents,
Before I get flamed, have been on XDA for with a HD2 for a while so bear with me - I have purchased a Mytouch and it has come with S-off but no root have tried pushing CWR via adb but comes back not reading the img - also came with 2.3.4 update S-off is ther a way I can flash a rom thats rooted to get Su permission ??
I am on H-boot .89
Any help would be great.
Thx
Stickies and INDEX are a great help.
Some basic reading is expected.
Thank Jack_R1 used to say the same myself I think re downgrade and start from scratch ... eeek and this one has a bad chipset -
No need to re-downgrade. If you got S-OFF - you're good.
Now flash engineering bootloader (0.85) by PD15IMG.ZIP way (search the guides for it) and use fastboot for flashing recovery.
This should guide you enough.
Thanks mate appreciate the help
Edit: have done your suggested but i am getting a Cid error ??
Means you probably don't have MT4G, but HTC Panache.
Look up a thread named "Videotron/Mobilicity Panache thread". There are instructions for making goldcard.
Actually, what it could also mean is that your phone was S-OFF-ed by XTC Clip and not by gfree, which means you're still not SuperCID. You might want to downgrade to Froyo and run gfree for SuperCID only.