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
Related
i been reformatting and trying to everything i can to get the hd2 to work android but when i try to run clrcad or haret i get this error
The file 'CLRCAD' cannot be opened.Either it is not signed with a trusted certificate,or on of its compenents cannon be found.If the problem persists,try reinstalling or restoring this file
The file 'haret' cannot be opened.Either it is not signed with a trusted certificate,or on of its compenents cannon be found.If the problem persists,try reinstalling or restoring this file
can someone pleaseee help
no idea what problem you have i only know that CLRCAD doesnt show any activity. if you see notthing .. thats how it should work
The signing messages i've never seen
I had the same thing.
My android 'crashed' and my telephone did a soft-reset.
After that I could not open any program again, always said: Either it is not signed with a trusted certificate etc.
Did a hard reset, and again on android. But a bit annoying
is there even a way to fix it? cause it was working at first then now it doesnt work at all and i reformatted my sd card so many times and trying to redo everything all over again and still no luck
i have the mattc 1.5 desire build in my phone for over 2 weeks and its
my fav one but just yesterday it i couldnt find my charger and phone died
when i charged it and try to go back to android it wouldnt let me in
same dumb message , then i it stopped with the message but now it gets
stuck in were it booting android ughh its annoying i only want Desire build ! mattc 1.5
and ive try downloading other links but they dont work anyone have links that work ??
To answer OP's question, the easiest way you can do to fix it is downloading another Android build and run it to see if it works. It might be caused by corrupted downloaded files.
Btw, have you gone through all essential setup steps?
yeah im pretty sure i have...i also tried downloading other ones too same message. i HARD SPL the phone...then i unzip all the files to the root of my sd card...and if that didnt work then i also tried putting it in an android folder...still didnt work..and reformatting the sd card also.
Same issue as above, I ran android for the first time today. I have gone back to it couple times during the day with no issues.
About an hour ago I tried to run it again and this time I got the error message.
I have tried the following
- Restarting the phone
- Copying different android builds onto the card and running them
- Formating the sd card and running different android builds
My hd2 is running a
- stock rom 1.66.707.1
- Radio 2.12.50.02_2
stock roms probably dont allow the running of unsigned files to protect the system files, either find the cab file to disable this or you need to change to a custom rom
a lot of people like the energy rom but i dont know how to flash the rom..
YES!!!! THANK YOU... it worked i flashed my rom to the ENERGY ROM and then i got it to android with macfroyo build
Viktorca said:
Same issue as above, I ran android for the first time today. I have gone back to it couple times during the day with no issues.
About an hour ago I tried to run it again and this time I got the error message.
I have tried the following
- Restarting the phone
- Copying different android builds onto the card and running them
- Formating the sd card and running different android builds
My hd2 is running a
- stock rom 1.66.707.1
- Radio 2.12.50.02_2
Click to expand...
Click to collapse
I have noticed that none of the applications on the sd card were working anymore. It was the same message as when trying to run android.
Hard reset and now everything (including android) is working.
If it happens again, I think it will be time to try a custom rom because using android is far too fun to give up.
well i didnt hardset mine because its unlocked it is tmobile but i got it unlocked for AT&T so i was to scared to hardset it and it might have relocked...idk if that is possible but didnt want to take the chances but i flashed it with the energy rom, and then did the android. but at first my android wasnt working. it will boot and then when i turn it off and back on it didnt work and that was pissing me off..but now i got it working. its pretty much easy doing this..its just time consuming if you dont know what ya doing cause it took me a while
It won't relock!
Sent from my HTC Desire using XDA App
oh...thanks..well i got it working now =] on android and its so much better then WM6.5
Same problem
Hi, I have a similar problem. the thing is that I try t run clrcad but nothing. then I flash the phone again and it works during 3 more times that I have to run again.
Really i´ts anoing.
I would like to if somebody knows why this happens.
Thank you
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
may i know why you flashed the latest stock rom using your sd card. would it not be easier to flash through your pc using a usb cable?
you might want to check the meaning of "bricking the phone"...........
then remove it from the title of the thread........
As Rurph mentioned, flash it via your pc, still following the instructions from theHTC site
I now tried flashing through PC, same freezing occurs.
To reiterate:
I have an original HTC HD2 bought from the official HTC shop in Czech republic.
I downloaded the latest official ROM for HTC HD2 from the official htc.com/cz website using my original serial number.
The download finished successfully every time (I tried it 5 times from all the different servers), and the SHA-1 hash of the files was identical every time.
I now flashed it using the normal PC method - everything appeared successful.
I also tried extracting the nbh file from the downloaded file - both by running the .exe file, and by extracting it using winrar - both methods gave me the same nbh file with the same SHA-1 hash. Then I moved the leoimg.nbh to the root of SD card and flashed using the SD-Card method. Everything appeared successful.
Both of the above methods give me a system that freezes completely at random. For example when starting the phone, it can just freeze (left it for 8 hours over night, it remained frozed), when moving from 1 tab to another (freezes in the middle of the animation), when opening the start menu, when going into settings, when making phone call, when opening SMS, and most importantly when NOT DOING ANYTHING AT ALL.
What can I do?
Try to flash an older Version.
I don't know if its possible, but maybe that solves your problem.
Did you have SPL 3.03? If no... Install HSPL and use a custom ROM like the one from NRGZ28 (EnergyROM)
If you an't flash the older version via RUU (Rom Update Utility) try to flash it from SD card. You can also perform a "task 29" with MTTY (before you flash)
But be careful, you can brick your phone...
I have always only used official ROMs from HTC, so I never needed HSPL so I never installed it. I also always prefer the official ROMs so I would rather not use a cooked one.
I think flashing an older version would solve the problem, however I would rather like to find out what the cause is...
So far, I managed to get my phone to a useable state by running Android from the SD card - it works flawlessly for all my purposes. The only problem was to start Android through Windows before windows manages to freeze...
Given that android does not freeze, I believe that the freezing problem must be a windows mobile issue.
Any suggestions for tracking down this freezing problem? Could it be a hardware issue?
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
oh and you didn't leave the old application data folder on your sd card did you? or try to restore registry settings?
samsamuel said:
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
Click to expand...
Click to collapse
I always hard reset before and after a flash. No change - freezing still occurs.
Even when I did multiple hard resets, the freezing persisted.
The SD card is freshly formatted, checked for no filesystem errors.
I did not restore any settings or anything else - the problem occurs on a completely fresh clean flash.
Additionally, the problem occurs even with no SIM card or SD card inserted into the phone.
Overheating?
I concur with rr5678, seems more like overheating than ROM problems, esp. that I've had the same ROM for a week with no problems whatsoever
hence kind request to OP: check overheating threads and please change the thread subject to a more accurate one so it does not spread misinformation and panic
as for the overheating - 1st thing to do is installing BattClock and monitoring correlation between freezes and battery temperature
rr5678 said:
Overheating?
Click to expand...
Click to collapse
The phone is definitely not overheating. It is very cold to touch and it runs Android without a problem.
OK I did some more testing - going back to any previous ROM fixes the freezing. Then installing the newest ROM reintroduces the freezing.
Given that it is definitely not a hardware issue (works on previous ROM, works on Android, no overheating), it looks like a Windows mobile issue.
I am surprised that nobody else is experiencing this. How come I am the only one? What is so special about my phone?
And the new firmware can "brick" the phone - a less skilled user would not be able to do anything with a frozen phone...
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
b2206015 said:
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
Click to expand...
Click to collapse
Try another sim card if you can. I know it sounds crazy but...
wardh said:
Try another sim card if you can. I know it sounds crazy but...
Click to expand...
Click to collapse
Thanks for the advice - but given that the phone freezes even with no SIM card inserted, I do not think that it is the case...
I have however tested inserting a different SIM card anyway, and the freezing occured again...
I too faced constant freezing problems with the official ROM but then I used HSPL and flashed a different radio (2.12 in my case) and ever since never faced any freezing problems..worth a try I guess...
epic fail
not being picky, but "bricking" is, as far I know, by definition an irreversible problem? Hanging and freezing and re-booting are not bricking.
That said, sorry to hear about your troubles.
Sounds like going back to your old ROM is the only solution right now.
b2206015 said:
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
Click to expand...
Click to collapse
Psaldorn said:
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Click to expand...
Click to collapse
Well, to me it seems your phone just doesn't like custom ROMs.
Here is an attempt to provide a definitive answer to what to do if your phone has the Bluetooth/Wifi hardware failure.
Note that some of the links don't seem to work with the xda-developer app or the Atrix built in browser. Please blame motorola, not me
Symptoms:
1) If your phone was set to try to use Wifi by default on boot:
Your phone boots into the OS but shortly afterwards freezes and reboots - and again and again.
2) If your phone boots with Wifi turned off:
Your phone boots into the OS and a few seconds after you enable the Wifi in settings or via a widget it shows "Error" and sometimes the phone reboots shortly afterwards. Bluetooth simply fails to work.
If you have warranty return it for a repair. If not the best you can get is to disable the Wifi and Bluetooth so the phone doesn't reboot and can be used with mobile data. Instructions for both are below:
Be sure it is the Bluetooth / Wifi hardware failure:
1) Are you running a custom ROM? - if yes go to 1.1, if no goto 2.
1.1) Reboot into recovery and make a backup.
1.2) Remove your SD card.
1.3) Reflash using RSD to stock - remember to get the right one for the right country!
Get RSD and drivers here:
http://forum.xda-developers.com/showthread.php?t=1136261
Search for your stock firmware using google
Use RSD to install the stock firmware file which will replace the bootloader, recovery and radio - takes about 20 minutes.
Goto 2.
2) Reboot into Stock Android Recovery and reset to factory defaults
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620
2.1) Reboot to Android and try enabling wifi from settings - if it reports "Error" after a few seconds and your phone may reboot shortly afterwards it is the hardware fault. Proceed to 3.
3) Check your remaining warranty here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/82507/p/30,6720,7898
Bottom left - enter your IMEI.
Warranty left goto 3.1 else goto 4.
3.1) Return to Motorola for repair - be sure you flashed back to stock first using instructions in 1.3
4) Unpalatable options are all that is left. Either pay or do without Wi-Fi and Bluetooth. Have money and the desire to fix your Atrix ($110 in the USA)? Goto 4.1 else 5
4.1) Consider paying Motorola to repair the phone anyway. Schedule a repair here https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/82507/p/30,6720,7898
5) This is a complex process. Google is your friend. Unlock your phone using the instructions below. Note you have no warranty to lose (see 3)!
http://forum.xda-developers.com/showthread.php?t=1136261
5.1) Install romracers CWM custom recovery using moto-fastboot (or Android fastboot):
http://forum.xda-developers.com/showthread.php?t=1204500
5.2) Did you take a backup earlier? If yes go to 5.3. If no goto 6.
5.3) Reboot into CWM recovery and restore your backup. Note if you are stuck in a bootloop this will be ok in a bit. Goto 7.
6) Install your favourite ROM using CWM recovery from a SDCARD or by moto-fastboot. Goto 7.
7) Reboot into CWM recovery
7.1) Plug your phone into your PC (you might have to wait for the driver to enumerate the phone first)
7.2) Find or install adb on your computer (hint - it comes with the Android SDK and platform tools from earlier):
adb shell
mount /system
cd /system/lib/modules
mv dhd.ko dhd.ko2
reboot
8) When you install a new ROM or kernel goto 7. Every time.
This little setup moves the driver linux needs to try to talk to the wifi/bluetooth chip which has failed so it can't find it. If it can't find it then it doesn't try to talk to the dead Broadcom Bluetooth Wifi chip that prevents the reboot cycle happening.
The fix was pioneered by:
mvniekerk
http://forum.xda-developers.com/member.php?u=2353874
So go thank him!
In the hopes this helps,
Matthew
Good job. Well said.
Considering how many posts I have seen after posting this solution perhaps it could be sticky?
I promise to maintain it.
Matthew
Sent from my MB860 using xda app-developers app
Hmmm
I think I have done that correctly and flashed the 2.8 Neutrino GT. There was no reboot up to now. But I want to ask if there is a fix for WIFI 'ERROR' and BLUETOOTH error without 'ERROR' message?
Guys please. I can try anything I don't want to lose my phone Warranty is over. How can I find the Broadcom BCM4329 wireless and bluetooth chipset for atrix? So I can find a technician to change it with mine.
If you have the failure there isn't much to be done.
Ifixit has a teardown but the chip is a very small ball grid type thing which will be very hard to fix.
What are your symptoms precisely?
Sent from my MB860 using xda app-developers app
mattaw2001 said:
If you have the failure there isn't much to be done.
Ifixit has a teardown but the chip is a very small ball grid type thing which will be very hard to fix.
What are your symptoms precisely?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
When I click on 'Turn on Wifi' button, It says 'Turning on Wifi' for 10 seconds and then 'Error' message comes up under the Wifi button and when I click on 'turn on bluetooth' it says 'turning on' but does not turn on. Same as wifi but without the 'error' message.
How can I fix this? I can't use wifi and bluetooth!
Nothing to be done. There is some discussion as to why but a chip in your phone made by broadcom which handles both wifi and Bluetooth has failed.
Short of replacing it requiring sophisticated soldering tools you are stuck. See the $110 Motorola warranty repair.
Sorry,
Matthew
Sent from my MB860 using xda app-developers app
Im stuck.
I have applied the fix to NottachTrix4G rom. I still have the random reboots. I really need help.
Do you get the wifi error message or not?
Secondly does this happen with the normal, stock Motorola rom?
Matthew
Sent from my MB860 using xda app-developers app
When i check wifi does show error. I have not tried the stock moto rom yet.
The best thing to do is return to stock and do a factory reset
Carry out a full backup first (nandroid or using CWM recovery).
The best thing to do is return the atrix to stock and then do a factory rest.
If the problem persists then it is a hardware problem and you can now return it under warranty without them knowing (see the thread for instructions).
Otherwise you seem rather stuck. Perhaps buy an atrix with a smashed screen and transfer the motherboard?
Matthew
Noattachtrix rom was good, but not good enough.
little_man_3666 said:
I have applied the fix to NottachTrix4G rom. I still have the random reboots. I really need help.
Click to expand...
Click to collapse
I ended up using RomGb instead and that fix the bootloop after using NottachTrix4G Rom.
This happened to me Saturday November 17, 2012. Rebooting did not help. Did my searches and found this thread - and was bummed to read that it is due to a hardware issue. Fortunately, I persisted. With the WiFi widget endlessly spinning, I tried the Bluetooth, which would just fail and go to an off state. I elected to do a force close on any running applications one by one, testing Bluetooth after each. I found that BlueTooth and WiFi functionality would come back after force closing some apps. I stupidly left WiFi on and rebooted the phone - this put me in an endless reboot cycle. In the midst of one I managed to enable car dock mode which I have configured to disable WiFi and this got me out of the loop. I found my issue, which has the same symptoms as the above, was caused by a recent update to WeatherBug Elite. I uninstalled the program, and am back to normal operation. Hope this helps others.
Update - it appears my problems continue. Although I can now access BT & WiFi, the problem will re-occur. Force closing Weather version 2.2.2 usually will clear the issue, but I have had a good working WiFi sessions halt to Error. Still gotta think it's software rather than hardware.
Thanks I thought it was the ROM until I found this thread
Well, I was wrong. The issue is hardware not software. In my case pressing the volume down button would change the behavior sometimes, like get bluetooth to work, press volume down it stops or vice versa. Time for a replacement.
I mount the system successfully but when I type cd /system/lib/modules I get it cant find the directory, Please help. I need to do this to stop reboot!!
Definitely Software
I have atrix 4g. Running MROM 2013 2 13. I have the error on WIFI and NO Bluetooth. No reboot, but I rarely use the wifi enough to leave it on(conserve the batt). This is a software issue as far as I can tell as well.. I can fix it by killing the mrom service in "manage applications". If I get a chance I will look further but this seems like enough of a fix to not care.. MROM is pretty great besides this issue.(which appears to happen on multiple roms. My guess would be that it started with CM, but only because that is what the roms are based off of that get the problem.
bubba1993 said:
I mount the system successfully but when I type cd /system/lib/modules I get it cant find the directory, Please help. I need to do this to stop reboot!!
Click to expand...
Click to collapse
Having the same issue. Wifi died after the phone fell off my hands. I had the CM10 ROM by ephinter and everything worked great except the wifi (no reboots). Then I had the AMAZING idea of installing a new ROM and the reboot loop started. EIther with any stock or custom ROM it continues to happen. Tried everything without success.
Have anyone tried disabling wifi in the settings.sqlite and see what happens?
jaunis I found out why mine was doing the boot loop and it is funny but very weird. I wiped the phone and put my cm7 back on there and forgot to activate my gmail account or any account for that case. Now I have been running it with no problems for 40 hours. But of course still no wifi. I am fine with that. but at least I am not dealing with the reboots.
I have an unlocked AT&T Atrix 4G with a custom ROM (Cyan 9.x & ICS 4.x). I started having WiFi issues where the device would reboot anytime I tried to enable the WiFi. This all started at least 6mo after installing the custom rom so I dont think its software related. To try and fix the issue I tried doing a data wipe factory reset, at this point I couldn't get past the welcome screen because WiFi didn't work and I dont have a SIM in the phone (my kid has been using it for games). So from here I decided to try and flash the phone back to stock using RSD Lite;
Be sure it is the Bluetooth / Wifi hardware failure:
1) Are you running a custom ROM? - if yes go to 1.1, if no goto 2.
1.1) Reboot into recovery and make a backup.
1.2) Remove your SD card.
1.3) Reflash using RSD to stock - remember to get the right one for the right country!
Get RSD and drivers here:
http://forum.xda-developers.com/showthread.php?t=1136261
Search for your stock firmware using google
Use RSD to install the stock firmware file which will replace the bootloader, recovery and radio - takes about 20 minutes.
Goto 2.
2) Reboot into Stock Android Recovery and reset to factory defaults
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620
Click to expand...
Click to collapse
I downloaded the AT&T 2.3.4 / 4.5.91 Service SBF which looks like this in RSDLite: 1ff-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-att-us-gas_na_olpsgbattspe_p011.sbf
I started the flash and left my phone for 15m or so to do its thing. When I came back my phone was boot looping (shown in a video here: http://youtu.be/V9wtBNEWRPQ ).
I can't do a factory reset from Stock Android Recovery (step 2 above), I can't get the menu for it. Now what do I do? Did I grab the wrong SBF file? Currently the only place I can grab SBF files at is here: http://www.das8nt.com/sbffiles.html
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
Dear Experts,
Months ago my 2y old XZU on 4.4.4 (6833, towel rooted, locked, CWM recovery) started to fail on init of LCD, when coming out of standby. LCD init not only fails when device gets waked up by "power" button, but also when power is applied (Dock connector or USB). So I guess in fact it is a firmware issue (not a defective power button or the like).
It gets worse and worse; when device is warm it sometimes needs 30 or more off/on cycles.
When LCD init fails, the screen either stays black (only backlight) or colored lines show up shortly and fade away. But in fact the device is running - only LCD is not working.
But when init is successful, the XZU can run nicely for hours (as navi).
I hope that a android FW update might help!?
Unfortunately OTA doesn't seem to work on routed devices even with still locked boot loader.
Is there a way to update directly to 5.1.1 available now? Is it possible to update in two steps?
I would not mind to loose root, but loosing the possibility to write to external SDCARD!
Any help/ideas? THANKS A LOT!
Thomas
Sounds like SOD, or Sleep Of Death. The Ultra had some issues with it back on Jelly Bean, but I hardly read about it being an issue on KitKat, but yeah, it's probably a software issue, so an update to 5.1.1 might just cure it. You have a couple of options here:
1. Update the official way by installing Sony's PC Companion app on your computer and updating it that way
2. Update it in a little less official way by updating it manually yourself with Flashtool on your computer
3. Update by flashing a customized version through a recovery system on your device (like CWM or TWRP)
I would personally update it through PC Companion if I were you, since I guess you're not that technical when it comes to flashing and troubleshooting things. PC Companion should notify you about the update as soon as you plug your Ultra to your computer. If it notifies you about the 5.0.2 update, then I guess you'll have to update to 5.0.2 first, and then you'll be able to update to 5.1.
Flashtool allows you to manually download a FTF, or the ROM file from XDA and then flash it yourself. It's a lot quicker than PC Companion, but also a lot more complicated for people who haven't used it before.
Flashing through a recovery is mainly for people who already are used to flashing and stuff like that, and know what they're (mostly) doing.
Any other questions?
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
zamzon said:
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
Click to expand...
Click to collapse
The OTA will only tell you to connect to the computer to update. And regarding SD-card, that won't be an issue. Android will ask you to grant permission to the SD-card in some cases, but I haven't had any issues with it. Most if not all file explorers works just fine, and you won't experience any issues with the SD-card.
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
zamzon said:
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
Click to expand...
Click to collapse
But that does sound like a hardware issue. The final thing you can do, before you'll have to send it in for repairs, or get a new device, is to do a full factory resetting and see if that finally helps. You just updated now, but there's still a lot of crap left over from the previous version, that might screw things up.
So my advice would be to do a wipe, check if it help, and if not either send it in for repairs or get a new device. It's not a software issue if the issue travels over several OS versions with you. It may be a faulty display connector.