Related
Here is what I've tried so far:
1- SuperOneClick. The program hangs at a step where it reads "Check if rooted : false"
2- Galaxy One Click Root. Program is responsive but it stops at "* daemon started successfully *" and does nothing from there.
3- Copying the "update.zip" file to the root of my internal SD card. I'm greeted by a "E: Signature verification failed. Installation aborted" error.
All remediable steps to fix one or all problems REQUIRES root, so i'm in limbo here. I honestly am about to cry. This seemed a hell of a lot easier when I read about it...
Well, what's left here for me to do? I'm lost. I read so many threads here I honestly can't do it anymore. This is my last resort.
This phone is all stock, AT&T Captivate.
Sorry if this is the wrong section of this forum... New here.
Flash your phone via Odin to jf6 stock then try superoneclick
Sent from my SPH-D710 using XDA App
hold up on that flash back. It oculd cause you to loop. Try using SOC v1.9 or lower. Also make sure your computer has all the required updates installed.
So this developed into a new, bigger, problem. I tried THIS guide to flash cyanogenmod (latest) but, guess what, the freaking thing hanged. So I was left with the only option, severing the link between PC and phone, and rebooting the phone.
I get this "phone - attention sign - computer" image. I think to myself "oh sh#&, I bricked the phone" so I rebooted it once again and to my surprise, the phone won't turn on. Won't react to the usb cable (can't boot to download mode), won't react to wall charger, won't turn on with the power button.
The battery was almost full...
What the heck is going on!?!? I had this phone for 3 days and I already ruined it?
I wan't to kill myself
leandroab said:
So this developed into a new, bigger, problem. I tried THIS guide to flash cyanogenmod (latest) but, guess what, the freaking thing hanged. So I was left with the only option, severing the link between PC and phone, and rebooting the phone.
I get this "phone - attention sign - computer" image. I think to myself "oh sh#&, I bricked the phone" so I rebooted it once again and to my surprise, the phone won't turn on. Won't react to the usb cable (can't boot to download mode), won't react to wall charger, won't turn on with the power button.
The battery was almost full...
What the heck is going on!?!? I had this phone for 3 days and I already ruined it?
I wan't to kill myself
Click to expand...
Click to collapse
Unfortunately, it doesn't sound promising. Even if you have a black screen, I would still try to access DL mode with Odin open (pull battery, remove sim, put battery back in, hold both volume buttons and insert the USB cord, don't touch the power button). If you get a yellow com light in Odin, even if the screen stays black, you're in download mode. If that doesn't work, you could try a jig and then see if Odin recognizes it. If neither of those work, you'll need to send your phone out to someone like Adam Outler to have it unbricked.
I get nothing with Odin. I can't believe I bricked my phone like that. I thought I would get an error screen at least. But this is outrageous. It's like the phone shorted and fried from the inside.
All I can say is wow... My happiness of a new phone turned to ashes in 30 seconds. Nice waste of money.
If you buy a USB download jig it will get you out of soft brick situations and if Odin fails try heimindal
Sent from my SPH-D710 using XDA App
leandroab said:
I get nothing with Odin. I can't believe I bricked my phone like that. I thought I would get an error screen at least. But this is outrageous. It's like the phone shorted and fried from the inside.
All I can say is wow... My happiness of a new phone turned to ashes in 30 seconds. Nice waste of money.
Click to expand...
Click to collapse
It didn't fry, it failed while flashing bootloaders. The bootloaders are what tell your phone what to do when you press power. Mismatched bootloaders = hard brick = no power up.
I would still try a jig, but if that doesn't work send a message to AdamOutler. He can give you the details of getting it unbricked.
MJHawaii said:
If you buy a USB download jig it will get you out of soft brick situations and if Odin fails try heimindal
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Considering the flashing hanged at the very beggining, I'm 90% sure it HARD-bricked my device. A jig wouldn't work and I'm left with a very fancy paperweight.
There is NO power on whatsoever.
My luck is amazing, isn't it?
Please, someone tell me there is still hope (there isn't probably)
apbthe3 said:
It didn't fry, it failed while flashing bootloaders. The bootloaders are what tell your phone what to do when you press power. Mismatched bootloaders = hard brick = no power up.
I would still try a jig, but if that doesn't work send a message to AdamOutler. He can give you the details of getting it unbricked.
Click to expand...
Click to collapse
Exactly. I figured
I have no idea of who "AdamOutler" is. But I'll find out. :/
FML
leandroab said:
Considering the flashing hanged at the very beggining, I'm 90% sure it HARD-bricked my device. A jig wouldn't work and I'm left with a very fancy paperweight.
There is NO power on whatsoever.
My luck is amazing, isn't it?
Please, someone tell me there is still hope (there isn't probably)
FML
Click to expand...
Click to collapse
I suspect you are correct about the hard brick, but I would still try a jig. I had a failure flashing bootloaders once that killed my cappy, but though a stroke of fortune a jig still worked for me. You can build one for a couple of bucks of parts from Radio Shack, you've got nothing to lose. If not, it can be repaired.
Before you start looking at all that, make sure you are hard bricked. Easiest way is to use Linux Mode Detector. Use the link below labeled Captivate sig link, then choose am i bricked?.
apbthe3 said:
I suspect you are correct about the hard brick, but I would still try a jig. I had a failure flashing bootloaders once that killed my cappy, but though a stroke of fortune a jig still worked for me. You can build one for a couple of bucks of parts from Radio Shack, you've got nothing to lose. If not, it can be repaired.
Click to expand...
Click to collapse
Yes, it's still worth a try. But unfortunately it will have to wait at least till the end of the month. That's when my college break is over and I'm back to school.
mrhaley30705 said:
Before you start looking at all that, make sure you are hard bricked. Easiest way is to use Linux Mode Detector. Use the link below labeled Captivate sig link, then choose am i bricked?.
Click to expand...
Click to collapse
Sorry but I'm not installing an OS just to use a program. I do believe the phone is hard-bricked though:
1- Doesn't power up with the on/off button
2- Doesn't go into recovery mode
3- Doesn't go into download mode
4- Doesn't light up when plugged into wall charger
If that isn't hard-bricked, then I'm really scared to find out what that really is
I sent a PM and an email to Adam Outler. I hope he replies it!
Linux is easier to use than you think, and it's a really handy tool to have when working with Android phones. You can install Linux entirely to a cheap thumb drive (I have a $4 4gb thumb drive running lubuntu) and it can get you out of a lot of Android related jams. If you're not willing to go through letting Linux up and running, might not want to do too much with phones either. I don't mean to be snarky, but I started using Linux casually a couple years before I started messing with phones and Linux is much more straightforward.
Edit: and if you have a multimeter around, check the voltage of your battery. Should be 4.2v=full, 3.5v ish is dead. If you battery pull, reinsert, hold volume up and down, and then connect to your pc with Odin open (don't hit power) what does Odin show? Last, did you get this phone used? Battery may be completely worn out, which would be why it was almost full and looks hard bricked now.
Wubi installer would be a better choice. And when your finished, it uninstalls just like an app. It's kind if a semipermanent dual boot. Check it out.
sekine12 said:
Linux is easier to use than you think, and it's a really handy tool to have when working with Android phones. You can install Linux entirely to a cheap thumb drive (I have a $4 4gb thumb drive running lubuntu) and it can get you out of a lot of Android related jams. If you're not willing to go through letting Linux up and running, might not want to do too much with phones either. I don't mean to be snarky, but I started using Linux casually a couple years before I started messing with phones and Linux is much more straightforward.
Click to expand...
Click to collapse
Well, I guess I'll look into that now. I'm running windows over a MacBook (stuck with it till I get back home). Maybe some tips running linux w/ a pendrive with bootcamp?
sekine12 said:
Edit: and if you have a multimeter around, check the voltage of your battery. Should be 4.2v=full, 3.5v ish is dead. If you battery pull, reinsert, hold volume up and down, and then connect to your pc with Odin open (don't hit power) what does Odin show? Last, did you get this phone used? Battery may be completely worn out, which would be why it was almost full and looks hard bricked now.
Click to expand...
Click to collapse
I'll look into the multimeter. The phone IS used, but I'm sure the battery isn't worn out.
Hooking up the phone, pressing both volume buttons, with odin open gives me nothing. Zip. If it was the battery wouldn't the phone give some sign of life after charging it for a while? Didn't happen.
mrhaley30705 said:
Wubi installer would be a better choice. And when your finished, it uninstalls just like an app. It's kind if a semipermanent dual boot. Check it out.
Click to expand...
Click to collapse
As stated, using windows with bootcamp over a MacBook. Maybe you can help me out? Will this work?
leandroab said:
If it was the battery wouldn't the phone give some sign of life after charging it for a while? Didn't happen.
Click to expand...
Click to collapse
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
apbthe3 said:
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
Click to expand...
Click to collapse
Right, or if the battery is so dead it can't start to turn on, it won't turn on. Or, if it was soft-bricked with no images to display, it may have killed itself without a firmware to allow it to charge properly. Not very likely, but there are a couple possibilities that end with a dead battery and no way to know.
apbthe3 said:
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
Click to expand...
Click to collapse
sekine12 said:
Right, or if the battery is so dead it can't start to turn on, it won't turn on. Or, if it was soft-bricked with no images to display, it may have killed itself without a firmware to allow it to charge properly. Not very likely, but there are a couple possibilities that end with a dead battery and no way to know.
Click to expand...
Click to collapse
Right. I'll check the V of the baterry once I get my hands on a multimeter.(somebody took all of them here at the house for some reason)
The multimeter read that the battery has 3.92V, so it's not dead. So to sum it up I only have two options now:
1- Try a USB jig
2- Attempt the UnBrickable mod/send it to Adam Outler
Both of them will take time. Unfortunate for me. Good news is that WILL have it back up and running. It will just take some time
leandroab said:
The multimeter read that the battery has 3.92V, so it's not dead. So to sum it up I only have two options now:
1- Try a USB jig
2- Attempt the UnBrickable mod/send it to Adam Outler
Both of them will take time. Unfortunate for me. Good news is that WILL have it back up and running. It will just take some time
Click to expand...
Click to collapse
So nothing whatsoever shows up in ODIN when you 1- batt pull, 2- batt reinsert, 3- plug in USB while holding either volume down, or volume up + vol down (w/o turning phone on)?
As the title suggests, I downloaded the app AParted by sylkat through Google Play in order to partition my EXTERNAL SD-card. However, in the hurry of doing this, I believe I have formatted the INTERNAL SD-card, which has resulted in a pretty much dead phone.
It does not respond to anything. I have tried all combinations, the hard-reset button, everything I can think of. My computer is no longer able to recognize it either.
I am then wondering if there is a way to recover the data in the internal SD-card, or just any fix?
Some info:
- My device is fully rooted with BL unlocked.
- I had installed iHackers 2.0 ROM on it
- I have backups made through TWRP-recovery
All help is highly appreciated. Thank you
- Sari95
Sari95 said:
It does not respond to anything. I have tried all combinations, the hard-reset button, everything I can think of. My computer is no longer able to recognize it either.
Click to expand...
Click to collapse
So you can't get into recovery, fastboot, or flash modes?
What happens if you plug the device in to charge?
Unless you can get into recovery, it's unlikely that you'll be able to recovery anything. If you do manage to flash a bootable ROM onto the phone, you'll be writing onto the internal SD card and physical overwriting all your old data, removing the possibility of recovery.
If you can get into recovery, you may be able to connect USB, mount the internal SD partition, and then try running a file recovery tool on it. I don't know if the whole USB mounting bit will actually work, haven't tried that.
If you formatted the internal memory of your phone forget to try recover the data. It's close to impossible and for laboratory experienced only. Even if you try many files can be corrupted and it will not work anyway. I try many apps for classic HDD and they recover almost pictures and mp3 only, and if many files are in sub-folders this get more complicated.
If you have a backup of your entire system I will suggest to go back to Stock flashing original FTF then go through all the process to get again iHackers 2.0 ROM on your phone and when you can access to the TWRP recovery, restore your latest backup and you will have your phone back like it was before formatting.
eclyptos said:
If you formatted the internal memory of your phone forget to try recover the data. It's close to impossible and for laboratory experienced only. Even if you try many files can be corrupted and it will not work anyway. I try many apps for classic HDD and they recover almost pictures and mp3 only, and if many files are in sub-folders this get more complicated.
If you have a backup of your entire system I will suggest to go back to Stock flashing original FTF then go through all the process to get again iHackers 2.0 ROM on your phone and when you can access to the TWRP recovery, restore your latest backup and you will have your phone back like it was before formatting.
Click to expand...
Click to collapse
I expected that. My main problem is that it does not do anything at all. If I had been able to connect it to my computer, I would have probably been able to fix it, but it does not connect to anything at all.
My only saviour would be a so-called "Jig", which boots the device into android through an SD-card, but I am not sure whether there exists one for Z1 or how to make one myself.
So is there any way of connecting or just giving the phone a breath of life through an SDcard-solution?
Probably only through the Update Service or Emma...
http://developer.sonymobile.com/services/flash-tool/
jamespmi said:
Probably only through the Update Service or Emma...
http://developer.sonymobile.com/services/flash-tool/
Click to expand...
Click to collapse
I have tried both EMMA and SUS without success.
xasbo said:
So you can't get into recovery, fastboot, or flash modes?
What happens if you plug the device in to charge?
Unless you can get into recovery, it's unlikely that you'll be able to recovery anything. If you do manage to flash a bootable ROM onto the phone, you'll be writing onto the internal SD card and physical overwriting all your old data, removing the possibility of recovery.
If you can get into recovery, you may be able to connect USB, mount the internal SD partition, and then try running a file recovery tool on it. I don't know if the whole USB mounting bit will actually work, haven't tried that.
Click to expand...
Click to collapse
Yes, I have tried all those.
1. Tried powerbutton + volume up -> nothing happened
2. Powerbutton + volume down --> nothing
3. plug into the wall --> nothing
4. Plug to computer --> nothing
Considering the internal SD-card, which acts as the brain of the phone, is formatted. The "brain" has been removed, thus it does not know what to do when I push the buttons or plug it to the computer.
Sari95 said:
Considering the internal SD-card, which acts as the brain of the phone, is formatted. The "brain" has been removed, thus it does not know what to do when I push the buttons or plug it to the computer.
Click to expand...
Click to collapse
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.
You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
xasbo said:
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.
You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
Click to expand...
Click to collapse
Hmmm... that I am not sure of.
Exactly! no vibration nor LED light when I push the powerbutton. Imagine yourself pushing the button, yet it is as if you did not push it at all. I have tried the force-off button too, so my last and final solution seems to be the service center.
Thanks for your replies! HIghly appreciated
xasbo said:
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.
You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
Click to expand...
Click to collapse
Sari95 said:
Hmmm... that I am not sure of.
Exactly! no vibration nor LED light when I push the powerbutton. Imagine yourself pushing the button, yet it is as if you did not push it at all. I have tried the force-off button too, so my last and final solution seems to be the service center.
Thanks for your replies! HIghly appreciated
Click to expand...
Click to collapse
WOOOPPP! I have some kind of development actually. Now, when I plug the device to the wall or computer, a red
LED lights up for about 3 seconds before disappearing. However, from here nothing happens and it is dead as usual.
Any idea how to go further from here ?
From what I've read. That means the battery is completely dead.
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
lil-diabo said:
From what I've read. That means the battery is completely dead.
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
Click to expand...
Click to collapse
This is a good point, I didn't consider a dead battery scenario (though it makes a lot of sense versus the phone just doing nothing). I haven't actually read about cases where USB charging will bring back a super dead phone, but it's theoretically possible if the battery were removed and charged manually. That process, however, is definitely only for people who know what they're doing with potentially explosive battery chemistry. If nothing else, leave it plugged in for a while and see what happens.
I remember posting in another thread where someone killed their battery. The best preventative measure is to make sure you never get below 10% or so. The generally dispersed "knowledge" that taking the battery to 0% is good for calibration is NOT TRUE. These are Li-ion batteries, and deep discharges permanently reduce the battery capacity.
lil-diabo said:
From what I've read. That means the battery is completely dead.
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
Click to expand...
Click to collapse
xasbo said:
This is a good point, I didn't consider a dead battery scenario (though it makes a lot of sense versus the phone just doing nothing). I haven't actually read about cases where USB charging will bring back a super dead phone, but it's theoretically possible if the battery were removed and charged manually. That process, however, is definitely only for people who know what they're doing with potentially explosive battery chemistry. If nothing else, leave it plugged in for a while and see what happens.
I remember posting in another thread where someone killed their battery. The best preventative measure is to make sure you never get below 10% or so. The generally dispersed "knowledge" that taking the battery to 0% is good for calibration is NOT TRUE. These are Li-ion batteries, and deep discharges permanently reduce the battery capacity.
Click to expand...
Click to collapse
Great point, you two.. This reason seems quite probable too. However at the same time, it is WEIRD if the battery suddenly dies as a result of formatting the internal SDcard :l
Maaan, I had a slight hope, but I'll try charging it overnight.
Worst case scenario, the service center finds out I had rooted it and I have to pay for the service....
Sari95 said:
Great point, you two.. This reason seems quite probable too. However at the same time, it is WEIRD if the battery suddenly dies as a result of formatting the internal SDcard :l
Maaan, I had a slight hope, but I'll try charging it overnight.
Worst case scenario, the service center finds out I had rooted it and I have to pay for the service....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2574764
There's an entire thread dedicated to how people bricked their phones. Have a look there for some info
It all relates to flashing phones, but maybe what you done had some kinda of a similar effect
Do you remember how much charge you had left?
Supposedly the system loses calibration with the battery and and and and (Most of this relates to flashing though, so hopefully you just have a completely dead battery and an overnight charge will fix it back up.
I also don't think you lose warranty from having your phone rooted?
Think voiding warranty only applies if you unlocked your boot loader... - I could be wrong though.
Good Luck!
Sari95 said:
WOOOPPP! I have some kind of development actually. Now, when I plug the device to the wall or computer, a red
LED lights up for about 3 seconds before disappearing. However, from here nothing happens and it is dead as usual.
Any idea how to go further from here ?
Click to expand...
Click to collapse
Actually I saw this behavior on deads Z1 thread, sorry to say, this actually is not a good sign.
lil-diabo said:
I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
Click to expand...
Click to collapse
Yes, I will suggest this too and when your phone apparently will be charged try just to push volume down and connect via usb to pc and see if it will be recognized. If he dose flash a stock FTF immediately.
lil-diabo said:
http://forum.xda-developers.com/showthread.php?t=2574764
There's an entire thread dedicated to how people bricked their phones. Have a look there for some info
It all relates to flashing phones, but maybe what you done had some kinda of a similar effect
Do you remember how much charge you had left?
Supposedly the system loses calibration with the battery and and and and (Most of this relates to flashing though, so hopefully you just have a completely dead battery and an overnight charge will fix it back up.
I also don't think you lose warranty from having your phone rooted?
Think voiding warranty only applies if you unlocked your boot loader... - I could be wrong though.
Good Luck!
Click to expand...
Click to collapse
Yea, I read through a few pages of that thread, but didn't feel it covered my case. I had a minimum of 89% of battery and it was charging. Hmm.. about the battery calibration, the day before this happened, I charged my phone to 100% and used Battery calibrator, which is an app in Play Store to calibrate it, so this shouldn't be a problem.. However, I suppose something has happened during the formatting.
I am quite certain one loses warranty when rooted or has unlocked BL.
eclyptos said:
Actually I saw this behavior on deads Z1 thread, sorry to say, this actually is not a good sign.
Yes, I will suggest this too and when your phone apparently will be charged try just to push volume down and connect via usb to pc and see if it will be recognized. If he dose flash a stock FTF immediately.
Click to expand...
Click to collapse
Indeed, this seems to be my last way out of this. Either it comes back to life in the morning, or I am doomed! haha I have even prepared FLASHTOOL and the firmware, if the phone actually comes back to life and is recognized by the computer.
I will update you on this! You are a very helpful group of people. I am grateful for your help so far :good:
Sari95 said:
Yea, I read through a few pages of that thread, but didn't feel it covered my case. I had a minimum of 89% of battery and it was charging. Hmm.. about the battery calibration, the day before this happened, I charged my phone to 100% and used Battery calibrator, which is an app in Play Store to calibrate it, so this shouldn't be a problem.. However, I suppose something has happened during the formatting.
I am quite certain one loses warranty when rooted or has unlocked BL.
Indeed, this seems to be my last way out of this. Either it comes back to life in the morning, or I am doomed! haha I have even prepared FLASHTOOL and the firmware, if the phone actually comes back to life and is recognized by the computer.
I will update you on this! You are a very helpful group of people. I am grateful for your help so far :good:
Click to expand...
Click to collapse
Woke up today and tested it. No sign of life at all so it is now sent to the service center..
Thank you for your help! You have helped me a lot
I was going a back up on my phone in twrp and noticed that the time was off. I read that if you reflash twrp(2.6.3.3) that it would fix the issue. I used freegee to do it the first time and it worked fine since I couldn't get any other program to flash twrp successfully. I received a snapchat while freegee was flashing so i checked it out(big mistake in hindsight). I then attempted to go back to freegee but it wasn't listed in recent apps. So I loaded up freegee again and it acted like it was the first time. I attempted to flash twrp again and it finished successfully but when I tried to restart my phone it does nothing. Was the other Freegee running and didn't finish correctly causing this?
If I hold the power button down it will just vibrate in ~15 second intervals
No LG logo, no back light.
No download mode.
No Recovery.
Tried disconnecting battery cable and plugging phone in to reach download mode.
I've tried a few things on other sites like trying to flash via linux but my phone won't show up. It wont' show up when plugged in to my laptop either
Is it a lost cause?Do I just take it back to the store and say the phone died and won't reboot?
Any help would be appreciated.
nostang3 said:
I was going a back up on my phone in twrp and noticed that the time was off. I read that if you reflash twrp(2.6.3.3) that it would fix the issue. I used freegee to do it the first time and it worked fine since I couldn't get any other program to flash twrp successfully. I received a snapchat while freegee was flashing so i checked it out(big mistake in hindsight). I then attempted to go back to freegee but it wasn't listed in recent apps. So I loaded up freegee again and it acted like it was the first time. I attempted to flash twrp again and it finished successfully but when I tried to restart my phone it does nothing. Was the other Freegee running and didn't finish correctly causing this?
If I hold the power button down it will just vibrate in ~15 second intervals
No LG logo, no back light.
No download mode.
No Recovery.
Tried disconnecting battery cable and plugging phone in to reach download mode.
I've tried a few things on other sites like trying to flash via linux but my phone won't show up. It wont' show up when plugged in to my laptop either
Is it a lost cause?Do I just take it back to the store and say the phone died and won't reboot?
Any help would be appreciated.
Click to expand...
Click to collapse
Just to be clear, when plugging the usb cable in you were holding volume up right?
If so, you could try this.
http://forum.xda-developers.com/showthread.php?t=2582142
I think a lot of people are having problems with freegee lately. Flashify is working great, however.
1heffer said:
Just to be clear, when plugging the usb cable in you were holding volume up right?
If so, you could try this.
http://forum.xda-developers.com/showthread.php?t=2582142
I think a lot of people are having problems with freegee lately. Flashify is working great, however.
Click to expand...
Click to collapse
Yeah, I've tried all possible combinations. Vol up with power, volume down with power, hold power for 15 seconds, hold power for 1 minute, hold power for 2 mins. I even took the case off, removed the battery connection and tried the Vol up plus plugging in usb cable.
I tried the linux thing in that thread before posting but it won't recognize my phone to even try it.
nostang3 said:
Yeah, I've tried all possible combinations. Vol up with power, volume down with power, hold power for 15 seconds, hold power for 1 minute, hold power for 2 mins. I even took the case off, removed the battery connection and tried the Vol up plus plugging in usb cable.
I tried the linux thing in that thread before posting but it won't recognize my phone to even try it.
Click to expand...
Click to collapse
Okay, I think this one then.
http://forum.xda-developers.com/showpost.php?p=51810022&postcount=38
It sounds like a similar situation.
1heffer said:
Okay, I think this one then.
http://forum.xda-developers.com/showpost.php?p=51810022&postcount=38
It sounds like a similar situation.
Click to expand...
Click to collapse
It's actually mostly the same process as before, since my phone isn't recognized in linux I can't transfer any files to it. I have been all over the internet and found a lot of threads but all of the require the phone to be recognized by the OS or boot into some mode.
Thanks for looking.
nostang3 said:
It's actually mostly the same process as before, since my phone isn't recognized in linux I can't transfer any files to it. I have been all over the internet and found a lot of threads but all of the require the phone to be recognized by the OS or boot into some mode.
Thanks for looking.
Click to expand...
Click to collapse
Yeah, I think thats what the first part of that post is referencing. If you read posts before that one, he couldn't get his device recognized either.
Hopefully someone else will chime in, this is actually a bit over my head at the moment.
1heffer said:
Yeah, I think thats what the first part of that post is referencing. If you read posts before that one, he couldn't get his device recognized either.
Click to expand...
Click to collapse
Yeah, I followed the steps at work with no dice. I'll try it again at home and see if changes anything.
1heffer said:
Yeah, I think thats what the first part of that post is referencing. If you read posts before that one, he couldn't get his device recognized either.
Hopefully someone else will chime in, this is actually a bit over my head at the moment.
Click to expand...
Click to collapse
Ok, he didn't have gdisk installed. Do you?
Did you get output after ls/dev/sd* ?
1heffer said:
Ok, he didn't have gdisk installed. Do you?
Did you get output after ls/dev/sd* ?
Click to expand...
Click to collapse
I had to Apt-get to get it. Once I got it and listed the devices I only got like 4 listed or something close to this: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
So I attempted the rest with /dev/sda5 but it was giving me errors. I'll attempt it again here after Ubuntu downloads and post the results.
So when I run
~$: ls /dev/sd*
Click to expand...
Click to collapse
I get
/dev/sda /dev/sda2 /dev/sdb1 /dev/sdc1 /dev/sdd1
/dev/sda1 /dev/sdb /dev/sdc /dev/sdd /dev/sde
Click to expand...
Click to collapse
I tried
~$: gdisk -l /dev/sdc
Click to expand...
Click to collapse
but replaced sdc with each variation of the ones above and none of them returned anything like the list in this thread.
nostang3 said:
So when I run
I get
I tried
but replaced sdc with each variation of the ones above and none of them returned anything like the list in this thread.
Click to expand...
Click to collapse
You're definately not getting anything back with more than 1 or 2 partitions. Could be a brick . Maybe if you're lucky you just overlooked some seemingly minute detail. Possibly try a different usb port or different computer.....sorry bud.
There are quite a few "bricked" threads in q&a, and some in dev. Maybe combing through all of that will shed a little light on the subject.
Good luck
1heffer said:
You're definately not getting anything back with more than 1 or 2 partitions. Could be a brick . Maybe if you're lucky you just overlooked some seemingly minute detail. Possibly try a different usb port or different computer.....sorry bud.
There are quite a few "bricked" threads in q&a, and some in dev. Maybe combing through all of that will shed a little light on the subject.
Good luck
Click to expand...
Click to collapse
I searched on this forum and no dice. Since it's not being recognized I'm screwed. I tried doing a different computer with no luck.
nostang3 said:
I searched on this forum and no dice. Since it's not being recognized I'm screwed. I tried doing a different computer with no luck.
Click to expand...
Click to collapse
Had the EXACT same issue, I just got a replacement.
The only different thing, I was messing around with basebands.
NOT a good idea.
hiddenfive said:
Had the EXACT same issue, I just got a replacement.
The only different thing, I was messing around with basebands.
NOT a good idea.
Click to expand...
Click to collapse
I have one being shipped to me as well but I was hoping to somehow get some files off the sd card(if there is one). I have some pictures that mean alot to me.
nostang3 said:
I have one being shipped to me as well but I was hoping to somehow get some files off the sd card(if there is one). I have some pictures that mean alot to me.
Click to expand...
Click to collapse
No backups stored on computer? Didn't backup to google cloud? No cloud backups?
I tried recovering the data for about 6 hours. No dice.
Also, to my knowledge, there is no SD card in the phone, maybe solder points for one but I don't know.
hiddenfive said:
No backups stored on computer? Didn't backup to google cloud? No cloud backups?
I tried recovering the data for about 6 hours. No dice.
Also, to my knowledge, there is no SD card in the phone, maybe solder points for one but I don't know.
Click to expand...
Click to collapse
I had plans to do a cloud backup today, but the error happened. I learned a lot today. Lol. Won't happen again. If it does I'll have a backup.
Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?
suckafoola said:
Hey everyone,
My friend came across an unfortunate problem with his HTC One. This is what happened according to him:
For the past few months the battery life was getting worse and became terrible, but it's been otherwise fine in terms of performance.
He was at work playing some music via aux
The song stopped playing unexpectedly
Figured that it was a problem with YouTube was like wtf, so he closed YouTube and tried reloading.
It wouldn't show anything and nothing worked, left it that way as to not mess it up more.
Then it completely froze and he shut it off
Not it wont turn back on at all.
He said he left it plugged in charging for a while, still nothing. Tried overnight, still nothing.
Says he really wants to get at least his pictures out of his phone.
So, what are some troubleshooting steps he can take, or what can he do?
Click to expand...
Click to collapse
try to boot the phone while shinning a bright light to the light sensor. (this is protection to avoid booting the phone when its in your pocket)
Press and hold Power and Volume down for at least 30 sec
Connect the phone to a Windows computer using the original usb cable (or any other cable already known to work for data transfer) to a USB 2.0 port on your computer, then go to Windows devices manger, is the device detected as QHSUSB ? Or Qualcomm something?
Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?
suckafoola said:
Hi thanks for the reply.
He said that when he plugged into his PC, QHUSB_DLOAD shows up in device manager. So now what?
Click to expand...
Click to collapse
Since the phone went in QHUSB_DLOAD by itself and randomly, this is an hardware failure, the phone will need a new motherboard. It would be fixable only if the phone went in this mode directly after flashing a (incompatible) firmware. Unfortunately there is no way to recover the data from it since the emmc is soldered on that defective board.
Sorry
Wow damn that's real bummer... so there really isn't anything he could do? I remember him telling me that he wanted to salvage pictures from his graduation, but this problem is not letting him
suckafoola said:
so there really isn't anything he could do?
Click to expand...
Click to collapse
Unfortunately no. Another perfect example why you must backup your important files regularly. Smartphones are unreliable for preserving data, they are not made to last very long (well like everything nowadays ).
I already heard of someone desoldering his emmc chip (not from a M7 btw) and soldering it back to other hardware to extract the data so this is not impossible but your friend would have to find someone really qualified to try this kind of thing and it will probably not be cheap if it can be done..... But no there is no conventional method (using your computer and a usb cable) to extract any data from this phone.
@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.
monrokhoury said:
@alray I know it sounds silly, but would it be possibly to save the pics by booting into twrp and copying them to a USB otg?
I'm guessing no
And yeah, it's always a bad idea to keep important files and data on one device.. be it a USB flash drive, an external hdd, a laptop, a smartphone.... etc
there's always the chance of it refusing to work or getting stolen.
Click to expand...
Click to collapse
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...
boleguc said:
What if it says qualcomm something?
Shining a light method doesnt work, i left it charging for 3 days, nothing, i tried connecting it to computer and turning on, but not working...
Click to expand...
Click to collapse
Doesn't matters what it's saying exactly, it's dead. It's only possible to unbrick a m7 that went in a "Qualcomm something" mode because of a bad firmware flash. If it went in that mode itself, without flashing, your phone is dead.
Sent from my HTC One using XDA Labs
alray said:
how are you supposed to go in twrp if the phone is stuck in qhusb_dload (qhusb_dload = phone not even booting in bootloader = dead).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Yeah I expected that lol
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
+cs.tribal said:
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
Click to expand...
Click to collapse
If you have warranty, just go and have your phone dealt with.
My reply sounds not-fun, but, there is a post from someone pointing out that sending his phone to service centre was his solution. It is reported by him that the issue has something to do with the motherboard.
same issue
+cs.tribal said:
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
Click to expand...
Click to collapse
i have same issue, before my mia2 working normaly, but after update v10.0.13 usb optopn grey and disable, before that i can use my usb for debuging my android app etc. now its stuck. i think in update have corrupt file system. its bug in rom update. u have solution or have been fix it?
TechnoSparks said:
If you have warranty, just go and have your phone dealt with.
My reply sounds not-fun, but, there is a post from someone pointing out that sending his phone to service centre was his solution. It is reported by him that the issue has something to do with the motherboard.
Click to expand...
Click to collapse
The warranty is off! So it looks like I'm stuck with this ROM cause, its literally dangerous to try installing something else, in case it gets bricked there will be no way restoring that phone i guess!
xplancer99 said:
i have same issue, before my mia2 working normaly, but after update v10.0.13 usb optopn grey and disable, before that i can use my usb for debuging my android app etc. now its stuck. i think in update have corrupt file system. its bug in rom update. u have solution or have been fix it?
Click to expand...
Click to collapse
Seems like there is no solution! But I bet that something can be possible, but who knows... we need to find out
I have the same problem, but the same thing that you say happened to me, I installed a rom and it gave an error and the cell phone died, it no longer connects in any way or does anything, just turn on in fastboot mode or in recovery mode, but I can't install anything, plus everything was formatted
balther said:
I have the same problem, but the same thing that you say happened to me, I installed a rom and it gave an error and the cell phone died, it no longer connects in any way or does anything, just turn on in fastboot mode or in recovery mode, but I can't install anything, plus everything was formatted
Click to expand...
Click to collapse
Well you ****ed up... The whole thing is ****ed up... Seems like the only way to unbrick it is change the motherboard!!
Btw...there is a new update that im about to install... Who knows, maybe it will fix something....
It is not a hardware issue it is a kernel issue...upon boot a "chargeonlymode" file is created in sbin folder... I am a rookie at this but after a month of digging, 2 mia2's and 4 charger modules later, something is focing our phone into chargeonlymode. If i can find the solution I will post it