Develop Bugs

[Q] Issue with HTC One X after bootloader unlock and recovery flash

Hey Guys,
So I am totally stumped at the moment.
I have used the Hasoon2000 HTC all-in-one and performed the following:
Unlocked the bootloader
flashed the recovery
Installed SuperSU
My phone is rooted and all is good but now everytime i try to open an app that has something to do with i think either the gpu or sound it freexes then restarts.
What should i try?? I have tried to flash stock recovery with no success and wiped the cache and tried full factory reset. All results in the same issue. I ahve even tried to remove the SU in the system/xbin and bin folders.
Should i try flashing with a stock rom?
Any help is much appreciated

scycer said:
Hey Guys,
So I am totally stumped at the moment.
I have used the Hasoon2000 HTC all-in-one and performed the following:
Unlocked the bootloader
flashed the recovery
Installed SuperSU
My phone is rooted and all is good but now everytime i try to open an app that has something to do with i think either the gpu or sound it freexes then restarts.
What should i try?? I have tried to flash stock recovery with no success and wiped the cache and tried full factory reset. All results in the same issue. I ahve even tried to remove the SU in the system/xbin and bin folders.
Should i try flashing with a stock rom?
Any help is much appreciated
Click to expand...
Click to collapse
Which apps are doing it, are they stock or 3rd party??
You will find there are still a lot of apps out there that dont work or arent too clever on ICS, so if its from the market id investigate its ics compatability b4 you do anything.
It has happened to me, PROPMODDER, it loads, but as soon as you try to alter something it all goes wrong.
Failing that, try booting into recovery, wipe the cache, dalvik cache, and finally fix permissions, see if that helps any, if it is stock apps causing the problem and you dont want to use 3rd party apps you could also boot into fastboot, open a cmd prompty changing to your ADB directory were fastboot is and try FASTBOOT ERASE CACHE, this can sometimes help with issues.
Good luck with it, i hope you solve it.

Thanks for the suggestion.
I have tried clearing both caches and fixing permission (clockwork recovery) but it has made no difference. it is any app including stock that cause this issue. Seems to be anything related to the GPU or sound (pretty sure sound).
I have the srock RUU, should i lock the boot loader and install the RUU (1.28)??

as a basic test i just tried Youtube and as soon as the video begins to play it freezes for 10 seconds then restarts

Attempted to install orignial RUU but got an image error unpn installation
I checked my phone which matchs the below file, dont know why it thinks its wrong
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe

scycer said:
Attempted to install orignial RUU but got an image error unpn installation
I checked my phone which matchs the below file, dont know why it thinks its wrong
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
Click to expand...
Click to collapse
Did you lock your boot loader before flashing the ruu?
Also, did you read some threads around here so you could understand what you are doing to your phone? I'm asking this because the all in one tool is nice, but it's also dangerous when you don't quite understand how it works

Well no i didnt have the bootloader relocked as it wouldnt load the OS back up, it just kept booting to bootloader. Turns out that was a good thing. Ran RUU and now im back to the beggining lol thanks all for your help. I will do some more reading before I root again
Any recommendations? all i want to do is a simple root to connect a ps3 controller lol

http://forum.xda-developers.com/showthread.php?t=1592355

[Soft-Brick] Stuck at boot screen

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

LG G3 Stuck In Bootloop

