[Q] Decypt Storage - HTC One SV

I have searched everywhere and no one has had a thread or any forum about this problem I turn on this htc one sv and it stays in air plane mode only emergency calls and the only screen it goes to is decrypt storage shown in the attachment when I unlock bootloader it goes through the motions and reboots and still does the samething reboot to fastboot and at top still says locked

Could you better explain in detail what you did before this problem arised. Include the status of your phone while you were doing whatever it was that you were doing? Also, it is asking for a password. This password is done so by the user. Do you not know your password? If you know your password then you should do away with this decryption. Otherwise, i can only speculate that this device was either taken by someone (stolen) or given to you by someone (which I would contact them for that password).
If this device was stolen then I will not help you.
Sent from my C525c using Tapatalk

walgrenz said:
I have searched everywhere and no one has had a thread or any forum about this problem I turn on this htc one sv and it stays in air plane mode only emergency calls and the only screen it goes to is decrypt storage shown in the attachment when I unlock bootloader it goes through the motions and reboots and still does the samething reboot to fastboot and at top still says locked
Click to expand...
Click to collapse
Thread closed - potentially illicit.

Related

[Q] Entered recovery mode, warning popped up

Hello all, I entered into recovery mode and got this warning today. http://i.imgur.com/CHya85E.jpg
For more info, I updated the other day to 4.1.2 and it removed my root access. Now, I was simply trying to remove the SuperSU app by going into recovery mode (don't know if it can be done there or not). Any help is extremely appreciated.
bootloader is locked. search around for an answer or someone will post it for you. I'm not the best at describing how to do it.
bobAbooE said:
bootloader is locked. search around for an answer or someone will post it for you. I'm not the best at describing how to do it.
Click to expand...
Click to collapse
Okay, thanks. Whenever I reboot my phone, there is text that comes up and says "custom" with an unlocked lock symbol. Could you point me in the right direction with this? Am I not able to go into recovery mode without the bootloader being unlocked?
I have the exact same issue. It came right after I upgraded Recovery to the latest Touch version. I am also on 4.1.2, but have been there a couple of weeks and have had no other problems. I don't believe I lost root with the upgrade.
If the boot loader has been relocked somehow, how can we fix it without being able to boot the phone? All attempts to boot including volume up/home/power, volume down/home/power, and home power just end up with the Verison message. It appears impossible to boot to recovery or even start the phone. I am lost.
See my thread called: “System software not authorized by Verizon Wireless has been found on your phone.” I also could not reboot the phone to fix it.
Some great info was posted there that enabled me to escape from the Verizon prison

[Q] Locked out of Nexus S

A few months ago while I was visiting family my cousin decided to lock me out of my phone by putting in the wrong pattern 30 times. I was then asked to provide my Gmail account and password to unlock it. However, when I input my Gmail account and password it says "Invalid username or password". I wasn't able to do much searching there since their internet was very unstable and rarely worked, so now that I'm back I checked and the Gmail account and password that I entered are correct, it just happens to not work on my phone. My WiFi and data off too, so that could be the reason why it's not verifying it.
When I turn off my phone and turn it back on while pressing the volume up button it does say that it's on fastboot mode and that it's unlocked. Not sure if there's any other information that I can provide that will be helpful. I really want to access my phone again without having to factory reset it since I've a lot of pictures that I haven't saved and I don't want to lose all my contacts again (not sure when I last backed up my phone or if I have ever backed it up).
Try this.
http://forum.xda-developers.com/showthread.php?t=1800799
Thank you for the link. I tried both methods posted on there but it didn't work. when I typed adb shell it would say device not found. I believe my USB debugging is turned off.
If you have a custom recovery then you can try the same commands.
If you have an unlocked bootloader, then flash a custom recovery and give it a go.
Sent from my Nexus S using Tapatalk
I went into bootloader mode and selected recovery.. but that didn't do much. it just showed an android with a red triangle and an exclamation mark inside of it. Then it went back to asking for a gmail account and password.
I'm trying to flash a custom recovery but its still not working. I was using this site for guidance http://forum.xda-developers.com/nexus-s/general/nexus-s-guide-unlock-bootloader-root-t2034264 but in the "early necessary requirements" it says that USB debugging should be enabled.. which it isn't for me.
I tried using all 3 commands but all I get is "waiting for device" and nothing happens after that.

[Q] Locked out phone. Any help will be much appreciated!!

Ok, so this is my first ever forum post and I have resorted to this after hours of searching for a fix.
So let's get straight to the point. After changing my drag password thingy, I forgot it. Numerous attempts later to unlock the password, I found myself on this 'Sign in with your google account' screen of doom.
My phone runs 4.0 ice-cream sandwich.
My problems are:
WiFi is disabled
USB-Debugging is disabled
Things I've already tried:
Factory reset on bootloader - the HTC screen just pops up then it freezes on it.
Recovery on bootloader - the HTC screen just pops up then it freezes on it.
Calling the phone with another phone and trying to drag the notification bar down/ button mashing - nothing happens.
Using ADB to unlock it - I can't because USB-Debugging is disabled.
Various fixes that use WiFi - WiFi is disabled.
Please, please, please help me! My phone has been locked like this for a month now. I've only had the phone for 6 months and I use(d) it very regularly. I will appreciate all the help I can get. Thanks!!
Mr.Stick said:
Ok, so this is my first ever forum post and I have resorted to this after hours of searching for a fix.
So let's get straight to the point. After changing my drag password thingy, I forgot it. Numerous attempts later to unlock the password, I found myself on this 'Sign in with your google account' screen of doom.
My phone runs 4.0 ice-cream sandwich.
My problems are:
WiFi is disabled
USB-Debugging is disabled
Things I've already tried:
Factory reset on bootloader - the HTC screen just pops up then it freezes on it.
Recovery on bootloader - the HTC screen just pops up then it freezes on it.
Calling the phone with another phone and trying to drag the notification bar down/ button mashing - nothing happens.
Using ADB to unlock it - I can't because USB-Debugging is disabled.
Various fixes that use WiFi - WiFi is disabled.
Please, please, please help me! My phone has been locked like this for a month now. I've only had the phone for 6 months and I use(d) it very regularly. I will appreciate all the help I can get. Thanks!!
Click to expand...
Click to collapse
Firstly - this is a QUESTION and should be in the Q&A forum
Secondly - you know that as you have already asked the question in the Q&A forum and someone attempted to help you, so why would you want to open a new thread?
SimonTS said:
Firstly - this is a QUESTION and should be in the Q&A forum
Secondly - you know that as you have already asked the question in the Q&A forum and someone attempted to help you, so why would you want to open a new thread?
Click to expand...
Click to collapse
Haha i thought id seen this post before.. thought i was going mad :sly:
If your boot loader is unlocked you can install 4xt recovery and install another ROM.
Factory reset doesn't help - that's strange but I have never tested it before :laugh:

Galaxy S7 boot loop (unrooted device)

Hi all,
Yesterday I installed an app from the play store and my phone suddenly turned unresponsive (the app was seemingly innocent) and crashed. When I attempted to turn it back on, it would reach the Samsung logo and go no further. I have attempted to fix it using smart switch, kies, odin etc yet it is still in a boot loop. Smart Switch, Kies and Odin all manage to successfully complete flashing the stock ROM but nothing changes. I have also wiped the cache and factory reset the device via the recovery mode, yet the boot loop still occurs.
Also, the boot loop isn't consistent. Sometimes it will only reach the "Samsung galaxy S7 - powered by android" splash screen, the "Samsung" splash screen, the green "installing apps..." splash screen and sometimes when it reaches the "Samsung" splash screen it crashes halfway.
As a side note, I am able to reach recovery and download mode.
Can anyone give me any further suggestions?
Thanks in advance
zelkov said:
Hi all,
Yesterday I installed an app from the play store and my phone suddenly turned unresponsive (the app was seemingly innocent) and crashed. When I attempted to turn it back on, it would reach the Samsung logo and go no further. I have attempted to fix it using smart switch, kies, odin etc yet it is still in a boot loop. Smart Switch, Kies and Odin all manage to successfully complete flashing the stock ROM but nothing changes. I have also wiped the cache and factory reset the device via the recovery mode, yet the boot loop still occurs.
Also, the boot loop isn't consistent. Sometimes it will only reach the "Samsung galaxy S7 - powered by android" splash screen, the "Samsung" splash screen, the green "installing apps..." splash screen and sometimes when it reaches the "Samsung" splash screen it crashes halfway.
As a side note, I am able to reach recovery and download mode.
Can anyone give me any further suggestions?
Thanks in advance
Click to expand...
Click to collapse
Hmm... This is puzzling, have you tried to boot into safe mode and then delete the app.
Here's how to turn on Safe mode:
1. Power the phone off.
2. Once the phone is off and all lights are emitting,
press and hold the “Power” button to turn the S7
back on.
3. When the Galaxy logo appears on the screen,
press and hold the “Volume Down” button.
4. Continue to hold the “Volume Down” button until
the phone completely boots. You will see the
words “Safe Mode” appear in the lower left
corner of the screen if you performed the steps
properly.
Here's how to get out of Safe Mode (if you are lucky and the device boots):
Just powering off and then restarting should get you out of Safe Mode, although some models may require you to hold down the Volume Down key.
Side Note: This probably would not work, although as the phone does not boot even after you flashed stock ROM.
Extra Side Note: Please check that you have not mistakenly flashed the wrong stock ROM as that may also produce the same symptoms.
EXTRA Extra Side Note: Try installing ADB on your laptop using this link:
http://forum.xda-developers.com/showthread.php?t=2317790&page=63
And then running adb devices to see if your device gets recognised, if it does try adb logcat and report back any errors you see to the forums, maybe we can understand something out of it.
By the way, please update this thread on any progress. :good:
Hope you get your device fixed!
Edit: I am curious, what is the name of the app?
Random04 said:
Hmm... This is puzzling, have you tried to boot into safe mode and then delete the app.
Here's how to turn on Safe mode:
1. Power the phone off.
2. Once the phone is off and all lights are emitting,
press and hold the “Power” button to turn the S7
back on.
3. When the Galaxy logo appears on the screen,
press and hold the “Volume Down” button.
4. Continue to hold the “Volume Down” button until
the phone completely boots. You will see the
words “Safe Mode” appear in the lower left
corner of the screen if you performed the steps
properly.
Here's how to get out of Safe Mode (if you are lucky and the device boots):
Just powering off and then restarting should get you out of Safe Mode, although some models may require you to hold down the Volume Down key.
Side Note: This probably would not work, although as the phone does not boot even after you flashed stock ROM.
Extra Side Note: Please check that you have not mistakenly flashed the wrong stock ROM as that may also produce the same symptoms.
EXTRA Extra Side Note: Try installing ADB on your laptop using this link:
http://forum.xda-developers.com/showthread.php?t=2317790&page=63
And then running adb devices to see if your device gets recognised, if it does try adb logcat and report back any errors you see to the forums, maybe we can understand something out of it.
By the way, please update this thread on any progress. :good:
Hope you get your device fixed!
Edit: I am curious, what is the name of the app?
Click to expand...
Click to collapse
Thank you for your suggestions. I managed to get it to boot up by deleting the cache.img file before flashing the ROM. However, I have encountered another issue - firstly, it prompted me for the password used to encrypt the device storage and when I did it did not recognise the password; thankfully default_password worked for this. Now, Google is asking me to enter an email address previously synced to the device, though I can't remember such addresses!
The app is called "Roll the Ball - slide puzzle" created by BitMango.
zelkov said:
Thank you for your suggestions. I managed to get it to boot up by deleting the cache.img file before flashing the ROM. However, I have encountered another issue - firstly, it prompted me for the password used to encrypt the device storage and when I did it did not recognise the password; thankfully default_password worked for this. Now, Google is asking me to enter an email address previously synced to the device, though I can't remember such addresses!
The app is called "Roll the Ball - slide puzzle" created by BitMango.
Click to expand...
Click to collapse
Google is asking for you to enter the Gmail id you signed in to when you set up play store (i.e your gmail account), this is called FRP and is installed on all latest Android devices to prevent someone who is not the owner to factory reset the phone (theft) through the recovery.
Although if you are unable to login due to it being corrupted or some other reason then follow this guide. http://forum.xda-developers.com/galaxy-s7/how-to/bypass-frp-samsung-s7-edge-global-usa-t3405954/
Best of Luck!:good:
Edit: Please read through the thread before you try to follow the guide as the guide does not work on latest Samsung firmwares so you may need to install an older version of the ROM for your phone.
(By the way, if you don't already use it, try Updato instead of Sammobile as it does not have a download speed limit. Link to the Thread: http://forum.xda-developers.com/gal...rgest-online-firmware-archive-t3413785/page18 , also, if this does not work try to use Samfirm, (precedessor to Updato/deprecated) it still (allegedly) works! Link: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/page99
Random04 said:
Google is asking for you to enter the Gmail id you signed in to when you set up play store (i.e your gmail account), this is called FRP and is installed on all latest Android devices to prevent someone who is not the owner to factory reset the phone (theft) through the recovery.
Although if you are unable to login due to it being corrupted or some other reason then follow this guide. http://forum.xda-developers.com/galaxy-s7/how-to/bypass-frp-samsung-s7-edge-global-usa-t3405954/
Best of Luck!:good:
Edit: Please read through the thread before you try to follow the guide as the guide does not work on latest Samsung firmwares so you may need to install an older version of the ROM for your phone.
(By the way, if you don't already use it, try Updato instead of Sammobile as it does not have a download speed limit. Link to the Thread: http://forum.xda-developers.com/gal...rgest-online-firmware-archive-t3413785/page18 , also, if this does not work try to use Samfirm, (precedessor to Updato/deprecated) it still (allegedly) works! Link: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647/page99
Click to expand...
Click to collapse
I managed to bypass the FRP but after factory resetting it I'm back to the beginning. This time, it boots to the lock screen that asks for the password to decrypt the file storage (default_password works for this) and then goes to the green splash screen with rotating gears that says "Android is upgrading... starting app xx of xx" and then crashes and loops.
Thank you for those links! I have been using Sammobile and it is so slow.
zelkov said:
I managed to bypass the FRP but after factory resetting it I'm back to the beginning. This time, it boots to the lock screen that asks for the password to decrypt the file storage (default_password works for this) and then goes to the green splash screen with rotating gears that says "Android is upgrading... starting app xx of xx" and then crashes and loops.
Thank you for those links! I have been using Sammobile and it is so slow.
Click to expand...
Click to collapse
If you can go to the Android is starting splash screen my first post in this thread (the safe mode one) may work. (On second thought, probably not, but still worth a shot)
Also, don't forget to take an adb logcat of your device as detailed in the first post as it may point out what exactly is causing the crash. (look out for recurring errors).
I wish that I could add more to this, but I am honestly running out of ideas.
Edit: Have you tried wiping the cache partition. :fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
If you can go to the Android is starting splash screen my first post in this thread (the safe mode one) may work. (On second thought, probably not, but still worth a shot)
Also, don't forget to take an adb logcat of your device as detailed in the first post as it may point out what exactly is causing the crash. (look out for recurring errors).
I wish that I could add more to this, but I am honestly running out of ideas.
Edit: Have you tried wiping the cache partition. :fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
Cheers for reminding me about safe mode; that made it boot up. I'm confused as to why safe mode made it work however, since I haven't installed any third party apps?
zelkov said:
Cheers for reminding me about safe mode; that made it boot up. I'm confused as to why safe mode made it work however, since I haven't installed any third party apps?
Click to expand...
Click to collapse
Safe Mode disables mostly all background running services, widgets and other non-system/user-installed apps. I think it may have to do with widgets or the pre-installed bloatware/crapware.
Have you tried the adb logcat with your phone when booting up without safe mode? I am asking you to do this as it may point out what exactly is causing this error.
By the way, Safe Mode does not seem to exactly disable user installed apps as I was able to open XDA Forums App on my S7 Edge. (Screenshot attached). :laugh:
Sent from my Samsung SM-G935F using XDA Labs
Random04 said:
Safe Mode disables mostly all background running services, widgets and other non-system/user-installed apps. I think it may have to do with widgets or the pre-installed bloatware/crapware.
Have you tried the adb logcat with your phone when booting up without safe mode? I am asking you to do this as it may point out what exactly is causing this error.
By the way, Safe Mode does not seem to exactly disable user installed apps as I was able to open XDA Forums App on my S7 Edge. (Screenshot attached). :laugh:
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
After booting in safe mode, it then let me boot normally for some reason. I bypassed the FRP lock again and factory restored the device, it seems to be working perfectly now, still a very strange experience. Thanks for your help!
zelkov said:
After booting in safe mode, it then let me boot normally for some reason. I bypassed the FRP lock again and factory restored the device, it seems to be working perfectly now, still a very strange experience. Thanks for your help!
Click to expand...
Click to collapse
It is probably a mystery that nobody should bother with now! Glad that I could help! :victory::victory::good:
Sent from my Samsung SM-G935F using XDA Labs

Locked out of phone, no recovery, usb debugging disabled, not sure of next steps.

Long story short - I thought I had lost my phone so I used Google's ADM to lock my Mi4c, it asked for a password and I entered 8 characters incl. numbers and letters, as I normally would. Anyways found my phone and now it's asking for a 4 digit pin, which I've never set up, I have no idea what the it could be. I've tried all the usuals.
So in the past I've used the tutorials on here to flash my device (thank you very much ), but it seems which ever way I updated it last time, it has relocked the bootloader. I was just re-granted permission (I was surprised to find that the permission expires) to use the miflash unlock tool, which completed successfully (as far as I'm aware). I thought this would allow me to access the recovery but it seems to be gone, no Mi recovery or TWRP! Nothing happens when I hold down the vol up and power button. No trouble accessing the fastboot though.
My questions is, before I go messing trying to fix this device:
Can I flash TWRP without USB debugging enabled? I can't access the settings due to the pin.
What is the best approach to solving this? I was hoping to use TWRP to delete the *.key files and hope that would unlock the device, but honestly I'm not precious about my content anymore I just want my phone back.
cherbe.3 said:
Long story short - I thought I had lost my phone so I used Google's ADM to lock my Mi4c, it asked for a password and I entered 8 characters incl. numbers and letters, as I normally would. Anyways found my phone and now it's asking for a 4 digit pin, which I've never set up, I have no idea what the it could be. I've tried all the usuals.
So in the past I've used the tutorials on here to flash my device (thank you very much ), but it seems which ever way I updated it last time, it has relocked the bootloader. I was just re-granted permission (I was surprised to find that the permission expires) to use the miflash unlock tool, which completed successfully (as far as I'm aware). I thought this would allow me to access the recovery but it seems to be gone, no Mi recovery or TWRP! Nothing happens when I hold down the vol up and power button. No trouble accessing the fastboot though.
My questions is, before I go messing trying to fix this device:
Can I flash TWRP without USB debugging enabled? I can't access the settings due to the pin.
What is the best approach to solving this? I was hoping to use TWRP to delete the *.key files and hope that would unlock the device, but honestly I'm not precious about my content anymore I just want my phone back.
Click to expand...
Click to collapse
Can't you just use android device manager again?
If your phone still boots up to lockscreen and is connected to the internet (mobile or better Wi-Fi) you should be able to access it from your computer or another device...
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Can't you just use android device manager again?
If your phone still boots up to lockscreen and is connected to the internet (mobile or better Wi-Fi) you should be able to access it from your computer or another device...
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Unfortunately not, I've tried changing the pin with ADM but it just tells me that a pin is already is place.
The phone is connected to the internet (both data and wifi), I just can't figure out how to get around it.
cherbe.3 said:
Unfortunately not, I've tried changing the pin with ADM but it just tells me that a pin is already is place.
The phone is connected to the internet (both data and wifi), I just can't figure out how to get around it.
Click to expand...
Click to collapse
If you contact Google support? Maybe they can assist a little or Google some more about the 4 vs 8 digits pin - there's something wrong, sure that the 8 digits aren't your PUK?
Maybe use ADM again, there're more options,
If you reset it via AMD?
Edit:
https://www.ifixit.com/Guide/Android+Device+Manager+-+Bypass+Screen+Lock+on+any+Android+Device/34600
Sorry, just have no time atm but I'll come back later
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
If you contact Google support? Maybe they can assist a little or Google some more about the 4 vs 8 digits pin - there's something wrong, sure that the 8 digits aren't your PUK?
Maybe use ADM again, there're more options,
If you reset it via AMD?
Edit:
https://www.ifixit.com/Guide/Android+Device+Manager+-+Bypass+Screen+Lock+on+any+Android+Device/34600
Sorry, just have no time atm but I'll come back later
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Unfortunately every time I tried to replace the lock pin, Google told me that there was already a pin assign and it wouldn't be replaced.
Anyways, I'm back into my phone! Ended up having to flash the Chinese official rom using fastboot and the MiFlash tool. From there I could enable USB debugging, and flash TWRP and then install a custom global rom. Lost all my content, but a lesson learnt. No complaints, I'm back to being connected to the world!
Thanks for taking the time to help, I really appreciate it

Categories

Resources