Hello
Im a big HTC fan, my main phone was the A9 until I moved to the U.S, so I decided to get the M9+ cause it has the double camera feature.
I got it from internet, model m9pw htc_hiau_ml_tuhl XC
CID-1111111
MID-0pk711100
os 2.30.401.1
update from Oct 18 2016
and it charged normally the first day and everything was so smooth, and then I got notifications about UPDATING to android 6 Marshmallow
after updating it, It stop charging, PC doesnt recognize it, no download mode, nor bootloader either (this model doesnt have fastboot option)
I tried differents usb cables, chargers, wall plugs, HTC diagnosys tool, HTC tech support FAQS nothing
but it charges when I turn it off, the red light goes on but charging it for hours it only gives me like 2% 3% if im lucky
and bootloader > Stock recovery says no SD detected, so I cant flash a zip RUU unless i find the way.
can it be hardware or is it an software issue?
theres no way to root it, to me to replace the drivers files (if it were drivers issues), also i read about HTC m9 issues about updating it and they recomend to unistall google photos... how to remove it without root? no usb port either!!
onle more thing, I tried HTC live chat...it doesnt work, also send them a email their web site doesnt work, it just no send it and no showing validation code either...
Related
hi all i bought defy about a year ago as a second phone from ebay with cm7 installed.last week i purchase another phone and give my 7 years old daughter. however i reset everything and phone turn old version blur mod then stuck on m logo i download rom and sort the problem.
real problem starts now i try to install cm 9 download all required files wiped the phone and install the rom however it didn't restart stuck on black screen and only white led when connected with usb also didn't connect or recognized by rds lite.I found tread battery wake up from i think was ''mggrager'' or something else finally rds recognized the phone and install another sbf but still stays same as black screen and white.i read so many threats on this side or others and each i installed custom roms without clearing cache
battery replaced with replacement battery also original
all drivers installed
it doesn't respond any buttons or usb connection
rds only with battery jump
please help what to do
I'm having the same problem as you are, i believe... I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport... I take my phone home, not really giving it much importance, and i noticed it would never charge and/or turn on, and that when I connect it to the pc, nothing happened other than the white led coming on.. RSD won't recognized it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
I don't know if i should make a thread of my own.. i think we have the same problem, and i REALLY need my phone back.. so i guess we could just help each other fixing it somehow....
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOLA_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
pasha543 said:
i already tried several times this method however no luck i am really not sure what to do any more i think only option try to find latest rom or first rom then try again if any luck will update and give the links
Click to expand...
Click to collapse
bump 4 help
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
easyxx said:
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
Click to expand...
Click to collapse
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
kophyo07 said:
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
Click to expand...
Click to collapse
If your phone displays Downloading... and fastboot keeps saying waiting for device then there is something wrong with the installed ADB driver. Check some of the posts in this forum like this one on how to fix this. http://forum.xda-developers.com/yotaphone-one/help/yotaphone-2-yd-206-china-flash-firmware-t3306797/post69311402#post69311402
Strange that you had an OTA (Over The Air update). You didn't do anything between the SIM/Google registration and OTA ?
Normally there are no OTAs allowed on yd206 phones bought from China/HK , where did you buy it ? Chinese retailers have their own firmware that they put on phones , for me , maybe you had bad firmware installed.
The warranty of your phone is voided if you flash yotaphones bought from China and HK .
When you use yotaflasher do you get error message or "waiting for device" ?
To flash the Yotaphone , it should be in developer mode , but you couldn't put it in this mode because it first did the OTA that started your bootloop. Android apps are updated like that ("installing x of 127") when it gets updated to lollipop. Normally the OTA should have worked OK. Did you allow enough time at the Yotaphone logo after the first reboot ? It stays on this logo for 5 minutes before starting. I made this mistake.
The OTA started just after you set up Google etc ?
If so, normal yotaflashing will never work, but at least you havent broken the warranty . The thing we need to know is what exactly happened when you tried to flash , what errors messages appeared ?
If you did not put the phone in developer mode, then you cannot easily flash the phone, so your best possibility is to return the phone. Normally you can contact the seller by chat or email . Some are very good in exchanging.
It IS possible to flash your phone using fastboot, but I would not personally attempt it and you would lose your warranty . You need rootkits, SDK toolkits, universal drivers and images. Google "bootloop without USB debugging".
When I flashed my yd206 , (after many attempts) I flashed my yd206 to yd201 Russian KitKat ROM first and then did an OTA to lollipop.
Hey,
So yesterday I decided to finally tinker with my phone. My main issue was that the Wifi kept disconnecting on it's own for no damn reason but no other device would do it. Found out it's a thing with the E4 and the option for disconnecting on a bad connection wasn't there.
At anyrate, I unlocked the bootloader and flashed TWRP. Then things started to go sour. While trying to root the phone, I ended up with no ROM. Tried a couple of different ones. Lineage OS, Resurrection Remix but none could get past the boot animation. Eventually I found the correct (I think) ROM for my phone. I'm in Canada and on Freedom Mobile so I went with the Retail Perry OS from here: https://mirrors.lolinet.com/firmware/moto/perry/official/RETAIL/
I tried installing with TWRP but it said invalid ZIP file so I found another way. Using instructions from https://forum.xda-developers.com/moto-e4/help/rsd-lite-device-connecting-t3671647 I used the rsdlite motorola xml to batch script file thing mentioned. Phone finally worked again! Went about installing the bits and bobs. Was working for a few hours and then I decided to update. I had used an older version of the firmware when the zip file was coming up as invalid in TWRP. The first two or three updates went fine. Downloaded, installed, restarted, fine. Then during one it just... stopped. I think it was restarting last I saw but I didn't even see the "Updating" animation page. The battery was over 60% minimum.
I've tried holding down all the buttons for 4 minutes, I've tried booting into recovery, into bootloader. Nothing. The screen stays black. Not even an animation for charging.
About a half an hour ago I tried plugging it into my computer. Initially there was a response by the PC. A popup came up and said something about Qualcomm <name> being successfully installed or updated. It went so quickly I didn't get a chance to read it. I went looking through My PC trying to find the device and see if I could access the files on it but there was nothing. So I unplugged it. Now I don't even get the Qualcomm thing. Device manager says that it was unable to be identified and I just get a notification saying USB is unrecognized. I've tried uninstalling and updating drivers in Device Manager to no avail. I'm out of ideas. Any thoughts from anyone?
Edit: While having the phone plugged into my PC if I try to access the bootloader mode by holding down the buttons for a longer period of time, my computer responds with noises. Mostly it's just the USB removed noise, but occasionally one sounds off if a new USB device is plugged in.
Resdrak said:
Hey,
So yesterday I decided to finally tinker with my phone. My main issue was that the Wifi kept disconnecting on it's own for no damn reason but no other device would do it. Found out it's a thing with the E4 and the option for disconnecting on a bad connection wasn't there.
At anyrate, I unlocked the bootloader and flashed TWRP. Then things started to go sour. While trying to root the phone, I ended up with no ROM. Tried a couple of different ones. Lineage OS, Resurrection Remix but none could get past the boot animation. Eventually I found the correct (I think) ROM for my phone. I'm in Canada and on Freedom Mobile so I went with the Retail Perry OS from here: https://mirrors.lolinet.com/firmware/moto/perry/official/RETAIL/
I tried installing with TWRP but it said invalid ZIP file so I found another way. Using instructions from https://forum.xda-developers.com/moto-e4/help/rsd-lite-device-connecting-t3671647 I used the rsdlite motorola xml to batch script file thing mentioned. Phone finally worked again! Went about installing the bits and bobs. Was working for a few hours and then I decided to update. I had used an older version of the firmware when the zip file was coming up as invalid in TWRP. The first two or three updates went fine. Downloaded, installed, restarted, fine. Then during one it just... stopped. I think it was restarting last I saw but I didn't even see the "Updating" animation page. The battery was over 60% minimum.
I've tried holding down all the buttons for 4 minutes, I've tried booting into recovery, into bootloader. Nothing. The screen stays black. Not even an animation for charging.
About a half an hour ago I tried plugging it into my computer. Initially there was a response by the PC. A popup came up and said something about Qualcomm <name> being successfully installed or updated. It went so quickly I didn't get a chance to read it. I went looking through My PC trying to find the device and see if I could access the files on it but there was nothing. So I unplugged it. Now I don't even get the Qualcomm thing. Device manager says that it was unable to be identified and I just get a notification saying USB is unrecognized. I've tried uninstalling and updating drivers in Device Manager to no avail. I'm out of ideas. Any thoughts from anyone?
Edit: While having the phone plugged into my PC if I try to access the bootloader mode by holding down the buttons for a longer period of time, my computer responds with noises. Mostly it's just the USB removed noise, but occasionally one sounds off if a new USB device is plugged in.
Click to expand...
Click to collapse
Sounds like you hard bricked it. I had the same thing happen with my E4 Plus. Not sure why this is happening with certain updates even without being rooted or trying to install ota's with stock recovery as you should do. I managed to get mine working again with this tutorial here but you need the right files for your specific device
https://www.google.com/amp/s/forum....-moto-g5-run-morning-post-image-t3776012/amp/
The correct img may be floating around these threads somewhere.
Stuck at Fastboot & Rescue Mode, tried multiple things; Always 100% Original Software
Hi reader,
First some background:
A month ago I changed my SIM Card in my 2.5 year old Huawei P9 Lite with original Android 7.0. I never flashed or rooted this phone. Developer options are on (not sure though). Since then, I saw a major battery drain. After charging fully, it drained fast to 51% and got stuck on 51%. The phone turned off. After trying to turn it on, the red LED flashes. Charging it for 2 days, the green led turns up. However, turning the phone one, the screen stays black and red light flashes. Charging for 5-10 minutes, the green light turns on but this loop of green and red lights continues.
What I want:
Get my contacts and notes back
What I tried:
- Volume down + power and connecting to pc -> Fastboot. Message:
* Please connect usb cable to your computer and open HiSuite -> done, but HiSuite does not recognize phone. Windows does, as Android Sooner Single ADB Interface. The cmd code: ''fastboot'' does not give the wanted result (not found). As windows does not recognize the correct phone, I tried to install a new Huawei USB driver. The problem is, that Windows says the Android Sooner driver is already the best driver available.
* Android reboot reason: AP_S_COLDBOOT NA. Volumekey_down_press_process_func
* Green android puppet
* PHONE Locked. FRP Lock. -> I tried to unlock via Universal Fastboot & ADB Tool. This program recognices device as ''FUH4C16518004949 fastboot'' and reboot button in the program phone works (but again the red light). I also tried to unlock bootloader but I cannot find the correct key via the Huawei website (thus could not try oem relock *Here Huawei Code*). I tried to flash EliteTWRP-3.2.1-0_2018-01-19.img, but that is not possible due to the lock.
What can I do next in order to get a backup of my contacts and notes?
Phone will go on charger again.
No one?
So you said you didn't do any root and/or unlocks? This seems like a battery/motherboard failure. To fix it, go to HUAWEI's official service center
The Restless Soul said:
So you said you didn't do any root and/or unlocks? This seems like a battery/motherboard failure. To fix it, go to HUAWEI's official service center
Click to expand...
Click to collapse
Thank you for your answer. That is correct, no root and no unlocks.
Huawei Service Centres are not nearby and warranty is over. That is the reason I wanted to try a few things.
Are there things I could still try?
richh008 said:
Thank you for your answer. That is correct, no root and no unlocks.
Huawei Service Centres are not nearby and warranty is over. That is the reason I wanted to try a few things.
Are there things I could still try?
Click to expand...
Click to collapse
Get the spare parts and fix it by yourself? The battery replacement is very hard and you can damage the display cords. So i recomment a third party service then.
Hi.
To start off, I'd like to say im no expert with phones, I had phones mostly to call, watch videos and listen to music, and this is my first attempt at doing all the stuff I will be describing now.
From the beginning:
I bought a seller refurbished LG G2, which worked fine when I received it, I had to do some updates which my phone found automatically, and it ended at OS version 4.4.2.
I wanted to finally have a decent but cheap phone, however it couldn't play some games I wanted to play and thought "Maybe if I update OS to something new, it will work, and it looks better"
Here my journey to update the phone to Android 11 started.
I was looking at many different videos and guide and everything, how to root, first time I rooted was by accident, only later a better video instructed me how to do it properly, then I installed the trww or whatever its called. then it didnt work properly after using that recovery to install android 11, so I had to flash it to some old version I found for my device (My version is LG D802 btw). For some reason it now had only 11gb of space, instead of 32gb. Anyway, I tried installing root and twrw thing again. After getting root and the recovery program I clicked reboot in its options and now my phone is having an issue.
First off, I left it to charge over 9 hours. If its NOT connected via usb it does nothing, power button, volume buttons do nothing.
I tried connecting it to my phone to flash it, but nope, after few seconds it says my phone disconnected from the usb and try again, even tho it is connected and I can see in device manager that it's seen by my PC. Now, I tried to enter the download mode manually, and it worked.
It says that it's rooted and B0 above it (this number was going down over different roots, twrw installs and flashes and such, no idea what it is.
I tried to flash it again since Im in download mod, however now the main issue appeared. It goes well for 40% of the flash using the LG flash tool 2014, I can see the progress in the download mode on the phone's screen, however once it reaches that certain point it just resets and the program treats it as disconnected.
Now when I have the phone connected via usb it just flashes red between 1 and 3 times, LG logo shows up for several seconds, then it turns off, and repeats the whole process.
During the flashing, software instructed me to remove the batter and try again, so I looked up how to remove it, did it, put everything back together, and its still the same.
Please tell me what to do, I've already spent over 10 hours trying to fix it and I just bought this phone...
hi... if your phone flashes LG logo - i'd recommend a full TOT flash of the original Lollipop image as a starting point...
just make sure you download a proper TOT file for your d802 device (32gb model)...
you'll end up with a working stock Lollipop rom which you can later root and flash a custom rom (i.e. Lineage 18)
Stock TOT file is usually about 2.6-2.7GB in size (at least for my 16gb model)
this youtube video shows how to do it and what is required for the process...
i think there is also an older thread here on XDA on how to TOT flash a G2 device (try to search it)