Hi,
I am having a serious problem where my G1 seems to halt while flashing /any/ rom and restoring my backup.
I am currently in recovery mode and I can issue ADB commands.
What do I do?
*Can't issue logcat
C:\Users\Rick>adb root
adbd is already running as root
C:\Users\Rick>adb logcat
/sbin/sh: exec: line 1: logcat: Permission denied
Click to expand...
Click to collapse
It has started to give me an error now,
Failure at line 344
copy_dir PACKAGE:data DATA
While flashing 2.1-v1.5
Ok, now I get this while booting
http://pastebin.com/deb9260d
then crash, and it does it again.(loop)
Unrooted and rerooted working fine delete me
Related
I've had an Incredible since launch that had a defective optical trackpad. Long story short, due to Verizon's terrible customer service I did not get my replacement until yesterday. I rooted my original Incredible without problem and backed up everything with Titanium thinking it would be an easy transition over to my replacement phone.
For some reason I am not able to get Superuser to install. Everything goes fine during the root process until I get to this step:
ln -s /system/bin/su /system/xbin/su
I get the following error:
ln: /system/xbin/su: File exists
The root instructions say to run the following command in the event of an error:
rm /system/xbin/su
At this point I get the error:
rm: cannot remove '/system/xbin/su': Permission denied
Obviously running the final command: 'chmod 06755 su' won't work and I just receive a 'Operation not permitted' error.
I've reset to factory settings 3 times with the same result every time I root. I end up with the Superuser icon in my app drawer, but root apps will obviously not work correctly as Superuser was not installed correctly with the correct permissions. If I only do the first 2 lines of the rooting process:
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su
then reboot, certain apps such as Root Explorer will work, but anything that requires Superuser obviously will not.
Please, for the love of god someone give me some help. I'm so frustrated.
I had the same problem...you will want to follow the official rooting guide, as they have built the superuser into the payloadupdate.zip. Start over following the Unrevoked team: Incredible Root process (sorry, my profile is too new to post links) and you will be good to go.
You were right. I ran the Payload update from recovery, then rebooted without doing anything on the command line. Superuser was in my app drawer on reboot, and I was able to restore with Titanium backup. Thanks for the help!
I was also getting this error. This thread helped me solve my problem. Thanks.
Sent from my ADR6300 using XDA App
Fuzzy_Dunlop said:
I've had an Incredible since launch that had a defective optical trackpad. Long story short, due to Verizon's terrible customer service I did not get my replacement until yesterday. I rooted my original Incredible without problem and backed up everything with Titanium thinking it would be an easy transition over to my replacement phone.
For some reason I am not able to get Superuser to install. Everything goes fine during the root process until I get to this step:
ln -s /system/bin/su /system/xbin/su
I get the following error:
ln: /system/xbin/su: File exists
The root instructions say to run the following command in the event of an error:
rm /system/xbin/su
At this point I get the error:
rm: cannot remove '/system/xbin/su': Permission denied
Obviously running the final command: 'chmod 06755 su' won't work and I just receive a 'Operation not permitted' error.
I've reset to factory settings 3 times with the same result every time I root. I end up with the Superuser icon in my app drawer, but root apps will obviously not work correctly as Superuser was not installed correctly with the correct permissions. If I only do the first 2 lines of the rooting process:
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su
then reboot, certain apps such as Root Explorer will work, but anything that requires Superuser obviously will not.
Please, for the love of god someone give me some help. I'm so frustrated.
Click to expand...
Click to collapse
I got the su file from below link
http://rapidshare.com/files/422997479/HTC_Magic_Recovery_and_su.zip
but still no result
I had rooted my fascinate and everything was working fine until few days ago.
Now, when I do adb shell and run 'su', I got "permission denied".
If I logcat at the same time, I would see
Code:
E/su (31300): Couldn't open database
W/su (31300): request rejected (2000->0 /system/bin/sh)
and of cause, none of the applications that require root can be started now.
I also tried to re-do the root process, and again 'no permission' error when trying to execute rage.bin.
Anybody can help?
Thanks,
Hello all
was following the newly posted easy way to root xoom with rootboot.img
everything was going find until i tried the adb remount command
it replied with the error "remount failed operation not permitted"
can anybody help me with this please? xoom is running fine but im stuck not being able to copy the su files and finish the process
thank you
Alright, ive used Dorimanx ROM's before and never had a problem. But now i cant install any apk using file explorer or adb install. I didnt change anything. Any help is greatly appreciated. I did post in his ROM Thread but i kinda need my phone...
What happens when i try to install an APK is my phone randomly reboots back to the bootanimation and then boots again. I even wiped every partition and tried again..
Anyone??? here is a snippit from my logcat stating the error, dont know why i get this error works perfectly fine on any other ROM...
Code:
E/PackageManager( 1487): Couldn't create temp file for downloaded package file.
E/AndroidRuntime( 1487): *** FATAL EXCEPTION IN SYSTEM PROCESS: PackageManager
Here is the full logcat i really want this ROM again im on CLK if that has anything to do with it. Ive ran it perfectly fine on MAGLDR a long time ago but now it just dont wanna work grrrrrr
Mehhh i fixed it, it was because i didnt have a sd-ext partition on my SD card and according to google, the /data/app /data/app-private directories were symlinked to /sd-ext which didnt exist therefore could not be created causing a loop. So i used adb shell to do the following commands
rm -r /data/app /data/app-private
mkdir /data/app /data/app-private
and it worked .. im gonna check the updater-script for the symlinks.
This question originally got posted on the relevant thread in the Android dev forum, but didn't get any replies so am trying it here in hope....I'm looking for advice on what I can try next which would be safe to try.
I installed and ran the Google Nexus 7 TOOLKIT V4.0.0, but the root failed (and I was also unable to backup the ROM, probably because the root failed). I did the following using the toolkit:
- unlocked the bootloader
- tried rooting using the SuperSU Method (I'm running build JOP40D on a brand new tablet
- got the "downloading boot.img" message (OK), and it rebooted
- did the Android setup after the reboot
- selected USB debugging mode - the tablet rebooted.
During the above process I noticed the message "remount failed: operation not permitted" amongst a stream of other messages.
The subsequent install of BusyBox also failed, with the following messages amongst others:
Code:
Setting permissions..
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Supervisor.apk: No such file or directory"
...
Testing busybox has been installed properly
...
/system/bin/sh: su: not found
Sending the command 'ls -l /system/xbin/' to device..
You should see a list of all busybox commands
/system/bin/sh: su: not found
Completed
How can I establish what the current state of my machine is, and what is the safest next step in my attempts to root it?
unlocked the bootloader? then all you have to do is fastboot flash a custom recovery then flash the su binaries or a custom rom then reboot. btw, dont use root toolkits, especially if your not familiar with basic procedures. nexus devices dont need root toolkits, its just as easy to root your device the right way.
simms22 said:
unlocked the bootloader? then all you have to do is fastboot flash a custom recovery then flash the su binaries or a custom rom then reboot. btw, dont use root toolkits, especially if your not familiar with basic procedures. nexus devices dont need root toolkits, its just as easy to root your device the right way.
Click to expand...
Click to collapse
Well, I think the Unlock Bootloader part worked. How could I check if it was successful?
itm said:
Well, I think the Unlock Bootloader part worked. How could I check if it was successful?
Click to expand...
Click to collapse
It seems that my attempt to unlock the bootloader wasn't successful - when I re-tried the Root option from the toolkit I got a message saying that the bootloader was locked.
So....I tried to unlock the bootloader again (with the tablet in Fastboot mode). I got the Yes/No option on tablet and selected Yes. I saw red text at the bottom of the Fastboot screen saying "Lock state - unlocked". So I then selected the option to Root (option 2, using the Chainfire method. This failed with the following errors:
remount failed: Operation not permitted
(then a few "no such file" messages removing old root files)
Pushing superuser.apk and su binary..
failed to copy root\su to /system/xbin/su : Read-only file system
failed to copy root\Superuser.apk to /system/app/Superuser.apk : Read-only file system
Setting permissions..
Unable to chmod /system/xbin/su: no such file or directory
Unable to chmod /system/app/Superuser.apk: no such file or directory
It looks like it's not being allowed write access to the drive???