hello every one
i have a problem with my one x and i need ur help
first of all my phone touch screen didnt respond after i lock the screen unless i restart ( that heppened when i upgraded to 4.2.2)
now it doesnt respond except when i flash a new rom and when the phone is locked for a minutes its not respoding at all even if i restarted the phone
please help me with this problem and is it a software of a hardware problem?
my regards
my hboot :1.39.0000
no possibility of a match with your rom, rom Try flash again.
it is not a problem in the hardware
Hboot 1.39....all roms work on that (no incompatibility) It can be hardware. If you are certain you flashed a rom correctly. Flash boot.img via fastboot, made a full wipe, install rom.....
Related
Hi folks!
I got the Wildfire S from my Mum and flashed it to 3 different Custom-ROMs.
the problem is, her phone has an error. Everytime when waking up from standby, it takes like 5 seconds before the display does take input!
Means : When someone calls and the display went on, u have to try many times (like 5 secs or more) to receive the call. same when trying to unlock.
With stock rom it was even worse! there it took like 10 seconds or more.
now we want to flash back original rom without root and take it back to our dealer and let it change with a working phone. problem now is, the USB-Ports seems to be broken or so??
when connecting with her laptop or even with my PC the pc's recognises the phone as "unknown device" and when trying to install usb-drivers for asb or fastboot, it says "the device is already up to date".
so i CANT use fastboot, adb or even the RUU-flasher-exe files
no i am searching for a way to flash the phone with a stock rom out of the recovery menu.
is there a way or a way to fix the usb-driver problem ???
someone plz help!
i installed htc sync and tried to flash the ruu manually by fastboot.
it only flashes system.img and the boot.img. when trying to flash the other stuff like hboot and recovery or radio it says "wrong verficiation id. Remote not allowed"
now the phone wont boot further than bootloader or recovery
bootloader is unlocked!
plz someone help!!
Is there a way to flash a stock rom out of the recovery?
can SOME PLEASE make me a backup of his system and upload it anywhere so i can fix mum's phone?
plz ppl help!
ok got it back working. with custom rom only, but its ok for now.
Hi,
The HTC Desire HD phone was hanging during boot (original RUU ROM). There was no luck to get the phone working again.
It was possible to get into the bootflash mode by holding the power en vol down button. I decided to upgrade the ROMto the latest version of Android. (after searching if it was supported).:cyclops:
First I upgrade the HBOOT to version 2.0.0.0029 to make rooting possible.
So far so good. Getting Root access en ready to go. (Security on)
First a upgrade for recovery flash to install recovery-CWM-5.8.3.1-Build6.
After doing this I installed the new rom (cm-10.1-20130322-UNOFFICIAL-ace) using CWM.:fingers-crossed:
This was going well. Booting the phone up and it was booting. But when displaying to enter the pin-code I discovered that the touchscreen was not working well. I can touch it but not the right numbers. It seems it is out of sync? I can’t unlock the phone.
It seems the up/down is working but left to right not.
Installed the rom again and with no luck. Then a downgrade to the original RUU ROM (RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed). The phone booted up but also the touchscreen was not working well. All the rooting was gone. So the RUU is orignal.
The did the upgrade again (HBOOT and the flash recovery).
Now I installed the ROM (cfx_ace-4.2.2-SR15) and GAPSS.
It is booting but the screen is still not working well. Did I do something wrong? Of is there a other kernel to resolved the touchscreen problem?
Mee to sir
Had the same on 4.* ROMs...
Then I had to reboot (put out battery), then it worked. Next Reboot the same nonworking touchscreen...
I'm now running Android Revolution HD (2.3.5, Sense 3.5) all works, no probs anymore :laugh:
Ok so guys i had just rooted my htc wildfire s (or atleast thought i rooted it ) and was trying to install a cyanogen mod ROM , it would not install ,if it would install it would be stuck at the htc logo screen , now i thought this would be the fault of recovery so i decided to install another recovery and flash that with cmd (fastboot flash recovery recovery.img) but then when i booted in recovery it would show me the pink recovery, i got a little scared and flashed another recovery and now the recovery will not even boot . it will just go on htc logo and black screen , i tried many different recoveries but no avail , it is in s-on right now , please forgive me if this sounds noobish i really am a noob at this .please provide me with a solution and tell me if it is bricked and if i can repair it by taking it to a software shop and asking them to do it for me (Just advise me if i can come back from this)
Flash the first recovery, which actually worked, and if it installs, wipe everything and flash a basic CM7 rom. It'll work. It's just soft bricked don't worry.
parasthakur37 said:
Flash the first recovery, which actually worked, and if it installs, wipe everything and flash a basic CM7 rom. It'll work. It's just soft bricked don't worry.
Click to expand...
Click to collapse
actually i gave it to a software store , he said he couldn't do it as the files were not to be found ... i think it might have been bricked but seeing as i can access h-boot only and when i turn on the phone it only stays on the htc logo screen and does not proceed can you call this bricked . ? i tried the first recovery as you mentioned but it was no use ... i tried relocking and unlocking bootloader again but it seems as if that was unnecessary as nothing different happened .. im still waiting for an answer
This is really very weird.
Check this out
http://forum.xda-developers.com/showpost.php?p=28646721&postcount=5
Start from square one, unlock the bootloader, flash the recovery, if one doesn't install, try another, at least one will surely work, and then flash a new rom.
All the best.
Remember, android can never be bricked, there is always a way out.
parasthakur37 said:
This is really very weird.
Check this out
http://forum.xda-developers.com/showpost.php?p=28646721&postcount=5
Start from square one, unlock the bootloader, flash the recovery, if one doesn't install, try another, at least one will surely work, and then flash a new rom.
All the best.
Remember, android can never be bricked, there is always a way out.
Click to expand...
Click to collapse
thank u for the quick reply but i donot know how but i just flashed an old recovery and voila it worked .. now i am a little scared to proceed please guide me what to do to bring back the stock rom ...
ITS DONE
i finally got it to work thank u so much i used jelly king rom on it and it worked DDDDD
Press thanks.
I was using the Lollipop Ressurection ROM when suddenly my phone starts to bootloop, and i have done all the methods to install Original or Original based ROM's, but it always freeze and reboot on the first boot screen. Just the CM11 was able to make the phone turn on but it doesn't recognize the SIM card. Help me please!!!
help what, all we can say is flash back to your orig backup or flash back a stock firmware.... maybe you have hardware problems, we dont even know what hardware your using, how long have you been using ressurection, what were you using before.... etc etc... you can boot into a recovery fine?
Hi guys,
(Samsung S4 Mini GT-i9190)
I could really use some help.
I have been searching all over and perhaps I'm not understanding what is being said so if it sounds familiar and there is a solution then i'm thankful.
So about a week ago, the phone came back from repairs and had the motherboard replaced after the phone was washed by accident. Nonetheless, there hasn't been any hardware defects besides signal loss now and then.
When the phone came back, it had 4.2.2 and it automatically picked up the update to 4.4.2 which I did. The phone worked fine until 2 days ago, where it just stuck at the Samsung galaxy gt-i9190 screen and just freezes there.
I can boot into a custom recovery (Philz) (not stock recovery for some reason) and download mode. I then attempted to install CM 11.0 as I got frustrated. It worked, booted past animated logo and install the apps until i came to the language section where the touchscreen which didn't work (unresponsive). I then reverted back to the stock ROM found at sammobile (i9190xxxCOD2XFA - South Africa), loaded the custom recovery and still no booting past the first screen. The custom recovery touchscreen (Philz) is also non responsive (besides using the volume keys, home button and power for navigation).
I flashed a couple of times, nothing works.
Is there a root cause to these issues? The unresponsive screen, not booting properly?
Some info: KNOX is voided 0x1
Please help!! Thank you in advance
It's not „root“ that cause your problem. You should have to choose right recovery for your model. Flash back to original ROM and look for one of fully supported custom ROM here on the XDA and fallow all steps how to flash it properly. Succes ! Cheers !
Alright, I'll try that. What I did in the meantime was flash, Slimkat 4.4.4 UNOFFICIAL rom for I9190 (http://forum.xda-developers.com/showthread.php?t=2708677).
The rom booted into the andoird system but the touchscreen is still unresponsive.
@Boombastical .. If you can help me by giving me a guide in order to do what you say, then please do help. Even in recovery especially TWRP the touchscreen is unresponsive except for ClockWorkMod and Philz. So i don't know if it is hardware related or I'm doing something wrong.
Its driving me crazy :crying:
Update
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
GeezyTab88 said:
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
Click to expand...
Click to collapse
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Confirmed for that is
GeezyTab88 said:
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Click to expand...
Click to collapse
Hey guys, just a quick update.
I reloaded Cyanogenmod mod CM13. I can confirm that my screen didn't freeze up and booted perfectly. I also then decided to take a chance adn reload the stock rom 4.4.2 and it also worked perfectly and booted directly into the OS.
I'm guessing the screen calibration was out.
So if this happens to you, I would suggest loading a custom rom and doing the screen calibration reset through adb and then test again with another custom rom. Once you comfortable, you can reload a stock rom.
I used Philz Touch for recovery
Thanks to everyone who put posts up .. Time to rest
Not working again!!
Hey,
So in my previous post I said I got it to work. Well I did, up until a few minutes ago when the phone just decided to freeze up again. I restarted the phone and would you know, back to square one!
I've noticed issues that I'm wondering if they could be the problem:
1) The audio didn't work at all. By audio, I mean the mic. When I did voice recording, it just gave static, whatsapp calls, the other person can't hear you as well as regular phone calls.
2) I just rooted the phone in order to change the audio_policy.cnf and delete lines relating to the above audio problem but then the screen, return, and menu button didn't function. The screen could still rotate until I pressed the power button to lock then unlock and then it didn't unlock :crying:
So once again, some help guys please. Is it rom related, hardware (motherboard, chip) or software that just isn't working right? Could it be KNOX?
Thanks