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
Related
The Wildfire S is now supported on HTC-Dev for bootloader unlocking. They seem to've recently added a bunch of devices "launched prior to September 2011" to the list of supported devices, which includes the Wildfire S. There's now a drop-down box instead of just a list of supported devices.
You have to apply an RUU if you're not running a certain software version to use this tool because it requires a specific HBOOT. Remember to backup your info/etc.
I'm hoping they add the Chacha to the list of supported devices soon, as we're still in the Legacy & Low Activity section
Is it true? Because another thread discust about HTC didn unlocked it
I will give it a Try. Btw I'm new here. I will edit this post as far it's done.
//Edit: It's done. Looked in Hboot and it say above all "***LOCKED (oow) ***"
just tested.
not only is is still s-on after this, but there is a big pink ote at the top of the bootscreen that says "*** LOCKED (OOW) ***"
no idea what this means :s
Woah, what?
Could you take a picture of it?
I'm curious how it looks.
did you updated rom before s-off?
Cold Ice said:
I will give it a Try. Btw I'm new here. I will edit this post as far it's done.
//Edit: It's done. Looked in Hboot and it say above all "***LOCKED (oow) ***"
Click to expand...
Click to collapse
Gloris said:
just tested.
not only is is still s-on after this, but there is a big pink ote at the top of the bootscreen that says "*** LOCKED (OOW) ***"
no idea what this means :s
Click to expand...
Click to collapse
Did you two go through with the whole procedure, or just applied the RUU?
EDIT: From what I've read, after you've gone through with the full procedure, that pink text should say UNLOCKED. You will still be S-ON, however the boot (kernel), recovery and system partitions will no longer be protected.
Gloris said:
just tested.
not only is is still s-on after this, but there is a big pink ote at the top of the bootscreen that says "*** LOCKED (OOW) ***"
no idea what this means :s
Click to expand...
Click to collapse
I'm wondering if this also patches the XTC-Clip exploit.
Anyone tried the clip on a post sept phone?
Wondering if they've patched the exploit for all HTC phones.
I forgot to do the whole procedure, i will give it a new try. I will come back and say if it works.
What is the actual difference among S-OFF and unlocked bootloader ?
Going to try this later lol
Sent from my HTC Wildfire S using xda premium
Nightshadow931 said:
What is the actual difference among S-OFF and unlocked bootloader ?
Click to expand...
Click to collapse
S-OFF means that there are zero restrictions on what you can modify/flash - ie. you can flash radios and bootloaders.
HTC's method of unlocking only allows you to flash kernels (/boot), recoveries (/recovery) and ROMs (/system)
d33ps1x said:
I'm wondering if this also patches the XTC-Clip exploit.
Anyone tried the clip on a post sept phone?
Wondering if they've patched the exploit for all HTC phones.
Click to expand...
Click to collapse
I don't think they can patch a hardware exploit without redesigning the hardware.
Edit: what we should try now is 'htc-unlock' a phone, then try to xtc-clip it to see if it still possible. But I still don't think they can patch out the clip.
Desire-Oxygen2.3.2 | WFS-stock
So, it's done and it's Unlocked!
Wow wow, Cold Ice! Can you guide how to do it? step by step? please! Or give some screen shoots
yups, i didn't realise there was more to the process than updating the ruu....just completed the process, and now it says unlocked, but it's still s-ON?
so what now? can i now put custom roms on to make the most of the limited memory, or do i need to s-off still first?
confused.com
Gloris said:
yups, i didn't realise there was more to the process than updating the ruu....just completed the process, and now it says unlocked, but it's still s-ON?
so what now? can i now put custom roms on to make the most of the limited memory, or do i need to s-off still first?
confused.com
Click to expand...
Click to collapse
You can still flash ROMs, you just can't flash radios and bootloaders
eoghan2t7 said:
Going to try this later lol
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
I'm not! LOL
Either way this is a great step forward for our little phone that could. Someone break out the sparkling wine. Save the champagne for S-OFF though.
Will this allow users to run CWM scripts to resize partitions or would that be locked down still?
Hi to all!
Few days ago, HTC released the unlock bootloader tool for HTC Desire also (and for other smartphone) HTCdev - Unlock Bootloader. So I tryed to follow the guide. The first step is intended to upgrade the HBOOT, so I have to connect the device to the computer, to download a RUU from a list on my computer and to execute it. But when my device automatically reboot (this is the procedure) I get and error that says "model id error"! (I have a MIUI Rom)
I write from Italy so I downloaded HTC Europe RUU (my device is not branded). Which one I have to try?
Is there anyone that tryed this procedure? Anyone can help me?
Thanks in advance.
Francesco.
P.S.: my device hboot detail
Bravo PVT1 ship s-on
HBoot-0.93.0001
Microp-031d
Touch Panel-synt0101
Radio 5.09.05.30-2
Same here http://forum.xda-developers.com/showthread.php?t=1431726
Did you run APTG or CT?
Both, but without success
same here, spent a few hours with no joy
Just use revolutionary.io
With revolutionary you don't loose warranty and have full bootloader unlocked.
Sent from my HTC Desire
Please use the Q&A Forum for questions Thanks
Moving to Q&A
andQlimax said:
Just use revolutionary.io
With revolutionary you don't loose warranty and have full bootloader unlocked.
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for the suggestion but I don't want just to unlock the bootloader but unlock the bootloader with HTC rules and tools.
Thanks.
http://forum.xda-developers.com/showpost.php?p=21119888&postcount=5
There is no point in unlocking bootloader with HTC's tools, unless you wish to use Htc's own crappy recovery to flash a custom rom..
Droidzone said:
Excellent...what we have here are some nice fat guinea pigs!
Click to expand...
Click to collapse
fat guinea pigs??? Excellent... we have an idiot! (also I add a "wink" so we are all happy, ok?).
Droidzone said:
There is no point in unlocking bootloader with HTC's tools, unless you wish to use Htc's own crappy recovery to flash a custom rom..
Click to expand...
Click to collapse
The point is that I want to try, to test, I'm curious to unlock my bootloader with HTC tools! And not simply unlock the bootloader! So, now, I have a problem. Can you help me? No? So, do not offend and make your businness!
Thanks.
Guineapig was a figure of speech, no offense meant. A guineapig is the commonest lab animal subjected to scientific experiments. If you feel that was offensive, I do apologize profusely.
Droidzone said:
Guineapig was a figure of speech, no offense meant. A guineapig is the commonest lab animal subjected to scientific experiments. If you feel that was offensive, I do apologize profusely.
Click to expand...
Click to collapse
Ok, apologize me too... it's difficult to understand a "figure of speech"...
So, I just tryed a new RUU from htcdev. They have upgraded the HTC EU one, but I get an error that says that I need to upgrade the ROM to 2.29.405.14.
I think that it's impossibile for me because I have a MIUI ROM, right?
Anyone tested it?
If you're bent on trying the unlocker, the first thing to do is unroot. Keep your goldcard ready, and run the RUU. After unrooting with whatever RUU you chose, select the same RUU from their choice (this is a tentative advice).
Word of caution: They're saying Hboot upgrade required. If that's true, be warned that you will never be able to run an Alpharev/Revolutionary S-off until they update their method to include this.
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.
Hello All..
I was an apple fan since 2007 The iOS, i wasnt really convinced with android till the day of release of HTC ONE X , This Phone Really Changes my mind with it Incredible Features and the quality of the device.
I,m new to android , i,ve learned how to unlock the bootlader , do the root and recovery , also installing a custom rooms and some MODs on it .
I need some information about:-
1- What does kernel and boot.img do?
2- What is the S-On and S-Off means ?
3- Is it possible to return my device as it is in the first original rom [bootloader locked, No root] as a new device? and HOW ?
4-Does MODs works on any room or for specific ones ?
5- What is H-boot ?
Any one use any instant messaging app like whatsapp Etc.. to contact him directly ? fast and easier
thank you in advance
1- What does kernel and boot.img do?
GOOGLE SOLVES EVERYTHING.
2- What is the S-On and S-Off means ?
HTC SENSE ON or HTC SENSE ON.
It enables or disables the htc sense interface.
3- Is it possible to return my device as it is in the first original rom [bootloader locked, No root] as a new device? and HOW ?
You can RELOCK your bootloader.... but anyways you lost your warranty (IF YOU UNLOCK YOUR BOOTLOADER).
ANd you can return to the original rom and config with this thread
4-Does MODs works on any room or for specific ones ?
See specifications about it.
5- What is H-boot ?
i DONT KNOW CLEARLY, BUT GOOGLE KNOWS TOO MUCH.
Well I can answer some of the questions:
1. boot.img contains the kernel inside (not sure what else)
2. S-ON or S-OFF I think means security-on/off
3 it is possible as long as the bootloader is locked/re-locked. You have to flash the RUU of your region/country where the phone came from. Without S-OFF we can't get super CID
I don't get your 4th question
5. HBOOT is loaded immediately when your phone is switched on, and it’s mainly responsible for checking and initializing the hardware and starting the phone’s software. It can also be used for flashing official software releases, as well as a few other things. HBoot can be compared to the BIOS on a computer.
1- What does kernel and boot.img do?
The kernel is like the middle-man between the hardware and the OS. it holds drivers for the hardware and tells the OS how to interact with the hardware.
2- What is the S-On and S-Off means ?
Security on/ Security off. It is another way to enable the phone to flash different Roms, The only way to flash roms at the moment is to unlock the bootloader but then HTC has a record of all unlocked phones.
3- Is it possible to return my device as it is in the first original rom [bootloader locked, No root] as a new device? and HOW ?
Yes it is, there are tutorials in this section on how to do this.
4-Does MODs works on any room or for specific ones ?
It depends what the mods are and how they are implemented, again it's best to read the threads on the specific mods.
5- What is H-boot ?
H-boot sort of holds the partition layout for the rom, from my experience with my desire different roms fitted different H-boot's. Not sure about anything else.
Added To my knowledge
Thanks All , i appreciate your fast responses
S-ON Locked = Security on + Bootloader locked = This is what your phone is out of the box.
S-ON Unlocked = Security on + Bootloader unlocked via htcdev = You can write new system and recovery images e.g. custom firmware. You can't alter the baseband or CID however. HTC run htcdev and know you unlocked it which will affect your warranty.
S-ON Relocked = Security on + Bootloader locked = You unlocked via htcdev and then relocked it. You can't go back to S-ON Locked normally. HTC know that you previously unlocked it.
S-OFF = Security off - You can alter anything you want in the phone including the baseband and CID value which determines what branding you get. You need a third party exploit to get S-OFF as HTC won't let you do it on retail handsets.
HBOOT is the bootloader. If you're concerned about getting S-OFF then you shouldn't update this at all since it may fix a vulnerability that is required later on for S-OFF.
Just for info:
Unlocking your bootloader does NOT void your warranty, your warranty is still valid for hardware issues but not software unless you have a branded phone, and if the software change made by you has affected the hardware somehow maybe by overclocking the CPU and frying it then the warranty will not cover it.
It should be noted that S-OFF DOES void all warranty.
wolfraim said:
2- What is the S-On and S-Off means ?
HTC SENSE ON or HTC SENSE ON.
It enables or disables the htc sense interface.
Click to expand...
Click to collapse
No, it definitely does not mean that.
Sent from my GT-I9100 using xda premium
joshnichols189 said:
No, it definitely does not mean that.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
so.... any explanation? xD
wolfraim said:
so.... any explanation? xD
Click to expand...
Click to collapse
S-ON = Security ON
S-OFF = Security OFF
Boot.img
Thanks all again..
other question :
[You NEED to flash boot.img via fastboot] HOW To i Do that? [Exact steps please]
DawoodWN said:
Thanks all again..
other question :
[You NEED to flash boot.img via fastboot] HOW To i Do that? [Exact steps please]
Click to expand...
Click to collapse
fastboot flash boot boot.img
Click to expand...
Click to collapse
is the command you type
Assuming you have the fastboot files in your PC and have the "boot.img" file together in the fastboot files.
1. Power Phone Off by Holding power button for 10 secs
2. select Fastboot with volume + or - then press power
3. plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
4. cd to your fastboot files folder cd c:\fastboot
5. type in your command prompt "fastboot flash boot boot.img"
I got some of the tut from bagofcrap24
I was trying to root my WFS (S-On method with HTC unlocked bootloader) except I keep getting an error '130 Model ID' when running the correct RUU for my phone and can't figure out why.
HTC-A510a (Marvel)
S-On
Virgin Mobile (Canada)
2.3.3 (Andriod)
2.1 HTC Sense
Software Number: 1.36.666.5
- Yes, I have downloaded it multiple times to check if the file was corrupt
- Yes, all the pre-requisites are installed (JDK, Andriod SDK, HTC drivers etc)
- Yes, USB debugging is on
- No, there isn't a WWE RUU for Virgin Mobile that I can see
I would prefer to keep s-on if possible because (theoretically less to go wrong) although I am not a complete noob, I am close to it and this is my only phone.
Do I have to go back to the (old?) gold-card method, is there another way, or am I just missing something?
Thanks in advance.
Asmodean1209 said:
I was trying to root my WFS (S-On method with HTC unlocked bootloader) except I keep getting an error '130 Model ID' when running the correct RUU for my phone and can't figure out why.
HTC-A510a (Marvel)
S-On
Virgin Mobile (Canada)
2.3.3 (Andriod)
2.1 HTC Sense
Software Number: 1.36.666.5
- Yes, I have downloaded it multiple times to check if the file was corrupt
- Yes, all the pre-requisites are installed (JDK, Andriod SDK, HTC drivers etc)
- Yes, USB debugging is on
- No, there isn't a WWE RUU for Virgin Mobile that I can see
I would prefer to keep s-on if possible because (theoretically less to go wrong) although I am not a complete noob, I am close to it and this is my only phone.
Do I have to go back to the (old?) gold-card method, is there another way, or am I just missing something?
Thanks in advance.
Click to expand...
Click to collapse
Have you unlocked your bootloader?
Sent from my HTC Wildfire S A510e using xda premium
vedang81 said:
Have you unlocked your bootloader?
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Sorry if if I wasnt clear. No, my bootloader is not unlocked - that is what I am in the process of doing. When I follow the instructions for that provided by HTC/S-On Unlock Tutorial, the RUU that they provide will not unlock my bootloader and produces the error '130 Model ID Error' and then restarts my phone. The problem is that is the correct RUU doesnt work and as far as I can tell, it is the only one provided by HTC that works for a WFS and Virgin Mobile (Canada).
I understand that you can use other RUU's (sometimes) to unlock your bootloader, but that could cause some issues with my radio, yes? As I said before, it is my only phone and unlike ROMS if I messed something up with a radio, I wouldn't know where to start troubleshooting.
Asmodean1209 said:
Sorry if if I wasnt clear. No, my bootloader is not unlocked - that is what I am in the process of doing. When I follow the instructions for that provided by HTC/S-On Unlock Tutorial, the RUU that they provide will not unlock my bootloader and produces the error '130 Model ID Error' and then restarts my phone. The problem is that is the correct RUU doesnt work and as far as I can tell, it is the only one provided by HTC that works for a WFS and Virgin Mobile (Canada).
I understand that you can use other RUU's (sometimes) to unlock your bootloader, but that could cause some issues with my radio, yes? As I said before, it is my only phone and unlike ROMS if I messed something up with a radio, I wouldn't know where to start troubleshooting.
Click to expand...
Click to collapse
Skip that RUU section.
Better u send me a pm i vl guide u there.
Sent from my Android lappy
vedang81 said:
Skip that RUU section.
Better u send me a pm i vl guide u there.
Click to expand...
Click to collapse
I guess vedang81 is taking a break or something. Either way what he suggested (skipping flashing the RUU) didn't work. When I entered the cmd commands it gave me "[ERR]Command error!!!". Vedang81 thought that this meant I didn't have the files or they weren't in the right place, however I double checked everything (all files were downloaded from HTC Dev links and were in the correct folders). Several other threads (on other devices) seemed to indicate that that error was what happened when you didn't flash the RUU and therefore didn't have the updated hboot. I also looked at simonsimon34's HTC Wildfire SUtility but that says it requires your bootloader to say **locked** to begin with and mine doesn't.
Not sure where to go from here...
Bump...
Asmodean1209 said:
I guess vedang81 is taking a break or something. Either way what he suggested (skipping flashing the RUU) didn't work. When I entered the cmd commands it gave me "[ERR]Command error!!!". Vedang81 thought that this meant I didn't have the files or they weren't in the right place, however I double checked everything (all files were downloaded from HTC Dev links and were in the correct folders). Several other threads (on other devices) seemed to indicate that that error was what happened when you didn't flash the RUU and therefore didn't have the updated hboot. I also looked at simonsimon34's HTC Wildfire SUtility but that says it requires your bootloader to say **locked** to begin with and mine doesn't.
Not sure where to go from here...
Click to expand...
Click to collapse
If your bootloader doesn't say **locked**, then it's already unlocked.