Develop Bugs

issues with bootloader

Hey i hope all is good.
I really need your help. I have a TILT 2 cell phone and by mistake a friend activated the bootloader. Previously the ROM has been updated. the phone got stuck in that screen and the only way to turn it off is removing the battery. so, i try to reboot the phone and it only loads the bootloader with a flash message saying "no image file". ok, i though, the ROM was damaged and after reading a lot in the forums, i followed the instruction to put a new ROM. I connected the phone the the computer and the message in the phone changed to USB and my PC installed the HTC USB Sync driver (but Active Sync does not detect the phone); anyways, i ran the task 29 and a new rom. I was able to see the progress bar in both (PC and Phone) but then the phone reboots and loads again the bootloader. I tried to use the HARD SPL 1.00 as well but it does the same thing after finishing the flash it loads again the bootloader.
can some help me pls?? i'm new in this and the phone is a work tool for me i really need your help.
rgds

You should do the HSPL before flashing a ROM (unless it was already done).
I would try to flash the newest HSPL, then a ROM.

Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls

jsolanon said:
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
Click to expand...
Click to collapse
Hrm, have you tried doing a task29? Re-flash the ROM after task29.

yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do

jsolanon said:
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
Click to expand...
Click to collapse
So you've flashed the stock ROM? Have you tried relocking? Probably won't do much, but worth a shot I guess.
When you flash back to stock you flash the stock ROM, then relock, then reflash stock.

Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help

jsolanon said:
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
Click to expand...
Click to collapse
My phone is never turned off. I'm not sure what else to suggest, you've tried seemingly every step that could remedy this problem. Radio firmware probably won't help, but it shouldn't hurt either - you could try a new radio...

hi , this happened to me, solved it by reloading the rom again via sd, once it finish maybe you will see the bootloader screen again, so with stylus pres the reset buttom a few times until the rom boot , this can take several times to make it boot. after revive your cell , do a task29 then reload the rom again then do a hard reset, this happened to my 2 times, and its still alive ,good luck.

Same Problem
Hi,
I'm having the same problem. Installed the latest official ROM from HTC/ATT (gorgeous), and same problem after install. Whenever you try to reboot, it gets stuck in the bootloader screen. The last 50 tries it will not reboot at all, even after removing the battery and hitting the power button. This used to work occasionally.
Any other process anyone knows for getting the device to read the ROM?
Is the phone just worn out?

I suggest you reflash the shipped rom to your device and after the flash finishes and your device begins to boot immediately remove the battery to turn it off before it boots. Then replace the battery and press and hold the Send and End keys and while holding them down press the Power button and follow the instructions to factory reset(hard reset).

[Q] Screen freezing if goes into sleep, never turns back on

Having an issue with my HOX today. It was in my pocket all day at work, pulled it out to make a phone call and afterwards when I went to hang up, the screen would not turn back on. It is still responsive to touch input and I can still unlock while the screen is black, but it still does not turn on. I can however hard restart it and the screen comes back on and I can still enter fastboot/recovery. But if I let the phone stand-by the issue repeats itself. I was on BinDroid v2 without any kernel when this happened, I got the phone into recovery and flashed both Energy and franco.Kernel and this issue is still happening. Is my best option to try and flash the original RUU and a stock rom?

I've had this issue since flashing the bricked kernel. I think the best option would be to go back to stock.
Sent from my HTC One X using XDA

i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.

Can't you restart the phone by holding the power button in?
If not then that's a strange one.
Sent from my HTC One X using XDA

