This is what my boot loader looks like
{
"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"
}
I ran s-off with the htc unlocker tool. Then flashed newtoroots sense 4 rom and had to install sense 4 boot image for it to boot. Then I installed venom rom. When I try to flash my nandroid back up to stock ics it won't boot. When I try to flash a stock ruu it says no image or wrong image found. I was told I need to relock? Does that mean no longer be s-off? What does locking and relocking mean? Can someone explain this to me or help me get back to stock? I named the file PH98IMg.zip, let it load in fast boot it does the no image or wrong image thing. I made sure it doesn't have .zip.zip So please someone explain to me the relocking and s-off thing. So if i'm s-off how do I relock and keep s-off? I just want to be able to flash the stock ruu. Thanks.
trigun123478 said:
This is what my boot loader looks like
I ran s-off with the htc unlocker tool. Then flashed newtoroots sense 4 rom and had to install sense 4 boot image for it to boot. Then I installed venom rom. When I try to flash my nandroid back up to stock ics it won't boot. When I try to flash a stock ruu it says no image or wrong image found. I was told I need to relock? Does that mean no longer be s-off? What does locking and relocking mean? Can someone explain this to me or help me get back to stock? I named the file PH98IMg.zip, let it load in fast boot it does the no image or wrong image thing. I made sure it doesn't have .zip.zip So please someone explain to me the relocking and s-off thing. So if i'm s-off how do I relock and keep s-off? I just want to be able to flash the stock ruu. Thanks.
Click to expand...
Click to collapse
HTC unlock is NOT s-off. To get s-off you have to go to unlimited.io and download the juopunutbear program for the rezound.
To run an ruu you must be locked boot loader. To relock to open fastboot and type "fastboot oem lock" then use the PH98IMG.zip.
If you use jbear to get s-off, you won't have to worry about locking and unlocking as you will stay locked but be able to flash all the stuff as unlocked.
Sent from my Galaxy Nexus
AshtonTS said:
HTC unlock is NOT s-off. To get s-off you have to go to unlimited.io and download the juopunutbear program for the rezound.
To run an ruu you must be locked boot loader. To relock to open fastboot and type "fastboot oem lock" then use the PH98IMG.zip.
If you use jbear to get s-off, you won't have to worry about locking and unlocking as you will stay locked but be able to flash all the stuff as unlocked.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you for clearing that up. Now I know I just fast boot oem lock and run it. Thank you so much.
AshtonTS said:
HTC unlock is NOT s-off. To get s-off you have to go to unlimited.io and download the juopunutbear program for the rezound.
To run an ruu you must be locked boot loader. To relock to open fastboot and type "fastboot oem lock" then use the PH98IMG.zip.
If you use jbear to get s-off, you won't have to worry about locking and unlocking as you will stay locked but be able to flash all the stuff as unlocked.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Does that also mean I can't flash a stock rooted ruu?
trigun123478 said:
Does that also mean I can't flash a stock rooted ruu?
Click to expand...
Click to collapse
You need s-off to go backwards in version numbers.
Apparently HTC and Verizon only want you to make progress, even if there are bumps in the road to progress.
btw, a stock ruu is never rooted.
So, first run the stock ruu, and then root it.
also, a Rom is not an ruu.
A Rom might be based on a stock ruu, but a Rom does not include everything that is in an ruu. A Rom is usually the system partition and the boot/kernel partition, both are modified and can no longer be referred to as being stock. An ruu includes, hboot, boot, system, radios, etc..
I think some ROMs are referred to as stock only because the developer started by modifying files from a stock REZOUND ruu, as opposed to starting with files from an ruu made by HTC for a totally different phone like the one-x for example. No Rom is stock, because even one modification to files from an ruu means it is no longer stock. it is a misnomer to refer to any Rom as being stock. Some roms might have fewer modifications and be closer to stock.
Stock usually also means all phone functions are working, where with a Rom one needs to read carefully to see what phone functions do not work with the Rom, and to consider how important the broken functions are to you.
regards,
Howard
ps I am writing all this because your quoted statement doesn't make sense, and I am having trouble sleeping this evening with nothing else to do.
I see everyone talking about fastboot, is that a program i should still have on my computer from when I rooted? It vaguely sounds familiar but I cant remember...
trizzypballr said:
I see everyone talking about fastboot, is that a program i should still have on my computer from when I rooted? It vaguely sounds familiar but I cant remember...
Click to expand...
Click to collapse
It's a .bat file that allows executing commands in the command prompt. When you rooted you did have to use fastboot to get the identifier token and flash the unlock_code.bin
Sent from my Galaxy Nexus
after you s-off never htcdev unlock. use a modified hboot instead
for convience reasons if you ever have to turn it back to complete stock.
Related
Unlock Boatloader is officially launched
This is not S-OFF
{
"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"
}
http://www.htcdev.com/bootloader/unlock-instructions
can anyone confirm this actually gives you S-OFF?
This unlocks my evo 3D but I still have S-ON.
No mention of S-OFF/S-ON. Only unlocking the bootloader (which it does successfully).
If I remember correctly HTC had said this was to be a 2 part process. Could part 2 be here?
Sent from my PG86100 using xda premium
cordell12 said:
If I remember correctly HTC had said this was to be a 2 part process. Could part 2 be here?
Click to expand...
Click to collapse
I'm not sure what the OP was referring to since the bootloader unlocker was open a few days ago. I unlocked my bootloader then and when I followed the link today it sent me to the exact same page.
Like I said, there is no mention of S-ON or S-OFF anywhere. Perhaps the OP can clarify or correct.
Also, I went ahead and went through the process again and it was identical with no S-OFF.
That is Lame, HTC knew exactly what we were talking about back when this all started. To "unlock" the bootloader and keep boot.img locked and S on is a major Fail on HTC!
Unless they come through with part 2...
Sent from my PG86100 using xda premium
I believe part one was the software update that allowed the unlock to be done, part two would be the unlock process they currently do on their website.
foss said:
I'm not sure what the OP was referring to since the bootloader unlocker was open a few days ago. I unlocked my bootloader then and when I followed the link today it sent me to the exact same page.
Like I said, there is no mention of S-ON or S-OFF anywhere. Perhaps the OP can clarify or correct.
Also, I went ahead and went through the process again and it was identical with no S-OFF.
Click to expand...
Click to collapse
I thought S-OFF/S-ON didn't matter with an "unlocked" bootloader. Doesn't unlocking the bootloader essentially remove the signature check, which without a signature check in place it doesnt matter if S is ON of OFF.
I can flash ROMs fine but I thought I couldn't flash a new radio because all of the tutorials state that I need S-OFF to flash radios. No?
No S off no Kernels
mlin said:
I thought S-OFF/S-ON didn't matter with an "unlocked" bootloader. Doesn't unlocking the bootloader essentially remove the signature check, which without a signature check in place it doesnt matter if S is ON of OFF.
Click to expand...
Click to collapse
They unlocked the Sytem and Data partition only with there unlock method. There unlock method does not in any way touch the S-Flag... So if you have s-off you will keep it, if you have s-on you are screwed and will NEVER get s-off unless revolutionary (or the like) do this for us again. I do understand that they may be looking at reverting the 1.5hboo to 1.4 then in turn allow you to use the there tool to obtain S-OFF.
If they would just unlock the boot partition all would be well regardless of S-Flag. Those bastards. So in essence you can flash a custom ROM or even install SU (whatever mods you want) but you wont be flashing a new kernel.
Luckily I had S-OFF and decided to experiment with this and my S-OFF remained and I can flash as I choose.
Steve0007 said:
Unlock Boatloader is officially launched
Click to expand...
Click to collapse
excuse me if im wrong, but isnt this the same thing thats been posted all around here for the past 2 weeks now?
bk718 said:
excuse me if im wrong, but isnt this the same thing thats been posted all around here for the past 2 weeks now?
Click to expand...
Click to collapse
Yep! Seems to be to me.
bk718 said:
excuse me if im wrong, but isnt this the same thing thats been posted all around here for the past 2 weeks now?
Click to expand...
Click to collapse
Sure is!
I wanna add that kernels CAN be flashed with this HTC method. They MUST be flashed with Fastboot though.
So by unlocking the bootloader can you us one of this phones with any service provider? For example I want the EVO 3D but I have Verizon
Sent from my ADR6300 using XDA App
People have been flashing 2.3.4 kernels with a modified ramdisk using fastboot (not recovery) from what I've read. I think people are too quick to judge HTC. They did what they said they would do. I don't think half of the people here even really know the intricacies of unlocked bootloaders and s-off (I certainly don't ). Does s-off even mean anything on non-HTC phones?
I remember people saying how easy it would be to get 'root' since we had an ENG bootloader. They acted like it was a done deal. It certainly took longer than they made it sound like it would and I don't know if alpharev even used the ENG bootloader to get s-off.
cordell12 said:
Sure is!
I wanna add that kernels CAN be flashed with this HTC method. They MUST be flashed with Fastboot though.
Click to expand...
Click to collapse
Are you sure is not Soff before the HTC Method?
mwalt2 said:
People have been flashing 2.3.4 kernels with a modified ramdisk using fastboot (not recovery) from what I've read. I think people are too quick to judge HTC. They did what they said they would do. I don't think half of the people here even really know the intricacies of unlocked bootloaders and s-off (I certainly don't ). Does s-off even mean anything on non-HTC phones?
Click to expand...
Click to collapse
Are you sure they are not S-OFF?
Can you please provide the fastboot command to do this? As well, The people that are flashing the modified kernels like on my ROM using freeza kernel are currently S-OFF if you are S-OFF you can flash modded kernel with hboot 1.5. If you are S-On you cannot. But since you two both say its possible can you please provide a citation or some other sort of proof. I would love to investigate this further! This means a whole new ball game.
EDIT: And yes, I do understand the intricacies of kernels, ROMS, eMMC partitions, etc. I am no expert like the guys at revolutionary or anything even close but I do understand.
And to answer your question about S-OFF on other devices. No such thing. I believe this is just an HTC thing. Im sure other manufactures have there own version of this but I only play with HTC.
I did do some ROM and kernel work on some LG stuff and they did not have any real protection at all. Apply ROOT and flash recovery, that was it. So simple, so easy.
scrosler said:
Are you sure is not Soff before the HTC Method?
Are you sure they are not S-OFF?
Can you please provide the fastboot command to do this? As well, The people that are flashing the modified kernels like on my ROM using freeza kernel are currently S-OFF if you are S-OFF you can flash modded kernel with hboot 1.5. If you are S-On you cannot. But since you two both say its possible can you please provide a citation or some other sort of proof. I would love to investigate this further! This means a whole new ball game.
EDIT: And yes, I do understand the intricacies of kernels, ROMS, eMMC partitions, etc. I am no expert like the guys at revolutionary or anything even close but I do understand.
And to answer your question about S-OFF on other devices. No such thing. I believe this is just an HTC thing. Im sure other manufactures have there own version of this but I only play with HTC.
I did do some ROM and kernel work on some LG stuff and they did not have any real protection at all. Apply ROOT and flash recovery, that was it. So simple, so easy.
Click to expand...
Click to collapse
I think it's fastboot as in using the pg86img.zip. I've just read about it in the general forum and can't test anything since I am s-off.
http://forum.xda-developers.com/showpost.php?p=17101607&postcount=264
mwalt2 said:
I think it's fastboot as in using the pg86img.zip. I've just read about it in the general forum and can't test anything since I am s-off.
http://forum.xda-developers.com/showpost.php?p=17101607&postcount=264
Click to expand...
Click to collapse
I am currently s-on htc unlock method. I have been pulling the boot.img out of the room zip then booting phone into fastboot. With boot.img in same dir as fastboot I use the command fastboot flash boot boot.img. After successful I use the volume buttons to get into recovery and flash the rom. Using md5sum I have tested the kernel partition is changed.
Sent from my PG86100 using Tapatalk
Azrael.arach said:
I am currently s-on htc unlock method. I have been pulling the boot.img out of the room zip then booting phone into fastboot. With boot.img in same dir as fastboot I use the command fastboot flash boot boot.img. After successful I use the volume buttons to get into recovery and flash the rom. Using md5sum I have tested the kernel partition is changed.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
NO ****????
Try this then.... FLash a ROM based on 2.3.3 then flash silverneedle 1.0, overclock and tell me if that works? If you can... If not its cool.
Hi,
I'm stuck in this situation with my htc evo view 4g device.
{
"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"
}
everytime I try to reboot, or enter recovery, or factory reset it just hangs at this screen:
I try to flash this stock rom
RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed
(via both RUU on my pc and goldcard with PG41IMG.zip), it was flashed flawlessly, but when finished it hangs in that "htc" screen.
I tried to s-off by revolutionary but I can not access the android working screen so that can not enable usb debugging mode, on the pc it just shows
waiting for device ....
Click to expand...
Click to collapse
I tried to unlock the bootloader via htcdev (I know my view 4g isn't in the supported list yet, but at least fastboot should read its info, but I was wrong). At step 8, it shows:
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
It still boots in to fastboot mode,and I could see that it's s-on, hboot is 1.13. Now I want to make it s-off or unlock the bootloader in order to flash a custom rom.
Can some one please help me with this ?
Thanks a lot,
Medkid
I tried to unlock the htc view's bootloader by htcdev, at steps 8 it shows me this
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
can you help ? plz
what were you trying to do when you got into this situation and did you run the ruu more than once?
mcord11758 said:
what were you trying to do when you got into this situation and did you run the ruu more than once?
Click to expand...
Click to collapse
Upload the logs from c:\ruu_log
yes, I try to run RUU about 10 times, and It always runs till the end, but after that my device just hangs at htc screen
mcord11758 said:
what were you trying to do when you got into this situation and did you run the ruu more than once?
Click to expand...
Click to collapse
I don't know what happened to my evo view, I didn't s-off it before. My brother borrowed it and when he gave it back to me, it was just in that situation, hung at htc screen. So I tried to flash another stock rom (actually , it's the rom running in my device) , but I have no luck to bring it back
Are you sure you're using the 1.22.651.1 RUU?
The reason for asking is that the RUU process is detecting that as the version-main on your device but is then saying there is a version check failure which would indicate that that is not the RUU you are using.
I tried the RUU in the first post, also another sprint express RUU 1.18 with no success bcoz of a bootloader error. I download these 2 roms from this thread
http://forum.xda-developers.com/showthread.php?t=1062184
You must use the 1.22.651.1 ROM, can you run that again and collect the RUU log for that version.
revolutionary root
medkid said:
I've a htc evo view 4g device. Now, it's stuck in the semibrick circumstance i think. It still boots in to fastboot mode,and I could see that it's s-on, hboot is 1.13. Now I want to make it s-off or unlock the bootloader in order to flash a custom rom. I tried the stock rom RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.05 31_NV_2.28_SPCS_release_198141_signed , it did flash but when it reboots it just hangs up at "htc" white screen.
I tried htcdev to unlock the bootloader but they do not support View 4g yet.
I tried revolution pre 0.4 without any luck because it asks for the device to enter the working screen. The tool only shows "wating device..."
Can some one please help me with this ?
Thanks a lot,
Medkid
Click to expand...
Click to collapse
I used the same method as I did on the Evo 3D for my HTC view tablet and it works My view is rooted hope this helps in anyway
dlo227 said:
I used the same method as I did on the Evo 3D for my HTC view tablet and it works My view is rooted hope this helps in anyway
Click to expand...
Click to collapse
thanks for your answer. But in order to make revolutionary to work, you have to access android working screen to enable the "usb debugging mode", if not, there is no luck. htcdev tool does not ask for this, everything is working on the fastboot mode. Unfortunately, somehow fastboot.exe couldn't read my device info in the step 8.
@globatron, I'll try to reflash it and upload the log. Thanks so much for joining me
Try pulling the rom.zip out of the 1.22 ruu.
Rename the zip PG41IMG.zip (.zip is the extension not part of the name, some people actually make that mistake).
Place the PGxx.zip in the root of an sdcard and place the card in the device.
Boot the device into bootloader/fastboot and let it read and hopefully it should install and get you back to a running state.
I find running ruu's can most times be a pain than a saviour.
lovethyEVO said:
Try pulling the rom.zip out of the 1.22 ruu.
Rename the zip PG41IMG.zip (.zip is the extension not part of the name, some people actually make that mistake).
Place the PGxx.zip in the root of an sdcard and place the card in the device.
Boot the device into bootloader/fastboot and let it read and hopefully it should install and get you back to a running state.
I find running ruu's can most times be a pain than a saviour.
Click to expand...
Click to collapse
thanks for your advice, I did try it that way with no success. let me make thing clearer in the first post.....
Run the RUU again as I said, with the version I specified. I need to see a log that is definitely for that version.
Sorry for the delay, it seems that the main battery is low, I can't run the RUU right now. It is charging. Sorry for that
when you have enough power to do this, delete all the old log files before running the RUU so only the ones from this run are included.
okay, here it is the log file
ok, that RUU was entirely successful. Does it boot now or is it still the same?
It's still the same, hangs at htc screen
try removing the sdcard and a factory reset (both together) then see if it will boot with the card still removed. If not take it in for repair telling sprint that you tried to take an OTA update then this happened.
was bored while trying to fix my kernel issue, so I copied the jpbear style for unlocked hboots. This will work just like the jpbear hboots, meaning fastboot flash is re-enabled without unlocking on HTCDev. I think it also enables fastboot extended commands but I'm not sure. Thanks to JuopunutBear for the original unlocked hboot. Note: when they put up their official one, I will take this down. I have tested it and it should not brick your phone, but the standard disclaimer applies as you are modifying your bootloader.
https://dl.dropbox.com/u/15902163/PH98IMG_hboot_2.27_unlocked.zip
MD5: 1109A13D4F33628BD1B53160FE42450E
Good work!
con247 said:
Do not download this until an md5 is posted!
Click to expand...
Click to collapse
Good call, save a few unnecessary bricks from being made
Sent from my ADR6425LVW using xda app-developers app
posted MD5.
Also, posted as a PH98IMG. I realized... its kinda pointless fastboot flashing something when fastboot flash is unlocked
delete
Downloaded, I'll try later......
Downloaded, I'll try later......About to go to sleep. Thanks for this!!
Screenshots after flash....
Well...couldn't go to sleep...flashed it.
{
"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"
}
As you can see......says vinylfreak89 at top....
Thanks
=========
wow...Tapatalk uploads big pictures....lol
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.2.7
i was thinking of tagging it with the usual jpbear tag but that would get way too confusing if/when they finally release one.
Notice it doesn't say "Locked" anywhere....
vinylfreak89 said:
i was thinking of tagging it with the usual jpbear tag but that would get way too confusing if/when they finally release one.
Click to expand...
Click to collapse
============
Notice it doesn't say "Locked" anywhere....did you edit that out?
actually it would say *** UNLOCKED *** if I didn't edit it. Apparently the changes this makes makes the phone think it was unlocked. I just edited the *** UNLOCKED *** text to **vinylfreak89**. Jpbear just edits it to =Juopuntbear=
Yep...just did a couple of quick flashbacks....
Yep...just did a couple of quick flashbacks....jBear2.25 and Stock2.27 and looked. Back on yours now...lol It's amazing...the flashing, etc. was pretty scary a few months back. Can do it all pretty quick now. I already had put the flashable zip for the stock 2.27 together a few days back. I do have a pretty quick learning curve...I have been modding phones since the Moto Razor flip phones, WM5,WM6,WM6.5 and now the Androids.
---------- Post added at 03:01 AM ---------- Previous post was at 02:53 AM ----------
What did you used to edit the nbo file? I have opened up copies with wordpad...just to see what was in it. Parts are readable....lol.
So, I suspect the primary advantage of this hboot, is that should one brick his phone and try and return it to Verizon, then Verizon will not suspect a thing because it will not show UNLOCKED or TAMPERED?
Instead Verizon will see "vinylfreaq89" and be convinced the phone has not been tampered with?
I suppose this might work with some Verizon employees who are high school dropouts.
Hihi lol
Great work, appreciate it.
regards
HowardZ said:
So, I suspect the primary advantage of this hboot, is that should one brick his phone and try and return it to Verizon, then Verizon will not suspect a thing because it will not show UNLOCKED or TAMPERED?
Instead Verizon will see "vinylfreaq89" and be convinced the phone has not been tampered with?
I suppose this might work with some Verizon employees who are high school dropouts.
Hihi lol
Great work, appreciate it.
regards
Click to expand...
Click to collapse
It would be really neat if you could make it say "locked" as if it never had been unlocked or tampered. That would help anyone needing Verizon service.
motenak said:
It would be really neat if you could make it say "locked" as if it never had been unlocked or tampered. That would help anyone needing Verizon service.
Click to expand...
Click to collapse
S-off on gingerbread came with an engineering hboot, which did exactly that. it would display "LOCKED" and act as if it was unlocked. There was an "ENG" indicator on another line that it was an engineering hboot. This hboot was leaked. and thus was signed by HTC. This hboot also was capable of additional fastboot commands, but no developers are making use of them to my knowledge.
It seems the sole purpose of these replacement hboots is to fool Verizon. I don't think they accomplish this mission very well.
Except for the GB ENG hboot, the other replacement hboots are not signed by HTC. This carries the risk that if the phone is given the command to becomr S-ON, then the phone becomes an unrecoverable brick. Perhaps some new verizon ota or ruu will try to turn s-on back on, and phones will become bricks.
Anyway, I am using the stock version if this hboot. and am wondering what advantages there might be to using this modified hboot?
I think sometimes smart talented developers rush into doing modifications before considering if it is really a good idea?
so... is this a patched hboot,or is it just a copy and hex edit of your unlocked hboot?
if its the latter... have yall that have flashed it,have you flashed back to the stock 2.27 hboot to make sure you are locked still?
id hate to see this hboot change the lock status flag on those devices that folks care.
the ICS JPbear hboots do work just fine in place of 2.25 and 2.27,so if this is messing with the lock status flag one can easily just use one of them to retain locked status.
im not criticizing,just curious. if it is a copied unlocked stock hboot,yall that flashed it have some big cast iron balls id have been afraid an unlocked stock hboot would have had some phone specific info that could have ended badly
if one can really flash between locked and unlocked by simply flashing an unlocked hboot,thats pretty interesting... i wouldn t have thot it would work out that way
Flashed back to Stock 2.27.........
Flashed back to Stock 2.27.........again. Still "LOCKED". Did this right after the screenshots I posted. Since I tried this "Modded hBoot have flashed Stock2.27,then Jbear2.25, then This2.27again. When Stock says "LOCKED". With others says "Jbear or vinyl"......Have had no problems.
manbat said:
Flashed back to Stock 2.27.........again. Still "LOCKED". Did this right after the screenshots I posted. Since I tried this "Modded hBoot have flashed Stock2.27,then Jbear2.25, then This2.27again. When Stock says "LOCKED". With others says "Jbear or vinyl"......Have had no problems.
Click to expand...
Click to collapse
thanks for the info. if youd said that earlier in the thread,my apologies,i hadnt seen it.
No problem...
No problem...I thought about most of your points before I flashed this one the first time...lol. Took a deep breath and did it... .
Hmmm...can I make a request for custom verbiage?
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Hate to be a thorn, but noticed form the pick on page 1, there is not recovery option listed. Or are my glasses foggy?
Hey guys I need a bit of help.
Im stuck running the RUU. Specifically the part right after it says "Erasing User Data" where it says "Sending"
Yes the sending part. The blue bar never does anything and the phone stays in the black screen with the words "HTC" in green.
Once I get the error I can disconnect and do a battery pull and the phone turns right back on.
I have my adb drivers and i have HTC Sync installed.
I tried running the RUU from both the C drive and my documents and the same results every time.
If anyone has a fix and knows what im doing wrong I will appreciate your help.
ThKs
Which RUU are you trying to flash? I see in your sig that you've got the Virgin Mobile Evo V so I'm assuming it's the 1.13.652.2 version.
When I've flashed the Sprint RUU.exe versions, it's hung a few times at the "waiting for bootloader" stage, especially when I flash it S-OFF with a custom bootloader installed. That is usually resolved by cancelling the Windows app and restarting it.
I've also found that starting the RUU.exe with the phone in the "fastboot USB" mode in the bootloader helps, but it sounds like you are past the point where that would make a difference.
The only thing I can suggest is to restart it with your phone in the bootloader, and give it plenty of time to complete. Normally it takes only about 10 minutes, but I'd give it at least 15.
If all else fails, you may need to get the phone serviced. You didn't say why you are flashing the RUU but if a partition got messed up or you have some type of hardware problem it may never flash successfully.
ramjet73
Yeah I have a Virgin Mobile RUU and I'm flashing it back to stock to reroot it so I can get s-off . I spoke to one of the members of unlimited.io and he said that the s-off tool will fail unless I'm on a stock ruu rom. I have the bootloader unlocked and im on a stock deodex rom but he tells me to ruu back to stock root and then use the tool. Other than that my phone is fine. I'm just trying to change my hboot and a few other things so that I can fix the signal loss problem that the Evo 3D for VM has.
Oh and yeah I've tried fastboot and bootloader. Actually that's the only way I get past the detection. When the ruu says that its rebooting the phone it fails. I have to have it already on fastboot or bootloader
Sent from my HTCEVOV4G using xda premium
roketteere said:
I have the bootloader unlocked...
Click to expand...
Click to collapse
If you are currently S-ON, your bootloader needs to locked to flash the RUU.exe successfully. You can do that with the "fastboot oem lock" command.
The JuopunutBear wire trick requires that you are HTC unlocked, so you will have to unlock again after flashing the RUU but can use the same unlock token as the first time.
ramjet73
ramjet73 said:
If you are currently S-ON, your bootloader needs to locked to flash the RUU.exe successfully. You can do that with the "fastboot oem lock" command.
The JuopunutBear wire trick requires that you are HTC unlocked, so you will have to unlock again after flashing the RUU but can use the same unlock token as the first time.
ramjet73
Click to expand...
Click to collapse
ok thank you I will post my results.
By the way here are two screen shots of what it looks like.
{
"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"
}
Thank you!
It work like a charm right after relocking the bootloader.
Now to reroot, unlock bootloader, and finally s-off
roketteere said:
Yeah I have a Virgin Mobile RUU and I'm flashing it back to stock to reroot it so I can get s-off . I spoke to one of the members of unlimited.io and he said that the s-off tool will fail unless I'm on a stock ruu rom. I have the bootloader unlocked and im on a stock deodex rom but he tells me to ruu back to stock root and then use the tool. Other than that my phone is fine. I'm just trying to change my hboot and a few other things so that I can fix the signal loss problem that the Evo 3D for VM has.
Oh and yeah I've tried fastboot and bootloader. Actually that's the only way I get past the detection. When the ruu says that its rebooting the phone it fails. I have to have it already on fastboot or bootloader
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Not true that you must be on stock. I was running meanrom 2.5 when I s-offed
Well it didn't work for me with 3 different roms so I asked for support on their site. That was the response that I got. Now im s-off, boot on eng, and rooted running harmonia rom.
I also changed pri and prl as suggested and now my signal is perfect no calling or texting problems.
Sent from my HTCEVOV4G using xda premium
Hello guys,
For over 24hours I have been working with my EMEA EVO3d to install a custom JB ROM. I have had lots of trouble and it seems that it was because of absence of my knowledge about this phone&CWM and Security ON/OFF
Anyway, after those long 24hour period, I have learned many things but there is a big problem, I can not boot my phone to a working Android, not even ICS ones. I am having boot loops whatever ROM I install. (tried miui original, ParanoidAndroid, LeeDroid ...) After installing ROM's with CWM, i did flashing boot.img from the zip file.
Current information about my phone :
1. Unlocked via htcdev way.
2. S-ON
3. ClockWorkMod 5.8.0.2 Touch
All of those are working flawlesly, i can run into FastBoot, CWM Recovery to install zip.
After struggling a real 12hours of work, I have an idea, I am at HBoot 1.53.007 and it is causing those boot loops. As I can not boot a ROM I am forced to use brick and wire methods but I dont feel doing that is safe for me. Also there is a cover in the back off my phone that i can not remove to use wire on one of places (not the metal one over SDCard)
So what I am looking for is a working ROM with HBoot 1.53.007, I guess I can do S-OFF with software (for example ext4)
By the way, I have got fastboot, adb, files, I can get into FASTBOOT USB screen bla bla.
Hope someone can help me so that i can get back my phone
Thanks
erkanea said:
Hello guys,
For over 24hours I have been working with my EMEA EVO3d to install a custom JB ROM. I have had lots of trouble and it seems that it was because of absence of my knowledge about this phone&CWM and Security ON/OFF
Anyway, after those long 24hour period, I have learned many things but there is a big problem, I can not boot my phone to a working Android, not even ICS ones. I am having boot loops whatever ROM I install. (tried miui original, ParanoidAndroid, LeeDroid ...) After installing ROM's with CWM, i did flashing boot.img from the zip file.
Current information about my phone :
1. Unlocked via htcdev way.
2. S-ON
3. ClockWorkMod 5.8.0.2 Touch
All of those are working flawlesly, i can run into FastBoot, CWM Recovery to install zip.
After struggling a real 12hours of work, I have an idea, I am at HBoot 1.53.007 and it is causing those boot loops. As I can not boot a ROM I am forced to use brick and wire methods but I dont feel doing that is safe for me. Also there is a cover in the back off my phone that i can not remove to use wire on one of places (not the metal one over SDCard)
So what I am looking for is a working ROM with HBoot 1.53.007, I guess I can do S-OFF with software (for example ext4)
By the way, I have got fastboot, adb, files, I can get into FASTBOOT USB screen bla bla.
Hope someone can help me so that i can get back my phone
Thanks
Click to expand...
Click to collapse
Yes, you have problems because you are on 1.53.0007. I had them too. But, I realized that I didn't see that anyone bricked their phone using "wire-trick", so I said to myself "Fu*k it, I'm gonna try it". So, I found thread, and followed what it says. Now, I flash ROMs on daily base, and don't have any problems with my phone..Here is THREAD with pictures (there were no pictures when I s-offed my phone) (Tip: First of all, read whole thread, so you can find if everything is prepared for s-off..It's not hard)
What do you mean "cover"..One use "wire-trick" with metal over SIM card and PIN like one on the picture:
Taken from www.unlimited.io
{
"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"
}
today i have realized that, when i was working with some ROM's, somehow my phone USB debugging disabled. So, every way of disabling security is kinda impossible including easiest way on that thread.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
flashing jb_hboot throws error
"FAILED (remote: 99 unknown fail)"
i think my phone is software bricked but couldnt found a way of unbricking. Tried shipped roms too.
Any help will be appriciated.
Just relock your bootloader, then install officialy ics ruu file with pc..and boot normaly. After that u can unlock bootloader,install recovery, do wire trick,install rom.
Sent from my HTC EVO 3D X515m using xda app-developers app
Dadovvv said:
Just relock your bootloader, then install officialy ics ruu file with pc..and boot normaly. After that u can unlock bootloader,install recovery, do wire trick,install rom.
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
even after installing stock rom my phone doesnt boot, either stays at boot HTC Logo, or reboot loops.
I have s-on hboot 1.53.0007
All roms works fine for me, i am now on VIPER3d sense 4.1 Remember, u must flash 4ext recovery touch to avoid kernel problems. So u dont need s-off
Bazyl93 said:
I have s-on hboot 1.53.0007
All roms works fine for me, i am now on VIPER3d sense 4.1 Remember, u must flash 4ext recovery touch to avoid kernel problems. So u dont need s-off
Click to expand...
Click to collapse
is there anyway of installing 4ext if you dont have any working rom? i mean flashing 4ext recovery from fastboot
SOLVED
problem solved, here is how :
found somewhere yoda's rom v6. flashed it via open recovery, flashed boot.img too. after reboot phone was stuck at htc logo once again. somehow i decided to put phone in AC charce since it was around %10. when the red light went on i thought "what is going on, this is new" and pressed power just for a second. and viola it was asking me to select a language.
anyway, after it i decided to do s-off via jounapator, phone gone again because of low battery. done everything from the first step to install yoda v6. without AC charge it is not working. I am serious.
PUT YOUR PHONE INTO AC CHARGE AND PRESS POWER MOMENTERALY.
I cant believe it but problem solved by AC charge, not USB.
Thanks all for helping.
Bazyl93 said:
I have s-on hboot 1.53.0007
All roms works fine for me, i am now on VIPER3d sense 4.1 Remember, u must flash 4ext recovery touch to avoid kernel problems. So u dont need s-off
Click to expand...
Click to collapse
can i flash cyanogenmod by 4ext with my s-on and hboot 1.53.007??? will it boot???
jyubil said:
can i flash cyanogenmod by 4ext with my s-on and hboot 1.53.007??? will it boot???
Click to expand...
Click to collapse
as far as i know...
you only can flash ICS ROM...
what cyanogenMod version do you want to flash ?
jyubil said:
can i flash cyanogenmod by 4ext with my s-on and hboot 1.53.007??? will it boot???
Click to expand...
Click to collapse
Only sense based ROMs will boot with your h-boot version. Don't even try CM, you'll just loose time and nerves
Is it sent?
naxsandbew said:
as far as i know...
you only can flash ICS ROM...
what cyanogenMod version do you want to flash ?
Click to expand...
Click to collapse
JB rom
jyubil said:
JB rom
Click to expand...
Click to collapse
Did you go to prison for a year?