Related
I have flashed the original 2.3 RUU upgrade from Htc dev. The phone is stuck on boot loop. It stays on HTC logo screen for few seconds and then restart again.
History:
I originally had RCMix installed on my phone. Suddenly the phone restarted and then got stuck on Joker screen. I found out that the memory card was corrupted, so reformatted sdcard through windows. Tried re-flashing but again was getting stuck on joker screen.
I flashed RUU's (initially Amoled one and got blank screen for a while) successfully but again was getting stuck on boot screen with no access to recovery , could only access fastboot.
So as a last resort , tried flashing 2.3 upgrade , so its no more stuck on the htc logo now, but keep restarting from that logo screen.
1) I understand it could potentially be a Mboard or Nand issue, but I suspect it could also just be bad sectors on internal memory or some other internal memory corrupt issue. Any thoughts ?
2) I could delete those partitions using fastboot commander but after using RUU , I have got a S-On device now. Is it possible to do S-Off just with fastboot without access to recovery/Adb ?
(Tried asking this on Revolutionary IRC, but no answers)
Got this device from e-bay and htc customer care says they don't honour the warranty after flashing 2.3 upgrade.
PS: I have tried searching and posting on various threads, but still looking for answers. That's why created a new thread.
Bump, Still looking for reply's
ridhavm said:
Bump, Still looking for reply's
Click to expand...
Click to collapse
Have you tried flashing the RUU again? It's the only thing I can think of tat might save your phone..
Yes, tried couple of tmes, goes to the boot loop again
ridhavm said:
Yes, tried couple of tmes, goes to the boot loop again
Click to expand...
Click to collapse
try leaving it for an hour or so, and then stick it in your freezer for 10 minutes in a plastic bag (no joke), then try again with the 2.3 RUU.. not much else you can do I'm afraid.
So is it a bricked device now even when I can access fastboot ?
try to boot it without the sd card..
as the first boot require some time, wait 15 minutes or more..
Did you DOWNGRADE hboot??? and than intall stock hboot?? which hboot did you used? if the new ones from alpharev.nl you'd probably didn't read this "Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first." it's not too late for downgrade... just do it on fastboot
adamkx7xdesire said:
Did you DOWNGRADE hboot??? and than intall stock hboot?? which hboot did you used? if the new ones from alpharev.nl you'd probably didn't read this "Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first." it's not too late for downgrade... just do it on fastboot
Click to expand...
Click to collapse
I did S-Off using alpharev few months earlier but don't remember specifically running any downgrade. After installing the RUU, the Hboot got overwritten, so definitely I was not on the latest alpharev's HBoot's.
Now to downgrade or S-Off , the phone needs to be detected by the setup, which uses adb. But I can not access adb, can only access FastBoot.
i think you can try to flash stock hboot on fastboot by fastboot tool and than do the RUU again... you can... try...
adamkx7xdesire said:
i think you can try to flash stock hboot on fastboot by fastboot tool and than do the RUU again... you can... try...
Click to expand...
Click to collapse
I don't think that's doable, is it ? I don't think we can downgrade the Hboot just like that with S-On.
The risk is loosing the access to Hboot/fastboot itself.
I tried that and it doesn't work with S-ON. I can't access my phone outside fastboot and hboot and I can't even flash radio that way... So now I have an expensive mp3 player with (occasional) wifi access... Anyone have a solution?
Sent from my HTC Desire using XDA App
matus.karahuta said:
I tried that and it doesn't work with S-ON. I can't access my phone outside fastboot and hboot and I can't even flash radio that way... So now I have an expensive mp3 player with (occasional) wifi access... Anyone have a solution?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Just out of curiosity, how are you playing music in Hboot/fastboot
I think only way for us is to go to HTC now unless otherwise a senior member here sees this post and suggests something else.
ridhavm said:
Just out of curiosity, how are you playing music in Hboot/fastboot
I think only way for us is to go to HTC now unless otherwise a senior member here sees this post and suggests something else.
Click to expand...
Click to collapse
Sorry about that, I forgot to add "via USB" over there... I meant that my pc can recognize my phone only when in hboot or fastboot, when connected by USB cable
Sent from my HTC Desire using XDA App
matus.karahuta said:
Sorry about that, I forgot to add "via USB" over there... I meant that my pc can recognize my phone only when in hboot or fastboot, when connected by USB cable
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
that seems an usb brick..a user solved it easily flashing RMD Recovery (its in dev section) with fastboot, it has built in "USB Brick Fix"
andQlimax said:
that seems an usb brick..a user solved it easily flashing RMD Recovery (its in dev section) with fastboot, it has built in "USB Brick Fix"
Click to expand...
Click to collapse
Don't you have to be S-Off to flash recovery? I went through the post http://forum.xda-developers.com/showthread.php?t=1137763 and it seems I won't be able to flash it, since I'm still S-On
Yes, Seems that my device is bricked and only way out seems to be HTC now.
ridhavm,
Have you swapped hboots to Downgrade from alpharev's site?
If not, then you are still S-OFF.
Check your hboot if it's not old one.
If you are desperate, you can msg me on gTalk. I can have a look. I have saved many phones, so if it's not physical damage, we will work it out.
Thanks, Have added you on Gtalk
I had friends alpharev hboot RUU 1.8 r2 CM7 CM7 r2 installed the system has failed to establish when it comes hboot trying to open because of the HTC says the phone will not turn on the four corners bootloadder exclamation comes only allows you to install RUU ondada error occurs when installing the system please help
I'm not joking when I say I answer this question every day. It's not a dig at you in particular but why don't people get this?
The cm7 r2 partition is too small for a stock Rom. Also the hboot has write protection on it. You must flash the downgrade.img from the alpharev website in fastboot mode (from off, back+power) using fastboot commands THEN RUU
Sent from my HTC Desire using xda premium
So, if you have already made the mistake of running the RUU first and gotten the error 110, can you still just go flash the downgrade.img and then RUU again or do you have to take stronger messures in hand to fix your mistake?
Edit: my friend made the mistake, which means i dont have the device on hand so i can see if thats even possible..
Yes you can, due to the fact that you are still S-OFF because the r2 Hboots by alpharev have an overwrite protection against RUU or OTA.
Yes you can. The only thing is the fastboot screen looks like 4 !!!! instead of the text it usually has, but it still functions
Do not have an opportunity to show a way to fix you happy
How about CWM? Would you be able to access that or has it been replaced or broken in some way?
(you might be able to read between the lines, that I dont know much about this stuff)
No, everything has gone except hboot. Fastboot flash downgrade.img then RUU is the ONLY fix
Sent from my HTC Desire using xda premium
Thx m8's, really appreciate it, I've gone ahead and thumbed all your posts up
4 fastboot commands work well with an exclamation point on the screen is by HTC so I can do with downgrade.img and fastboot commands will open the RUU bootloader then yeah
So, my friend claims he got fastboot working and flashed the downgrader.img only to get a bootloader error 140 when running the RUU. Atm im trying to get him to use an RUU reported to work here: http://forum.xda-developers.com/showthread.php?t=857245&highlight=140. Plz let me know if this is not the right approach.
It just means the RUU he has has too old a hboot version. What RUU is it?
Sent from my HTC Desire using xda premium
RUU_Bravo_Vodafone_TR_1.30.184.3_Radio_32.41.00.32U_4.08.00.09_release_139001_signed.zıp
alpharev 1.8 cm7 r2 hboot
I have a RUU they remained so during the installation process has failed to help, please
I have tried all have the same error as well as more than one RUU
I'm sorry my English is not good as well as a recipe that you are the only charity isteyebildiğim This gives you a very happy people
ibrahimşahan said:
RUU_Bravo_Vodafone_TR_1.30.184.3_Radio_32.41.00.32U_4.08.00.09_release_139001_signed.zıp
Click to expand...
Click to collapse
I wouldn't use that. That 1 means its android 2.1 (Eclair). Very very old.
Unfortunately I cannot find any other .841. RUU's, only OTA's which you cannot use.
ibrahimşahan said:
alpharev 1.8 cm7 r2 hboot
Click to expand...
Click to collapse
Once you have the downgrade.img flast via fastboot, Maybe the htcdev.com android 2.3 RUU will work as it is unbranded. It works for most branded devices, but I dont know for sure if your Carrier in your location is covered.
The RUU is here:
http://www.htcdev.com/process/legal_download/152
Go there, tick the agree box and proceed. Try to flash that (ONLY after flashing downgrade.img) and see what happens.
okay thank you I can not do tomorrow to try and take my phone to technical service to the technical service they said I had 132 USD I can change the motherboard they will send you a message right away thanks in advance
What the? Changing the motherboard is nothing to do with it
Sent from my HTC Desire using xda premium
rootSU said:
What RUU is it?
Click to expand...
Click to collapse
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00. 32U_5.11.05.27_release_151783
rootSU said:
Maybe the htcdev.com android 2.3 RUU will work as it is unbranded.
Click to expand...
Click to collapse
I guess i could get my friend to try this one out aswell? As i believe this would have the newest HBOOT out there?
Edit: he got it working.. finally! thx again
remain in place for 4 bang HTC RUU does not install the phone icon so you need to change the motherboard said technical service
I don't understand your English very well. Did you do what I said? This should fix it. No money involved
Sent from my HTC Desire using xda premium
never heard of that before
Note: This works for some people, but I suggest you don't update, because majority of the people are having problems.
theq86 has reported his phone bricked.
Conclusions:
1- S-ON & Bootloader Locked
Your HBOOT will stay to the version 1.08.0000.
You will not be able to unlock the bootloader until HTCDev updates its RUU.
2- S-ON & Bootloader Unlocked (HBOOT 1.08.0009)
Your HBOOT will be downgraded to 1.08.0000 and your bootloader will be locked again. You will lose root and CWM.
You will not be able to unlock the bootloader until HTCDev updates its RUU.
3- S-OFF
Your HBOOT will stay (or be updated/downgraded) to 1.08.0000.
You don't have to worry about the bootloader cause it is unlocked forever.
For those who performed the update and are S-ON and want to unlock their bootloader, three solutions :
1- S-OFF your phone with an XTC-Clip
2- Wait for a software S-OFF (they are getting closer and closer)
3- Wait that HTCDev updates its RUU. We should write to them to be sure they are aware of this problem.
Want to get rid of the notifications telling you to update?
1. Download update (to the phone).
2. When the phone asks to install update, plug your phone to the computer in Disk Drive mode.
3. Run Winrar and browse to sdcard/download and enter OTA_Marvel_S_HTC_Europe_2.13.401.3-2.13.401.2_release_237041qqcw21hxt5vkhdz6.zip.
4. Inside you will find file firmware.zip. Unpack it anywhere.
5. Run Winrar and enter unpacked firmware.zip.
6. Click INFO button and go to SFX label.
7. Click "Remove the already existing module from the archive" and OK.
8. Delete all files except "android-info.txt". Save file (firmware.zip).
9. Replace firmware.zip in original OTA update.
10. Run update in your phone.
11. You will see yellow exclamation mark in triangle which means failure.
12. Remove the baterry for one second.
13. Turn on. Phone will show smtng like "update file is corrupt. download again?" - click NO. Turn off automatic check for updates in settings.
--------------------------------------------------------------------
Credits:
theq86 - Bricked his phone in the process! Click thanks for him!
popopo0 - Solution to get rid of the notification icon.
pihug12 - OP of the source post.
Source: [OTA Update] 2.13.401.2 => 2.13.401.3
Why is this update bad?
Why is this update bad? (background info)
HTC included it's newest radio and hboot with the update. Actually nothing to worry about, but there's a problem regarding software version numbers.
For example (HTC EU example):
My WFS shipped EU 2.3.3 (sw no. 1.33.401.2)
Then came the FOTA to EU 2.3.5 (sw no. 2.13.401.2)
And some days past a new FOTA (sw no. 2.13.401.3)
the software numbers are the problem here. HTCDEV provides the RUU updater for unlockable hboot only for 2.13.401.2.
As we know, HTC will not allow us to downgrade even a signed ruu. Thus, we will get a main version is older error.
This leads to the conclusions above.
------------------------------------
Will there be a way to re-unlock the phone?
HTC wrote:
Unfortunately once the device has updated to the most recent software it cannot be reverted to the previous update allowing the device to be unlocked. I can escalate this issue as a feature request to see if a further Hboot update can be released in the future for users who may have missed the opportunity to unlock their devices.
I hope that this information meets with your requirements. Should you have any further questions please do not hesitate to contact me again.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader until HTCDev updates its RUU.
Click to expand...
Click to collapse
1) downgrade 2.13.401.3 to 2.13.401.2
http://forum.xda-developers.com/showthread.php?t=1301388
http://www.filefactory.com/file/c0a...5.3035H_7.53.39.03M_release_225747_signed.exe
2) Only Step-0 (ruu-downloads - Install hboot 1.08.0099)
http://htcdev.com/bootloader
3) I rebooted to bootloader mode and my hboot is 1.08.0099 unlocked
Works fine for me ...
I've S-OFF'd my phone with xtc clip. Should I update my phone?
Also, my Hboot is 0.90.0000
What are the benefits of
Hboot 1.08.0009 as compared to 0.90.000?!
Thanks
Sent from my HTC Wildfire S A510e using xda premium
Royal King said:
I've S-OFF'd my phone with xtc clip. Should I update my phone?
Also, my Hboot is 0.90.0000
What are the benefits of
Hboot 1.08.0009 as compared to 0.90.000?!
Thanks
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I'm qurious about this as well. I'm S-OFF, but haven't installed any custom ROM yet, only Link2SD. So I should be able to install the update without problems, right?
Andreas75k said:
I'm qurious about this as well. I'm S-OFF, but haven't installed any custom ROM yet, only Link2SD. So I should be able to install the update without problems, right?
Click to expand...
Click to collapse
right, see conclusion 1 above.
After struggling to unlock BL my wfs s-on, I prefer not to update. I don't want to take risk.
theq86 said:
Why is this update bad? (background info)
HTC included it's newest radio and hboot with the update. Actually nothing to worry about, but there's a problem regarding software version numbers.
For example (HTC EU example):
My WFS shipped EU 2.3.3 (sw no. 1.33.401.2)
Then came the FOTA to EU 2.3.5 (sw no. 2.13.401.2)
And some days past a new FOTA (sw no. 2.13.401.3)
the software numbers are the problem here. HTCDEV provides the RUU updater for unlockable hboot only for 2.13.401.2.
As we know, HTC will not allow us to downgrade even a signed ruu. Thus, we will get a main version is older error.
This leads to the conclusions above.
------------------------------------
Will there be a way to re-unlock the phone?
I'm not promising anything. I told HTCDEV about the problems in general. Maybe I can get them to provide a RUU for 2.13.401.3 so that everyone who updated this can unlock again. I'm currently negotiating with HTC and waiting for an answer.
Click to expand...
Click to collapse
The easiest way is to edit the software number to a lower one. The How-To is in the forum here:
http://forum.xda-developers.com/showthread.php?t=1301388
Only do the steps before the ruu extract
ONeill123 said:
The easiest way is to edit the software number to a lower one. The How-To is in the forum here:
http://forum.xda-developers.com/showthread.php?t=1301388
Only do the steps before the ruu extract
Click to expand...
Click to collapse
Pitty it is not useful for me. can not even boot into android or access adb
--------------------------------------
UPDATED POST #2 IMPORTANT
Hi there!
I need a little help.. My problem is that I can't remove CWM 5.0.2.8 from my Marvel.
It is S-OFF with XTC Clip.
USB Debugging is ON.
Fast Boot is ON.
I have stock ROM 2.3.5
I chose Charge Only.
I use Marvel Auto-Installers. It detect my Marvel.. I press uninstall recovery (HTC original). Then my phone restarts. After booting I shut down and restart with vlume down pressed to check what recovery I have and... surprise: still CWM 5.0.2.8!
Any little help will be appreciated.
Then please download the auto-installers new.
Go to the folder installed the auto-installers and you will find a orig.img and a fastboot.exe
Restart your phone into the fastboot mode and open terminal. Navigate to the fastboot.exe and execute this command:
fastboot flash recovery orig.img
Thanks a lot!
sending 'recovery' <3100KB>... OKAY
writing 'recovery' ... FAILED (remote: not allowed)
Any ideas?
helbet said:
Thanks a lot!
sending 'recovery' <3100KB>... OKAY
writing 'recovery' ... FAILED (remote: not allowed)
Any ideas?
Click to expand...
Click to collapse
strange behavior for an s-off device ...
theq86 said:
strange behavior for an s-off device ...
Click to expand...
Click to collapse
Anyway .. thanks a lot! I give up with this update..
No, this command must work for unlocked bootloader too.
Have you relocked bootloader? Or check if u really unlocked!!!
I don't know how my bootloader is.. My phone is S-Off by XTC Clip and I have a stock ROM 2.3.5 installed in CWM Recovery from a zip file..
Ähm, i think the StockHBOOT does not support the flash recovery command, if i'm right
Or what HBOOTversion you have?
ONeill123 said:
Ähm, i think the StockHBOOT does not support the flash recovery command, if i'm right
Or what HBOOTversion you have?
Click to expand...
Click to collapse
of course it does support. as you see in helbets post. just fastboot rejects flashing. which should not happen if he is s-off
Can anyone confirm whether this updated ROM can be rooted using the usual methods (GingerBreak/ZergRush) ?
Thanks.
Sent from my Desire Z running CM7.
I can confirm , done it. Head to http://forum.xda-developers.com/showthread.php?t=1445867 there is solution.
Want to re-lock your bootloader for some reason?
Want to get back to the state it were before unlocking?
Want to get rid of RELOCKED and instead have LOCKED (OOW) (1.08.0099) or LOCKED (1.09.0099) again for Downgrading and get warranty back?
Want to unlock bootloader again without data wipe?
Want to downgrade to an earlier RUU?
Control your bootloader now as you wish!
* Easily switch between LOCKED (OOW), RELOCKED or UNLOCKED without losing data.
* Set Superversion
What is Superversion:
All RUUs have main software number versions. You can not downgrade to lower versions. In the forums there is a fix where you have to edit and reflash your misc partition.(http://forum.xda-developers.com/showthread.php?t=1445867)
Now you need no hex editor anymore. Just chose Superversion option and the update.zip will do anything for you.
UPDATE:
* Added option for Superversion
http://www.mediafire.com/file/a7m70dmrd0gdvav/bltool-signed.zip
Is this universal or gsm? I can see this being very helpful
Nice, can't wait to try it.
simonsimons34 said:
Is this universal or gsm? I can see this being very helpful
Click to expand...
Click to collapse
Well for I never had a non GSM-phone I don't know. But there should be no great difference
this looks amazing!
thanks
i don't see why it wouldn't work with cdma. It pulls your misc partition img. Its not like it has a misc.img included and flashing that. So, I think it would work on CDMA just fine. For that matter, any device really.
jmztaylor said:
i don't see why it wouldn't work with cdma. It pulls your misc partition img. Its not like it has a misc.img included and flashing that. So, I think it would work on CDMA just fine. For that matter, any device really.
Click to expand...
Click to collapse
Right. It dumps the misc partition to a file. the "bltool" looks at specific offsets and only changes what it has to change. the rest is kept as is and the partition is dumped back.
unless CDMA phones use the different offsets in the misc.img (which is highly improbable) it works with cdma, too.
I'll post this for kalaker
kalaker said:
Hello,
I would just like to inform you that your WFS bootloader unlock/relock tool does work on CDMA (Marvelc) phones.
I would make a contribution in the thread, however, I have not yet reached 10 posts.
Thank you for such a wonderful script.
kalaker
Click to expand...
Click to collapse
Can it bypass the HTCDev procedure to unlock the bootloader the first time (with HBOOT 1.09.0099) or not yet ?
pihug12 said:
Can it bypass the HTCDev procedure to unlock the bootloader the first time (with HBOOT 1.09.0099) or not yet ?
Click to expand...
Click to collapse
you need CWM recovery to use this tool, and you cant install CWM to an unlocked phone
Can this be done with a HTC Wildfire Buzz ?
Edit: It works on the Buzz but it doesn't get S-On back
hacktrix2006 said:
Can this be done with a HTC Wildfire Buzz ?
Edit: It works on the Buzz but it doesn't get S-On back
Click to expand...
Click to collapse
It's not intended to.
Well i used it and it works well under the HTC Wildfire (Buzz) Although the superversion still just shows unlocked. I have tried it myself and no harm came to the Hboot at all.
With S-On though i have managed with a little bit of adb shell magic by typing this into adb shell as root i.e #
echo -e '[email protected]=7,1\r' > /dev/smd0
and then rebooting the phone.
This tool will just change the misc partition. It sets the bootloader lock state.
the superversion option changes the main version to 0.0.0.0 so that any ruu can be installed.
Thanks for info at least you know it will work on the Wildfire (buzz) the little brother to Wildfire S (marvel)
Can somebody please tell me how to update it...
I'm stuck on fastboot and I cannot use adb, so is there any way I can update this with fastboot on Wildfire S (marvel) S-ON????
can this tools works for HTC One V?
i need to get the **LOCKED** status back for warranty purpose
spiderio said:
can this tools works for HTC One V?
i need to get the **LOCKED** status back for warranty purpose
Click to expand...
Click to collapse
I'm interested in whether it works for the One S, also. Don't need to get back for warranty, but this tool is invaluable.
Locked (oow = out of warranty) just in case anyone is relocking for warranty purposes only.
Sent using tapatalk 2 via an Android telephonic device.
Please do not try it on HTC One Devices or any other eMMC based devices (ALL highend devices)
It won't work because MTD drivers are not able to access eMMC
Hi all,
First of all, I can imagine that this problem has already been encountered a million times, but I tried searching the forum and didn't see the exact same problem as mine with the same setup. I'm happy to read more if someone points me to another thread with the solution.
Long story short, I tried flashing JellyTime_42 on this phone and even though everything seemed to work well, it's not booting and I'm stuck with the HTC logo.
unlocked the bootloader with HTC dev
flashed CWM recovery 5.8.1.5-ace
uploaded cm-JellyTime_42 and gapps.
wiped data, cache and dalvik cache using CWM
installed JellyTime
rebooted... and that's where I am now.
Some info about the phone itself. It's an Desire HD on ATT. cid: CWS__001
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0030
MICROP-0438
RADIO-26.17.14.11_M
eMMC-boot
As I said, I can fastboot, and although I'm not sure how to push other stuff to the phone, that part seems functional.
Thanks a lot for your help!!
Nick
You need to fastboot flash the boot.img from the ROM zip.
bananagranola said:
You need to fastboot flash the boot.img from the ROM zip.
Click to expand...
Click to collapse
Thanks so much bananagranola, that worked and I can now boot and use the phone!
(for some reason I never saw that step mentioned in any tutorial)
Thanks again
Most tutorials are for S-Off.
Yes, the preferred unlock method for the DHD/I4G is to get S-OFF using the Advanced Ace Hack Kit (AAHK). You can still do that, you just need to relock your bootloader and run the AAHK. The command to relock was given in the last step of HTCdev unlock.
You better do that soon though, if you want. - http://forum.xda-developers.com/showthread.php?p=38157931
There are 2-3 tutorials in the Ace Think Tank thread for both the AAHK and HTCdev methods of unlock. I've made one for flashing a ROM after HTCdev unlock too. You'll find all the information you'll need about this phone in the Ace Think Tank thread. Look through it.
Also, I suggest you use either 4ext or TWRP recovery rather than CWM. CWM is very dated and causes problems while installing some ROMs (like the recent ViperDHD updates).
For 4ext - Download and install 4ext Recovery Updater from www.4ext.net and flash the latest touch recovery.
For TWRP - Install Goo Manager from Play Store->Menu->Install OpenRecoveryScript
Sent from my Desire HD using xda premium
Hi sashank,
Thanks for your input.
Why is AAHK the preferred method? It seems way complicated compared to what I've done, but probably I'm missing something. That said, the phone works like a charm now after flashing boot.img.
Because if you have S-OFF, you won't need to flash boot.img every time you flash a ROM/kernel/ROM update. You don't need to have a PC with you just to flash a ROM. Also, you can directly restore a backup with no hassle. With HTCdev unlock, you need to flash the boot.img in the backup folder separately to complete the process. I do this for my friend's One X because it doesn't have an S-OFF method unfortunately, and it's quite a hassle. If you're okay with flashing boot.img every time, then stick with HTCdev unlock, no problem.
AAHK is actually quite simple to use. It does everything for you. You just need to follow the instructions to the letter, select a few options correctly and it does the rest. Don't be intimidated by it.
Sent from my Desire HD using xda premium
Nico7578 said:
Hi sashank,
Thanks for your input.
Why is AAHK the preferred method? It seems way complicated compared to what I've done, but probably I'm missing something. That said, the phone works like a charm now after flashing boot.img.
Click to expand...
Click to collapse
Nico, HTCDEV just allows you to have a limited control over your device. You will still be linked to your carrier or sales code (CID) and will not be able to flash RUU from other carriers/geographical areas. That might sound useless now, but belive me that when you get stuck and can not find a RUU for your device you will remember it!
Besides, HTCDEV will not allow you to flash radios and some other stuff. Not to metion that your bootloader says *UNLOCKED* in a beautiful pink color at the top...LOL
S-OFF disables all kinda of security in the phone (nand security off) and that allows you to flash anything at all. From RUU's to radios without facing issues. Besides, that is completely reversible and will leave no traces of being S-OFF if you need to get to a service centre.
Nico7578 said:
Hi sashank,
Thanks for your input.
Why is AAHK the preferred method? It seems way complicated compared to what I've done, but probably I'm missing something.
Click to expand...
Click to collapse
Because AAHK gives you full control on your device. It basically gives you permanent root privileges, S-OFFs your phone and with SuperCID (if needed) you actually unbrand your phone...that is that you can install every ROM you want on it.
It's not so difficult, to be honest, you just need to carefully read the guide and you'll soon unleash the real power of your device
NeoLocutus said:
Because AAHK gives you full control on your device. It basically gives you permanent root privileges, S-OFFs your phone and with SuperCID (if needed) you actually unbrand your phone...that is that you can install every ROM you want on it.
It's not so difficult, to be honest, you just need to carefully read the guide and you'll soon unleash the real power of your device
Click to expand...
Click to collapse
I think that something is wrong there. The root access is only to rom level. If you flash a RUU you will lose root privileges until SU is flashed again. What the Hack Kit gives you is S-OFF permanently, which is reversible anyway.
Please Help
Hello
I need help. Please
I recently brought a friend's phone (Desire HD) to flash custom ROM on. I flashed boot.img via fastboot but when I select recovery, A white screen with HTC shows and after a few seconds, black screen occurs. I know screen is on however. I dont know what to do. The bootloader says unlocked but it says
S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
The steps that I did was.
1. I unlocked the bootloader via HTCDev. It gave me error so I updated via RUU manually through fastboot.
2. After that, I was able to unlock the bootloader via HTCDev.
3. I followed this (http://www.teamandroid.com/2013/04/...android-422-jellytime-jelly-bean-rom-guide/2/) to flash method to Jelly-time on DHD. But when I flashed boot.img via fastboot cmd, it does not go to Recovery, it only shows phone with exclamation mark. If I reboot the phone, it shows white HTC screen and then black black screen. Please help me what to do. After unlocking via HTCDev, I didn't intall CWM, I though flashing boot.img is actually installing CWN :'|
Thanks a LOT in advance
I worked it successfully. I fastboot flashed CWM and it worked. Case closed