Develop Bugs

[Q] htc one x bricked. not charging. not booting. only bootloader

usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed

http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!

kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...

FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up

hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)

Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA

Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.

Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/

Is my M8 bricked?

Hi XDA-Fellows
1) thanks for all the help of this community so far
2) my problem: I had my HTC One M8 rooted, installed TWRP (I think in the end I had 2.7.8.0 as last version) and Cyanogenmod with a nightly build of around 18. March 2016 installed! THEN the big mistake happened. In advanced developers menu of cyanogenmod I activated the option that was called something like "on update of system also replace recovery software". That obviously was stupid.
Upon rebooting normally TWRP launched and installed the latest nightly. This time I see the white screen with HTC logo on it, red text in bottom, top part of the screen shows "ENTERING RECOVERY", 3 seconds later I see a black screen and every like 2 or 3 seconds it looks like the screen gets powered, it flashes darkgrey shortly (again, looks like it gets powered but instantly shuts off immediately).
This just can be stopped by pressing either P+U or P+D for like 10 seconds. Then again, white screen with HTC logo and ENTERING RECOVERY and the screen switch on/off-loop.
Is my device bricked? What can I do now?
Any help is appreciated.

Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..

BelDev said:
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
Click to expand...
Click to collapse
Yes I can enter bootloader. How should I go on from here on?

Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..

BelDev said:
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
Click to expand...
Click to collapse
Thanks. I will give it a try and give feedback.

It worked. I could enter bootloader, switched to FASTBOOT mode, installed ADB Drivers for windows and replaced recovery with latest TWRP! THanks a lot for your help! I thought I could throw away my M8

Well. It worked not completely. I was able to reboot my phone into the Cyanogenmod. But upon entering recovery mode (which I expected now to be TWRP) I get the same result again ... Screen off/on within seconds, repeating endlessly

I think you need to reflash the boot.img and the ROM completely. Because i don't know why do you have a black screen.

I activated root access for apps and tried ROM Manager first! It failed, then I used flashify which worked. Automatically downloaded latest TWRP (3.0.0.1) and flashed it, reboot into recovery. Everything works like a charm again! Thanks again for your help!

tab s 8.4 wifi stuck in TWRP boot loop

I was an idiot and did a factory reset (not while in recovery mode) and when everything restarted I ended up with my tablet stuck trying to load TWRP - I am/was running the lastest CM nightly from the end of May, I don't know what version of TWRP is currently on there. I just get the blue teamwin screen that stays there for about 5 seconds, flashes black, then back to the teamwin screen again. I got it into download mode one time, but as I was not in a situation where I could take advantage, and have since forgotten what I did to get it into download mode. (I think) I've tried all the button combinations with the tablet in the bootloop, and with it off (dead battery) to no avail. I've checked the forums and the few that I've found with the same situation as me, there is either no solution offered, or the solution was never posted, just that the situation was resolved - the thread most resembling my situation is this one http://forum.xda-developers.com/galaxy-tab-s/help/galaxy-tab-s-sm-800-stuck-flashing-twrp-t3219865.
Any help would be greatly appreciated. If you need more information, let me know. Thanks!

S4 Mini I9195 flashed with official LineageOS ROM does not start anymore

Hello!
the issue:
My device s4 mini (serranoltexx) does not boot further than the initial Samsung logo (showing the "normal" warranty kernel in the left top end of the screen), and then turns black. I can't do anything beyond this stage. When I take out the battery and insert it again, the device boots /starts automatically until the samsung sign and turns black again.
the background:
Last year in July, I flashed mys4 mini (serranoltexx) using odin, twrp and one of the latest official lineageOS Roms 14.1 (July 2018), with nano gapps. But since this morning (10. of January 2019), I can't start my device anymore. The latest update, which I did for the ROM was in July. Due to work reasons and since the official maintenance expired, I did not follow any other Lineage updates for my device, e.g. on this website. But I could use my device daily without any problems until this morning, when I started an app (music player) and after a few tones, the music stopped and the device turned black. Since then I could not enter or boot my device properly. I use a 32gb sd card as an integrated storage.
steps already done:
I tried to enter the recovery mode. When switching it on (taking the battery out and back in), I can enter the initial screen of the recovery mode, but after may be 3 to 5 seconds it turns black again. Saying nothing. I intended to flashed fresh using odin and twrp, and then the latest lineageOS ROM versions from your website. But the same sequence happened again: After using the key sequence for entering the download mode, I can enter it and push the volume up button, but then the device turns black again, saying and reacting to nothing. I changed the batteries (I have several), but it did not change anything. And this puzzles me ....
I know that my device updated trwp yesterday - when my device was still working - but I turned it off and I could turn it one this morning functioning well until I used an app.
the question /the request:
Is there any possibility to fix this problem? Could anyone help me on this issue, please. I really like my s4 mini, I do not want throw it away. I would really appreciate any advice which would possibly fix my problems.
Many thanks in advance for your replies and help

Question for the experts (hardware)..

So, this is more for interest than anything else, but here's the scenario.
A friends 5T did a sudden shutdown. He picked up the phone, unlocked the screen and opened WhatsApp. An error message flashed on the screen - too fast to read - and the phone shut down immediately. He tried to restart, but it was stuck at the boot logo (circle with rotating dots).
We had a go at trying to get it back up again and did the following. I should note that both recovery and fastboot were available, however the bootloader was locked.
1) Booted into recover and sideloaded the latest OnePlus ROM - Stuck at boot logo
2) Got hold of unbrick tool and flashed with latest version (seems to be Android 8.1) - Stuck at boot logo
We were about to give up assuming a hardware issue when on a whim I tried the old unbrick for Android 7. Amazingly the phone booted. I quickly enabled bootloader unlock and unlocked the bootloader. We then flashed TWRP and tried to flash a custom ROM (Bliss in this case) - followed all the instructions to the T and got stuck at the (Bliss) boot logo (very cool boot logo by the way).
We then flashed a rollback version of Android 7 designed for folks coming back from one of the early beta 8 versions. This booted again, although it replaced TWRP as expected. We then sideloaded the latest version of 7 we could find (seems to be 7.11).
So here's the question. The only thing not working on the phone is the Wi-Fi. It does not switch on and shows a MAC address of 02:00:00:00:00:00 which indicates an issue. So I'm assuming something to do with the Wi-Fi has died on the mainboard. However, Bluetooth still works, SIM cards still work. I can use the phone normally with a mobile data.
So, what would stop anything above version 7.11 from booting if just the Wi-Fi is broken? Is there some link to this that was added in Android 8. It would great to update to 8 or 9 and still be able to use the phone, as everything else seems to work.
P.S. I have noticed that the camera takes about 10 seconds for the image to appear after the app opens, then works fine after that. Related maybe?
Anyway, was just wondering if anyone knows the inner workings and can shed some light on this one.