IPS1989 said:
i have the same problem but in my case the phone is just suck at a black screen. am not able to do anything at all, am just sitting now waiting for my battery to die so that i may be able to reboot it. if you any suggestions to solve this, please do tell as i am in a dire situation.
Click to expand...
Click to collapse
This is what I'm doing as well. I tried using a nandroid to go back to stock and that still doesn't work. It's almost impossible to get the phone into the bootloader but it's do able. One thing I'm noticing though, is that if the screen does manage to turn on when I boot it up, it wants to send an error report to HTC about it. Also, once the screen goes off and won't come back on, it's very laggy to other inputs. Example, pressing the power like you want to wake it and then pressing to volume keys has a very noticeable delay.
Thankfully, HTC is already doing a warranty call on it for the yellow spots on my screen (now like dark orange spots now)
Update: HTC said that the screen issue I'm having is unlikely able to be fixed by a software repair and that I have to send it in for a repair. 7-10 business days.... great.

Also with an untouched phone
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it ;-)

lisophorm said:
Guys, I am afraid this is a hardware problem. My phone is UNROOTED with the last upgrade and I am having the same issue.
Take it back to the assistance. OOPS, you rooted it
Click to expand...
Click to collapse
Hi.. I'm also facing the same issue ... however this didn't start till few days ago. I have had this phone for six months now and was on stock most of the times.
But since this week , I started getting issues where once the screen goes black , it doesn't come back on. Although , I can reboot the phone with long press power button and also go back to bootloader/recovery without any issues.
Can u confirm its the hardware issue ? If yes, did the techinicians told you anything about what is causing this and it can be corrected easily ? I want to try my hands on it before going to customer care as I have void my warranty and will have to pay for repairs.
Cheers !

its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2

shadow fiend said:
its kernels issue.
you should flash orginal kernel or flash a rom with irginal kernel to fix this issue.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
First time I started facing the issue, I was on stock 4.0.4 rom with stock kernels unrooted and locked bootloader.
So not sure if the issue was related to kernel. Anyways I'l try to get stock kernel and use it.
Cheers

OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio

dev997 said:
OK.. so I did tried to get the stock 4.0.4 rom with stock kerne but same issue.
Also in the meanwhile I tried all other prominent HOX roms , bot AOSP and sense.
I have found that the issue is more severe and frequent on Sense roms (confirmed on all JB roms Ondroid, Maximus and ADHD as well as VenomX) but its very much stable on AOKP ICJ and CM10 roms. However still sometimes screen doesn't come on in ICJ too.
Now I'm starting to think there might be some issue with HBoot 1.28. My CID is 001 so there shouldn't be any issue, but if I remember correctly when I installed the Hboot, there was a 'Failed' message , but the process did completed.
Should I try to again flash Hboot 1.28 as I can't apparantely go back to older ones ? anything else I should try.
I'd really like to hear from some ppl who have faced this issue and mentioned in posts above on how they managed to solve it.
Cheerio
Click to expand...
Click to collapse
have you solve this issue?

new problem?

okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.

mr.dj26 said:
okay guys ill make this quick.
my one x had no problems at all since I got it, few days ago htc launcher starts to crash and i realize a bit of battery drain and some lag, so I pressed the power botton for 10 sec for a full restart. after boot(ONEX logo) comes a black screen and i cant do anything, i press power button nothing happens just the buttons at the bottom will light up.
i posted my problem here at XDA and i was told to do a factory rest which i did and it erased all my pics and data .
anyway, today i pressed the power botton and same problem happend so can anyone tell me whats rong with the phone?
things you may need to know.
fast boot mode is on
android version 4.0.3
htc sense 4.0
software 1.26.401.2 (I didnt update software because im hoping to get S-off.)
PLEASE GUYS HELP
i really dont want to factory rest my phone every day.
Click to expand...
Click to collapse
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?

PAGOT said:
Why do you have fastboot on?
And why you didn't update? Where did you find out that you will get S-OFF on that firmware?
Click to expand...
Click to collapse
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?

mr.dj26 said:
software update will update hboot, and fast boot is on because when i shut off the off and turn it on it starts up in seconds.
anyway, any idea about the problem?
Click to expand...
Click to collapse
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?

Turn off fast-boot. And then do a reboot. Elimination my friend.

