so my screen recently stopped displaying anything,and im probably gonna send it in to verizon ASAP. is there a way to unroot the device using somthing like adb?
theblorg said:
so my screen recently stopped displaying anything,and im probably gonna send it in to verizon ASAP. is there a way to unroot the device using somthing like adb?
Click to expand...
Click to collapse
RUU10chars
theblorg said:
so my screen recently stopped displaying anything,and im probably gonna send it in to verizon ASAP. is there a way to unroot the device using somthing like adb?
Click to expand...
Click to collapse
If you can't see the screen, then neither can Verizon. By the time your phone gets to a repair facility (which might not even happen at this point), nobody is going to care who the prior owner of the phone was. Something to consider.
But, since you asked, here's a couple of alternatives.
(1) Try using the "Official" 2.1 RUU -or-
(2) Manually install the Leak-V3 ROM via adb [SIZE=+1]with Amon_RA booted[/SIZE]:
(a) Unpack the Leak-V3 PB00IMG.ZIP file on your PC. (Note that Windows native "compressed folder" zip implementations may not work because of the way that HTC signs the PB00IMG.ZIP files; iirc 7-zip should work, and certainly Linux/cygwin versions of "unzip" will work)
(b) Push the following individual files (unpacked from the PB00IMG.ZIP) to your sdcard:
Code:
adb push recovery.img /sdcard/
adb push boot.img /sdcard/
adb push system.img /sdcard/
adb push userdata.img /sdcard/
(c) Start a shell on the phone with adb ("adb shell")
(d) In the adb shell on the phone, perform the following steps, exactly as shown here. ( Do not type them - cut and paste, one line at a time )
Code:
mount /system
mount /data
mount /sdcard
flash_image boot /sdcard/boot.img
cd /system
rm -rf /system/*
unyaffs /sdcard/system.img
cd /data
rm -rf /data/*
unyaffs /sdcard/userdata.img
flash_image recovery /sdcard/recovery.img
cd /
sync
umount /data
umount /system
umount /sdcard
cd /cache
rm -rf /cache/*
exit
That's it. (You might see an error during the " rm -rf /cache/* " command, or complaints about the "lost+found" directory with any of the rm commands, but that's OK)
The "unyaffs" command will take some time with the system.img file - it's a big file (~160 MB); just let it go until the unyaffs command prints a message that it is finished.
Note that "flash_image" is already part of Amon_RA - you don't need to transfer it to the (booted) Amon_RA.
bftb0
bftb0 said:
If you can't see the screen, then neither can Verizon. By the time your phone gets to a repair facility (which might not even happen at this point), nobody is going to care who the prior owner of the phone was. Something to consider.
Click to expand...
Click to collapse
great info to know. im still probably gonna unroot it, just in case. thanks for the great post.
bftb0's the man!
Hello, I got the ATRIX on Bell and I tried rooting it yesterday...I don't know if it worked but when I installed Superuser I couldn't access any applications from it. So I took it as if it didn't work and Factory Reset everything (I haven't installed any ROMS or anything else) I followed these steps I found on the AndroidForums
#4. Open a command prompt on your computer (Windows logo key + R, type cmd) and go to that directory (should be c:/moto-fastboot-win32)
#5. Type the following commands one by one:
Code:
moto-fastboot.exe flash preinstall preinstall.img
moto-fastboot.exe reboot
Your phone will reboot, when it is up and running again, type the following into the command prompt.
Code:
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
It comes with a superuser apk in the files and that post, but I recommend you install superuser from the android market.
Click to expand...
Click to collapse
So now I was wondering if I try to root it again will it brick the phone? I'm running on Gingerbread 2.3.4. Would superoneclick work with this?
Thanks (I tried to look for similar threads but couldn't find any, sorry for double posts)
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.
i need to pull and push some system files in my phone for that i need to enter recovery mode in my xperia sola.please help to enter recovery mode.my phone is rooted.thanks in advance :good:
dviraj00 said:
i need to pull and push some system files in my phone for that i need to enter recovery mode in my xperia sola.please help to enter recovery mode.my phone is rooted.thanks in advance :good:
Click to expand...
Click to collapse
I think you dont need to put your device to recovery mode. Just use adb shell
to pull: (no need superuser privileges)
ex: format: adb pull [location of the file in the device] [to where the file is save locally]
adb pull /system/xbin/su c:
Click to expand...
Click to collapse
to push: (need su) since you rooted then:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
chmod 777 /system/app
then exit from devices, go to your command prompt and type:
adb push <local> <remote>
Click to expand...
Click to collapse
Hope it helps
capsule46 said:
I think you dont need to put your device to recovery mode. Just use adb shell
to pull: (no need superuser privileges)
to push: (need su) since you rooted then:
Hope it helps
Click to expand...
Click to collapse
thank you mate bt i am just a noob and dont know how to use adb shell.can u tell me plzz.this will save my relationship,plz mate
Hi, sorry for late reply
I assume you have installed your device driver properly
Then install android sdk: go to developer.android.com/sdk
Follow the step to install it. If you done it properly,you will find adb command in folder installation name platform-tools
Use it in command prompt. You can type adb /? to learn its capability.
Or you just go frok my post earlier
Hope it helps
Sent from my GT-N7100 using Tapatalk 2
I need help with this ASAP, as my device is currently in a bootloop because a boot animation app didn't work as well as I thought it would and my Dell Streak 7 will not boot up.
The device does still respond to adb commands, so there's a chance at saving it.
Unfortunately, I cannot get adb push to work, it says no permission when I try to do:
adb push bootanimation.zip /system/media
It says permission denied. I either need to know how to get adb push working or how to COMPLETELY reset the tablet, including all the system files such as bootanimation.zip. I need help as soon as possible
HackAttack37 said:
I need help with this ASAP, as my device is currently in a bootloop because a boot animation app didn't work as well as I thought it would and my Dell Streak 7 will not boot up.
The device does still respond to adb commands, so there's a chance at saving it.
Unfortunately, I cannot get adb push to work, it says no permission when I try to do:
adb push bootanimation.zip /system/media
It says permission denied. I either need to know how to get adb push working or how to COMPLETELY reset the tablet, including all the system files such as bootanimation.zip. I need help as soon as possible
Click to expand...
Click to collapse
Ok, I can help.
First, you cannot adb push to a system partition. you would need to have unprotected adb running in su mode.
Also, you will have to remount the system partition to rw.
try this code:
Code:
adb push bootanimation.zip /data/local/tmp/bootanimation.zip
adb shell "su -c busybox mount -o remount,rw /system"
adb shell "su -c cat /data/local/tmp/bootanimation.zip > /system/media/bootanimation.zip"