Database Info

[Q] Stock Sensation stuck on white HTC screen and bootloop

Thanks

spturner said:
I have also tried the HTC bootloader unlock on the HTC website, but after following the instructions exactly, it failed. I tried twice.
Click to expand...
Click to collapse
when you are saying it failed what do you mean exactly?
i would suggest you to use ganeshp's guide from general section to S-OFF your device but unfortunately your device is not in working condition

I would say its time to retire your sensation... If you cannot unlock the bootloader and a factory reset does not help then I dont think there is much more that can be done.

I would say... Find the cid then based on it... Find the proper ruu and run it...
Sent from my HTC Sensation using xda premium

The failure I get when trying the HTC unlocking tool is the same as a lot of people have reported

spturner said:
The failure I get when trying the HTC unlocking tool is the same as a lot of people have reported -
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.170s
I've triple checked the process and am sure I'm doing it right.
I bought the phone on ebay a few months ago and it's been working fine up until now.
A few things about the phone however -
1. It was sent to me with a box, but the IMEI number on the phone didn't match the number on the box. I've since found that maybe this could be due to an HTC motherboard repair when it was under warranty (I understand there was a high dust under the screen failure rate on these models ?) This could also explain why the HTC unlock doesn't work ?
2. When I got the phone, I did a factory reset and the only language packs available as part of the factory reset were Asian ones, (Thai etc), but after a full reset, it operated fine in English.
3. The phone is sim-free
Unless anyone can come up with any solutions it sounds like it's time to take a sledgehammer to the thing, and also a mental note to NEVER buy HTC again. Time for the Nexus 4 I think.
Thanks
Click to expand...
Click to collapse
i think that causes the failure because of different imei after motherboard's replacement
if i remember well there is somewhere a thread of what to do when htcdev fails after motherboard is being replacing
and it comes with different imei
but i don't remember where
give it a try and search it

I have none of these, as the phone is completely stock and of course I can't get into the phone to install things or change settings.

spturner said:
Thanks, yes I had already searched and found various ways to do this, but it seems most do not work, or you at least need to have other things installed and working, or USB debugging enabled.
I have none of these, as the phone is completely stock and of course I can't get into the phone to install things or change settings.
Here comes that sledgehammer ! Actually, maybe I'll just fry it in a microwave and post the video on youtube.
Goodbye HTC...you pile of junk phone manufacturer.
Click to expand...
Click to collapse
Nooooooooooo... :silly:
as i said find the proper RUU ...from here and flash it
TIP: RUU can be flashed from bootloader and no adb is required ..thus usb debugging enabling is not required

For the moment, the sledgehammer is put away as it seems you guys might just get me sorted...maybe ?
Thanks

Any further assistance will be much appreciated
Thanks

ask FootBall for the non xe RUU ...

[Q] Is there a working Bootloader unlock for 9.16.XT926 ? Please?

I have tried every method I can find on here and none of them work? Would really like to try some custom roms, I have never had an android phone I didnt have full control over, I hate it! Am I missing something? Or am I just screwed?
Thanks! If It can't be unlocked I will be looking to trade for a phone that I can work with.. maybe a Nexus or something.

if you are on 9.16, you should be able to unlock the bootloader. you must not be following the directions properly or something because the unlock tool.app (i think) works. i used it no problem.
perhaps you could post some links to what you have tried and a screen shot of your system version screen so we can have a look at things.

Here is a screenshot of my system info. The only thing I have ver done is rooted it. So it shouldn't of been upgraded than downgraded.
I have tried motocolypse method many times, and get an error:
[*] Device found.[*] Pushing unlock tool...
3738 KB/s (38280 bytes in 0.010s)[*] Unlocking phone...
[+] TrustZone target address resolved to 2a020a02
[-] TrustZone write failed: -11.[*] Cleaning up...[*] Unlocking complete. Rebooting into bootloader mode.[*] Press enter once the phone has rebooted into bootloader mode.
I also have read you should get an SU prompt while running the unlock? I never do. But I have Root, with SU working.

