Related
Hi I'm new here, I have a nexus 7 2013 which wont go past the google screen, it just sits there doing nothing. I can still get into recovery mode and do a factory reset using wipe data/factory reset but it comes up with a bunch of errors such as:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
etc.
I have no idea what to do. I've only had the Nexus since October 2013. It has been running the stock Kitkat 4.4.2 with no root or any bootloader mods
I dont know if this has anything to do with it but last night my sister turned the Nexus on but just as it finished booting (it got to the lock screen) she turned it off straight away before things like the notification bar and background had loaded up. We only turned it on about an hour ago and that was when the Nexus got stuck on the Google logo screen. Also the Nexus was plugged into the stock charger that came with it while this was happening.
What do I do from here?
Is the device bricked?
Or is it as simply flashing a ROM?
Many Thanks
Saajan
saajan_b123 said:
Hi I'm new here, I have a nexus 7 2013 which wont go past the google screen, it just sits there doing nothing. I can still get into recovery mode and do a factory reset using wipe data/factory reset but it comes up with a bunch of errors such as:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
etc.
I have no idea what to do. I've only had the Nexus since October 2013. It has been running the stock Kitkat 4.4.2 with no root or any bootloader mods
I dont know if this has anything to do with it but last night my sister turned the Nexus on but just as it finished booting (it got to the lock screen) she turned it off straight away before things like the notification bar and background had loaded up. We only turned it on about an hour ago and that was when the Nexus got stuck on the Google logo screen. Also the Nexus was plugged into the stock charger that came with it while this was happening.
What do I do from here?
Is the device bricked?
Or is it as simply flashing a ROM?
Many Thanks
Saajan
Click to expand...
Click to collapse
I would suggest that you put it into fastboot mode (aka get to the bootloader), and fastboot flash the factory image. However, you do have to unlock the bootloader first.
Follow Post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051
charesa39 said:
I would suggest that you put it into fastboot mode (aka get to the bootloader), and fastboot flash the factory image. However, you do have to unlock the bootloader first.
Follow Post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051
Click to expand...
Click to collapse
Thank you, it worked great. I didnt know you could flash the image using fast boot
saajan_b123 said:
Thank you, it worked great. I didnt know you could flash the image using fast boot
Click to expand...
Click to collapse
Awesome. Glad it worked out for you. As far as I know, fastboot is the only way to flash the factory image. Well, I suppose toolkits can flash it as well, but I, personally, am not a huge fan of them. Plus, it's the same process in fastboot as well, just automated. They're convenient for someone that already knows what they're doing, but for "nooks," they can often do more harm than good.
Sent from my Nexus 5 using xda app-developers app
hello guys,
I have the same problem with my nexus 7 2013 (wifi), and i am trying real hard to fix it, but i cannot.
When i try to unlock the boodloader in ADB, the screen freezes, and it will not respond anymore to commands. I have to reset the tablet manually, and boot into recovery mysefl, where the bootloader state is locked..
Running stock android, no root, bootloader locked, no usb debugging!
I think the problem is that the usb debuging is off, and i cannot write on the tablet in adb trough a usb connection.
Can someone help me?
Thank you in advance!
:sasquatch: said:
hello guys,
I have the same problem with my nexus 7 2013 (wifi), and i am trying real hard to fix it, but i cannot.
When i try to unlock the boodloader in ADB, the screen freezes, and it will not respond anymore to commands. I have to reset the tablet manually, and boot into recovery mysefl, where the bootloader state is locked..
Running stock android, no root, bootloader locked, no usb debugging!
I think the problem is that the usb debuging is off, and i cannot write on the tablet in adb trough a usb connection.
Can someone help me?
Thank you in advance!
Click to expand...
Click to collapse
You should be unlocking the bootloader with fastboot, not adb. Once unlocked, flash the factory image with fastboot.
I tried with fastboot, and it works perfect until i select (yes) option from the tablet. After selecting (yea) the tablet freezes and the bootloader remains locked! I have to hard reset the tablet to acces recovery mode again...
Any ideeas?
In fastboot mode, when i try fastboot oem unlock and select yes in tablet. tablet freezes and the bootloader remains locked!
Can someone help me out
It can be an hardware issue, someone say to massage the back of the tablet ( on the X) maybe it work, should be a flat off position.
Btw look at this thread where hundreds of peoples have the same issue... Nexus 7 stuck on Google screen
Hi friends,
+ I just got my M9 today. While unlocking Bootloder,i reboot into Download Mode the first time and get this error msg : "Security checking failed NOT_FIND_SMART IO -- SD NOT MOUNTED "
+ But i can unlock the bootloader successfully. Then ,the phone wouldn't let me flash the TWRP recovery, i got this error msg all the time :
c:\adb>fastboot flash recovery twrp.img
target reported max download size of 800000000 bytes
error: cannot load 'twrp.img': No error
Then i search Google and only this forum has my question. http://forum.gsmhosting.com/vbb/f485/java-card-htc-1888938/index3.html
They are talking about using Java card to S-OFF the HTC ONE M9
I contact my reseller and they swear that this phone has been never used before. Pls help! Did my phone was modified with a Java Card
I have had the error pop up I. The download screen since I was at the att store in Saturday picking the thing up. And I know mine was fresh out if the box from ATT. And rooting the M9 was a pain the first 2 times around. Neither used the same steps but both times rooting was achieved and this thing is a beast. I'm gonna go back to stock one more time to get a fresh dump before letting the ninja do his majik and and take this thing s off
Sent from my HTC One M9 using XDA Free mobile app
mefurst said:
I have had the error pop up I. The download screen since I was at the att store in Saturday picking the thing up. And I know mine was fresh out if the box from ATT. And rooting the M9 was a pain the first 2 times around. Neither used the same steps but both times rooting was achieved and this thing is a beast. I'm gonna go back to stock one more time to get a fresh dump before letting the ninja do his majik and and take this thing s off
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
So is this normal sir?
Which version of twrp did you try?
Sent from my HTC One M9
sinosuke said:
So is this normal sir?
Click to expand...
Click to collapse
I am by no means a seasoned veteran here. but it seems that flags is being thrown do to the fact that the phone is in download mode with out the OP****.img file being present where download thinks it should be. it hasn't stopped me from rooting the phone, going back to stock, flashing the RUU and rooting again.
I may be completely off base, and hopefully one of the Vets here will let me know before i do some damage, but i think it is just a newish feature for HTC that doesn't have all the bugs worked out yet.
One thing to be sure of is that you are using the <b>BETA TWRP 2.8.6.4</b> i have heard some bad things happening using the wrong recovery version ***props to Cap for all his work***
I got this error when I tried to flash the RUU so I flashed it through an sd card butbtgats not possible for the recovery.
Download the latest TWRP not the official and try to flash it again
S-Off
mr.dj26 said:
I got this error when I tried to flash the RUU so I flashed it through an sd card butbtgats not possible for the recovery.
Download the latest TWRP not the official and try to flash it again
Click to expand...
Click to collapse
Today i finally went for it and went S-Off and hey... the error is gone.
sinosuke said:
Hi friends,
+ I just got my M9 today. While unlocking Bootloder,i reboot into Download Mode the first time and get this error msg : "Security checking failed NOT_FIND_SMART IO -- SD NOT MOUNTED "
+ But i can unlock the bootloader successfully. Then ,the phone wouldn't let me flash the TWRP recovery, i got this error msg all the time :
c:\adb>fastboot flash recovery twrp.img
target reported max download size of 800000000 bytes
error: cannot load 'twrp.img': No error
Then i search Google and only this forum has my question. http://forum.gsmhosting.com/vbb/f485/java-card-htc-1888938/index3.html
They are talking about using Java card to S-OFF the HTC ONE M9
I contact my reseller and they swear that this phone has been never used before. Pls help! Did my phone was modified with a Java Card
Click to expand...
Click to collapse
i guess youve got the solution for the other post but the the sake of helping others,
remove the extension from twrp.img _> twrp
and then flash , this is a common error for many people , ive never faced it though.
Mines totally stock OOB, going into recovery i get the same error as you do about IO
Hello everybody,
i hope the xdadevs can help me with my problem.
Since two Days i try to recover my Nexus 7 form a bootloop.
A week ago i flashed Kali Nethunter 2.0 via TWRP on my Device (Nexus 7 2003 Wifi) - Everything worked fine till yesterday.
My device run out of energy so i loaded it and startet it shortly after that.
Then i regognized the bootloop. I tried to restart the device but it had no effect.
After that i tried to boot into the Recovery Mode with TWRP to restore my working backup. But it got stucked on the loading screen of TWRP too.
Now i tried to recover some images and fix the problem with some manuals which seemed promising. - no success
After a while i did something incredible stupid and locked my bootloader again (i wanted to try to lock and unlock it since some tools couldnt flash the stock rom).
The situation right now:
I cant boot up normaly: Stuck while "Google" is displayed
I cant boot in Recovery Mode (TWRP): Stuck on the blue TWRP Logo
If i try to use the Skipsoft Toolkit or something else it fails - or do i miss something
Recover the Stock rom by using the "flash-all.bat" fails because of this (pastebin. c0m/ie0dBv1D). I used the stock rom of Android 4.4.4(razor-ktu84p) because every other stockrom says this (pastebin. c0m/Dz31k8qu).
I wonder why the stock rom needs to get the bootloader unlocked... ive red so much about it that it just works out of the box..... am i doing something wrong ?
If i try to unlock again, the selection screen on the tablet shows up. I choose yes and hit the Power button. At the console the output <bootloader> erasing userdata" shows up and "freezes?!"... nothing happens afterwards.
Thats about it and this is where i am stuck. I would really appreciate if someone could help me ! I would even reward or spend some money on help.
I try to fix it meanwhile and update this post if something new happens.
I had to alternate the links because im a new member, im sorry for that !
Thanks in advanced and sorry for the spelling
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
diehard2013 said:
did you try the nexus root toolkit ?
war your PC detecting (USB) the Nexus prior to this problem?
Click to expand...
Click to collapse
Yeah i tried it but it couldnt fix my problems. Returning to Stock Rom will always tell me that i need the bootloader unlocked... and i cant unlock it.
My PC and Linux Notebook where recognizing before it was bricked. Now it only gets detected in fastboot because it wont start anymore.
Hi guys.
This is my first thread as this is my last chance. I have my HTC for 4 weeks and everything was really well. It was on CM13 with TWRP 2.8.5.0 (95% sure).
Yesterday my phone turned off and after I turned it on again it stuck in bootloop (CM logo).
I tried to make a factory reset in TWRP but there's a problem with E: unable to mount /data and /cache.
I tried several things to repair it but i made things worse.
Now TWRP is starting as a recovery maybe every 6-8 time. Download mode is failing to boot.
So now I'm with bricked phone and I really need it for my work. Is there any chance to repair it? Or I need to prepare for expenses?
Thanks in advance for any help
Tgorak88.en said:
Hi guys.
This is my first thread as this is my last chance. I have my HTC for 4 weeks and everything was really well. It was on CM13 with TWRP 2.8.5.0 (95% sure).
Yesterday my phone turned off and after I turned it on again it stuck in bootloop (CM logo).
I tried to make a factory reset in TWRP but there's a problem with E: unable to mount /data and /cache.
I tried several things to repair it but i made things worse.
Now TWRP is starting as a recovery maybe every 6-8 time. Download mode is failing to boot.
So now I'm with bricked phone and I really need it for my work. Is there any chance to repair it? Or I need to prepare for expenses?
Thanks in advance for any help
Click to expand...
Click to collapse
If you can get into download mode, you can likely flash the RUU.exe from HTCdev. Turn your phone off by holding the power and volume up button. When phone is going on, slide your finger down to the volume down. Once in 'download' mode, you can flash RUU.
Tgorak88.en said:
Download mode is failing to boot.
Click to expand...
Click to collapse
king200 said:
If you can get into download mode, you can likely flash the RUU.exe from HTCdev. Turn your phone off by holding the power and volume up button. When phone is going on, slide your finger down to the volume down. Once in 'download' mode, you can flash RUU.
Click to expand...
Click to collapse
That's the problem that download mode is failing to boot. And when download mode worked and I tried to install Clean RUU from HTC site i had only list of files with 0% and after 10-12 files the phone was just rebooting. I think that there's not one problem as there's also problem in TWRP with "E: -unable to mount /cache" and "E: unable to mount /data".
How do you think what I should do as a first thing try to mount the partitions or go straight to installation of stock ROM?
Thanks
Usually those errors mean that twrp is borked. Have you flashed another twrp?. I use this one: https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk
Beamed in by telepathy.
shivadow said:
Usually those errors mean that twrp is borked. Have you flashed another twrp?. I use this one: https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi @shivadow I have the same issue with twrp 2.8.7.0, but I tried to flash different versions of TWRP with no success, even Roms or whatever it says the same legend of unable to mount, do you have any other suggestion? :crying:
Thanks !
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
Tgorak88.en said:
That's the problem that download mode is failing to boot. And when download mode worked and I tried to install Clean RUU from HTC site i had only list of files with 0% and after 10-12 files the phone was just rebooting. I think that there's not one problem as there's also problem in TWRP with "E: -unable to mount /cache" and "E: unable to mount /data".
How do you think what I should do as a first thing try to mount the partitions or go straight to installation of stock ROM?
Thanks
Click to expand...
Click to collapse
@Tgorak88.en did you find a solution for this? thanks !
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
Click to expand...
Click to collapse
Hi Sorry to say, I have " Exactly" the same problem and have also reached the same place, I asked on these forums without success. in the end I sent it back to HTC and they want £200 to repair it or £29.00 diagnostic fee. I have asked them to send it back and will have to pay the £29.00. If it is within warrantee send it back.
m01y1i00 said:
Hi Sorry to say, I have " Exactly" the same problem and have also reached the same place, I asked on these forums without success. in the end I sent it back to HTC and they want £200 to repair it or £29.00 diagnostic fee. I have asked them to send it back and will have to pay the £29.00. If it is within warrantee send it back.
Click to expand...
Click to collapse
Thanks for your fast reply.
I will get in contact with them and see what they will say. My phone is under warranty so i will pay only for shipping charges.
I bought it from a german eshop and i am from Cyprus.
The problem is, the official distributor for HTC here in Cyprus is Greece and i had a bad experience with them. I sent an old HTC One X 4 years before which had a board issue, and after waiting for a month they sent it back and guess what. It had the same problem. So i got in contact with the US website, described the problem and mentioned also the "official distributors" in Cyprus and Greece and how their "service" was and they told me i will have a brand new phone here in Cyprus within a week (which became a reality).
So before i experience the same issues i will clear everything from here (if anybody know a successful solution) and then communicate with HTC how to resolve this.
Thanks again for your reply!
Is this a general/common problem on htc? I am worried
Spike97 said:
Is this a general/common problem on htc? I am worried
Click to expand...
Click to collapse
I'd be lying if I'd say that I haven't read about the issue several times, already. However, you need to be aware of the fact that most of the time only people with problems are creating threads whereas people who have no issues at all won't do the same for praising the phone.
In other words: Yes, this problem does exist but no, not everyone faces it. I know many users whose M9 is still working fine.
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
Click to expand...
Click to collapse
I also have a bootloop issue with Locked and S-ON... Care to let me know how you managed to get it working the 1st time?
Where to find the corrent stock ROM and the method you did to get it working..
i have the same problem. Where can i get a rom.zip
Bootloop
gmayer1212 said:
i have the same problem. Where can i get a rom.zip
Click to expand...
Click to collapse
Take the new OTA Nougat, separate those three files on your sd card
Install it with fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and it will be working takes 5-10 minutes to restart
kwaichang said:
Take the new OTA Nougat, separate those three files on your sd card
Install it with fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and it will be working takes 5-10 minutes to restart
Click to expand...
Click to collapse
Please don't give such advice. If the firmware isn't matching the system version users will face bugs and lags or the phone won't even boot. (The latter happens for example if you try to use an Android M system with an Android L firmware.) Besides a user with a locked bootloader and a firmware/system-mismatch won't be able to install any OTAs unless that person flashes a RUU for fixing the mismatch*. The catch is there is no publicly available Android N RUU for every variant of the M9, at the moment. And with S-ON you aren't able to use older RUUs. That means people might have to contact Llabtoofer's RUU Service (which isn't for free!) if they followed your recommendation.
* Users with an unlocked bootloader need to fix the mismatch, as well, but at least they have twrp backups as an alternative solution for the problem.
@gmayer1212 & @htcm9guy: You may want to read the ReadMe thread. It's pinned above the normal threads here in this section.
Flippy498 said:
Please don't give such advice. If the firmware isn't matching the system version users will face bugs and lags or the phone won't even boot. (The latter happens for example if you try to use an Android M system with an Android L firmware.) Besides a user with a firmware/system-mismatch won't be able to install any OTAs unless that persons flashes a RUU for fixing the mismatch. The catch is there is no publicly available Android N RUU for every variant of the M9, at the moment. And with S-ON you aren't able to use older RUUs. That means people might have to contact Llabtoofer's RUU Service (which isn't for free!) if they followed your recommendation.
@gmayer1212 & @htcm9guy: You may want to read the ReadMe thread. It's pinned above the normal threads here in this section.
Click to expand...
Click to collapse
Sorry for that. Mine was also hanging in bootloop but unlocked S-on T-mobile Germany
kwaichang said:
Sorry for that. Mine was also hanging in bootloop but unlocked S-on T-mobile Germany
Click to expand...
Click to collapse
Don't get me wrong, I don't want to discourage you from helping others. It's just important that you know which variant of the M9 the user with the problems owns in such cases. Just recommending to flash random stock files only causes more problems than it solves.
Just to chime in --- same problem happened to me yesterday.
Phone has been working fine --- then yesterday phone went unstable so I reset and got caught in bootloop.
After doing a factory reset and many tries -- got it to boot to android, only to get bombarded by google play service errors -- most likely wrong version of google play services for android?? I manually installed google play services apk... Reset and after many tries was able to boot again -- system was smooth. But did a quick reset to check whether problem was fixed and now i'm back in boot loop.
I wonder if there's a problem with a recent google apps update over playstore that's killing boot?
Hello,
i have the same problem but in some ways different. My M9 was running nearly fine until yester der evening. I just plugged the power supply and suddenly black screen, bootloop. But the really big problem is i don't come in any different stable mode than bootloader. If i try to get into download or recovery mode, the silver htc-logo appears for less than a secound, short vibration and reboot - and this is in loop also.
So for me i don't se a way to factory reset or reinstall any RUU or anything else?
Is it destroyed? :crying:
I was complete S-Off before, running on the last firmware with ViperOneM9 6.1.0.
Thans for your support,
Bond
That sounds like the dead nand issue. It's a hardware failure (c.f. the FAQ of the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
If your phone is under warranty, it has a stock rom, and bootloader is still locked, then send it to HTC after contacting them via chat.
They will replace either the board or the device.
This is whhat they did for me.
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
Click to expand...
Click to collapse
is your phone recongized - what shows "fastboot devices"
pear-i said:
Just to chime in --- same problem happened to me yesterday.
Phone has been working fine --- then yesterday phone went unstable so I reset and got caught in bootloop.
After doing a factory reset and many tries -- got it to boot to android, only to get bombarded by google play service errors -- most likely wrong version of google play services for android?? I manually installed google play services apk... Reset and after many tries was able to boot again -- system was smooth. But did a quick reset to check whether problem was fixed and now i'm back in boot loop.
I wonder if there's a problem with a recent google apps update over playstore that's killing boot?
Click to expand...
Click to collapse
I too wonder the same - recently had the bootloop issue with my M9, just when it was updating apps from the Playstore... quite suspicious...
My HTC M9 is also in boot loop
htcm9guy said:
I also have a bootloop issue with Locked and S-ON... Care to let me know how you managed to get it working the 1st time?
Where to find the corrent stock ROM and the method you did to get it working..
Click to expand...
Click to collapse
It happened at last Saturday, when I've just tried to perform a regular reset to my HTC M9 (from the regular device's menu).
I can't enter to download mode (fail), wipe cache and wipe all (factory reset) didn't help.
Is there any chance to fix it at home? Or just to buy a new phone?
And, does this issue can occur in other devices, HTC or any other brand?
Please advise.
(Can't upload a picture of my device, since I'm a new user...)
Thanks!
As far as I know there's nothing you can do. There are no reports of successful diy repairs of a dead nand M9.
Theoretically this issue can happen with any phone. However, it looks like the probability of its occurence on a M9 increased a lot during the last months.
I´m also stuck in bootloader mode
recovery mode / download mode endup with red text:
"failed to boot to download mode"
***Software status: Modified***
***LOCKED***
***S-ON***
***Security Warning***
Cannot get the token as fastboot oem commands end up empty or unknown command.
I think USB-debbugging is "off"
How can i get S-OFF
or how can i get token
Thanks.