How to delete Gesture.key - General Paranoid Android Discussion

Hey Guys,
I got a problem with my old HTC Desire. Yesterday I started my device and saw a 5x5 pattern which I can't remember. Then I tried to delete - via ADB - my Gesture.key to get access to the device. But my ADB told me: "no such file or directory found. "
So the desire is still locked and I have no access. The second thing I tried was via recovery, but I got the same results.
Hope you can help me and looking forward for a solution.
-caligula
Gesendet von meinem D5803 mit Tapatalk

So.
What exactly does this have to do with Paranoid Android?

Related

Help! Connecting thru USB, but not able to flash anything

Brand new phone...can't believe i did something wrong only a few hours into it!?
To cut to it, i am not able to run anything on my PC to my Atrix bc the phone is not visible to it via usb sync. It DOES still see it if i needed to transfer files etc, just not so i can flash anything to it off the PC.
And not sure if it has anything to do with it, but it seems like i ran into my problem when i inserted and formatted my SD card. Here's what i did (and i hadn't gotten very far):
I rooted with SuperOneClick, then I installed DG's Adeo ROM and the update.
I was trying to install Gingerbread and was just putting busybox installer on my phone when i went to put my SD card in there from my old phone. i formatted the card and it seemed after i did that i lost connectivity via the USB. It could still access the phone, but everytime i run ATRIX4G_MobileTV_GBTheme.bat it hangs at "daemon started succesfully" . It also hangs if i try to run SuperOneClick again on "waiting for device."
I wasn't sure what to do to get it running right again so i did a full wipe from the settings. Still can't connect
Any help be greatly appreciated. i've literally had this phone 4 hours so sorry if i'm missing something dumb
Try running aRoot (search this forum) and then trying all that.
thanks for that suggestion, gonna try that....just as soon as the damn search function comes back!!
oh the waiting...i am not going to be able to sleep tonight till i get somethin happenin
No need to search, it's only hanging about 3-5 posts down in this section. It's also here:
http://forum.xda-developers.com/showthread.php?t=981866
Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB
Dillsnik said:
Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB
Click to expand...
Click to collapse
Do you have Root Explorer? If so, look in /sbin and see if you have 'adbd' showing
OR
Have you tried installing the ADB interface from the Android SDK? See if your device can be seen? If not see THIS ARTICLE (external link to addictivetips) on setting up ADB.
No, I don't have Root Explorer
I installed SDK and ADB and it does show up, but only when the USB setting is set to "Motorola phone portal." None of the other options it shows up in device mgr.
I am kinda stabbing in the dark at this point...thinking maybe it's a driver issue?
maybe if i uninstall all the drivers and start from scratch i might have some luck? i actually did unistall all the drivers thru device mgr, but they just came right back next time i connected...so maybe i need to delete them entirely?
any suggestions to trouble shoot this greatly appreciated...i know it's probably small potatos but i'm really jammed up here...
Moved as not android development
Have you tried installing the latest drivers again directly from the Motorola Mobility site? You can install Media Link or just the drivers with MotoHelper. For some reason my phone installed all of this, but there were updates available immediately.
The ADB interface should function when USB is set to None.
Sent from my Rooted Atrix using Tapatalk Pro
Yeah i actually did a system restore and reinstalled all the drivers etc.
I can see the phone now in the device mgr under ADB interface when connection is set to "None" for USB
But still hangs when trying to flash basically anything
Do you have or can you pick up a Terminal Emulator in the Market and list the files in /sbin? See if you have adbd...
From $
su
cd /sbin
ls (Lower case L, not 1)
Look through list of files for adbd.
Sent from my Rooted Atrix using Tapatalk Pro
OK, No it's not in there
See this post here: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1 and the cooresponding thread for replacing adbd. There's another post in the thread about changing the permissions so that it doesn't get lost again with a reboot. You might have to purchase Root Explorer since you cannot push anything via ADB over USB.
Sent from my Rooted Atrix using Tapatalk Pro
This seems to be the type of problem i am having, very much thanks for directing me to that other thread.
At this point i have copied ADB to the sbin folder but nothing flashing yet...need to read through that thread more and play with it.
What a PITA so far but thanks so much for the help!
No problem. I hope it works out. If you don't mind, post up and let me know if you get it going and what it took so we can try to help others.
Sent from my Rooted Atrix using Tapatalk Pro

