Related
I would like to set my phone to europe.pool.ntp.org becouse it's default northamerica.pool.ntp.org
How can I edit this file ? When I try to type adb shell to terminal it gives me an error message.
Thanks
Not development related moved to General
At first U must root R phone and then install Root Explorer. After that go to SYSTEM/ETC/
Here u need to edit GPS.CONF file and change NTP Server from northamerica.pool.ntp.org to europe.pool.ntp.org.
I hope that I help U m8.
Get write acces in system folder
I used the post I've quoted down here. After you have gained write acces in the system folder you can edit gps.conf!
octy said:
By default the /system is mounted in read-only mode.
With 'root' access you can change this.
First 'root' your phone with tutorial 'slumpolo' has provided at
the begining of this thread.
Then open a shell on your phone with adb
Code:
adb shell
Grant 'root' access with 'su' command and have a look of memory partitions
Code:
su
mount
In 'mount' command output, identify the partition on which /system was mounted.
In my phone it was '/dev/block/stl6'
Finally you can remount it to get read-write permissions on it.
But before be sure to be outside /system in the shell (by typing 'cd /' for example).
Code:
mount -o remount,rw /dev/block/stl6 /system
Do the modification you want..... BECAREFUL of want you do, you can damage your phone.
Set read-only mode again
Code:
mount -o remount,ro /dev/block/stl6 /system
Sorry I cannot made any snapshot for the moment, I can't use my phone.
Hope it can help you.
Click to expand...
Click to collapse
By the way, for Slovakia I think you can better change to sk.pool.ntp.org
Complete list of European NTP servers:
http://www.pool.ntp.org/zone/europe
Other area's:
http://support.ntp.org/bin/view/Servers/NTPPoolServers
LeoApollo said:
By the way, for Slovakia I think you can better change to sk.pool.ntp.org
Complete list of European NTP servers:
http://www.pool.ntp.org/zone/europe
Other area's:
http://support.ntp.org/bin/view/Servers/NTPPoolServers
Click to expand...
Click to collapse
I see, probably I can use also CZ, HU, AT, DE or SK or EU .. I've red that the best is with more sites.
"After you have gained write acces " How can I gain write access ? I have rooted - but Adb shell doesn't work, did I missed something ? Thaks
nastyba said:
"After you have gained write acces " How can I gain write access ? I have rooted - but Adb shell doesn't work, did I missed something ? Thaks
Click to expand...
Click to collapse
i think yes adb is for the PC. it is part of the android sdk tools.
i did that on my desire (it should be same) but i have problem i edit and save file and now i cant see it
i can see that backup file but how do i restore it?
i tried create new file it wont work i cant see it (it says file created sucessfuly)
aantdesign said:
At first U must root R phone and then install Root Explorer. After that go to SYSTEM/ETC/
Here u need to edit GPS.CONF file and change NTP Server from northamerica.pool.ntp.org to europe.pool.ntp.org.
I hope that I help U m8.
Click to expand...
Click to collapse
U can use adb on Win or linux or qtadb.
Give these commands on adb shell..
su
mount -o remount,rw /dev/block/stl6 /system
exit
exit
adb pull /system/etc/gps.conf
Edit the gps.conf the way u like.
Then mount again in rw mode.
adb push gps.conf /system/etc/gps.conf
adb reboot
Done.
moved
new post @sgs2
nastyba said:
I would like to set my phone to europe.pool.ntp.org becouse it's default northamerica.pool.ntp.org
How can I edit this file ? When I try to type adb shell to terminal it gives me an error message.
Thanks
Not development related moved to General
Click to expand...
Click to collapse
U can use the apo "FasterFix" from market.
arunmcops said:
U can use the apo "FasterFix" from market.
Click to expand...
Click to collapse
Thanks for the tip much easier to change with this application done in seconds
Hi,
My phone was bricked as I tried to replace framework-res.apk with some other file. It was struck in bootloop mode.
Unfortunately, I couldn't find stock ROM of that phone as it is new model. So, I cannot flash stock ROM.
The only way I can see is to replace corrupted framework-res.apk with stock framework-res.apk (I have taken back up).
So, can you tell me what is the best way to access system files of bricked phone on PC.
Your help is much appreciated.
Forgot to mention, my phone model is XOLO B700
Okay m not sure bt I guess u will need adb .. also u need to run adb in root mode so that u can replace the framework-file.. wid command
adb push ...
doctor_droid said:
Okay m not sure bt I guess u will need adb .. also u need to run adb in root mode so that u can replace the framework-file.. wid command
adb push ...
Click to expand...
Click to collapse
THANKS BROTHER..
can u let me know the steps to run adb commands...im new to these things bt learning many things coz of this issue
veerusayz said:
THANKS BROTHER..
can u let me know the steps to run adb commands...im new to these things bt learning many things coz of this issue
Click to expand...
Click to collapse
Check my thread
http://forum.xda-developers.com/showthread.php?t=2266638
Specially practice the adb push command...
Its like adb push "file location on pc" "file location on phone" which in ur case would be system folder I guess
I will keep on looking for stock rom for xolo b700 .. if I found one I will let u know
doctor_droid said:
Check my thread
http://forum.xda-developers.com/showthread.php?t=2266638
Specially practice the adb push command...
Its like adb push "file location on pc" "file location on phone" which in ur case would be system folder I guess
I will keep on looking for stock rom for xolo b700 .. if I found one I will let u know
Click to expand...
Click to collapse
Thanks a lot, waiting for good news
doctor_droid said:
Check my thread
http://forum.xda-developers.com/showthread.php?t=2266638
Specially practice the adb push command...
Its like adb push "file location on pc" "file location on phone" which in ur case would be system folder I guess
I will keep on looking for stock rom for xolo b700 .. if I found one I will let u know
Click to expand...
Click to collapse
Links are not working in ur thrd
veerusayz said:
Links are not working in ur thrd
Click to expand...
Click to collapse
Here
http://www.google.com/url?q=http://...wQFjAA&usg=AFQjCNH8f3wEs-3NrRrF7aAuqNJ8Du_sNA
doctor_droid said:
Here
http://www.google.com/url?q=http://...wQFjAA&usg=AFQjCNH8f3wEs-3NrRrF7aAuqNJ8Du_sNA
Click to expand...
Click to collapse
Thanks boss! I could able to download adb files on my pc.
I've started my phone into recovery mode and connected PC via US cable.
Have executed commands like start server, root I could able to execute.
When I tried below, I'm getting error
adb push <Location of framework-res.apk on my PC> /system/framework/
Pls help. I think I'm close to solution.
veerusayz said:
Thanks boss! I could able to download adb files on my pc.
I've started my phone into recovery mode and connected PC via US cable.
Have executed commands like start server, root I could able to execute.
When I tried below, I'm getting error
adb push <Location of framework-res.apk on my PC> /system/framework/
Pls help. I think I'm close to solution.
Click to expand...
Click to collapse
can you help on this brother?
veerusayz said:
can you help on this brother?
Click to expand...
Click to collapse
It's best to just "cd(change directory)" your way into the adb folder with the file right beside adb.exe,
that should fix the problem, I think.
Oh, can you post the error here. Just what it says, I mean.
It should help.
Jackoz530 said:
It's best to just "cd(change directory)" your way into the adb folder with the file right beside adb.exe,
that should fix the problem, I think.
Oh, can you post the error here. Just what it says, I mean.
It should help.
Click to expand...
Click to collapse
can you give step by step instructions.
I've placed adb folder in D:\ drive
pls provide step by step instructions
veerusayz said:
can you give step by step instructions.
I've placed adb folder in D:\ drive
pls provide step by step instructions
Click to expand...
Click to collapse
getting this error
- exec '/system/bin/sh' failed: Not a directory (20) nRet(-1) -
veerusayz said:
getting this error
- exec '/system/bin/sh' failed: Not a directory (20) nRet(-1) -
Click to expand...
Click to collapse
Judging from this error(and I ain't so sure):
1. Your output folder path(the path leading to the system folder) is wrong.(Correct your path)
2. Remove sh from the path. ADB detected sh as not a folder but another type of file(archive, apk etc...)
You can try to use cd to figure out the path, provided your phone's being detected by your computer now(which I doubt).
Code:
1. cd (E:/ or whatever your cellphone's drive)
2. dir
3. Then cd your way into another folder(choose from those that appear)
Repeat steps 2 and 3
Jackoz530 said:
Judging from this error(and I ain't so sure):
1. Your output folder path(the path leading to the system folder) is wrong.(Correct your path)
2. Remove sh from the path. ADB detected sh as not a folder but another type of file(archive, apk etc...)
You can try to use cd to figure out the path, provided your phone's being detected by your computer now(which I doubt).
Code:
1. cd (E:/ or whatever your cellphone's drive)
2. dir
3. Then cd your way into another folder(choose from those that appear)
Repeat steps 2 and 3
Click to expand...
Click to collapse
Handed over my phone to service center
THIS IS BEST METHOD IF U WANT TO REMOVE UNWANTED SYSTEM APP AND YOUR DEVICE IS UNROOTED...
REQUIREMENT
1. I am doing this in Ubuntu 13.04(64-bits)
2. Adb(If u dont have adb the download my adb attachment)
3. Assuming that u have placed the adb file in home directory...
PROCESS
1. Open the terminal by pressing "Ctrl+t+Alt" buttons together..
2. Now type the following commands--- ./adb root
3. Next Command --- ./adb shell
4. If u can see "[email protected]" Then u r going right...
5. Next Command--- cd system/app
6. This is the directory where all system apps r located..
7. Next Command--- ls
8. it Will list all the system apps.Make a close look at that particular apk that u want to remove.
9. Next Command--- mount -o remount,rw /system
10. Next Command-- rm x.apk
11. x.apk ,x is the name of apk file that u want to remove
12. Next Command - mount -o remount,r /system
13. Reboot your phone and done...
CAUTION !!!!!!!!! IF ANYTHING HAPPENS TO YOUR PHONE THAT IS UNEXPECTED THEN U R RESPONSIBLE FOR IT,,, DO IT ON YOUR RISK!!!!!!!!! IT WORKED ON MY PHONE!!!!!!!!!!
!!!!!!!!!!!!!IF NOT SURE OF THIS METHOD THEN YOU TRY IT ON AN EMULATOR THAT IS UNROOTED ALREADY AND GET SURE OF IT.....
ENJOY OPEN SOURCENESS
your title says
Remove system apps even from your unrooted device without any exploit
Click to expand...
Click to collapse
next you say
THIS IS BEST METHOD IF U WANT TO REMOVE UNWANTED SYSTEM APP AND YOUR DEVICE IS UNROOTED...
Click to expand...
Click to collapse
but now the important thing
THIS MEYHOD WILL WORK IF YOUR DEVICE IS ROOTED
Click to expand...
Click to collapse
means your thread title is misleading, you need a rooted phone to do that as
./adb root
Click to expand...
Click to collapse
will fail as well.
also you need to enable Debugging Mode on your phone first and you need to grant ADB root permissions on an rooted phone as well.
also you can do
./adb remount
Click to expand...
Click to collapse
instead of
mount -o remount,rw /system
Click to expand...
Click to collapse
oh, and you need to make your adb binary executeable with
chmod +x
Click to expand...
Click to collapse
You must be rooted for this method to work...
thxxx.. dude
Evisceration said:
your title says
next you say
but now the important thing
means your thread title is misleading, you need a rooted phone to do that as
will fail as well.
also you need to enable Debugging Mode on your phone first and you need to grant ADB root permissions on an rooted phone as well.
also you can do
instead of
oh, and you need to make your adb binary executeable with
Click to expand...
Click to collapse
now i got it dude
Here's the SE link with my issue.
https://android.stackexchange.com/questions/131577/cannot-remove-rename-move-build-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
XDA Visitor said:
Here's the SE link with my issue.
https://android.stackexchange.com/q...-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
Click to expand...
Click to collapse
Hello,
Since adb works for you. You can try these (One by one)
Code:
adb root
adb remount
adb pull /system/build.prop
Make the required changes which you messed in build.prop
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
Alteratively, you could register for a XDA Account so you could reply to the threads in the forums as well as get expertise help
-Vatsal
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
UsernameNotRecognized said:
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
Click to expand...
Click to collapse
Hello,
You need to get adb root working, Try running it as administrator.
If still doesnt work, then give a try to this
-Vatsal
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
UsernameNotRecognized said:
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
Click to expand...
Click to collapse
Hello,
Well, you edited build.prop and saved that so that would mean you were rooted? Isn't it?
ADB commands work without root. However the /data partition is only accessible by rooted users* and while /system can be read by anyone, it's a read-only partition and root is needed to remount it as writable.
-Vatsal
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
UsernameNotRecognized said:
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
Click to expand...
Click to collapse
Hello,
You may try posting your query here regarding this.
Android Q&A, Help & Troubleshooting or [URL="http://forum.xda-developers.com/showthread.php?t=2259645]General Q&A[/URL]
The experts there maybe able to assist you
-Vatsal
Abstrk_2dx said:
just flash the stock build.prop it will boot up
Click to expand...
Click to collapse
Yeah.... How
Spflasher doesn't work.
I do have a rom, but spflasher does not work.
UsernameNotRecognized said:
I do have a rom, but spflasher does not work.
Click to expand...
Click to collapse
Hello,
Read the post above, You may try asking there in that forum/thread. The experts there may be able to assist you
-Vatsal
I have but no one has replied as of yet.
UsernameNotRecognized said:
I have but no one has replied as of yet.
Click to expand...
Click to collapse
Hello,
I would recommend you waiting and having a bit of patience untill they figure out your problem and reply to it.
Thank you
-Vatsal
- I already rooted my device using supersu but my device won't boot because I changed some files in system framework.
- Have access in adb and there's a su binary
- I tried to copy files to /system/app but it requires permission.
some stock recovery have mount /system
ineedroot69 said:
some stock recovery have mount /system
Click to expand...
Click to collapse
unfortunately I can't boot to recovery..
I tried to adb reboot recovery but it won't go to the recovery ui
You via ADB can run any command as superuser:
Code:
adb devices
adb shell "$(which 'su') -c '<YOUR_SHELL_COMMAND_HERE>'"
jwoegerbauer said:
You via ADB can run any command as superuser:
Code:
adb devices
adb shell "$(which 'su') -c '<YOUR_SHELL_COMMAND_HERE>'"
[
[/QUOTE]
Click to expand...
Click to collapse
Hi, thanks for the reply!
I already tried in shell, su -c 'mount -o remount,rw /system' but still it didn't change into rw
iluvtorock26 said:
unfortunately I can't boot to recovery..
I tried to adb reboot recovery but it won't go to the recovery ui
Click to expand...
Click to collapse
you are rooted?
this is kinda sound stupid but it might work download "fx file explorer" from playstore then give it root permission then access this directory from fx file explorer "System (Root) > System" then while on that folder access upper right options then change to rw
just be careful with fx file explorer... one wrong move and you might accidentally delete whole partition lmao
ineedroot69 said:
you are rooted?
this is kinda sound stupid but it might work download "fx file explorer" from playstore then give it root permission then access this directory from fx file explorer "System (Root) > System" then while on that folder access upper right options then change to rw
Click to expand...
Click to collapse
Yes, I used SuperSU to root my device.
My device hanging in the bootloop so running an app is not possible.
iluvtorock26 said:
Hi, thanks for the reply!
I already tried in shell, su -c 'mount -o remount,rw /system' but still it didn't change into rw
Click to expand...
Click to collapse
Maybe SELinux is enforced, also maybe AVB 1.0 and/or AVB 2.0 is enabled ( AKA bootloader is locked ): both deny to operate on /system partition
jwoegerbauer said:
Maybe SELinux is enforced, also maybe AVB 1.0 and/or AVB 2.0 is enabled ( AKA bootloader is locked ): both deny to operate on /system partition
Click to expand...
Click to collapse
Sorry I'm newbie to rooting the file, so I'm not familiar in SELinux or AVB.
iluvtorock26 said:
Sorry I'm newbie to rooting the file, so I'm not familiar in SELinux or AVB.
Click to expand...
Click to collapse
Then you should familiarize yourself with these Android security mechanisms as soon as possible.
jwoegerbauer said:
Then you should familiarize yourself with these Android security mechanisms as soon as possible.
Click to expand...
Click to collapse
Do you have any idea on how to fix the bootloop?
iluvtorock26 said:
Yes, I used SuperSU to root my device.
My device hanging in the bootloop so running an app is not possible.
Click to expand...
Click to collapse
you should have said that in the beginning that you are on bootloop
ineedroot69 said:
you should have said that in the beginning that you are on bootloop
Click to expand...
Click to collapse
Sorry about that, I just want to fixed it by replacing the correct jar file in the system framework.
iluvtorock26 said:
Do you have any idea on how to fix the bootloop?
Click to expand...
Click to collapse
Start a new thread titled "How to fix bootloop on <YOUR_DEVICES_BRAND / MODEL>"
S
jwoegerbauer said:
Start a new thread titled "How to fix bootloop on <YOUR_DEVICES_BRAND / MODEL>"
Click to expand...
Click to collapse
Sure.. thank you!