Database Users

New SPL via OTA?

Hi guys,
Not sure if anyone's brought this up but search didn't turn up anything. Anyways, I had flashed my T-Mobile MyTouch with Cyanogen's ROM a few weeks ago. At the time, I had 1.33.2005 for SPL (which is what came with the phone) and after T-Mobile performed their Donut upgrade.. now my SPL is 1.33.006. I would have never noticed this if I wasn't tempted to try out other ROMs. Now, I can't get into Recovery Mode but Fastboot still works. Nor am I able to use flashrec to dump the recovery image back. I didn't do anything to this phone since loading Cyanogen's ROM and at the time, I still had .2005 after I had it on.
Has anyone else noticed this?

WOW that sucks! the spl they gave you is a perfect spl.
My question is did they close the one click root access with the ota doughnut?

integrated said:
Hi guys,
Not sure if anyone's brought this up but search didn't turn up anything. Anyways, I had flashed my T-Mobile MyTouch with Cyanogen's ROM a few weeks ago. At the time, I had 1.33.2005 for SPL (which is what came with the phone) and after T-Mobile performed their Donut upgrade.. now my SPL is 1.33.006. I would have never noticed this if I wasn't tempted to try out other ROMs. Now, I can't get into Recovery Mode but Fastboot still works. Nor am I able to use flashrec to dump the recovery image back. I didn't do anything to this phone since loading Cyanogen's ROM and at the time, I still had .2005 after I had it on.
Has anyone else noticed this?
Click to expand...
Click to collapse
I had that HBOOT 1.33.0006 too, but I never took a look @ what I had before so I don't know if it has been changed. However, if memory serves me right, I thought we lost the ability to OTA upgrade when we root and flash custom roms? anyone can confirm on this?
Also I can still access recovery mode and fastboot, so it seems like nothing has been changed on my phone even though I have the same SPL as yours

Android0014 said:
I had that HBOOT 1.33.0006 too, but I never took a look @ what I had before so I don't know if it has been changed. However, if memory serves me right, I thought we lost the ability to OTA upgrade when we root and flash custom roms? anyone can confirm on this?
Also I can still access recovery mode and fastboot, so it seems like nothing has been changed on my phone even though I have the same SPL as yours
Click to expand...
Click to collapse
That's what I thought too but this sudden change is worrisome. I'm also not sure if this SPL is even rootable with the current methods. By the sounds of it, I don't think so but correct me if I'm wrong.
This sucks!

I bought my MT3G last week and it came with that SPL. It's rootable, as long as you're on 1.5 firmware. Use the recovery flasher to flash Anom_RA's recovery, boot into recovery, flash a rooted ROM and the engineering SPL. Check my sig for the correct SPL.
If you're on 1.6, you're not out of luck. Pick up the SAPPIMG.nbh file, rename it to sappimg.nbh, place it in the root of your sdcard, boot up into hboot (volume down + power) and flash that. It will put you back into 1.5 firmware and from there you can repeat the steps above.

DOHCtor said:
I bought my MT3G last week and it came with that SPL. It's rootable, as long as you're on 1.5 firmware. Use the recovery flasher to flash Anom_RA's recovery, boot into recovery, flash a rooted ROM and the engineering SPL. Check my sig for the correct SPL.
If you're on 1.6, you're not out of luck. Pick up the SAPPIMG.nbh file, rename it to sappimg.nbh, place it in the root of your sdcard, boot up into hboot (volume down + power) and flash that. It will put you back into 1.5 firmware and from there you can repeat the steps above.
Click to expand...
Click to collapse
This worked great. Thank you sir!

I was holding off until I could get a definite answer on this question, but I accidentally clicked the Install button today... When it came back up, I still had the same SPL/Radio/etc that I started with: (this is with a MT3G on T-Mobile USA)
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
Just my experience, HTH

Radio update problem...

Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?

I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.

speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition

That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.

AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer

You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.

yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..

bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!

