Hello all,
I'm a little desparate with an error that occurred some time ago. My HTC One was updated and suddenly was encrypted.
Factory reset is not working and Recovery option is not working as well.
What I've done so far, after several forum messages:
1. I tried to execute the HTC dev (unlock_code.bin) hint in a way to unlock the bootloader, but with no success at all. I always get the "*** LOCKED ***" (S-ON) option enabled. Then, I saw a lot of messages in foruns regarding the HBOOT version 1.55 that is installed in my device. It seems that with this version, it's not possible to change the configuration to S-OFF.
2. No fastboot commands work, including all the flash writing options. All of them with signature failures. Again in this case it seems to be a issue related to S-ON/S-OFF.
3. I couldn't run the cellphone in USB debugging (after the boot, I'm presented with the infamous: "type password to decrypt storage", which obviously I don't have the password).
4. Runrunner didn't work.
At this very moment my device is a paperweight... Does anybody have another idea about what could be done in this case?
All my problems seem to be focused on my inability to change the option S-ON to S-OFF.
Any help is very appreciated!
Paulo
Hi!, I have a RAZR D3 (XT919). It ships with Android 4.1.2, but I upgraded it to 4.4.2. A few days ago, I dropped it, and the screen shattered, the screen itself it's not broken, I mean, it displays what it needs to, but half of the screen lost the "touch" capabilities, meaning that I can't input my unlock pattern. I've tried everything in order to be able to unlock it (do not ask why I need it to be unlocked, I just NEED it unlocked), I tried through ADB, but, USB debugging is not enabeld (it actually IS enabled, but I can't confirm the debugging access to my pc because it does not show up the window that asks for confirmation, and, even if it did, I would not be able to tap it not because of the broken screen, because I think the touch part that is still working is in range, but because it would not let me tap it in the unlock screen), I tried through flashing a zip file (actually, lot's of them) that in theory disabled the pattern... yet, no luck (I'm aware that I may needed to input a random pattern, it didn't worked), I tried a file manager made for recovery mode, didn't worked either. So, in short terms, I tried tons of things to unlock the damn phone (factory reset is not an option) and nothing works. I just don't know what to do, I will be buying a new one, of course, but I need it unlocked right now. Oh, I also tried with a USB-OTG cable with either the pc keyboard and mouse, the device simply does not support it. So... yeah, I'm pretty much screwed. Don't be afraid to post any complicated solution, just keep in mind, to make it as clear as possible, thanks for caring and I hope somebody would be able to help me!
Do you have twrp installed?
If so, Go to twrp>file manager>data>system and there delete lockscreen.db and reboot
Black_Eyes said:
Do you have twrp installed?
If so, Go to twrp>file manager>data>system and there delete lockscreen.db and reboot
Click to expand...
Click to collapse
Sorry, I'm not sure that I do (most likely not), even if I did, how am I supposed to browse my files? I can't acces my phone through my pc either unless I enable US debugging (literally, it shows no folder neither files... it's like an empty windows folder), thanks for caring anyway
Nikephor said:
Sorry, I'm not sure that I do (most likely not), even if I did, how am I supposed to browse my files? I can't acces my phone through my pc either unless I enable US debugging (literally, it shows no folder neither files... it's like an empty windows folder), thanks for caring anyway
Click to expand...
Click to collapse
That's because phone is Pattern locked.
If there is no lock, you will be able to browse your files
Black_Eyes said:
That's because phone is Pattern locked.
If there is no lock, you will be able to browse your files
Click to expand...
Click to collapse
so... what can I do to unlock it?
what do u mean by unlock?
sim unlock or pattern unlock?
asadnow2k said:
what do u mean by unlock?
sim unlock or pattern unlock?
Click to expand...
Click to collapse
Pattern unlock, now the screen ins completly broken, it still shows the image, but the touchscreen itself does not work at all
i dont have any trick to bypass moto phones for samsung and lg i got
Nevermind guys, thanks for trying to help, but I already bought a new phone (LG F60). It's not that I wasn't gonna buy a new one anyway, but, I wanted to check some stuff on some apps that were on the functional part of the screen, anyway, you said you have some tricks for LG devices, if you know anything to get some tweaking or just for knowledge for any problem that I may encounter in the future, let me know (I don't want to root it yet because I will lose guarantee). With that said, thanks agakn for trying, I hope this is not the only time I'll get to this forum. See ya!
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
Code:
adb devices
adb reboot bootloader
fastboot getvar all
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
Code:
fastboot oem unlock
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
TootyRooty said:
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
Click to expand...
Click to collapse
I have the exact same issue I read some threads and nothing solid has come out of it some say they managed to get root but others say they bricked the phone
Any news on this topic? I too have one i desperately would like to root because it is permanently full and you cant do anything wih it. The Google apps and the apps installed by my service provider take up all the onboard storage space. I downloaded only Whatsapp and Facebook Lite and bam,the phone is completely full and useless as it cant do updates,runs extremely slow and does all sorts of random stuff like restarting on its own etc. driving me utterly insane.
Hello,
Let me tell you my story and perhaps someone will come up with a miracle solution for my problem.
I was trying to flash my device so: I opened developer options and enabled enabled USB debugging.
I though this was enough, but in the middle of the process I got some errors like "Preflash validation failture". So I went back and discovered that I had the fastboot locked and that in order to unlock it I should get a code from Motorola. I got the code, but when I was going to unlock it, I got another error saying that I can't unlock my flash boot since I didn't enable the check "Enable OEM Unlock" and at that moment was when I discovered I was screwed.
Someone said, that I was just a matter of downloading a Stock room, and repeat the process but I have downloaded tons of them and no luck.
At this point, I would try anything just to be able to open my phone in recovery mode because I can't do anything with it is dead,
I have read tons and tons of posts and all off them lead me to the same point, flash through fastboot repeat all the commands, but I have been there almost 100times. I'm about to get crazy.
If someone knows something, I will really appreciate it.
So I got this Sony Xperia X model F5121 from one of my relatives, and I ran into quite a few issues when I tried rooting it. it says Bootloader Unlock Allowed: NO, which would mean that i couldn't get into fastboot mode and unlock my bootloader but here's the very specific and weird part: I can get into fastboot mode, at least I believe so. My phone was carrier locked to Vodafone but I payed a professional to unlock that and now I can use every SIM I want. I looked online and the first XDA page said that unlocking the SIM meant that fastboot mode is unlocked as well. So I tried, I plugged my phone in while holding the volume key, a blue light popped up and it meant I was currently using fastboot mode, but when i try doing anything it says "waiting for devices" and doesnt end up working at all. Am I missing some drivers? Is it just impossible? Could one of you be kind enough to provide the needed files and some instructions for this procedure? i'm asking for a lot, I know but if there's anyone kind enough. I'm running the absolute latest version of Android 8 Sony provides.
EDIT: YEs, used adb shell, I have the ADB drivers, I tried the szuzu install or what the TWRP codename for it is, but everything just stops at "waiting for devices" and I can't do anything.
Since you are not allowed to unlock the bootloader - Bootloader unlock allowed - No, there is no way to unlock it and root it. Sorry.
even if you want to try again, make sure to force install googles drivers
instead of sonys