Hello,
I have an HTC One M8 (T-Mobile) that I had a friend root (he has a PC, I have a Mac, plus he's done it before) and all was going well until I installed a rooted app (I think it was Super SU or something) and my phone went into a boot loop, showing nothing but the HTC logo when I tried to turn it on. I panicked, even though it wasn't the end of the world, as I had just bought this phone from a classifieds source and had no personal info/pictures/contacts/anything on it yet.
However, I am still stuck with a soft bricked phone. My friend suggested going into recovery mode and rebooting (see attached picture) but it didn't help. Then he tried side-loading a ROM onto the device, but his computer (both of them, PCs, and even his brother's PC for good measure) didn't show it recognized the phone anywhere in the file system. And he said he looked EVERYWHERE and tried everything. Then he tried downloading HTC's own proprietary system for installing a custom ROM (I forget what it's called) but his PC wouldn't recognize it, so he couldn't use it either). He all but gave up on trying to restore my phone to how it was after he ran into the last of these problems.
I, however, refuse to believe that with the wealth of knowledge at my disposal via the internet that there is no way to fix this, even though I have a Mac. Is there ANYONE who's patient and Terminal-savvy that can help me get my M8 back to normal working condition? I don't even care about rooting it anymore. Thanks in advance for your instructions/suggestions.
I would just go into TWRP and mount the internal storage as usb, copy a ROM to the phone, umount internal storage and do a full wipe and install the ROM.
Do you want Stock, modified stock, CM??, GPE? you just need to figure out which version of ROM you want.
I think I already tried this...
I was just trying to install the stock firmware via a micro USB but the phone wouldn't recognize it on the micro USB stick in TWRP, is there a reason for this? As I'm assuming a restore to stock firmware is impossible if it can't recognize or read the firmware I'm trying to restore it to. Thank you
Hello? Anyone?
Related
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.
^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!
Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!
And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .
All,
I have used my GS3 for awhile now without issue. I'm abroad for the forseeable future, so I've only been using it for Wi-Fi calling and internet/apps. Regardless, Kies NEVER worked for me, and my computer never recognized the USB device. Up until recently, I've just used my iPod for music, so no problem.
Fast forward and my friend, who also has a GS3, tried to update my drivers and root/flash my phone so I can drag and drop files the way he does with his. I let him do this because I'm newb to this, and because he assured me he knew what he was doing as he'd done it to his and his girlfriend's phone.
As it turns out, he has an international version (he used ToolKit instead of QCom ToolKit) and he tried to root the wrong files to my phone. At first, I thought it was hard-bricked (which really puts me in a tough position since I won't be back in the States until January), but I don't think even his root attempt worked properly.
So where I'm at now:
The phone will not boot up. When I turn it on I get the Samsung Galaxy S III logo, but android never loads. The phone will charge via USB and the wall.
I can access recovery bootup
I can access download bootup (the ability to do the two above lead me to believe it isn't hardbricked, I read on these forums, if I can get to download bootup then it's probably fix-able)
I've combed the forums and the internet, in general, for a fix. I downloaded the factory restore settings from samsung-updates (sorry if I cannot plug this site, it's not intentional, simply to provide as much info as possible), but Odin always "FAIL"s when I attempt to apply it.
Additionally, I've attempted to recover via recovery bootup/reset, and then load the factory restore setting via Odin. This did load them, but the phone did not boot up.
QM ToolKit was acknowledging the phone, so I attempted to boot the correct files using ToolKit (the ALLINONE option) and this worked correctly, as expected via QM ToolKit. But still the phone would not boot up.
The phone sits at a black screen after the GSIII logo with the blue LED lit up.
Any tips or advice would be appreciated. I'm in quite a situation.
sadly i have the same problem, this happened randomly and cant get my device to boot
If you Odin tmo stock image tar and odin recognized your device and all went well then boot into stock recovery factory reset then reboot. It should boot up if all is well. When you plug to pc does your computer recognizes it?
Sent from my SGH-T999 using xda app-developers app
Provided your boot loader and download manager partitions are working(as it appears to be the case) you can get your phone back to a "working" state.
What I suspect happened is that at some point during the process of playing with it, your partition table got hosed and now android is borked. I would recommend re-partitioning it but I don't have enough info around me and available to give you instructions to do so. I'll do some digging and try to get back to you.
Hi there,
I've been trying to fix this issue for a while now and I haven't seen any guides on my particular issue.
Basically what's going on is I tried doing a factory reset on the phone while having cyanogenmod flashed and when it booted, it would keep booting up in the recovery.
There seem to be no backups or roms on the phone.
Now here's the kicker, when I try using the Nexus root toolkit, it doesn't recognize my device whatsoever. I've uninstalled the drivers fully and reinstalled them and still nothing.
When I plug the phone in, it doesn't show up as an external source (other than in the device manager with a "!" by 'galaxy nexus'), so I can't just put a ROM on there and try flashing that.
I'm stuck. I have no idea what I can do to get this back up & running.
It's a GSM phone, being from Canada I believe it to be Yakju...
Anybody have any ideas? I really need this phone to start working!!
Have you tried the method in this tutorial?
you may bring ti back to samsung customer service.
Hi guys,
I REALLY need some help on this one...! I majorly messed up.. I'm on the road at the moment, which makes this even more difficult.
So I was running CandyRom on the old L firmware. I was getting ready to upgrade to another M Rom (Skydragon).
So I read that, of course, I need to upgrade the firmware. So I stuck 6.12 (6.012? Whatever latest one is) official firmware.zip on the SD, changed its name to Oxxxxx.zip (I can't remember the exact name) and booted into bootloader to install.
Now my problem is that this has (seemingly) wiped TWRP from my phone.
So here are my tools:
Windows laptop.
USB Cable.
(Very slow) internet.
How do I get from my phone being stuck in this state, to installing TWRP again, and being able to flash a rom? I can't directly access the SD card, and I'm not even sure I can ADB into the phone from its current state...
Also, my bootloader says that my phone is 'relocked' if that makes any difference.
Been a while since I've tinkered with all of this... please be gentle. Would really appreciate any help!
Files downloaded so far: TWRP 3.0 .img for one M8...
edit: I've installed HTC USB drivers... trying to download ADB drivers so I can at least use fastboot to get into phone. Let's hope it works...
Meanwhile... please help T_T
Expert advice needed please. This is a puzzle that someone might enjoy solving.
Although I have a fair bit of experience with flashing, I tried to flash my 8.0 for the first time and it has dramatically failed. It was probably my fault - not an uncommon story.
What is less common is that I am struggling to figure out how to undo the damage I've done. What's really making this difficult is that no computer recognises the device as USB any more so I can't use Odin, Kies, etc to repair or return to stock. I have tried everything I can think of to deal with the USB issue, the usual cable, driver, port nonsense. I don't think the USB problem is Windows now.
I suspect one of these things may have happened:
The USB port just went bad coincidentally during this flash process (charge, no data). I have ordered a new port but it will take weeks to arrive.
Has the device come out of Developer/USB debugging mode somehow? I can't tell because I can't boot to an OS.
I wonder if the ROM flash has corrupted the firmware the deals with USB - is that possible? Where is the devices USB drivers located? Is it in the bootloader, something like BIOS?
I'm suspicious of the bootloader, as the screen is weirdly corrupted now when I turn on or reboot the device - fuzzy white lines rather than a logo - but that disappears when OS tries to load, or I go into Recovery/Download.
I actually did do a backup of the original ROM to the SD card; but restoring it doesn't work, just produces an endless Samsung boot, even if I then wipe and reset.
I can get into Download mode, and a Recovery (Philz for N5120) but since I can't connect to the devise with USB in any way, it's very hard to get the Recovery to flash anything new and useful. I did put my SD Card in another phone and copied over the stock ROM zip from Samsung, but it refuses to flash - I think because it doesn't like Philz Recovery? I can't think how to replace Philz Recovery with another by flashing, without USB.
I may have to wait to replace the USB port, but I fear that won't fix it. Until then, I can only think of one other thing to try, and that is to copy a ROM onto the SD Card through another phone, and try to flash it. Lineage doesn't flash, and nor does the stock zip I got from Samsung. Would anything else work?
Can I flash an alternative recovery from within the recovery? Philz only lets me flash zips, not img or tars.
So it's quite a mess, but if anyone has a brilliant idea of how to get out of this, I'd love to hear it.
THANK YOU if you have a genius idea.
So after a few days of working on this, I did manage to resolve it, and I thought I'd just add a note about how I escaped this obscure problem.
The device went bad because I stupidly flashed an incompatible Recovery to the device and somewhere between doing this, backup and restoring and flashing, it corrupted mostly everything including something in the bootloader.
Oddly enough, the solution seemed to be to mess up the Recovery even more by flashing something even more random - it seems this provoked the device into restoring its own basic Recovery. Using this to wipe and reset the device somehow enabled Download mode's USB interface to start working again so I was able to use Kies to return to stock, which repaired everything including the bootloader.
Finally, I flashed the correct Recovery for this device, and then managed to flash the ROM I wanted. A happy ending to a stressful story; the device now works better than it ever has done before.