Database Info

[Q] How to fix stuck on SPLASH SCREEN (HTC Logo)?? No s-off/ No root (Sensation XE)

I installed a new rom... What i did was that i took out the Boot.img From the rom zip file and flashed it using adb without putting the zip file is my memory card. Now whenever i boot, the screen is stuck at the htc text. Is there anyway to fix this??
Thanks

How did you flash a ROM without being S-OFF? That's new for me.
Anyways, the boot image updated your bootloader. If you flashed an image from any firmware above 3.12, Gingerbread won't boot. If you flashed firmware 3.12 or lower, ICS won't boot. You need to flash the right package.

When you say "flashed via adb" can you explain the exact commands used?
Also what rom, what is your hboot screen saying now?
Sent from my Pyramid-T using xda premium

V1k70r said:
How did you flash a ROM without being S-OFF? That's new for me.
Anyways, the boot image updated your bootloader. If you flashed an image from any firmware above 3.12, Gingerbread won't boot. If you flashed firmware 3.12 or lower, ICS won't boot. You need to flash the right package.
Click to expand...
Click to collapse
I unlocked the bootloader using HTCdev method.

stringer7 said:
When you say "flashed via adb" can you explain the exact commands used?
Also what rom, what is your hboot screen saying now?
Sent from my Pyramid-T using xda premium
Click to expand...
Click to collapse
I followed this thread (http://forum.xda-developers.com/showthread.php?p=21922297#post21922297) but i downloaded a different ROM. I dont have my phone right now, but when i get it back i will tell you what the hboot says. I took the Boot.img From the zip and put it inside ADB-Windows folder which i downloaded from the thread. Then i did this... "fastboot flash boot boot.img" and after that, "fastboot reboot-bootloader" All i said is from this thread.

I need TMOUS Firmware please

After attempting to install Revolution HD ROM with ICS on my Sensation 4G I am stuck in boot loop.
I suspect it is because I installed the wrong firmware being a noob.
Does anyone have the stock firmware (not the RUU executable, just the firmware .zip) I could flash to re-install my team win recovery & restore my device back to t-mobile stock everything?

did u flash the latest firmware before flashing ARHD?

Econet said:
After attempting to install Revolution HD ROM with ICS on my Sensation 4G I am stuck in boot loop.
I suspect it is because I installed the wrong firmware being a noob.
Does anyone have the stock firmware (not the RUU executable, just the firmware .zip) I could flash to re-install my team win recovery & restore my device back to t-mobile stock everything?
Click to expand...
Click to collapse
What is your CID? The firmware depends on your CID number. If you don't know, go into cmd and type the following. I am assuming you have the SDK configured and installed with the HBOOT drivers. Assuming you are not already in fastboot USB mode. Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
then
adb reboot bootloader
then
adb getvar cid
Then get the latest correct firmware from here. Put the PG58IMG.zip on the root of your SD card. If it doesn't work check that it isn't called PG58IMG.zip.zip. If it succeeds and your phone is still in a bootloop, (it happened to me) flash a new ROM or flash the official RUU and then restart the rooting process.
Thanks if I helped

When you flashed ARHD did you use the 6.5.5 that was released today? and if so, sis you choose the faux kernel? This is a known issue if so, check the ARHD thread or just flash the faux kernel manually from its thread.

Sgt.Incontro said:
What is your CID? The firmware depends on If it succeeds and your phone is still in a bootloop, (it happened to me) flash a new ROM or flash the official RUU and then restart the rooting process.
Thanks if I helped
Click to expand...
Click to collapse
I tried all 4 of the firmware packages in the firmware thread & none of them got me out of bootloop. How do I flash the official RUU? Do I just run the RUU.exe then boot to phone to Fastboot mode and connect it via USB to the PC?
Also, to get the CID via cmd prompt do I need to be in fastboot on the phone too?

Find my post for a guide / fix
Sent from my HTC Sensation 4G using xda premium

craven667 said:
Find my post for a guide / fix
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I found your post & this seems to be the relevant info to me:
http://forum.xda-developers.com/showthread.php?t=1542555
"...You also have to be 100% stock (e.g. NOT rooted). If you are running a custom ROM you HAVE to use the http://www.4shared.com/file/risaQet4...pe_1454012.htm RUU to get back to stock but you HAVE to leave the phone S-OFF. "
I still have the following question:
"How do I flash the official RUU? Do I just run the RUU.exe then boot to phone to Fastboot mode and connect it via USB to the PC?"
Click to expand...
Click to collapse

Also, it appears my PC is not able to detect the phone when its connected (another issue from me stupidly flashing the wrong firmware?).
Is there a way to flash the stock TMO US Firmware when phone/computer can't connect for adb and fastboot commands?
Will flashing via HBoot (dropping the .zip file in the root folder of the SD card) work?

I get [Error 131] Wrong Customer ID when I try flashing using the RUU.
I know I changed my CID last night to HTC__001 from the default TMOsomething one.
How do I change the CID when the phone isn't recognized by adb & fastboot?
Is there a way to change it over HBoot?

Update (in case any Noob like me ever has this same issue again):
I managed to finally get the PC to "see" the phone by HBOOT installing 4Ext Recovery.
Updated back to stock firmware. Then I fastboot changed the CID back to T-MOB010 and was able to flash (via HBoot) the stock T-Mo firmware 1.50.531.1.
Now I'm back to stock everything.
Lesson: Don't ever flash firmware before verifying it supports your Model & CID!

Okay guys im really stucked trying to repair the phone...

Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
************************ Update ************************
Okay great... now after waiting for 4332 seconds for the writing part to finish... I knew its not going to work via waiting any longer... I unplugged the USB... the command prompt shows up an error (FAILED, too many links)... I attempted to restart the phone from the HTC logo and now it doesnt start at all... cant even get into bootloader... =.=
************************ Update ************************
Okay I've managed to save my phone using this method http://unlimited.io/qhsusbdload.htm
So now im back to square one... I can go bootloader... i unlocked it again... but i still cant go recovery...
************************ Update ************************
Now its back to being bricked again... as I was working on the phone outside when i managed to unbricked it. I choose to power off the phone from bootloader menu, thinking that I could work on it when I get home... alas, when i got home... the phone doesnt turn on... and i saw the dreaded QHSUSB_DLOAD thingy again...... omg... And the above method no longer works..........

kedirakevo said:
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
Click to expand...
Click to collapse
Stuck in a similar problem not sure what to do...

I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app

If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL

exad said:
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
how do i flash rom when recovery aint working?

area51avenger said:
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1952426
Program says phone's bootloader must be locked in order to flash ruu zip

kedirakevo said:
how do i flash rom when recovery aint working?
Click to expand...
Click to collapse
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app

exad said:
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....

kedirakevo said:
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
Click to expand...
Click to collapse
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app

exad said:
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0

kedirakevo said:
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
Click to expand...
Click to collapse
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app

kedirakevo said:
Program says phone's bootloader must be locked in order to flash ruu zip
Click to expand...
Click to collapse
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.

exad said:
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
wish I could try that... it bricked now.

twistedddx said:
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
Click to expand...
Click to collapse
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......

Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app

exad said:
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
beats me man... Told you, was trying to flash RUU through zip then it just hung there... but I managed to save my phone... I redownloaded and reflashed recovery as you advised but still no avail! Basically, back to square one....

kedirakevo said:
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Click to expand...
Click to collapse
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
kedirakevo said:
was trying to flash RUU through zip then it just hung there.
Click to expand...
Click to collapse
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.

twistedddx said:
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
Click to expand...
Click to collapse
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...

kedirakevo said:
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
Click to expand...
Click to collapse
The least risky way would be to flash a stock ROM from here not an ruu. There are some untouched roms. I, myself have bricked running the telus ruu.
Sent from my One X using xda app-developers app

From total stock 4.1 to rooted 4.4.2

Hi everyone, I've yet to successfully load a custom ROM on my ville but I have got s-off and supercid. I'm currently on relocked bootloader running the total stock android 4.1. I'd just like to check through the steps I need to take to try a new 4.4.2 ROM. I was thinking of trying twistedkat.
1. Unlock bootloader (I already have the unlock file from htcdev)
2. Load custom recovery (I have TWRP 2.6.3.0 ready to go)
3. Flash SuperSU
4. Flash Rom file (do I need to unzip or flash the zip file in the recovery?)
5. Flash 4.4 Gapps
Any other steps I've missed? I'm on hboot 2.15, kernel 3.14 from the stock updater.
Thanks very much

fatboyslimerr said:
Hi everyone, I've yet to successfully load a custom ROM on my ville but I have got s-off and supercid. I'm currently on relocked bootloader running the total stock android 4.1. I'd just like to check through the steps I need to take to try a new 4.4.2 ROM. I was thinking of trying twistedkat.
1. Unlock bootloader (I already have the unlock file from htcdev)
2. Load custom recovery (I have TWRP 2.6.3.0 ready to go)
3. Flash SuperSU
4. Flash Rom file (do I need to unzip or flash the zip file in the recovery?)
5. Flash 4.4 Gapps
Any other steps I've missed? I'm on hboot 2.15, kernel 3.14 from the stock updater.
Thanks very much
Click to expand...
Click to collapse
1- if you didn't unlock your bootloader, you have to
2- i don't know which twrp you have but you shuld use the one from twistedkat thread (it's different from official one)
3- it's unrelated with custom rom flashing
4- DON'T unzip the rom, just flash the zip from recovery
5- you have to flash g-apps if want to use google's apps (gmail, playstore, etc.)
you don't need anything else AFAIK
have fun
Sent from my One S using xda app-developers app