Turn your phone off, hold the camera button down, and power on your phone.
What do you see?

each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.

speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer

speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer

[Q] Unroot for Warranty Repair

I need to send my Mytouch 4g in for repair due to an issue with "limited service" problems. Both T-Mobile and HTC said it is a rare problem and it needs to come in for repair.
My problem is that my phone is/has been rooted. I need to COMPLETELY UNROOT it before sending it in, or they will not repair/replace.
What can I do to completely unroot so they will not know that it was ever rooted?
I have run the unlockr method with the PD15IMG but Im not sure that is it. What else can do to see that it was rooted? Is there anything other than info in the bootloader? I turned the S-On again.
PS - the issue with my phone is when i put in my SIM card (under any rom, including stock) it comes back with a message saying "limited service" and i cannot do anything to fix it. If you have an answer for this too, that would be helpful.
Either way I dont want to lost this phone due to root/warranty problems.
Thanks ahead of time....

How did you root it? Did you use gfree and simunlock? Did you flash engineering hboot? Did you S-OFF? Did you flash custom images?
There are a lot of questions to answer in what to undo.
If you SIM/Super CID unlocked and radio S-OFF with gfree then you need to follow the instructions in the gfree thread on how to restore your part7 backup.
If you flashed the engineering hboot, again, follow info in the gfree thread on how to flash it back to stock.
Once you are back to normal hboot and S-ON, just loading the PD15IMG for the complete OTA (find the thread in the dev section) will factory wipe and clear the rest for you.

Thanks for the quick reply. I followed the unlockr method completely to gain root.
theunlockr.com/2010/12/10/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-mytouch-4g-htc-glacier/
Then I installed Iced Glacier.
I also did their unroot method which includes flashing the PD15IMG and turning the S-On. Normally, should I receive an OTA after flashing this? Or is this THE updated image?
If is should expect an OTA, I will not get it. The reason i need to send the phone in is because i do not get service with the SIM card in. It reads "Limited service" "Emergency Calls Only". In this case, i would not recieve an OTA. Is there anything else I can do?
Thanks again.

http://forum.xda-developers.com/showthread.php?t=858996
Scroll down to "follow these steps to restore stock hboot (0.86.0000) and flash that back on if you have not already.
If you flashed the PD15IMG from this thread then it already has the OTA updated applied and you should be g2g.

Thank you very much. That is a huge help.
After updating the HBoot and flashing the PD15IMG we should be back to stock.
Is there any way after that HTC will see it as previously rooted?
I thought to myself that the hackers were smarter than the developers.... Im glad I was right.
Thanks again.
Sent from my HTC Glacier using XDA App

pnut22r said:
Is there any way after that HTC will see it as previously rooted?
Click to expand...
Click to collapse
With S-ON, a stock hboot, and a fresh flash of the OTA image -- no, not to my knowledge.

Ok so I am expecting to receive a replacement for the BAD SCREEN (inferior) issue. So preparing to get my phone to STOCK condition.
--------PRESENT STATE----------
Rooted - using http://forum.xda-developers.com/showthread.php?t=858021
S=OFF
Radio - 26.09.04.26
ROM - Nexus AOSP 1.2.7
Recovery - 3.0.2.4
----------STOCK STATE------------
Unroot - http://forum.xda-developers.com/showthread.php?t=924923
S=ON
Radio - 26.03.02.26 http://forum.xda-developers.com/showthread.php?t=1059347
Recovery - ????
Now I kind of know where I need to be at but I am not sure of the sequence of the steps. Also, how do I get back to stock recovery from Clockwork?
Is there a good check list of things to make sure before sending back the old phone?
thanks a lot.

for unroot
download stock rom from here http://forum.xda-developers.com/showthread.php?t=901477
rename it PD15IMG.zip and put it in the root of your sdcard not in a folder
go into hboot by powering off then hold VOL DOWN+POWER
then it will automatically check to find PD15IMG.zip when it ask for update click yes
wait for it to install done stock unroot