BruteSource said:
Here is a screenshot of my system info. The only thing I have ver done is rooted it. So it shouldn't of been upgraded than downgraded.
I have tried motocolypse method many times, and get an error:
[*] Device found.[*] Pushing unlock tool...
3738 KB/s (38280 bytes in 0.010s)[*] Unlocking phone...
[+] TrustZone target address resolved to 2a020a02
[-] TrustZone write failed: -11.[*] Cleaning up...[*] Unlocking complete. Rebooting into bootloader mode.[*] Press enter once the phone has rebooted into bootloader mode.
I also have read you should get an SU prompt while running the unlock? I never do. But I have Root, with SU working.
Click to expand...
Click to collapse
Trustzone fail is telling me that you've updated at one point. When I ran the exploit on my M, I did have to enable SU access, but I don't even think you're getting that far. Do me a favor and boot into your fastboot screen and post the pic or tell us what date is on there.

2013-04-25
Sent from my QMV7A using XDA Premium HD app

BruteSource said:
2013-04-25
Sent from my QMV7A using XDA Premium HD app
Click to expand...
Click to collapse
if you updated then downgraded it would most likely boot loop so i doubt that is an option.
try uninstalling whatever superuser app you use and install a different one. you wont loose root.
just trying to make sure the app gets root. there arent too many options as to why this wont work.

Now it says permission denied and reboots. I got Chains SU instead of the cwm one..
Sent from my QMV7A using XDA Premium HD app
Doesn't... "[*] Device found.[*] Pushing unlock tool...
3738 KB/s (38280 bytes in 0.010s)[*] Unlocking phone...
[+] TrustZone target address resolved to 2a020a02
[-] TrustZone write failed: -11.[*] Cleaning up..."
Mean that the app got root permission but just failed to work? Permission denied seems to mean it isn't getting root.

BruteSource said:
Now it says permission denied and reboots. I got Chains SU instead of the cwm one..
Sent from my QMV7A using XDA Premium HD app
Doesn't... "[*] Device found.[*] Pushing unlock tool...
3738 KB/s (38280 bytes in 0.010s)[*] Unlocking phone...
[+] TrustZone target address resolved to 2a020a02
[-] TrustZone write failed: -11.[*] Cleaning up..."
Mean that the app got root permission but just failed to work? Permission denied seems to mean it isn't getting root.
Click to expand...
Click to collapse
see if there is a way to update the binaries, i dont recall how each one works specifically.
seems like you dont have root though, or something is jacked with it.
if there is no binary update, you may want to re-root, something seems wrong.

I use like 6 different root apps all the time.. There is no way the binary resolved the TrustZone target address without the app getting permissions..
And by uninstalling my CWM SU I did lose root by the way, can't even reinstall or get root back in adb shell.. now I do need to reroot. Thanks.

BruteSource said:
I use like 6 different root apps all the time.. There is no way the binary resolved the TrustZone target address without the app getting permissions..
And by uninstalling my CWM SU I did lose root by the way, can't even reinstall or get root back in adb shell.. now I do need to reroot. Thanks.
Click to expand...
Click to collapse
i have changed root apps many times and never lost root, frequently the one i dont like is included with the root tool and i change it afterwards.
uninstalling the app wouldnt take the code out of the system.
btw, if you lost root then how did it resolve the tz target addy the second time?
you said there is no way it can without root.

That was a paste from my previous post.. And how do you know what root method I used? I appreciate you trying to help but if it was a perms problem it wouldn't have even gotten to the trustzone error.
Sent from my QMV7A using XDA Premium HD app

BruteSource said:
That was a paste from my previous post.. And how do you know what root method I used? I appreciate you trying to help but if it was a perms problem it wouldn't have even gotten to the trustzone error.
Sent from my QMV7A using XDA Premium HD app
Click to expand...
Click to collapse
try this http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/

That's the same exploit.. The only one. The one Verizon fixed. Same batch file even. Only known method.
Sent from my QMV7A using XDA Premium HD app

BruteSource said:
That's the same exploit.. The only one. The one Verizon fixed. Same batch file even. Only known method.
Sent from my QMV7A using XDA Premium HD app
Click to expand...
Click to collapse
sorry, i thought one initiated from an app and one ran through the pc. same exploit i know, but different method, thought it might work.
ohh well

bweN diorD said:
sorry, i thought one initiated from an app and one ran through the pc. same exploit i know, but different method, thought it might work.
ohh well
Click to expand...
Click to collapse
Yeah, there are two different ones. There was Motopocalypse the app and it was included in Utility 1.20, I believe. Then there was Motopocalypse the exploit. That's the one I used. OP see if you can find Utility 1.20 and use that to unlock.
edit: It's in 1.21
http://forum.xda-developers.com/showthread.php?t=2307439

