I got a Droid DNA back from a repair store and it was booting as a ONE. It wasn't working properly so I relocked to run the 3.06.605.4 update which would not take. It had an error. I'm stuck at the bootloader screen saying it's a DNA not a ONE and it's relocked. I don't have the .bin used to unlock it as the store did it.
I need to get it working at least booting into android. Any help?
FrankthaTank said:
I got a Droid DNA back from a repair store and it was booting as a ONE. It wasn't working properly so I relocked to run the 3.06.605.4 update which would not take. It had an error. I'm stuck at the bootloader screen saying it's a DNA not a ONE and it's relocked. I don't have the .bin used to unlock it as the store did it.
I need to get it working at least booting into android. Any help?
Click to expand...
Click to collapse
Sounds like the store doesn't know what there doing. Anyways are you soff?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Just use an soff method or run the ruu. And then soff.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Related
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
I'm not sure what u flashed but it sounds like you flashed the whole thing which means you have stock recovery now. Either fastboot flash recovery image or download thru goo manager.
Once you have a custom recovery installed your all set. Don't worry about the locked on your bootloader
Sent from my EVO using xda premium
mainstang said:
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You should have flashed the first file the one with no kernel,hboot, or stock recovery that would have updated everything you needed to be updated
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
mainstang said:
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
No you just did the same as taking the OTA as far as I can tell. As long as everything is working you should be fine
So this has probably been posted already, but I got a warranty replacement and the rezound I have now is S-OFF with unlock bootloader. I know I have to relock the bootloader and it'll flash a stock HBOOT, but what about the S-OFF?
http://forum.xda-developers.com/showthread.php?p=25165453
I used this a few months ago and it worked like a charm.
Sent from my Rezound using xda app-developers app
Now am I doing this before or after I run the RUU?
After.
Sent from my Rezound using xda app-developers app
So when I'm trying to run the RUU the exe keeps giving me error issues. So I tried to relock the bootloader but it won't lock and keeps saying "INFODevice was already locked"
Figured it out, had to flash the RUU via .zip instead of exe. Mods please delete thread.
I had a unlocked bootloader, rooted rezound running AOKP JB rom. Now after trying to flash a differnet kernel (stupid me) I can't get past the bootloader screen. I was able to relock my bootloader but now on Hboot screen it says ***tampered*** *****relocked**** and ****security warning**** I am completely stuck. Am I SOL or is there a chance to fix this? Any help would be greatly appreciated.
bluerez79 said:
I had a unlocked bootloader, rooted rezound running AOKP JB rom. Now after trying to flash a differnet kernel (stupid me) I can't get past the bootloader screen. I was able to relock my bootloader but now on Hboot screen it says ***tampered*** *****relocked**** and ****security warning**** I am completely stuck. Am I SOL or is there a chance to fix this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Get back into fastboot. Unlocked your phone. You can just go back and flash the boot.img that was on your original rom
Flyhalf205 said:
Get back into fastboot. Unlocked your phone. You can just go back and flash the boot.img that was on your original rom
Click to expand...
Click to collapse
I tried. I went through the htc.dev and it all went ok until i tried to submit it. It said "unlocking bootloader failed"
bluerez79 said:
I tried. I went through the htc.dev and it all went ok until i tried to submit it. It said "unlocking bootloader failed"
Click to expand...
Click to collapse
You s-on or s-off?
Might as well install the RUU again...
Flyhalf205 said:
You s-on or s-off?
Might as well install the RUU again...
Click to expand...
Click to collapse
S-on
Can I flash with a locked bootloader?
Sent from my Galaxy Nexus using xda app-developers app
bluerez79 said:
Can I flash with a locked bootloader?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You won't be able to flash a rom or kernel if your s-on and locked. The only thing you can do is try and unlock bootloader or run RUU and restart from scratch
I can't unlock boot loader. Went thru the process and it said the token was too long. So I guess I'll look for the RUU and give it a go.
Sent from my Galaxy Nexus using xda app-developers app
bluerez79 said:
I can't unlock boot loader. Went thru the process and it said the token was too long. So I guess I'll look for the RUU and give it a go.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
At what point did it say that? When you are trying to get it from the HTC site? If that's it you are just copying too much. Make sure you don't copy any extra characters at all.
If it's when you are flashing the unlock token bin file then I agree that you should just run the RUU and get back to fresh stock then try again.
Use the RUU that is the .12 version rather than the global leak, unless you have already run the global leak one, if you want to be able to take the newest OTA.
I tries to flash ruu from my pc. The command prompt said “access denied"
Sent from my Galaxy Nexus using xda app-developers app
And your bootloader is locked? You talked about getting the unlock token, did you unlock it again before RUUing?
It needs to be locked to run the RUU.
bluerez79 said:
I tries to flash ruu from my pc. The command prompt said “access denied"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
How are you flashing it?
Fastboot flash and then the name of the ruu
Sent from my Galaxy Nexus using xda app-developers app
It was locked when I tried to flash ruu
Sent from my Galaxy Nexus using xda app-developers app
Try this:
fastboot oem rebootRUU
fastboot flash zip {nameofruu}.zip
Or place it on your sd card and flash it in hboot
If it's an exe file you need to double click on that on your pc while the phone is connected.
Hey guys I had to send my HTC One back to ATT. So I stupidly tried to get it back to stock, so I first flashed an Odex-ed Stock Rooted Rom, then flashed stock recovery in fastboot, then locked the bootloader and am now trying to run the RUU. And it doesnt seem to be working..what do I do? I just keep booting into the bootloader straight. Im so lost.
So your bootloader is locked, you start the ruu and what happens?
I had a similar issue. For some resason all of my laptops had issues with drivers. If you go in device manager in windows, check to see if you see exclamation mark on my HTC.
I tried different drivers, sync app from HTC and even fresh virtual box environments on MacBook to no avail. It always shows that yellow exclamation when in bootloader.
Anyways, didn't mean to hijack your thread but just trying to see what's in your device manager. Try hansoon HTC one app?
Sent from my HTC One using xda app-developers app
it either says "Phone not found" or the RUU wont even open .. will say issues with drivers
Damn, I hope you get it figured out. I wish I could help. I know I better keep my htc one stock for the time being. This could of happened to me.
Sent from my HTC One using Tapatalk 2
Packer2058 said:
Hey guys I had to send my HTC One back to ATT. So I stupidly tried to get it back to stock, so I first flashed an Odex-ed Stock Rooted Rom, then flashed stock recovery in fastboot, then locked the bootloader and am now trying to run the RUU. And it doesnt seem to be working..what do I do? I just keep booting into the bootloader straight. Im so lost.
Click to expand...
Click to collapse
Lol u can't just lock ur boot loader u have to run the firmware first and u must unroot all he had to do is unlock bootloader again and it would of booted
Sent from my HTC Butterfly using xda premium
Packer2058 said:
it either says "Phone not found" or the RUU wont even open .. will say issues with drivers
Click to expand...
Click to collapse
Reinstall the drivers
daorderdillon said:
Lol u can't just lock ur boot loader u have to run the firmware first and u must unroot all he had to do is unlock bootloader again and it would of booted
Sent from my HTC Butterfly using xda premium
Click to expand...
Click to collapse
yea i unlocked bootloader and it booted...what to do now
Packer2058 said:
yea i unlocked bootloader and it booted...what to do now
Click to expand...
Click to collapse
Flash a Rom like android revolutionary
Sent from my HTC Butterfly using xda premium
Happy New Years Everyone.
I am doing a warranty return on my HTC DNA. The DNA is rooted with Moonshine S-Off; HBOOT - 1.33.4444; RADIO - 1.01.04.0300; ROM - Viper DNA.
I have searched but found nothing that outlines the restore to stock for the 4.2.2 upgrade. I know I will have to restore the stock ROM and the stock bootloader and put the device back to S-On.
Can someone please share their process to return to Verizon Stock.
Thanks in advance.
Eduardo
I have found the following thread and will give it a try. I will updated later when the process is complete.
http://forum.xda-developers.com/showthread.php?t=2293919
There is thread that is a complete guide in the development section. I just did it worked fine just follow the steps it's very simple.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
There is thread that is a complete guide in the development section. I just did it worked fine just follow the steps it's very simple.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, Jaggar. Is the process the same as I linked in my previous post?
Yeah that's the one I used and I moonshined my dna and it worked great.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Yeah that's the one I used and I moonshined my dna and it worked great.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Great. I'm going to try the process tomorrow. Can you tell me if it completely wipes the phone. I don't want to have to clean it up before sending it back.
I've enjoyed the phone but it has been giving me lots of troubles with the SIM card and losing connectivity. I'm moving to the LG G2 and going to give it a shot.
eejimen said:
Great. I'm going to try the process tomorrow. Can you tell me if it completely wipes the phone. I don't want to have to clean it up before sending it back.
I've enjoyed the phone but it has been giving me lots of troubles with the SIM card and losing connectivity. I'm moving to the LG G2 and going to give it a shot.
Click to expand...
Click to collapse
It will wipe everything and your phone will be like it was out if the box. For the sim card errors you can call htc and they will ship you a new sim tray for free and it's thicker and will not give you any errors. I did it and have not had an error since putting it in.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Just word of advise j wouldnt run stock ruu. If I were you is just run the 3.04 ruu which if u follow the steps will give u s on bootkoader locked and Ur device will b on current update. Verizon doesn't require you phone to bone stock
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Either Ruu you use you will get to the same setup the other one just has ota updates it really doesn't matter.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Update:
I was able to get my phone back to 4.1.2 Stock using the instructions from post #2. I didn't bother configuring or updating the phone. It has already been packaged and ready to go back to VZW.
I did run in to some issues that required me to do a little more reading.
First I had to restore 1.15 bootloader and splash screen (post #4 in the above referenced thread). This was a little scary as there is a warning during boot up about being the engineering boot loader version and *** Tampered*** and ***Locked*** warning at top of boot loader screen. This is OK keep moving forward with the process.
Also to get the RUU executable to work correctly, reboot the phone into the bootloader and plug phone into computer. With out this step, I was getting and unkown error and update fails.
Peace.
I did this a few weeks ago (following the guide linked above), the only hiccup I hit was the 1.15 RUU failing (error 155). I was on a Sense 5 ROM (NOS) and apparently that was causing the RUU to see the wrong version number of my phone and say it wasn't compatible. I flashed a Sense 4 ROM and everything worked from there.
detonation said:
I did this a few weeks ago (following the guide linked above), the only hiccup I hit was the 1.15 RUU failing (error 155). I was on a Sense 5 ROM (NOS) and apparently that was causing the RUU to see the wrong version number of my phone and say it wasn't compatible. I flashed a Sense 4 ROM and everything worked from there.
Click to expand...
Click to collapse
Yea you half to be soff to downgrade software version.