Thanks for your reponse. I was aware of that method and was planning on using it. Does that also take care of clockwork recovery and updated radio?

New Mytouch fender user, semi-bricked. Looking for help

Hey guys, I am a decently experienced android user (D1, D2, Eris, SGS, etc). But I seem to have run into a problem. I had rooted a friend of mines MyTouch Fender months ago, using some root app, I forget which, z4root or one of those.
Anyways, he came to me the other day because he got a new phone, and the MyTouch Fender is semi-bricked, im not sure what he did, he said he was playing with it and screwed it up. Anyways, the phone just stays at the Fender loading screen. I can access hboot, recovery etc. The phone is completely stock, 32A, S-ON Google, etc. So what would be the easiest way for me to get this phone going again? He's given the phone to me for free, and I would like to get it working to give to my gf to replace her crackberry curve.
If someone could point in the right direction that would be great. Unfortunately I have no idea what he did to break it in the first place. I've tried wiping data and cache via stock recovery to no avail. Is there maybe a stock oem update.zip that could be flashed via recovery that would flash it back to stock?
I do eventually want to mod the phone and probably throw CM6 on it, but for now I'd rather just bring it back to working stock. Unless rooting it and custom recoveries would be faster.
Thanks in advance.

It's certainly fixable, but I don't know about getting back to stock. The issue is that no one has an actual stock Fender sappimg (sappimg being a file you flash from fastboot to get completely back to stock). The things you will lose by rooting will be the extra Fender apps and the Fender splash image (the first image you see when booting the phone). That's pretty much all that's missing, but there's a group of guys working on getting it back in order. So it all really depends on what you want to do right now. Do you want to root and install a custom recovery/ROM (which will be the quickest fix right now) or would you rather wait until someone can get a similar stock image put back together?
Since you can't get into the ROM, you'll have to root using the goldcard method. Luckily for you it seems you have an extra Android powered phone around to be able to make the goldcard (you need to be able to boot the phone to complete this process).
At either rate, the best way to go about getting you straightened out would be for you to post the phone's current fastboot information. To do this, turn the phone off, then turn it back on holding the back button+power. Post everything from there.

Thanks man. Here's the info from HBOOT:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CLPD-13
RADIO-2.22.28.25
For the moment I would like whatever is the easiest way to get it close to stock. My problem is I don't always readily have access to a computer, but I have lots of android phones, lol. I'd like if I could just make a goldcard on another phone if possible, and flash a normal stock image from another dream/sapphire that is compatible. Is this possible?
Sent from my SCH-I500

hello first post

You could flash the stock sappimg for the myTouch 1.2. The myTouch 1.2 is the one that came out after the Fender. Same everything minus the Fender splash screen and apps. It also isn't capable of getting the 2.2.1 OTA update that came out last month. It's also stock 1.6, but it is very stable and pretty fast considering the phone's hardware.
I can tell that you that your friend's phone got hosed doing the OTA update and he could've gotten a Samsung Vibrant as a trade-out if he would've called T-Mobile about the issue, but we won't tell him that.
Rooting would require computer access. Actually, you'll need a computer period. Either rate. Before we do anything, try booting into recovery (hold home+power) and doing a "wipe data/factory reset" and then reboot. We could also try just reapplying the update.
You can hit me up on Google Talk at [email protected] if you want to get this sorted out tonight instead of having to go back and forth.

Do you have custom recovery or stock recovery...
If it is custom recovery, then fixing your problem(s) is pretty straight forward...

mumilover said:
Do you have custom recovery or stock recovery...
If it is custom recovery, then fixing your problem(s) is pretty straight forward...
Click to expand...
Click to collapse
Got him on Google Talk. Apparently his friend or the former owner hosed the phone doing the OTA since he's got the new radio and the SPL is untouched. We're going to try re-flashing the OTA update and maybe root later on. He's just trying to get it back working.

