Database Info

[Q] Unbootable device

Hi guys, new here (don't judge! xD)
So I have had a HTC Sensation for almost a good year. Halfway through this year I decided to try get off stock sense and see what advantages rooting does so I unlocked the bootdevice following the instructions on HTC's website and managed to installed Cyanogenmod hassle free. Recently however, I have looked into getting Android Revolution HD and thought I would switch to see what it is like. This is where I started getting problems, I think it first started with me using Clockworkmod Recovery instead of 4EXT to install and secondly I forgot to use Smart Recovery in 4EXT.
Basically, I have tried formatting and wiping, using the superwipe script, trying to recover using my nandroid backup of CMod, trying to install a stock rom, tried to install the RUU exe file ("RUU_PYRAMID_ICS_etc...") but every time it tells me the ROM has successfully installed, I reboot and it gets stuck at the White Screen of Death with the green HTC logo (the one just before the "quietly brilliant" slogan (or the blue CMod man)). So at the moment I don't have a working phone
Code:
***unlocked ***
Pyramid PVT SHIP S-ON RL
HBOOT – 1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.862.13
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5811000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4069mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have tried to install "PG58IMG.zip" many times but have failed every time. It just says "Parsing" the zip file but doesn't actually install. I have tried USB 2.0 drivers, reinstalling the HTC drivers, trying to flash through CMD but it just won't work! Would you guys be ever so kind to help me out! I have tried looking at every related thread under HTC Sensation

First delete your imei and serial number foryou own safety
If you have still 4ext recovery installed enable smartflash and then immediately restore your nandroid backup
Before this format all partitions except sdcard from 4ext
If that fails flash the boot.img of your current rom manually
If you don't know how go in general section and search the thread for flashing roms with S-ON.do only extra 1 step
Sent from my HTC Sensation Z710e using xda premium

rzr86 said:
First delete your imei and serial number foryou own safety
If you have still 4ext recovery installed enable smartflash and then immediately restore your nandroid backup
Before this format all partitions except sdcard from 4ext
If that fails flash the boot.img of your current rom manually
If you don't know how go in general section and search the thread for flashing roms with S-ON.do only extra 1 step
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Thank you!! I managed to get the stock HTC Rom running again by flashing a kernel using the HTC Sensation tool (I copied the boot.img out of the zip file) and ran the "Flash your kernel here". If I copied a the boot.img and flashed it from say "Android_Revolution_HD-Sensation_6.8.0_XE.zip\kernels\sebastian\" Do you think that may solve my problem?

rhys_mcg said:
Thank you!! I managed to get the stock HTC Rom running again by flashing a kernel using the HTC Sensation tool (I copied the boot.img out of the zip file) and ran the "Flash your kernel here". If I copied a the boot.img and flashed it from say "Android_Revolution_HD-Sensation_6.8.0_XE.zip\kernels\sebastian\" Do you think that may solve my problem?
Click to expand...
Click to collapse
Hi,
Look HERE
This guide will tell you everything you need to know.

[Q] I need some steps on what to do next.

Right now I can not turn my phone on, it just gets stuck in the htc quietly brilliant "This build is for development purpses only" red text screen every time I reboot it.
I have TWRP v2.4.3.0 installed and working, bootload is unlocked, I don't know what to do next. Could anyone be kind enough to give me a clear set of instructions ("flash rom" isn't helping - would help a lot if you mentioned which rom and how to flash it and whether to reset factory settings/clear cache). all I want to do is to get past the htc quietly brilliant screen, no matter how. Help please.
Info about my phone below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:***************
(bootloader) imei: *********
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

It's pretty easy. All you have to is to follow the instructions over here.

rootrider said:
It's pretty easy. All you have to is to follow the instructions over here.
Click to expand...
Click to collapse
I think the root of my problem may be finding a custom rom compatible with hboot 1.13..
Every rom i try to install fails (trickdroid, viperones), is there any way i can update hboot first?

rootrider said:
It's pretty easy. All you have to is to follow the instructions over here.
Click to expand...
Click to collapse
Helloooooo?
I'm stuck, it's not like I didn't try installing roms before.
They're failing because I have hboot 1.13 and I can't find ANY roms that are compatible with 1.13.
I also can't download an RUU, because no RUU is available for my carrier/version (CID: ROGERS001)

that link given is for the S3 variant
i can't tell by your specs--do you have an S3 as opposed to S4
i don't think Rogers would have S3, but not up to speed on that stuff
those roms are for the S4
i don't know why .13 is an issue
you don't give your specific flashing process for which rom
did you flash boot image an do all OP install instructions to include wiping system as part of wipe
i am calling it a nite, but we would need more specifics like i mentioned, unless rootrider gave you that link bc you are S3

rugmankc said:
that link given is for the S3 variant
i can't tell by your specs--do you have an S3 as opposed to S4
i don't think Rogers would have S3, but not up to speed on that stuff
those roms are for the S4
i don't know why .13 is an issue
you don't give your specific flashing process for which rom
did you flash boot image an do all OP install instructions to include wiping system as part of wipe
i am calling it a nite, but we would need more specifics like i mentioned, unless rootrider gave you that link bc you are S3
Click to expand...
Click to collapse
I'm S4, and I managed to fix it... never got viperones to work though, first i did the superCID process and downloaded a t-mobile ruu, and then tried to custom rom viperones which didn't work ended up working with aokp, so thanks anyways, how do I close this thread

Get different twrp. Many people have problems flashing roms with 2.4.3.0 version.
Sent from my HTC One S using xda app-developers app

Glad you got it. Mod may close it. Since you asked.

[Q] lot's of problems

Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.