2ndInit_Installer

Found by laidaxin , from w.w.w.591fan.c.o.m
for us that are noobs, what exactly is this?
dingding2012 said:
Found by laidaxin , from w.w.w.591fan.c.o.m
Click to expand...
Click to collapse
Doesn't work for me.
Sent from my MB860 using XDA App
thebluetoothkid said:
for us that are noobs, what exactly is this?
Click to expand...
Click to collapse
Its supposed to be a working recovery for flipside. I can't get it to work however.
Sent from my MB860 using XDA App
I tried and it was a working recovery for my 508.
I installed it.
when reboot, I continued clicking the volumn down button, and the entered.
Sorry for my poor English.
dingding2012 said:
I tried and it was a working recovery for my 508.
I installed it.
when reboot, I continued clicking the volumn down button, and the entered.
Sorry for my poor English.
Click to expand...
Click to collapse
I am able to do all that also, but can't backup and can't install anything. I get error can't mount data/recovery and aborts.
ok... so i'm trying for the 100th time to install this silly thing... and for some reason... when i try to run it... it kicks me out...
i'm not sure what i'm doing wrong...
when i attempt to pause the install process... i get a screen full of if i type adb without an argument...
if someone could gimme a hand with this or tell me what the hell i am doing wrong... i'd appreciate it...
i wanna try to get laidaxin's cm7.2 working on my phone...
i dunno if it matters... but i am attempting to install from a windows xp machine...
Hello!
First, Thanks to all people around this work, specially Laidaxin for good work.
Well, sadly... I also still stuck on install the FlipSide recovery option of the first post... I did all te proccess by eleven times, testing different details that may be not clear for me (as run as administrator, with abd CMD screen closed and opened, if the version of adb never shows me the logs that appears in cmd screenshot... several times I got on the FlipSide the screens talking about su and later 2ndinit script got superuser permissions... but the screens of cmd generated by the script are so fast that was not able to read or check if the 2ndinit script was succesfull or if there something else that may be failing/missed... so by now still no luck)
as a resume, in hope that may help to test from new friends around here:
1) I reflashed my FlipSide to stock with sbf from the other thread tutorial (I use sbfflash in linux and everything works fine, using Power+UParrow in keyboard to enter in bootloader mode my Flipside)... and then I insert my SIM and SD card wiped with only the CM7-Laidaxin.zip file on it, ...complete setup as minimal possible in order to be able to set USB mode to memory access, and turn on usb development in applications menu.
2) Then I ROOT with SuperOneClick version 2.1.1!!! and connect my phone in normal use screen home (NOT bootloader mode!) with UBS debugging turn on and with USB mode set to memory card access (NOT Moto Portal No Media access...), the other methos with Z4root and newer versions of SuperOneClick FAILS for me...
3) I then try to install recovery with Laidaxin installer and procedure, but as I said after some attemps I still not success in get the recovery working, also try diferent ways... removing battery then reboot with VolumeDown pressed, Turn off normal and repeat, turning ON AND AFTER see the Red Moto press the VolDown key short time, later maintained it long, then pressing it several times, etc...
So, I made this resume in order to share info from my side and hope to save some time to other friends that may want to test the CM7 from Laidaxin, than in fact seems like a GREAT work for our Flips... so please if any help to get this fully working and tested will be very gratefull...
Best regards!
Ok... since I still can't get the automated installer working... I would really appreciate if someone could direct me to the forum/website that that installer came from... I would love to try to push it myself... but I'd have to do some reading...
Sent from my MB508 using Tapatalk
rignfool said:
Ok... since I still can't get the automated installer working... I would really appreciate if someone could direct me to the forum/website that that installer came from... I would love to try to push it myself... but I'd have to do some reading...
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
Hi!
Ok, I am not totally sure, but I suspect that this is the original link of this recovery, however, just now I need to go to my work, so, I do not have chance right now to check it, but hope may be usefull.
http://forum.xda-developers.com/showthread.php?t=944543
Best regards!
You should be able to install it like this:
- Extract everything in the "data" folder into a folder called "bootmenu" on your sdcard
- Then use either "adb shell" from a command prompt, or Terminal Emulator on the phone should work:
Code:
su
cp -R /sdcard/bootmenu /data/bootmenu
cd /data/bootmenu
chmod 0755 *
./install.sh
And it should say "Install complate...."
You can also remove the folder(s) if you want:
Code:
rm -R /data/bootmenu
rm -R /sdcard/bootmenu
Then to get into it, reboot the phone and once the notification light turns on, hit volume down
You my friend.... are the ****ing man...
FYI
Use the touchpad to select
Sent from my MB508 using Tapatalk
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
rignfool said:
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
I ran into the same problem but mine also stopped me from installing any other rom to test, run, or otherwise. I'm at a standstill in terms of helping test.
rignfool said:
One thing doesn't work though... it can't unmount system... so I was unable to do a nandroid restore... rather depressing....
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
laidaxin's rom replaces this recovery with one that doesn't quite work perfectly yet...
You should be able to boot back into CM7 and re-run the above commands and it'll work again
That doesn't change anything for me... it still won't unmount system...
I think if I read the output from the script install...
Our recovery installs to system... since Motorola doesn't love us
Sent from my MB508 using Tapatalk
Maybe try "rm -R /system/bootmenu" then install it...
rignfool said:
That doesn't change anything for me... it still won't unmount system...
I think if I read the output from the script install...
Our recovery installs to system... since Motorola doesn't love us
Sent from my MB508 using Tapatalk
Click to expand...
Click to collapse
It does the same for me, which is what's keeping me from trying CM7, as I have no way to restore my current nandroid. The defy installs their recovery to /system as well and I gather that it works as intended, I wonder if it's that we need our own build of CWM. Do we know if whoever built CWM for the defy has their source tweaks available?
Unless you have something irreplacable in your /system or /data... I would just have RSD lite and an sbf ready... and take the plunge...
Because....
When you use CM7... apps2sd moves not only the apk... but also the lib files to the sd card...
As long as you switch the 'network operator' to GSM only (in wireless and networks)... laidaxin's kang runs beautifully... much much faster than stock
Sent from my Filpside using Tapatalk
Link2SD has no problem moving the lib files in our stock rom... I'm no stranger to reflashing with RSD Lite, it's just tedious to get everything set back up JUST right, and this is exactly the kind of thing nandroid is great for.