Yeah utility uses the exact same thing, motocolypse or however you spell it, I still tried it. Literally launches the exact same bat. Still think it's weird I get no root prompt, but I know it's getting root cause of the trusted zone error. Oh well I'm gonna give up and wait for kitkat ota that was announced, just no date yet.
Sent from my QMV7A using XDA Premium HD app

Unlocked by motorola
Why you don't use the Motorola bootloader unlock service?
This is very easy and safetly...
Try by the link:
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
Best wishes,
Cleiton

Because its only for developer versions of the phone? This has been well documented on these very forums But I did try a while ago for the hell of it... To no avail of course.. Since my phone is not a developer edition.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app

cleiton.a said:
Why you don't use the Motorola bootloader unlock service?
This is very easy and safetly...
Try by the link:
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
Best wishes,
Cleiton
Click to expand...
Click to collapse
You can only use that on the 925 or Developer's editions of the 926.

I think I bricked my HTC One X AT&T

Hello everyone,
I am in trouble but not sure if I bricked my HTC One X AT&T hboot 1.09 or not
Here is what happened:
I had Android 4.0.3 running and rooted with bootloader unlocked.
S-ON for sure.
Yesterday I tried to install custom rom or I thought if anything wrong goes bad I would upgrade it to the latest
4.2.2 from HTC.
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
the only thing my device is doing now is just booting to the screen where HTC in green and the red text beneath it or I can go to the
bootloader menu.
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
I wiped everything from the recovery and then locked the bootleader and now I am really really stuck.
just the bootloader is showing.
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Is my device done and I should through it away or there is a hope of fixing it?
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Please guys, any suggestion? I am all for fixing it.
It was a stupid mistake ahhhh.
Thanks in advance.

Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.

Mr Hofs said:
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Click to expand...
Click to collapse
Sorry, is there anyway someone can move this thread to the appropriate forum.
I apologize.

I will report this one to get it moved. Good luck in the correct section

Moved to: AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting.
(mod team)

Looks like you've possibly made several mistakes there. First problem is you've been lurking in the wrong forum, which means you've probably been trying to flash ROMs that aren't for our device. Our device forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within our forum. Flashing ROMs/kernels/radios that aren't intended for our device can very easily result in a bricked phone.
I think your phone is fine as long as you can get it into the bootloader. Your problem when you were flashing ROMs is that TWRP 2.4.x and 2.5.x are buggy and are basically useless. This is probably a blessing in disguise if you were attempting to flash the wrong ROM, it probably saved your ass. Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system? I need to know what you were doing that caused your device to falter. Also, don't ever run a jb RUU while you're s-on or you'll definitely brick your phone, doing that (SuperCID + s-on + jb RUU) has a 100% kill rate.
As a piece of advice, I'd suggest you stop "experiencing" with your device because the experiments you've been conducting could have easily bricked your phone on several occasions. You're extremely lucky. It seems to me that you need to do some research about our device and what you can and can't do with it. A good place to start would be my Evita FAQ and How-To Guide For Beginners threads in my signature, and build from there.
Sent from my Evita

You are not bricked. With this phone, as long as the screen comes on, you are almost certainly not bricked. You just don't know how to recover.
shakash3obd said:
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
Click to expand...
Click to collapse
What the heck does "some commands" mean? You need to be specific about the exact steps you took. If you don't know the commands you tried, that is a problem, as it implies you are not being careful while modding the phone.
shakash3obd said:
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
Click to expand...
Click to collapse
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
shakash3obd said:
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Click to expand...
Click to collapse
You can't (and shouldn't) just run any RUU. You should run the proper RUU for your carrier version (AT&T) and with s-on it has to be equal or later then the hboot version on the phone. Also do not run a Jellybean RUU on the phone, since SuperCID + S-on will brick the device on most Jellybean RUUs. You're okay if the screen is coming on, but don't run any RUUs unless somewhere here specifically instructs you to.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).

shakash3obd said:
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Click to expand...
Click to collapse
AT&T warranties phones for 1 year. So you are out of the warranty period, if that is what you are wondering about. And warranty covers manufacturing defects, not damage done by the owner due to their negligence.
Besides, you don't need a repair or replacement. You just need to know how to recover properly from what you have done.

timmaaa said:
Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
...
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system?
....
Click to expand...
Click to collapse
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:

redpoint73 said:
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
Click to expand...
Click to collapse
Thanks for your comments.
I put the command I used in the previous reply.
As far as the version of TWRP, I originally tried the latest one, but it wont flash at at that's why I tried an older version.
Again in my previous reply i said that I am not able to Re-unlock the bootloader.
Yes I am still in hboot 1.09 but don't remember the build number unfortunately.
Because all what I am in is because of my lack of knowledge of custom roms, would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!

shakash3obd said:
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
Click to expand...
Click to collapse
I won't judge you, I'm here to try and help you. Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work. If not, I'm really not sure what you can do. In future, just be careful and make sure know exactly what you're doing before you do it. Fastboot commands have very specific functions and should only be used in specific situations, issuing random commands is a bad idea. I you're unsure about anything or if you have any question at all please feel free to ask here or in my q&a thread.
Sent from my Evita

timmaaa said:
Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work.
Sent from my Evita
Click to expand...
Click to collapse
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again

shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That message suggests that you haven't copied the identifier token correctly. You need to make sure you copy the whole thing, including all of the arrows at the beginning and end.
Sent from my Evita

shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That error message simply means you cut and pasted the token incorrectly (included an extra character or characters that you were not supposed to). Follow the instruction very carefully and exactly for what exactly needs to be cut and pasted.
---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------
shakash3obd said:
would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Click to expand...
Click to collapse
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
shakash3obd said:
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
Click to expand...
Click to collapse
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
---------- Post added at 03:54 PM ---------- Previous post was at 03:43 PM ----------
shakash3obd said:
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
Click to expand...
Click to collapse
The bootloader unlock is a bit finicky, and its known to fail for some folks for no good reason (even if you did it all correct), possibly even numerous times. I would suggest just making sure you do the steps correctly and keep trying.
shakash3obd said:
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me
Click to expand...
Click to collapse
The only judgement I have of you, is that you seem to be rushing forward a bit too much, and not researching properly.
Fastboot (and phone modding in general) is not a place to be experimenting. You should not be trying fastboot commands haphazardly. I've seen more than a few devices on this forum bricked with a couple careless fastboot commands. I would recommend you not running any fastboot commands, unless you have obtained them from one of the established guides on this forum, or from a reputable/knowledgeable contributor on this forum.

redpoint73 said:
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
I
I am waiting right here right now until my phone is fixed.
Thank you so much guys
EDIT:
I tried to download RUU 1.73 and the links were down
so i downloaded 1.85 for now.
Waiting for your other instructions. Sir.

shakash3obd said:
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
Click to expand...
Click to collapse
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).

redpoint73 said:
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
Click to expand...
Click to collapse
This is actually my original intention, I don't want to have all the junk that comes from HTC and the one from AT&T.
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Really appreciate your help.

shakash3obd said:
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Click to expand...
Click to collapse
Best/recommended/favorite ROM discussions are not allowed on XDA. They are each good in their own way, and everyone has different preferences. Part of the fun of flashing custom ROMs is trying them out, to see what you like the best.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM. Sense is limited to Jellybean, for now.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
shakash3obd said:
Thank you so much guys
Click to expand...
Click to collapse
Feel free to click the "Thanks" button for any posts that you found helpful.

redpoint73 said:
Best/recommended/favorite ROM discussions are not allowed on XDA.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM
.
Click to expand...
Click to collapse
I will check the index of yours when I find it since I am always lost in the xda forum.
Sorry to ask for something not allowed in XDA, I will start looking for AOSP ROM since I want something like KitKat.
If we can forget about "recommendation/best ROM" will anyone can point me to where to find KitKat like ROM for my device or
give a list of names or links to threads in XDA. Or even the whole forum starting point for which i can find these type of ROMs
just to avoid bricking my device since it's S-On

redpoint73 said:
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
Click to expand...
Click to collapse
What I was afraid of is happening, I run RUU 1.85 and I am right now passed 50 minute with the phone screen is black with HTC logo on it.
is this normal?
should I be doing anything? or just wait more or unplug the phone from the PC?

[Q] N5 Root, is it a good Idea?

So I have always rooted my phones in the past.
I rooted my Samsung Galaxy S2 because well, it needed KitKat and Samsung is lame...
Now I am faced with the decision to root or not to root. My N5 is awesome it has Full support and is the raw experience I want, rooting would let me have a little more fun in the way of mods and tweaks, but all the problems everyone seems to be having is kinda putting me off so I guess I just need help.
Also there is a difference between unlocking boot loader and rooting, does the unlocking void warranty?

