Related
Hi everyone,
My phone is magic (TIM).After I flashed the new radio(6.35.10.18) and SPL(1.76.2007), I don't know why my ENG S turned ON automatically, and I can't solve it (even if I reflash the SPL in recovery).
Also there is a more serious problem, After I flashed any new ROM such as SuperHero, Eclaire, Villian,Robomix v0.1 and rebooted it, it keeps frozen at the first boot screen(splash screen). At last I tried to use a CM ROM, it can be started finally!
I'm very confused, the CM ROM is Android 1.5, so does it mean that I can only use the ROM with 1.5 for now? Cannot be!^%%$#@@!%$...
You used a CM rom with a 6.35 radio and 1.76 spl? And can't use the roms that require the new radio and spl? I'm pretty sure you DIDNT FLASH the new radio and spl.
Yes, I did! I pressed BACK+POWER to boot into fastboot model, it displays 1.76 and 6.35 with ENG S-ON!
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
KAwAtA said:
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Click to expand...
Click to collapse
er...it's CursorSense32A-1.2.6.1 and recovery 1.6.2(the hero version)
Wow, you're using cursor sense? that would've been nicer to know rather than CyanogenMod
xaueious said:
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
Click to expand...
Click to collapse
I don't get it, how does that help his problem? I know he wants to change to S-OFF but the main problem is his roms don't load up. But like the other guy, I notice that they can only use CursorSense soo im not sure
Show me step by step on how you flashed the ENG 1.76.2007 SPL (although this shouldnt affect it at all)
pyee0124 said:
You should still be able to flash custom ROMS regardless of S-ON. One of the other things you should try is formatting your SD card again.. Try a full FAT32, then try partitioning afterwards. I found that I could only boot Ahmgsk with FAT32/Swap/Ext2.
Click to expand...
Click to collapse
Do you have any swap/ext partitions?
First I flashed Engineering SPL 1.33.2010 in recovery, and reboot into fastboot, I saw I'm ENG S-OFF at that moment, so I flashed new SPL and radio then. Maybe the problem comes with the old incompatible recovery, after I reboot my phone this time, it beame bootlooping(see my thread posted:http://forum.xda-developers.com/showthread.php?t=658220), I was almost thought it was bricked! But luckily the phone fixed itself(I thought), I could enter fastboot, at that time I noticed that my ENG changed S-ON.
That's my whole story, hope it can help you to help me fix the problem.
I have a ext3 partition but in order to protect my TF card I didn't partition a swap
Sorry man, hope someone else can help you. I just dont even understand how you got an S-ON SPL if you followed the thread ppl provided in the other one cause an ENG SPL was provided. Dunno how you got perfect, and I am completely not sure why you can't flash other new radio Roms. Hopefully someone else can help
It doesn't matter bro, I'll find another way to solve it, still thank you!
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
xaueious said:
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
Click to expand...
Click to collapse
Um he made an error and he said it was CursorSense, not CM.
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
xaueious said:
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
Click to expand...
Click to collapse
and after reading that thread, I read that you posted this command for sd card problems. Please point out where He is supposed to read, I'm either blind or you're wrong (Seeing as how you missed his CursorSense mistake and stating that the title of the other thread is fastboot oem enableqxdm 0, lol, I don't think I'm blind)
Sorry if I sound like a douchebag here but seriously, you although this guy posted in the wrong section *sigh*, if you wanna be a douche, at least read over his problems properly. You're not helping at all right now and again, he made a mistake about cyanogenmod which was already cleared up and you failed to read that. You should really, get your lazy ass to read this thread more clearly (LOL I don't evne know if that made sense, its 3am and since u live in toronto, oh same time there i assume!) But yeah, if you wanna be a douche, you gotta at least be right or something. But whatever, I just find it totally ridiculous how you're flaming this guy. But if I'm wrong, then go for it and flame me! I haven't seen anything helpful from you here
KAwAtA said:
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
Click to expand...
Click to collapse
I think so too, it's a forum to discuss about technic, not complain.
I have the same situation as you, the ENG SPL changed from S-OFF to S-ON.
Also, can't boot any 2.0/2.1 roms.
I did a lot of flash and try to fix the SPL to S-OFF, but no luck. Such as:
Flash ENG SPL 1.76.2007 again and again;
Flash back to 3.22 radio and 1.33 SPL, then flash the 1.33 ENG SPL;
Flash the device from 3.22 radio and 1.33 SP to 6.35 radio and 1.76 SPL;
A month after, I noticed that my phone can't turn on the Bluetooth. The Bluetooth only can be turned on while first time I boot up the phone, when you disable it and try to enable again, no go...
I send the phone back to HTC for repair, and HTC said that my motherboard was damaged...
I notice more and more people have the same issue as me (and you), I am afraid that some of the 2.1 rom might have some wrong drivers that make my phone go wrong.. (because I didn't flash any rom, I only restart my phone while my phone can't boot and SPL changed to S-ON....)
Be careful everyone, hope my finding is wrong..
I've seen the oem command fix the S-ON to S-OFF before, which is why I posted it. Sd card disabling and s-on happen together in those cases.
Come to think of it, the time I got S-ON too was with battery pull and hard rebooting. Maybe S-ON is activated with memory debugging as a flash corruption protection scheme.
littlestrong try checking the integrity of your file system and reflashing your ROM entirely. Sometimes flash just wears out.
There's also the issue of flashing the radio and spl from recovery, as sometimes it causes issues. The best way is to do it with fastboot. I know your SPL is locked so you can't do that though. Your best bet was the oem command with 1.76 HBOOT versions. Other than that it would be playing with serial cables and JTAG.
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
nabor said:
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
Click to expand...
Click to collapse
I've never heard of "oem" commands flashing spl/radio/rec. But you can give the command he gave you a try
The best way would be to use fastboot commands. I don't think a corrupted rom makes it S-ON. I got S-OFF as soon as I flashed my eng spl
O.K. thanks. Got it, seems no solutions yet. I think I should learn the kernel first, it is fundamentally to know how a ROM, a system works!
And sorry for my poor English, I fund I missed a "y" above in "mabe"
can somebody tell me, how in this case I can install a new SPL, or recovery?
Mod. edit: not dev related, moved to general
Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).
knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.
so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814
lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App
knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App
knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit
NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.
Possibly try to re download the sappimg from the mgic spl thread?
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.
NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!
Hello,where can i found a good and easy tuto to make the legend s-off???
I cant find a clear step by step
Thanks a lot !!!!
Hi.. Step by step is given in the process..
Just go to www.alpharev.nl download the iso and boot it.. Then you are instructed..
Othervise search the development section.. There are 2-3 threads regarding this issue..
How safe is this? I am concerned about modified HBoot and partitions, as surely this is the stage that can brick your phone.
There were a lot of horror stories when it came out, have things settled down?
EDIT: I would say it's not very safe at all. My first impressions are that the script is fraught with danger. First try failed to copy files and aborted (perhaps I said yes to install Clockwork Recovery when I already had it?), 2nd and 3rd tried it simply didn't go into fastboot despite pressing the power button loads of times. Each time a nervous battery pull.
Given up, before I end up with a bricked phone.
If a make a nandroid and something with s-off go bad,can i restore the backup and everything is ok?
dangal said:
If a make a nandroid and something with s-off go bad,can i restore the backup and everything is ok?
Click to expand...
Click to collapse
No, if HBoot flashing fails, the phone is bricked.
Ok,was easy,make a iso boot cd,3 steps and everything is ok i have s-off in the legend
@CrazyPeter: I think it's more scary than dangerous. The timing in step 1 and 2 is way off, but step 3 is straight forward(this is the dangerous part). You just have to make sure the phone is connected.
Edit: I had to count to about 4.5 seconds after the -------> before pressing power. When it tells you to press power it's to late.
Sent from my Legend using XDA App
You certainly need to know what you are doing.
It's VERY possible you get lucky and get past stage2 but fail on stage 3 timing, if this is the case, then you have a partly updated boot and you need to boot recovery and nandroid backup (in the Advanced restore) the Boot partition and then try everything from the beginning again.
It took me 5 times round this route. It wouldn't be so bad if the script detected that you were restarting after the first timing critical bit and carried on from there.
As I remember there are no timing on step 3, only 1 and 2. Once you get past step 2 it's pretty easy. It can still go wrong though, if you loose connection when the bootloader is flashing during the 3rd step.
Sent from my Legend using XDA App
Now i have S-off,to enter in recovery mode what is the bets method?
Hello!
I've read lot of different topics here, but still cannot find exact answer for my questions.
I have a HTC Legend Device with S-ON.
It's CID is HTC__038, and HBOOT version is 1.01.0000
Do I have any chance to S-OFF my device? Does success of S-OFF'ing depends on how fast you press buttons during procedure? Can I still use custom ROM's without s-offing my phone?
Thanks a lot!
vpupkin said:
HBOOT version is 1.01.0000
Do I have any chance to S-OFF my device? Does success of S-OFF'ing depends on how fast you press buttons during procedure? Can I still use custom ROM's without s-offing my phone?
Click to expand...
Click to collapse
You cannot S-OFF your Legend if the HBOOT version is above 1.00.
The chances of an S-OFF success do not solely depend on "how fast you press buttons".
You can still use custom ROMs without S-OFF.
S-OFF
Can i use AlphaRev 1.8 HBOOT reflash utility with temp root to get S-OFF, i have an unbranded legend, open network phone (not sim locked) and HBoot 0.43.0001, Radio- 7.05.35.26L, I'd like to try CyanogenMod. I have been trying to root my phone using paul modaco's tutorials with no luck. Please help
To install AlphaRev your Legend must be rooted first.
Hi guys,
I've tried many ways to fix and hope that some light could be shed from you
- Trying to get back to stock build after downgrading to 1.31 via this process wiki.cyanogenmod.com/wiki/HTC_Legend:_Full_Update_Guide
- The ‘rooting tools’ in step 2 of 2nd section were not available anywhere so tried other avenues to root
- None successful
- After lots of playing around – I decided to try and get back to latest stock build
- Ran the uncracking.bat file which was installed during the Cyanogenmod process (which I hoped would restore things)
- Not successful
- I’m thinking that maybe the adb shell command from the Cyanogenmod process may have caused some issue: /data/local/flash_image misc /data/local/misc1-2.img
- Trying the HTC OTA system update (from Android 2.1 to 2.2) fails while trying to update and goes into the recovery screen (red triangle with exclamation mark, black background) <<<<<<<<<
- Then, when pushing vol up and power the following error is shown:-
----> E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
Any help would be greatly appreciated..
Doing a general factory reset does not seem to help.
I do not need to keep any apps or data, a complete wipe so I can start afresh would be great if possible!
Thanks
94 views and no replies.
Oh dear
I tried to return to stock rom by running the wwe rom from shipped-roms only got the error 155. Then extracted the rom.zip from the exe and flash that no go, couldn't work out a way to do it successfully.
Sent from my Legend using xda app-developers app
Cool.. It doesn't have to be stock. All I need is 2.2 or 2.3 (I was trying for cyanogenmod 7.2). At the moment it's stuck on a buggy 2.1!
I'm not sure of the current state, as I said I think going half way through the cyanogenmod kinda of changed something important ( eg. /data/local/flash_image misc /data/local/misc1-2.img via ADB).
Do you know of any way I could make either of these OSs work, with the minimum of hassle?
ranger4740 said:
I tried to return to stock rom by running the wwe rom from shipped-roms only got the error 155. Then extracted the rom.zip from the exe and flash that no go, couldn't work out a way to do it successfully.
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
1st thing 1st, unlock your bootloader.
2ndly, once unlocked, flash cwm.
3rd, download any ROM you want (lets pick cm 7.2 for starting point since you said no need for stock ROM) then put into your sd card.
Lastly, boot into cwm. Wipe all (data, cache, dalvik cache) then Flash(install) ROM.
Thats it (assuming your device is not usb bricked or hard bricked and you do all the steps correctly).
How?
To unlock, go to htc web site or google "unlock bootloader+htc dev"
Flash cwm? Go to dev section, theres a thread of cwm, follow "s-off" method (of course after unlocking your BL.
Boot into cwm? Shut down/turn off your phone. Once it off, press power button and volume down at the same time, hold it fow few moment before release it.
Once in cwm, install from sd card (you will know once you in it)
Then? Enjoy ur legend and flash any ROM once you got bored with cm7!
Sent from my Legend using xda app-developers app
Thanks for the response.
Firstly: -
- HTC Sync is not reading my (I think needed for HTCDev boot unlock)
- I did try just running the HTC Dev RUU - but it said I need to update the ROM(?) (from Build 1.31), which I believe is done by the HTC OTA update, which doesn't work
HBOOT 1.00
S-ON
Build 1.31
Not allowing update as loops into recovery with E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
feed3 said:
1st thing 1st, unlock your bootloader.
2ndly, once unlocked, flash cwm.
3rd, download any ROM you want (lets pick cm 7.2 for starting point since you said no need for stock ROM) then put into your sd card.
Lastly, boot into cwm. Wipe all (data, cache, dalvik cache) then Flash(install) ROM.
Thats it (assuming your device is not usb bricked or hard bricked and you do all the steps correctly).
How?
To unlock, go to htc web site or google "unlock bootloader+htc dev"
Flash cwm? Go to dev section, theres a thread of cwm, follow "s-off" method (of course after unlocking your BL.
Boot into cwm? Shut down/turn off your phone. Once it off, press power button and volume down at the same time, hold it fow few moment before release it.
Once in cwm, install from sd card (you will know once you in it)
Then? Enjoy ur legend and flash any ROM once you got bored with cm7!
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
Curveau said:
Thanks for the response.
Firstly: -
- HTC Sync is not reading my (I think needed for HTCDev boot unlock)
- I did try just running the HTC Dev RUU - but it said I need to update the ROM(?) (from Build 1.31), which I believe is done by the HTC OTA update, which doesn't work
HBOOT 1.00
S-ON
Build 1.31
Not allowing update as loops into recovery with E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
No, you dont need htc sync. i've never installed htc sync either. you only need the driver (which is logically will be installed along with htc sync but also can be installed separately and it is needed so that your device will be recognized when you boot it into fastboot mode) and no, you no need to upgrade ROM, you only need to upgrade your bootloader (that HBOOT 1.00) and it is not updated through OTA.
Seriously, it took me only 2 hours (including downloading and installing SDK, driver, waiting for unlock file from htc etc) last time i did it and i have done it twice which 2nd time (because i had usb soft brick) is much more shorter as i saved the unlock file and it seems can be reused. What takes longer for me at that time is to understand the whole process, reading and researching through multiple sites but now you have a guide, so all you have to do is to read the instructions carefully. Once you unlock your bootloader and flash cwm, everything will be super easy (assuming your device doesn't have any defects from the beginning.)
Ok, thanks very much feed3. Will try this again based your info and the mini guide I've just written myself.
But before I go ahead, I'd rather not touch it than to make it unusable.
What does USB Bricked and Hard Bricked mean?
Thanks
----------------------------------
My guide:-
After reading the latest reply at XDA decided to give the root another go:-
http://forum.xda-developers.com/showthread.php?p=29969951#post29969951
- Seems need to upgrade HBOOT (to use the HTC Dev boot unlocker)
o See here post 62 and poss (BEFORE THIS READ NEXT BIT) 74 http://forum.xda-developers.com/showthread.php?t=1498298&page=7
- READ HERE FIRST Looks like other people have had issues using stock Vodaphone 2gb SD card for goldcard. Get another and try. Go post that states ‘EDIT: It seems the LEGEIMG is not getting loaded’ that and the few posts after explain what’s happening. http://forums.whirlpool.net.au/archive/1657826
- So neeed to have a gold card in to make the above work <<
o Looks like this can do an auto gold card for you https://sites.google.com/site/roothtchero/goldcard-2. Remember to format to FAT32 in windows as opposed to phone. SEE Hubdolt POST WHICH TALKS ABOUT FORMATTING VIA THE CMD LINE (FOR VODAPHONE LEGEND)
Curveau said:
Ok, thanks very much feed3. Will try this again based your info and the mini guide I've just written myself.
But before I go ahead, I'd rather not touch it than to make it unusable.
What does USB Bricked and Hard Bricked mean?
Thanks
----------------------------------
My guide:-
After reading the latest reply at XDA decided to give the root another go:-
http://forum.xda-developers.com/showthread.php?p=29969951#post29969951
- Seems need to upgrade HBOOT (to use the HTC Dev boot unlocker)
o See here post 62 and poss (BEFORE THIS READ NEXT BIT) 74 http://forum.xda-developers.com/showthread.php?t=1498298&page=7
- READ HERE FIRST Looks like other people have had issues using stock Vodaphone 2gb SD card for goldcard. Get another and try. Go post that states ‘EDIT: It seems the LEGEIMG is not getting loaded’ that and the few posts after explain what’s happening. http://forums.whirlpool.net.au/archive/1657826
- So neeed to have a gold card in to make the above work <<
o Looks like this can do an auto gold card for you https://sites.google.com/site/roothtchero/goldcard-2. Remember to format to FAT32 in windows as opposed to phone. SEE Hubdolt POST WHICH TALKS ABOUT FORMATTING VIA THE CMD LINE (FOR VODAPHONE LEGEND)
Click to expand...
Click to collapse
in short, hard bricked means your phone is totally unuseable, usually because of hardware defects but also might be cause by flashing wrong ROM, for example flashing ROM that actually not built for your device. Usually, you cannot do anything with it, cannot enter fastboot, recovery etc. Soft brick is repairable, you still can boot to recovery or even to the OS. Might be caused by some partition corruption (in the case of usb bricked, it is /misc partition).
If you use htc dev path to unlock your bootloader, no need for gold card. Thats for sure.
If your phone is usb soft bricked (among the symptoms are you will be able to boot into the OS ONLY if your phone are pluged in into usb, and/or adb not working at all) then google or search in xda for "htc legend+usb brick" and fix it. I'm pretty sure only then you can update your HBOOT and therefore unlock your bootloader via htc dev.
Once done, go to HERE and flash cwm using s-off method (dont care about your s-on that you see in your bootloader, the "UNLOCKED" word in it is more important)
In response:-
Thanks for the clarification.
- when using the process here http://forum.xda-developers.com/showthread.php?t=1498298&page=7 - and trying to get the bootloader to run the LEGEIMG.zip file, it flashes up stating "no image or wrong image!", it runs too fast to read it exactly.
- then looking at the same error this guy was getting at (see the 'EDIT: It seems the LEGEIMG' post onwards) http://forums.whirlpool.net.au/archive/1657826 - they have the same Vodfone Legend as me, a gold card had to be used to do the above update process (which should update HBOOT).
- this is the only HBOOT update process I've seen, but isn't clear as they look like they're on 2.2 and HBOOT 1.01.
............................Good grief
feed3 said:
in short, hard bricked means your phone is totally unuseable, usually because of hardware defects but also might be cause by flashing wrong ROM, for example flashing ROM that actually not built for your device. Usually, you cannot do anything with it, cannot enter fastboot, recovery etc. Soft brick is repairable, you still can boot to recovery or even to the OS. Might be caused by some partition corruption (in the case of usb bricked, it is /misc partition).
If you use htc dev path to unlock your bootloader, no need for gold card. Thats for sure.
If your phone is usb soft bricked (among the symptoms are you will be able to boot into the OS ONLY if your phone are pluged in into usb, and/or adb not working at all) then google or search in xda for "htc legend+usb brick" and fix it. I'm pretty sure only then you can update your HBOOT and therefore unlock your bootloader via htc dev.
Once done, go to HERE and flash cwm using s-off method (dont care about your s-on that you see in your bootloader, the "UNLOCKED" word in it is more important)
Click to expand...
Click to collapse
Curveau said:
In response:-
Thanks for the clarification.
- when using the process here http://forum.xda-developers.com/showthread.php?t=1498298&page=7 - and trying to get the bootloader to run the LEGEIMG.zip file, it flashes up stating "no image or wrong image!", it runs too fast to read it exactly.
- then looking at the same error this guy was getting at (see the 'EDIT: It seems the LEGEIMG' post onwards) http://forums.whirlpool.net.au/archive/1657826 - they have the same Vodfone Legend as me, a gold card had to be used to do the above update process (which should update HBOOT).
- this is the only HBOOT update process I've seen, but isn't clear as they look like they're on 2.2 and HBOOT 1.01.
............................Good grief
Click to expand...
Click to collapse
EXACTLY the same error message that you got, HERE and the op solve it.
Btw, during unlocking my bootloader, i've never encounter (or did i forget already??) to requiring this zip file. Isn't bootloader RUU from HTCdev is all we need? I think thats the only file i have to get (apart from the unlock bin file of course) if my memory doesn't cheat me..
Sure - but as the guy mentions formatting to FAT32, that's usually associated with goldcard creation right.
I've ran the bootloader RUU from HTC Dev a few times, and it always says that the ROM (HBOOT, build(?)) needs updating. Thus trying the aforementioned process (post 62 http://forum.xda-developers.com/showthread.php?t=1498298&page=7) to try and get the Rom (HBOOT) updated, which didn't work, which then loops back round to dealing with the zip file read error.
feed3 said:
EXACTLY the same error message that you got, HERE and the op solve it.
Btw, during unlocking my bootloader, i've never encounter (or did i forget already??) to requiring this zip file. Isn't bootloader RUU from HTCdev is all we need? I think thats the only file i have to get (apart from the unlock bin file of course) if my memory doesn't cheat me..
Click to expand...
Click to collapse
I'm getting more confuse here. I've never use goldcard as i reluctant to "sacrifice" my one and only card but here i am with unlocked bootloader. The RUU file is the one that will update your bootloader. Read instructions at htc dev carefully.. good luck..
Sent from my Legend using xda app-developers app
You need to read this post by blay0, it instructs how to update hboot without going back to stock, using gold card or any other outdated method of rooting (unless your on hboot less than 1.00 then you should follow the s-off method of rooting)
http://forum.xda-developers.com/showthread.php?p=22613990
Sent from my Legend using xda app-developers app
I think the reason I can't do the blay0 method is because of the stock sd card I'm using. It's not picking up the rom zip file.
I've ordered another http://www.kikatek.com/P188409/SDC10-8GB-Kingston-MicroSDHC-8GB-Card-Class-10?source=froogle
Will try again, and if that doesn't work - try this other method (as the guy here has HBOOT 1.00 and a Vodafone Legend too) http://chrg.zxq.net/htc-legend-root.html.
Many thanks for all your help people.
Will report back any success for the benefit of others.
All the best
ranger4740 said:
You need to read this post by blay0, it instructs how to update hboot without going back to stock, using gold card or any other outdated method of rooting (unless your on hboot less than 1.00 then you should follow the s-off method of rooting)
http://forum.xda-developers.com/showthread.php?p=22613990
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
Hi guys,
Good news! I unlocked the bootloader with my 'new' SD card using the blay0 process (from the last post).
This is the first time I've done this though, and am just trying to figure out how to flash CyanogenMod 7.2.
ROM Manager doesn't work with 2.1 (installed) any more.
Can someone please briefly explain how I would flash.
Many thanks
Curveau said:
I think the reason I can't do the blay0 method is because of the stock sd card I'm using. It's not picking up the rom zip file.
I've ordered another http://www.kikatek.com/P188409/SDC10-8GB-Kingston-MicroSDHC-8GB-Card-Class-10?source=froogle
Will try again, and if that doesn't work - try this other method (as the guy here has HBOOT 1.00 and a Vodafone Legend too) http://chrg.zxq.net/htc-legend-root.html.
Many thanks for all your help people.
Will report back any success for the benefit of others.
All the best
Click to expand...
Click to collapse
SOLVED
Ah, done !! Woohoo!
That was lots of work. Well, easy via the HTCDev method <<
To get 7.2 on followed here:-
see s-off method to install recovery image http://forum.xda-developers.com/showthread.php?t=1290841&highlight=clockwork
To get into the recovery – use the col down + power button
Follow Method via Recovery here http://wiki.cyanogenmod.com/wiki/HTC_Legend:_Full_Update_Guide
Good luck everyone and thanks again XDA
Curveau said:
Hi guys,
Good news! I unlocked the bootloader with my 'new' SD card using the blay0 process (from the last post).
This is the first time I've done this though, and am just trying to figure out how to flash CyanogenMod 7.2.
ROM Manager doesn't work with 2.1 (installed) any more.
Can someone please briefly explain how I would flash.
Many thanks
Click to expand...
Click to collapse
Hello,
take the recovery-clockwork-5.0.2.0-legend.zip , put it on your SD-card and rename it to update.zip. Then use th S-ON-method from here and you will have no problem.
so there is no way to return the legend back to stock rom after all ?
Hello, I have been having loads of problems with reception (staying in 2g mode, staying completely offline all day until I notice and toggle airplane mode, etc.), so I really wanted to try a new radio.
I started in this thread: http://forum.xda-developers.com/showthread.php?t=2115197 which was really encouraging. I got all the way up to setting up ADB and having the phone verified to be attached while in bootloader fastboot. However, every time i try to send the command: "fastboot flash radio radio.img" i get this error: failed <remote not allowed>
I have researched that error and came across multiple forums. There weren't many answers, other than that the bootloader might be locked, or isn't in s-off mode. I can confirm that my bootloader reads:"S-OFF" on the top line. So, I am thinking it is locked then?
I will update the bootloader if i absolutely need to, but I was hoping to get some last words of advice before I do. It seems like that should be the very last resort. Especially after reading that I might have to use the bootloader to flash every kernel if I use a new rom with a different kernel than the one i am currently on. I am also worried about bricking the device, although, I am pretty careful. Oh, and I don't care at all about the warranty. This phone is years past that by now.
Also, I have tried renaming the file to PD15img.zip and dropping it in the root of the SD card to attempt flashing it with HBOOT in the bootloader; but it says: "wrong zipped image". I already double and triple checked that the md5 code matched, even after renaming it.
So, any advice? is it possible that there is another way to do this besides using the bootloader? Like using CWM? I am on CWM
touch v5.8.1.0 BTW
Or, could i maybe upgrade the bootloader, use adb fastboot to change the radio, then switch back to the bootloader i am currently on to avoid complications in the future? Or, since I am still a total n00b, is there any chance I am just doing something wrong with ADB?
In case it helps for reference, this is all of the info about my bootloader that I can read while in that mode:
GLACIER PVT SHIP S-OFF
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010
Thank you so much for anyone who is willing to help me tackle this. This old phone has been all I can afford lately, and it has been my sole source of internet at home via tethering. Having even a marginally better radio reception would make a world of difference.
Cheers!
S off equals unlocked boot loader.
All good there.
Grab the 4ext app from
4ext.net
And install 4ext recovery, much better. Then try flashing whatever you want. Gotta be careful, Some radios can brick if you mess up.
Sent from my iPhone using Tapatalk
Thanks so much for the help. I really did like cwm touch, but I'll switch if 4ext will allow me to do this. Do you think I could mess anything up if I just tried flashing it in cwm? Also, (super n00b question here) should I rename the file to be .zip? I would assume so I just want to be certain.
kinsaturated said:
Thanks so much for the help. I really did like cwm touch, but I'll switch if 4ext will allow me to do this. Do you think I could mess anything up if I just tried flashing it in cwm? Also, (super n00b question here) should I rename the file to be .zip? I would assume so I just want to be certain.
Click to expand...
Click to collapse
Nahh Just install the app and let it do it's work.
The recovery is also touch.