Database Info

[Q] stuck on splash-screen

Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow

onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.

Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?

onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.

so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?

onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.

finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?

onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.

http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium

tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.

Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium

heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.

an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.

SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help

onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know

Stuck in Bootloop

Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.

We need more details .....which kernels did you flash ??

I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.

sagarsaoji said:
I didn't flash any kernals separately, just the one that came with insertcoin 2.3.
http://insertcoin-roms.org/2012/08/insertcoin-evolution-sense-4-v2-3-sensation/
That has all the information about the rom I flashed.
Click to expand...
Click to collapse
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE

malybru said:
Hi,
Try starting again from scratch.
Run a RUU.
Look HERE
Click to expand...
Click to collapse
I flashed a RUU through the rom.zip. The process seemed to be stuck at step [4] System for quite a while, kept unzipping and updating over and over again. It eventually completed but now I'm stuck in bootloop with a large BEEP sound after "htc simply brilliant" screen, then phone reboots and have to pull the battery out. PLEASE HELP ME

Did you install stock kernel ??
Because some roms need specific kernels which only work on the Rom and your going to stock so its not gonna boot

sagarsaoji said:
Hey you guys, my friend dropped her phone and it went into bootloop. She was using some old ARHD Rom. She then wiped her phone somehow (not sure what she did). I ended up installing the insertcoin 2.3 (sense 4) rom I am using on my phone but its still stuck in bootloop. I can access the 4ext recovery.
Bootloader info is:
Pyramid PVT Ship S-Off RL
HBOOT - 1.27.1100, Radio - 11.24A. 3504. 31_M
OpenADSP - v05.6.0.2226.0.0418
eMMC - boot.
Please any help on how to get it back to stock or any running rom would be much appreciated.
Click to expand...
Click to collapse
IS the Phone S-OFF?
This step is extremely important, because we are not s-off and there is a problem with creating the "boot.img". T-Macgnolia explained it nicely:
When you use HTC Dev to unlock your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read those partitions. But there is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the .zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed the New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just what thee name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of something called a Linux kernel. This means that your bootloader boots the Linux kernel and the hardware of the device. The Linux kernel then boots the Android OS. The kernel is also the connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on the system partition you will have troubles like Wifi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for the ROM or you will more than likely have troubles.
Click to expand...
Click to collapse
There are 2 ways to enable smartflash, one is a temporary way inside the 4EXT recovery itself (only for first time!) and the second way is permanent, through the 4EXT application.
The permanent way can only be enabled if your phone has ROOT! It's impossible to do it when you are going to flash a ROM for the first time.
Once you have flashed your ROM you have to install the 4EXT application and enable smartflash through it, which is explained in Step 5.
3A. Enable 4EXT Temporary smartflash
Enabling this is as simple is getting into the recovery and enabling it as an option.
NOTE: You only need to do this right before flashing your first ROM, so you should skip this step and come back here when the guide tells you to.
Disable "Fast Boot" on your phone.
Code:
Settings
Power
Untick "Fast boot"
Turn off your phone
Hold the Power AND Volume Down button until you see a white screen which says: "Fasboot".
Navigate to "RECOVERY" and select it, you should now boot into the 4EXT recovery
Select "Tools"
Scroll Down and select "Enable 4EXT SmartFlash"
Again, you only need to do this ONCE, once you have flashed your first custom ROM and enabled permanent smartflash, you don't need to this any more!
Click to expand...
Click to collapse
Source
Hope I am not talking nonsense

wetfoot said:
IS the Phone S-OFF?
Source
Hope I am not talking nonsense
Click to expand...
Click to collapse
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?

Sure thing .......
Do you know how to get the stock kernel from the ruu ?

