Hi, I got Motorola Moto G, original system, no root. I just encrypted my phone, process most probably finished without problems - I stopped watching the phone on around 90%. Then it restarted, boot animation, "enter your password to decrypt the phone", I type it in, green robo shows for 1 second and then black screen (backlighted) :/ After couple hours nothing changes.
If I type wrong password, phone ofc doesn't acccept it. Computer sees device, but I can't access it. When I turn off the phone by pressing POWER for long time, it just resets and goes back to asking for passwod again.
Please help me recover my data...
EDIT
before entering password PC says phone is off, after typing it, PC says it doesn't have drivers (it worked normally before encryption).
EDIT 2
I can enter fast boot, but IDK what next. Recovery mode just ends with "NO COMMAND"
I see that probably all users who got this problem have Motorola Moto G too. Mostly people who use CM and tried to encrypt phone.
I downloaded Android SDK, fastboot.exe tool sees my phone in this state. Not sure if it can be used to do something useful....
adb.exe doesn't see device
Cyanogenmod is very buggy and in perpetual development state, not recommended.
Try this
http://forum.xda-developers.com/showthread.php?t=2542219
scandiun said:
Cyanogenmod is very buggy and in perpetual development state, not recommended.
Try this
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks, but I got stock Android and I don't want to loose my warranty :/
bump
So, I left the phone in black screen step over night. Battery ran out. I tried turning it on/off, entering fast boot mode, but nothing happened, then connected to USB. LED turned on for a while, screen too, showing battery with 0%. But now nothing again. Just black or off, not sure. Can't do literally anything, I tried pressing different keys for minutes and changing USB slot.
EDIT
nevermind, fixed battery problem, Moto G with no power needs normal charger or much longer time on USB
From what I've read, encrypted data on phone is protected by password and some kind of encryption key/file. Reflhasing firmware would cause permanent lose of that key and thus whole encrypted data.
The only solution I guess is copying that key on PC. Copying encrypted data if possible, and decrypting on PC using some tool, as Android is open source, so it shouldn't be a problem to extract it's decryption mechanism and run it on PC.
OR copying key to PC, reflashing phone, copying back key and praying this time system will start.
Related
Hi everyone,
Yesterday I made a Radio update to version 63.18.55.06_6.35.07.08. I made it putting the update.zip (radio rom) file in the SD Card.
All worked fine until the htc hero restarted (after appears the box with the orange arrow). Thereafter the Hero only shows the Hero logo when I turn on.
I tried to init the fastboot pressing home+power and home+back+power buttons (without SD Card and without SIM card) but always the result is the same, the logo appears and nothing happens.
The computer doesn't detects the Hero's USB connection and I can't run adb commands because it raises the "device not found" error.
Someone can help me?
Thanks in advance!
Did you let the screen with the box run its course?
Did the recovery console come back up saying formatting cache?
Have you tryed holding just back+power? ive never heard of using back+home+power
And also, i think your supposed to enter recovery with the sd in.
If that works then in that state is should be found by adb.
But yes, as the poster before me said, it should show the "unpacking" image, and then it should reboot. It should then go straight back into the recovery and the recovery will format the cache. If you tryed to turn it off at any point then, then something is badly mucked up. But it isnt bricked, and probably can be saved. Its only bricked when no logos at all come up on boot. If you managed to get it reconised by adb, you could probs format the cache manualy, though i dont know the command
All the previous steps after the breack are as you say, but after the "unpacking" image, the htc hero restarted and showed the hero logo instead the correct menu.
The problem with the adb is that the computer doesn't recognize the htc hero across usb. When I write the adb command ("adb devices") doesn't displays any device, and I can't run any adb shell for the same reason. How can I run any adb command if the device isn't recognized by the computer?
Have you tryed just taking the battery out, waiting 30 seconds, putting it back in, then booting the phone holding back+power?
And adb is very strange i find... Sometimes it reconises a phone, sometimes it doesnt, for no apparent reason. Have you tryed leaving it on the hero logo for a while then running adb commands?
If he has flashed, wouldnt the USB Debugging setting be reset also, wouldnt this be why he cannot access via adb.
Hi.
I habe exactly the same problem. I have updated radion.
Now ther come only the T-Mobile Logo and that's all.
I can not enter neither Recovery Mode nor fasbtoot does do something.
Any suggestions?
Lado
this problem shud be fixed asap because i think its a threat for all hero modders and owners as our phones get killed at anytime with this process. so guys lets try to find a solution for this problem. cheers
Updated Radio to 63.18.55.06JU_6.35.09.26 and it killed my hero.
first the box with the orange arrow came up and then the whole phone died... now it wont even turn on the screen.
please fix?????????????????
I had the box with the orange arrow yesterday after flashing radio.
The phone isn't dead, I think it's just working.
I kinda paniced also when it happend but I got into recovery eventually.
When you flash a radio it does not actually install that image until your first boot (when you see that phone out the box image).
At this point DO NOT DO ANYTHING WITH THE PHONE just wait and it will install the image and reboot for you. IT CAN TAKE UP TO 10 MINUTES.
If you turn it off or otherwise interrupt this process it can really mess up your phone. however the general rule is so long as you can see the HTC logo when you turn on i.e. it still turns on you can in theory always recover, its just a matter of finding the way that works.
Hi,
I've got Lenovo s650, rooted with a custom rom (MIUI). All was perfect for weeks but few days ago it started randomly going off. Then I noticed that sometimes when I listen to music it crashes (making the music freeze and repeat same note for like 10secs) and shuts down. I thought it could be related to some apps but since I was very busy I didn't do anything about it.
Now today I noticed that my phone suddenly lost network coverage (in area where I always use it). I tried airplane mode on/off but didn't help, so I powered off and thought I will do hard reset when I get back home. However since then the phone is completely dead. Can't get into recovery, if I plug into USB nothing happens, if I take out the battery the red light turns and it goes to "META" mode for few secs (as it's intended to) but I can't download anything into it as I get some DRAM error in Upgrade /flash/ tool.
Funny thing that somehow I was trying all the combinations Volume up/down/both + power and at some point I randomly managed to turn it on so I was gonna make a backup of my stuff but it froze and shut down again. Now nothing works......
Any ideas what happened? :/
Some additional info:
I've got TWRP recovery (however I am unable to re-download it again via flashtool because of DRAM error).
I tried getting into adb but I am not sure if it's possible when the phone is off (tried volume button combinations with battery in and out but nothing).
Also when my phone is with battery and I put it into USB, pc recognizes it as "MTK USB Port", but it keeps disconnecting and reconnecting every 5 seconds. Tried to replace it with adb USB driver but didn't work.
Not having a phone I'll probably give a "Format all" option a shot in flash tool... either gonna brick it forever or fix it..
Edit1: Can't even format due to DRAM error....... :/
Edit2: This is so bizarre... I managed to connect my phone a couple of times in Mediatek preloader mode so the flash tool started flashing the rom, but stopped in a few mins unable to format something because it's protected.
I also managed to turn on the phone a couple of times and tried connecting via adb, but once I grant root permissions, adb shell on my pc cannot find device anymore.
It seems like either a hardware or kernel problem but I know nothing about either of them..
Edit3: I don't know how but I fixed it. Phone seems to be fine for now
Edit4: After 1 hour of working the phone died in exactly the same way.... And so this 6-week old phone will be going to rubbish bin. End of my blog.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
Hi, got a samsung J6 phone with android 8.0, non-rooted and no custom recovery, usb debug is enabled
It just froze when starting an app that always worked before, now there is a blackscreen, buttons doesn't do anything; power included, but the phone seem still on, and as a proof, he's detected by my PC, which won't happen when it's off, on my side at least, i tried to reboot it into recovery via adb, this error popped:
C:\android\platform-tools>adb reboot recovery
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
then i tried to kill the server, and it just hand there doing nothing too now.
C:\android\platform-tools>adb kill-server
_
i can't remove the battery nor i can open the phone without breaking it seem, so what should i do?
@Gess1t
The catch is that you must have root access on your device if you want to perform adb reboot recovery cmd
So basically, my phone is just unusable now? tried to call it with another phone, instantly not available, so well, guess i'll have to wait for the end of the quarantine to send it for repair, still have the warranty i believe . hope they just don't remove my internal data for no reason, cause if they do that my google auth i had there is gone forever.
but wouldn't the phone still work if it was just the screen?
After all the battery still receive power apparently and the phone seem to do be detected by my PC, so it seem it still on? or maybe it's still in that crashing state.
So i was right, it was in a certain freeze mod, after couple day, the battery seem to have emptied, as i knew it would happen, i then plugged it in one of my external fast-charge battery, screen showing battery, i can turn it on, and it seem to run normally, playing high graphic game seem to be just as fine as before. still weird tho, what happened?
So my mom and I have the same phone, a Huawei P Smart 2019 pot-lx1.
The problem
The phone started doing a boot loop anytime you try to turn it on.
It vibrates and shows the Huawei logo like normal, but after the logo the screen turns dark (not off, just dark, the backlight seems to still be on).
Sometimes after this black screen, a 'recharging' icon is visible in red for a brief moment. It's a red circle with a red lightning symbol in the middle.
It does this regardless of whether it's plugged in or not.
I have no idea what this means because as far as I'm aware, the device can function fine without power (see further down below).
After this black screen or flashing the red recharging icon, it just reboots and does the same.
What I tried
The phone refuses to open Erecovery mode (hold volume up and plug in the device). I have confirmed that this method -should- work since I tried it on my own phone of the same model. In the case of my mom's phone it just shows a black screen like normal.
I can get the phone into fastboot, which is great. It tells you to open HiSuite on your computer, which I do, only for HiSuite to tell me "Your device is not supported for system recovery". Furthermore, any commands that could help me return 'Command not allowed', this is returned from the bootloader of the phone and is NOT an OS permissions issue. I've tried stuff like booting into TWRP or wiping userdata this way but it's simply not allowed.
Regarding the battery, I've tried unplugging the phone while it's in fastboot mode. It just stays on like expected and doesn't turn off, so I don't think the battery has no charge.
From what I gather online, the phone has an FRP lock which prevents you from doing anything that could result in the phone getting a reset. FRP can supposedly be disabled, I've tried dc-unlocker but it simply didn't work, presumably the phone is 'too new' because it wasn't in the model list. (I used detection & then the blue nuke option that said Temp FRP unlock or something like that). There are sites that offer FRP unlock passwords which can be used with 'fastboot oem frp-unlock XXX' but I REALLY don't trust these sites and the prices are expensive.
USB debugging is not enabled and I cannot possibly enable it because the phone will never boot, hence I cannot hop into adb and disable FRP that way or do anything else that adb could. I'm essentially stuck.
I also tried some random things like holding volume up + volume down + power during boot. I have also tried countless times to get into erecovery but it simply will never get to that point.
I also tried downloading the phone's firmware and putting all the files where the UPDATE.app is also located in the 'dload' folder on an SD. I also tried putting an 'update.zip' in the root, but this didn't do anything and I think it's pointless unless you can boot into erecovery.
My mom and dad suspect they damaged something related to charging the phone, either the pins or something inside the device by inserting the charger agressively, is that possible at all? It could explain the red charging icon regardless of battery status, but I'm really not sure.
Same problem!
Hi I have the exact same problem with my huawei. Could you able to solve your problem? If so, could you tell me how?
Thank you in advance.