By the way i recommend you to change your cid back to original, because supercid has no advantage over original cid. But one day you may want to turn back to stock and if you forget that your device has supercid it will brick the device
Sent from my One S using xda app-developers app

Do not forget to flash boot.img in fastboot! To do it, you need to extract boot.img from ROM zip file to same directory with fastboot on your computer and and reboot your device to fastboot mode. Then run this in terminal/cmd: fastboot flash boot boot.img . If you don't do this, your device won't boot to OS. Flashing SuperSU with a custom ROM is unnecessary since root usually is included in custom ROM.
EDIT: You don't need to flash boot.img, because you have S-OFF. Didn't notice it first.

ka_55 said:
By the way i recommend you to change your cid back to original, because supercid has no advantage over original cid. But one day you may want to turn back to stock and if you forget that your device has supercid it will brick the device
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Oh no! I've already ran a RUU with supercid to get back to total stock and that didn't cause any problems. Problem is I don't actually know what the original cid was!

fatboyslimerr said:
Oh no! I've already ran a RUU with supercid to get back to total stock and that didn't cause any problems. Problem is I don't actually know what the original cid was!
Click to expand...
Click to collapse
I checked again, ruu doesn't seem cause a brick but ota updates may cause such thing. So i think you shouldn't install ota updates till you remember your original cid
Sent from my One S using xda app-developers app

