Need someone with tons of knowledge here to help me out
I'm currently dealing with a Nexus 6, unrooted, stock.
The phone was dropped and the screen was destroyed. During the drop something internally must have been damaged as the phone starts the At&t music up and resets immediately and will keep looping until the power dies or I put it into the fastboot screen to shut it up, in which the phone stays on that screen. (or at least theres where im assuming its going)
The thing is, my computer recognizes the phone as an android device and shows the android device bootloader on my device manager on my cpu. Every time I try to get into recovery (or at least how I recall doing it without a screen to assist) the phone just restarts to the at&t music once again...
Is there any hope here for retrieving my data on this thing? I figured I could do something with adb although im not too savvy with it. Just assuming since the computer does recognize the device in some way, it is possible hopefully.
Btw I dont think debugging is on atm.
Any help would be super appreciated. Even willing to donate to anyone that may be able to assist me in this.
If and when Mobiletechvideos gets back up and running, they can more than likely save the entire device and if not at least get your data. But unfortunately because of the high demand for their services, they have gone into a temporary work hold until all current orders are complete. Either way, I would try to get ahold of them and see if they can assist or can point you in the right direction.
If it is unrooted with stock recovery and not booting up to android, there will be no easy way to get your data off.
It is possible, though very unreliable and extremely difficult to unlock the bootloader, flash a custom recovery, create an image of the data partition and scan that on a computer with data recovery software, but that really isn't worth doing.
hi ... how r u .... i have this problem too .... broken screen ... screen totally black ..... stock rom no root no recovery ...... debuging not enabled
http://forum.xda-developers.com/showthread.php?t=2786395&nocache=1
this guy said in his thread i can access the phone via computer but i need to enable debugging which i donno how to do with screen totally black
any suggestions is really appreciated
Related
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
TNSM said:
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
Click to expand...
Click to collapse
You may try to pull off the battery for few mins, then with someone's help hold the 3 buttons for download mode and then plug in the battery...
If you can't turn it in download mode there's no way to fix it, except jtag maybe.
Hey guys, I need some help.
My beloved phone got too full the other night and ended up in a coma. Now she..I mean it, wont wake up anymore. I can only get her to open her eyes enough for a couple of blinks, but never really to a conscious state. I'm certainly not willing to let her go and want to keep her from loosing all the good memories we had together... Please help me safe her!...
Enough storytelling...
I've got the Samsung GT-I9252 (Galaxy S4 Active), which is not rooted. Recently I updated to Lollipop which worked fine without any issues.
As I am a usual data horder, I quickly ran out of space (yes, both on the SD card and the internal memory), so that I constantly saw the warning in the status bar that the phone ran out of memory. As I wasn't near a computer I could use for a while to move some files, I continued using it as normal. Because of the lack of memory, the google play store would not install any updates, which was totally fine. However, the Samsung app-store-thing seemed to care a bit less about it and tried to force to download and install what it thought to be "important updates", like for example "text-to-speach" (I haven't even figured out how to use that feature)... Even though there would not be enough space. And I couldn'd really do anything to stop it. The phone started to get slower and I wasn't even able to take pictures anymore (still not around a computer to tranfer data). So the other day I wanted to restart the phone (as I had done a couple of times since the message of lack of space) and it would just not boot up anymore.
It is stuck at the Samsung logo.
My first thought was, well I simply plug it into a computer and transfer some data to make some space and then it would boot up again, but I had to find out that you do not simply plug your phone into a computer and access its data if it refuses to boot...
So I read about the safe mode and tried to find it without any luck (either I'm too stupid to activate it or it got removed). Next I tried to sweep the cache partition, as I managed to get into the recovery boot. It got deleted, but the phone would still not boot.
I definitley want to avoid a factory reset for various reasons!
Then I read about some ways to push/pull data from your phone with a computer, when in recovery mode (with ADB if I recall correctly)... But that's kind of as far as I got.
Now I'm asking for your help and expertise.
Do you think it would be possible to transfer and/or delete some files and if that would solve the problem and lets the phone boot up again; and if yes, how should I approach? Or do you think the cause for the problem lies somewhere completely different?
Thank you so much in advance!
-Nino
Go to Recovery, go to Mount USB storage then connect your phone to your PC. Wait for a few minutes as the drivers will still be installed. Move all your files then try rebooting. I'm not really sure what could be the cause of your problem but if it still doesn't boot up, I've got no clue what other things you could do aside from factory resetting. To be safe, wait for another reply before taking my advise.
Thanks for your reply, VIPNobie!
Well it reminds me that I actually read about it and the problem is that in the recovery boot there is not the option to choose mount usb =/
Don't really understand why.. It would be the easiest solution tho.
Alright, so now I managed to fix it. To be honest, I'm not exactly sure what the problem\solution was. My plan was to connect it with Heimdall and see what I could do through that.. I set the phone in download mode, got the drivers installed and detected the device in heimdall, I ran the command to list the partitons and as soon as that finished, the computer notified me that the device had been disconnected and my phone restarted by itself... tho this time it booted normally as if nothing happened.. so I could back up my data, still need to try to restart the phone, but just wanted to make sure that I got everything backed up.
So even if this might not help others, this thread can be set to solved I guess
Thanks again.
I have the same problem. what did you mean by "I ran the command to list the partitons". Please provide more details.
Donino said:
Hey guys, I need some help.
My beloved phone got too full the other night and ended up in a coma. Now she..I mean it, wont wake up anymore. I can only get her to open her eyes enough for a couple of blinks, but never really to a conscious state. I'm certainly not willing to let her go and want to keep her from loosing all the good memories we had together... Please help me safe her!...
Enough storytelling...
I've got the Samsung GT-I9252 (Galaxy S4 Active), which is not rooted. Recently I updated to Lollipop which worked fine without any issues.
As I am a usual data horder, I quickly ran out of space (yes, both on the SD card and the internal memory), so that I constantly saw the warning in the status bar that the phone ran out of memory. As I wasn't near a computer I could use for a while to move some files, I continued using it as normal. Because of the lack of memory, the google play store would not install any updates, which was totally fine. However, the Samsung app-store-thing seemed to care a bit less about it and tried to force to download and install what it thought to be "important updates", like for example "text-to-speach" (I haven't even figured out how to use that feature)... Even though there would not be enough space. And I couldn'd really do anything to stop it. The phone started to get slower and I wasn't even able to take pictures anymore (still not around a computer to tranfer data). So the other day I wanted to restart the phone (as I had done a couple of times since the message of lack of space) and it would just not boot up anymore.
It is stuck at the Samsung logo.
My first thought was, well I simply plug it into a computer and transfer some data to make some space and then it would boot up again, but I had to find out that you do not simply plug your phone into a computer and access its data if it refuses to boot...
So I read about the safe mode and tried to find it without any luck (either I'm too stupid to activate it or it got removed). Next I tried to sweep the cache partition, as I managed to get into the recovery boot. It got deleted, but the phone would still not boot.
I definitley want to avoid a factory reset for various reasons!
Then I read about some ways to push/pull data from your phone with a computer, when in recovery mode (with ADB if I recall correctly)... But that's kind of as far as I got.
Now I'm asking for your help and expertise.
Do you think it would be possible to transfer and/or delete some files and if that would solve the problem and lets the phone boot up again; and if yes, how should I approach? Or do you think the cause for the problem lies somewhere completely different?
Thank you so much in advance!
-Nino
Click to expand...
Click to collapse
Lacking storage booting is the option you choose. Fixed it?
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.
So I shattered my display and the screen wont turn on but it still vibrates when i get notifications, i was wondering if anyone would know of a way to sort of project the display onto a TV or PC so i can use apps that i installed to backup messages and app data and stuff?
I'm pretty sure if the phone still works you can run it in ADP on your PC and basically click through the phone. Then do whatever you need to do and back it up.
BlueForce64 said:
I'm pretty sure if the phone still works you can run it in ADP on your PC and basically click through the phone. Then do whatever you need to do and back it up.
Click to expand...
Click to collapse
Here's the problem with that:
ADB doesn't work unless you first enable it in developer options. Once you do that, you have to click yes on a confirmation dialog the first time you use it. Both of these processes require a functioning screen.
If you have an unlocked phone with TWRP installed, and you can blindly convince the phone to boot into TWRP (maybe by booting into bootloader and using fastboot reboot-recovery, but I'll have to check and see if that command works when I get home. I think it does.), you'll be able to access the data on your phone by simply plugging it into a computer. If you do not have TWRP installed, and you have no lockscreen set up (no swipe, no password, no pin, no nothing), you might be able to access the data by plugging it into a computer after it boots.
If none of those situations apply, and the data is worth about $100 to you, you might want to look into a screen replacement service. Sometimes you can find little electronics places in malls or shopping centers that will do it, and I'm pretty sure there are businesses that you can mail your phone to and they'll mail it back once the work is completed. A friend of mine even found a service that sent someone to her house to replace her screen then and there.
Thanks, booting into TWRP worked and I was able to get most of the stuff I needed. I completely forgot I could get into it that way.
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.