Hello fellow Wildfire owners ,
HTC have released their official bootloader unlocking tool for some more HTC devices, and among them is the Wildfire. I'm not 100% sure what the advantages or disadvantages are to using a tool like Revolutionary, but it is worth a look. To use it you will need a HTC dev account.
Check it out here.
I've been wondering about this tool after reading the HTC dev site warning about warranties being void and not being able to go back after using the unlock tool. As it stands atm I can just flash hboot to go back to s-on and stock whenever I like but does anyone know if this is the case with the tool and bootloader update HTC supplies?
Or am I just being paranoid? It doesn't affect me as I'm already unlocked but I'd hate to see people get screwed over and find out they've locked something else which means you can't downgrade and s-on again, kinda like with the froyo update.
Sent from my HTC Wildfire using xda premium
Gonna check it out.
Because I already used AlphaRevX, I'll check it up to the actual unlocking part.
---------- Post added at 10:39 PM ---------- Previous post was at 10:13 PM ----------
Here we go, some screen shots
First I get to know that this voids my warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then they tell you that you need to flash a RUU. (If they're stock, good for getting the right ruu for un-rooting! They're probably country specific, since you need to specify your country when registering.)
Step 1-4: USB Fastboot
Step 5-7 Getting ADB and Fastboot then navigating there with cd (skipped that part, because most of us knows how to start up cmd and use the cd command )
Step 8-10: Getting a unique ID token.
After this you should get the tool via e-mail.
Hello, I have HBoot-0-80-007 and my wildfire rooted with the unrevocked method, using this bootloader unlock will I be able to S-Off my terminal or I wiould need to change the H-Boot anyway?
Is there any manual to get S-Off on a Wildfire with HBoot 0.8?
Thank you.
shakeador said:
Hello, I have HBoot-0-80-007 and my wildfire rooted with the unrevocked method, using this bootloader unlock will I be able to S-Off my terminal or I wiould need to change the H-Boot anyway?
Is there any manual to get S-Off on a Wildfire with HBoot 0.8?
Thank you.
Click to expand...
Click to collapse
to use alpharev you must have hboot 1.001. so you must update hboot attention you mustn't update to hboot 1.002
Whichever way you choose to unlock you'll need to upgrade hboot. See here point 5 I think.
http://forum.xda-developers.com/showthread.php?t=1029318
This should get you ready to use revolutionary to unlock, if however you choose the HTC tool I presume it will unlock the phone so you can flash a new Rom but the radio and sim lock will still be locked.
From the looks of it so far I would go with revolutionary for now as that is tried and tested but the HTC tool is still new and I don't think anyone has posted of a successful unlock with it yet.
Edit: as the ninja said don't update to the latest hboot or else you'll need to downgrade again.
Sent from my HTC Wildfire using xda premium
shakeador said:
Hello, I have HBoot-0-80-007 and my wildfire rooted with the unrevocked method, using this bootloader unlock will I be able to S-Off my terminal or I wiould need to change the H-Boot anyway?
Is there any manual to get S-Off on a Wildfire with HBoot 0.8?
Thank you.
Click to expand...
Click to collapse
In my opinion, if you want S-OFF, do it with revolutionary as HTCDev doesn't unlock the radio.
To do this you will need to first flash this RUU: here. Then run Revolutionary
Scratch0805 said:
Edit: as the ninja said don't update to the latest hboot or else you'll need to downgrade again.
Click to expand...
Click to collapse
Ninja? I'm a ninja?
lol....because you beat me to answering the question.
Sent from my HTC Wildfire using xda premium
scratch0805 said:
lol....because you beat me to answering the question.
sent from my htc wildfire using xda premium
Click to expand...
Click to collapse
mega looool
Thank you al!!!!
Definitely not an offer to unlock bootloadera the official way that will offer from HTC. The main reason for this is that each authorized service account has specialized in information system of the HTC. If you send information to the identification code of smarttfona until HTC, which is obviously necessary to get the code to unlock the bootloader-a, then this information will have access and any authorized service. So easy, can be determined whether the service was unlocked smartphone, and according to the above quotation is accordingly limited or void warranty!
Unlocking procedure, which resembles that offered by AlphaRev a Revolutionary.
If informal way also allows you to unlock (although theoretically still would void the warranty), at least not openly declare it to HTC. And you can return the state of his phone to factory state!
jacktyler1807 said:
In my opinion, if you want S-OFF, do it with revolutionary as HTCDev doesn't unlock the radio.
Click to expand...
Click to collapse
Right, give one reason why the htc unlocking tool should be used?
Quotes from HTCdev:
Security is left on to protect things like the radio, and SIM lock.
HTC eagerly anticipates your innovations.
Click to expand...
Click to collapse
Bit late isn't it?
I successfully unlocked my bootloader with the HTCDev Tool (after getting S-ON again, of course) and so far, so good. Though I have no root on the stock ROM, even with Superuser. Maybe I'll have to flash a custom ROM, but has anybody got an idea on how to get SU on the stock ROM?
Sent from my HTC Wildfire using XDA App
Is it like AlphaRevX/rEVOlutionary?
As for SU on stock, try flashing a su package in a recovery.
http://androidsu.com/superuser/
Bootloader says UNLOCKED, but still S-ON. Weird.
Will try flashing CWM later.
Sent from my HTC Wildfire using XDA App
I really don't know why you bother with official unlock when revolutionary works just fine...
cheers
pl0ppy said:
Bootloader says UNLOCKED, but still S-ON. Weird.
Will try flashing CWM later.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Is the hboot version number any different, I presume you can use fastboot to flash cwm or PC49IMG maybe.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Is the hboot version number any different, I presume you can use fastboot to flash cwm or PC49IMG maybe.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Yep, new HBOOT! I had 1.01.1001 before, now I have 1.02.0000. If flashing a recovery from fastboot doesn't work, then I am screwed, right?
pl0ppy said:
Yep, new HBOOT! I had 1.01.1001 before, now I have 1.02.0000. If flashing a recovery from fastboot doesn't work, then I am screwed, right?
Click to expand...
Click to collapse
You should be able to root with Gingerbreak as the Security is off. Once you've done that, you should be able to use ROM Manager/ Root Toolbox to flash a recovery
Related
Brought to you by touchpro247 and I. (touchpro247 put his phone on the line testing this)
First off, I take no blame for anything that happens due to this. This can potentially brick your phone. If this bricks your phone, makes it unstable, kills your cat.. YOUR FAULT not mine.
Please, don't make typos in the commands.
Eng Hboots allow you to flash unsigned images, and opens up more fastboot commands. Most people do not need this. This will not [provide perm root, or un-writeprotecte the emmc chip. In fact, if you don't have s-off it won't work for you.
Requirements:
Root
radio (ship) s-off
Busybox properly installed
adb working
If you do not have busybox, you can use this app to install it https://market.android.com/details?id=stericson.busybox
Download the ENGHboot for Vivo here:
http://cunninglogic.com/android/vivo/vivo_enghboot.img
put the file on your sdcard
Follow these commands
Code:
adb shell
If you have havea $ prompt and not a # prompt, run su
Code:
su
You should now have a # prompt and can continue
Code:
busybox md5sum /sdcard/vivo_enghboot.img
If the output is NOT b1829cfb7cf5d462660a58aa5449d27c , STOP redownload the file and try again. Anything else could cause a brick. If it matches, continue.
Code:
dd if=/sdcard/vivo_enghboot.img of=/dev/block/mmcblk0p18
reboot bootloader
You should now see this, and are done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy
Very nice.!
Note: This is case sensitive and the file should be placed on the root of your sdcard.
Please just use the "THANKS" feature.
We all need to help keep the Dev threads clean.
Sent from my HTC Incredible S using XDA Premium App
very good!!
look forward to s on～～～
Hi, Man, thank you so much, thanks for your hard working, god bless you.
very nice! good how to
need root ,s-on!!XXXXXXXX
it is soon~!
If a way to unlock the emmc write protection is found (it is not kernel based, and wpthis will not work), then this hboot can be used to set the phone s-off.
i think unlock s-on is not so far
jcase said:
If a way to unlock the emmc write protection is found (it is not kernel based, and wpthis will not work), then this hboot can be used to set the phone s-off.
Click to expand...
Click to collapse
to oil, s-on people wait for you, thx~~~
i think unlock s-on is not so far～～～
dump of vivo hboot after xtc-clip
Hi,
Thank you for this post.
Before trying to flash your hboot, i've made a dump of the one i've obtained after unlocking my phone with an xtc-clip.
It seems that this is the same as yours but a little bit more recent.
Version 1.09.0000.
I've uploaded it here : http://www.multiupload.com/QPS8W9RH0M
If someone is interested.
max-k said:
Hi,
Thank you for this post.
Before trying to flash your hboot, i've made a dump of the one i've obtained after unlocking my phone with an xtc-clip.
It seems that this is the same as yours but a little bit more recent.
Version 1.09.0000.
I've uploaded it here : http://www.multiupload.com/QPS8W9RH0M
If someone is interested.
Click to expand...
Click to collapse
Thanks for this. Couple of questions.
How did you dump the hboot image? I actually had no idea this was possible... Also, did the hboot version actually change after you used the xtc clip? I'm not 100% sure how the clip works internally, but was under the impression that it sets the flags at the radio level, and doesn't specifically modify the bootloader.
deficitism said:
Thanks for this. Couple of questions.
How did you dump the hboot image?
I actually had no idea this was possible...
Click to expand...
Click to collapse
I've dumped the image using your process :
dd if=/dev/block/mmcblk0p18 of=/sdcard/vivo_hboot.img
Also, perhaps it doesn't works. I don't try to reflash it yet.
deficitism said:
Also, did the hboot version actually change after you used the xtc clip? I'm not 100% sure how the clip works internally, but was under the impression that it sets the flags at the radio level, and doesn't specifically modify the bootloader.
Click to expand...
Click to collapse
I'm not sure too.
Perhaps you're right.
But, if you're right, i don't know if there are any differences between my old hboot and yours.
Options in "fastboot" and "bootloader" are the same.
max-k said:
I've dumped the image using your process :
dd if=/dev/block/mmcblk0p18 of=/sdcard/vivo_hboot.img
Also, perhaps it doesn't works. I don't try to reflash it yet.
I'm not sure too.
Perhaps you're right.
But, if you're right, i don't know if there are any differences between my old hboot and yours.
Options in "fastboot" and "bootloader" are the same.
Click to expand...
Click to collapse
The ENG (engineering) is on top. The hboot you dumped is on bottom of the picture, it is a SHIP hboot. Meaning, unless the radio says other wise, you are s-on. It also has limited fastboot commands, and checks for signatures before flashing.
XTC clip sets s-off in the radio config, and does not modify hboot in any way.
I do not know how you determined it to be the same. Most of the time ENG hboots are older, as they are not used in production, but in testing.
jcase said:
The ENG (engineering) is on top. The hboot you dumped is on bottom of the picture, it is a SHIP hboot. Meaning, unless the radio says other wise, you are s-on. It also has limited fastboot commands, and checks for signatures before flashing.
XTC clip sets s-off in the radio config, and does not modify hboot in any way.
I do not know how you determined it to be the same. Most of the time ENG hboots are older, as they are not used in production, but in testing.
Click to expand...
Click to collapse
Yep. Although, he should now be able to flash the engineering bootloader.
From the looks of it, it appears we should be able to talk to the bootloader through a USB cable with some sort of console access. I recall unrevoked's toolset doing so to temporarily disable the NAND protection long enough to flash a custom recovery. Unfortunately, these devices seem to only be booting factory signed hboot and recovery images.
We need either:
(1) As jcase said, an old ass radio image.
(2) A signed engineering bootloader
(3) A methodology for simulating the ports/diag commands that the sim unlock clip is using. And a way to send the config flags over USB.
(4) A brand spanking new vulnerability
Just thinking aloud.
I think best bet will be a new exploit to remove wp and allowed us to flash the eng hboot or set the radio s-off
Sent from my LG Revolution
jcase said:
The ENG (engineering) is on top. The hboot you dumped is on bottom of the picture, it is a SHIP hboot. Meaning, unless the radio says other wise, you are s-on. It also has limited fastboot commands, and checks for signatures before flashing.
XTC clip sets s-off in the radio config, and does not modify hboot in any way.
I do not know how you determined it to be the same. Most of the time ENG hboots are older, as they are not used in production, but in testing.
Click to expand...
Click to collapse
Thank-you for this explanations.
After floundering around for about a week trying to figure out how to get S=OFF on my nice new HTC One M7. I have done it.
With help from @ClydeB1 (top Man)
and a few others along the way whom I will credit during this post.
My ISP is Orange (EE) in the UK. My shiny new HTC one CID is ORANG001 FW 2.24.61.1 and software out the box was the same. Hboot 1.54. No Revone, moonshine or Rumrunner compatable files.
I saw some users having success flashing other SW mainly by flashing 401.8 and 401.1 and 161.1
I flashed stock versions of the above but no joy so I downloaded
Guru Reset M7 2.24.401.8 from @crushalot in http://forum.xda-developers.com/showthread.php?t=2471869
The above will wipe your recovery if you have a custom recovery installed.
Then I see some one (I am sorry I lost your post) flashing 401.8 with rumrunner 401.1
Then go to rumrunner http://rumrunner.us/
and download 2.24.401.1 (notice the last figure)
Follow all the instructions from these to sites and freedom is yours.
After I got S=OFF (6 Pour) I used @Mike1966 brilliant guide at http://forum.xda-developers.com/showthread.php?t=2265618 to reflash TWRP after. You will still keep all your files and backups tho. The only problem I had was after re-flash of TWRP it freezes. Therefore you are unable to nandroid but after you do fastboot flash recovery recovery.img (point 10) then you can do your first back up.
I am not a dev. Just thought I would help some one else who may be in the same boat.
If this post is in the wrong forum then would a nice kind mod please put it where it should be.
If this helps some one you will make my day by clicking my thanks button.
I was on the exact same firmware , I am with T-Mobile UK
I had 2.24.61.1 CID ORANG001 1.54
All I did to get S-off was use the Rumrunner for 2.24.161.1 and it worked perfect after Pouring 3
Someone else I think mentioned it in the bounty thread very shortly after rumrunner was released
tehdomil said:
I was on the exact same firmware , I am with T-Mobile UK
I had 2.24.61.1 CID ORANG001 1.54
All I did to get S-off was use the Rumrunner for 2.24.161.1 and it worked perfect after Pouring 3
Someone else I think mentioned it in the bounty thread very shortly after rumrunner was released
Click to expand...
Click to collapse
Yep. First thing I tried. No joy tho.
have any of you guys nandroid (backed-up) the original EE (orange/tmobile) software before flashing a custom rom?
my one has the worst battery life in the world. so i need to return it to stock and send it back to get repaired or whatever...would like to use the proper img to return to stock though as oppose the the other one which i have downloaded....(M7 CWM Nandroid Backup CID ORANG001 1.28.61.7 2013-04-22)
Cheers.
I wish. Can not find it anywhere. If you find it let me know please.
duryard said:
I wish. Can not find it anywhere. If you find it let me know please.
Click to expand...
Click to collapse
I have it, First thing I did was a nandroid backup on mine once I flashed TWRP, Will get it uploaded for you.
Cool
Jackering said:
I have it, First thing I did was a nandroid backup on mine once I flashed TWRP, Will get it uploaded for you.
Click to expand...
Click to collapse
That would be cool mate. Is it 2.24.61.1 or 1.28.61.7
duryard said:
That would be cool mate. Is it 2.24.61.1 or 1.28.61.7
Click to expand...
Click to collapse
2.24.61.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk
Jackering said:
2.24.61.1
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
@Jackering That will be ideal mate as I was unable to get a nandroid of mine.
duryard said:
@Jackering That will be ideal mate as I was unable to get a nandroid of mine.
Click to expand...
Click to collapse
Uploaded here: https://www.dropbox.com/sh/a85ma3hbi631qon/u_ZcyaGt5L
If anyone can mirror it I would be most grateful, Only place I can get it to upload is to my Dropbox.
Jackering said:
Uploaded here: https://www.dropbox.com/sh/a85ma3hbi631qon/u_ZcyaGt5L
If anyone can mirror it I would be most grateful, Only place I can get it to upload is to my Dropbox.
Click to expand...
Click to collapse
Thanks @Jackering I will zip them and get them up somewhere.
No problems, awesome.
---------- Post added at 07:32 PM ---------- Previous post was at 07:24 PM ----------
duryard said:
Thanks @Jackering I will zip them and get them up somewhere.
Click to expand...
Click to collapse
Sorry for the double post, do you know where I can find a stock recovery.img for our devices? Only one I can find is a US One.
Jackering said:
No problems, awesome.
---------- Post added at 07:32 PM ---------- Previous post was at 07:24 PM ----------
Sorry for the double post, do you know where I can find a stock recovery.img for our devices? Only one I can find is a US One.
Click to expand...
Click to collapse
No. I am still looking for that myself
stock stuff
@Jackering If you go to http://forum.xda-developers.com/showthread.php?t=2428276 crushalot has a recovery for the 2.24.161.1 which is Vodafone. I will ask him what if anything can be done with the files you uploaded as I was expecting them to be in a one single file.
duryard said:
Thanks @Jackering I will zip them and get them up somewhere.
Click to expand...
Click to collapse
duryard said:
@Jackering If you go to http://forum.xda-developers.com/showthread.php?t=2428276 crushalot has a recovery for the 2.24.161.1 which is Vodafone. I will ask him what if anything can be done with the files you uploaded as I was expecting them to be in a one single file.
Click to expand...
Click to collapse
You'll need to put them in a folder called 2013-11-02--18-12-40 JDQ39, The backup was taken with TWRP, so stick it in the TWRP Backups folder, then restore from it
A few questions guys...
Do your ORANG001 phones are locked to Orange and/or have any kind of branding in the software? Like any Orange apps? I'm asking this because I bought my HTC One off eBay and the seller said it was unlocked and simfree. I assumed it was HTC__001 but now that I have it on my hands I see it's an ORANG001.
I'm wondering if I should return it or keep it and proceed with the S-OFF procedure on this thread... More questions:
I believe S-OFF allows me to change the CID. Is there any benefit in doing so since I can just install whatever ROM I want and don't care about OTA updates anymore?
Does the S-OFF procedure here described require me to unlock the bootloader through HTC Dev website? If so, what's the point since if I have to return the phone for warranty they will check their database and see I've unlocked the bootloader?
With S-OFF I can set the bootloader to LOCKED instead of RELOCKED? And unlock it again at will, correct?
Does S-OFF allow me to change the CID number and set the phone to LOCKED, making it look like a WWE phone?
Does getting S-OFF once allows me to change the phone back to S-ON and back to S-OFF at will?
Nazgulled said:
A few questions guys...
Do your ORANG001 phones are locked to Orange and/or have any kind of branding in the software? Like any Orange apps? I'm asking this because I bought my HTC One off eBay and the seller said it was unlocked and simfree. I assumed it was HTC__001 but now that I have it on my hands I see it's an ORANG001.
I'm wondering if I should return it or keep it and proceed with the S-OFF procedure on this thread... More questions:
I believe S-OFF allows me to change the CID. Is there any benefit in doing so since I can just install whatever ROM I want and don't care about OTA updates anymore?
Does the S-OFF procedure here described require me to unlock the bootloader through HTC Dev website? If so, what's the point since if I have to return the phone for warranty they will check their database and see I've unlocked the bootloader?
With S-OFF I can set the bootloader to LOCKED instead of RELOCKED? And unlock it again at will, correct?
Does S-OFF allow me to change the CID number and set the phone to LOCKED, making it look like a WWE phone?
Does getting S-OFF once allows me to change the phone back to S-ON and back to S-OFF at will?
Click to expand...
Click to collapse
I will answer some of your questions.
My Phone (ORANG001) is locked to orange but has no orange branding/software. I have no idea if it is sim free or not as not tried another sim. Easy enough to try tho.
You Must unlock the boot loader before S=Off. HTC AFAIK both can be reversed.
I have sent phones to repair in the past (HTC Sensation and desire) Unlocked, S=Off and custom rom and never had HTC refuse to repair them.
You only need Unlocked boot loader to change roms. AFAIK S=Off allows you to update the FW
Click the link in my sig for a good place to start.
Thanks.
But could anyone clarify a little bit more, please?
Nazgulled said:
A few questions guys...
Do your ORANG001 phones are locked to Orange and/or have any kind of branding in the software? Like any Orange apps? I'm asking this because I bought my HTC One off eBay and the seller said it was unlocked and simfree. I assumed it was HTC__001 but now that I have it on my hands I see it's an ORANG001.
I'm wondering if I should return it or keep it and proceed with the S-OFF procedure on this thread... More questions:
I believe S-OFF allows me to change the CID. Is there any benefit in doing so since I can just install whatever ROM I want and don't care about OTA updates anymore?
Does the S-OFF procedure here described require me to unlock the bootloader through HTC Dev website? If so, what's the point since if I have to return the phone for warranty they will check their database and see I've unlocked the bootloader?
With S-OFF I can set the bootloader to LOCKED instead of RELOCKED? And unlock it again at will, correct?
Does S-OFF allow me to change the CID number and set the phone to LOCKED, making it look like a WWE phone?
Does getting S-OFF once allows me to change the phone back to S-ON and back to S-OFF at will?
Click to expand...
Click to collapse
1) changing cid doesn't make a lot of difference, but you are best changing it to HTC__001 so that you can flash custom firmware
2) s-off does require an unlocked bootloader
3) to get a "locked" bootloader you would need to flash an RUU
4) you can change cid to HTC__001 WWE, to get locked instead of relocked see above
5) Depends, if you change hboot after getting s-off, once you go back s-on again you may not then be able to go back to s-off
thanks for the Nandroids guys! @Jackering
using 3.62.401.1 at the moment, but restored the stock recovery image (pretty sure its just a WWE same as 401 type)
@clarkson63 @Nazgulled you can set your bootloader to locked again without using a RUU. http://forum.xda-developers.com/showthread.php?t=2475914 Have a look there. It does require s-off to do, but thats fine once you use rumrunner (in Linux, for it to work for me) then just adb using SU and you can lock your bootloader
Also, as long as your hboot is original you should be able to go from s-off to s-on easy as you did the first time, its highly un-recommended though as this has a possibility to brick the device (if not stock hboot etc)
EDIT: also, how long do your battery's last guys? @clarkson63 @Nazgulled @Jackering I'm lucky if I get 10-12hours out of mine and that is with moderate/light usage! Certainly no heavy usage! Since the phones in my pocked most of the day during work.
My phone is Hboot 1.13 with S-OFF already.
This is what is shown when I press volume down+power
VIVO PVT SHIP S-OFF RL
HBOOT - 1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011, 18:34:39
How do I root it and install custom recovery in this? Please guide.
moomal said:
My phone is Hboot 1.13 with S-OFF already.
This is what is shown when I press volume down+power
VIVO PVT SHIP S-OFF RL
HBOOT - 1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011, 18:34:39
How do I root it and install custom recovery in this? Please guide.
Click to expand...
Click to collapse
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
072665995 said:
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
Click to expand...
Click to collapse
Thanks a lot
072665995 said:
Reboot to fastboot.
Flash custom Recovery.
Flash superuser script.
Flash whatever ROM.
The specifics of how to do those 4 above steps should be in every guide. Just search the guide a bit
Click to expand...
Click to collapse
I tried to flash through my PC. But it says Failed (Not allowed) Can you tell what the problem might be?
moomal said:
I tried to flash through my PC. But it says Failed (Not allowed) Can you tell what the problem might be?
Click to expand...
Click to collapse
How can i fix your problem if i IBT even know what's wrong??
Can you post a screenshot of the cmd ??
Sent from my Incredible S using xda app-developers app
072665995 said:
How can i fix your problem if i IBT even know what's wrong??
Can you post a screenshot of the cmd ??
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
moomal said:
Click to expand...
Click to collapse
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
mafie said:
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
Click to expand...
Click to collapse
Tried that too. Still won't work
moomal said:
Click to expand...
Click to collapse
windows 8 might be a bit different. Search a bit online.
Also search in google "writing recovery FAILED"
I'm sure other people have had this problem before.
072665995 said:
windows 8 might be a bit different. Search a bit online.
Also search in google "writing recovery FAILED"
I'm sure other people have had this problem before.
Click to expand...
Click to collapse
Can't find any for Incredible s.
mafie said:
i guess it doesn't work with win8. Try running cmd with admin rights. if fails then. try with Win7
Click to expand...
Click to collapse
My phone is refurbished and it's still on Android 2.3.3 (It won't update) In case it helps.
Okay. This is a stupid question.. but just in case.. is your bootloader locked or unlocked?? I feel something is wrong there..
The same happened with one of my friend too..
Sent from my HTC Incredible S
moomal said:
Click to expand...
Click to collapse
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
cowboysgz said:
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
Click to expand...
Click to collapse
Just run revolutionary. Flash custom recovery. Flash Superuser script and you're good to go.
Also stop posting the same issue multiple times. Its possibly the easiest way to piss another XDA member off. Post once about your issue in the general forum and DO NOT post again somewhere else.
cowboysgz said:
Were you able to flash anything? Mine says hboot 1.13 too but no locked or unlocked water mark with S-OFF but when I type in commands it sayas I cant. Did you fix it? I dont even have a custom recovery or rom. It's just dead
Click to expand...
Click to collapse
Yes I was able to do it. Since it's S-OFF but still unlocked so it won't allow you. So I followed this link:
http://forum.xda-developers.com/showthread.php?t=1591729
It would do it for sure
Hi to all!!! :laugh:
Sorry if this was posted previously somewhere here...but i'm wondering trying to find a definitive answer to this...
I'm coming back to an HTC One (new, not used), so is there the possibility to have the S-OFF without get in touch with HTCdev with the latest H-BOOT version?
Please excuse me if this already exists here...but I just couldn't found a definitive answer...
Thanks in advance to everyone will post an help! :good:
--anx-- said:
Hi to all!!! :laugh:
Sorry if this was posted previously somewhere here...but i'm wondering trying to find a definitive answer to this...
I'm coming back to an HTC One (new, not used), so is there the possibility to have the S-OFF without get in touch with HTCdev with the latest H-BOOT version?
Please excuse me if this already exists here...but I just couldn't found a definitive answer...
Thanks in advance to everyone will post an help! :good:
Click to expand...
Click to collapse
1- There's no such thing as a definitive answer, because nobody can say that you will get S-Off even with unlocked (HTCdev) bootloader
2- there's no such thing as "latest hboot", that's why version numbers exist... "latest" (as far as i'm aware of) at the time of this writing is hboot 1.57
anyway, to answer your question:
3- you can try http://firewater-soff.com/ using the temproot exploit, but if it doesn't work, then i guess the answer would be no;
there's also WeakSauce temproot, which may or may not work also.
nkk71 said:
1- There's no such thing as a definitive answer, because nobody can say that you will get S-Off even with unlocked (HTCdev) bootloader
2- there's no such thing as "latest hboot", that's why version numbers exist... "latest" (as far as i'm aware of) at the time of this writing is hboot 1.57
anyway, to answer your question:
3- you can try http://firewater-soff.com/ using the temproot exploit, but if it doesn't work, then i guess the answer would be no;
there's also WeakSauce temproot, which may or may not work also.
Click to expand...
Click to collapse
Wow...to get a reply from an Android Revolution team member it's really perfect!!! :highfive:
I'll have to try the first option then the second and follow the instructions wrote down there right? But in all the two cases I'll have to request the HTCdev token I'm afraid... :crying:
I just have planned to install the Android Revolution with the last Sense 6 right after unboxing the brand new phone...
--anx-- said:
Wow...to get a reply from an Android Revolution team member it's really perfect!!! :highfive:
I'll have to try the first option then the second and follow the instructions wrote down there right? But in all the two cases I'll have to request the HTCdev token I'm afraid... :crying:
I just have planned to install the Android Revolution with the last Sense 6 right after unboxing the brand new phone...
Click to expand...
Click to collapse
Why so worried about HTCdev?
Anyway, you can give the temproot exploits a try; maybe you'll be one of the lucky ones and it/they work for you.... if not then you'll need to unlock using HTCdev
nkk71 said:
Why so worried about HTCdev?
Anyway, you can give the temproot exploits a try; maybe you'll be one of the lucky ones and it/they work for you.... if not then you'll need to unlock using HTCdev
Click to expand...
Click to collapse
Well...the only thing that annoy me about HTCdev it's the fact that they'll know that you've unlocked the phone and can bother you if you'll send the phone to them in case of need of assistance...even if it had hardware faults...that's the only thing...
--anx-- said:
Well...the only thing that annoy me about HTCdev it's the fact that they'll know that you've unlocked the phone and can bother you if you'll send the phone to them in case of need of assistance...even if it had hardware faults...that's the only thing...
Click to expand...
Click to collapse
well,
1- plenty of guides around to returning 100% to stock (including mine )
2- just because you used HTCdev, can they actually prove you used the unlock code? maybe you requested one, and then got scared and didn't use it after all... how can they prove you unlocked your device just because you asked for a code?
nkk71 said:
well,
1- plenty of guides around to returning 100% to stock (including mine )
2- just because you used HTCdev, can they actually prove you used the unlock code? maybe you requested one, and then got scared and didn't use it after all... how can they prove you unlocked your device just because you asked for a code?
Click to expand...
Click to collapse
Oh...so, even if I'm S-ON I can return 100% back to stock? tampered signature deletion included?
Excuse me again, but I've left for too much time HTC One development, my fault....
--anx-- said:
Oh...so, even if I'm S-ON I can return 100% back to stock? tampered signature deletion included?
Excuse me again, but I've left for too much time HTC One development, my fault....
Click to expand...
Click to collapse
with S-On, you can only set it back to RELOCKED not LOCKED, so you still need S-Off for that, the problem isn't HTCdev, the problem is whether S-Off is going to work or not, very likely yes, but there have been a lot of "unable to get S-Off" threads recently.
nkk71 said:
with S-On, you can only set it back to RELOCKED not LOCKED, so you still need S-Off for that, the problem isn't HTCdev, the problem is whether S-Off is going to work or not, very likely yes, but there have been a lot of "unable to get S-Off" threads recently.
Click to expand...
Click to collapse
So there's a possibility of that problem...but generally the trick have to work in most of the cases I've read...
But in order to gain S-OFF you still have to unlock the phone via HTCdev and then try the trick...if I'm not wrong at least...
--anx-- said:
So there's a possibility of that problem...but generally the trick have to work in most of the cases I've read...
But in order to gain S-OFF you still have to unlock the phone via HTCdev and then try the trick...if I'm not wrong at least...
Click to expand...
Click to collapse
Hopefully it will work, but you can try the temproot exploit method first, it's very likely to fail on newer ROMs, but you can try!!
from firewater method 2:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nkk71 said:
Hopefully it will work, but you can try the temproot exploit method first, it's very likely to fail on newer ROMs, but you can try!!
from firewater method 2:
Click to expand...
Click to collapse
Wow! So before the real unlock bis via HTCdev I can try this temp root and see if this work to gain the S-OFF prior to act with HTCdev usual method...
Seems really good...hope it will work...
When I'll receive the phone I'll try these steps as you suggested: first try with temp root method...if this didn't work I'll have to go with HTCdev and after that try one of those methods to gain S-OFF...hoping that them will work...
I'm on the right wave?
--anx-- said:
Wow! So before the real unlock bis via HTCdev I can try this temp root and see if this work to gain the S-OFF prior to act with HTCdev usual method...
Seems really good...hope it will work...
When I'll receive the phone I'll try these steps as you suggested: first try with temp root method...if this didn't work I'll have to go with HTCdev and after that try one of those methods to gain S-OFF...hoping that them will work...
I'm on the right wave?
Click to expand...
Click to collapse
lol
"]When I'll receive the phone"... maybe the phone will come S-Off, or on hboot 1.44, etc.
so first get the phone, do a "fastboot getvar all" and then you can see which method will/should work for you (revone, rumrunner, firewater, weaksauce)
nkk71 said:
lol
"]When I'll receive the phone"... maybe the phone will come S-Off, or on hboot 1.44, etc.
so first get the phone, do a "fastboot getvar all" and then you can see which method will/should work for you (revone, rumrunner, firewater, weaksauce)
Click to expand...
Click to collapse
Why "fastboot getvar all" and not a simple boot into recovery to see the actual hboot version?
I'm just keeping myself "ready" for the big one...
--anx-- said:
Why "fastboot getvar all" and not a simple boot into recovery to see the actual hboot version?
I'm just keeping myself "ready" for the big one...
Click to expand...
Click to collapse
same difference
fastboot getvar all won't harm your phone, but you could keep it as a record.
and you are right bootloader will give you 1 piece of information that the getvar won't ... the date of hboot (only significant if it's hboot 1.44)
oh and the big One, is the M8, the M7 is a bit smaller
nkk71 said:
same difference
fastboot getvar all won't harm your phone, but you could keep it as a record.
and you are right bootloader will give you 1 piece of information that the getvar won't ... the date of hboot (only significant if it's hboot 1.44)
oh and the big One, is the M8, the M7 is a bit smaller
Click to expand...
Click to collapse
So I can go into fastboot like very other phone an see the hboot version if it's good for s-off or I can use the getvar all command in equal...
Well you're right anyway...the Big One it's the M8...but a phone that keeps itself actual and still rockin after one year out...well...it's big too...
--anx-- said:
So I can go into fastboot like very other phone an see the hboot version if it's good for s-off or I can use the getvar all command in equal...
Well you're right anyway...the Big One it's the M8...but a phone that keeps itself actual and still rockin after one year out...well...it's big too...
Click to expand...
Click to collapse
I have the One just here!
The HBOOT is 1.56.0000, with RADIO-4A.25.3263.21, date Feb 26 2014...with Android 4.4.2 and Sense 5.5...
I still can try the S-OFF procedure with these parameters???
--anx-- said:
I have the One just here!
The HBOOT is 1.56.0000, with RADIO-4A.25.3263.21, date Feb 26 2014...with Android 4.4.2 and Sense 5.5...
I still can try the S-OFF procedure with these parameters???
Click to expand...
Click to collapse
It's highly unlikely the temproot exploits will work (so you'll have to unlock using HTCdev), but:
to be perfectly honest, I think you're jumping the gun a little with S-Off. I think you should do some more research into the M7, because the information you provided sounds like you're quite new this phone.
I can more or less guess, what ROM and firmware you have, but maybe you should first understand the differences between ROM, firmware, radio, kernel, etc.
and where you get that information and using which tools.
Also take a look at Do we really need S-OFF?
I'm not trying to be say you shouldn't get S-Off, but all in good time, once you are familiar with it and what it allows you to do.
nkk71 said:
It's highly unlikely the temproot exploits will work (so you'll have to unlock using HTCdev), but:
to be perfectly honest, I think you're jumping the gun a little with S-Off. I think you should do some more research into the M7, because the information you provided sounds like you're quite new this phone.
Click to expand...
Click to collapse
Honestly yes, I've already had the One in last year's July, but never unlocked it...only stock since I've sold it...so I've never get deep into modifications, rom, tools etcetera...
nkk71 said:
I can more or less guess, what ROM and firmware you have, but maybe you should first understand the differences between ROM, firmware, radio, kernel, etc.
and where you get that information and using which tools.
Also take a look at Do we really need S-OFF?
I'm not trying to be say you shouldn't get S-Off, but all in good time, once you are familiar with it and what it allows you to do.
Click to expand...
Click to collapse
If HTC don't let the HARDWARE warranty die or make it complicated with unlocking the phone, I'd probably unlocked the phone in 0 time since unboxing the phone, via HTCdev...but the fact that the warranty will be a trivia (even with hardware faults...) with the "tampered" and "relocked" question...well...I'm really afraid to let "the rom game" begin like I've done with almost all the phones that I've had...in fact now I know ADB, Fastboot, push commands via Terminal (MacOs) like the palm of my hand... :laugh:
--anx-- said:
Honestly yes, I've already had the One in last year's July, but never unlocked it...only stock since I've sold it...so I've never get deep into modifications, rom, tools etcetera...
If HTC don't let the HARDWARE warranty die or make it complicated with unlocking the phone, I'd probably unlocked the phone in 0 time since unboxing the phone, via HTCdev...but the fact that the warranty will be a trivia (even with hardware faults...) with the "tampered" and "relocked" question...well...I'm really afraid to let "the rom game" begin like I've done with almost all the phones that I've had...in fact now I know ADB, Fastboot, push commands via Terminal (MacOs) like the palm of my hand... :laugh:
Click to expand...
Click to collapse
fair enough, but what I meant before:
1- ROM is usually found in Settings->About
2- firmware is what you get from a fastboot getvar all
3- Android version is irrelevant as we're more interested in the base
4- radio doesn't matter, cause you can flash any radio you want (even with S-On) on the M7
you can go ahead and try the temproot exploits, but I doubt that they will work on a 4.xx ROM.... so you will have no choice but to use HTCdev to unlock... and again, how can they prove you actually used the code, not just asked for one, and then got scared
and even if you don't get S-Off, you can still install a custom recovery (TWRP 2.6.3.3+ preferred at the moment), and install a custom ROM.
nkk71 said:
fair enough, but what I meant before:
1- ROM is usually found in Settings->About
2- firmware is what you get from a fastboot getvar all
3- Android version is irrelevant as we're more interested in the base
4- radio doesn't matter, cause you can flash any radio you want (even with S-On) on the M7
you can go ahead and try the temproot exploits, but I doubt that they will work on a 4.xx ROM
Click to expand...
Click to collapse
Yes, got it...and I've checked but I've noticed that 4.4.2 isn't supported for the temproot, only 4.3...sadly...
nkk71 said:
.... so you will have no choice but to use HTCdev to unlock... and again, how can they prove you actually used the code, not just asked for one, and then got scared
and even if you don't get S-Off, you can still install a custom recovery (TWRP 2.6.3.3+ preferred at the moment), and install a custom ROM.
Click to expand...
Click to collapse
Yes, with S-ON pratically I can do everything, I've done that before on my old HTC ONE S some months ago, I remember it...but...HTC can recognize the unlocking because I'll have the "TAMPERED" and "RELOCKED" signatures in fastboot...so they can prove that I've used the token...while with S-OFF you can restore these signatures back to "stock" totally...like you've never used that token...
This is the only hassle...
hi all
i have a HTC One M7_UL
i updated my phone OTA from the setting , phone restarted , battry 0 and phone off
now im on the bootloader setting
i tried to unlock my phone bootloader to install a custom rom , but it failed in unlock process
then i tried to find a original rom for my phone and install RUU or original ZIP but i cant find the Correct rom
see this pictures please , this is all info you need to know
please help me ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello alishadlou,
here you could find stock roms from Google Play Edition and Firmware.
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
You could take a look here too:
http://forum.xda-developers.com/showthread.php?t=2358781
Hope that help you out.
Greeting
Crytix
alishadlou said:
hi all
i have a HTC One M7_UL
i updated my phone OTA from the setting , phone restarted , battry 0 and phone off
now im on the bootloader setting
i tried to unlock my phone bootloader to install a custom rom , but it failed in unlock process
then i tried to find a original rom for my phone and install RUU or original ZIP but i cant find the Correct rom
Click to expand...
Click to collapse
GPE devices must be unlocked using "fastboot oem unlock" not using htcdev.com
Your bootloader version (1.44) doesn't match your firmware version btw
But tell me, I see in your post history that you have bricked 6 different phones in 5 months... How is that possible ?
alray said:
Your bootloader version (1.44) doesn't match your firmware version btw
Click to expand...
Click to collapse
not to mention he has the HTC (white) hboot, not the GPE (black) one
that device was definitely S-OFF before
alray said:
GPE devices must be unlocked using "fastboot oem unlock" not using htcdev.com
Your bootloader version (1.44) doesn't match your firmware version btw
But tell me, I see in your post history that you have bricked 6 different phones in 5 months... How is that possible ?
Click to expand...
Click to collapse
very very thanks for your nice help ( i love the people who help each other like this .... )
my phone + my friends phone sometimes + love to change roms , try new things , and all of them , and maybe this will be my job for future .
and i treid that you said
but this error
check it please
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so. The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities. So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Google and HTC
BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
Click to expand...
Click to collapse
Greeting
Crytix
Crytix said:
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so. The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities. So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Google and HTC
Greeting
Crytix
Click to expand...
Click to collapse
the reason i want to unlock the phone , is that i want install custom rom to can use my phone !!!
phone is hang on logo now !!! and i couldnt find the RUU for my phone ( can you please help me find my correct ruu file ? then i install it and using phone dont need unlock any more
Crytix said:
You could take a look here too:
http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
Here you could find the stock ruu, firmware, bootloader and recovery.
alishadlou said:
the reason i want to unlock the phone , is that i want install custom rom to can use my phone !!!
phone is hang on logo now !!! and i couldnt find the RUU for my phone ( can you please help me find my correct ruu file ? then i install it and using phone dont need unlock any more
Click to expand...
Click to collapse
I don´t allow to link outside xda, because I´m low poster. Please use the external link in that topic linked above.
Greetings
Crytix
Crytix said:
I think your HBoot needs to be upgraded, and it sounds like perhaps you didn't run the RUU to do so.
Click to expand...
Click to collapse
The actual Hboot installed on OP's phone is a Hboot from a Sense based firmware (not a GPE hboot) like nkk71 noted. GPE hboot are black colored. The current firmware version installed (5.11.1700.3) include the 1.54 GPE (black) hboot (he is on 1.44). So its a Sense hboot on a GPE phone + not the right version number for the firmware installed, so its confirm what nkk71 said, that phone was previously s-off, someone flashed the wrong hboot and turned it back s-on.
That being said, you can only, on a "normal" GPE phone, unlock the bootloader using the "fastboot oem unlock" command as opposed to Sense firmware which must be unlocked using htcdev's unlock code. There is also a well known bug with newer GPE firmware (hboot 1.54+) making the bootloader not unlockable.
So in theory, since the phone is running a Sense Hboot, he should be able to unlock using htcdev's unlock code which doesn't seem to work. "fastboot oem unlock" method for GPE variant doesn't work neither.
In his situation, he probably can't unlock his phone because of the wrong hboot installed vs his current firmware version or since the phone was s-off at some point, he might have a custom hboot...
The HTCdev site notes that phones with an asterisk (*) next to them in the list must run an RUU before unlocking because the bootloader on the device did not originally ship with unlocking capabilities.
Click to expand...
Click to collapse
And this is not applicable to the M7, all shipped M7 bootloader were unlockable and currently, the only M7 version that can't be unlocked is Verizon due to carrier demand.
So first you need to make sure your firmware is up to date (which it sounds like it is), and then you also need to download and run the RUU.
Click to expand...
Click to collapse
Updating the firmware or flashing a RUU will not solve his problem with the not unlockable bootloader. He will definitively need s-off again.[...deleted...] I would try to flash the ruu and achieve s-off with sunshine.
alray said:
Updating the firmware or flashing a RUU will not solve his problem with the not unlockable bootloader. He will definitively need s-off again. I would try to s-off before trying a RUU and then if its not working, flashing the ruu and try to s-off again.
Click to expand...
Click to collapse
With hboot 1.44 it's possible to unlock and S-Off with revone.
@op could you get an adb connection to your phone? Recovery for example.
If not, I can't help you more. Sorry.
Crytix said:
With hboot 1.44 it's possible to unlock and S-Off with revone.
Click to expand...
Click to collapse
Just realized he can't do what I suggested above (I would try to s-off before trying a RUU ), the phone is bricked. Your phone must be able to boot in the OS to achieve S-OFF. So he will need to flash the RUU so the phone can boot and then if he still want to unlock his bootloader, he will need to use Sunshine S-OFF (hboot will not be 1.44 anymore after the ruu).
could you get an adb connection to your phone? Recovery for example.
Click to expand...
Click to collapse
You can only use adb commands from 2 places
1- from a booted OS with usb debug turned ON ---> not possible phone is bricked
2- From custom recovery ---> not possible bootloader is locked, even if he aleady had a custom recovery installed, he can't boot to it, bootloader must be unlocked to boot a custom recovery.
and anyway, adb connection won't help since all S-OFF exploits need a working OS to do the magic...
alray said:
Just realized he can't do what I suggested above (I would try to s-off before trying a RUU ), the phone is bricked. Your phone must be able to boot in the OS to achieve S-OFF. So he will need to flash the RUU so the phone can boot and then if he still want to unlock his bootloader, he will need to use Sunshine S-OFF (hboot will not be 1.44 anymore after the ruu).
You can only use adb commands from 2 places
1- from a booted OS with usb debug turned ON ---> not possible phone is bricked
2- From custom recovery ---> not possible bootloader is locked, even if he aleady had a custom recovery installed, he can't boot to it, bootloader must be unlocked to boot a custom recovery.
and anyway, adb connection won't help since all S-OFF exploits need a working OS to do the magic...
Click to expand...
Click to collapse
first of all thanks for nice explains and i know very good things now
wht i should i do now ? i dont know what RUU can i install on my phone , the version its not matter for me , i just want my phone back and can use it
help me please
i cant find the correct version and i dont know what ruu i can install on my phone
alishadlou said:
first of all thanks for nice explains and i know very good things now
wht i should i do now ? i dont know what RUU can i install on my phone , the version its not matter for me , i just want my phone back and can use it
help me please
i cant find the correct version and i dont know what ruu i can install on my phone
Click to expand...
Click to collapse
5.11.1700.3 ruu. Check in the general section there is a ruu sticky thread. At post 1 you'll find instructions how to flash the ruu and also the 5.11.1700.3 ruu
alray said:
5.11.1700.3 ruu. Check in the general section there is a ruu sticky thread. At post 1 you'll find instructions how to flash the ruu and also the 5.11.1700.3 ruu
Click to expand...
Click to collapse
<3 Tnxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <3
My Phone is up nowww
thankkk youu very much
tnx everybody
my phone worked nice , but yesterday , its turn off and no power
when i connect it to pc , its show this driver installing : qhsusb dload
what should i do now ?
help please ...
no help ... ? ....
Use charger to charge it till 100%.