Is there still warranty on an EVO 3D with touchscreen issues? It was unlocked to be rooted, but it never ran any custom software beyond that.
I can restore the original firmware.
This is for Canada.
xaueious said:
Is there still warranty on an EVO 3D with touchscreen issues? It was unlocked to be rooted, but it never ran any custom software beyond that.
I can restore the original firmware.
This is for Canada.
Click to expand...
Click to collapse
Relock the phone and you are set.
xaueious said:
Is there still warranty on an EVO 3D with touchscreen issues? It was unlocked to be rooted, but it never ran any custom software beyond that.
I can restore the original firmware.
This is for Canada.
Click to expand...
Click to collapse
if any questions come up take the phone and then do the Jbear wire trick... that will re-establish the phone to **LOCKED** and not **RELOCKED** then from fastboot usb type in fastboot oem writesecureflag 3
from there is should get you to s-on and locked so its like your custumization never happened
Warranty is one year after the purchase date.
If you decide to do the wire trick to get the bootloader back to "*** LOCKED ***" (stock) status, make sure to say "no" to the JuopunutBear bootloader and stay with the stock version. Using the "fastboot oem writesecureflag 3" command with a custom bootloader such as JBear, Revolutionary, or ENG installed will brick your phone.
You could also flash the RUU again after performing the wire trick to make sure everything is 100% stock before setting it back to S-ON and having it serviced.
ramjet73
no one has asked if it was unkocked through HTC DEV. if it was, and you are still within the year warranty it still should be covered. unless they hit you with the touch screen being messed up due to software issue. they will have record even if you go back to stock.
littlebeeper said:
no one has asked if it was unkocked through HTC DEV. if it was, and you are still within the year warranty it still should be covered. unless they hit you with the touch screen being messed up due to software issue. they will have record even if you go back to stock.
Click to expand...
Click to collapse
From what I've read, the carriers don't bother checking (or perhaps have access to) the htcdev.com database. Even if they did, or it was being returned to HTC for service, I don't think they can prove it was actually unlocked even if you requested a token unless it is in the "*** RELOCKED ***" state. As has already been mentioned, that can be reset to the stock "*** LOCKED ***" state by doing the wire trick.
ramjet73
Ok Rogers wireless is your carrier then you better lock it up tight, stock 100% otherwise they will shafts you big time, Rogers is my carrier unfortunately, and I am speaking from experience
( Don't ask me for help as I couldn't care if your phone explodes, eh! )
Related
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
I am having the same problem, but I found a way around it. If I boot the kernel through fastboot it will boot up. (You'd need to re unlock). My hboot doesn't really work anymore..
------
3(d)vo one s
Newts my hero.
evo bryan said:
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
Click to expand...
Click to collapse
Im not even sure at this point how to re-unlock it. i am wondering if i should have flashed to an older ruu though.
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
wards.jfasa said:
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
Click to expand...
Click to collapse
flashimage gui is able to do it inside android, im guessing it stores it in a tempory folder, let me see if i can find the temp folder where it stores before rebooting to flash it...........brb
did you check this post http://forum.xda-developers.com/showthread.php?t=1627897
This helped me out when I was Juopunutbear S-OFF'ing my phone. But I was at Hboot 1.50.
http://androidforums.com/evo-3d-all...mware-upgrade-ruu-flash-unbricking-guide.html
Pretty good guide.
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
The security warning is because you are using a custom rom so will not be able to use the RUU through the bootloader.
What you need to do is download the RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00. 1216_signed.exe from here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
If you then run that exe while your phone is in fastboot and connected to your pc it will factory reset your phone and put you back on stock rom and kernel.
Hey all, I got a warrantied phone and send my old one back only to find issues with the one they sent me. So I'm having to go through the process of going back to stock with the 1st replacement now that I got the 2nd replacement in hand.
I flashed the latest Stock GB RUU and that went fine. I did the S-On process and it's now S-On again...but still shows Unlocked. The last time I did this if I'm not mistaken, it relocked the phone when I did those two steps.
1. Has this happened to anybody else?
2. If so, how'd you fix it (ie. getting it back to "Locked")?
Sidenote: I hope Con247 doesn't see this or he's liable to kill me. LOL BUT IT WASN'T MY FAULT, THEY SENT ME A BAD PHONE WITH A PROXIMITY SENSOR ISSUE!!! LOL
To show locked as well, you have to do S-off procedure again. It changes the bootloader status to locked during the process.
Then repeat what you did; revert to stock again and S-on procedure again.
PhantasmRezound said:
To show locked as well, you have to do S-off procedure again. It changes the bootloader status to locked during the process.
Then repeat what you did; revert to stock again and S-on procedure again.
Click to expand...
Click to collapse
I got you. We'll see what happens.
PhantasmRezound said:
To show locked as well, you have to do S-off procedure again. It changes the bootloader status to locked during the process.
Then repeat what you did; revert to stock again and S-on procedure again.
Click to expand...
Click to collapse
Worked...Thanks.
Hey,
I have a Telus Amaze 4G and I have lost my radio. Phone says it has an unknown Baseband/IMEI. Not sure where I went wrong/ lost my radio but this is a run down of what I've done to my handset so far:
- Rooted
- Flashed CWM recovery.
- Flashed EnergyRom.
- Sent phone to HTC because of suspected warranty issue. (Wouldn't Charge)
- Phone returned un-repaired from HTC.
- Charged battery externally, phone finally booted.
- Replaced CWM with 4EXT.
- Ran the Telus GB RUU exe from windows.
- Did the OTA ICS from the phone.
- Attempted upgrade to SpeedRom, failed because the OTA had failed, didn't realize this until the next around, this is where I think it went wrong. Had done a full wipe of all partitions, except SD from 4EXT in the process.
- Re-applied original Telus GB RUU.
- Re-applied Telus ICS OTA. this is when I realized I had no radio. I had not put in my SIM-Card since the phone was returned from HTC so not exactly sure when it stopped working but the OTA had installed correctly this time.
- Re-rooted.
- Did the wire-trick and obtained S-OFF.
- Flashed the latests JP hboot.
- Used fastboot to flash several radio.img files from various TMO and Telus RUUs, nada.
- Flashed the T-Mobile ICS RUU via hboot, still no radio.
- Extracted the rom from the Telus GB RUU and applied that via hboot, still no radio.
The only thread I could find where someone had mentioned the missing baseband on an amaze 4g, the only suggested fix was to reflash a stock, GB rom but that didn't work. Now I am at a loss at to what I could try next.
Any suggestions would be greatly appreciated.
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Jay_Rulen said:
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Click to expand...
Click to collapse
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Dark Nightmare said:
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Click to expand...
Click to collapse
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
inluck said:
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
Click to expand...
Click to collapse
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
inluck said:
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
Click to expand...
Click to collapse
I can't say, just keep your fingers crossed that it doesn't.
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
inluck said:
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
Click to expand...
Click to collapse
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
inluck said:
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
Click to expand...
Click to collapse
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
inluck said:
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
Click to expand...
Click to collapse
It's not the hboot. I gotta find the s-on thread, since you have to be on a stock bootloader before you s-on. I probably missed something.
Sent from an Amaaaaaazing place :-D
http://forum.xda-developers.com/showthread.php?t=1647728
I just remembered another trick as well, when you s-off the device, it relock your bootloader but it says "locked" not relocked, therefore when you s-off, do not flash the jb hboot when they ask you if you wanna flash it, then simply s-on via the fastboot command, voila!
Sent from an Amaaaaaazing place :-D
So I am trying to Un-Root my HTC DNA, and I was following these steps
http://forum.xda-developers.com/showthread.php?t=2017525
But when I'm running the RUU, i get an error 155: Unknown error.
Telling me to get the correct ROM Update Utility, but i can't find it anywhere but on that website.
Once the RUU Update has failed and I restart the phone,it goes straight into boot menu with ****TAMPERED*****. ******RELOCKED******, and *******Security Warning******* At the top and when I try to do a factory data reset on the phone, it goes into the fastboot menu, with the same notifications uptop.
Any idea what might be going on?
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
I have tired to do it in all three of my USB Ports.
All i can say is try starting the RUU.exe and have your phone booted normally. not in fastboot. it worked for me both ways. might be something to try. If it fails again try re-downloading the file, rinse and repeat.
cmay227 said:
RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed
this is the name of the RUU u need. not sure about the errors. just google uroot and relock dna and it should be the top link. or just look in rootzwiki
it looks like you got the correct RUU, try a different usb port. How far does it go? does it even start. make sure your usb debugging and booted in fastboot.
Click to expand...
Click to collapse
Pretty sure you can't relock unless you used htcdev.
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
jonesin said:
As Adryn said if you used htcdev I'm pretty sure we can still "relock" but the exploit has permanatly changed the CID of all our phones. So fastboot oem lock still works and the ruu will revert the phone to its "stock" state as in factory shipped software and bloat but the bootloader will still reflect that it has been tampered with and the same token can be used to unlock again immediately afterward. So what I'm saying to all others is that the exploit is irreversible. There were a couple guys toying with it in the irc yesterday. But unless you absolutely have to do this theres really NO reason because you won't be able to cover the tracks of the hacking you've already done to your phone.
Click to expand...
Click to collapse
To me the main benefit of running the RUU was to get rid of the Tampered status in the boot loader screen. But your right it will say Relocked instead of locked. no way around that......so kinda pointless warranty wise.just removes root
Well I'm in the process of redownloading the RUU file.
I am still kind of curious, how come I can't reset to factory default through the boot loader or though the settings -> restore feature? Does it have to do with being rooted?
If you don't have a good reason to unroot, I would encourage you to wait. Those have have unrooted, and relocked, have had problems unlocking a second time.
I've locked and relocked many times and It was a pain in the ass to get unlocked status back. I would get the unlock prompt on the phone and choose yes but it ended up always still saying relocked. I finallly read to shut phone down completly before going into fasboot. I was just choosing restart. Have not had a issue unlocking since. Unlock code takes everytime.
Sent from my HTC6435LVW using xda app-developers app
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Mazer_R said:
OP, if you're attempting to get the 'locked' message on the bootloader back, you won't (as others have stated,) but if you're trying this to get your warranty back, the persons at Verizon won't look at this when you return the device. Neither will the people at the Verizon corporate office. All they will do is completely reflash the device including bootloader and that will be that.
Mazer
Sent from my rooted and debloated Droid DNA.
Click to expand...
Click to collapse
Thanks from the reply. I mainly wanted to un-root it to 1) Check for updates an 2) Restore to OEM to see if a problem I am/was having with my Aux jack could have been fixed that way.
I managed to get it to work...I think what the problem was, was that I had PDANET installed, so when the phone rebooted to flash the ruu, Pdanet started and caused the flash to fail. I disabled Pdanet and any other non-essential programs that were running in the background on my laptop, and the flashing worked.
I wasn't too worried about the root or the unlocked status because I'll be returning it under the 14 day guarantee.
Once I've unlocked boot loader and rooted the phone, is there a way to revert back to stock un rooted and un locked should I need to use sprints TEP?
Yes all you need to do is Run an RUU.
centro714 said:
Once I've unlocked boot loader and rooted the phone, is there a way to revert back to stock un rooted and un locked should I need to use sprints TEP?
Click to expand...
Click to collapse
just flash the latest (or your current RUU if you are s-on) and re-lock your bootloader too. You can also make the phone s-on if you are s-off currently, but to tell you the truth in the past 6 years the number of phones i had replaced by sprint when I have TEP they never ever cared. I had a my m8 replaced by them and when I was showing them how the power button would not work all the time the phone was unlocked and running the google play addition rom.. lol They dont really care. Certainly flash the RUU but the relock and son are up to you. They take two seconds to do and can be undone easily if you for some reason do not get the phone replaced.
To relock bootloader - I believe this thread requires s-off but I think it will give you a Locked status instead of the "relocked"
http://forum.xda-developers.com/one...er-htcdevs-t3092036/post60334159#post60334159 - Thank @scotty1223 for the thread
To go from s-off to s-on
fastboot oem writesecureflag 3
***EDIT*** Important - in those threads be careful about what RUU you flash when they tell you do especially if you are s-on. I mean worst case you brick and you're getting the phone replaced but still just an FYI. Flash only the RUU of your current firmware version if s-on
I won't bother asking what s on and off and ruu are lol, I'll do that research myself.
Just glad to see some activity here.
Thanks for the help. Phone is awesome now on bad boys rom!
centro714 said:
I won't bother asking what s on and off and ruu are lol, I'll do that research myself.
Just glad to see some activity here.
Thanks for the help. Phone is awesome now on bad boys rom!
Click to expand...
Click to collapse
Good Good, may I ask? Why the TEP claim/replacement? if its running well.
deakelem said:
Good Good, may I ask? Why the TEP claim/replacement? if its running well.
Click to expand...
Click to collapse
Just preparing for the future. If there's no way of reverting back to fully stock, then I may cancel tep, but all looks good now.