sagarsaoji said:
The phone is S-Off but now it says "locked" on top in purple where as it used to not before. Also should I flash kernel before or after flashing RUU rom?
Click to expand...
Click to collapse
Hi,
The RUU contains a stock ROM ,recovery,kernel,firmware,and radio.
It should be the only thing you need to flash/run.
I do not know why the RUU did not work.
Now that it is "Locked", then you cannot flash an RUU with version less than your phone's current version.
The RUU should reset all your partitions,(Except s-off), and restore your phone to stock.
If your current version is the same as the RUU,try running it again by doing it manually (section 4 in the guide)

Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
EDIT: just some further info...can't get adb to find device even though it is in fastboot usb mode..any way to get that working?

sagarsaoji said:
Section 4 of what guide (sorry for being this confused).
Also tried flashing other kernels and got assert failed: write_raw_image("/tmp/newboot.img", "boot") error
I ended up reinstalling CWM recovery, don't know how to get 4ext with just the bootloader...if there is any way possible I'd be willing to try the Smartflash option.
Click to expand...
Click to collapse
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.

malybru said:
Hi,
The guide I mentioned in my first post ( HERE )
Flashing a kernel will not achieve anything.
Using smartflash if you are s-off,will not achieve anything.
Click to expand...
Click to collapse
Still not booting, making a beep after "simply brilliant" screen and reboots constantly. I was able to get ADB to finally work. I also followed Step 4 from the guide but even after the RUU flashes completely the phone is stuck in bootloop.

[Q] Stupid mistake - now stuck in boot loop