Thanks for the replies guys. One last question. If I load Twistedkat, which is based on CM11, I'll lose Sense?
Can I have sense as well? Is there a flashable sense zip file or something?
Thanks!

You will absolutely lose sense, and there is no way to install sense with kitkat roms right now for our one s
Sent from my HTC One S

See attached screenshot. Now successfully on 4.4.2.
I did need to get SuperSU. Thanks for all the help

How to restore to stock using signed OTA Zip

I got the HTC One S (S4) with Hboot 2.15 carrier is Virgin Mobile Canada (Bell Mobility, CID: BM_____1) with bootloader unlock via HTC Dev. I have been using CyanogenMod for quite some time and have no nandoird backup. My phone was updated to JellyBean via an OTA prior to unlocking and installing custom rom.
My reason from wanting to restore to stock is that I can't facepalm s-off but discovered that Moonshine s-off is compatible with my phone and stock OTA from carrier. I want s-off mainly to flash custom kernel. I've been just using fastboot to flash the boot.img thus far but seems that I can't do this with customer kernels.
I looked on the RUU thread in the development section and there is no RUU for my phone (ally RUU's for my carrier are older and don't work). The signed OTA for BM is available as a zip. There is no .exe here. Inside the OTA zip there is a firmware.zip which contains things like the radio, recovery, and boot.img. The zip for the OTA also includes a folder for /system. This is not a system.img but just a folder. There are some other small files also.
I tried locking the bootloader via fastboot and then flashing the OTA zip that doesn't work. If I extract the firmware.zip from the OTA's zip and after running "fastboot oem rebootRUU" I am able to flash the firmware.zip successfully. This however doesn't allow the phone to boot as nothing is flashed to /system.
I'm not sure how to get this to work. I read that what I need to do is rename the OTA's zip to update.zip and place is sdcard partition and then I can from the stock recovery flash this. I am able to get in the stock recovery but when there it displays and error saying that it can't mount sdcard (both CWM and TWRP can mount SD card). How do I flash this to restore to stock. How can I get the /system part of the OTA to flash?