Hi ppl, I am a magic dev, but i wanted to ask few q's about rooting wildfire and its new bootloader. So, my friend has one and updated it to latest froyo and yesterday we tried rooting it via unrevoked and find out that it doesnt root it with same error "firmware too new". However i noticed that bootloader is S-off (on HTC magic t means fastbooot is enabled to write radios and recoverys and other bootloaders). So my question is why didnt some1 tried installing recovery via fastboot since its s-off and is it possible that way????
If it's s-off all you need to do is downgrade to 2.1 (by flashing an RUU I think) then run Unrevoked
WoblyGoblin said:
So my question is why didnt some1 tried installing recovery via fastboot since its s-off and is it possible that way????
Click to expand...
Click to collapse
i tried this nethod. process fails on signature check.
If you have succesfuly downgraded to 2.1 using a ruu and unrevoked is installed succesfuly, you need to
1. Copy a costum ROM in the root directory of your sdcard
2. Boot in recovery en search for "disable/enable signature check", and select it using your trackball
3. Search for "apply update.zip from sdcard", or something like that. Afther conforming the process should start.
I'm sorry that my instructions aren't that clear - i dont have the recovery myself due to the official froyo update. And I'm sory for my spelling errors
Good luck,
Erwin
Point is i need his nand backup to make him a rom as i am dev. And dont want to revert to 2.1. No1 answered to my question since it is s-off does it have fastboot access for fastboot commands like:
fastboot flash recovery xxxxxxxxx.img?????
WoblyGoblin said:
Point is i need his nand backup to make him a rom as i am dev. And dont want to revert to 2.1. No1 answered to my question since it is s-off does it have fastboot access for fastboot commands like:
fastboot flash recovery xxxxxxxxx.img?????
Click to expand...
Click to collapse
I tried to do it via fastboot flash recovery xxx.img as I did on a Nexus One, but didn't work. I don't remember the error, but basically didn't have access...
Had to use a test version of Unrevoked. Look this thread and try it: http://forum.xda-developers.com/showthread.php?t=993102
antonio1475 said:
I tried to do it via fastboot flash recovery xxx.img as I did on a Nexus One, but didn't work. I don't remember the error, but basically didn't have access...
Had to use a test version of Unrevoked. Look this thread and try it: http://forum.xda-developers.com/showthread.php?t=993102
Click to expand...
Click to collapse
for 93$ and shipping for that price you cannot get a android phone.
devil-strike said:
for 93$ and shipping for that price you cannot get a android phone.
Click to expand...
Click to collapse
Sorry, what? I don't understand :S
antonio1475 said:
Sorry, what? I don't understand :S
Click to expand...
Click to collapse
You say that the clip cost allot more than a new phone, but for 93dollar you dont have a new android phone, xtc clip cost only 93dollar.
devil-strike said:
You say that the clip cost allot more than a new phone, but for 93dollar you dont have a new android phone, xtc clip cost only 93dollar.
Click to expand...
Click to collapse
Where? The prices at the thread of XTC Clip are around 200$, and in my country it costs around 300$. I was talking with these prices in mind.
devil-strike said:
You say that the clip cost allot more than a new phone, but for 93dollar you dont have a new android phone, xtc clip cost only 93dollar.
Click to expand...
Click to collapse
And by the way, I think I said that in another thread, not in this one.
Related
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
OolonColuphid said:
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
Click to expand...
Click to collapse
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
cigar3tte said:
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
Click to expand...
Click to collapse
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
My apologies, only thought of the G1.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
Are you saying that I wouldn't be able to root using the "traditional" method?
OolonColuphid said:
Are you saying that I wouldn't be able to root using the "traditional" method?
Click to expand...
Click to collapse
Post your phone info before you ask that.
cigar3tte said:
Post your phone info before you ask that.
Click to expand...
Click to collapse
Sorry. It's a US T-Mobile G1
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
HardSPL won't brick phones, not to the same degree as dangerSPL anyways.
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
sprarky said:
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
Click to expand...
Click to collapse
lbcoder said:
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
Click to expand...
Click to collapse
OK cool. Thanks for that. That confirms a few things for me.
Now this might seem a little ignorant but how do i get my root back now? I have done several searches but couldn't really find anything that confirms the exact method for this situation.
If there is no reason to go back to RC29 and do that whole process again then whats the other way of doing it?
As i now have the normal recovery console back any attempt to try and flash CM's just results in the phone telling me i cant su (or don't have root)
Thanks again
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
jackslim said:
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
Click to expand...
Click to collapse
Yeah i do! that sounds exactly like what i need to do. You know of a how-to anywhere for doing this?
Cheers
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
jackslim said:
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
Click to expand...
Click to collapse
Hey,
Thanks for your help. Managed to get it all working they way you described after some searching and a few hours. Thanks again dude.
OolonColuphid - Hope i didn't hijack your thread too badly. Does any of the above information help you out at all? I found it fairly easy to flash the recovery from fastboot then flash back to whatever i want via the recovery console.
Cheers,
Sean
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
ephayzee said:
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
Click to expand...
Click to collapse
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
jackslim said:
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Good looking man, thanks!
Does FlashRec still work on donut, or have they patched that exploit?
OolonColuphid said:
Does FlashRec still work on donut, or have they patched that exploit?
Click to expand...
Click to collapse
OMG! can u not read!
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
!!!UPDATE!!!
Whats Completed,
S-OFF
Custom Recovery
ENG Bootloader.
HBOOT 2.02.0000 is completely cracked.
Advantage of hboot 2.02 > 0.76?
[email protected] said:
Advantage of hboot 2.02 > 0.76?
Click to expand...
Click to collapse
THIS !!!!!!!! >
2.02 is non engineering hboot... so i would think there is not much point... but than again... i think probably 99% of us dont even touch those options.
Uh nothing that i know of, except that HBOOT 2.02 that i have found will NOT downgrade to .76 as they patched it, I tried the eng-PC36IMG.zip, unrevoked etc. They do not root, nand unlock and install recovery.
eng-PC36IMG.zip skips installing the bootloader wich is the HBOOT.
Unrevoked Errors out and will not get past the HBOOT and throws a error saying lost connection.
So far can not downgrade the stupid hboot. This is what happens.
http://img215.imageshack.us/img215/1126/img20101102215418.jpg
amoamare said:
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
Click to expand...
Click to collapse
How did you get s off? Ive been trying everything for the past week
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
amoamare said:
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
Click to expand...
Click to collapse
How did you do it?
Hex edit? Cough cough.
Like i said, more info will be released in a bit. I'm waiting for a response from someone.
kenny21 said:
How did you get s off? Ive been trying everything for the past week
Click to expand...
Click to collapse
If you have s-off then you should be able to make a PC36IMG.zip out of one of these hboots found here http://forum.xda-developers.com/showthread.php?t=801568
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
amoamare said:
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
Click to expand...
Click to collapse
so, will this fix let us root the phone and load recovery and flash roms again? im so tired of being stock lol.
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
amoamare said:
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
Click to expand...
Click to collapse
could we have an ETA on your fix? i would love to try it before i go to sleep ;(
Like i said just waiting on a message from someone and will post from there.
amoamare said:
Like i said just waiting on a message from someone and will post from there.
Click to expand...
Click to collapse
Thanks for the effort. I bought an Evo today with 2.02 Hboot on it. I was afraid to be stuck with stock for a long time.
Ok 2.02 has been successfully cracked all the way.
http://d.imagehost.org/0355/IMG_20101102_233241.jpg
ENG bootloader has been loaded on. All fastboot cmds are restored. Sweet.
It's basically all in the title...
As it is, the wildfire is nor "really" rooted, as there is no way to write to the \system, thus making it impossible to do certain things (ie installing custom hosts file).
If Sunaabh does not do it, is there any way to obtain that WITHOUT using a shell? I've been searching, but I found at least 4 different procedures which claimed to work, but ultimately didn't.
Thanks!
Roms don't make phones get s-off, you need to wait for alpharev or get a xtc clip
kevin2516 said:
Roms don't make phones get s-off, you need to wait for alpharev our get a xtc clip
Click to expand...
Click to collapse
And you can do everything even with s-on using adb and recovery...
E.g. just push the new hosts file using adb or use a flashable zip
so its not impossible.
kevin2516 said:
And you can do everything even with s-on using adb and recovery...
E.g. just push the new hosts file using adb or use a flashable zip
so its not impossible.
Click to expand...
Click to collapse
Is not working if the system is read only, also zipfiles must be signed, and no1 have the Signature, of so you also can install recovery rom.
Thanks to everyone but... this just adds to my confusion. So is it possible or not to flash zip files with s-on?. I would not want to use ADB unless it's absolutely necessary...
Veon11 said:
Thanks to everyone but... this just adds to my confusion. So is it possible or not to flash zip files with s-on?. I would not want to use ADB unless it's absolutely necessary...
Click to expand...
Click to collapse
Of course it is possible to flash ZIP files using S-ON. Majority of the people here are on S-ON systems and still use Custom ROM's, Flashable ZIPs for additional functionality, kernels, radios and stuff.
Oh, and just as an FYI, I would advice you to get over your paranoia of ADB and try it out. It's an extremely useful component.
OK, thanks a lot! Guess I'll have to give ADB a try.
So, i can flash a rom with ADB, with s-on? Do i need temp root? What is the method exactly? Thy
Gurdjieff said:
So, i can flash a rom with ADB, with s-on? Do i need temp root? What is the method exactly? Thy
Click to expand...
Click to collapse
Refer this:
http://forum.xda-developers.com/showthread.php?t=824396
3xeno said:
Refer this:
http://forum.xda-developers.com/showthread.php?t=824396
Click to expand...
Click to collapse
Ok, sorry, this is not so clear for me yet.
If i want to flash a custom rom i need a custom recovery?
But adb show device offline in fastboot (due the new hboot?) so i stuck here.
I found this for Aria, but maybe
http://thetechjournal.com/electronics/mobile/how-to-installing-custom-rom-on-unrooted-htc-aria.xhtml
Gurdjieff said:
Ok, sorry, this is not so clear for me yet.
If i want to flash a custom rom i need a custom recovery?
But adb show device offline in fastboot (due the new hboot?) so i stuck here.
I found this for Aria, but maybe
http://thetechjournal.com/electronics/mobile/how-to-installing-custom-rom-on-unrooted-htc-aria.xhtml
Click to expand...
Click to collapse
Are you on official Froyo release (Or, in another way, HBOOT 1.01)? If that's the case, and, it is on S-ON, then, it is not possible to root.
As for the Aria process, its a bit vague I think. Basically, what he is doing there is rooting, but, I don't think that process works on the Wildfire's new Hboot.
If you are on the older Hboot, just follow the guide step by step I linked above. Its foolproof.
3xeno said:
Are you on official Froyo release (Or, in another way, HBOOT 1.01)? If that's the case, and, it is on S-ON, then, it is not possible to root.
As for the Aria process, its a bit vague I think. Basically, what he is doing there is rooting, but, I don't think that process works on the Wildfire's new Hboot.
If you are on the older Hboot, just follow the guide step by step I linked above. Its foolproof.
Click to expand...
Click to collapse
Ok then i misunderstood you, i thought you talked about that we could flash a rom without root on official 2.2 too.
Anyway thank you for the help
Gurdjieff said:
Ok then i misunderstood you, i thought you talked about that we could flash a rom without root on official 2.2 too.
Anyway thank you for the help
Click to expand...
Click to collapse
Yes, that's what I thought. Since this topic starts with S-OFF, that is why I said you can install Custom ROMs on official 2.2.1. Not on S-ON systems.
Anyway, glad its all clear now.
My phone was made s-off via xtc clip.
It's rooted with superoneclick (couldn't get unrevoked to work).
ROM Manager is in the superuser list and has been granted root access.
In ROM Manager I click "flash clockworkmod recovery", select "HTC Buzz (Wildfire)" and it says "successfully downloaded clockworkmod recovery".
But every time I click "reboot into recovery" I just get a black screen with a phone in the middle and a red triangle.
I then have to remove the battery to get the phone back on.
Any ideas folks ?
I read somewhere that the current version of ROM manager doesn't work with Android 2.2.
Is this right ?
I tried an older version and it appeared to try and install clockwork recovery for a few seconds then I got a black screen with a phone and a red question mark.
try flashing custom recovery with PC49IMG process. get the file from here.
http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
and one more thing, if u get issues with flashing custom roms then try to use different version of recovery.
issues like amend scripting.......
Thanks for the reply.
I tried putting the PC49IMG.zip file in the root of the sd card but when I go into HBOOT it says ....
CID incorrect !
Update Fail !
Do I need to do a factory reset ?
scobodon said:
Thanks for the reply.
I tried putting the PC49IMG.zip file in the root of the sd card but when I go into HBOOT it says ....
CID incorrect !
Update Fail !
Do I need to do a factory reset ?
Click to expand...
Click to collapse
CID error after making S-OFF huh ?
U do have another option. Can try an official RUU of ur region with the radio Radio_13.53.55.24H_3.35.19.25
this gives u hboot 0.80 . Then u can root the phone with unrevoked (use version 3.2).
Would this be ok ?
http://rom.tat.tw/wildfire/extracte...19.25_release_151892_signed_101410_003737.zip
scobodon said:
Would this be ok ?
http://rom.tat.tw/wildfire/extracte...19.25_release_151892_signed_101410_003737.zip
Click to expand...
Click to collapse
The one specific for ur region (if it is there) is more preferable. However it will also be ok.
And better get it from shipped roms website if u havent started the download yet.
here: http://www.shipped-roms.org/shipped/Buzz/
Thanks for the list.
So, is it just a case of running the exe with my phone connected ?
scobodon said:
Thanks for the list.
So, is it just a case of running the exe with my phone connected ?
Click to expand...
Click to collapse
Yes certainly. Connect the phone under charge mode.
No luck.
Got a "customer id error" in the Windows program.
scobodon said:
No luck.
Got a "customer id error" in the Windows program.
Click to expand...
Click to collapse
Sorry, cant go further. That might be due to region. I think there might be ur region RUU in that website there. Don't know completely to solve cid errors. Probably a gold card might be the solution.
But there are solutions for cid errors. Go with this thread (same one as earlier), it might help u. http://forum.xda-developers.com/showthread.php?t=993102
Thanks again for all your help so far, much appreciated.
I found a multi region RUU with the same kernel as the one I'm on.
Do you think flashing this will allow me to then flash one of the older RUUs ?
Also, if I do this will it make my phone s-on again ?
scobodon said:
Thanks again for all your help so far, much appreciated.
I found a multi region RUU with the same kernel as the one I'm on.
Do you think flashing this will allow me to then flash one of the older RUUs ?
Also, if I do this will it make my phone s-on again ?
Click to expand...
Click to collapse
When ur phone has S-OFF (by xtc clip) u can flash any wildfire RUU of ur region (i mean downgrading hboot is also possible). Yes u can flash older RUU also, that's what u attempted to do with that WWE ruu.
Once u do S-OFF by xtc clip, then u can't get back to S-ON in any way. XTC clip directly wipes off the secure flag in the radio NVRAM. So, AFAIK, there is no way for u (by xtc clip) to get back to S-ON even when u flash an updated hboot.
But alpharev2 (not yet released for wildfire) will patch the hboot to make it think that the secure flag is off. So, if done by alpharev S-OFF is not permanent. When done S-OFF with alpharev, then if u flash an updated hboot, the phone returns to S-ON. This is not the case with u.
Tried the RUU with the same kernel that's on my phone but got the "customer ID error" again.
I'm starting to think something went wrong when they used the xtc clip.
When I get the red triangle in HBOOT, if I press vol up + power I get the message "failed to verify signature".
I thought having s-off was supposed to bypass the signature checks
scobodon said:
Tried the RUU with the same kernel that's on my phone but got the "customer ID error" again.
I'm starting to think something went wrong when they used the xtc clip.
When I get the red triangle in HBOOT, if I press vol up + power I get the message "failed to verify signature".
I thought having s-off was supposed to bypass the signature checks
Click to expand...
Click to collapse
AFAIK, after S-OFF it should skip the signature check. That is how we can flash the custom recovery through PC49IMG process.
There is a full guide of XTC clip rooting in the development section. If u think something went wrong when they used xtc clip, u might get an answer there. link: http://forum.xda-developers.com/showthread.php?t=1057524
And also one more link to what we can do after S-OFF here.
link: http://forum.xda-developers.com/showpost.php?p=13025129&postcount=3
In that try the fastboot flash recovery command. May be a hope
Woo hoo, success !!
I made a goldcard and the RUU installed fine.
I now have Android 2.1 and HBOOT 0.80.0007.
I guess the goldcard is where I was going wrong.
Edit : Just got unrevoked to work first time too.
And now I've got CM7 installed !!!
A very happy bunny.
Many thanks again for the help and advice.
Wouldn't have got it working without this forum.
That's fine.
Sent from my HTC Wildfire using XDA App
hey guys everytime i try to flash a recovery in fastboot it comes up
FAILED (remote: not allow)
is there away to fix this issue as most of the spl eng files are no longer downloadable due to sites being closed
You... don't flash it in fastboot? Just a suggestion
Do I not? How do I flash it then as I only have stock recovery?
1. Get root
2. Install rom manager
3. Try to flash recovery from list
P.s. in extra cases there is trouble with flashing recovery through rom manager, so you have to flash it manually (read one of sticked topics in general section)
Sent from my A7-040 using Tapatalk
Rom manager won't install iv already tried that option. Is it anything 2do with hboot?
DanOMac said:
Rom manager won't install iv already tried that option. Is it anything 2do with hboot?
Click to expand...
Click to collapse
No. This mode solves other problems...
You need follow this manual: http://forum.xda-developers.com/showthread.php?t=756918
If you have root already, then do steps 5, 7 and 9
iv already tried everything on the link u posted I'm losing my patiants with this old phone think I will just quit at go back 2playing around with my sensation
DanOMac said:
iv already tried everything on the link u posted I'm losing my patiants with this old phone think I will just quit at go back 2playing around with my sensation
Click to expand...
Click to collapse
Yep, but you did not provide any technical info about troubles, that i can not help you.
What info would u like to no
DanOMac said:
What info would u like to no
Click to expand...
Click to collapse
What is exactly problem, when you are flashing recovery manually?
I try 2push it in fast boot and it says remote not allowed
DanOMac said:
I try 2push it in fast boot and it says remote not allowed
Click to expand...
Click to collapse
And why are you using fastboot?
Because I only have stock recovery and from manager will not install wot other ways are there 2flash it
Manually from adb or a terminal emulator
Or try this app: http://db.tt/VuMG4Owy (don't remember where I got it.. if its a paid app, I will remove it. Link will be removed in ~24 hours)
the app in the link does not work says my device htc magic is not supported
all sorted folks i made a goldcard flashed new spl and got s-off recovery flashed fine after that thanks for ur help