Can SOMEONE PLEASE help me? I'm in Recovery RIGHT [email protected] - Droid Incredible Q&A, Help & Troubleshooting

I need to know how to remove apps! I have read some posts and threads but it just says something like
"while in recovery do this:
[email protected]$ adb shell
$ su
# /system/bin/rm /system/app/CityID.apk"
Am I supposed to paste in that whole thing? It keeps telling me "is not recognized as an internal or external command, operable program or batch file"
Where am I supposed to put this?
I finally got into recovery and I have on idea what to do!

Are you rooted?
if you are,
type
su<hit enter key>
/system/bin/rm /system/app/CityID.apk<hit enter key>
Bye bye CityID.

x.v_ said:
Are you rooted?
if you are,
type
su<hit enter key>
/system/bin/rm /system/app/CityID.apk<hit enter key>
Bye bye CityID.
Click to expand...
Click to collapse
It's GONE. THANKS!
can i use that same string for other apps and just change the names of the apps before the .apk?

htc_woe_is_me said:
It's GONE. THANKS!
can i use that same string for other apps and just change the names of the apps before the .apk?
Click to expand...
Click to collapse
I'd hold off for right now if i were you.

johnnybags said:
I'd hold off for right now if i were you.
Click to expand...
Click to collapse
Why? Root works fine, it's compatible with the upcoming NAND unlock, and it's 100% reversible

x.v_ said:
Are you rooted?
if you are,
type
su<hit enter key>
/system/bin/rm /system/app/CityID.apk<hit enter key>
Bye bye CityID.
Click to expand...
Click to collapse
That'll only work if you already had the NAND protection removed. As soon as he reboots CityID.apk will be restored, unfortunately. With NAND still enabled you need to be in recovery to remove apps permanently.
However, will work great once the upcomming NAND Protection Removal process comes out, Thanks unrEVOked.

CaptainTaco said:
That'll only work if you already had the NAND protection removed. As soon as he reboots CityID.apk will be restored, unfortunately. With NAND still enabled you need to be in recovery to remove apps permanently.
However, will work great once the upcomming NAND Protection Removal process comes out, Thanks unrEVOked.
Click to expand...
Click to collapse
He says he's in recovery, so if he is - CityID.apk is gone forever and will definitely not be there after a reboot or a hard reset if he followed the instructions.

seanmcd72 said:
He says he's in recovery, so if he is - CityID.apk is gone forever and will definitely not be there after a reboot or a hard reset if he followed the instructions.
Click to expand...
Click to collapse
Missed the "in recovery" part. I have A.D.D. if you make a title with more than... let's say 2 capitalized words, expect me to read only the caps, as they are more intriguing... So for me this post read "SOMEONE PLEASE, RIGHT [email protected]"
... A.D.D. it makes life more enjoyable!

CaptainTaco said:
Missed the "in recovery" part. I have A.D.D. if you make a title with more than... let's say 2 capitalized words, expect me to read only the caps, as they are more intriguing... So for me this post read "SOMEONE PLEASE, RIGHT [email protected]"
... A.D.D. it makes life more enjoyable!
Click to expand...
Click to collapse
Actually going off of what you said it would have read like;
"CSOMEONE PLEASE RRIGHT [email protected]
It's fascinating that your mind adds proper punctuation when it's seeing only fragments of what you read.

heavensblade23 said:
Why? Root works fine, it's compatible with the upcoming NAND unlock, and it's 100% reversible
Click to expand...
Click to collapse
why? because someone had to explain that he had to press enter after each line of:
[email protected]$ adb shell
$ su
# /system/bin/rm /system/app/CityID.apk"
That's generally a good sign that you shouldn't be telling someone that it's ok to be poking around and deleting things.
That's why.

Honestly77 said:
Actually going off of what you said it would have read like;
"CSOMEONE PLEASE RRIGHT [email protected]
It's fascinating that your mind adds proper punctuation when it's seeing only fragments of what you read.
Click to expand...
Click to collapse
Hahaha. Well you know... how it read... in my head? We'll just go with, my mind reads the pretty and distracting capitalized letters, and adds what it needs to make it make sense... yeah... that's it...

Related

froyo user.conf

