Related
Explanations:
Have a Best Buy HTC Flyer with OTA stock HC 3.2 and wanted to downgrade to GB and used this method http://forum.xda-developers.com/showthread.php?t=1307759
Followed all directions from Post #1 to #11 using RUU_Flyer_BrightstarUS_WWE_1.36.1540.32_R_Radio_20 .3501.30.089BU_3809.05.04.10_M_release_191425_sign ed.exe as my RUU.
Ran RUU and HTC flyer pops up with bootloader screen on computer RUU says sending. Let it run max for 2-3hrs. Still saying the same thing. Unplugged it and now getting
FLYER PVT SHIP S-ON RL
HBOOT-1.10.0000
MICROP-0950
RADIO-3809.05.04.10_M
eMMC-boot
May 4 2011,11:04:45
When I select reboot it restarts and boots up the a white screen with HTC in green and stays this way.
When I try running the RUU again it does the same thing, just sits on sending.......
I am able to get to fastboot and hboot screen.
I am able to use flashboot
I am not able to to use adb
When I click recovery it just blinks and boots back up to Hboot so I'm thinking I don't have a recovery.
I tried running HTC unlock website again but I recieve an error when running the flashbook unlock command.
I'm thinking the since I'm S-ON I can't run recovery from flashboot
Please help......
As I understand from your post, you were S-ON on GB, ran OTA, and were on S-ON HC, right ?
HAVE YOU TRIED THIS THREAD FIRST ?
http://forum.xda-developers.com/showthread.php?t=1428104
Ok, what was your INITAL hBoot version ?
Good explanation. I've seen threads where people go:
i flashed ledroid hc on me gb flyer. it bricked it plz halp!
jaguaralani said:
As I understand from your post, you were S-ON on GB, ran OTA, and were on S-ON HC, right ?
HAVE YOU TRIED THIS THREAD FIRST ?
http://forum.xda-developers.com/showthread.php?t=1428104
Ok, what was your INITAL hBoot version ?
Click to expand...
Click to collapse
I was on stock OTA HC with S-ON. And wanted to go to back to GB.
rkum19 said:
Explanations:
Have a Best Buy HTC Flyer with OTA stock HC 3.2 and wanted to downgrade to GB and used this method http://forum.xda-developers.com/showthread.php?t=1307759
Followed all directions from Post #1 to #11 using RUU_Flyer_BrightstarUS_WWE_1.36.1540.32_R_Radio_20 .3501.30.089BU_3809.05.04.10_M_release_191425_sign ed.exe as my RUU.
Ran RUU and HTC flyer pops up with bootloader screen on computer RUU says sending. Let it run max for 2-3hrs. Still saying the same thing. Unplugged it and now getting
FLYER PVT SHIP S-ON RL
HBOOT-1.10.0000
MICROP-0950
RADIO-3809.05.04.10_M
eMMC-boot
May 4 2011,11:04:45
When I select reboot it restarts and boots up the a white screen with HTC in green and stays this way.
When I try running the RUU again it does the same thing, just sits on sending.......
I am able to get to fastboot and hboot screen.
I am able to use flashboot
I am not able to to use adb
When I click recovery it just blinks and boots back up to Hboot so I'm thinking I don't have a recovery.
I tried running HTC unlock website again but I recieve an error when running the flashbook unlock command.
I'm thinking the since I'm S-ON I can't run recovery from flashboot
Please help......
Click to expand...
Click to collapse
put it in fastboot mode and run the RUU again.
from fastboot
fastboot oem rebootRUU
Run stock ruu (only if you have the exe)
do you have the ruu.exe or just the zip?
if its just the zip make sure you run cmd with administrator rights and make sure the ruu zip is in the directory where your fastboot resides. on a windows 7 box (Program Files (x84)/Android/android-sdk/platform-tools)
then:
fastboot flash zip ruu_zip_name.zip
Good luck
wranglerray said:
from fastboot
fastboot oem rebootRUU
Run stock ruu (only if you have the exe)
do you have the ruu.exe or just the zip?
if its just the zip make sure you run cmd with administrator rights and make sure the ruu zip is in the directory where your fastboot resides. on a windows 7 box (Program Files (x84)/Android/android-sdk/platform-tools)
then:
fastboot flash zip ruu_zip_name.zip
Good luck
Click to expand...
Click to collapse
This should work for you, I had similar issues, and had to run fastboot commands to get it loaded right. This is the best explanation I've seen, should be added somewhere in the pinned docs.
Also you may have another option.
hboot 1.10.0000 is a stock hboot for the BB wifi flyer.
From fastboot you should be able to run revolutionary to gain s-off irregardless of your rom state. after you have s-off its just a matter of do you want HC or GB.
You can always relock the bootloader once you have a working rom again.
I have the HC s-off ruu. its buried in a thread somewhere but i'd be happy to host it somewhere so you could download it.
wranglerray said:
Also you may have another option.
hboot 1.10.0000 is a stock hboot for the BB wifi flyer.
From fastboot you should be able to run revolutionary to gain s-off irregardless of your rom state. after you have s-off its just a matter of do you want HC or GB.
You can always relock the bootloader once you have a working rom again.
I have the HC s-off ruu. its buried in a thread somewhere but i'd be happy to host it somewhere so you could download it.
Click to expand...
Click to collapse
None of that is correct.
Is it just me or is the last post from the person with the issue from March 6th?
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Is it just me or is the last post from the person with the issue from March 6th?
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Yes, you're correct. I only replied to the thread to make sure the incorrect infomation didn't waste anyones time.
I decided to run the 4.03.605.2 RUU before flashing back to Neo's Adrenaline 2.0...running the RUU reflashed a stock recovery and returned the bootloader to Locked, of course, so I went to the HTC Dev site to try to unlock it. I'm sure it's already a known issue but it appears that HTC's bootloader unlock tool is down and has been for some short time with no apparent efforts on their part to fix it.
So, I'm stuck with a locked bootloader until such time as someone can find a way to flash recovery without needing to unlock...
buh, wasn't the whole point of S-OFF so you don't have to use HTC's bootloader unlocker tool?
just s-off.
Yes, but if you flash an RUU that updates HBOOT, it will relock. Doesn't change the S flag, but it does indeed lock. I've had this happen twice.
Managed to find my original unlock_code.bin. Worked perfectly, I'm back in business...
When you unlock your phone, SAVE THE UNLOCK TOKEN!!! It can be used on your device no matter what you do.
socal87 said:
Yes, but if you flash an RUU that updates HBOOT, it will relock. Doesn't change the S flag, but it does indeed lock. I've had this happen twice.
Managed to find my original unlock_code.bin. Worked perfectly, I'm back in business...
When you unlock your phone, SAVE THE UNLOCK TOKEN!!! It can be used on your device no matter what you do.
Click to expand...
Click to collapse
I think the point he was trying to make is that if you are s-off, it overides the lock/unlock so you don't have to be unlocked anymore. S-off and locked, you can install whatever you want...
nrfitchett4 said:
I think the point he was trying to make is that if you are s-off, it overides the lock/unlock so you don't have to be unlocked anymore. S-off and locked, you can install whatever you want...
Click to expand...
Click to collapse
That's what I thought too, but I tried to flash recovery after running the RUU...got the "not allowed" error; unlocked, and had no issue.
To my knowledge, all S-off does is "break" the locks on certain partitions, such as boot, so they can be written from recovery...and allow flashing of radios and HBOOT without a valid signature. Recovery itself is what decides what you can flash in terms of ROMs...the stock recovery won't flash anything but an original signed .zip.
Next time just flash the the jupunto bear hboot it makes everything easier and all you need is the s off to flash it. I do it right after running any ruu
I ran the latest ruu,was s-off,locked bootloader,and flashed the recovery without any problems. You can try to push it through adb if anything
Sent from my ADR6425LVW using Tapatalk 2
I keep my phone unlocked all the time.
I can ruu with an unlocked bootloader because I have s-off.
The ruu process always leaves my phone in its unlocked state.
I never bother using jbear hboots, as they don't accomplish anything useful that anyone is likely to use. It gives some additional fastboot commands that nobody is using. If someday I need a jbear hboot command, then I'll flash it. Otherwise it just seems to be extra work, and it appears to have complicated your life.
---------- Post added at 06:19 AM ---------- Previous post was at 05:54 AM ----------
jayochs said:
buh, wasn't the whole point of S-OFF so you don't have to use HTC's bootloader unlocker tool?
just s-off.
Click to expand...
Click to collapse
No, the instructions at hbear's website list being htcdev unlocked as a prerequisite along with being stock and rooted, before even attempting the s-off procedure. Soff is something in addition to unlocked.
The jbear hboot acts like it is unlocked, whether the phone is locked or unlocked. Supposedly this will fool Verizon that your returned borked phone was not tampered with - well until Verizon notices jbear written on your hboot screen.
However, running a ruu will install a stock hboot.
Personally I think jbear hboots are a waste of effort. They are not going to fool anyone at Verizon because jbear is displayed on the hboot screen.
If somehow you go back to s-on with the jbear hboot still installed, then you are,oops, permanently bricked.
The additional fastboot commands one gets with the jbear hboot are not being used, not even by developers during their Rom installation procedures.
After every ruu, you need to repeat the htcdev unlock, and reflash the jbear hboot. This is extra work.
Everytime one flashes an hboot he is taking a bricking risk. if the flashing fails for any reason, like you pulled out the battery or battery runs out of power, or your file got corrupted, then you have an unrecoverable brick. That's why OTAs refuse to install on a low battery charge.
S-off + htcdev Unlocked are wonderful, but I think the concept of modified hboots should be reconsidered.
regards
Howard
HowardZ said:
I keep my phone unlocked all the time.
I can ruu with an unlocked bootloader because I have s-off.
The ruu process always leaves my phone in its unlocked state.
I never bother using jbear hboots, as they don't accomplish anything useful that anyone is likely to use. It gives some additional fastboot commands that nobody is using. If someday I need a jbear hboot command, then I'll flash it. Otherwise it just seems to be extra work, and it appears to have complicated your life.
---------- Post added at 06:19 AM ---------- Previous post was at 05:54 AM ----------
No, the instructions at hbear's website list being htcdev unlocked as a prerequisite along with being stock and rooted, before even attempting the s-off procedure. Soff is something in addition to unlocked.
The jbear hboot acts like it is unlocked, whether the phone is locked or unlocked. Supposedly this will fool Verizon that your returned borked phone was not tampered with - well until Verizon notices jbear written on your hboot screen.
However, running a ruu will install a stock hboot.
Personally I think jbear hboots are a waste of effort. They are not going to fool anyone at Verizon because jbear is displayed on the hboot screen.
If somehow you go back to s-on with the jbear hboot still installed, then you are,oops, permanently bricked.
The additional fastboot commands one gets with the jbear hboot are not being used, not even by developers during their Rom installation procedures.
After every ruu, you need to repeat the htcdev unlock, and reflash the jbear hboot. This is extra work.
Everytime one flashes an hboot he is taking a bricking risk. if the flashing fails for any reason, like you pulled out the battery or battery runs out of power, or your file got corrupted, then you have an unrecoverable brick. That's why OTAs refuse to install on a low battery charge.
S-off + htcdev Unlocked are wonderful, but I think the concept of modified hboots should be reconsidered.
regards
Howard
Click to expand...
Click to collapse
You are wrong in so many ways Howard.please everyone font bother reading this post.
Ok jbear hboot is not meant to fool Verizon. It's meant to provide fastboot commands even while the bootloader is locked.
As for op,I can confirm after running the ruu,you will still have to unlock to flash your recovery, if you still have your unlock code file you can unlock with that just like you did the first time .
Oh and the HTC website always does that just keep trying like every hour or so, if you can't find that unlock file they e mailed you
Sent from my ADR6425LVW using xda app-developers app
I am s-off and locked. And have been able to flash everything under the sun with no problems
The jb hboots are used not to fool Verizon, but to allow people to use fastboot commands like, "fastboot flash recovery (filename.img)" after s-off.
If you are s-off with stock hboot you can't run those commands.
Like Howard said, if you are on the jb hboot and you run the s-on command...then you're bricked. So those people with jb hboots are told to run a RUU first. Like Howard says, there are some risks to flashing things...its also risky to put your phone in your shirt pocket when you are around water.
Now, you can unlock your device after s-off (like Howard did) and use those commands with the stock hboot. However, if you want to return it to Verizon and you lock it, then it will read 'relocked' (i believe). I think that is the ONLY disadvantage of unlocking after s-off.
All this 'stuff' is in these threads. Some of it is personal preference and we all have a reason why our phones are configured certain ways. Just be aware of the implications.
There's no extra work on flashing jbear hboot. Right after the ruu rename the jhboot.zip to ph98img boot on hboot, flash and done. It seems you don't have a lot of knowledge when it comes into hboot stuffs.(no offense intended) And like the others guys said jbear is not to fool anyone and beside the jbear is an unlocked hboot.
socal87 said:
So, I'm stuck with a locked bootloader until such time as someone can find a way to flash recovery without needing to unlock...
Click to expand...
Click to collapse
There is a flashable amon ra you can use. You don't need to unlock. You also will need to flash supersu again too because you lost root after the ruu. If you want to stay on a stock hboot, then you run things as ph98 files.
Sent from my ADR6425LVW using xda app-developers app
dassh said:
There is a flashable amon ra you can use. You don't need to unlock. You also will need to flash supersu again too because you lost root after the ruu. If you want to stay on a stock hboot, then you run things as ph98 files.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
But he does need to be s-off...and I think he said he wasn't.
topgun1953 said:
The jb hboots are used not to fool Verizon, but to allow people to use fastboot commands like, "fastboot flash recovery (filename.img)" after s-off.
If you are s-off with stock hboot you can't run those commands.
Like Howard said, if you are on the jb hboot and you run the s-on command...then you're bricked. So those people with jb hboots are told to run a RUU first. Like Howard says, there are some risks to flashing things...its also risky to put your phone in your shirt pocket when you are around water.
Now, you can unlock your device after s-off (like Howard did) and use those commands with the stock hboot. However, if you want to return it to Verizon and you lock it, then it will read 'relocked' (i believe). I think that is the ONLY disadvantage of unlocking after s-off.
All this 'stuff' is in these threads. Some of it is personal preference and we all have a reason why our phones are configured certain ways. Just be aware of the implications.
Click to expand...
Click to collapse
with s-off and unlocked and stock hboot
one can
fastboot boot recoveryImageFile.IMG
fastboot flash recovery recoveryImageFile.IMG
fastboot flash boot kernelImageFile.IMG
I have done these, and they work.
It makes one wonder who really needs jbear hboots.
p.s. if someday I brick my phone, I don't plan to return to a Verizon store and lie to them.
HowardZ said:
with s-off and unlocked and stock hboot
one can
fastboot boot recoveryImageFile.IMG
fastboot flash recovery recoveryImageFile.IMG
fastboot flash boot kernelImageFile.IMG
I have done these, and they work.
It makes one wonder who really needs jbear hboots.
Click to expand...
Click to collapse
Yes you can flash those things. I guess that's what I was saying.
The "reason" that I know of to use jb hboots is if you ever want to return or sell your phone in a 'locked' state, you can. If you s-off, unlock, and then relock, I think it says "relocked" on the hboot screen.
topgun1953 said:
Yes you can flash those things. I guess that's what I was saying.
The "reason" that I know of to use jb hboots is if you ever want to return or sell your phone in a 'locked' state, you can. If you s-off, unlock, and then relock, I think it says "relocked" on the hboot screen.
Click to expand...
Click to collapse
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
HowardZ said:
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
Click to expand...
Click to collapse
I don't think verizon cares. IMHO
In my case, I'm locked, s-off, stock hboot. I can get what I want in ph98img.zip files so I don't use fastboot. I can write the s-on flag, and flash the lastest ota and my phone will be like stock, out of the box....good for some, doesn't really matter to me.
HowardZ said:
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
Click to expand...
Click to collapse
Verizon don't care about s-off because there's some rezound that came out s-off out of the box.
topgun1953 said:
But he does need to be s-off...and I think he said he wasn't.
Click to expand...
Click to collapse
Yes, absolutely needs to be s-off for what i was suggesting. I may have mis-understood the op and subsequent posts. If the op doesn't want to s-off then unlock is a necessity but if s-offed, then the op has a choice to unlock or stay locked.
I chose to stay locked, like Topgun says, it's easier. The only difference is i did install a jbear hboot, but again that was because i think it's easier to use fastboot sometimes instead of trying to repackage something as a ph98.
Sent from my ADR6425LVW using xda app-developers app
---------- Post added at 01:28 PM ---------- Previous post was at 01:22 PM ----------
HowardZ said:
p.s. if someday I brick my phone, I don't plan to return to a Verizon store and lie to them.
Click to expand...
Click to collapse
If you brick, you couldn't change your hboot anyway. Using a jbear hboot is not to be deceptive.
Sent from my ADR6425LVW using xda app-developers app
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
In other words, Only attempt this AFTER flashing back to a STOCK RUU. (as this will flash the STOCK HBOOT.)
I know the process JUST came out, but I'm sure this will eventually come in to use.
Instructions:
1) Download and run an RUU. Found HERE
2) Open a cmd window. Plug in phone, charge only mode, usb debugging on.
3) Run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Disclaimer:
I am not responsible for anything harmful that happens to your phone. Use at your OWN risk. Thank you.
http://forum.xda-developers.com/showthread.php?p=35437335
reserved.
reserved. 2.
Do these steps clear the "relocked" flag?
Sent from my ADR6410LVW using Tapatalk 2
mdmower said:
Do these steps clear the "relocked" flag?
Sent from my ADR6410LVW using Tapatalk 2
Click to expand...
Click to collapse
Whatever it said when it was S-ON is my understanding. but since I haven't yet tested this for our phone I can't say 100%
From the looks of your post, I guess you sourced the information from http://forum.xda-developers.com/showthread.php?t=1612937, which I also had bookmarked for my future reference. From that thread, here's how I understand it:
If we S-OFF then unlock, we can expect RELOCKED after S-ON.
If we S-OFF but keep bootloader locked, we can expect LOCKED after S-ON.
It doesn't look like we can expect a custom tag to stick around after S-ON.
Source post (different phone, so may not be the same for us)
scotty1223 said:
correct. only way to get locked back,is to turn s-on,then re unlock and re-s-off. and then,do not unlock after s-off. your hboot will stay locked and you can s-on again,if you need to. just keep in mind that turning s-on should only be done for warranty purposes.
Click to expand...
Click to collapse
mdmower said:
From the looks of your post, I guess you sourced the information from http://forum.xda-developers.com/showthread.php?t=1612937, which I also had bookmarked for my future reference. From that thread, here's how I understand it:
If we S-OFF then unlock, we can expect RELOCKED after S-ON.
If we S-OFF but keep bootloader locked, we can expect LOCKED after S-ON.
It doesn't look like we can expect a custom tag to stick around after S-ON.
Source post (different phone, so may not be the same for us)
Click to expand...
Click to collapse
Yes Sir, indeed.
Andy real quick question flashing ruu well eliminate soff correct
No, hence post 1. I'm guessing this relates to your MIUI adventure. You can have S-OFF and LOCKED bootloader.
Sent from my ADR6410LVW using Tapatalk 2
no this command, and this command only is what I know to get to S-ON
fastboot oem writesecureflag 3
andybones said:
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
In other words, Only attempt this AFTER flashing back to a STOCK RUU. (as this will flash the STOCK HBOOT.)
I know the process JUST came out, but I'm sure this will eventually come in to use.
Instructions:
1) Download and run an RUU. Found HERE
2) Open a cmd window. Plug in phone, charge only mode, usb debugging on.
3) Run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Disclaimer:
I am not responsible for anything harmful that happens to your phone. Use at your OWN risk. Thank you.
Click to expand...
Click to collapse
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
IXVash said:
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
Click to expand...
Click to collapse
Erm, wrong forum IXVash?
andybones said:
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
Click to expand...
Click to collapse
andybones refers to this, but to clarify, the DirtyRacun hboot is an engineering hboot. If going s-on, make sure to run the RUU first.
Sent from my Fireball using Xparent Blue Tapatalk 2
IXVash said:
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
Click to expand...
Click to collapse
that's because this is the HTC DROID INCREDIBLE 4G LTE FORUM... NOT THE EVO 4G LTE.
I know my RUU's point to the correct thread... because I made it!
Do I need to flash the dirty racun hboot from their page? Is having the dirt racun hboot important? Mine says 1.15.000 I have since gaining s-off have had to flash our ruu.
*Edit* I went ahead flashed it now I'm back to where I was after the s-off tool right where I needed to be
sent from my all powerful INC4G
mdmower said:
Erm, wrong forum IXVash?
Click to expand...
Click to collapse
well crap. Sorry It was a long night /facepalm
prairiedogn said:
Do I need to flash the dirty racun hboot from their page? Is having the dirt racun hboot important? Mine says 1.15.000 I have since gaining s-off have had to flash our ruu.
*Edit* I went ahead flashed it now I'm back to where I was after the s-off tool right where I needed to be
sent from my all powerful INC4G
Click to expand...
Click to collapse
The ENG HBOOT has different options. Glad you got it back.
sent from my DINC4 using Tapatalk 2
Hi,
I need stock "Locked" bootloader.
I've RUU the DirtyRacun Phone by advice as an attempt to fix (SIM failed) and now the Phone is S-OFF with stock Hboot "RELOCKED". Had to unlock the device again for last fix attempts.
Will flashing with S-OFF with stock signed Hboot clear bootloader security flags changing "RELOCKED" back to "LOCKED"?
Now RUU doesn't deliver "Locked" bootloader status. Should I next Flash signed stock Hboot first? Or should I Flash a DR Hboot then RUU again?
Last I would do your posted above for S-ON from Fastboot down since OS locks (no ADB).
Don't want to brick my phone.
Thanks In Advance!
mpeg3s said:
Hi,
I need stock "Locked" bootloader.
I've RUU the DirtyRacun Phone by advice as an attempt to fix (SIM failed) and now the Phone is S-OFF with stock Hboot "RELOCKED". Had to unlock the device again for last fix attempts.
Will flashing with S-OFF with stock signed Hboot clear bootloader security flags changing "RELOCKED" back to "LOCKED"?
Now RUU doesn't deliver "Locked" bootloader status. Should I next Flash signed stock Hboot first? Or should I Flash a DR Hboot then RUU again?
Last I would do your posted above for S-ON from Fastboot down since OS locks (no ADB).
Don't want to brick my phone.
Thanks In Advance!
Click to expand...
Click to collapse
To get back to truly LOCKED, check this post:
http://forum.xda-developers.com/showthread.php?p=35437335
Sent from my Kindle Fire using Xparent Blue Tapatalk 2
junkmail9 said:
To get back to truly LOCKED, check this post:
http://forum.xda-developers.com/showthread.php?p=35437335
Sent from my Kindle Fire using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
nice find man, I made this based off of his post anyway, so his thread would be the place to go, I'll add it to the OP.
Got an OPTUS HTC EVO 3D with unlocked bootloader S-ON, NOT rooted HBOOT 1.53.0007 with Stock ICS rom.
whenever I turn it on, it loads to the HTC logo and restarts, it also apply to the recovery mode, no matter using HBOOT, adb, fastboot mode are still the same(have tried to load different boot.img, recovery.img). I have read and tried lot of methods still doesn't work. Would relock the bootloader and load the OPTUS001 RUU the only solution to fix it? But the problem is that I don't have the NAND backup and couldn't find any of the ROM that is suitable. Any suggestion is appreciated. Thanks!
YES. Flashing a ruu will fix it.
For s-on users, lock bootloader with "fastboot oem lock" command. Download and run the RUU (it must be ics ruu). All RUUs are available from there -> http://forum.xda-developers.com/showthread.php?t=2094402
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
Also, you must have adb drivers installed!
MrJyrks said:
YES. Flashing a ruu will fix it.
For s-on users, lock bootloader with "fastboot oem lock" command. Download and run the RUU (it must be ics ruu). All RUUs are available from there -> http://forum.xda-developers.com/showthread.php?t=2094402
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
Also, you must have adb drivers installed!
Click to expand...
Click to collapse
It is still with s-on and I couldn't change the CID, which is still remain OPTUS001. In this case, the only RUU that suits me is the OPTUS RUU, but I couldn't find any of them. Any idea?
Well, in theory it should be possible to flash any ruu even if the cid is not supported by default. If you download a ruu and run it, the ruu creates a temporary directory which holds both the stock rom and recovery. You need to add your cid in a file somewhere in the rom zip, then it can be installed. Don't ask me how and if it will work, since i don't know for sure.
These Files are for the Verizon Droid DNA (dlx), Do not under any circumstances flash these on a different device!
I am simply posting these for their use. As you already know, I am not to blame if you mess up your device.
You are fully responsible for downloading and flashing any file posted by me!
By downloading any of these files you accept these terms.
*** Make sure to do 1 at a time ***
hboot = bootloader
radio = baseband
recovery = recovery
Flashing Instructions
These can ONLY be flashed in fastboot mode, NO EXCEPTIONS!!!
(please do not ask for Recovery Flashable zips, I will not make them as of yet!)
Code:
*** Boot into Bootloader/Fastboot USB Mode ***
Step 1) fastboot oem rebootRUU
[COLOR="Red"]*** Wait for the device to reboot to a black screen with an HTC logo ***[/COLOR]
Step 2a) fastboot flash zip PL83IMG_#.##_hboot.zip
or
Step 2b) fastboot flash zip PL83IMG_#.##_Radio.zip
or
Step 2c) fastboot flash zip PL83IMG_#.##_Recovery.zip
[COLOR="Red"]*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way][/COLOR]
Step 3) fastboot reboot-bootloader
Firmware Links
Check the MD5SUM Hash after you download!
Firmware:
hboot
Code:
*** You may need to scroll down ***
[B][COLOR="Red"]1.15.605.4[/COLOR] hboot (1.33.0001)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4884]Download Here[/url]
[B]2.[COLOR="Red"]04[/COLOR].605.2 hboot (1.33.0001)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4885]Download Here[/url]
[B]2.[COLOR="Red"]06[/COLOR].605.1 hboot (1.33.0001)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4886]Download Here[/url]
[B]2.[COLOR="Red"]07[/COLOR].605.1 hboot (1.33.0001)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4887]Download Here[/url]
[B][COLOR="Red"]3.06[/COLOR].605.4 hboot (1.54.0000)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4888]Download Here[/url]
[B][COLOR="Red"]4.09[/COLOR].605.1 hboot (?.??.????)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=6028]Download Here > Latest <[/url]
Radio
Code:
*** You may need to scroll down ***
[B][COLOR="Red"]1.15.605.4[/COLOR] Radio (1.00.00.1023)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4889]Download Here[/url]
[B]2.[COLOR="Red"]04[/COLOR].605.2 Radio (1.01.01.0110)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4890]Download Here[/url]
[B]2.[COLOR="Red"]06[/COLOR].605.1 Radio (1.01.04.0308)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4891]Download Here[/url]
[B][COLOR="Red"]3.06[/COLOR].605.4 Radio (1.01.01.1112)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4892]Download Here[/url]
[B][COLOR="Red"]4.09[/COLOR].605.1 Radio (1.02.01.0207)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=6029]Download Here > Latest < [/url]
Misc:
Code:
[B][COLOR="Red"]3.06[/COLOR].605.4 Stock Recovery[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4893]Download Here[/url]
This bootloader has been modified to not display the HTC DEV message on the boot/splash screen
Code:
[B]Modified hboot (1.54.1234)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4895]Download Here[/url]
If you flashed a custom Splash Image, this will flash the Stock one back onto the device
Code:
[B]Stock HTC Splash Image[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4896]Download Here[/url]
Engineering Bootloader:
WARNING: THIS "ENG HBOOT" IS EXTREMELY DANGEROUS!
DO NOT UNLOCK, LOCK, S-OFF, S-ON, OR RUU YOUR DEVICE WITH THIS BOOTLOADER!
IT WILL "HARD-BRICK" YOUR DEVICE 100% GUARANTEED!
THE "ENG HBOOT" WILL FLASH ANYTHING TO ANY PARTITION WITHOUT CHECKING!
TAKE EXTREME CAUTION WHEN CHOOSING YOUR FILES!
FLASH AT YOUR OWN RISK, THIS APPLIES TO ALL FILES POSTED!
Code:
[B]Engineering hboot (1.39.2000)[/B]: [url=http://forum.xda-developers.com/devdb/project/dl/?id=4894]Download Here[/url]
RUU Links
Code:
[SENSE 4 RUU]
RUU_DLX_WL_JB_45_VERIZON_WWE [COLOR="Red"][B][U]1.15.605.4[/U][/B][/COLOR] Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe
[url=https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing]Download Here**[/url]
[SENSE 5 RUU]
RUU_DLX_WL_JB_50_S_VERIZON_WWE [COLOR="Green"][B][U]3.06.605.4[/U][/B][/COLOR] Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2.exe
[url=https://drive.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/edit?usp=sharing]Download Here[/url]
If you are experiencing issues with the SENSE 5 RUU, follow this next guide.
This will wipe your device and flashes a stock recovery.
Make sure to backup your data!
Alt 3.06 RUU
Credits for this little guide goes to jailbird2
Code:
*** Boot into Bootloader/Fastboot USB Mode***
fastboot oem rebootRUU
fastboot flash zip 306_firmware_part1.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
[COLOR="Red"]*** This next part is very important, you need to flash this twice ***[/COLOR]
fastboot flash zip 306_firmware_part2.zip
fastboot flash zip 306_firmware_part2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip SENSE_5_RUU_ROM.zip
Code:
[B]306_firmware_part1.zip[/B] [url=http://forum.xda-developers.com/devdb/project/dl/?id=4898]Download Here[/url]
[B]306_firmware_part2.zip[/B] [url=http://forum.xda-developers.com/devdb/project/dl/?id=4897]Download Here[/url]
[B]SENSE_5_RUU_ROM.zip[/B] [url=http://forum.xda-developers.com/devdb/project/dl/?id=4899]Download Here[/url]
Downloads Served ~ 20,000
** In order to use the 1.15 RUU, you must revert back to the stock 1.15 hboot located above
I am not taking credit for the files, I only take credit for the guide and links I provide.
XDA:DevDB Information
[Latest OTA: 4.09.605.1] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU], Tool/Utility for the HTC Droid DNA
Contributors
.torrented
Version Information
Status: Stable
Created 2014-03-22
Last Updated 2014-12-14
Frequently Asked Firmware Questions:
Q: If I flash a different bootloader will I lose S-OFF or my unlocked status?
A: No, By flashing a different bootloader you will retain your current bootloader status.
Q: The RUU.exe keeps giving me errors, what can I do?
A: Look below the RUU.exe links and you will see a small guide with 3 different files, use that.
Q: What are the advantages to flashing newer firmware?
A: (hboot) Compatibility with future software from HTC.
A: (radio) This could potentially resolve any connection issues, or low signal quality, that your device may have.
.torrented said:
I decided to have this here to bring it to the public more than it was. If a Mod deems this unnecessary he/she shall remove this thread.
Click to expand...
Click to collapse
I sent u a pm so u can add 2.07 RUU idk if you got the pm or didn't want to add it.
Also I think a mod should sticky this.
thayl0 said:
I sent u a pm so u can add 2.07 RUU idk if you got the pm or didn't want to add it.
Also I think a mod should sticky this.
Click to expand...
Click to collapse
I would feel better posting an actual .exe version rather than whatever that was. I also figured since the 3.06 was released people would rather RUU to the newer RUU anyways. Thanks though, it's been hectic with my new class schedule and work. That's why I didn't respond.
this is probably a dumb question and I'm kind of a total noob to this whole thing. I was wondering, if I flash the HBoot and Radio provided here, will I still have S-Off and root?
I currently have S-Off and have root. I've also installed a custom rom.
When I hold volume down and power here is the information I have (bootloader?)
moonshine S-OFF
MONARUDO PVT SHIP S-OFF
CID-VZW___001
HBOOT-1.33.4444
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
cmiz87 said:
this is probably a dumb question and I'm kind of a total noob to this whole thing. I was wondering, if I flash the HBoot and Radio provided here, will I still have S-Off and root?
I currently have S-Off and have root. I've also installed a custom rom.
When I hold volume down and power here is the information I have (bootloader?)
moonshine S-OFF
MONARUDO PVT SHIP S-OFF
CID-VZW___001
HBOOT-1.33.4444
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Click to expand...
Click to collapse
Yes, changing radios or HBoot will not affect your S-Off or root status. :good:
Have fun...
I am having the hardest time flashing the HBOOT. When i type adb devices it comes back FA122345 attached , but when i type the reboot fastboot command thats when i completely lose the USB connection and it tells me it is not recognized. any suggestions? BTW can a HBOOT file be made into a flashable .zip to use in recovery?
@.torrented I flashed what I thought was the latest radio and hboot, however I realized that I'm now on hboot 1.33.0001 instead of my previous 1.33.4444. The latest is 1.54, which I believe comes from 3.06, is there not an hboot from that firmware?
Bob_is_a_Droid said:
I am having the hardest time flashing the HBOOT. When i type adb devices it comes back FA122345 attached , but when i type the reboot fastboot command thats when i completely lose the USB connection and it tells me it is not recognized. any suggestions? BTW can a HBOOT file be made into a flashable .zip to use in recovery?
Click to expand...
Click to collapse
They can be, but I won't make them.
rejectedjs said:
@.torrented I flashed what I thought was the latest radio and hboot, however I realized that I'm now on hboot 1.33.0001 instead of my previous 1.33.4444. The latest is 1.54, which I believe comes from 3.06, is there not an hboot from that firmware?
Click to expand...
Click to collapse
I cannot get my hands on it if there is one, I can't extract it out of the RUU like I normally would be able to. (HTC encrypts them)
I'll try and hunt it down.
Edit* Until I can decrypt the RUU we won't have a new bootloader
Thanks @santod040 I never update my device so I never get a change to get those OTAPkg's
.torrented said:
They can be, but I won't make them.
I cannot get my hands on it if there is one, I can't extract it out of the RUU like I normally would be able to. (HTC encrypts them)
I'll try and hunt it down.
Click to expand...
Click to collapse
I had to hunt them back down as well, as I had the OTApkg's and then lost them on another drive somewhere.
......But HERE YOU GO :good:
santod040 said:
I had to hunt them back down as well, as I had the OTApkg's and then lost them on another drive somewhere.
......But HERE YOU GO :good:
Click to expand...
Click to collapse
Which one is the newest 3.06 OTAPkg.zip?
.torrented said:
Which one is the newest 3.06 OTAPkg.zip?
Click to expand...
Click to collapse
The smaller OTA package was the smaller pre-update.
The larger one is the final 3.06 OTA package.
Is this the proper file to download the latest 1.54.000 hboot?
Hello.
I have HBOOT 1.54.0000 (after flash to OTA 3.06.605.4) Radio: 1.01.01.1112, S-OFF and unlock Bootoader of Rumrunner, have ViperDNA with Sense 4 +
Can I use 3.06.605.4 OTA radio? It seems that this is the latest. Because I have problems with unstable WiFi signal. Or if I can without any problem to flash every rafio available in this thread for the purposes of the test? I'll be grateful for the quick reply.
John823 said:
Hello.
I have HBOOT 1.54.0000 (after flash to OTA 3.06.605.4) Radio: 1.01.01.1112, S-OFF and unlock Bootoader of Rumrunner, have ViperDNA with Sense 4 +
Can I use 3.06.605.4 OTA radio? It seems that this is the latest. Because I have problems with unstable WiFi signal. Or if I can without any problem to flash every rafio available in this thread for the purposes of the test? I'll be grateful for the quick reply.
Click to expand...
Click to collapse
You can use any radio you want to.
The 3.06 Radio version is 1.01.01.1112
sabres032 said:
Is this the proper file to download the latest 1.54.000 hboot?
Click to expand...
Click to collapse
I don't know the bootloader version #'s
.torrented said:
You can use any radio you want to.
The 3.06 Radio version is 1.01.01.1112
Click to expand...
Click to collapse
Well, yes. I'll try to lower the radio. Thank you.
New hboot/booloader
Thanks to @santod040 for the OTAPkg.zip I was able to get the new bootloader from the 3.06 update!
Link posted in OP!
Re-lock bootlaoder?
Do I have to re-lock the bootloader first before I flash the new Hboot firmware?
a7878 said:
Do I have to re-lock the bootloader first before I flash the new Hboot firmware?
Click to expand...
Click to collapse
Nope
Sent from my HTC6435LVW using XDA Premium HD app