Develop Bugs

imate kjam won't boot past splash

Hi,
First, I ran some tests on my kjam. The kjam came default with the kjam rom on it, naturally. I wanted to CID unlock this phone, so I downgraded the rom to button's "beer glass" splash screen rom. Then I was able to run aWizard successfully to CID unlock the phone. I then upgraded back to the original kjam rom. Both the downgrade and the upgrade went smoothly.
I then found out I wanted to customize my splash, so I downgraded again. I customized the main splash (not the HTC one) using aWizard. Worked like a charm. I also ran some extra itsme tools to read and write from rom in some locations I needed access to.
Everything was working great at that point. But the downgrade ROM didn't properly respond to some of the printed keys on the kjam keyboard, so I thought I should upgrade again. However, this time, I decided I want to keep my splash etc., so I tried to upgrade only my radio and OS rom, as backed up by aWizard previously from the original kjam ROM. I used aWizard to restore the selected areas of ROM, rather than the RUU tool.
I upgraded the radio ROM, didn't reboot the device to keep the radio and OS in sync, upgraded the OS ROM, just as that was happening, the phone received a phone call (or text message, do not know which), and hung. While the aWizard eventually completed the upgrade, the phone did not reboot or "un-hang" itself after aWizard displayed success (there was no error on the console window).
So I soft rebooted the phone. The splash screen came, but without a GSM version on it. I was like, "shoot!", something bad must have happened, lets just put the full kjam rom on this, and get it over with - never mind the custom splashes. So I went into bootloader and applied the kjam rom.
Now it displayed the GSM version as well on the splash screen, but again, it never left the splash screen. I was like, again, "shoot!", lets just go back to that old downgrade ROM with the funny keyboard, then we can figure this out again. So I went into the bootloader and applied the downgrade ROM.
Alas, the beer glass splash screen remained hung as well! And actually, since then, I've downloaded and installed ALL ROMs I've been able to find - ALL of them have hung.
My bootloader is still working fine and dandy...any idea why this might be happening? Was the problem in the phone call I received? In using aWizard without rebooting? In using aWizard at all? In trying to manually edit the machine ROM using itsme tools (mind you, those edits worked fine until I started updating the GSM/OS ROM)?
And oh, after hanging for a while on the splash screen, the phone screen starts flickering real bad (whilst still on the splash); in case that provides any help.

To clarify the bootloader situation a little more:
I've got FULL bootloader capability. I can mtty into it, I can write commands, I can install full new ROMs from the bootloader, etc. So this would seem to indicate my phone may not be a brick yet...its a brick that can display changeable wallpapers I even figured out how to draw progress bars and write text to the bootloader screen using MTTY commands. Fun, actually! Its a $700 etch-a-sketch pad

same probleme
Hi sir mimarsinan,
i have Qtek9100 with same probleme. Please give solutione for me to use phone again.
Thank you
Lionel
PS:
sorry for english

no good
Hi Lionel,
better not wait for him to reply to your request...
go here: http://forum.xda-developers.com/showthread.php?t=276963 and see solution that worked for many
good luck

Can any of you facing same problem post the reason(s) you believe to be responsible for the situation?
I think that in my case (yes, it happened to me too) was the fact that i flashed only OS chunk ending up with IPL/SPL 1.xxx and OS 2.xxx and i didn't use any RUU; instead i used an itsme program (podcread.exe)
cheers

How to get rid of the branding

I have a Question ,I flashed duttys rom with no problem and all is fine,but was just wondering how to change the first boot screen with this ugly looking T-Mobile screen , I thought when you flash a rom that this First boot screen is changed also,Would be grateful to have the original HTC boot screen instead of this T-Mobile screen,,
Love this forum ,best PDA forum on the net!!!!

Have posted the Zip file containing the HTC splash.
You need an active sync connection running and then open the RUU.
Select update ROM and it will then write a new splash screen but won't alter your O/S Rom.
It takes less than 2 mins. Oh, make sure your battery is more than 50%.
JSM1970
Credit to Lord Ghost for Official Splashscreen

Thanks Alot Really Supi

Kaiser loocked before flashing android