All guides and info threads are linked in my signature and will answer almost all your questions
I'm not sure of all these "problems" you're referring to. Basically, idiots have the most problems. Normal people don't really have any
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

rootSU said:
Basically, idiots have the most problems. Normal people don't really have any
Click to expand...
Click to collapse
this. i have been rooted since day one and have ZERO problems.

I think this: http://forum.xda-developers.com/showpost.php?p=54746284&postcount=8
Applies here too, what do you think, @rootSU?

Right. Root doesn't modify files that can cause an issue assuming you're doing it right. I'd highly recommend NOT using a toolkit and rooting yourself and unlocking the bootloader yourself, it assures nothing goes wrong and you get some experience.
rootSU's guide are a treasure trove of information, take a looksie.

unlocking the bootloader lets you flash a custom recovery to flash things, it has nothing to do with root. you can flash any roms or kernels you want, without root. all root does is give you permission to change system files. and you would flash the root zip in your new recovery once you unlock the bootloader.

simms22 said:
unlocking the bootloader lets you flash a custom recovery to flash things, it has nothing to do with root. you can flash any roms or kernels you want, without root. all root does is give you permission to change system files. and you would flash the root zip in your new recovery once you unlock the bootloader.
Click to expand...
Click to collapse
So would unlocking the boot loader void the warranty?

Spectrys said:
So would unlocking the boot loader void the warranty?
Click to expand...
Click to collapse
depending on who you bought it from, yes and no. but anyways, you can lock the bootloader after as well, easily. generally, google will still except warrenty if the bootloader is unlocked for any hardware issue. other companies will void the warrenty, including LG. but again, it can be relocked

simms22 said:
depending on who you bought it from, yes and no. but anyways, you can lock the bootloader after as well, easily. generally, google will still except warrenty if the bootloader is unlocked for any hardware issue. other companies will void the warrenty, including LG. but again, it can be relocked
Click to expand...
Click to collapse
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.

Spectrys said:
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Click to expand...
Click to collapse
yup. anything that needs to be flashed will go through your custom recovery, which needs an unlocked boitloader to get flashed onto your device. then youll use that recovery to flash things, and make backups.

Spectrys said:
So would unlocking allow me to do things like mods, such as rings and boot screens?
Sorry kinda new to boot loaders.
Click to expand...
Click to collapse
Unlocking the bootloader is a requirement in order to use a custom recovery. And most mods are installed by flashable zips in recovery. So yes kind of required.
Sent from my Nexus 5 using Tapatalk

Awesome! You guys are great I am going to unlock later today or tomorrow.
Now next question the ota updates will I be able to install those if I keep stock with an unlocked boot loader?

Spectrys said:
Awesome! You guys are great I am going to unlock later today or tomorrow.
Now next question the ota updates will I be able to install those if I keep stock with an unlocked boot loader?
Click to expand...
Click to collapse
If you click the link in my signature, theres a thread about ota. All guides and info is there. Every question you've asked today is answered there
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

Pretty sure you told me that earlier, thanks.
Looking at it now.

Spectrys said:
Pretty sure you told me that earlier, thanks.
Looking at it now.
Click to expand...
Click to collapse
Yepp. Loads of good stuff there
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client

sure
root is best thing to do . just root and install custom kernel

MohamedHusseinMohamed said:
root is best thing to do . just root and install custom kernel
Click to expand...
Click to collapse
you do not need root to install custom kernels
all you need root for is to change system files. well, that's all root does, is give you permission.

Spectrys said:
So I have always rooted my phones in the past.
I rooted my Samsung Galaxy S2 because well, it needed KitKat and Samsung is lame...
Now I am faced with the decision to root or not to root. My N5 is awesome it has Full support and is the raw experience I want, rooting would let me have a little more fun in the way of mods and tweaks, but all the problems everyone seems to be having is kinda putting me off so I guess I just need help.
Also there is a difference between unlocking boot loader and rooting, does the unlocking void warranty?
Click to expand...
Click to collapse
You have to unlock the boot loader in order to root. Personally at this time I would not root because of android L around the corner. With rooting, you can longer receive ota's. Yes it fun to tweak but if I were in your position I wouldn't....
Sent from my Nexus 5 using XDA Premium 4 mobile app

