Related
Hi, I've recently bought a HTC Magic and since then I've been reading into how to root my phone. Before I start I would like to know if it's possible on my phone.
Details:
HTC Magic Vodafone Uk (32B)
Hboot: 1.33.0007
Firmware version: 1.5
Build: CRC24
I've read from a thread in another section of this forum
that it would be impossible because of 1.33.0007 being a perfect spl BUT my phone is running the firmware version 1.5, with a CRC24 build. Would this mean I will be able to root my phone or not?
Also I've been reading up on how you either have cupcake or donut. My version is 1.5 so would that mean I have cupcake?
I'm worried that I might brick my phone so would prefer to use the one click tutorial at theunlockr (would add link but I can't) which is for htc magic running on cupcake.
Would it work?
Sorry for all my questions and I probably will end up asking more
Thanks if anyone can answer these for me!
You should be able to root using the relentless rooter or by following the guide on the unlockr. You are lucky you are running cupcake and don't need to downgrade
I think you are only really at risk when you flash radio and spl. Using the unlockr's stuff shouldn't be too bad. But read eveerything a bajillion times incase
same boat
Hey bunnybag
Was in the same boat as you until yesterday.
Also had a perfect SPL (0010) on a 32A.
I was also reading up a lot wrt getting a new ROM on my phone, and was also afraid of bricking it...
The gold-card method seemed quite involved, and that QMAT application doesn't exist anymore, and the newer version of it, does not run in XP or Vista...
Yesterday, I used the one click method from theunlockr, and after a few mistakes, it worked! Now I have a shiny CyanogenMod running with a 1.6 donut
It seems with the one click method -that you do not need to change the radio or SPL (which I guess are the most dangerous flashes to attempt)
Quicky summary of what I did, and where I deviated:
1) Read the one click method from theunlocker, and some of the comments at the bottom. Also - very importantly - watch the YouTube video at the top of the one click method page a few times!!
2) Downloaded the FlashRec apk (follow link on the one click method's page)
3) Installed FlashRec (the latest version of FlashRec looks slightly different to the one in the YouTube video but functions the same)
4) Did a backup of the existing recovery image via FlashRec. After the backup, you can copy the backed up .img to your PC...
5) Copied the latest Amon RA recovery image (v1.5.2) onto the SD card. Make sure you get the right one... there is a different one for 32A/32B... [Deviation from the one click method- which uses an older version of the RA recovery image]
6) Attempted to flash the new RA recovery via FlashRec. Here is where I struck a problem - the thing just stalled - for a good 10mins - and said 'do not interrupt' :|
I hooked up the USB cable, and from the command prompt ran: adb catlog
From here, scrolling up, I could see that FlashRec gave some message of invalid recovery image... Bit of a bummer - I checked the CRCs of the recovery image after copying it to the SD, and also tripple-checked the filename I typed into FlashRec! In the one click method page, they also warn about inadvertently adding spaces to the end of the filename when you type it in. I also checked for that.
I attempted it once more as follows:
-Rebooted phone
-Deleted the RA recovery .img from the SD
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
-Flash succeeded! maybe FlashRec can't handle very long file names?
7) After the recovery was flashed, I booted into recovery mode (HOME & POWER). Seems like the Amon RA recovery image takes slightly longer to boot that the stock recovery... so - don't crap yourself if it takes a few seconds. This is also a good point to stop, and watch the second video from theunclockr on how to load a new ROM...
8) After verifying that the new recovery image was working I booted back into Android, and I copied my ROM's files onto the SD. I used the Cyanogen Mod. The Cyanogen wiki has a page on how to load it for a 32A and also 32B.
Basically, you need the latest stable cyanogen mod, an Android 1.6 "defanged" ROM (link available on the Cyanogen wiki), and a new kernel. The kernel is 32A/32B specific, so get the right one.
9) With the 3 files on the SD, I booted back into the new RA recovery I just flashed.
10) Did a Nandroid backup
11) Did a wipe/factory reset [Deviation from theunlockr method: I did not format my SD card, or partition it into Ext & Swap. I prefer not to have a Swap partition on the SD, nor do I think I'll need to swap any apps out to the SD card... I think the 32A has enough space... you can read further about it in the xda-developers wiki, under page: HTC_Sapphire_Hacking_2]
12) Still in RA recovery, I applied (in order) a) the defanged 1.6 ROM, b) the Cyanogen mod, c) the new 32A kernel
13) Flashing it takes a while - there is a progress bar...
14) Reboot after all 3 were flashed. The first reboot takes a looong time... couple of minutes... don't worry, or try to reboot again... just give it time.
15) Once inside - tested everything: GPS, Wifi, Phone, Market, G-sensor, Gtalk, Gmail.
16) It might be worth while to note that once the phone is booted, and you've entered your SIM PIN, and the Android desktop is displayed, it can still take a few seconds - 4 or 5 I guess, before you are able to interact (swipe desktop left/right). Give it time to settle down, and all is well
//TODO: still need to flash a new splash-image...
Good luck - post back here with your results!
How to root Magic (32A) with Europe ROM ROM Version:3.05.401.3 with Sense?
Have somebody any idea, how to root Magic (32A) with Europe ROM Version:3.05.401.3 with Sense? Thanks!
bogo_mips said:
Hey bunnybag
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
Good luck - post back here with your results!
Click to expand...
Click to collapse
Ah, I tried using the unlockr's method and failed at flashrec. The unlockr kept saying that the reason was because I was already on Donuts but that is not true. I ended up using the relentless rooter software (looking back, his method is basically an automation of the original method).
Maybe you should post this also in the unlockr so that people who have "backup failed" messages know what to do?
Thanks for the info. It will be very helpful for other members trying to use the unlockr method.
Thanks for the post guys.
@bogo_mips: Great advice and I'll more than likely use this along with the unlockr one click tutorial.
Oh and there's one thing I'm worried about. My phone has somehow automatically downloaded the 1.6 upgrade and it keeps asking me to install it. Anyone know of a way to delete it so that it won't upgrade?
I'm worried that it might install if I turn my phone off.
@bunnybag: that 1.6 download sounds like a problem... if it takes, you'll no longer be able to do to the one-click method...
Check around the forum for advice. I'd guess - since the download would have had to happen in user-space, that the downloaded file might be sitting on the SD card or possibly the phone's flash. Get that Linda Filemanager app from the market and poke around... I guess if you could find the file, and delete / rename it - you could avert an install?
Alternativley, I'm guessing that if you can attempt the one-click method, that you'll have a new recovery image before you power down your phone, so - I think that will keep you safe...
@visitador02: according to the FlashRec page, there are 1.5 cupcakes out there which have been patched, so - FlashRec can't work on them... maybe that is what happened to you...
Hi guys, I'm pretty new here so I hope someone can help me.
I am having serious issues trying to load ANY new ROM onto my missus HTC Vodafone Magic 32B Details -
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Since getting the phone second hand from eBay it has played up like nothing else, it now will not even boot into the OS, I’m pretty sure the guy I bought it from, who I cannot get in contact with, stuffed something up when he unlocked it for different carriers. But I'm positive it is an OS issue and not a straight hardware fault.
Anyway I have spent about a day and a half mucking about on here trying things and reading a HEAP of stuff and I just can’t seem find a definitive answer to my problem.
I have tried installing many different roms:
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.7 Swap
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap.zip
st0kes-v1.4.1
HTC_Magic_Vodafone_AU_Original_ROM
and a few others I cannot remember.
I am using Amon RA recovery ROM, I have rooted the phone based on method 2 in the magic rooting wiki (everything went smoothly), I have updated the SPL to version 2005 which are all the apparent pre requisites for performing this kind of operation.
Anyway down to the problem every time I try and apply a ROM, by renaming it to update.zip, copying it to the root of my SD card, then loading up RA recovery ROM and going to flash zip from SDcard I get the following messages:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Install from sdcard...
finding update package...
opening update package...
verifying update package...
E:corrupt file:
<various file names based on which ROM I’m trying to use, always the same one on each ROM though>
E:verification failed
Installation aborted
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is starting to drive me insane, I really need to get ANY usable ROM on there I don’t care which one, otherwise I have a AU$400 lump of useless technology.
Any help people can provide me with be unbelievably appreciated.
Thanks in advance
i cant guarantee i can help, but i will try to see if i can, or also help wit some research for ya
first, what version of amon ra are you using???
2nd, do you know if you got 1.5 or 1.6 firmware???
idk too much about firmware, all i know is my mytouch was cupcake when i got it (1.5) then updated to 1.6 ota...
also are you making sure that you wipe before you try to load the roms???
Hi mate, thanks for getting back to me so quickly
The version of amon ra i am using is recovery-RA-sapphire-v1.6.2G.img this seemed to be the right one as i have a google branded phone
I am not sure what version of firmware i have, is there an easy way to check? the only real details I have is what i get from the fastboot screen as i posted above
And yes I am definately wiping the phone before I install the roms, every single time
Thanks
well i just did a few searches and i couldn't find out how to check the firmware...
i dont want to tell you to try something and then crash your system, but...lol...
i would try to "Unroot" the device, basically placing it back to 1.5 firmware and then you can "Root" it yourself.
if you want to try this here is the link for the 1.5 software
link for tutorial:
http://theunlockr .com/2009/08/22/how-to-unroot-your-mytouch-3g/
link for file:
http://www.megaupload .com/?d=BLM4EDGE
no space in the url tho...
all you have to do is,
boot into recovery
go to wipe, and wipe the top three options
go back to the main screen and select Usb-Ms toggle
then plug your device in via usb
and drop the file to your sd card. (not in a sub folder)
then safely remove your phone from pc
then press home on your phone to disable usb
then choose power off.
now to turn it back on,
holding Volume "Down" + "Power"
DON'T PRESS ANYTHING YET
after it reads the image it should show at the bottom, Action:yes, and then click trackball,
let that run all the way thru, and make sure you have enough battery juice, for this to run all the way thru.
when it's complete it will ask if you want reboot, then click Action for yes (trackball)
i believe that should unroot your phone but PLEASE PLEASE PLEASE
do as much research as possible and also question others about this method and see if you can come to a conclusion in which you are satisfied.
as always, i am in no way responsible for the Bricking or Exploding of your device...
here is a link that has great tutorials & and also you might want to check youtube, thats where i findout how to alot of things...
Um, you already have amon ra recovery on there. I assume you've already bought it rooted?
You can only check the firmware by booting up your phone and going into settings. Since you've wiped and aren't able to install a rom, you aren't able to use the phone right now, am i correct?
sanman1185, I'm glad you try to help but you gotta get more info from him first. Cause if he's already rooted, doing what you're telling him to do won't make much progress. Edit: Ok, he's already rooted. You're just telling him to do what he's already done? And he doesn't have any firmware because his phone lacks any rom right now.
Anyways, answer some of those and don't be too worried about bricking your phone. The main reason that people brick their phones is when they touch the radio and SPL.
Edit: Ok I just read that you rooted your phone so you don't need to "unroot" and root it again.
You also put on SPL 2005 instead, so post your boot info again. I assume it's an ENG SPL too, if you haven't found a solution, send me a PM and I'll help you on google talk / MSN or something.
Ps. You don't have to rename the roms to update.zip, his new recovery allows you to flash w/e zip you want. Try another SD card as well, maybe that'll help? but if not, yeah just pm me
KAwAtA - def. understand what your sayin, only reason i was thinkin to unroot and start fresh is cuz, when i started flashin roms, i ended up being stuck on the boot screen for over 30mins. pulled the battery, then read somewhere to partition sd card, then that wiped the zip from my card, lol...so what i did instead of placing another rom on the device, is "unrooted" and started fresh from the start. my theory is if you think your "Jack'd" then start from the beginning and find your mistake.
and if he did unroot and it ran Cupcake on device, and actually loaded wouldn't that have been making progress??? since he couldnt get it to load in the first place???
like i said just a thought, theory, or 2centz (sense)...
but again, i'm glad someone actually responded with a diff method or with additional ?'s, so this way he can get answers from all angle's ya kno...
and if you guys do figure this nifty lil'thang out, could you post what you guys did on here, so myself or future ppl'z that may run into this can have it as a ref??? thnx... Pce
Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.
Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.
I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App
What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).
Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.
you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted
gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.
I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.
Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)
buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU
DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice
DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.
Hi guys,
I'd like to return my G2 to stock....completely stock and I have a few questions to make sure I'm doing this right (as I've heard that simply installing an officially signed ROM can screw things up).
Right now, I've done everything using the gfree method to get radio, s-off, and even the engineering hboot installed.
My question then becomes, should I follow the instructions as per wiki on returning to stock, or do I follow this guide?
My next question is then, is there anything specific that I should do first? Like remove hboot first, and then follow either of the above guides? And if I hve to remove hboot, how would I go about doing that (I tried searching, but I wasn't able to find anything).
If anyone could guide me on the matter, Id really appreciate it.
I'd like confirmation on the best and most up-to-date guide on this as well. Thanks
Just follow the guide that you linked to in your thread. You don't need to mess with hboot. As long as you follow the guide correctly you will overwrite the engineering hboot with the stock hboot.
Sent from my T-Mobile G2 running Cyanogenmod.
Since you used gfree, you'll need to either restore the partition 7 backup or use gfree to S-ON and set your CID back.
Then follow something like the guide you linked to in order to flash the correct PC10IMG for your phone (as stated earlier, this will also get rid of your engineering HBOOT).
If you had one of the later phones that came with the OTA preinstalled, update your phone with it after the flash is done.
Format your SD card from your settings and then enter the bootloader one more time to do a factory rest.
You should then be completely back to how the phone was when you first got it (with the exception of subsidy unlock if you didn't have the original partition 7 backup from gfree---unlocking your phone is allowed by most carriers though, so shouldn't be a problem).
Thank you for that information. In which order do I do this? Restore the partition first (how would I do this?), or do I install the stock ROM first? Or...?
As you see, I'm confused as to the order of how I would go about doing this assuming I followed the gfree method through and through
Currently, I have an original nandroid backup through clockwerk. Would I "restore" that backup first in the recovery menu, followed by restoring the original gfree backup partition?
My biggest worry currently is that I can't put any stock rom on the phone due to the engineered hboot causing a booting loop problem (something I read on a sticky or something?)? Because based on the Wiki, I need to install the stock ROM first before reinstating the backup gfree partition.
Again, thank you everyone thus far for helping me out with my questions. I do hope that you guys can still answer my remaining questions!
ianmcquinn said:
Since you used gfree, you'll need to either restore the partition 7 backup or use gfree to S-ON and set your CID back.
Then follow something like the guide you linked to in order to flash the correct PC10IMG for your phone (as stated earlier, this will also get rid of your engineering HBOOT).
If you had one of the later phones that came with the OTA preinstalled, update your phone with it after the flash is done.
Format your SD card from your settings and then enter the bootloader one more time to do a factory rest.
You should then be completely back to how the phone was when you first got it (with the exception of subsidy unlock if you didn't have the original partition 7 backup from gfree---unlocking your phone is allowed by most carriers though, so shouldn't be a problem).
Click to expand...
Click to collapse
Okay, thanks guys, I managed to return everything back to stock.
PoisonWolf said:
Thank you for that information. In which order do I do this? Restore the partition first (how would I do this?), or do I install the stock ROM first? Or...?
As you see, I'm confused as to the order of how I would go about doing this assuming I followed the gfree method through and through
Currently, I have an original nandroid backup through clockwerk. Would I "restore" that backup first in the recovery menu, followed by restoring the original gfree backup partition?
My biggest worry currently is that I can't put any stock rom on the phone due to the engineered hboot causing a booting loop problem (something I read on a sticky or something?)? Because based on the Wiki, I need to install the stock ROM first before reinstating the backup gfree partition.
Again, thank you everyone thus far for helping me out with my questions. I do hope that you guys can still answer my remaining questions!
Click to expand...
Click to collapse
Hi!
My original guide how to go back to stock can be found here: http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
It is absolutely up to date and i did this myself several times.
There is only one important prerequisite before you follow this guide: You need to be radio S-OFF before you start this.
The engineering-hboot only causes problems if you are not radio S-OFF. So if you used gfree to get radio S-OFF the eng-hboot will not be a problem.
There is no need to install the nandroid backup before you do this procedure.
have fun - Guhl
Thanks for that but I have successfully returned the phone to stock already
I just used my nandroid backup followed by manually setting the Cid back to tmob010. After that, I iinstalled the stock recovery and used the guide I linked earlier by starting at procedure 2.
In short, it was a very eclectic approach and I did what made sense to me. Lawl. It all worked out ok. Back to the good old hd2 for now
guhl99 said:
Hi!
My original guide how to go back to stock can be found here: http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
It is absolutely up to date and i did this myself several times.
There is only one important prerequisite before you follow this guide: You need to be radio S-OFF before you start this.
The engineering-hboot only causes problems if you are not radio S-OFF. So if you used gfree to get radio S-OFF the eng-hboot will not be a problem.
There is no need to install the nandroid backup before you do this procedure.
have fun - Guhl
Click to expand...
Click to collapse
Sent from my HD2
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