PAGOT said:
Well try to use your phone without the fast boot on?
And okay I still do not get the point? Have you asked in the S-OFF thread and they said, that S-OFF will come only for the old hboot and everyone who updated wont get S-OFF?
If that would be the case, there would be many many unhappy ppl.
So you rather will be on a half year old bug filled fw as to update and use your phone properly?
Click to expand...
Click to collapse
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help

oliseo said:
Turn off fast-boot. And then do a reboot. Elimination my friend.
Click to expand...
Click to collapse
so you think this is the reason of the problem?
thanks

mr.dj26 said:
i tried hard reset with both fast boot on and off both work; i just dono why im having this problem.
and about the update, i didnt have any issues with my phone so I didnt update and I have read somewhere that after update it would be difficult to s-off i dont remember.
thank for your help
Click to expand...
Click to collapse
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..

mr.dj26 said:
so you think this is the reason of the problem?
thanks
Click to expand...
Click to collapse
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.

HebeGuess said:
To be rude, you think you have no issues with 1.26 doesn't means that the firmware is stable. And yes, everyone here knew 1.29 is the ways much better than 1.26 with a bunches of fixes and tweaks.
For the s-off progress, as far as I know those developers who are working on it do not stayed tight on 1.26 hboot (correct me if I'm wrong), though some of them has s-off devices. The main barriers on s-off path was not a newer hboot patching holes (there is no big hole found yet) but was the HTC hardworks to barricaded us to have a talk with tegra. On my guess, even there is a solution reveal it will be less likely to be achieve through an old hboot only.
To be honest, you are the only here i had seen that are stayed on 1.26 for s-off..
Click to expand...
Click to collapse
lol
thanks for your help

oliseo said:
With bugs like this, it's a process of elimination. Unless it's specifically ruled out (ie, you still suffer the same bug regardless of fast-boot being on or off), then you can only assume that may be.
See what happens if you turn it off. If it works, you know that was causing the issue. If it doesn't, then repeat the process until you eliminate all possibilities. (ie, does it crash after you've transferred files via USB, switched WiFi on/off).
Once all possibilities (within your remit of course) have been exhausted then it's time to send it off, as it's nothing you can solve and it could be a hardware issues (bad memory perhaps??)
Anyway, let's go for the easy fix first, and I keep my fingers crossed that turning off fast-boot helps.
Click to expand...
Click to collapse
i really appreciate ur help guys
i just had the problem again, fast boot was off.. just did a factory reset
theres no crashs when transferring file or turning wifi on or off.
this is really weird.
do you think flashing RUU may help or its the ame as factory reset?
thanks..

Worth trying.

BenPope said:
Worth trying.
Click to expand...
Click to collapse
I have never flashed an ruu before.
can you tell me how that work and from where I can get it? my cid is J_15
and im useing mac, will it work?
thanks m8

There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.

BenPope said:
There is a sticky Endeavor shipped ROM collection thread in dev section.
You can't easily do it from Mac, if at all.
Click to expand...
Click to collapse
theres no guide on how this works..
my cid is J_15, which file should i download ?:S
i really hope this would do it, htc support at my place isn't that good and i really dont want to send it back and wait for ages

,,
i rebooted the phone now more than 10 times with now problems,
the phone now has no apps or anything brand new.
could it be a cause of apps or something?

Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.

BenPope said:
Just look at your software version, then find the RUU in the link from the first page in the sticky thread.
Then borrow a Windows machine and run the RUU with your phone connected.
Click to expand...
Click to collapse
okay here it is 1.26.401.2
now when i want to download it it requires premium account WT* ?!

.
dose flashing the RUU require adb or only htc driver?