Yup. Stock recovery. From what I just got from the guy I got it from, it died after/while doing the ota update. It stuck on the splash when it went to reboot.
My guess its due to the fact I rooted the phone like 8 months ago, and removed a bunch of stuff via adb. Including probably what it considers some critical system stuff.
Sent from my SCH-I500

have a mytouch 3g 1.2 with the old radio and SPL, i acidently bricked it trying to flash the new radio and SPL and now i cant get into recovery or fastboot and the flash screen is frozen, pleassssssee help me get this fixed it has been completel useless for the last week or so

[Q] PLEASE HELP - Weird Situation with Returning to Stock

I'm running Virtuous 1.1.8 ROM with latest radio (stickied-thread that shows May 11th date).
The first I did (accidentily) was make S=on. Now, whenever I try to go to bootloader to load PD15IMG.zip, it says "Main version is older. Update fail".
I believe I need to get back to S=off and first put stock recovery on before doing the pd15img.zip... Is that right? I have tried to get back to s=off without any luck.
I would appreciate ANY help. Thank you.

Legaleye3000 said:
I'm running Virtuous 1.1.8 ROM with latest radio (stickied-thread that shows May 11th date).
The first I did (accidentily) was make S=on. Now, whenever I try to go to bootloader to load PD15IMG.zip, it says "Main version is older. Update fail".
I believe I need to get back to S=off and first put stock recovery on before doing the pd15img.zip... Is that right? I have tried to get back to s=off without any luck.
I would appreciate ANY help. Thank you.
Click to expand...
Click to collapse
The file you are trying to load is a radio file. You cant flash a new radio unless you have S=off. Second, how and why are you trying to flash a new radio?

I don't know. I've read a bunch of guides and I think I'm totally confused now.
What do I need to do as step 1 in this situation? If its to get my device back to s=off, I can't figure it out. It was s=off, then I accidentily made it s=on.
I would appreciate any help. Thank you.

I remember someone else doing something similar in this thread. The thread gets a little confusing as someone else jumps in with a problem and you have 4 people talking back and forth. Read the whole thing to make sure it's identical to your problem. Something on page 4 fixed resolved one of their issues.
http://forum.xda-developers.com/showthread.php?t=1092170

Legaleye3000 said:
I'm running Virtuous 1.1.8 ROM with latest radio (stickied-thread that shows May 11th date).
The first I did (accidentily) was make S=on. Now, whenever I try to go to bootloader to load PD15IMG.zip, it says "Main version is older. Update fail".
I believe I need to get back to S=off and first put stock recovery on before doing the pd15img.zip... Is that right? I have tried to get back to s=off without any luck.
I would appreciate ANY help. Thank you.
Click to expand...
Click to collapse
what you should have done was revert back to the stock radio before flashing the stock PD15IMG. since you have the updated radio, when you flashed the PD15IMG it turned your security on and flashed the stock hboot, but since youre on the updated radio you now have a radio lockout. this happened to me and I never got mine fixed, tried every method possible, so I just bricked it. KOLOHE got his fixed, try the methods he did since youre pretty much in the same boat. post back with your results...
ps- there should be a sticky made or something of the sort stating that you should be on the stock radio before trying to flash the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M

I just read your thread... I have tried everything... no luck... I now have no access to the phone except bootloader/recovery, meaning the only way to get my phone working again is through the .zip in the bootloader. I think I'm bricked

Legaleye3000 said:
I just read your thread... I have tried everything... no luck... I now have no access to the phone except bootloader/recovery, meaning the only way to get my phone working again is through the .zip in the bootloader. I think I'm bricked
Click to expand...
Click to collapse
you cant even get into recovery? are you sure? thats weird....I was still able to get into recovery and flash roms and everything, but couldnt flash in hboot

If I just turn on my phone like normal now, it gets stuck at the very first screen (white "MyTouch 4G"). I can still access recovery, but that's it. I tried flashing CM7 7.0.3 and when I reboot, still white "MyTouch 4G" screen...