I'm not sure what I did wrong but I'm sure it's my fault.
Here goes.
I had an HTC One S (that I rooted using Hassoon's tool ver. 3.3.1). I go rid of it.
Now I got another one for my cousin. We decided to root it and flash a custom ROM.
I followed the steps in the tool up to where you flash your own recovery (which I did; TeamWin latest version from site).
While the phone rebooted we went and got CM10 (the monthly) and GAPPS.
The phone then started up but for some reason a warning came up saying we didn't have root and we had to finish installing SuperUser. We did. The phone rebooted. We put the new ROM and GAPPS in the internal storage.
Rebooted to recovery. Wiped everything except the internal memory (we did not back up) and installed the new rom. Now the phone is stuck on the HTC splash screen.
I tried following another thread here and fear I may have made things worse for myself. I downloaded the latest tool from Hassoon and ran the command "fastboot oem lock" in an attempt to maybe return back to a stock rom or something where we can UN-brick this phone.
Anyway I'm in over my head.. please help.
Here's the info.
***TAMPERED***
***RELOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.11T.50.02.22
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41

You needed to flash the kernel for the new rom you installed.

hasoon2000 said:
You needed to flash the kernel for the new rom you installed.
Click to expand...
Click to collapse
did it resolved the problem?

hasoon2000 said:
You needed to flash the kernel for the new rom you installed.
Click to expand...
Click to collapse
Forgive me for being "slow" but..
Doesn't CyanogenMod 10.1 come with it's own Kernel?
If not then I may need a link directly to a kernel that I can download and then flash (I looked on the cyanogenmod website and the only thing I could find was how to build the Kernel in Linux).

Ysleiro said:
Forgive me for being "slow" but..
Doesn't CyanogenMod 10.1 come with it's own Kernel?
If not then I may need a link directly to a kernel that I can download and then flash (I looked on the cyanogenmod website and the only thing I could find was how to build the Kernel in Linux).
Click to expand...
Click to collapse
S-ON devices with HBOOT version of 1.13 or higher do not allow kernels to be flashed through recovery. So even though you have flashed the ROM, the kernel will not have been flashed. You'll need to extract the boot.img from the ROM zip file manually, boot the phone into fastboot mode then use the command:
fastboot flash boot boot.img
This will flash the kernel manually.

djsubtronic said:
S-ON devices with HBOOT version of 1.13 or higher do not allow kernels to be flashed through recovery. So even though you have flashed the ROM, the kernel will not have been flashed. You'll need to extract the boot.img from the ROM zip file manually, boot the phone into fastboot mode then use the command:
fastboot flash boot boot.img
This will flash the kernel manually.
Click to expand...
Click to collapse
MUCH APPRECIATED. Solved!
I will be donating to the both of you for your commitment to the community.

[Q] Issue with I4g. HTCDev unlocked but now some rom will not boot and others no wifi

I am having trouble trying to return my brothers I4G back to stock after it was HTCDev unlocked. Currently it has a rom on it that is able to boot however the wifi setting keeps saying error. I tried to install another rom (specifically sabsa prime) however that would not boot past the white splash screen. since then ive been trying to get back to stock using every method I could find but to no avail. I tried to downgrade my hboot because i read that as the solution but even then I am unable to do anything. The Bootloader info is as follows
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO26.10.04.03_M
eMMC-boot
Dec 22 2011, 14:28:19
Please help me. I really need to either get this phone back to stock or at least get the wifi working.

When you flash a ROM you need to also fastboot flash a boot.img. read my signature for details.

bananagranola said:
When you flash a ROM you need to also fastboot flash a boot.img. read my signature for details.
Click to expand...
Click to collapse
Yes I have tried this. On every build of the Sabsa Prime Rom I am unable to find the boot.img. The other rom I tried managed to boot without the need of flashing the boot.img

Try another ROM?

assassin82492 said:
Yes I have tried this. On every build of the Sabsa Prime Rom I am unable to find the boot.img. The other rom I tried managed to boot without the need of flashing the boot.img
Click to expand...
Click to collapse
If Sabsa is a multi device rom you will find it under the kernel / Ace folder. It is not possible to boot a custom rom with an unlock bootloader without flashing the boot.img as HTCDEV does not support the boot flashing by a custom recovery.

I tried another Rom and it worked without problems. For some reason the other 4 or 5 roms I tried did not work at all. Its not my first choice bit the current Rom I'm on seems pretty good. Thanks
Sent from my HTC One X using xda app-developers app

[HELP] Messed phone, messed situation - I'll show you

Hello - I'm new here,
Some day ago I was trying to change rom on my HTC One S. I've ended up with Cyanogenmod which worked almost ok but after some update system crashed.
So I was trying to find something else - I've ended on Venom.
I was having issues almost all the time - phone was resetting, had calling, signal issues.
Then today I was trying to install another rom but I've ended "softbricked" after installing newest Cyanogenmod for One s. Just blank screen after flashing it from recovery.
Please help me to make this phone to work I will have some big problems without it (I know I'm stupid messing with that in the first place)
Anyway if there's some good souls on XDA, here's my specs:
Team Win Recovery project 2.7.1.0
HBoot 2.15 - Tampered, S-On (no idea what happened)
radio 1.1.50
opendsp-v31.1.0.45.0815
And my situation: I was trying to install ANY of windows 8.1 driver that works with this phone but none of it was working properly. I have only connected and sent zip files trough adb commands (while in recovery).
PLEASE HELP! So many hours on this and nothing works as it should.
*crying idiot*
What rom should I install to make this phone shine again?
I have now unlocked fastboot on Windows thanks to http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337

Since you didn't mention it I got to ask you whether you flashed the kernel (boot.img) via fastboot after you flashed any rom via your recovery. Due to the fact that your phone is still S-ON none of the roms here on xda is going to work properly without that step.
I guess your problems started because the cyanogenmod update you tried to install contained a new kernel your phone couldn't flash on its own (because of the S-ON status).
Just unzip the "boot.img" from the rom archive into your fastboot/adb folder and flash it with "fastboot flash boot boot.img" and your phone should work properly again.

Thanks!
I have flashed new boot.img before installing rom from recovery (http://forum.xda-developers.com/htc-one-s/development/unofficial-slimkat-hboot-2-15-t2918217). And rom worked correctly - without reboots. I hope that is the end of my problems.
Should I do S-off and get rid of that Tampered thing? Or I can leave it as is?

Well, that depends on you. If you want do downgrade your hboot, install the leaked hboot 2.16 or don't want to be obliged to always flash the kernel seperately then you should S-OFF your phone.
The "tampered" actually has no effect besides that it may annoy you. It dissappeared after I ran a RUU the first time.