I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
lulzy1 said:
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
Click to expand...
Click to collapse
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
ramjet73 said:
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
Click to expand...
Click to collapse
your guide is the first guide I tried with no luck.. and yes im sprint
lulzy1 said:
your guide is the first guide I tried with no luck.. and yes im sprint
Click to expand...
Click to collapse
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Definitely post up the information ramjet73 is asking for.
Btw ramjet, you are quick. You always beat me to it!
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Sent from my PG86100 using Tapatalk 2
ramjet73 said:
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Click to expand...
Click to collapse
bootloader header
***unlocked*** (currently, as I relock it to run RUU)
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar cid
cid: SPCS_001
finished. total time: -0.000s
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
My battery is too low to run RUU right and im about to go to sleep I will update with the exact wording tomorrow but it says that Do not have the right RUU for my device. and if i am remembering correctly it says error 155 but I cant be 100% positive.
what i am using is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed
Brian706 said:
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Click to expand...
Click to collapse
He said in the OP that "I relock before using RUU but no matter what i get this message", but that's why I want to see his bootloader info and the text of the message he is getting.
I always recommend starting the RUU.exe with the phone in "fastboot usb" mode, but in theory it should work even if he is booted into Android.
Let's see what he has to say.
lulzy1 said:
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
Click to expand...
Click to collapse
That mainver doesn't look right. I should be 2.89.651.2 if you are on hboot 1.58. If that's really the current mainver it would explain why you can't flash the RUU. I have no idea how that could have been changed without flashing something with an incorrect android-info.txt in a PG86IMG.zip file, which requires S-OFF, or someone setting the mainver incorrectly via ADB. Did you get the phone new or used?
Please verify that is correct, and if it is, it will need to changed before the RUU will take.
Also, when you try to run the RUU.exe again make sure the phone is in fastboot USB mode.
ramjet73
I will rerun the comand later to make sure, I always run it from fastboot usb. Also i got the phone as an insurance replacement. sprint sucks so bad there is no telling if the phone is actually new or not
ok.. update I redid your command this morning and got what you were looking for.
C:\Users\lulzy\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: 2.89.651.2
finished. total time: 0.000s
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
lulzy1 said:
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
Click to expand...
Click to collapse
So your CID and mainver look OK.
The 155 error usually means your current bootloader is unlocked.
Try relocking your your bootloader, then remove and and replace the battery and start the bootloader. Since your bootloader is currently unlocked, the status should show as "*** RELOCKED ***". Make sure it does and that you are connected to your PC in "fastboot usb" mode, then try it again.
If that doesn't work, you can try downloading just the RUU.exe from here. It's the same one that is in the QADERSO .zip file, but it's worth a try.
ramjet73
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
lulzy1 said:
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
Click to expand...
Click to collapse
The battery low indicator in fastboot mode sounds like a hardware problem to me. If your battery isn't charging correctly it may be a problem with your cable or USB port. Many people have gotten the RUU.exe to flash successfully by changing to a different cable and/or PC, but if you can't do that I suggest fully charging the battery with the A/C adapter that came with the phone before trying to flash the RUU.exe again.
Flashing the RUU.exe with the phone in Android mode may be masking the problem, but something is not right with your hardware.
ramjet73
all done!! different computer and cord works.
Thanks alot
How do you relock the hboot? I'm getting the same error. Thanks.
"fastboot OEM lock"
Phone:
Sprint HTC EVO 3D
Root & S-Off(JBear)
HBoot: JBear 1.58.5858
Firmware: 2.89.651.5
Radio: 1.09.00.0706
Rom: FroZenROM Ep 2.1
Kernel: AnthraX 2.7.0
Recovery: TWRP 2.3.3.0
SDCard: San Disk 64GB Extreme Class 10 UHS-1 (Low External Storage Wizard? Uninstall)
i need help
i need some help fixing my phone i rooted it had it working well for about 2 hours changed somthing now im stuck on the htc green and white sceen
my bootloader says relocked ive been trying to follow the guides but nothing seems to work, right now the phone is in the bootloader as thats all ive been able to access i have a virgin mobile evo 3d with hboot 1.58..can somebody please help me? or is my phone screwed?
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Brian706 said:
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Click to expand...
Click to collapse
thanks for the response but i actually managed to fix it yesterday. idk what i changed but i was using the clockworld recovery but it wouldnt install the stock shooter file so i used 4ext and its all bueno now except it boots as a sprint phone now but whatever i can deal with that
Glad you got it!
I'd stick with 4ext. I have heard cwm doesn't play well with this device but have not experienced it first hand.
Yea I won't be putting that back on my phone now I have a question I believe I have the vmobile stock shooter on my pc I need to fast boot that to get my splash screen and stuff back right? Cause right now when I turn it on it says sprint
Related
i rooted my girlfriends sprint evo 3d using unknownforce's down grade method, i wanna return her phone back to complete stock how would i do that? she is s-off right now. thanks for the advice
You could flash an ruu from bootloader since your s-off. Here's a link for a list of ruu pick the one that says ics shooter 35 s 2.89 1.09.00.0706 spcs wwe to that nature http://www.filefactory.com/f/4ef0ef536face67a/. Just remember to rename the file PG86IMG in all caps and place on the root of your sdcard. Power down your phone, and boot up into bootloader and let your phone detect the file and confirm to update. Next you might want to get a drink or something to eat. It'll take like 10 minutes. Hope that helps
Jsparta26 said:
You could flash an ruu from bootloader since your s-off. Here's a link for a list of ruu pick the one that says ics shooter 35 s 2.89 1.09.00.0706 spcs wwe to that nature http://www.filefactory.com/f/4ef0ef536face67a/. Just remember to rename the file PG86IMG in all caps and place on the root of your sdcard. Power down your phone, and boot up into bootloader and let your phone detect the file and confirm to update. Next you might want to get a drink or something to eat. It'll take like 10 minutes. Hope that helps
Click to expand...
Click to collapse
that will revert the s-off to right?
wikedone said:
that will revert the s-off to right?
Click to expand...
Click to collapse
No.
You need to issue the "fastboot oem writescureflag 3" command with the phone in fastboot USB mode after flashing the RUU to reset the S-OFF status to S-ON. Make sure you have the stock bootloader installed before you do that.
ramjet73
ramjet73 said:
No.
You need to issue the "fastboot oem writescureflag 3" command with the phone in fastboot USB mode after flashing the RUU to reset the S-OFF status to S-ON. Make sure you have the stock bootloader installed before you do that.
ramjet73
Click to expand...
Click to collapse
ok the file i downloaded is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe i just rename that to PG86IMG or what cuz when i run the ruu in windows it errors out with usb connectio error
wikedone said:
ok the file i downloaded is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe i just rename that to PG86IMG or what cuz when i run the ruu in windows it errors out with usb connectio error
Click to expand...
Click to collapse
The .exe version of the RUU needs to be run from Windows. Make sure your phone is in the "fastboot usb" mode in the bootloader and the "fastboot devices" command returns your serial number before you run the RUU.
There's also a .zip version of the RUU around somewhere on these forums that can be run from the bootloader, but I don't have a link to that. It would be safer to extract it yourself from the RUU.exe using this procedure.
ramjet73
ramjet73 said:
The .exe version of the RUU needs to be run from Windows. Make sure your phone is in the "fastboot usb" mode in the bootloader and the "fastboot devices" command returns your serial number before you run the RUU.
There's also a .zip version of the RUU around somewhere on these forums that can be run from the bootloader, but I don't have a link to that. It would be safer to extract it yourself from the RUU.exe using this procedure.
ramjet73
Click to expand...
Click to collapse
ok i got the ruu to run and the phone is updated to ICS the hboot says
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
RADIO-1.09.00.0706
OpenADSP-v02.6.0.2226.00.0217
eMMC-boot
May 17 2012, 15:06:44
How do i know if i have the stock bootloader so i can Make it S-On
wikedone said:
ok i got the ruu to run and the phone is updated to ICS the hboot says
*** LOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
^^^^^^^^^^^
How do i know if i have the stock bootloader so i can Make it S-On
Click to expand...
Click to collapse
That's the stock bootloader, which was installed by the RUU. Most of the custom bootloaders (Revolutionary, Juopunutbear) have their name where the "*** LOCKED ***" status shows on your phone.
ramjet73
It's also courtesy to hit the thank you button when someone has helped you (meaning ramjet) Just thought I would throw that out.
Well first of all I will say that I am running a CDMA EVO3D with HBOOT 1.58 and S-ON.
Now with that out of the way, I will explain myself. After rooting my phone after the ICS update, i installed some ROMs and encountered some problems. After researching what the problem was I had managed to keep S-ON and that is why some of the features were broke. Then after doing more research I decided that it would be best to go back to stock and redo everything. So right now I have relocked my phone and am still running a custom ICS ROM. I have tried numerous RUU attempts and I always get the ERROR [140]: Bootloader Version Error after it try's "Sending/Updating Signature". So what in the world do I do next
Which RUU are trying to flash and where did you get it?
ramjet73
ramjet73 said:
Which RUU are trying to flash and where did you get it?
ramjet73
Click to expand...
Click to collapse
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed -Just copied the whole name if that works lol, and I got it from this thread
lxbeale said:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed -Just copied the whole name if that works lol, and I got it from this thread
Click to expand...
Click to collapse
That's a GB RUU and you are on the Sprint ICS build now so it won't let you downgrade with S-ON. You can get S-OFF if you need to flash GB for some reason, or use this Sprint ICS RUU instead.
ramjet73
ramjet73 said:
That's a GB RUU and you are on the Sprint ICS build now so it won't let you downgrade with S-ON. You can get S-OFF if you need to flash GB for some reason, or use this instead.
ramjet73
Click to expand...
Click to collapse
I just tried that RUU and I got Error 132 after it was erasing my data
lxbeale said:
I just tried that RUU and I got Error 132 after it was erasing my data
Click to expand...
Click to collapse
Did your relock your bootloader before trying to flash it?
Here's a post with some troubleshooting info for flashing an RUU.
ramjet73
ramjet73 said:
Did your relock your bootloader before trying to flash it?
with some troubleshooting info for flashing an RUU.
ramjet73
Click to expand...
Click to collapse
It is relocked and the main version as well as the cid is at the appropriate settings for Sprint. I also tried using a different wire and PC, still getting the same results
lxbeale said:
It is relocked and the main version as well as the cid is at the appropriate settings for Sprint. I also tried using a different wire and PC, still getting the same results
Click to expand...
Click to collapse
I kind of lost track of where things stand now. Could you please supply the following information:
1. The heading information (top 3 lines) from your bootloader
2. The RUU you are currently trying to flash and where you got it
3. How you are flashing the RUU and when you get the error
The 132 error is a signature problem that is usually caused by an unlocked bootloader and I don't understand how you are getting it unless the RUU you are flashing is corrupted.
You could try downloading the RUU.exe from here and make sure the MD5 matches.
ramjet73
ramjet73 said:
I kind of lost track of where things stand now. Could you please supply the following information:
1. The heading information (top 3 lines) from your bootloader
2. The RUU you are currently trying to flash and where you got it
3. How you are flashing the RUU and when you get the error
The 132 error is a signature problem that is usually caused by an unlocked bootloader and I don't understand how you are getting it unless the RUU you are flashing is corrupted.
You could try downloading the RUU.exe from and make sure the MD5 matches.
ramjet73
Click to expand...
Click to collapse
Sorry it took me so long to reply, but this is the first three lines:
SHOOTER XC SHIP S-ON RL
HBOOT=1.58.000
RADIO-1.09.00.0706
The RUU that I tried was the one you recommended in the comments and then how I am doing it is having USB Debuging on while in fastboot usb then running the RUU
How did you fix this?
lxbeale said:
Sorry it took me so long to reply, but this is the first three lines:
SHOOTER XC SHIP S-ON RL
HBOOT=1.58.000
RADIO-1.09.00.0706
The RUU that I tried was the one you recommended in the comments and then how I am doing it is having USB Debuging on while in fastboot usb then running the RUU
Click to expand...
Click to collapse
How did you fix this? I have the same issue.
I'm trying to get my 1.58Hboot phone over to S-Off so i can downgrade my hboot easily to try out some more interesting roms. I have the steps and guides to get this done, but it requires me to have a stock rom. i have a stock rooted odex rom but it says it has to be plain stock.
So i feel like i've tried alot of things to try to get this stock rom:
RUU files
PG86IMG.zip files
Which all failed to do anything... is there anyway to get this done easy like maybe just flash something with 4ext?
Any help would be much appreciated, thanks.
akin175 said:
Which all failed to do anything... is there anyway to get this done easy like maybe just flash something with 4ext?
Any help would be much appreciated, thanks.
Click to expand...
Click to collapse
How did they fail? What error messages did you get?
The zip version of the RUU should flash from the bootloader even if you are S-ON.
ramjet73
ramjet73 said:
How did they fail? What error messages did you get?
The zip version of the RUU should flash from the bootloader even if you are S-ON.
ramjet73
Click to expand...
Click to collapse
I don't get any errors on those, my bootloader finds the zip it parses the file then does nothing with it, it just goes back to the main directory screen.
The Ruu.exe file says updating form image 2.89.651.2 to 289.651.2 then it takes my screen to the "HTC" screen and it says "sending" but then gives me ERROR 155 UNKNOWN ERROR
akin175 said:
I don't get any errors on those, my bootloader finds the zip it parses the file then does nothing with it, it just goes back to the main directory screen.
The Ruu.exe file says updating form image 2.89.651.2 to 289.651.2 then it takes my screen to the "HTC" screen and it says "sending" but then gives me ERROR 155 UNKNOWN ERROR
Click to expand...
Click to collapse
Have you relocked your bootloader before attempting to flash the RUU?
Try issuing the following fastboot commands and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
ramjet73 said:
Have you relocked your bootloader before attempting to flash the RUU?
Try issuing the following fastboot commands and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Click to expand...
Click to collapse
No i havn't, i thought it had to be unlocked to flash anything.
I'm not 100% sure where you me to issue these commands, i've only really used ADB to unlock my phone.
akin175 said:
No i havn't, i thought it had to be unlocked to flash anything.
I'm not 100% sure where you me to issue these commands, i've only really used ADB to unlock my phone.
Click to expand...
Click to collapse
You had to use fastboot to flash the unlock token and your custom recovery. It's in the same directory as ADB.
Since you didn't relock your bootloader you could start with Step1 in this guide and it has everything you need to get to S-OFF.
ramjet73
ramjet73 said:
You had to use fastboot to flash the unlock token and your custom recovery. It's in the same directory as ADB.
Since you didn't relock your bootloader you could start with Step1 in this guide and it has everything you need to get to S-OFF.
ramjet73
Click to expand...
Click to collapse
I figured it out while after i posted that and now feel dumb for posting that.
c:\>cd adb
c:\ADB>fastboot getvar cid
cid: SPCS_001
finished. total time: 0.000s
c:\ADB> fastboot getvar mainver
mainver: 2.89.651.2
finished. total time: 0.010s
c:\ADB>
ramjet73 said:
You had to use fastboot to flash the unlock token and your custom recovery. It's in the same directory as ADB.
Since you didn't relock your bootloader you could start with Step1 in this guide and it has everything you need to get to S-OFF.
ramjet73
Click to expand...
Click to collapse
I checked out your link and it's the wire trick way like i wanted to do, so i'll be following it set by step, thank you very much i really appreciate your time .
akin175 said:
cid: SPCS_001
mainver: 2.89.651.2
Click to expand...
Click to collapse
OK, you're good to go.
Just follow the guide and you should be able to get S-OFF.
ramjet73
Hi,
Device: Flyer Wifi 16gb
HBOOT: 6.11.1111
Revolutionary S-OFF
No Root (apparently by Root Checker Basic)
3.2.1 RUU
i followed this guide:
http://forum.xda-developers.com/showpost.php?p=19339909&postcount=1
to regain S-ON and standard recovery. Unfortunately it didnt work, I installed the RUU, it boots and works fine but if I send the devices to bootloader via ADB it lands back in Revolutionary. The guide was completed without errors.
So I am currently on RUU but with S-OFF and Revolutionary and I would like to get S-ON and standard recovery.
I found several other guides, but I cant see what puts them above the mentioned one and therefore I prefer to ask...
Thank you very much in advance for any help,
P32r
More
For example this:
http://forum.xda-developers.com/showthread.php?t=1257909
just ends in that:
http://forum.xda-developers.com/showpost.php?p=16147471&postcount=77
and that holds for everything I found.
Somebody said I could just use fastboot and send "fastboot oem lock" for the lock and RUU afterwards. But am I right that HBOOT is not replaced by RUU at all? Do I have to downgrade first?
p32r said:
For example this:
http://forum.xda-developers.com/showthread.php?t=1257909
just ends in that:
http://forum.xda-developers.com/showpost.php?p=16147471&postcount=77
and that holds for everything I found.
Somebody said I could just use fastboot and send "fastboot oem lock" for the lock and RUU afterwards. But am I right that HBOOT is not replaced by RUU at all? Do I have to downgrade first?
Click to expand...
Click to collapse
the RUU flash will not write over a S Off Hboot. the procedure you listed in the OP is the only one I know of that will do what you want. Are you sure that when you:
fastboot flash hboot flyer_downgrader.nb0
it was successful?
pic
Thank you for your help!
I attached the output of fastboot and I actually dont think that it flashes correctly but all I saw is "OKAY" and "finished"...
Is the screen supposed to show anything during this flash? Because it stays just the way it is and shows no change in HBOOT or any part of the fastboot screen.
After rebooting it says "HBOOT-6.10.1005" but revolutionary still.
Great Success!
Got it! Works with RUU
RUU_Flyer_HTC_WWE_Wifi_1.36.1114.32_Radio_20.3501.30.089BU_3809.05.04.10_M_release_191235_signed
and NOT with the one I used. With this RUU I did the exact same procedure and succeeded. Now on stock recovery, S-ON and 1.10.0000!
Thank you for the guide, it really does work
Hello all,
I'm Beginner with htc, i have problem with boot loop, i have done lot of search in the internet and i applied many procedures but i couldn't resolve the problem.
My phone is :
HTC EVO 3D GSM
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.02.02
eMMC-boot
Can i have your helps please?
Thank you very much
Best regards,
On hboot 1.53 s-on you can only flash sense based roms. This means ics only, no jelly bean, because jb is based on cyanogenmod. If you have 4ext recovery, go into it, and in the Tools section, activate Smartflash. That way you will not have any more boot loops on ics sense roms, but the rest are still unavailable to you... i suggest you revert to stock ruu, go to unlimited.io and get s-off, then downgrade hboot to 1.49, for everything to work. There are a lot of tutorials around here for that
Sent from my Evo 3D GSM using xda premium
aagrou said:
Hello all,
I'm Beginner with htc, i have problem with boot loop, i have done lot of search in the internet and i applied many procedures but i couldn't resolve the problem.
My phone is :
HTC EVO 3D GSM
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.02.02
eMMC-boot
Can i have your helps please?
Thank you very much
Best regards,
Click to expand...
Click to collapse
What abaout your bootloader is it LOCKED or UNLOCKED ? Do u have custom rom or original stock ICS rom?
Dadovvv said:
What abaout your bootloader is it LOCKED or UNLOCKED ? Do u have custom rom or original stock ICS rom?
Click to expand...
Click to collapse
thank you for your replays,
my phone is unloked, i don't know each rom or ruu i can use i downloaded a lot of rom and ice, i had installed them by 4rex and fasboot but doesn't work.
I can't switch my phone to s-off.
thank you very much for all helps,
best regrades,
I really suggest you to S-OFF and for that, here's a small tutorial: Go to 4EXT, Wipe everything except SD Card. Then reboot into bootloader. In bootloader click the power button to activate fastboot and connect your phone to pc. In a command prompt, while the phone is connected (in hboot fastboot, very important) write "fastboot oem lock". After you have done so, find the RUU file to fit your phone (http://androidfiles.org/ruu/?dir=Shooter search for the one to fit your radios). After the ruu has completed, root your phone again, and then get S-OFF from unlimited.io. Then everything will work nicely
posedatull said:
I really suggest you to S-OFF and for that, here's a small tutorial: Go to 4EXT, Wipe everything except SD Card. Then reboot into bootloader. In bootloader click the power button to activate fastboot and connect your phone to pc. In a command prompt, while the phone is connected (in hboot fastboot, very important) write "fastboot oem lock". After you have done so, find the RUU file to fit your phone (http://androidfiles.org/ruu/?dir=Shooter search for the one to fit your radios). After the ruu has completed, root your phone again, and then get S-OFF from unlimited.io. Then everything will work nicely
Click to expand...
Click to collapse
when the RUU has completed just unlock bootloader again and u are ready to go with wire trick ,,no need to root (root does not require more for wire trick)
Thank you all,
I have done this yesterday but doesn't work for my phone, i have use all ruu.exe that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
Please, can you send me a link for any ruu works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
Dadovvv said:
when the RUU has completed just unlock bootloader again and u are ready to go with wire trick ,,no need to root (root does not require more for wire trick)
Click to expand...
Click to collapse
Thank you all,
I have done this yesterday but doesn't work for my phone, i have use all ruu.exe that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
The ruu that i have used from the ()are:
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_264110_signed.exe
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262715_signed.exe
Please, can you send me a link for any ruu works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
posedatull said:
I really suggest you to S-OFF and for that, here's a small tutorial: Go to 4EXT, Wipe everything except SD Card. Then reboot into bootloader. In bootloader click the power button to activate fastboot and connect your phone to pc. In a command prompt, while the phone is connected (in hboot fastboot, very important) write "fastboot oem lock". After you have done so, find the RUU file to fit your phone (http://androidfiles.org/ruu/?dir=Shooter search for the one to fit your radios). After the ruu has completed, root your phone again, and then get S-OFF from unlimited.io. Then everything will work nicely
Click to expand...
Click to collapse
Thank you all,
I have done this yesterday but doesn't work for my phone, i have use all ruu.exe that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
The ruu that i have used from the ()are:
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Rad io_11.77.3504.00U_11.25.3504.06_M_release_264110_s igned.exe
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262714_sig ned.exe
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio _11.77.3504.00U_11.25.3504.06_M_release_262715_sig ned.exe
Please, can you send me a link for any ruu works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
Thank you, this has been very helpful!
posedatull said:
On hboot 1.53 s-on you can only flash sense based roms. This means ics only, no jelly bean, because jb is based on cyanogenmod. If you have 4ext recovery, go into it, and in the Tools section, activate Smartflash. That way you will not have any more boot loops on ics sense roms, but the rest are still unavailable to you... i suggest you revert to stock ruu, go to unlimited.io and get s-off, then downgrade hboot to 1.49, for everything to work. There are a lot of tutorials around here for that
Sent from my Evo 3D GSM using xda premium
Click to expand...
Click to collapse
aagrou said:
Thank you all,
I have done this yesterday but doesn't work for my phone, i have use all ruu.exe that have the same radios like my phone but it doesn't completed, the ruu.exe show me the error that my phone is non-compatible with this ruu,
Please, can you send me a link for any ruu works with my phone described above,?
Thank you very much for your all collaborations and helps,
Best regards,
Click to expand...
Click to collapse
I think you can enter the fastboot mode in the phone, connect it to your pc, use "fastboot oem readcid", the cid can tell what ruu to choose.
radiowave21 said:
I think you can enter the fastboot mode in the phone, connect it to your pc, use "fastboot oem readcid", the cid can tell what ruu to choose.
Click to expand...
Click to collapse
Hello, my cid: VODAP304:
but i don't no wich ruu work with my phone.
thank you,