I'm in the same position. Woke up yesterday, booted phone, black screen after "HTC One" screen. Oddly I could change the volume and the volume changer would display on a black screen. Restarted, same thing. Factory reset, no problems. All the while fast-boot is off.
Same thing happened this morning, cold boot, "HTC One" screen then black screen. Factory reset and immediately rebooted - same thing again! is this a hardware issue or a corrupt software issue?
Will go and join the incredibly long and slow moving at the HTC service centre after work.
---------- Post added at 12:34 PM ---------- Previous post was at 11:50 AM ----------
I've spoken with HTC customer services and they recommend taking the phone in to get it flashed - basically they think that there is a problem with the software. They claim it is a quick job.
They offered to come out to my office and collect my phone and return it tomorrow - I'm impressed with that level of service... pending they can fix it with a simple flash of the firmware!

[Q] Stuck to boot image+restart itself in recovery

Hi guys I'm new posting here but can't find the solutions anywhere...
My HTC Desire HD is stuck to boot image ( http://forum.xda-developers.com/showthread.php?t=1673652 ) which I flashed two weeks ago without problems, is mounting the JellyTime R10 rom ( http://forum.xda-developers.com/showthread.php?t=1778202 ) from like a month without any problem since yesterday when I'd travel to a vacation and let the DHD at home to found it back stucked as I'm come back.
The problem is there is no USB Debug, which I searched without finding it when the DHD was ok, the Volume Down is brocken and I'm able to enter the recovery only by attacking the DHD to an energy sources.
Unfortunately when I chose an option like "whipe" for example, it restart immediately and then get stuck.
I've tried to re-flash the recovery but it says "error device not found" so I guess is cause of the USB Debug...
Any ideas ? I like the phone and found nicely from about 2 1/2 years so I' wasn't planning to change it at all :/

I've probably solved the problem.
I've attacked the DHD to the charger in order to enter the recovery and than used the physical buttons (home, menu, back, search ) and not the volume and power button to enter the wipe options. it worked without restarting. I've cleaned the cache and it stopped looping.
Now I'm reinstalling the clockwork and a new 2.3.x rom. hopping it will be really stable unlike the other I've tried.
If someone can please link me a stable rom for my DHD it would be really a nice guy unlike other 74 who read and skipped the question until now !

PROBLEM NOT SOLVED.
I solved only the loop thing, the phone still don't hard resect and is invisible to the computer, may be because if I attack it at a power source it turns on in recovery and then crash, I've unlocked the developers section in the settings and turn on the USB Debug but the phone is still invisible.
I really need help about that, is there any way to solve that problem ? I need to factory resect it to solve the problems.

Can you reflash a recovery from fastboot? Have you tried running a RUU?

bananagranola said:
Can you reflash a recovery from fastboot? Have you tried running a RUU?
Click to expand...
Click to collapse
hi, sorry for the late answer I've lost the hope XD
I bought a note 2 but still REALLY interested in saving my DHD.
Unfortunately I can't access the phone from a pc because if I attach it to the mini usb it immediately turn on in recovery mode, and can't change anything by the recovery mod, it start but it just don't change anything :/

bimbows said:
I've probably solved the problem.
I've attacked the DHD to the charger in order to enter the recovery and than used the physical buttons (home, menu, back, search ) and not the volume and power button to enter the wipe options. it worked without restarting. I've cleaned the cache and it stopped looping.
Now I'm reinstalling the clockwork and a new 2.3.x rom. hopping it will be really stable unlike the other I've tried.
If someone can please link me a stable rom for my DHD it would be really a nice guy unlike other 74 who read and skipped the question until now !
Click to expand...
Click to collapse
I'm running this: http://forum.xda-developers.com/showthread.php?t=840040 (Sense 3.5)
very stable, all working fine
Maybe the USB-Port on the phone is dirty or a metalpiece in it or try another cable

[Q] Nexus 7 suddenly bricked ?

Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.

Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.

I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app

There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.

The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!

Do u guys have the most up to date version of whatever particular recovery that you're on?

Yep. I've flashed the stock recovery multiple times to no avail. :/

nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?

wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/

nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?

wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.

nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.

wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!