Legaleye3000 said:
If I just turn on my phone like normal now, it gets stuck at the very first screen (white "MyTouch 4G"). I can still access recovery, but that's it. I tried flashing CM7 7.0.3 and when I reboot, still white "MyTouch 4G" screen...
Click to expand...
Click to collapse
the thing is, since you were on virtuous fusion the kernel from that rom will stick to every other rom (dont ask, I have no idea why lol). try flashing virtuous in recovery, that should work. since the kernel from the rom is sticking, you can only flash roms that are compatible with the kernel. you should still have total root access, but your r/w should be disabled because of the radio issue. only downsides to the problem...

Ok- so once I flash virtuous back... I'm still unable to ultimately get back to flash... correct? Thanks.

If I'm sending this phone in to T-Mobile for warranty exchange, I wonder if it will be better to put on virtuous (obviously non-stock rom), or leave it in a seemingly bricked state that only shows the "white MyTouch 4G" screen... What do you think? Thanks.

Legaleye3000 said:
Ok- so once I flash virtuous back... I'm still unable to ultimately get back to flash... correct? Thanks.
Click to expand...
Click to collapse
it will still say s=on and stock hboot, but you should still have root access when you flash virtuous. if you have tried all the methods in the other thread, then you are unfortunately out of luck...

Legaleye3000 said:
If I'm sending this phone in to T-Mobile for warranty exchange, I wonder if it will be better to put on virtuous (obviously non-stock rom), or leave it in a seemingly bricked state that only shows the "white MyTouch 4G" screen... What do you think? Thanks.
Click to expand...
Click to collapse
they can still get into hboot and recovery to see that youre using clockwork

clarknick27 said:
they can still get into hboot and recovery to see that youre using clockwork
Click to expand...
Click to collapse
Maybe he will get lucky like others who have returned rooted devices, he might give it to a not so smart person . There's always the shock treatment too if you cant flash the phone back to stock, only if OP has something to send high volts to phone.

Ace42 said:
Maybe he will get lucky like others who have returned rooted devices, he might give it to a not so smart person . There's always the shock treatment too if you cant flash the phone back to stock, only if OP has something to send high volts to phone.
Click to expand...
Click to collapse
thats how I got my replacement

Ace42 said:
Maybe he will get lucky like others who have returned rooted devices, he might give it to a not so smart person . There's always the shock treatment too if you cant flash the phone back to stock, only if OP has something to send high volts to phone.
Click to expand...
Click to collapse
And people wonder why T-mobile is charging a processing fee now for doing warranty exchanges.

You think I should be able to put stock recovery back on in my situation?
Also, where can I find that panache leaked rom? I don't understand how that's supposed to fix my problem...?

I think I got it to work! I used the hex editing method and flashed the .zip file in bootloader at the end of completing the guide (.zip that was included in that thread) and everything seems to be working like stock!
When I try to go to recovery, I get that icon with a red exclamation mark (which I think is normal for completely stock phones..??).
The only thing I'm not 100% sure about is in bootloader, it says hboot version ..86 Besides that, everything seems 100% stock. Will that .86 be an issue? Thanks.

Legaleye3000 said:
I think I got it to work! I used the hex editing method and flashed the .zip file in bootloader at the end of completing the guide (.zip that was included in that thread) and everything seems to be working like stock!
When I try to go to recovery, I get that icon with a red exclamation mark (which I think is normal for completely stock phones..??).
The only thing I'm not 100% sure about is in bootloader, it says hboot version ..86 Besides that, everything seems 100% stock. Will that .86 be an issue? Thanks.
Click to expand...
Click to collapse
.86 is the stock bootloader. I'm glad you were able to fix it. I'm not sire about the red ! maybe someone else can answer it. So are you going to keep it and start all over again?

I think the red exclamation mark is normal. If memory serves me right, the recovery was not accessible on complete stock and if you try to go to it you get this red exclamation point (someone correct me if I'm wrong).
I need to send this phone in as a warranty replacement. So it seems MISSION ACCOMPLISHED.
Thanks for your help along the way!