[Q] Copy files from phone to nexus 4 when boot-looping?

Hello, I bought a Nexus 4 for a few months, and i used a custom kernel,custom recovery,edited some system files and stock 4.2.2 rom.
Today my younger brother got the phone and ota updated to 4.3.... When I tried to turn on the phone, the phone boot-looped.....
I want to flash the new stock 4.3 rom, but I want to backup some important photos and whatsapp messages first...And I can go to the recovery and fastboot mode only....
I googled and found a way called "android adb", is that really can copy files and folders when the phone is boot-looping?If yes, how to do?
Thank you very much.
Flashing a ROM will do nothing to your photos or existing whatsapp messages unless you choose to format the memory.
As to the ADB part, I use this toolkit when required.
Yes, you can use adb commands like "adb pull" to get your files
Has mentioned above you can use the command so the syntax would be:
adb pull /sdcard/Important_file.doc C://Nexus_4_Bak/Important_file.doc
Sent from my Nexus 4 using Tapatalk 4 Beta
All guys thank you very much
I got back my photos
avatartorres said:
All guys thank you very much
I got back my photos
Click to expand...
Click to collapse
How were you able to get your photos?

[Q] Nexus 4 not bootin afer modifying build.prop :(

Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again
If you can enter recovery do a factory reset
Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem
no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok
Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.
Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909

Is there a guide on how to manually install Remix 1.0/1.5 on the Ultratablet?

I think that I need to downgrade but that is not possible directly from the tablet. I found the old Jide page:
https://forum.jide.com/index.php?p=/discussion/633/remix-os-1-5-rom-for-remix-ultratablet-release
...that provides the original Remix 1.5 image along with instructions, but I honestly find that too difficult to follow as I have never manually flashed a system image before. Does anyone know of an easier guide that will help? YouTube only has people flashing Remix onto PC, and there is no dedicated tool for doing this. I've only ever done this on my old Nexus 7 but I used the NRT to automate the process.
Nope! I had inquired about going back after the first round of 2.0 and that is what they sent me also....I find the latest 2.0.xxx version nearly meeting my needs again so am staying on it.
Sent from my SHIELD Tablet using Tapatalk
thelanceleader said:
I think that I need to downgrade but that is not possible directly from the tablet. I found the old Jide page:
https://forum.jide.com/index.php?p=/discussion/633/remix-os-1-5-rom-for-remix-ultratablet-release
...that provides the original Remix 1.5 image along with instructions, but I honestly find that too difficult to follow as I have never manually flashed a system image before. Does anyone know of an easier guide that will help? YouTube only has people flashing Remix onto PC, and there is no dedicated tool for doing this. I've only ever done this on my old Nexus 7 but I used the NRT to automate the process.
Click to expand...
Click to collapse
If you still want to go back it is really easy. I've done it because I wanted to revert from a rooted to stock and it is easy.
*** Before you do anything, copy any data (contacts, sms, email, music etc.) to the external SD card or other media Everything gets erased ***
Make sure you have the correct drivers such as naked drivers etc.
Connect from USB port on your computer to the micro sd port on the tablet
Open a command prompt on the pc (cmd)
Move to where the adb executable is stored
Type ADB devices - This will show whether or not you have everything setup OK
Type ADB Bootloader
Copy each command shown on the Remix isntruction page.
Move to the command prompt screen and paste the copied instructions
Repeat for each of the three instructions and finally type fastboot reboot.
It will take a while to reboot, but you will end up with a completely refreshed tablet and have the most current updates.
anyone have a direct link to the image?? I can't load the old jide forums
found it http://support.jide.com/hc/en-us/articles/219111847-How-to-flash-Remix-OS-1-5-?
SoreGums said:
anyone have a direct link to the image?? I can't load the old jide forums
found it http://support.jide.com/hc/en-us/articles/219111847-How-to-flash-Remix-OS-1-5-?
Click to expand...
Click to collapse
I can upload it to my gdrive if it helps?
Gesendet von meinem LG-D855 mit Tapatalk
lol its been 3 years but I just dug out my ultratablet and i want to make it not completely useless (2. is laggy as hell and I literally can't do anything) by any chance do you still have that rom?
drazini said:
lol its been 3 years but I just dug out my ultratablet and i want to make it not completely useless (2. is laggy as hell and I literally can't do anything) by any chance do you still have that rom?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6QbFTXmsda3SHFpUE9aQmtzOVU/view?usp=drivesdk
Gesendet von meinem Pixel 2 XL mit Tapatalk
tschmid said:
https://drive.google.com/file/d/0B6QbFTXmsda3SHFpUE9aQmtzOVU/view?usp=drivesdk
Gesendet von meinem Pixel 2 XL mit Tapatalk
Click to expand...
Click to collapse
thank you so much

Categories

Resources