Okay so I kind of have a clue about what this is and what it can do but I have no idea about some useful stuff to put into this file. GIVE ME EVERYTHING YOU CAN!!!!!!
hatefuel19 said:
Okay so I kind of have a clue about what this is and what it can do but I have no idea about some useful stuff to put into this file. GIVE ME EVERYTHING YOU CAN!!!!!!
Click to expand...
Click to collapse
What do you mean? It has some configuration settings, and there's a "CustomCommands" section where you can pass your own commands to the system at boot. So some have been using it recently to bind mount a few files to test some hw3d stuff. gralloc changes, etc.
I use this section to delete all of the *.rec files that are created at the root of my SD. The command is pretty straightforward
Code:
rm -f /sdcard/*.rec
Not sure what else you're looking for to be honest...
Whatever else than:
Code:
censored for noobs' safety
... I guess
sad0felix said:
Whatever else than:
... I guess
Click to expand...
Click to collapse
DON'T USE THAT COMMAND!
That's almost as childish as telling someone to put
Code:
:(){ :|:& };:
in their bash terminal... What's the point? Let's not try to take advantage of the noobs too much...
Oh, and don't use that command either If you're curious, see this post on the bash fork bomb
sad0felix said:
Whatever else than:
Code:
rm -f /*
... I guess
Click to expand...
Click to collapse
WOW I DID THIS AND IT MADE MY PHONE 3x FASTER......THANKS A MILLION!!!!
Really I was just looking for useful commands to maybe make boot times faster. I'm actually Linux+ certified for the douchebag I'm quoting but have never messed with android and really dont even know that much about it. If you have any useful commands to run at startup let me know.
and the better way is rm -f-r / so you make sure it gets everything
arrrghhh said:
DON'T USE THAT COMMAND!
Click to expand...
Click to collapse
1) I wrote "whatever else than", not "try this".
2) Only the mighty ultranoob could possibly try something clearly labeled "to be avoided", but I guess this ultranoob wouldn't even locate the conf file, nor bother about it.
3) In any case I evaluated hatefuel skilled enough to survive.
It seems I was right about his skillbase, but also quite wrong about his sense of humor ...
hatefuel19 said:
I'm actually Linux+ certified for the douchebag I'm quoting but have never messed with android and really dont even know that much about it.
Click to expand...
Click to collapse
LOL, yeah, dude, you are the pro ... I am the noob, whatever ...
Yeah, it's normal that every linux+ certified pro/geek starts a thread on this forum asking what to put in a linux bash script file ...
I am the noob here, so I just search/use google.
hatefuel19 said:
rm -f -r / so you make sure it gets everything
Click to expand...
Click to collapse
Oh, how stupid I am, I thought that avoiding do declare recursiveness could save some of your files in case you were worse than ultranoob.
Now, thanks for telling everybody how to properly fsck up their phone.
sad0felix said:
1)
Oh, how stupid I am, I thought that avoiding do declare recursiveness could save some of your files in case you were worse than ultranoob.
Now, thanks for telling everybody how to properly fsck up their phone.
Click to expand...
Click to collapse
Well I don't see how removing the root directory from the sd card could properly fsck up a phone but hey, im the one asking for help here right?
my bad that I came off like a douche i just hate asking for help with some new stuff and getting replies that don't belong. I didnt know if there was any neat stuff that could be done with this file specifically for android. As this post is going nowhere I wouldn't complain if a mod deleted it LMFAO

Prem Root MyTouch 4g 0.86.0000 bootloader!

Alright kids I'll try to make this a simple as possible those of you that are scratching your heads and wondering why you cant get S-on to say OFF..... on the newer MT4G with bootloader 0.86.0000 HERE WE GO.
Step 1:
Download Androzip,Terminal Emulator,Root Explorer and Superuser
Download - Visionary11(yes its an old build, but its simple and less confusing for you noobs.)
Once you have these apps put them on you MT4G homescreen page(doesnt matter in what order just as long as these apps are quickly accessible to you.)
Step 2:
Make sure you go into Settings on your MT4G.
now that you have selected Settings select Applications Make sure that Unknown sources has been selected
On the same Settings screen you will also see Fast boot Make aure to deselect it!
Once the Fast boot has been deselected, select the Development you be transfered to another screen the only items that should be selected is USB debugging. Once you have finished this go back to you home screen.
Step 3:
At this point you should be at the home screen with all the apps you downloaded in Step 1.
Now Select Visionary, once Visionary is open select Set system r/w after root.
Now press Root Now!. let Visionary temproot your MT4G(CAN TAKE UP TO 10-30 SECONDS BE PATIENT!)
Ok that part is Done. go back to your home screen.
Step 4:
Select Terminal and type - su you should see "Terminal Emulator has been granted superuser permission", it will be a real quick pop up saying this. Ok you are now temp rooted. go ahead and select the hardkey arrow and press it until you get to the home screen.
Step 5:
With theMT4G's internet browser find the gfree file on the TRUE PermaRoot and the ULTIMATE S=Off!!! forum
Open the gfree file with Androzip, that you download onto your MT4G NOT with what your computers
unzips this file with!
Step 6:
Once you have Unziped the gfree file from your phone into your phone, you will need to locate and transfer everything that is in the gfree folder DO NOT TRANSFER THE FOLDER ITSELF WITH THE CONTENTS IN IT. Just open the gfree folder and transfer everything inside there. Time to locate where Androzip placed the gfree file
Open Root Explorer scroll down until you see the sdcard file, ok open it!
Scroll down until you see the AndroZip file open it! WALA.... I present to you the extracted gfree scripts. Now that your looking at them, I need you to select the Menu Hardkey Button which is next to your home Hardkey Button. Once you've pressed the Menu hardkey it will options will pop up on your MT4G screen, select Multi-select now select everything inside of the gfree folder.( youll notice the green checks when selecting ) you will also see another option of commands, select move
Now with move selected, navigate those files with the arrow hardkey on your MT4G to /data/local and paste them in that location. Done with that process! close your Root Explorer and return to your home screen.
Step 7:
Open Terminal Emulator and type the following:
type "su", and hit enter
type "cd /data/local" and hit enter.
type "chmod 777 gfree" and hit enter to make the program executable.
type "./gfree -f" and hit enter.
Wait for the program to finish and then reboot into HBoot you'll see that S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked!
You will need to run visionary11 again (w/set system r/w after root checked and then press Root Now!) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
This will work 100 percent if you read these instruction very carefully and follow these steps exactly!
Thats the same instructions from the gfree thread.
How is this different?
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
mine had bootloader 86 and it rooted just fine. People just need to follow the directions better.
easeback said:
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
Click to expand...
Click to collapse
My phone has 86. Bootloader and it took me bout 15 min using gfree method still has 86. Bootloader i didnt do eng but root was easy as pie
Sent from my HTC Glacier using XDA Premium App
He took out the the extra talk and just put it very simple it shouldn't take no more the 5 min to do
easeback said:
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
Click to expand...
Click to collapse
this thread is beyond unnecessary.
i told those guys over n over they were doing it wrong lol. my phone came with .86 also and never had any issues.
Hes just trying to help but, it doesnt matter how many people post this, some of them still don't know how to follow instructions. Thanks for helping the noobs.
Sent from my HTC Glacier using XDA Premium App
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
TeeJay3800 said:
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
Click to expand...
Click to collapse
Version 0.86.0000 is what ur phone comes with u have yhe eng
Sent from my HTC Glacier using XDA Premium App
elry567 said:
Version 0.86.0000 is what ur phone comes with u have yhe eng
Click to expand...
Click to collapse
I have the engineering bootloader? I don't know how that's possible since I never changed it. I just rooted and installed CWM.
TeeJay3800 said:
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
Click to expand...
Click to collapse
You have the eng bootloader. Your better off with it.
Yes, ALL the MT4Gs (at least all the ones I've seen) come with the 0.86.0000 bootloader. There shouldn't be any reason for this preventing you from rooting. The 0.85.2007 is the engineering bootloader. You get this either by manually flashing it (as per the instructions in grankin's true permroot thread) or if you used the root.sh script (such as those of us who followed theunlockr.com's walkthrough).
If you aren't succeeding with the gfree method, either you aren't following instructions properly or something else is interfering. My friend couldn't get VISIONary to temproot, but after uninstalling one of his file explorer apps, all of a sudden VISIONary worked.
Same here. Got mine the 11th of this month and rooted first try no problem.
option94 said:
mine had bootloader 86 and it rooted just fine. People just need to follow the directions better.
Click to expand...
Click to collapse
Sent from my HTC Glacier using Tapatalk
jdkoren said:
You get this either by manually flashing it (as per the instructions in grankin's true permroot thread) or if you used the root.sh script (such as those of us who followed theunlockr.com's walkthrough).
Click to expand...
Click to collapse
The method I used did include running the root.sh script, so that must be how I got the engineering bootloader. Thanks for the info.
TeeJay3800 said:
The method I used did include running the root.sh script, so that must be how I got the engineering bootloader. Thanks for the info.
Click to expand...
Click to collapse
That is correct... The root.sh includes the engineering bootloader within it and it is the better of the 2. I suggest installing it and you will not have any more problems.
SWEET! Thanks! I missed the other 50 threads with these directions!
Just a tip for people having problems rooting using the gfree method. Follow the instructions to the "T" and it works. As for the commands for terminal emulator...copy and paste them to a word document so you can be sure where there are spaces, and make sure that your 0's are not O's and so forth...Don't be afraid to ask for help, there are alot of nice people on this forum that will help you out.
thnx
thanks alot for this, idk why people on xda don't know how to speak in laymans terms, i guess it's to drive the noobies away, i've been around here since cyanogen had 3.0 on the G1, and i shyed away from using the gfree method on my buddies phone since it looked complicated (didn't want to do alot of reading and work) and i was just wanting to do it fast.
this thread simplified things for me so i can know what i'm doing, also i didn't want to download root explorere (dont' wanna pay $4) so i just pushed every file manualy using adb.
"adb push c:/blah data/local"
aalsmadi1 said:
thanks alot for this, idk why people on xda don't know how to speak in laymans terms, i guess it's to drive the noobies away, i've been around here since cyanogen had 3.0 on the G1, and i shyed away from using the gfree method on my buddies phone since it looked complicated (didn't want to do alot of reading and work) and i was just wanting to do it fast.
this thread simplified things for me so i can know what i'm doing, also i didn't want to download root explorere (dont' wanna pay $4) so i just pushed every file manualy using adb.
"adb push c:/blah data/local"
Click to expand...
Click to collapse
ES Filer explorer does what root explorer does as well, but it's free.

New for the Devs: ROOTED system dump here

Major edit:
This is now the rooted system pull, including EVERYTHING that you'll need to dev for this phone. Links are here:
http://d-h.st/2No This link is system.img compressed to a 7z format, expect it to be HUGE (about 1.4gb) when uncompressed.
http://d-h.st/7YC This is the standard system.tar.gz pull.
http://d-h.st/wvp System.tar.gz mirror
If anyone needs another system dump uploaded let me know. Got mine today and am in no hurry to switch over to it so its a test bed.
Thanks for posting. I'm sure this will be of great help to some folks doing research on the device for some flashing goodness!
anyone wanna test TW launcher with wallpaper scrolling
already have it done.
howtomen said:
anyone wanna test TW launcher with wallpaper scrolling
already have it done.
Click to expand...
Click to collapse
You're already on a roll! Good to see some familiar SN's on this side already!
howtomen said:
anyone wanna test TW launcher with wallpaper scrolling
already have it done.
Click to expand...
Click to collapse
wut? lol the launcher doesn't have wallpaper scrolling? wow didn't know that.
HERE IS A JumboFiles MIRROR
Thanks, Neverends. Just edited my first post.
I got a T-mo version today, and would love to provide a dump, but I don't have a clue how. My Odin/adb are all good, I just don't know what the commands are. Anyone want to give me a list so I can have at it?
Janis said:
I got a T-mo version today, and would love to provide a dump, but I don't have a clue how. My Odin/adb are all good, I just don't know what the commands are. Anyone want to give me a list so I can have at it?
Click to expand...
Click to collapse
Adb pull /system and post in tmobile forum
Sent from my HTC Desire HD using xda premium
Janis said:
I got a T-mo version today, and would love to provide a dump, but I don't have a clue how. My Odin/adb are all good, I just don't know what the commands are. Anyone want to give me a list so I can have at it?
Click to expand...
Click to collapse
Make a folder to hold the dump. I did C:/SGS3Dump
Then type adb pull /system C:/SGS3Dump and it takes about 15 minutes to complete
entropism said:
Make a folder to hold the dump. I did C:/SGS3Dump
Then type adb pull /system C:/SGS3Dump and it takes about 15 minutes to complete
Click to expand...
Click to collapse
There is a better way to do this. By doing it the way that you mention windows will add a carriage return to end of every line of the basic files, since Adnroid is linux at it's base, that is not a good thing.
The better way to grab a system image is like this:
adb shell
cat /dev/block/system > /sdcard/system.img
This can be mounted like an iso on any OS.
I'll do this now. Thanks for the tip!
Edit: Says no such file or directory. odd
jimbridgman said:
There is a better way to do this. By doing it the way that you mention windows will add a carriage return to end of every line of the basic files, since Adnroid is linux at it's base, that is not a good thing.
The better way to grab a system image is like this:
adb shell
cat /dev/block/system > /sdcard/system.img
This can be mounted like an iso on any OS.
Click to expand...
Click to collapse
no root so it cant be done....
howtomen said:
no root so it cant be done....
Click to expand...
Click to collapse
Yes that is true, but still a better way for a true image. The other way, will miss any files that are not readable by "other" on the filesystem, so that can be an issue, as well.
As soon as we get root, I'll post up a proper system dump. I just need to know how to get access to the boot.img, so we can get root.
entropism said:
I'll do this now. Thanks for the tip!
Edit: Says no such file or directory. odd
Click to expand...
Click to collapse
You may have to figure out where the device for /system is at in /dev it may be something like /dev/block/mmcblk0p(1-26). Those last numbers in the parenthesis are the partition number for /system, that will be what you will need to find in /dev/block, and it will be a number between 1 and 25 usually.
You will need root to this, just like howtomen mentioned. For now how you mentioned will just sort of do the job. It would be best to do it from cygwin rather than from the windows command line though, as cygwin should NOT add the carriage returns.
OK well... I have a linux machine I can use, but I never used ADB on it. if someone wants to walk me through it, I'll do a system dump on linux. If not, well, not much I can do...
Would love to look at the dump, but that mirror ain't working well for me.
Sent from my SGH-I997 using xda premium
Me neither... I'm posting up my dropbox again.
http://dl.dropbox.com/u/6421623/ATTSGS3 System Dump.7z

[manta][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Nexus 10 (manta)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
Flashing can brick your phone
This will be removed after people report it is booting fine without bricking their phone
Click to expand...
Click to collapse
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
espionage724 said:
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
Click to expand...
Click to collapse
I warn people when I release an untested recovery on a given device
Most noobs tend to forget that flashing is not a safe operation. It can always turn into a nightmare
You can check the list of currently supported devices from main thread here: http://forum.xda-developers.com/showthread.php?t=2201860
And browse into the different device support forums
Till now, the warning never became true except when some people flashed the wrong file in their phone
This warning should keep noobs away from testing it
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
espionage724 said:
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
Click to expand...
Click to collapse
LoL
It is a generic copy paste message
Well, will you be the first to give a feedback ?
Phil3759 said:
Well, will you be the first to give a feedback ?
Click to expand...
Click to collapse
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
espionage724 said:
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
Click to expand...
Click to collapse
Thank you for the feedback (reached my daily limit for :good
Brightness:
Do you by case know the path for your device brightness file?
Not a big deal though as I can search / look for it in rc files. I used Samsung usual path, but it seems they used a different one for google devices
Battery:
Will check for the battery path used
Touch
It is supposed to be one finger to use
Interesting though...
Can any one run this in adb shell while in recovery
Or you can use the console terminal in aroma file manager while in recovery
Code:
find /sys/. -name '*bright*' >/sdcard/brightness.txt
Then
Code:
find /sys/. -name '*battery*' >/sdcard/battery.txt
And attach the resulting brightness.txt and battery.txt files on sdcard
About multi touch: i will look to allow only slot 0 to ignore second finger
Sent from my GT-I9100 using Tapatalk 2
Forget it. I found path in source
Sent from my GT-I9100 using Tapatalk 2
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/. -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Click to expand...
Click to collapse
see attached - is this what you're looking for?
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
Sorry I'm a bit out of sync with you -- but I've attached the one you asked for just before revising your post.
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
Result is attached. I'll run the other command in a moment.
Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
OK -- re-learning linux command line as I go (it's been many years!). Good to wake up that part of the brain again...
Had to modify command above: needed a space between ls and -l, and I'm assuming you want "/sys" up front in the fully qualified file name... Assuming that's all good, the new result is attached as battery2.txt
Let me know if this is what you need, or if anything else is needed. I've got some time to squeeze in a few of these today as needed. Also REALLY looking forward to trying this out on my N10 (and would love to see this on the Galaxy Nexus if ever possible!).
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Phil3759 said:
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Click to expand...
Click to collapse
Try the attached...
jonstrong said:
Try the attached...
Click to expand...
Click to collapse
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Phil3759 said:
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Click to expand...
Click to collapse
Great -- let me know if you need anything else -- I'm home today, and can pull some more if needed.
Does this recovery support USB OTG?
I must be in stupid mode today !!
Have been running Galaxy S3 with PhilZ Touch for some time now .... superb :good:
Got a new Nexus 10 last week and want it on there as well ..... stupid bit coming now
Downloaded latest version from this thread - but it shows as "philz_touch_5.00.7-manta.img"
Not a zip or a tar file for Odin ..... what am I missing from under my nose?
Homer

Forgot Your Password? Here's A [GUIDE] To Remove Password Without Data Loss. [ROOT]

Sometimes Password lags or something and you will not be able to use your phone, here's a ROOT-ONLY method.
Are you a veteran? Here's a short guide. (in "/data/system" delete locksettings.db, locksettings.db.shm, locksettings.db.wal)
Not a veteran? (Don't know a lot about phone stuff)
Read this guide.
Code:
Alert, do NOT delete any file from system to "free up space", this will kill your device. I'm not responsible if you do something -outside this guide- that might damage your phone, read carefully and good luck!
REQUIREMENTS:
-You will need a recovery that can delete files (has a 'file manager' feature), Recommend: TWRP Recovery
GUIDE:
Step 1: Reboot to recovery mode,
This can be done -on the galaxy a10- by turning your phone off and long-clicking volume up button THEN power button (at the same time), but it might ask for password while turning it off, so we need to reboot it manually.
While the phone is on... long click power and volume down for 7.5 seconds, it will turn off. Immediately when it turns off you need to keep clicking power but click volume up instead of down, when the phone boots it will get in the recovery mode, for sure.
Step 2: Locate the password file
The password file is the file your phone stores your pin/pattern/password at. it is called 'locksettings.db'
We need to delete it -and all it's "variants"- from your device.
In twrp... choose 'ADVANCED'.
choose 'FILE MANAGER' after that.
it will show you the files on your phone. If you look at the top file (the highest one) it will be called (up a level), click it again and again until it disappears. If you don't see that file that means you are at the deepest folder (ROOT).
choose "data" folder
choose "system" folder
Scroll down until you find "locksettings.db" tap it and click DELETE.
Do the same for "locksettings.db.shm" and "locksettings.db.wal" (delete them too)
Step 3: Rebooting into the os
To turn your phone on again click the back button and return to the home screen.
Click "REBOOT"
Click "SYSTEM"
That's all now the password is removed.
Tested on Samsung Galaxy A10
Need more help? Contact me on my telegram, https://t.me/BrudherBoard
"-You will need a recovery that can delete file"
You can't install a custom recovery without Usb Debugging and OEM unlocking.
What's the point of the tutorial ?
gsmer87 said:
"-You will need a recovery that can delete file"
You can't install a custom recovery without Usb Debugging and OEM unlocking.
What's the point of the tutorial ?
Click to expand...
Click to collapse
well you can see [ROOT] at the end of the title, so
rooting your phone means unlocking bl, so [ROOT] means your bootloader is unlocked and you have a custom recovery that can install zips such as magisk so you can grant root access to apps.
now tell me what's the point of your message?
BrotherBoard said:
well you can see [ROOT] at the end of the title, so
rooting your phone means unlocking bl, so [ROOT] means your bootloader is unlocked and you have a custom recovery that can install zips such as magisk so you can grant root access to apps.
now tell me what's the point of your message?
Click to expand...
Click to collapse
The point of my message is that your tutorial is useless. You can't root your phone without data loss and putting the [ROOT] in your [GUIDE] doesn't make it less useless.
PLEASE prove me wrong ! I wold realy like to be wrong about this .
Total useless nowadays
Now all device's have FRP & KG enable
And with this you can't flash any custom image
gsmer87 said:
The point of my message is that your tutorial is useless.
Click to expand...
Click to collapse
Mr Hassan said:
Total useless nowadays
Click to expand...
Click to collapse
I have to disagree a bit with these statements. It's not entirely useless but the demographic this targets is very limited.
For this tutorial to work you have to
1) Have your phone rooted with a custom recovery
2) Have your data unencrypted by going out of your way to keep it unencrypted
Not everyone meets these 2 criteria but for those who do, this is somewhat helpful so that you know which files exactly are responsible for your lock method in lockscreen.
I'd probably add those 2 as perquisites so that you don't get bombarded with noobs asking why they can't access their data partition even if they have a custom recovery.
ShaDisNX255 said:
I have to disagree a bit with these statements. It's not entirely useless but the demographic this targets is very limited.
For this tutorial to work you have to
1) Have your phone rooted with a custom recovery
2) Have your data unencrypted by going out of your way to keep it unencrypted
Not everyone meets these 2 criteria but for those who do, this is somewhat helpful so that you know which files exactly are responsible for your lock method in lockscreen.
I'd probably add those 2 as perquisites so that you don't get bombarded with noobs asking why they can't access their data partition even if they have a custom recovery.
Click to expand...
Click to collapse
i've literally put a [ROOT] at the title
gsmer87 said:
The point of my message is that your tutorial is useless. You can't root your phone without data loss and putting the [ROOT] in your [GUIDE] doesn't make it less useless.
PLEASE prove me wrong ! I wold realy like to be wrong about this .
Click to expand...
Click to collapse
in new phones that are not rooted, there is no way to remove lock screen without data loss, sir imagine locking your house up with the key inside, how would you get in?
BrotherBoard said:
in new phones that are not rooted, there is no way to remove lock screen without data loss, sir imagine locking your house up with the key inside, how would you get in?
Click to expand...
Click to collapse
There are so many ways to get into a house without a key; you can't even imagine.
Wait.. Is the house rooted? :]
Timmmmaaahh! said:
There are so many ways to get into a house without a key; you can't even imagine.
Wait.. Is the house rooted? :]
Click to expand...
Click to collapse
maybe but I'm talking about not being able to use your phone, not breaking in a house :]
BrotherBoard said:
maybe but I'm talking about not being able to use your phone, not breaking in a house :]
Click to expand...
Click to collapse
Hey, you started the house analogy. And it was over 2 months ago, you're too late for a retort
Timmmmaaahh! said:
Hey, you started the house analogy. And it was over 2 months ago, you're too late for a retort
Click to expand...
Click to collapse
ok bro no hate, you have replied to a thread that I was just bored and like why not to write that up on xda and I have put a [ROOT] in the title, I see I have made no mistakes at this.
BrotherBoard said:
Sometimes Password lags or something and you will not be able to use your phone, here's a ROOT-ONLY method.
Are you a veteran? Here's a short guide. (in "/data/system" delete locksettings.db, locksettings.db.shm, locksettings.db.wal)
Not a veteran? (Don't know a lot about phone stuff)
Read this guide.
Code:
Alert, do NOT delete any file from system to "free up space", this will kill your device. I'm not responsible if you do something -outside this guide- that might damage your phone, read carefully and good luck!
REQUIREMENTS:
-You will need a recovery that can delete files (has a 'file manager' feature), Recommend: TWRP Recovery
GUIDE:
Step 1: Reboot to recovery mode,
This can be done -on the galaxy a10- by turning your phone off and long-clicking volume up button THEN power button (at the same time), but it might ask for password while turning it off, so we need to reboot it manually.
While the phone is on... long click power and volume down for 7.5 seconds, it will turn off. Immediately when it turns off you need to keep clicking power but click volume up instead of down, when the phone boots it will get in the recovery mode, for sure.
Step 2: Locate the password file
The password file is the file your phone stores your pin/pattern/password at. it is called 'locksettings.db'
We need to delete it -and all it's "variants"- from your device.
In twrp... choose 'ADVANCED'.
choose 'FILE MANAGER' after that.
it will show you the files on your phone. If you look at the top file (the highest one) it will be called (up a level), click it again and again until it disappears. If you don't see that file that means you are at the deepest folder (ROOT).
choose "data" folder
choose "system" folder
Scroll down until you find "locksettings.db" tap it and click DELETE.
Do the same for "locksettings.db.shm" and "locksettings.db.wal" (delete them too)
Step 3: Rebooting into the os
To turn your phone on again click the back button and return to the home screen.
Click "REBOOT"
Click "SYSTEM"
That's all now the password is removed.
Tested on Samsung Galaxy A10
Need more help? Contact me on my telegram, https://t.me/BrudherBoard
Click to expand...
Click to collapse
Was useful for me bro
SsamsungA10 said:
Was useful for me bro
Click to expand...
Click to collapse
are you Samsung A10 from telegram
...was also helpful for me. Thank you!

Categories

Resources