dec1153 said:
With rooting, you can longer receive ota's.
Click to expand...
Click to collapse
Not true. You can receive OTA's if rooted (read the OTA help-desk thread) However, what's the big deal about OTA's?
1) You can get a rooted rom flashed based on the latest build BEFORE you get the OTA
2) Much less to go wrong that way than with OTA.
I think too many people put too much importance in OTA updates. Its a poor method of delivery and not even quick

rootSU said:
Not true. You can receive OTA's if rooted (read the OTA help-desk thread) However, what's the big deal about OTA's?
1) You can get a rooted rom flashed based on the latest build BEFORE you get the OTA
2) Much less to go wrong that way than with OTA.
I think too many people put too much importance in OTA updates. Its a poor method of delivery and not even quick
Click to expand...
Click to collapse
Personally, I think that if you don't know how to update manually and are completely reliant on OTAs, then you shouldn't have root access in the first place because you don't know what you're doing.

Help needed desperately!

Okay so I haven't rooted or rommed for quite some time and i decided to finally come back to it after stopping over a year ago. I just recently got this m8 for verizon and i wanted to turn it into a developer edition. Well I used sunshine to s-off my device, and i changed my mid and cid to the developer ones. (yes i know they're the right ones. I've triple checked them. All was going well. I then used the jrummy rom installer to install my twrp. When I did that, it rebooted and then all of my stuff was gone except for my hboot, recovery, and fastboot. the recovery said it couldn't mount anything. not even the system! so i couldn't flash anything. i tried sideloading liquid smooth through adb in twrp and all it does is boot loop. so i thought that I should probably run the appropriate RUU. I tried. I keep getting error 155. even after i relocked the bootloader. But before i locked the bootloader i flashed a stock recovery img. i tried manually installing a RUU zip. wrong mid (tried using verizon one when i had already changed the mid to developer one. I can't find the right zip for the developer edition and none of the .exe ones work. i keep getting error 155. So now the only thing i can access is a bootlooping liquid smooth rom and hboot/fastboot/ruu mode. no recovery. and as far as i still know, a recovery cannot recognize the system partition and any .exe ruu gives me the 155 error. I am in desperaste need of help. at this point i don't even care about lollipop and anything. just help get me back to stock please!! :crying: :crying: :crying: :crying:
Edit: I was on Stock Verizon 4.4.4 when I started all of this, and I was following this thread http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003

Ryuk666 said:
Okay so I haven't rooted or rommed for quite some time and i decided to finally come back to it after stopping over a year ago. I just recently got this m8 for verizon and i wanted to turn it into a developer edition. Well I used sunshine to s-off my device, and i changed my mid and cid to the developer ones. (yes i know they're the right ones. I've triple checked them. All was going well. I then used the jrummy rom installer to install my twrp. When I did that, it rebooted and then all of my stuff was gone except for my hboot, recovery, and fastboot. the recovery said it couldn't mount anything. not even the system! so i couldn't flash anything. i tried sideloading liquid smooth through adb in twrp and all it does is boot loop. so i thought that I should probably run the appropriate RUU. I tried. I keep getting error 155. even after i relocked the bootloader. But before i locked the bootloader i flashed a stock recovery img. i tried manually installing a RUU zip. wrong mid (tried using verizon one when i had already changed the mid to developer one. I can't find the right zip for the developer edition and none of the .exe ones work. i keep getting error 155. So now the only thing i can access is a bootlooping liquid smooth rom and hboot/fastboot/ruu mode. no recovery. and as far as i still know, a recovery cannot recognize the system partition and any .exe ruu gives me the 155 error. I am in desperaste need of help. at this point i don't even care about lollipop and anything. just help get me back to stock please!! :crying: :crying: :crying: :crying:
Edit: I was on Stock Verizon 4.4.4 when I started all of this, and I was following this thread http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
Click to expand...
Click to collapse
Can you go into bootloader an try to flash twrp via fast boot? Then if you can try going into recovery by picking recovery in boot loader..

