please help me. i dont know what to do with this cell... anyhow i managed to get it into this screen...
it would keep restarting after displaying htc quietly brilliant.
i have no idea what was done to this cell as i got it lying around in my closet.
What do you mean you got it lying around in my closet? You don't know what you did to it in the past?
Sent from my Evita
no actually my cousin might have screwed up my cell and kept it back...
timmaaa said:
What do you mean you got it lying around in my closet? You don't know what you did to it in the past?
Sent from my Evita
Click to expand...
Click to collapse
Well I think the first thing you should do is talk to your cousin and find out exactly what he did to the device, then you can report back here.
Sent from my Evita
is there any other way through which we can come to know what can be done??? such as an odin thing which i used to do in my samsung note 1 or 3???
timmaaa said:
Well I think the first thing you should do is talk to your cousin and find out exactly what he did to the device, then you can report back here.
Sent from my Evita
Click to expand...
Click to collapse
To know what needs to be done I need to know the history of the device. Odin is Samsung only, there is no HTC equivalent. Who got the phone to this point, you or your cousin? You need to find out what he's done.
Sent from my Evita
Well, one problem is that the screen is cracked.
Seriously though, the phone for some reason or other cannot load into the OS, and is stuck in bootloader. Other than that, not much else can be determined if you don't know the history of what was done.
pvirus86 said:
is there any other way through which we can come to know what can be done??? such as an odin thing which i used to do in my samsung note 1 or 3???
Click to expand...
Click to collapse
Nope. You need to know the history of the device. There is an HTC-specific recovery utility. But running it on a device with unknown history can brick the phone permanently. Particularly since the device is definitely tampered (as shown on the first line of the screen).
Also, the phone's IMEI is personal information, and should not be posted on the internet. You should edit the photo to hide the IMEI.
Unlock your bootloader. Sometimes if you have custom installed or fragments of a custom ROM on the device it will boot directly into your bootloader. After unlocking your bootloader you can install a recovery image and sideload a ROM.
yes i asked my brother and he is saying he doesnt remember what he had done to it... if anyone can show me a way to do something ill try it... or else should i take it to some shop to get it fixed.... which would cost me... but first i wanted to get my hands over d expert advise of u all
Return the phone to stock and never let your brother touch any electronic device of yours again.
Sent from my Evita
but can you let me know to revert it to stock. and will i have to do it from windows 7 or my mac os wud work???
pvirus86 said:
but can you let me know to revert it to stock. and will i have to do it from windows 7 or my mac os wud work???
Click to expand...
Click to collapse
This phone is in a dangerous state.. Running the RUU in this state could brick the phone (make it permanantly unusable without a jtag). Though typically that is how one would return a phone to stock.. to be honest, the safest thing to do would be to unlock the bootloader, flash a rom, S-OFF and then return it to stock. If these seem like foreign terms to you, you have a lot of reading to do. Your phone is in a tough spot right now ESPECIALLY not knowing the history regarding what was done. You would need the bootloader unlock token to reunlock that phone if you don't have it, there's very little chance of safely returning that phone to stock.
pvirus86 said:
yes i asked my brother and he is saying he doesnt remember what he had done to it...
Click to expand...
Click to collapse
Brother or cousin, or both? It seems you don't even know who has been messing with your phone. And the person(s) messing with it don't have a clue what they are doing. So its no wonder the phone is in the state it is.
Agree with above that RUU is risky. Better to s-off the phone first.
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader n turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
pvirus86 said:
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader not turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
Click to expand...
Click to collapse
There are detailed instructions available at htcdev for unlocking your bootloader. Once you've done that you need to flash a custom recovery, then you can flash root, then you can get s-off. Check my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita
pvirus86 said:
Thank u all for the prompt replies, I have played with Samsung but not with HTC. But I can try to unlock the bootloader n turn d s-off. Can I get an step guide for HTC. The thing was I have many cellphone that I buy and use it very rarely. Majority I use is my note 3.
Click to expand...
Click to collapse
Every device manufaccturer/model has different root methods. If you want to root the phone, you have to put the time in to learn the correct process. There is no shortcut. You won't find a step-by-step guide for the entire process, because of the different carrier version and firmware updates (root method, etc. differs for each). But all the resources you need are sticky at the top of either this Q&A forum section, or General section.
hi i tried to get to unlock the bootloader from the HTCDEV site. first of all the HTC ONE X wasnt on the list so i selected other supported devices
then followed the steps and got the following error
Error Code: 160.
Error Reason: MID Not Allowed.
now what does this mean??
That means you have the original CID still, which means you should be able to run the 3.18 RUU without any problems. Check your CID by issuing this fastboot command:
Code:
fastboot oem readcid
Sent from my Evita
yes i had issued this command after finding it in one of the websites and this was the result which i got
cid: CWS__001
or cid: c??__001
i forgot the exact two letter after C. i think it was CWS
You have the original at&t CID. That means you can run the 3.18 RUU without having to unlock the bootloader and get s-off first.
Sent from my Evita
Related
Hi,
Would it be possible to unlock the bootloader without going thru HTCDev?
I found this thread regarding a universal HTC unlocker here: http://forum.xda-developers.com/showpost.php?p=24324567
Would this work for the One XL?
HTC Dev site does not show One X, Select “All other supported models” if you cannot find your phone in this list
Has anyone done this with the One X
Pumpiron579 said:
HTC Dev site does not show One X, Select “All other supported models” if you cannot find your phone in this list
Has anyone done this with the One X
Click to expand...
Click to collapse
This will likely work, but my question was about unlocking the bootloader without using HTCDev.
This is even more important now, as reports are that HTC is denying warranty if the bootloader is unlocked via their site.
GameGod72 said:
This will likely work, but my question was about unlocking the bootloader without using HTCDev.
This is even more important now, as reports are that HTC is denying warranty if the bootloader is unlocked via their site.
Click to expand...
Click to collapse
I know, I didn't want to start a thread asking that. was just wondering since it is not listed. I wouldn't use that yet, seems like within a week, we will have s-off and more
GameGod72 said:
Hi,
Would it be possible to unlock the bootloader without going thru HTCDev?
I found this thread regarding a universal HTC unlocker here: http://forum.xda-developers.com/showpost.php?p=24324567
Would this work for the One XL?
Click to expand...
Click to collapse
Tried the universal HTC unlocker and it didn't work. Nothing wrong with my phone either after it failed either.
danada said:
Tried the universal HTC unlocker and it didn't work. Nothing wrong with my phone either after it failed either.
Click to expand...
Click to collapse
Bummer. Thanks for trying though.
Hopefully the superb devs on board will figure out a way to do this.
I think it's very possible using the same method, it just needs to be adjusted for the new partition layout of the newer HTC devices.
everything i have read about HTCDev unlocker is that if you return the phone for warranty work with a custom ROM loaded, they will deny it.
BUT, if you have the bootloader unlocked and running the stock rom (return to stock before sending it in), they will process the warranty work as usual.
I still want to find a way around HTCDev, but, just letting you know what i have read
buddy17 said:
everything i have read about HTCDev unlocker is that if you return the phone for warranty work with a custom ROM loaded, they will deny it.
BUT, if you have the bootloader unlocked and running the stock rom (return to stock before sending it in), they will process the warranty work as usual.
Click to expand...
Click to collapse
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
On a previous device I'd owned, after S-OFF they found a way to get rid of the device specific "TAMPERED" logo in the bootloader. I suspect there would be a way to do so on this device as well.
I can't remember which device it was, though...
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
Its probably a combination of the device being registered for unlock on HTCDev and something on the device.
I'm pretty sure, sooner or later, the devs will figure out a way to return the device to a "clean" state. All the more reason I would love for a way to get this done without going thru official channels.
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
cause of illegal software,
Look,
We are contacting you concerning the HTC One X which you returned to us due to there being a yellow tint on the display. As you are aware we sent the handset to the HTC service centre as it was not possible to have it classed as a DOA (dead on arrival), due to the bootloader being unlocked and illegal software having been installed. The HTC service has confirmed that illegal software has been installed on the handset at some time by yourself resulting in the warranty being invalidated. Simply unlocking and relocking the bootloader would not have invalidated the warranty.
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
When you flash custom software it trips a switch that displays "Tampered" on the HBOOT screen, whether or not you flash stock back on and relock the bootloader.
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
Actually read the posts though. The guy didn't send it to HTC.
HTC will still service the device, even after an unlock.
OK, on topic... I just looked through the HTCdev process for the first time. It seems that we should start by comparing device identifier tokens and unlock files, right?
Perhaps there is a pattern to them or we can figure out how to generate one from the other? Maybe the device identifier token has nothing to do with the unlock file apart from HTC wanting to record a unique identifier of the phone?
Has anybody tried using an unlock file from a different user's phone (of the same make/model)? That would be a huge break-through if it was that easy!
I would think somebody would have tried this, but up until now, nobody seemed to have a problem following HTC's process to get their bootloader unlocked.
Thanks,
Billy
Pumpiron579 said:
cause of illegal software,
Look,
We are contacting you concerning the HTC One X which you returned to us due to there being a yellow tint on the display. As you are aware we sent the handset to the HTC service centre as it was not possible to have it classed as a DOA (dead on arrival), due to the bootloader being unlocked and illegal software having been installed. The HTC service has confirmed that illegal software has been installed on the handset at some time by yourself resulting in the warranty being invalidated. Simply unlocking and relocking the bootloader would not have invalidated the warranty.
Click to expand...
Click to collapse
If you read the whole chat conversation, the tech was instructed to call it "illegal" software. Doesn't mean it was in fact illegal.
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
ughhh i cant believe htc is being gay
i guess im not going to buy one and wait for a gs3
Im sure someone will make a software hack or a hardware one like the SGSII.
JeepFreak said:
OK, on topic... I just looked through the HTCdev process for the first time. It seems that we should start by comparing device identifier tokens and unlock files, right?
Perhaps there is a pattern to them or we can figure out how to generate one from the other? Maybe the device identifier token has nothing to do with the unlock file apart from HTC wanting to record a unique identifier of the phone?
Has anybody tried using an unlock file from a different user's phone (of the same make/model)? That would be a huge break-through if it was that easy!
I would think somebody would have tried this, but up until now, nobody seemed to have a problem following HTC's process to get their bootloader unlocked.
Thanks,
Billy
Click to expand...
Click to collapse
Maybe nobody wants to be on topic? I guess I'll give this a try next week when I get my phone =\
Billy
Hi guys im new getting my one x from ma bell, in a few days. Im coming from an amaze, amaze forums.
You guys need to understand, htc WILL know if anything was "tampered" with.
Most software bares a timestamps, or something similar that will let them know when and what the phone was flashed with. So even if you reflash, its going to show a timestamp of sorts.
Htc put the disclaimer of warranty denial to give them an option im sure.
I returned several phones rooted, bricked to T-Mobile, and they never said anything. Its like a car, the manufacturer can void your warranty for any "mods" you do....
I hope every one here gets some patience, and not worry about rooting, bootloader unlock , bloatware.
For now it is what it is... and it's only been
... a day???
We will get this ***** unlocked, romed and kick some ass... just gonna take time... and from the looks of it we have some brilliant devs here! .
Be patient and give it some time guys, check out the amaze forums and see what happens when people start whining about stuff going to slow or not happening ( not calling any one a whiner, so chill)... the devs start disappearing.
Ok im done... probably not the right place for intros but ah well!!!
And remember
.its just a gdam phone!
.
Sent from my DROIDX using xda premium
Hey, I'm kind of a noob here. Where do I get fastboot.exe from? Im stuck on step 11 in the "[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev" thread
you need to download the android sdk, it has it in there as stated in the htcdev unlocking instructions
Thanks, I was able to get it to work once the one click unlock tool was posted.
Sent from my HTC One X using Tapatalk 2
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
xeper said:
Stupid questions but I can't seem to find simple answers:
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
b) how do I tell what version I have?
c) does/can this get rid of the "tampered" on the bootloader screen?
d) does/can this give us full S-Off?
Click to expand...
Click to collapse
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
HydroSkillet said:
I'm assuming you're on the HTCDEV part because if you're not using the tool and you're asking this question you're doing it wrong.
that being said, it should come in the android SDK, if it doesn't then just copy the exe file out of the tool folder that you unzipped.
Edit, I see you already got it answered.
---------- Post added at 10:43 AM ---------- Previous post was at 10:39 AM ----------
a) do I need to be on a specific FW version or have a specific bootloader to unlock?
--- i did it on 1.7, although I think 1.82 works
b) how do I tell what version I have?
--- settings > about phone > Software
c) does/can this get rid of the "tampered" on the bootloader screen?
----- absolutely not, look at the screenshots on the OP in the dev section
d) does/can this give us full S-Off?
-----no
Click to expand...
Click to collapse
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Maybe, who knows on the "tampered" and yea you void your warranty so if you are afraid of hardware failure then don't do it, or but insurance on it. That's what I have, if I brick it cost me 100.00 rather than 600.00.
"Waiting for device"
Every attempt and different ways always brings me to that part. I have does the oneClick supercid program and I've even gone through the HTCDEV website 6 times now. after it reboots into boot loader mode and I direct it to the folder with the 3 files in it through cmd and I get to the final step to where it says "Waiting for device" trying to get the cid codes for my phone and nothing. I am at the end of my ropes of how to unlock codes. if anyone can help me or walk me through via text or video I would be so happy. I just want this thing finally unlocked and over with.
I take it your on this step?
11. Type "dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up type "fastboot oem readcid" and hit enter. It should read "11111111".
12. Next type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there. Choose "All other supported models" from the dropdown menu.
If so, Step 11 is kinda tricky worded after you type the command to reboot the device. Just don't even wait put the second line in "fastboot oem readcid" the batch file will wait for the phone. I hope this helps ya I had the same problem before And booted the phone back up and tried again but last time I just rebooted with the command then right after than put in the second command.
xeper said:
Thanks for the info.
Another couple of dumb questions:
Will we ever be able to get rid of that "tampered" notice?
How does that notice effect me should my phone, say, fall and break its screen or have some other hardware-related failure? (I'm a klutz)
What does SuperCID mean and how does that effect me?
Click to expand...
Click to collapse
Devs will find a way to remove tampered label once we find S-OFF. After the device has been "tampered", if your phone breaks and you send it to HTC warranty, they will not replace your phone if you have flashed a custom ROM on it. How they know you've flashed a custon ROM, I'm not sure.
SuperCID is the development CID designed to work on HTC phones. It allows you to unlock your bootloader through HTCDev.com. It also allows you to flash RUUs, because RUUs check CIDs on phones to determine whether the RUU is a valid ROM for your phone. However, it has been said this is hit/miss.
Don't take my exact word for it, use GOOGLE.COM.
I waited for the one-click tools, and I'm glad I did.
Forgot to mention
my Main computer is my iMac and I have a windows 7 laptop I switch to for my flashing/rooting etc... because I am not good with terminal or adb steps after a few seizures I've had recently. So shell stuff is completely useless to me. I can follow the steps on the briefmobile website then I have the HTCDEV account. but still at a lost.. for some reason.
I never got a 1111111 or whatever message
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
hazmatik said:
It just went straight to "Waiting for/on device" I tried again even attempted somewhat the hex edit way. but I never saw any "CW__111" or whatever in the file that I threw into HxE I think that was the hex program I used on my laptop. To frustrated to check in other room. I even kept looking at 210 section and nothing. So I'm not sure what is going on that won't let me unlock. Maybe I'll check youtube to see if there is a video on unlocking the bootloader.
Click to expand...
Click to collapse
You should just use the one-click Super-CID tool in the Developers section, it's much faster and hassle free.
Thanks but that option never succeeded
I finally got it to unlock and get past that "Waiting for device issue" it seems even though I had my device plugged in and all the android and HTC drivers installed, it never registered that it could sense android 1.0 plugged in. so I had to manually right click and force it to install the drivers and it finally found device. low and behold it clicked and I got my email instantly right afterwards. So now I need how on installing CWM any ideas how to? be I am wanting to try out Team nocturnal's Rom for a little bit to see what it has to offer. Thanks for comment also by the way.
Hi all,
Again I've searched everywhere and can't find this so I must post my second in 1.5 years of lurking.
I'm usually good at breaking in to my phones but turns out I know only enough to be dangerous. I think the backup.ab file is my last option before I give up on this phone. Basically I can't re-unlock the bootloader due to an error 150 after making a mess of my phone and supercid (returned to stock values) etc. I'm hoping a full restore will help me pass the bootloader unlock however I didn't learn about it until recent so don't have one. Something is different about the RUU's maybe or possibly htcdev doesn't give out more than one unlock code.
Feel free to help if you can by offering a link to an s4 backup.ab file, another way to unlock without htcdev, or using this code...
<<<< Identifier Token Start >>>>
1700AFDC35C0F82BDA1C7D4E2DA1701C
D6CA28DD3B33DCB09D4250509789B86D
4C7BFF879A3CA0BA463E620CCEE9BE8D
A7203AB6C13F99932FD0CA9B9E2E2373
550463EFED6DF4D329000585DB278470
A753C1F674C0969BD5E3229DF526FBEC
C949BA53604319420CE0441874446C78
7B3356AB59746E140A1FD50207A45BF6
93A3F204FB111045DD77379E930FD675
667463DCCDDFA1400761799EF37144ED
1EA59F82CACA2022AD20F5342658F891
8EFFE8CAC5A619F7CA1F47CF22BD6B30
8FA33533B08831B1ECEB012B55D11955
21293A0337576353E621CCA6D5A50CE8
16353F9F2B0EEE1A66D62E6D336A790E
D4C6B64A99889BC3CF66367451564F84
<<<<< Identifier Token End >>>>>
Thanks!!!!
i've got the same problem mate, error 150, this happened after downgrading the bootloader, the phone works great, butt i can't unlock it. all the ruu's that i installed finished well butt didn't repaired what ever happened to the phone
Camboozle said:
Hi all,
Again I've searched everywhere and can't find this so I must post my second in 1.5 years of lurking.
I'm usually good at breaking in to my phones but turns out I know only enough to be dangerous. I think the backup.ab file is my last option before I give up on this phone. Basically I can't re-unlock the bootloader due to an error 150 after making a mess of my phone and supercid (returned to stock values) etc. I'm hoping a full restore will help me pass the bootloader unlock however I didn't learn about it until recent so don't have one. Something is different about the RUU's maybe or possibly htcdev doesn't give out more than one unlock code.
Feel free to help if you can by offering a link to an s4 backup.ab file, another way to unlock without htcdev, or using this code...
<<<< Identifier Token Start >>>>
1700AFDC35C0F82BDA1C7D4E2DA1701C
D6CA28DD3B33DCB09D4250509789B86D
4C7BFF879A3CA0BA463E620CCEE9BE8D
A7203AB6C13F99932FD0CA9B9E2E2373
550463EFED6DF4D329000585DB278470
A753C1F674C0969BD5E3229DF526FBEC
C949BA53604319420CE0441874446C78
7B3356AB59746E140A1FD50207A45BF6
93A3F204FB111045DD77379E930FD675
667463DCCDDFA1400761799EF37144ED
1EA59F82CACA2022AD20F5342658F891
8EFFE8CAC5A619F7CA1F47CF22BD6B30
8FA33533B08831B1ECEB012B55D11955
21293A0337576353E621CCA6D5A50CE8
16353F9F2B0EEE1A66D62E6D336A790E
D4C6B64A99889BC3CF66367451564F84
<<<<< Identifier Token End >>>>>
Thanks!!!!
Click to expand...
Click to collapse
alexskin said:
i've got the same problem mate, error 150, this happened after downgrading the bootloader, the phone works great, butt i can't unlock it. all the ruu's that i installed finished well butt didn't repaired what ever happened to the phone
Click to expand...
Click to collapse
look through you email archive for the original mail from htcdev & re-download the unlock_code!
rustykwak said:
look through you email archive for the original mail from htcdev & re-download the unlock_code!
Click to expand...
Click to collapse
it does not work, i've tried it. although i've got a few nandroids and revoverys from when i has unlocked, and i might have one prior to unlocking, i don't know if it could help
alexskin said:
it does not work, i've tried it. although i've got a few nandroids and revoverys from when i has unlocked, and i might have one prior to unlocking, i don't know if it could help
Click to expand...
Click to collapse
you have the original unlock_code? if so keep trying I have heard a few people had to try it several times before the unlock worked!
rustykwak said:
you have the original unlock_code? if so keep trying I have heard a few people had to try it several times before the unlock worked!
Click to expand...
Click to collapse
i't won't work since the token is based on the old cid, witch was from spain orange, and know i have the free spain cid
alexskin said:
i't won't work since the token is based on the old cid, witch was from spain orange, and know i have the free spain cid
Click to expand...
Click to collapse
I'm in the same boat. I have the original unlock code as I thought it would always work but my token has changed 2 times noticeably in the last week so I don't think it will work. Also I have a full backup so have my original boot and recovery but can't write them. That's why I asked about the backup.adb file since I thought maybe it will bypass security and bring me back to stock and perhaps original token.
How can you obtaain a backup.adb?
cicciocant said:
How can you obtaain a backup.adb?
Click to expand...
Click to collapse
That's what I'd like to know but you can make your own prior to unlocking and rooting or whatever you do with adb backup command and follow directions on your phone. It was pretty quick and painless with my new android phone. Do a search and you'll see more info on the subject.
I have to do a 14 day exchange on my phone. Bought it at Best Buy. I have a few dead pixels amongst other things. I'm very familiar with ADB, bootloader, custom recovery, and OS. Right now, my M8 is unlocked, s-off , and rooted. It's running a custom rooted RUU Rom. Before I attempt it, what would be the best way to get my phone back to its original state? Does Best Buy even care? Does my account get linked to HTC when it is sent back and I'm charged $600 for it being s-off? If I understand it correctly, and I'm asking if this is right, I would want to find and download and flash the original RUU through ADB, find and type in a line of code to Lock bootloader, and find and type in a line of code to s-on, right? Or does best buy not even check or care?
BygSii said:
I have to do a 14 day exchange on my phone. Bought it at Best Buy. I have a few dead pixels amongst other things. I'm very familiar with ADB, bootloader, custom recovery, and OS. Right now, my M8 is unlocked, s-off , and rooted. It's running a custom rooted RUU Rom. Before I attempt it, what would be the best way to get my phone back to its original state? Does Best Buy even care? Does my account get linked to HTC when it is sent back and I'm charged $600 for it being s-off? If I understand it correctly, and I'm asking if this is right, I would want to find and download and flash the original RUU through ADB, find and type in a line of code to Lock bootloader, and find and type in a line of code to s-on, right? Or does best buy not even check or care?
Click to expand...
Click to collapse
You should check out Scotty's thread in this forum.
http://forum.xda-developers.com/showthread.php?t=2729139
He is quite knowledgeable and gives a good discussion of what steps are appropriate/reasonable/safe to take in these situations.
Ok, I'll check out it. I also found this to install rooted original firmware back onto the HTC M8, it might help with my situation, or it might help with others http://forum.xda-developers.com/showthread.php?t=2727831
I purchased a Verizon htc one m8 off some guy and i went home erased the phone a 2nd time and realized something called SuperSu was installed and i knew right then & there this fool gave sold me rooted phone so i click the app and pressed full unroot then restarted the phone the app was erased... Restarted the phone in bootloader mode or what ever and the top says Unlocked and S-off but no tampered sign and the software status says official so the questions i have are
1) Do i have to re root this phone in order to lock the bootloader and return to S-on?
2) Will re locking the bootloader or returning to S-on brick my device or any chance of bricking my device ?
3)If my software status says official is that good or bad ?
4) Will i be able to install future updates at all if i leave the device like it is now ?
Thnak you for taking your time to read this.
Why would you want to relock it? Learn how to do things this way and take advantage is the fact that you aren't locked down to Verizon's chains.
...
silver04v said:
Why would you want to relock it? Learn how to do things this way and take advantage is the fact that you aren't locked down to Verizon's chains.
Click to expand...
Click to collapse
well i pay 11 dollars for a warranty i need my warranty lol...
MH1994 said:
well i pay 11 dollars for a warranty i need my warranty lol...
Click to expand...
Click to collapse
Verizon doesnt care if its rooted or S-OFF.
If I have to send a phone back I send it with my own ROMS on them.
They have never said anything.
As well, I dont recommend turning S-On as you have a much greater chance of bricking the phone.
I would just leave it as it is... Well, actually... I would load my ROM
Well lol
scrosler said:
Verizon doesnt care if its rooted or S-OFF.
If I have to send a phone back I send it with my own ROMS on them.
They have never said anything.
As well, I dont recommend turning S-On as you have a much greater chance of bricking the phone.
I would just leave it as it is... Well, actually... I would load my ROM
Click to expand...
Click to collapse
well software wise i think they would i mean if my software messed up it would be "my fault" lol...i dont think they would replace my phone