Related
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
good news and bad news.
good news, im pretty damn sure thats not a brick as you can still get into fastboot (the vol down + power)((atleast thats what i think fastboot is))
bad news, i dunno how to fix it.
i know theres a way to revert to original stock ROM via fastboot, so im sure it is fixable. don't know about custom ROMs via fastboot.
bed time, though. good luck, man, and dont get bummed cause im 99% sure you aren't just plain ****ed.
edit: just noticed screenie, but can't see it because my girlfriends retarded wanna-be stepdad decides to look at pr0n all night and continues to install "mywebsearch" **** and i can't get to it. :/
Hopped on my mytouch, still think your good but let someone else who knows more vertify that.
another option
one other thing you can do,
go to a rogers store, and tell them you tried applying the so called essential upgrade 'b/c you care about your safety' and the '911 issue is a important fix'. tell them you recieved instructions to do w/e it is using the SD card method.
basically, you tried the update ---> phone got messed up.
i know someone else did it and it was grounds for them just giving you a new phone.
not saying 100% it'll work, but its worth it b/c you get a new device with the new ROM on it if it does.
goodluck.
cdstewart said:
I attempted the update via SD card method
Click to expand...
Click to collapse
Can you clarify which SD card method? Was it using the official DREAIMG.nbh from Rogers?
I thought that I had bricked my phone because I went for a hail mary attempt to root my phone. But unfortunately it wouldn't get past the Rogers screen.
However, after talking to a CSR, they sent me a link to the Windows 7 file and it rewrote everything back onto my phone and I was able to boot it normally again.
@r3s-rt
Ya, thanks. I figured I wasn't completely boned.
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
@dotster
This is the method,
Upgrade Instructions for Rogers HTC Magic
Requirements:
Rogers Magic
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
Part1
The first part will prepare the device for the actual update but will not upgrade the Operating System, the upgrade itself will be performed in Part2.
1) Download the HTC_Magic_Update_File1.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents and please do not change the file name.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are also 3rd party applications on Android Market place to back up your applications and personal data.
3) Power off the device.
4) Remove the existing microSD card from your device (if there is one already installed), press in on the microSD Card to eject it and then remove it from the slot.
Insert the microSD card with the SAPPIMG.zip on it in the microSD slot, slide it into the slot until you feel a “clickâ€.
5) Press and hold the Volume Down Button and the Power buttons until the display turns white.
6) The update will begin installing, please follow any onscreen instructions, press the trackball when prompted to press “Actionâ€
7. Once the update is complete, “Press Action to Complete†will be displayed on the screen, press the TrackBall for the device to reboot and complete the first part of the upgrade process.
8. Power off the device to prepare for the step 2 below.
Part 2
Upgrading the device.
1) Delete the SAPPIMG.zip from the microSD card
2) Download the HTC_Magic_Update_File2.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents. Please do not change the file name.
3) Follow the same instructions as in Part 1 - step 3 TO 8.
4) Delete the SAPPIMG.zip file from the card.
Click to expand...
Click to collapse
Keep in mind this is magic and not dream
Thanks for the help guys.
cdstewart said:
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
Click to expand...
Click to collapse
I had the same problem while installing the new update yesterday. I had to call Rogers to guide me through it and even he couldn't figure it out. My phone just kept rebooting over and over after installing the first update. Even in recovery mode it didn't give me a chance to wipe, flash or restore anything because it would reboot in a matter of 2 seconds. The tech support guy on the phone had no idea what to do. I finally realised that I had a seperate Mini SDcard USB adapter that I could put my SDcard in and then plug into the USB. That allowed me to access my SDcard so I was able to delete the first SAPPIMG and then put the new SAPPIMG from the second update onto the SDcard. I repeated the same process from the first update (I was able to access fastboot without it rebooting), everything installed perfectly and now the phone is up and running great. If you don't have a Mini SDcard to USB adapter I'd suggest picking one up at your nearest Electronics store. I believe I picked mine up at BestBuy for $35 which came with a 4gb class 4 SDcard. The adapter is so small that it actually sits on my key-chain. Hope this helps.
Rogers Magic
Radio: 6.35.10.18
SPL: 1.76.0010
(unrooted)
cdstewart said:
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
Click to expand...
Click to collapse
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
cdstewart said:
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
Click to expand...
Click to collapse
I was rooted before, this is why I'm sure I've had the same problem as many of you. It seems though that this issue doesn't just stop at us... This issue has been happening with many other carriers and I'm not sure why (as of yet). I've flashed dozens of other Sense ROM's and even ROM's without Sense for ei. Espresso and Eclair and they all worked fine before. This new Sense ROM from Rogers is fantastic. So try what I did and you should be on your way with no issues.
Now if only we can root this damn phone.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18
Chynkinese said:
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
Click to expand...
Click to collapse
After the update your phone won't be rooted anymore, therefor your warranty will still be in effect. After flashing the first update it already changes your SPL and Radio therefor Rogers wouldn`t know if you were rooted prior to the update. If you stuck in the boot loop just follow my instructions and you will be home free.
Now if only we can root this damn phone.
Rogers HTC Magic (32a)
HBoot - 1.76.0010
Radio - 6.35.10.18
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
cdstewart said:
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
Click to expand...
Click to collapse
Happy to hear that I could help. They did misname the files but how could you blame someone who goes by the name of Rogers. I have several services with them and it's nothing but headaches with them.
I'm sure it was a rushed update as well. The devs at HTC were probably pressed for time to get this update up and out the door within a couple of days. Rogers will possibly be a major distributor for them in the next upcoming years.
Thanks a lot!
That solved it.
Anyone been able to root this ROM yet..?? I have tryed everything and I just keep semi bricking my phone.. but I can always recover it.
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
Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash
ok. here goes.
On rebooting my phone last night it doesnt come back on. It vibrates 3 times and the LED flashes orange.
The only way it comes back on is if i take out the battery for a while and then power it on again.
here is a chronology of what happens.
reboot or power down
devices powers off but doesnt restart. vibrates 3 times and the LED flashes orange.
pull out the battery and SDCARD and wait a minute.
After this I can now boot into CM7
Reboot or power off to restart. same thing happens again
this happens everytime i power down the device
things i have noticed
on plugging it into my PC it recognises my device as a qualcomm_cdma_technologies msm desire and tries to install drivers for it.
this is the first time i have seen this. My device is GSM based and i am on tmobile UK.
Device can never power back on immediately from power off. just vibrates 3 times, LED flashes. Only comes back when i pull battery and SD and wait a few seconds before powering it back on
What i have tried but they all dont solve it
flashing a new cwm recovery. i am able to flash a new one from rom manager but doesnt solve the problem. currently on Rom manager 4.2.0.2 and CWM 3.0.2.6
formatting my SDCARD through ROM Manager.
doing a full wipe and reflashing stable CM7.
all of these completed successfully with no errors
What i can do successfully
i can boot into bootloader and recovery from commandprompt or using the power+volume down combination. doesnt always power on because of the no boot (start) problem .
i can do "adb devices" and successfully see my device as HT0****** in the list of devices
On the terminal app, on typing "su" it gains root permission successfully.
i can succesfully access my SDCARD using astro and also using mount usb storage in recovery.
device information
HTC DEsire hd.
CM7.0.3 stable, previously on nightly CM_ace_full 83
ROM manager version 4.2.0.2
CWM 3.0.2.6
Radio 26.09.04.11_M2
hdboot-0.85.2007 (PD9810000)
ACE PVT ENG S-OFF
USBdebugging always on
please let me know if any further information is needed and how to get it.
I really need some help. I have trawled the forums and i am starting to believe that i have a partially bricked device or a usb brick. I havent seen any real solutions or any post with a problem like mine so i want to be sure that that is the issue before trying the fixes there. Is there any thread for fixing a Desire HD USB brick, because all the ones i have seen do not have a definite fix.
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
andyharney said:
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
Click to expand...
Click to collapse
Thanks andy.
In flashing the HTC RUU. is that the process of removing root?. because i was thinking of removing root and then sending it back. but thought there might be a software fix for it i could try first.
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
andyharney said:
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
Click to expand...
Click to collapse
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
santet said:
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
Click to expand...
Click to collapse
I recently had to send mt phone back to HTC. What I did was flash the RUU, temproot and revert to stock CID (don't know why I didn't do this first) then flash the RUU again just to make absolutely sure that all was well.
Yeah I would use the tool to change Radio S-OFF to ON and restore the CID before you run the RUU. You will save yourself a lot of time and effort.
ok. on first try i already have a problem. i downloaded the easy radio tool.
connected my device with usb debugging on. run the application as administrator. clicked on Stock CID (my device is unbranded desire hd) started up, notified as pushing file to sd. reurned with unknown error, probably connection.
i tried the same with Radio S-On. same response.
i am doing this before flashing the new RUU i downloaded which is version RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed.zip.
what have i done wrong?
Don't panic your ok,
It just means you will have to run the RUU first then run Visionary+(r14) to get temp root then run the Radio S-OFF tool.
I have gone through all the steps with no glitches. How do i verify that my device no more has radio S-On and is fully returned to stock enough so as not to voide warranty. I have the stock ROM installed.
I also want to try updating using the recent OTA update and use the device a while to see if the problem returns before returning it to HTC.
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
andyharney said:
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
Click to expand...
Click to collapse
Funny enough no more problem of being unable to reboot.
I have installed titanium.
i want to update to the latest OTA 2.3 update for the desirehd. do you know if the visioinary root and the the easy radio tool for s-off work after that update which i believe is the latest one.
I will use the device in its stock condition for two mpore days and if i do not have any more issues then im going to install a custon rom once again.
Thanks loads for all the help.
If you upgrade to 2.3 (2.36.405.x) then Visionary+ no longer works, you have to use GingerBreak instead. You can still downgrade to an earlier firmware.
I tried rooting again using visionary. got the same problem after applying permroot and then using the easy radio tool for S-OFF. After applying permroot it booted fine. But after applying S-OFF and SUperCID it goes back to same error and doesnt boot again. It seems then that it has something to do with the rooting process.
I will post a new thread asking if anyone has been unable to complete the S-OFF and SUPERCID process .
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
andyharney said:
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
Click to expand...
Click to collapse
I did exactly as you said using temproot so as to be able to turn apply S-OFF and the stock CID.
but after i did that and it worked i just tried rooting once again permanently and had the same issue. I have updated to the OTA update and i will use that for a while as when reading the gingerbreak threads people do not seem to trust that it works fine.
I just re-read my last post, sorry if I came across as a d*ck, that was not the intent.
I would remain stock for a few days to see if that has an affect. If rooting is the cause of your issue, I doubt HTC will repair it because it has booting problems once rooted.
I once had my Evo rooted when it first came out, ran a rooted update and then did a full RUU (on the XDAwiki page) to unroot sometime around January of 2011. Since then I have ran a stock Evo, I have received and installed all OTA's from Sprint since and from what I can tell my phone is stock.
Over the last month I have been chasing down a new reception issue with my Evo. After two previous visits to two different Sprint repair facilities where I was told they performed a hard reset (pulled the battery) and updated profiles. Sprint phone service checked my local tower and "reset" it. On Tuesday I was told by phone based Sprint to take my phone in and start the insurance replacement process.
Yesterday I took my phone back into the same Sprint center that said they reset and updated my phone and was informed that I still had Superuser capabilities and my phone is rooted (which from what I can tell cannot still be the case)and therefore even though they previously claimed to have updated and worked on my phone now say they can't touch it. Sprint will send me a new phone with the caveat that I will be charged an indisputable 500 charge if my poorly functioning phone is determined to be rooted.
I have already run the RUU (in January) in the XDA Wiki to get it stock, what are my other options?
Will running it again change anything? Is there anything beyond running the RUU I need to focus on?
Thanks for any help provided.
Boot into bootloader (Volume Down + Power key from OFF) and see if it says S-OFF at the top. That might be what they are looking at. However, that isn't Superuser (su) privileges like they are saying. Sounds fishy.
Easiest thing might be to try a different Sprint location if possible.
it does say S-OFF at the top.
How do I remove that?
redo the RUU?
I am going to give this a shot
http://forum.xda-developers.com/showthread.php?t=780141
will update.
insert cust. service joke said:
I am going to give this a shot
http://forum.xda-developers.com/showthread.php?t=780141
will update.
Click to expand...
Click to collapse
From the point you're at now, there is only one way to get it to S-on. You need to install a custom recovery image, then use that recovery to flash the unrevoked S-on tool, and then after that you need to run the RUU again. You'll then be fully stock.
So, download the PC36IMG.zip I attatch. It is Amon Ra V2.3 recovery. Put the file on your sd card, not in any folders. Just on the main directory. Also place the unrevoked forever S-on tool on your sd card at this time. Boot to the bootloader, by holding power and volume down when your phone is turned off. It will scan and find the file and ask you to update. Press volume up to say yes. That will flash the recovery for you. When that is finished up, don't choose to reboot. Then from your bootloader's menu, choose 'recovery.' That will then boot you to recovery. Then in recovery, choose install zip from sd card, and find the unrevoked forever s-on tool that you put on the card. Then select to flash it. That should set your bootloader back to S-on. Once that's done, turn your phone off and boot back to the bootloader. Confirm that it now says S-on. If so, then all you need to do is run the RUU or a PC36IMG.zip of the RUU. You'll be good to go after that. Good luck.
insert cust. service joke said:
I am going to give this a shot
http://forum.xda-developers.com/showthread.php?t=780141
will update.
Click to expand...
Click to collapse
Is your phone currently on software number 4.24?
k2buckley said:
From the point you're at now, there is only one way to get it to S-on. You need to install a custom recovery image, then use that recovery to flash the unrevoked S-on tool, and then after that you need to run the RUU again. You'll then be fully stock.
So, download the PC36IMG.zip I attatch. It is Amon Ra V2.3 recovery. Put the file on your sd card, not in any folders. Just on the main directory. Also place the unrevoked forever S-on tool on your sd card at this time. Boot to the bootloader, by holding power and volume down when your phone is turned off. It will scan and find the file and ask you to update. Press volume up to say yes. That will flash the recovery for you. When that is finished up, don't choose to reboot. Then from your bootloader's menu, choose 'recovery.' That will then boot you to recovery. Then in recovery, choose install zip from sd card, and find the unrevoked forever s-on tool that you put on the card. Then select to flash it. That should set your bootloader back to S-on. Once that's done, turn your phone off and boot back to the bootloader. Confirm that it now says S-on. If so, then all you need to do is run the RUU or a PC36IMG.zip of the RUU. You'll be good to go after that. Good luck.
Click to expand...
Click to collapse
This will get your phone fixed.
Sent from my PC36100 using XDA Premium App
k2buckley said:
From the point you're at now, there is only one way to get it to S-on. You need to install a custom recovery image, then use that recovery to flash the unrevoked S-on tool, and then after that you need to run the RUU again. You'll then be fully stock.
So, download the PC36IMG.zip I attatch. It is Amon Ra V2.3 recovery. Put the file on your sd card, not in any folders. Just on the main directory. Also place the unrevoked forever S-on tool on your sd card at this time. Boot to the bootloader, by holding power and volume down when your phone is turned off. It will scan and find the file and ask you to update. Press volume up to say yes. That will flash the recovery for you. When that is finished up, don't choose to reboot. Then from your bootloader's menu, choose 'recovery.' That will then boot you to recovery. Then in recovery, choose install zip from sd card, and find the unrevoked forever s-on tool that you put on the card. Then select to flash it. That should set your bootloader back to S-on. Once that's done, turn your phone off and boot back to the bootloader. Confirm that it now says S-on. If so, then all you need to do is run the RUU or a PC36IMG.zip of the RUU. You'll be good to go after that. Good luck.
Click to expand...
Click to collapse
K2Buckley, thanks for the help. The phone automatically ran the update, but when I go into recovery and try to flash the unrevoked-son.zip I keep getting Installation aborted. When I boot back to bootloader it still says s off.
Specifically:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted.
insert cust. service joke said:
K2Buckley, thanks for the help. The phone automatically ran the update, but when I go into recovery and try to flash the unrevoked-son.zip I keep getting Installation aborted. When I boot back to bootloader it still says s off.
Specifically:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted.
Click to expand...
Click to collapse
What software number does your phone have? Is it the 4.24 GB?
software number: 4.24.651.1
build number: 4.24.651.1 CL61076 release-keys
Kernel version: [email protected] #1
Tue Jun 14 23:58:32 CST 2011
Thanks,
S
Looks like your stuck cuz of the last update like the rest of us with new evos that have the latest build 2.3.3.
insert cust. service joke said:
software number: 4.24.651.1
build number: 4.24.651.1 CL61076 release-keys
Kernel version: [email protected] #1
Tue Jun 14 23:58:32 CST 2011
Thanks,
S
Click to expand...
Click to collapse
The S-ON tool appears to be patched in the GB ROM 4.24. You likely need to
1. Downgrade back to 3.70 (use the same PC36IMG file from
http://forum.xda-developers.com/showthread.php?t=780141
It should work if your phone is truly S-OFF).
2. Remove that PC36IMG file, then copy and run the PC36IMG update for the Amon recovery that Rem3Dy gave you.
3. Remove that PC36IMG file, then flash the S-ON tool from RECOVERY, and then finally,
4. Copy to SDcard and run the PC36IMG file from step 1 again, or the RUU which you were originally using for your stock ROM. Unfortunately, the RUU for 4.24 will permanently remove the ability to reroot the phone until the devs figure it out, but if you are returning the phone, then you might not care at this point.
Hope this works for you this time.
Yeah I was gonna say the same thing. As long as you're s-off, you can downgrade back to froyo to use the s-on tool.
Sent from my PC36100 using XDA App
insert cust. service joke said:
K2Buckley, thanks for the help. The phone automatically ran the update, but when I go into recovery and try to flash the unrevoked-son.zip I keep getting Installation aborted. When I boot back to bootloader it still says s off.
Specifically:
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted.
Click to expand...
Click to collapse
Lousy. When you took the ota, it upgraded your radio. If you're s off, try downgrading your radios back to 3.70 ruu. Then reflash your recovery, and try the s on tool again. Hopefully you can downgrade your radio, because the s on tool doesn't work on your current radio version.
Sent from my PG86100 using Tapatalk
k2buckley said:
Lousy. When you took the ota, it upgraded your radio. If you're s off, try downgrading your radios back to 3.70 ruu. Then reflash your recovery, and try the s on tool again. Hopefully you can downgrade your radio, because the s on tool doesn't work on your current radio version.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Ed zachary, you need to flash an older version radio.
Sent from my PC36100 using Tapatalk
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
insert cust. service joke said:
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PC36100 using XDA Premium App
insert cust. service joke said:
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
Click to expand...
Click to collapse
Glad you got it squared away and all set. Good deal. As always, glad to help.
insert cust. service joke said:
K2Buckley, and Shorty Doggg
Thanks for all your assistance, and the idiot proof step by step instructions. I finally have S-on, and am updating to current as we speak. I am looking forward to stopping by the other Sprint repair facility tomorrow. Hopefully I can get a new phone that works again sooner than later.
s
Click to expand...
Click to collapse
Just an fyi, if sprint found your phone rooted, they may have completely blacklisted the phone, and they may not provide service on it anymore. Just giving you a heads up.
So...I thought sprint didn't care if your phone was rooted or not? From all the stories I've heard at least. This means if I try to do an insurance claim due to a cracked screen or something they won't allow it?
Okay heres a simple question about a mytouch 4g, the phone is s-on and 0.86 hboot. My question is, do i need to make a gold card to install the stock firmware on it or can i just put the stock firmware on the sdcard and install it??? I dont know what happened to the phone that it wont start up normally so any help appreciated
Easiest thing to do now is factory reset. Thats what I did with mine.
enelyam said:
Okay heres a simple question about a mytouch 4g, the phone is s-on and 0.86 hboot. My question is, do i need to make a gold card to install the stock firmware on it or can i just put the stock firmware on the sdcard and install it??? I dont know what happened to the phone that it wont start up normally so any help appreciated
Click to expand...
Click to collapse
Put the stock firmware on the sdcard and flash. You don't need a gold card to upgrade.
-Team MS
Sent from my HTC Glacier MIUI using xda premium
Well, the problem i found is that if i put the image file on an empty and formatted sd card the phone will say wrong image file. Yes, its not named PD15IMG.zip.zip or anything like that. And its the same image i have used to flash other mytouch 4g back to stock.
Also, can someone point me to the right direction to find the gingerbread update for the MT4G because the links in here are extinguished because of the megaguys been caught.... Thanks! Since the Foyo doesnt want to work maybe the Gingerbread will who knows.
The file for flashing in bootloader has to be named PD15IMG.ZIP, or it won't work. To flash anything else, you'll need recovery in place, which you don't have.
You won't be able to flash the same version of firmware as you had, only newer one.
Well, if that is the case then i need the gingerbread version for the mytouch 4g. And all the links i had were From the MEGAproblem website. I need a link to download the gingerbread version....
Okay i finally got the gingerbread version for the mytouch 4g. But the problem persist!!!!! I'ts very frustrating because im used to do this and for some reason this phone wont read the IMG file no matter what. Since i dont know how it ended up like that. The only thing i know its that it will get to the bootloader and everything works fine with that. Other than that it will not respond to any of the 2 IMG files(Froyo or ginger). I tried to rename it PD15IMG.zip. Left it as is PD15IMG which is the way im used to use it but NOTHING!!!! It's very weird to say the least....
Does it say "wrong or non-existing file"?
If yes - reformat your SD card, put the file on it and try again.
Does it say "main image is older"?
In that case, find the latest Gingerbread PD15IMG, because you don't have the latest one.
Okay, i have the 312mb PD15IMG which i think is the Froyo. And also have the 315mb Which as far as i can recall is the Gingerbread version. And yes, it says wrong image file nothing about no image file. I will double check on that then and let you guys know thanks...
where did you get the stock froyo and gingerbread IMGs?
im having the same problem (i think)
when the phone is powered on, it boots straight to the bootloader, i thought well ill just factory reset it, no dice, it just shows the three androids on the skateboards then reboots into the bootloader again, i tried to get into the recovery and it did the exact same thing. the phone is my friends and he gave it to me to fix, he says its stock so i want to just flash the updates to see if that fixes the problem
SuperSwaggtastic said:
where did you get the stock froyo and gingerbread IMGs?
im having the same problem (i think)
when the phone is powered on, it boots straight to the bootloader, i thought well ill just factory reset it, no dice, it just shows the three androids on the skateboards then reboots into the bootloader again, i tried to get into the recovery and it did the exact same thing. the phone is my friends and he gave it to me to fix, he says its stock so i want to just flash the updates to see if that fixes the problem
Click to expand...
Click to collapse
did you ever find a resolution. I'm having the same problem. Thanks