[Completed] [Q] HTC M8 Won't Switch On - XDA Assist

This post doesn't seem to match others asked before.
I had a perfectly working rooted/rom'd HTC One (M8). Unfortunately, screen cracked so I sent it off to the insurer to sort. It came back looking great. However, I was now unable to access any of the internal storage. Everytime I tried to download a photo, voice clip or Mod Edit: removed mention of warez it would say 'unable to download', 'cannot save' or something along those lines.
I checked to see the device was still rooted. It was. Nevertheless, I perhaps in ignorance, ran through all the steps over again and spent 3.5 hrs doing so! I now have a wonderful adb file on my desktop and I was fiddling around doing fast reboots etc and trying to flash a customrom in the hope that this would fix the storage invisibility/lack of permissions. I tried fixing with busybox etc but I couldn't even install busybox as it didn't recognise that there was any internal storage whatsoever! I also could not load onto my storage (for the same reason!) the latest SuperSU zip to flash as a rom.
In the end, through fiddling about, I was able to find my old storage pack. It was all there and I located an old SuperSU from when I had previously rooted about 6 months ago (an old version now I assume). Flashed this and rebooted. I was still adb connected so ran a fastboot and chose to run the TeamWin Recovery Wipe (standard setting, not advanced).
When wiped, I tried to get my phone to turn back on thinking it would be factory reset and I could start again but now I literally cannot get my phone on!! It is plugged into the computer via USB (i've tried disconnecting it too) and no matter what I try I cannot get this phone to do anything now - it's just a black screen that doesn't look completely off if I look closely it looks like it is on somehow....? Tried holding down vol down and power - nothing. It has flatlined!
Any help PLEASE!!!!! ?????

Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-one-m8 To get help on your specific problem try asking here, http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783

Related

[Q] Stuck in a reboot loop, please help

I got my Viewsonic GTablet on Friday (2/11/2011). I loved it and had no issues. I downloaded and installed the update from Viewsonic. I visited the Marketplace that's installed on the device and downloaded some apps, mainly games. Today (2/14/2011) I took it to my university and tried to get on the campus WiFi. I had difficulties, so I took it to the IT department on campus to get some help. They took my device, tried to get it on the network and said that my device could not get on the network because their network uses certain "secure credentials" or something like that. As soon as I get my device back from them, every time it boots up I get and error message that says that Dashboard Home has stopped unexpectedly and to try again. I called Viewsonic's Customer Service, and they determined that I was stuck in a reboot loop. I have tried rebooting the kernel more time than I can count, but it doesn't do anything to help.
Has anyone else been able to solve this problem? I would take it back to the store I bought it from (Office Depot) to get an exchange, but they don't have one in stock anywhere close to where I live, and I don't have the box the device came in anymore.
What do you suggest I do?
The device is running the stock OS with the update from Viewsonic. The only apps I have installed are from the marketplace that comes with the device. I have not tampered with the OS or settings. I am also mildly technically challenged, but I am working on educating myself.
I appreciate any and all help. Thanks in advance. I also apologize if this has issue has already been posted and answered.
vafalla,
This doesn't sound like the boot loops I had, but I guess if it doesn't get you to a screen you can work with the result is the same.
If it were me I would get on a PC and go the the Development part of this forum. I think you need to get ClockWorkMod installed. CWM is a replacement "recovery" program that gives you other functionality to restore, communicate, partition drives and a bunch of other things. There are a couple of threads in the Dev section that tell how. You can download CWM v.08 (the older one works!) and put the update.zip file on a microSD card and edit the recovery folder "command" (no .txt or other ending, just command) file in Notepad to load "sdcard2" instead of sdcard. then put the card in the gtab and reboot holding down the Vol+ key down. You'll get a message in the upper left corner of the screen that recovery is loading. After it installs, if it doesn't startup, reboot with the Vol+ key down again and you should be able to get into CWM.
From there, you can find the CWM partition command and change the two partitions to 2048 and 0.
From there, there are a bunch of threads which tell how to load either a stock recovery file to get back to stock -- or how to load VEGAn 5.1 (or now, 5.11).
Hope this helps get you started. I just didn't want you to think your tab is bricked and that all hope is lost!
Rev
P. S. --- Some of the other threads may have better instructions than mine!!!
Thanks so much for the help! I'll get right on it and see what happens.
Plug in your gtab to the power and see if it boots. Could be they ran your battery down.
Bootloop help
If you really want to learn about the gtablet, youtube ehunyadi. he has done over 10 excellent videos and his most recent is how to install CWM and TNT lite 4.2..sounds like only diereence for you is you'd install CWM to microsd.

[Q] Noob Question/Issue

Hi all, Have been reading here for quite a while before flashing my Sprint Hero.
I used the Z4 Root method, d/l busybox and clockworld recovery as you showed in the video. All worked perfectly. Cleared all of the caches. Flashed with aospMOD 0.9.9.2, and now phone boots into this mod.
One issue is there is no market, I cannot get back to the flash prog to flash the googleapps.apk, which is in the root of my SD card, as well as the Z4 Root prog. When I click on these to install, the HTC Sync App Installer starts and advised me to connect a phone...?... I can go to the Market via the browser and d/l from there, but HTC Sync will not recognize my phone now when attempting to install a new app or just sync. I'd like to play with some different mods, but when I hold down the Phone and Home buttons, I'm brought to the stock recovery which just resets the data in the phone.
If I have not given enough info please let me know,
Any assist would be appreciated...
Resolved
Well, I remember way back from the early days of FTA that learning a new hobby is quite fun. I simply made a "learning" error; I was NOT rebooting the phone so I could see the Recovery screen, I was merely powering it on and off. Once I hit reboot and saw the Recovery option I realized I hadn't read enough
I initially installed the first recovery image using the terminal commands as outlined on this site; Worked great!
Got it all working now and feel confident in playing around without bricking...
Ruwiten7

[Q] Sprint Nexus S 4g bricked: HELP!

Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App
Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.
Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App
Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.
Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.
Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.
I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'
Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.
How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2

[Q] HTC One S Terrible bootloop/soft brick on TrickDroid ,cant find solution

Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.

[Q] Big problem: cant mount SD&cant connect to PC

Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
PC connection
DieterW91 said:
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
Click to expand...
Click to collapse
I've had success getting a connection to Windows just be using a different USB port, the ones at the back are best. Then at least you get fastboot access...But I also still have the problem with the sdcard, still working on that, trying to figure out a way to fix it from fastboot...
any progress yet rosanna? I was also able to make the connection with my pc, by using the usb ports on the back (thanks for that!). But I haven't been able to mount my sd card yet. I tried with another recovery but that didn't do the trick.
I got into the UI of my current ROM, and then my pc said I needed to format the SD before I could use it.
But I wasn't sure this is a good idea to do in windows.
Anyone know if it is save to format your internal sd card when prompted to do so in windows?
Have a look here
Sent from my ElementalXed One S
Try using a Linux live cd (try Ubuntu). You'll need a blank DVD to burn the iso to. Reboot your computer and see if it recognizes your device (no drivers needed). If it does try a more stable build this time.
benJX said:
Have a look here
Sent from my ElementalXed One S
Click to expand...
Click to collapse
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
DieterW91 said:
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
Click to expand...
Click to collapse
1 minute - downloadlink is on the way
Here you are: http://forum.xda-developers.com/attachment.php?attachmentid=2622663&d=1394422408
You can flash it with the toolkit selecting "Custom recovery".
When you're Storage is back alive and kickin' you can flash a custom revovery again.
My favourites are
TWRP 2.7.0.0 - http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
and
PhilZ advanced CWM - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville
In my opinion TWRP is easiest to handle and PhilZ has some more features.
DieterW91 said:
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
Click to expand...
Click to collapse
Another direct link here, I personally flashed it manually trough fastboot, for me the easiest and fastest way to do it. Then proceed to the clear storage and flash your custom recovery (like @LS.xD I recommend TWRP but this is your choice )
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
DieterW91 said:
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
Click to expand...
Click to collapse
Feel free to hit the "thanks" button

Categories

Resources