theconverter said:
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
Click to expand...
Click to collapse
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now

rzr86 said:
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
Click to expand...
Click to collapse
Hi,Yep tried that one still getting signed error.
Thanks for looking

You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **

lot's of problems
Gatosbil said:
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
Click to expand...
Click to collapse
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s

theconverter said:
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
Click to expand...
Click to collapse
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command

rzr86 said:
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
extract the recovery.img and flash it via fastboot command
Click to expand...
Click to collapse
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts

theconverter said:
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
Click to expand...
Click to collapse
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked

rzr86 said:
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
Click to expand...
Click to collapse
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?

theconverter said:
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
Click to expand...
Click to collapse
i really don't know mate

rzr86 said:
i really don't know mate
Click to expand...
Click to collapse
Hi, just a update ive fixed my phone, :laugh: done so by making a gold card following the tut's on this fourm installed 4ext via the card booted into recovery cleared dalvik cache ect and now boot's without any loop's.
Looking forward to flashing cyanogenmod and maybe going s-off
Many thanks for all your help and suggestions ill hit the thanks button for you.
Just need to mark as " solved " not sure how ( mod's ? )

[Q] Rogers HTC One X help with customer recovery issue...

Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?

If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong

nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.

13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved

Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?

audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.

I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!

Stuck in Bootloader after Flashing RUU (No Custom Recovery)

Yesterday I went through the process of unlocking my bootloader, rooting the phone and then S-OFF via Sunshine. After completing these steps, I attempted to flash a RUU (http://forum.xda-developers.com/one-e8/development/ruu-sprint-htc-one-e8-1-22-651-1-stock-t2952981) - the reason for this being I am attempting to unlock my SIM for use on another carrier. So, I was able to successfully flash the RUU via fastboot commands (followed these instructions: https://www.youtube.com/watch?feature=player_embedded&v=ybu7fZa41so) and then rebooted the device. Upon rebooting the device, I was able to use the phone for 10 seconds or so before it automatically reboot itself. This happened several times before the bootloop stopped and I was able to use the phone just fine. Thinking everything was working, I proceeded to the next step in unlocking my SIM (outlined here: http://forum.xda-developers.com/one...51-1-stock-t2952981/post57116360#post57116360) which was to flash a zip (found here: http://forum.xda-developers.com/atta...1&d=1417208962). Upon flashing the zip, I was unable to successfully reboot the phone. Instead, I am only able to access the bootloader and TWRP recovery.
I am currently at a loss for what to do. One issue is that I may have attempted to flash the RUU and subsequently the zip while my phone was low battery (roughly <15%; I've read this can cause issues but I'm not 100% sure). I am currently charging my phone in hopes that this may solve the issue but I am not entirely optimistic.
I realize that I am an idiot for not having a stock rooted TWRP backup - I actually did create one (albeit on my internal storage) which was subsequently deleted when flashing the RUU. I have not been able to find a stock rooted backup of the Sprint HTC One E8 (perhaps I am not looking in the right places), could anyone help me find this? Or should I try to flash the RUU linked above again (am I wrong in assuming this would serve as a custom recovery)?
I am concerned that I may have bricked my phone...so any help at all would be appreciated.

Hope I can help. First the good news- you have not bricked your phone. Now the (not so) bad news- you are in a bit of a mess but will be able to come out with a functional phone.
It sounds like you have a Sprint phone and tried to flash another RUU.
I need to know exact model number of your phone, MID, CID stock ROM etc and what RUU you had tried to use.
The easiest way would be to find a stock RUU that your phone had come with, rename it to 0PAIJMG.zip and put in the root of an external micro sd and reboot the phone in bootloader and let the phone reinstall the original RUU (as you have already done once).
Before, you try to flash another RUU make sure you have superCID and have modified MID as well ( there are plenty of discussion on this in this forum).

Alright, so after a day of tinkering with things I think I may have resolved the issue (but not achieved my goal of unlocking the SIM).
I ended up getting superCID, and flashing the current RUU for the Sprint HTC One from HTC's website. The phone is now up and running on 2.32.651.7. I did this by downloading the .exe. file straight from HTC's website and following the utility instructions. I was previously trying to manually flash 1.22.651.1.
So my phone is up and running, however I would still like to unlock the SIM. I am following the instructions in the link I provided in my previous post (http://forum.xda-developers.com/one-...0#post57116360) but am somewhat hesitant to re-flash the 1.22.651.1 RUU as instructed in the guide considering what I just went through. I know that I would be able to just revert back to my current RUU which is stable, but I'm not inclined to go through with the process if it is just a dead-end. Would I be able to go through with the instructions (specifically everything including flashing the zip file from http://forum.xda-developers.com/atta...1&d=1417208962 and onwards) and still be able to successfully unlock the SIM from the 2.32.651.7 RUU? Or do you think it specifically requires the 1.22.651.1 RUU to work?
I'm not familiar with MID or why I need to modify it, could you elaborate or should I just look into other forum posts?
As for my phone info, here you go: (I used the command fastboot getvar all; not sure if this is what you wanted)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.32.651.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4AASP00761
(bootloader) imei: 990004299346803
(bootloader) imei2: Not Support
(bootloader) meid: 99000429934680
(bootloader) product: mec_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ50000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d0c41a5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

OK so I'm pretty sure what is causing problems is the step outlined here - "flash the attached zip http://forum.xda-developers.com/atta...1&d=1417208962". Apparently the file is supposed to grant write access to modify an APK file and allow the phone to be rooted, however, whenever I flash the zip file from TWRP recovery, I am no longer able to boot into my OS...instead I boot straight to recovery. Not sure why this is - any help would be appreciated!