hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
the problem was in the file permissions. i had to remove write permissions to the group. (rw-r--r--)
You can fix permissions using adb
Sent from my GT-S5830 using xda premium
the.fuzzy.guy said:
hi,
I still have adb access,
already tried to adb-push of the original build.prop backup back in place, it is actually uploaded, but won't boot anyway.
backup done by build.prop editor, and file pop and push from a linux machine (so no CRLF thing for sure).
attaching snapshot of logcat.txt
... *HELP*
thank you
Click to expand...
Click to collapse
First of all DO NOT WIPE DATA / FACTORY RESET
This will remove adb access. Depending how far you can boot, do you get adb in recovery or normal. Can you use adb shell? If you can you can us adb shell chmod 644 /system/build.prop
EDIT:
Failing that try to install a zip. Sell my links for both current and older zips
Related
Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.
So this is my issue.
I've not got a typical problem with how to edit the apk or what not, but my modified frameworks changes aren't taking effect on the device.
I've used AutoAPKTool to decompile, do my changes then compile and ADB to transfer the apk across to my System/Framework folder, but the changes aren't showing on the device, for instance if I change an image.
This is what I'm using to transfer via ADB,
"su
stop
cp /system/framework/framework-res.apk /system/framework/framework-res.old
cp /storage/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
sync
start"
I've tried doing a normal "adb push" function but each time I get "Permission Denied" dispite having SU privelages and yes I'm rooted. I've google every possible permission problem but no luck.
I'm using the Archos 70, I hope this is the right forum and I appreciate all help.
Regards.
Anyone please?
You have to put your updated image in the _custom_res folder with the correct folder structure.
HTH
Did you mount system as read/write before copying?
Sent from my HTC Glacier using XDA Premium App
Hi,
I'm attempting to replace Email.apk on my miui rom. This is the method I am using:
Code:
adb push Email.apk /sdcard/
adb shell
su
rm /system/app/Email.apk
rm /system/app/Email.odex
mount -o rw,remount /dev/block/mmcblk0p9 /system
cp /sdcard/Email.apk /system/app
reboot
When the phone has rebooted, my changes do not take affect. To check, I pulled the /system/app/Email.apk back, and found it to be the original version.
Can anyone tell me what I'm doing wrong here?
Thanks,
Have figured this out...
adb appears to send some kind of cached version over. Renaming the file before transferring forced adb to use the correct file, and all is well.
jimhaddon said:
Have figured this out...
adb appears to send some kind of cached version over. Renaming the file before transferring forced adb to use the correct file, and all is well.
Click to expand...
Click to collapse
How? I like to know too, guide step by step....thanks
You mean renaming the original file first to any name then copy the moded file with the original name ?
If that what u mean , so I better to delete the original one first then but enstead my moded file . Is that right ?
Sent from my GT-I9100 using XDA App
Just use something like root explorer, no need for adb...
Joey2o11 said:
Just use something like root explorer, no need for adb...
Click to expand...
Click to collapse
I tried to use root explorer to change phone.apk, it didnt work.. i changed the file but it kept on crashing all the time ...
Sent from my GT-I9100 using XDA App
hielo_te said:
I tried to use root explorer to change phone.apk, it didnt work.. i changed the file but it kept on crashing all the time ...
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You'll get lots of FCs until you reboot the phone then it should be fine.
Well I've had my first issue with my shiny new handset! I rooted it this afternoon and decided to modify the build.prop to change the dalvik heap size as recommended by various people. However on rebooting, the phone's now hanging on the splash screen.
I can get into download and recovery ok - any ideas on how to fix this? Is build.prop editable in either of these modes?
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
As said extract the original one from the rom and push it manually via adb push command
Sent from my GT-I9300 using Tapatalk 2
Oddly enough I used the build.prop editor app from the Play store. Seems that the issue was that it didn't put an 'm' at the end of the line specifying the size - so it read as '128'. Anyway, I've done what you suggested, and it worked - excellent stuff, thanks!
Next time, just use Jota Text Editor on your phone
I have use it many times to edit my build.prop file and never have issue
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
guitarplayer365 said:
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
Click to expand...
Click to collapse
Make sure you're not in a readonly directory on the host,
a default cmd in windows will start in the dir of %ComSpec% (Usually C:\windows\system32).
Abd will try to put files wherever you're located in you filesystem, unless you tell it otherwise. (adb pull {source} [destination])
Sent from my GT-I9300 using XDA
T0yK4T said:
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
Click to expand...
Click to collapse
How do I do ADB pull/push if I can only get to the stock recovery screen? (The one with Mr. Android on his back with the ! above him)
BTW, I'm on a Note 3
Check the permissions!!!!!
The build.prop file should have 644 permissions.
Check if it fits, else change them using adb.
See other thread
http://forum.xda-developers.com/showthread.php?t=1927198
Hi,
i accidently changed the permission of the folder "system" to READ only. atleast i think so... i used Yaffs Explorer to change permission of "system" and i ticked the first line on all 3.
again.. this was an accident cuz i didnt know what i was doing.
now the problem is my phone just keeps restarting ... and then it boots into recovery (3e) on its own...
i tried using ADB to change the permission with adb shell ... and all that.. problem is
adb works. phone connects and shows off as device.
but if i try using the adb shell command or any other command with adb ( except sideload ) it tells me
"PERMISSION DENIED" and similar messages...
i have no clue how to safe my phone now any help would be much much appreciated.
i thought something of my own...
is it possible to write a shell script which changes the permission of "system" folder to its correct one.. make it as a .ZIP file and update use it with "update from adb"
please any help^^
best regards
Krype
I assume you are rooted have you gone into CWM and reset permissions?