Hi XDA, many threads here have helped me in the past so time to ask another (probably stupid) question. It's a bit of a long story so I apologise in advance.
I've been running CM (one of the nightly builds from about 3 weeks back, don't have the file so I can't say which) on my phone for a while with no issues until a couple of nights ago when it was overheating (charging while playing a game, stupid I know) so I decided to turn it off so it could cool down without taking it off charge.
The following morning I turn it back on to find that it's getting to the blue android head logo of CM and getting stuck there. First thing I do is reboot into TWRP and flash my backup from right after I installed CM. Reboot and... same result. Okay, no biggie right? Time to reinstall CM (the latest nightly build from yesterday) and Google Apps (nano package) via TWRP and reboot again. Still stuck at the blue android head logo. The reinstall was handled after using the Wipe-Factory Reset function of TWRP, as the guide here explains.
At this point I decide to do a bit of research and learn that it's called a softbrick or bootloop and apparently flashing the stock rom can fix it. The LG software suite won't even recognise the device but a friend of mine found this guide so I attempted to run through it. All goes well until it comes time for the software to connect to the phone - I pop it in download mode while putting the USB cable in, the program says waiting for connection, runs for 14 seconds and says it's trying to put the phone into download mode, at this point it fails saying the phone can't be put into download mode.
Some of the comments beneath the article offer fixes like using USB 2.0 instead of 3.0, putting the program into compatability mode for Win7 and running in administrator mode. To be thorough I tried every USB port on my machine (both 2.0 and 3.0) and run the program in compatability mode (with and without admin mode) for several versions of windows. Same result every time.
Another friend then suggests that somehow permissions got borked and it might be worth reflashing SuperSU to the system but at this point I'm at a loss for how to do that. I have the one click root script that I got from god knows where (not this one because that didn't work for me) that has a SuperSU zip in it, presumably it flashes that to the phone when it runs (found this out the hard way because I've been a moron in the past and tried installing SuperSU through TWRP and broke the boot previously, fixed by re-running the one click root script - this was ages ago before even installing CM.)
So right now I can put the phone into download mode manually, get into TWRP and use all its functions as well as connect to my PC and use ADB functions while the phone's in TWRP but can't boot into CM or flash a stock rom. Any help would be appreciated, I've spent a whole day reading guides, asking friends and clumsily trying to fix this only to get nowhere.

Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..

jinderation said:
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
Click to expand...
Click to collapse
I haven't tried that, I didn't even know it was possible. Could you give me some more detailed pointers on how to do this? I noticed that the stock ROM I have cames as a .TOT file but CM is several files and folders in the zip. Will it install fine from that zipped up TOT file?
Thank you so much for your time.

When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model

jinderation said:
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
Click to expand...
Click to collapse
Thank you so much. I got it sorted. I really appreciate you taking the time to help me out with my stupidity.

Secure booting error after Hidden menu test

Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.

juba08 said:
Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.
Click to expand...
Click to collapse
Hello,
You need to install Mr.Bump (click on it to download it) and move it to your Phone (Go to TWRP,connect your phone with your PC,move the file to your phone)Then click install and select "Mr.Bump.zip" file.
Greetings.

thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928

juba08 said:
thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.

Sotiris02 said:
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.
Click to expand...
Click to collapse
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.

juba08 said:
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.
Click to expand...
Click to collapse
Hmm Try this guide Unbrick guide (it's officially for D855)

thanks it worked in second time now i can enter download mode i am flashing with lg flash tool. the problem is i could not install twrp before. i tried 5 roms + autorec, twrp manager and twrp offical app. and all resulted failing to open clock work mode. now i will try with D85530B_00_1217_32G.kdz
i have twrp backup in my sd card that why i am trying to boot into twrp for more than 24 hours. i hope i can do this. i winn never use eutorec i will use offical twrp app next time.
i can open android but i cant open twrp i got error boot vefication failed. i can use phone like that but i want to get my backup. if i cant i will have to install apps one by one and i will also lose some files, contacts, data etc.

I accidentaly deleted my system on my oneplus 5t

I still can get into recovery and fastboot, but when I boot into the system the screen is just black and the led glows white.
I tried sideloading a rom with adb and also installing a rom with twrp, but nothing worked. The unbricking tools also didnt help. Some of them suggest to power the phone off and press the volume up button 5 seconds, while still pressing it to connect the phone to the pc. The following steps dont help, because my pc doesnt recognize my phone.
I am exhausted, what can I do?

So what process did u try for the unbrick tool, BC that should have worked 100%. What errors did u get? Saying it didn't work does not help us.

How TWRP is unable to install a new rom ?? what error messages did you get there ?? which OS you are currently on when system was deleted? and which version ??.
try to provide as much details please

Simply flash the latest oos version.
Nd u done.
Data remain save n safe.
Nothing to Worry.