Yesterday I try to flash android on nand in my at&t tilt, with valentines rom, I flash the kernel recomended and follow the instructions but the rom don't boot, so, I dedided re flash Winmo.
First at all, I try to flash a cooked rom I make, the flash completed 100% and the phone reboot, but stuck on RBG screen!!
Then I try to flash winmo 6.1 custom rom, and this one works well!! but.........
is the only rom I can use, cause if I flash another rom (custom or cooked) the boot stuck on RBG screen (the screen where the radio, roms and version appears in red letters)
I try to unlock security again, thinking this maybe the problem, using pof tutorial, and having in tricolor screen the message SECURITY UNLOCKED in red letters. before that, I flash again another rom but the problem still!!
I try to flash a winmo 6.0 custom rom, to use jowkys tutorial but the rom stuck in RBG screen too.
So... What can I do? I'm confused... PLEASE HELP ME!!!!!!
For extra info... in memory data, in the part of internal storage only appear 30Mb!!!! and not the 145Mb that should be!!!
SLP: 1.0 olipof
Radio: 1.70Olinex
ROM: Winmo 6.1 oficial

I think you need a recent hard SPL.
Look at here: http://forum.xda-developers.com/showthread.php?t=498320
If I am correct I installed DaveShaw's 3.34. I can't check it because i'm not a kaiser owner now.
Bye

Sony Xperia Pro with PACMAN

Dear Techies
I love to play around and use new gadgets ans fotware. Android is my first choice but unfortunately this something very new for me. I was looking for Jelly Bean and got it as Pacman. Which i came to know is combo of three ROMS features.
I decided to go for first time for custom ROM with my SOny Xperia Pro MK16i. It was having its official ROM as ICS (b 587 i suppose).
I could read 3 steps mainly one was Unlocking the boot and then Root and then flash ROM. I did first 2 (right i suppose) but when i came to the last one for flashing the custom ROM i suppose i did something wrong.
with flashtool i flashed IMG file in fastboot mode. I was done without any error i did restart to the system. Pacman logo came with SONY under it but then nothing i did 3-4 times but i was left with very dim light screen with nothing on it.
But i suppose this was a better position than now. here i think i did the main mistake i again flashed with recoveryNeo IMG (it was in fastboot folder which i downloaed earlier).:crying:
SInce then its blank no light for first 2-3 attempts for restarting it vibrate but now even it doesnt vibrate.
I dont what to do next lots of question did i bricked my phone. Is that recoverable ? can i still get it back to official ROM if yes then how or can i still put custom ROM if yes then HOW ?
Please help
thanks in advance

Please guys Help me
Hunk2012 said:
Dear Techies
I love to play around and use new gadgets ans fotware. Android is my first choice but unfortunately this something very new for me. I was looking for Jelly Bean and got it as Pacman. Which i came to know is combo of three ROMS features.
I decided to go for first time for custom ROM with my SOny Xperia Pro MK16i. It was having its official ROM as ICS (b 587 i suppose).
I could read 3 steps mainly one was Unlocking the boot and then Root and then flash ROM. I did first 2 (right i suppose) but when i came to the last one for flashing the custom ROM i suppose i did something wrong.
with flashtool i flashed IMG file in fastboot mode. I was done without any error i did restart to the system. Pacman logo came with SONY under it but then nothing i did 3-4 times but i was left with very dim light screen with nothing on it.
But i suppose this was a better position than now. here i think i did the main mistake i again flashed with recoveryNeo IMG (it was in fastboot folder which i downloaed earlier).:crying:
SInce then its blank no light for first 2-3 attempts for restarting it vibrate but now even it doesnt vibrate.
I dont what to do next lots of question did i bricked my phone. Is that recoverable ? can i still get it back to official ROM if yes then how or can i still put custom ROM if yes then HOW ?
Please help
thanks in advance
Click to expand...
Click to collapse

Xperia Pro flashed
Hunk2012 said:
Please guys Help me
Click to expand...
Click to collapse
After flashing the kernel, you need to boot through recovery mode with the PACman build (.zip) available on your SD storage. To log in to recovery mode, as soon as you get the PACman SONY splash screen (when LED turns blue) press the volume down button located at the side of your device. Once into recovery:
1. back up your data
2. wipe all user data and cache
3. Install update from a zip file and pick the relevant ROM
Just in case you're completely locked out and want your old ICS 587 build, just switch off your cellphone, connect it to your PC with Sony PCC installed. In all probability, PCC identifies it as a Sony device but not the model. Follow the steps on the screen and choose xperia pro when the option to install stock OS appears.
I bricked my xperia pro twice before successfully upgrading to PACman 17 so its a pretty normal scenario.
Do let us know how goes it!

HTC One x (protoype) bootloop after jellybean update

HTC One x (protoype) bootloop after jellybean update
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just go to the top of the page where it says "Reason:" I put a link in it just copy and paste the link in your browser, sorry but this is the only way I can share links as I don't have 10 posts. The pictures show all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and Thank you for it, I hope you can help me!