I've seen about 20 posts on how to root my Mytouch 4G, but I still can't do it! When I try and run SU, I get errors. However, I've managed to S=OFF, which I can't even imagine how. Here's what my boot screen is showing:
Glacier PVT ENG S-OFF
HBoot-0.85.2007 (PD1510000)
Microp-0429
Radio-26.03.02.26_M
eMMC-boot
OCT 11 2010, xx:xx:xx
There seems to be a few different set of instructions, but none seem to be working. I've tried the VISIONary way, as well as the other methods.
if you are s=off with the .85 engineering screen all you need to do is download VISIONary.apk
Temp root
perma root.
done.
Thanks N, but I can't seem to get that to work. I have Visionary r14. Also, when I reboot, at the loader screen, I started seeing some "pxxxx.zip" files getting errors, such as "wrong image". Not sure what I need to do...
Chicago T said:
Thanks N, but I can't seem to get that to work. I have Visionary r14. Also, when I reboot, at the loader screen, I started seeing some "pxxxx.zip" files getting errors, such as "wrong image". Not sure what I need to do...
Click to expand...
Click to collapse
I have the same screen as you with the eng bootloader.
When I do volume down + pwr I also get the boot screen and goes through a pd15img wrong image yada yada.... I thought that was normal????
However I have s off and su works for me in terminal.
Sent from my HTC Glacier using XDA App
The root methods follow this pattern:
1. Temproot with VISIONary
2. Run a script to get S-OFF (I recommend gfree for this)
3. Permroot with VISIONary
You have the Engineering bootloader (HBoot-0.85.2007), so I assume you used the root.sh script. Did you attempt permroot with VISIONary afterwards? That should be all you have to do (make sure to uncheck temproot on boot when you do).
Ignore that stuff about PD15IMG, that's normal. The bootloader is looking for a file on your sd card named PD15IMG.zip and isn't finding it. That zip file (which you can find on these forums) is used to revert back to stock.
If you have s-off all you have to do is temproot again, flash clockwork recovery, and flash away. My phone did same thing, once you get a recovery you're good to go.
what neidlinger said. plus,
"You have the Engineering bootloader (HBoot-0.85.2007), so I assume you used the root.sh script."
the main gree thread also has a bootloader part which is what i used - he could have done that too, which is diff than root.sh. i think we dont really know how he got to where he is.
chicago- what i learned when i rooted is that gfree or your method just turns s=off. that's not rooting, it's just removing radio security so that you can then root- you still like neidlinger said have to then run visionary+ to do it again.
you run it once to let gfree or root.sh work, then you run it again to actually gain root. the only thing is that i would download visionary+ 11, as many instances have shown that 14 doesnt do the job on some phones. 11 is older, but seem to work more often. uninstall 14 and install 11.
just run it, make sure "set to rw" is checked, nothing else checked. make sure usb debugging is checked on your phone. than reboot again after running visionary, you should be ok. my 1st time i ran it, it hung. then i removed the battery, and in terminal i couldnt get su. i ran visionary+ 11 again, with the settings described, then rebooted, and boom, i was su.
Also make sure you don't have a PDIMG15.zip or whatever it's called on the root of your sdcard or that'll keep effing up with bootloader. And make sure "temproot on boot" isn't checked cause that kept screwing up my roots too. Following jdkoren's instructions should get the job done for you. Good luck!
yeah i forgot to also say the i get that looking for pdming whatnot when i boot into hboot, but i thought that was normal - looks like it always checks for a zip file it needs to restore stock, and when it doesnt find it on the SD root, it assumes you dont want to, or need to restore your phone, which is good.... one day when you need to restore, you could put that file on your sd card, reboot, and boom, it'll pick it up.
so, it's normal it seems.
Related
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.
I rooted my phone using the method at theunlockr.com but I read somewhere not to root your phone that way because it does not get you true s-off? My phone says s-off and I have been flashing roms without problems so far, just curious after reading that. Anyone know if this is true?
Here is what I did:
open visionary, check "Set system r/w after root" on
run temproot
open terminal and entered:
su - got super user
cd /sdcard/root
sh root.sh
That's what I used for rooting my first MT4G and didn't have any issues whatsoever so I don't see what's wrong with it. I used gfree second time and if I remember correctly your method was easier but gfree sim unlocks your phone to be used with different carriers.
Sent from my HTC Glacier using XDA Premium App
Towle said:
I rooted my phone using the method at theunlockr.com but I read somewhere not to root your phone that way because it does not get you true s-off? My phone says s-off and I have been flashing roms without problems so far, just curious after reading that. Anyone know if this is true?
Click to expand...
Click to collapse
Something like that. Using root.sh will put the engineering bootloader on your device and basically "forges" messages to HBoot when it asks the radio whether you have S-ON or S-OFF. You'll be able to flash ROMs and stuff.
The gfree script will actually give you radio S-OFF, as well as unlock your SIM and unlock your Carrier ID (SuperCID). You can still use it even if you already did the root.sh script, just follow the directions in that thread and ignore anything to do with VISIONary.
After hearing about the potential issues with the gfree method i decided to go back and completely unroot my phone and start fresh from the traditional method. Everything seems to be fine except one small problem, no matter what i cannot get S=ON. I've tried the gGfree unroot method, ive never installed the ENG boot loader, i did use the gfree command to turn the flag off but the reverse command doesn't seem to turn it back on either. Ive even re flashed a stock image file through Hboot but alas no luck. Any pointers?
Do you have a link for the potential issues? I am curious about what they are.
http://forum.xda-developers.com/showthread.php?t=1079025
Its been getting worse recently judging from the number of posts about it.
Doogitronix said:
http://forum.xda-developers.com/showthread.php?t=1079025
Its been getting worse recently judging from the number of posts about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1035278
Hey could you tell me if this is also gfree? I am new to the MT4G so im not so caught up with certain terms yet. I ill get ENG SPL then to be safe.
That is the Gfree method. For now its probably best not to use it until the causes of the bad partition issues are found and resolved.
Rooting the phone with either method can cause this,no one knws why & how this happens,it just does.. I mean if u full wipe completely at least twice & let the kernel set after phne boots,u shouldnt have this issue just be mindful of what u doin.. Flash recovery before goin into clockwork to wipe system,thats what I do & havent had this problem since my 1st mytouch 4g
Mytouch 4g-White
Root Method-gfree
Permrooted s=off
CWR-3.0.2.4
Rom-Royalginger v2.0
Kernel-ckisgen-smartass-v1.1
You may be right, but back to the original issue i still cant get S=ON no matter which method i use to root or unroot. I did find something odd though when rooting with the root.sh file, i get this error.
sh root.sh
Inserting kernel module
insmod: init_module '/sdcard/root/wpx.ko' failed (Function not implemented)
Duplicating hboot
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.650 secs (1613193 bytes/sec)
I wonder if that's an issue.
On a side note i went ahead and flashed the ENG boot loader and it shows my CID is still CID = 11111111, which from what i have read is all around SU permissions on the phone. One more question, how do i find out if i successfully re locked the SIMLOCK?
I wanted to thank you for informing me of this and I hope you fix your MT4G too, now I have upgraded to eng for safety.
-Best wishes
Looks like i found a resolution! I followed jjackson56's method detailed here
http://forum.xda-developers.com/showthread.php?t=924923&highlight=unroot
but instead of running the script i went by the helpful tip of one of the commentators on the thread erickdj who basically spelled it out for me.
"I was having issues using the automated script to unroot(mostly to turn s-on), so I realized all I needed to do was run "./gfree --secu_flag on" to turn security "ON" and then flash the PD15IMG.zip file through hboot, that set the phone back to stock really fast and easy. Didn't have to mess with part7backup files or nothing like that. "
So in summary, download and unzip the PD15IMG.zip to your sd card from that thread and run the "./gfree --secu_flag on" then reboot into hboot and select yes to run the update, itll take restart if you have the ENG bootloader because it relflashes the stock hboot then itll carry on and restore everything else.
(Note i used this process while on an ENG bootloader obviously so if you try with a stock hboot and fail consider flashing an ENG loader then trying again)
The 2 root methods i know about
1. sh root.sh
2. gfree
is there any other ?
Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
How is the progress on fixing your phone?
jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary
I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it
Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio
I got my sisters Wildfire here and it's stuck in a bootloop.
It is NOT rooted, has no S-Off and so on.
It has the stock rom.
It didn't run fluently, so I just rebooted it. But since then it doesn't boot.
Tried taking out battery, putting it back in, no success.
Tried taking out SD-Card. no success.
Then I booted into Bootloader (Vol + Power down).
Buzz PVT Ship S-ON
HBOOT-1.01.0001
MICROP-0622
TOUCH PANEL-ATMELCO 3_16ac
RADIO-3.35.20.10
All I get to choose is Fastboot, Recovery, Clear storage and Sim-lock.
Recovery turns out to be nothing, I can't get to it. Might be, because there is no CWM on it.
I was lucky to be able to root and s-off my DHD, so I don't have any idea, how to fix this problem with the Wildfire.
Any suggestions how to solve this little problem?
Thanks in advance
Which method u adopted for rooting....try revolutionary method and u will be s-on....bt ur mobile doesn't on....try to intall ruu which can be downloaded from shipped-roms.com,download wwe version file....run it,it will install stock rom again,then enable debugging mode,goto revolutionary.io fill the form and copy generated alphanumeric code carefully and download the file run it and u will get s-on....
Sent from my HTC Wildfire using XDA App
Thanks, but actually I neither want root nor s-off on it...I just want to get this smartphone to boot again...I'll try to get the RUU on it, like you suggested
Sent from my Desire HD using Tapatalk
Would "RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_s
igned.exe" be the right one?
And if, what to do next with it?
Thanks in advance
- Extract the Rom.zip from the RUU you listed. Procedure here:
http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
- Rename this zip to PC49IMG.zip
- Place this on the root of the sd card
- Reboot in HBoot mode, the phone will detect the file and will attempt to install. Select Yes and let it proceed.
Thanks, I'll do that when I'm done in University :-D
Just so I have more opportunities in case this happens again.
Could you give me a link to a instruction how to root and s-off?
This would help
And, just in case, which do you think is the best Custom Rom for the Wildfire?
You can use Revolutionary to get S-OFF and Clockworkmod Recovery. Guide here:
http://joel5121.blogspot.com/2011/06/wildfire-22-root-tutorial.html
The only thing that has changed is AlphaRev's Website. The new address is revolutionary.io. Everything else remains the same. Although, you will need a booting device to get it to work.
Lastly, ROM choice depends on whether one would like to keep HTC Sense or not. If not, then I would go with Cyanogenmod / Oxygen (Two ROMs I am pretty sure are available for the DHD as well). And, if you would like to keep HTC Sense, then the current favorites are DK Custom ROM and RemPuzzleROM.
Complete Listing available in the Index Thread linked in my Sig.
Good Luck
I only want to flash a ROM on the Wildfire. My dhd runs on arhd and I won't change that well, unless there's a newer version of arhd
Anyways, what is the best sense ROM
for the Wildfire? Should run smooth but stable and fast. And of course it should've good battery life
Sent from my refrigerator using Tapatalk
I'm stuck myself. Wildfire is working again, but neither can I root nor can I make S-OFF.
On AlphaRevX it "sends in Caroline" and "Caroline" comes out with an error report
However, USB-Debugging was turned on, SD Card active, connected to pc, but "only charge"...
That far for S-Off...
Then I'm trying unrevoked. Works so far, until the Wildifre is in the bootloader. Unrevoked tells me, it's waiting for bootloader. When I choose Fastboot on the device, unrevoked works on and tells me "Waiting for HBOOT to be ready..."
Nothing happens after that. If I choose Bootloader on the device, unrevoked tells me, that it has lost connection to the phone.
Then I tried Gingerbreak. Gingerbreak works, reboots the phone, I check for SU and can't find it. So I guess it's not rooted then :-/
Any suggestions?
Your only (free) option is Revolutionary on Wildfire's with official 2.2.1 and HBoot 1.01.x. Any other method (Unrevoked, Gingerbreak, SuperOneClick etc) will not work and will result in failure. Errors on Revolutionary can usually be treated EXCEPT when it says "Not writing bad block at mtd 0x00000", in which case, there are bad blocks on the NAND memory, and there is no fix yet.
The paid option is to find a store with an XTC Clip hardware box, which can S-OFF the Wildfire as well. They will charge you a 1-time fee for using it.
3xeno said:
Your only (free) option is Revolutionary on Wildfire's with official 2.2.1 and HBoot 1.01.x. Any other method (Unrevoked, Gingerbreak, SuperOneClick etc) will not work and will result in failure. Errors on Revolutionary can usually be treated EXCEPT when it says "Not writing bad block at mtd 0x00000", in which case, there are bad blocks on the NAND memory, and there is no fix yet.
The paid option is to find a store with an XTC Clip hardware box, which can S-OFF the Wildfire as well. They will charge you a 1-time fee for using it.
Click to expand...
Click to collapse
So since this is exactly the fault that is displayed, there is nothing I can do...
But this other tool for s-off ain't working either. If I'd have at least s-off...in this tutorials I first make s-off and afterwards there is a zip archive which will give me SU. Can I install cwm without Root? I'd really like to flash cyanogen...
Sent from my refrigerator using Tapatalk
No, unfortunately, as I stated in my previous post, you cannot.
The best option will be revolutionary but solve ur first problem and then move on to this...we r always here....
Sent from my HTC Wildfire using XDA App