Related
The title probably says it all but I'm curious if it's even possible to change the *LOCKED* to *UNLOCKED* after getting S-OFF and flashing the ENG H-Boot?
When I tried to use HTC-Dev, it gave me an error message.
Thoughts?
It is possible. Maybe you didn't see my reply to you in the other post.
The process is the exact same as the one with S-On bootloader. Make sure your identification code is correct and you include the header and the ending
idaggerpwn said:
It is possible. Maybe you didn't see my reply to you in the other post.
The process is the exact same as the one with S-On bootloader. Make sure your identification code is correct and you include the header and the ending
Click to expand...
Click to collapse
I got it. Thanks for the tip man. Guess I had messed something up the first time I tried and it told me the unlock token was bad.
Think I copied the "INFO" parts too. This time it went through smoothly.
I'm now officially ENG S-OFF, HTC Unlocked, and SUPERCID.
Bring it on XDA. I'm ready.
How do you flash the ENG H-Boot?
HuskyHamburger said:
How do you flash the ENG H-Boot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=1018938&d=1335108356
Rename to PH85IMG.zip and place on root of external sd card.
Reboot into bootloader and install it.
dharvey4651 said:
http://forum.xda-developers.com/attachment.php?attachmentid=1018938&d=1335108356
Rename to PH85IMG.zip and place on root of external sd card.
Reboot into bootloader and install it.
Click to expand...
Click to collapse
Thanks man!
Edit: What are the improvements with the ENG-HBoot rather than the Juopunutbear hboot?
HuskyHamburger said:
Thanks man!
Edit: What are the improvements with the ENG-HBoot rather than the Juopunutbear hboot?
Click to expand...
Click to collapse
engineering boot allows for extended adb commands. im curious, why do you feel the need to unlock via htc.dev?
mrmako777 said:
engineering boot allows for extended adb commands. im curious, why do you feel the need to unlock via htc.dev?
Click to expand...
Click to collapse
Just wanted the word "UNLOCKED" instead of "LOCKED".
I know it makes no difference since I have ENG hboot but I wanted it anyway.
Looks better on the bootloader screen
dharvey4651 said:
Just wanted the word "UNLOCKED" instead of "LOCKED".
I know it makes no difference since I have ENG hboot but I wanted it anyway.
Looks better on the bootloader screen
Click to expand...
Click to collapse
LOL fair enough
Not working for me... It seems my phone wont recognize the PH85IMG.zip file on my sd card... I placed it on the card and on the internal storage...
LOCKED
RUBY PVT SHIP S-OFF RL
HBOOT-1.90.0006
e-MMC-boot
Any help would be appreciated!
Thanks!
tagme said:
Not working for me... It seems my phone wont recognize the PH85IMG.zip file on my sd card... I placed it on the card and on the internal storage...
LOCKED
RUBY PVT SHIP S-OFF RL
HBOOT-1.90.0006
e-MMC-boot
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
I re-unlocked the bootloader with the original "root" instructions wich worked well... Kinda weird, I read it wasn't supposed to work... When I'm in hboot, it scans the sdcard for ph85img.zip but it doesn't see it...???
try deleting the "zip" and just rename it PH85IMG
dharvey4651 said:
Just wanted the word "UNLOCKED" instead of "LOCKED".
I know it makes no difference since I have ENG hboot but I wanted it anyway.
Looks better on the bootloader screen
Click to expand...
Click to collapse
That made me laugh because it sounded a bit like me. Sometimes there is really no reason othe than "because I want to."
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
After turning S-OFF and gettin bootloader unlocked, everythings works perfectly:laugh:. But know I have problem with cid. I can't change it when i type
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
nothing happens, and I still have cid: 0202. I can't install any firmware and RUU doesn't work. How to fix it, and make cid: HTC__001 again?
markk99 said:
How to fix it, and make cid: HTC__001 again?
Click to expand...
Click to collapse
Do u really think that this belongs to development?
There is also one more problem I've had before. I can't turn me WiFi on. When I push button to start it won't, and after moment says ERROR.
fixing cid 0202
Here is the problem hboot. Higher hboot than 1.49.0007 cant change cid. if you downgrade your hboot to 1.49.0007 you can.
I changed it in downgrade procces, my hboot was 1.49.1107.
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
Hello ,
I just bought a used DNA. when i'm entered to the bootloader i see the following info :
TAMPEERED (in Gray)
UNLOCKED
SHIP S-ON
HBOOT - 1.33.0001
RADIO 1.00.00.1023_3
My ROM is Supercharged hatka
Build Number : 2.04.605.2
i have root access and my CID is VZW_001 (I used CID getter)
Does it's means that i cant S-OFF my device right now \ Change my CID ?
and one more question - can i change rom ? (if he is on the same Build number)
incident said:
Hello ,
I just bought a used DNA. when i'm entered to the bootloader i see the following info :
TAMPEERED (in Gray)
UNLOCKED
SHIP S-ON
HBOOT - 1.33.0001
RADIO 1.00.00.1023_3
My ROM is Supercharged hatka
Build Number : 2.04.605.2
i have root access and my CID is VZW_001 (I used CID getter)
Does it's means that i cant S-OFF my device right now \ Change my CID ?
and one more question - can i change rom ? (if he is on the same Build number)
Click to expand...
Click to collapse
I believe you need to do this first: http://forum.xda-developers.com/showthread.php?t=2149417
Then, change the CID and then you can S-off your device and change ROM
Someone confirm?:highfive:
Edit: Also, check to see what Kernel you're using
And get GooManager and update your twrp recovery [my suggestion]
UrGuardian999 said:
I believe you need to do this first: http://forum.xda-developers.com/showthread.php?t=2149417
Then, change the CID and then you can S-off your device and change ROM
Someone confirm?:highfive:
Edit: Also, check to see what Kernel you're using
And get GooManager and update your twrp recovery [my suggestion]
Click to expand...
Click to collapse
Hi Mate,
Thanks for the quick response. are you sure that i can S-OFF my device ? (even if i already with 2.04 build ?):fingers-crossed::fingers-crossed::fingers-crossed:
btw . my Kernel is 3.4.10-ga02d2c6 [email protected] #1 SMP PREEMPT
incident said:
Hi Mate,
Thanks for the quick response. are you sure that i can S-OFF my device ? (even if i already with 2.04 build ?):fingers-crossed::fingers-crossed::fingers-crossed:
btw . my Kernel is 3.4.10-ga02d2c6 [email protected] #1 SMP PREEMPT
Click to expand...
Click to collapse
You need to use that first link and remove the OTA [2.04 build] and revert back. Then you can go down the road of s-off'ing your device. As always, follow the directions of each link I posted. I'm sure you can S-off, but you're a few steps away.
I suggest you flash DSB's 3.1.3 Kernel. It's been very stable for me.
Wait for someone else to respond too, but I'm pretty sure this is all that you need to do
I deleted all the relevant APk's of the OTA
I installed the CID-2.APK but it's still shows me VZW_001 :<
can i S-OFF my device without the changing my CID ? (probebly it's will not benefit me a lot..)
btw
Can i change rom or i'm stuck with "hataka" ?
incident said:
I deleted all the relevant APk's of the OTA
I installed the CID-2.APK but it's still shows me VZW_001 :<
can i S-OFF my device without the changing my CID ? (probebly it's will not benefit me a lot..)
btw
Can i change rom or i'm stuck with "hataka" ?
Click to expand...
Click to collapse
I think you need to flash this file to remove it, not just delete related APK's.
As for CID
For this to work [S-off], you must be HTCdev unlocked and have superCID
Click to expand...
Click to collapse
Your CID can't be VZW_001
And of course you can flash another ROM other than Hatka, that's just one of the options
UrGuardian999 said:
I think you need to flash this file to remove it, not just delete related APK's.
As for CID
Your CID can't be VZW_001
And of course you can flash another ROM other than Hatka, that's just one of the options
Click to expand...
Click to collapse
When i said that i deleted those apk h i mean that they removed with this script, sorry about the missunderstanding.
Here is my cid via cid getter .. maybe the cid getter mistake and i need to check with the fastboot command?
Sent from my HTC6435LVW using xda app-developers app
If you see something else (e.g. VZW__001) then reboot normally and try the process again.
Click to expand...
Click to collapse
If it didn't change, I guess try a couple more times and use the fastboot command
Go on your computer and do the command to read the cid. Cid getter is buggy and shows the vzw one no matter what.
Sent from my HTC6435LVW using xda app-developers app
BOOOM !!!
got to my laptop at home, did fast boot getvar cid :
CID : 222222222
should i now do the S-OFF guide without any problems ??:fingers-crossed::fingers-crossed:
Bigandrewgold said:
Go on your computer and do the command to read the cid. Cid getter is buggy and shows the vzw one no matter what.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Now that you mentioned it in the other thread, it won't matter anyways because he also has the OTA.
@Incident, you're going to have to wait till they fix the OTA issue before you can press on.
Correction:
For this to work, you must be HTCdev unlocked and have superCID (custom recovery/root is optional), see the thread below for help and information regarding obtaining superCID, unlock, etc. If you have taken the OTA for the DNA (sw version 2.xx) without FIRST obtaining superCID, there is no superCID nor s-off method for you currently. Note this thread is provided for convenience only
Looks like you can do S-off, but do it at your own risk.
UrGuardian999 said:
Now that you mentioned it in the other thread, it won't matter anyways because he also has the OTA.
@Incident, you're going to have to wait till they fix the OTA issue before you can press on.
Correction:
For this to work, you must be HTCdev unlocked and have superCID (custom recovery/root is optional), see the thread below for help and information regarding obtaining superCID, unlock, etc. If you have taken the OTA for the DNA (sw version 2.xx) without FIRST obtaining superCID, there is no superCID nor s-off method for you currently. Note this thread is provided for convenience only
Looks like you can do S-off, but do it at your own risk.
Click to expand...
Click to collapse
I think that CID-GETTER app is buggy , look my result in the cmd :
c:\ADB + Fastboot + Drivers>fastboot getvar cid
cid: 22222222
finished. total time: 0.000s
so i can do the S-OFF "without" worries ?
incident said:
I think that CID-GETTER app is buggy , look my result in the cmd :
c:\ADB + Fastboot + Drivers>fastboot getvar cid
cid: 22222222
finished. total time: 0.000s
so i can do the S-OFF "without" worries ?
Click to expand...
Click to collapse
Yes, you can s off without any problems.
Sent from my HTC6435LVW using xda app-developers app
incident said:
I think that CID-GETTER app is buggy , look my result in the cmd :
c:\ADB + Fastboot + Drivers>fastboot getvar cid
cid: 22222222
finished. total time: 0.000s
so i can do the S-OFF "without" worries ?
Click to expand...
Click to collapse
Agree, it says in the S-off thead that as long as you're unlocked and have CID you should be good to go