First let me talk about how I got into this mess. I had used the thunderbolt as my phone previously and had rooted it, installing custom roms often. After getting a new phone, I decided to unroot my thunderbolt and give it to a family member. At first, everything was working fine; I had no problems unrooting the phone. However, a month or so later it started having problems.
Upon booting, the phone goes straight to hboot where it displays a security warning. But this only happens occasionally. Sometimes it will actually boot but take about 20+ minutes to start up where it come to the homescreen with a solid black background, soon to freeze and turn off.
I have tried fixing the phone based off methods others used to fix similar issues, but to no avail. For example, I have tried flashing the 2.11.605.19 firmware through hboot only to have the same problems occur. Perhaps I did not use the right version. Do you guys have any idea on how I can fix this? Could flashing an ruu (if there is one) for the latest ics build solve this?
When I try to unlock the bootloader through htcdev, everything works fine up until the confirmation screen on my phone asking if I want to unlock the bootloader or not. For some reason, the power button won't work to press yes. It does work normally for saying no and everything else though. I have tried using the adb to force it to use the power button, but in its "unlock the bootloader" state it isnt connected.
some relevant info for the phone:
hboot version - 1.05.0000
radio - 1.49.00.0406w_1 - should be the radio from 2.11.605.19
Related
It is ok yesterday.
And I installed about 10 apps today and found that it will reboot if I lock the phone (the screen goes dark).
I don't remember the name of those apps.
So, how can I find out the problem of the certain app?
Must I uninstall all the apps to find out the problem?
THX!
If u go to the market and download a app called (instant uninstaller) it lets u choose to show the apps by date installed
Sent from my ADR6400L using XDA Premium App
thx！ let me try it.
So did this fix your issue? I am having the exact same problem.
I'm rooted (using ADB method), running Das BAMF 2.1 with Imoseyon's 2.54test4 kernel .
I can reproduce the a reboot everytime by doing this:
1. With the phone unplugged from the charger, press the lock button so the screen goes off. Once the screen goes off, in about 10 seconds it will reboot everytime.
2. Or, if I leave it set and the screen goes off by itself, it will reboot in about 10 seconds (after the screen goes off) everytime.
If I leave it on the charger, or never let the screen go off, it has never rebooted on me. I got this phone 2 days ago and have been battling it ever since.
UPDATE:
I have eliminated the following as a potential issue.
1. I wiped everything and flashed a new ROM, Kernal, and Radio, and still the exact same results.
2. I tried a new battery, and still the same results.
3. Tried two other kernals with each of the two ROMS, and still the same results.
Out of ideas at the moment.
Thinking of trying to flash back to stock so I can see if it still does it then.... Lost.
Solved my problem for now. Here is what I did.
1. Flashed back to these radios
CDMA: 1.13.605.7
LTE: 1.12.605.6
2. Flashed back to Froyo based ROM, Das BAMF 1.8.
Of course, I wiped everything before doing so. I've been up for about an hour now with my phone resting comfortably with no reboots at all.
Will try again in a few days to flash back to a gingerbread based rom, as I would really like to have Netflix.
If anyone has a gingerbread ROM and radio combo that they have working well together please let me know. You might also shout out which kernal you are using too.
UPDATE:
So I have obviously done some more troubleshooting on this, and I may have something to make sense of.
Since I flashed the GB MR2 radio and ThunderstickGB rom using the kernal provided with it. After bootup, I again had the reboot issues everytime the screen timed out or was locked. Just like before, It would reboot everytime unless the screen was kept on or plugged in to a charger.
I flashed back to the original Froyo radio just to see if that would make a change. Of course, I had no signal, but it would at least tell me if it were the newer MR2 or MR2.5 radios giving me fits. Even with the original radio, it still gave me the same reboots on screen timeout or locked.
So, I started over and this is what finally worked:
Flashed MR2 radio and ThunderstickGB rom again. This time, I flashed the stock GB kernal, instead of using a modified one. Bingo.... no reboots at all.
My feeling is that for some reason, some of the Kernals are undervolting the unit to a point that it shuts off or reboots. I am completely technically illiterate when it comes to the inner workings of Kernals and such, but the one common demoninator between my working Froyo and GB roms was that there was no Governor or Speed Tweak controlling the processor other than what comes in stock form.
Oh and by the way, thanks for eveyone's help with this.... I couldn't have done it without you.
Hello:
I unlocked the bootloader on my HTC Jetstream following the instructions on HTC Dev. After the unlock was completed my device keeps crashing upon loading the android OS. I can play around with it for about 10 seconds then it restarts. The only time it does not crash is when its connected to USB cable to my laptop. Can anyone shed any light on this issue?
Many thanks!
Take out the sim card and use WiFi only.
Boot after Root
I had a similar experience. I ended up restoring to factory (through the vol dn and Power method)
Then went back through the steps (didn't need to unlock again, just needed to follow step 2.)
same here
I had to factory reset and re lock to fix mine. I reinstalled the updated stock and runs perfect no, no rebooting during podcast and netflix. Run netflix 4 hours a day no issues now.
Hello I don’t know if anyone might be able to help but if theres any senior members that reads this and can shed any light on my problem, I’d be very grateful. First a little info on my phone and root:
In the bootloader it says ***TAMPERED*** ***UNLOCKED*** JEWEL PVT SHIP S-ON RL, HBOOT- 1.12.0000, RADIO-1.02.12.0427, Open-DSP-v25.o1.32.0405, eMMC boot. The rom that was loaded on the phone was an HTC build called Viper Rom. When the HTC 'quietly brilliant' screen comes up, underneath in red text it says "This build is for developement purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action." There were no issues with the bluetooth for months. My Bluetooth started disconnecting roughly 3 or 4 weeks ago and I have tried almost everything I can think of to try and fix it. First checking the three Bluetooth headset devices I use on other devices and they show up no problem. The perplexing thing that I recently found is when connectin via USB and opening all the files on the phone, there is no 'root' file that I can find anywhere. What I have tried:
1. Soft resets
2. safe mode restarts
3. factory resets
4. Bluetooth fix/ repair app
5. Change wifi frequency band from 'auto' to '2.4'
Now all of the 5 things above that I have tried worked one time and all stopped working within about 2 hours. Some almost right away the bt was disconnecting- even though it would re-connect, soon that stopped. From that point forward I have done the following:
1. Downloaded and flashed the 'Team Venom's version of Viper Rom 2.0.0.
The rom worked fine. but no BT. Another member on XDA suggested flashing the latest Mean Rom based on the HTC update 2.13.651.1. Did so, no BT. Then I flashed the latest Viper Rom 2.0.2 also based on the update and no BT. My next step was flashing a rooted version of that update that Max (Mikroms) posted on here. I did a factory rest, wipe cashe, wipe Dalvik cashe- six times before doing so. I Thought bricked my phone, it was bootlooping. I held down the power button for two full minutes then let go and then held down the power and vol down buttons and luckily the bootloader came up. I again did a factory reset, cashe and Dalvik wipe and reflashed the Viper Rom 2.0.2 again. which is the best rom I have ever used. This time some of the viper Tweak aren't working of available but everything else works fine except the BT.
I found out a couple of days ago there are a couple other people having a similar problem. I called HTC and they are aware theres a BT problem and are working on a fix which could take weeks. I dont know how I would get this fix since my phone is S-on. Another senior member has told me I can get S-off on the phone since I have 1.12 Hboot. I will be reading up on how to properly do that but was also told that that wouldn't have anything to do with the BT. I see it as being able to get updates, fixes and other stuff I have read about 'S-off'
After reading online, I found something about fixing bluetooth with logcat but didn't quite understand it. I do have an app on my phone now called aLogcat but do not know how to use it. I also went through the Play store and came across an app called 'rSAP- Bluetooth SIM Access Profile'. I then read the reviews and it sounded like the fix. Instead of spendingt the $12.49, I downloaded the trial version. An error came up "System file library not found. Is the an HTC/Samsung phone?" with no means to reply. The first clue about the problem is that the BT system files are not there, empty or blocked somehow. The only other things I can think of are:
Finding a stock rom, downloading/ flashing latest stock RUU.
Finding and copying the bluetooth system files from a friends evo 4G LTE phone that is a couple months newer.
I will be contacting my BT headset manufacturer and see if I can find out what should be on the phone for files since HTC wont or dosen't know what they are. Is there anyone out there in the developement world that may know how to access and copy the BT software on the phone or have any answers or suggestions moving forward???
Thanks in advance for any info,
TJ
in the same situation!
Ok anybody have any ideas? My Bluetooth stopped working as well on the last couple of builds of cm10. I tried restarting normally, also by holding the power button for ten seconds, clearing cache, clearing dalvik cache, I've restored a nandroid, and even got desperate and completely changed kernels and ROM OVER to mean ROM. OH and tried fixing permissions. It seems like the original post said, the files aren't just plain there! I cannot find anything on the web so far that allows you to flash a specific "Bluetooth installer". Please help if you got any ideas! Thanks!
Have you tried running the ruu and starting over?
Sent from my EVO using Tapatalk 2
neopolotin75 said:
Have you tried running the ruu and starting over?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
In order to do so I nees to lock the bootloader. I cannot get the bootloader locked! Idownloaded the sdk tools theyre installed. When connecting my phonew in bootloader mode through the usb it does not show up on my pc. I rebooted the phone then connected, selected disk drive, then booted into bootloader. Of course during the switch my pc chimed a disconnect sound then a connect sound.so it dropped my connection through disk drive thus blockng me from accessing my phone through the bootloader on the pc. I have spent 4 hours at this this evening so I can return this piece of crap back to spint and I cant even relocked it...Whats even worse is when going to my c drive on my pc there is no android sdk file at the top....Any suggestions?
bump
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
Hello. I decided to start a new thread. I have a Moonshine s-off phone. Recently I reset the phone put stock recovery on it and ran the newest RUU. It worked I got the new software[emoji3] . Then I unlocked the phone using the HTCDev method and my old unlock key, everything worked, when I went into BOOTLOADER phone said TAMPERED UNLOCKED S-OFF.
The only thing missing is my camera. Sometimes it turns on, but very rarely ( maybe 1/200 tries ). It tells me Unable To Start The Camera.
I think it's a software glitch, as with previous version of Android I had no issues. Also with the new OS the flash is BUSY sometimes. When I want to use a flashlight phone tells me PHONE SCREEN WILL BE USED FOR ILLUMINATION SINCE THE FLASH IS IN USE BY OTHER APP. There is no other app running...
I tried flashing TWRP but fastboot just hangs, I left it on for 3 hours and it never finished. I tried using the SD IMG method. It goes thru, tells me to reboot. When I do I'm on the same stock recovery...
I have backups of my phone. But they are all done with TWRP and I can't install it. I tried CWM as well, same result, timeout.
I might try running a lower version RUU and see if that fixes all...
[emoji27] [emoji23] [emoji24]
I have found a temp solution. If I disable my Phone Data and Location for a few minutes, then enable just the Phone Data camera will start. I don't know the time you need to wait... 2-5 minutes. I tried just putting the phone in Airplane mode but that did not make my camera. App start...
My Flash started working again. I have updated all my Apps, maybe that helped...