Tigerstown said:
Can you go into bootloader an try to flash twrp via fast boot? Then if you can try going into recovery by picking recovery in boot loader..
Click to expand...
Click to collapse
I tried already. it gives me this error in my command prompt:
target reported max download size of 1826414592 bytes
sending 'recovery' (14814 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.388s
And then that's all I get. twrp was not flashed.

Ryuk666 said:
I tried already. it gives me this error in my command prompt:
target reported max download size of 1826414592 bytes
sending 'recovery' (14814 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.388s
And then that's all I get. twrp was not flashed.
Click to expand...
Click to collapse
So have you tried to change your Cid back to vzw an run the ruu?

I had the dev cid, but then i changed it to super cid. i'll try the vzw one right now and get back to you in a moment

Ryuk666 said:
I had the dev cid, but then i changed it to super cid. i'll try the vzw one right now and get back to you in a moment
Click to expand...
Click to collapse
An use the VZW ruu too

Tigerstown said:
An use the VZW ruu too
Click to expand...
Click to collapse
I'm using the VZW RUU zip through the external sd card and i changed the cid to the verizon one. It was loading the RUU zip and it gave me this:
Model ID incorrect!
Update Fail!
Press <POWER> to reboot.
When i press power it just throws me back into the bootlooping liquid smooth rom to i have to put it back into fastboot so I'm still at a standstill.

Ryuk666 said:
I'm using the VZW RUU zip through the external sd card and i changed the cid to the verizon one. It was loading the RUU zip and it gave me this:
Model ID incorrect!
Update Fail!
Press <POWER> to reboot.
When i press power it just throws me back into the bootlooping liquid smooth rom to i have to put it back into fastboot so I'm still at a standstill.
Click to expand...
Click to collapse
You change your mid as well? If so can you change it back to VZW one.

How do i go about doing that through fastboot? I did it through adb last time.

Ryuk666 said:
How do i go about doing that through fastboot? I did it through adb last time.
Click to expand...
Click to collapse
Hold tight for a few mins. Don't do anything else. I'm talking to someone now. He is going to join in an finish getting you booted...

Ryuk666 said:
How do i go about doing that through fastboot? I did it through adb last time.
Click to expand...
Click to collapse
any chance you can install teamviewer so i can get you fixed up and booted?

Okay thank you so much. I will sit here and leave it alone and wait patiently lol.

dottat said:
any chance you can install teamviewer so i can get you fixed up and booted?
Click to expand...
Click to collapse
One moment and i'll go do that now.

Ryuk666 said:
One moment and i'll go do that now.
Click to expand...
Click to collapse
PM me the login info...

Dottat you are seriously the man! You are so awesome! I would have never gotten that done myself. You are seriously amazing!

Glad your all set. That's why I hit him up

I am having the exact same issue except i found a couple problems in my recovery log that stumped me some how in the mix my serial number became =£Ðcçy™yüRv–²‹ and my mid shows
ro.boot.mid=
in my boot log what can i do to solve these problems????
---------- Post added at 07:02 AM ---------- Previous post was at 06:45 AM ----------
I am having the exact same issue except i found a couple problems in my recovery log that stumped me some how in the mix my serial number became =£Ðcçy™yüRv–²‹ and my mid shows
ro.boot.mid=smiley and an arrow (woulent paste)
in my boot log what can i do to solve these problems????

People I think it would be best to give up the dev conversion idea on a verizon m8. A bunch of us tried and tried and take this from experience you will be opening up a can of worms. Wouldnt it be nice to be able to oh heck yeah I would like to also but unless your really really really experienced with this stuff your going to be regretting trying it.
It would be nice but I think it wont work because of the cdma side of the verizon m8. It works great on at&t & tmobile verizons which are all gsm. Our verizon phones are world phones and both cdma and gsm so somewhere lies the incompatibility.
Believe me I tried and tried and tried and I spent a lot of time getting my phone back working right again. My recommendation is if your thinking about trying to convert your verizon m8 to a dev edition save yourself a big headache and dont waste your time. Either that or get an at&t or tmobile m8 and convert it, but then use it on either at&t or tmobile where it will work right and the LTE will work.
It was really nice of these guys to help get his phone fixed so anyone else thinking about it learn from his mistake and forget about it lol.

Ryuk666 said:
Dottat you are seriously the man! You are so awesome! I would have never gotten that done myself. You are seriously amazing!
Click to expand...
Click to collapse
Did you get your fixed? because i have similar problem. i got my verizon m8 messed up MiD To 0P6B10000 instead of 0P6B20000. And now i cant flash any official firmware. can you help me out?

Mine did indeed get fixed. But I'm not exactly sure how. Dottat was a huge help. He definitely knows what he's doing lol. He was going through command prompt fastboot commands so fast I couldn't follow him haha.