Related
When trying to launch EITHER camera app or camcorder app, screen goes black, and then says application has to force close.
Can still view photos in Gallery app and on camera app (I have since deleted them all from camera app, thinking I had used up its capacity).
Have tried soft reboot, hard reboot, pwer off + remove battery + recharge (which worked once, but the problem recurred). Nothing helps right now.
PLEASE HELP! G-1, carrier is T-Mobile.
daBandmaster said:
When trying to launch EITHER camera app or camcorder app, screen goes black, and then says application has to force close.
Can still view photos in Gallery app and on camera app (I have since deleted them all from camera app, thinking I had used up its capacity).
Have tried soft reboot, hard reboot, pwer off + remove battery + recharge (which worked once, but the problem recurred). Nothing helps right now.
PLEASE HELP! G-1, carrier is T-Mobile.
Click to expand...
Click to collapse
I recently had something like this happen to me, it was a ROM issue. I reflashed a new ROM (CY-3.6.8.1) and it worked mint again. But I also see this is your first post, are you rooted?
What is "rooted?"
If you don't want to root, just reload the factory cupcake rom and see if that corrects it. Just like other poster said sounds like a rom issue.
http://forum.xda-developers.com/showthread.php?t=442480
Try This
from Terminal
su
mount -o rw,remount -t yaffs2, /dev/block/mtdblock3 /system
rm /system/app/Camera.apk
rm /system/app/HTCAlbum.apk (That Will uninstall them)
(Download these two files and put them on the root of sd card.)
http://www.mediafire.com/file/jwrgqgndfwm/Camera.apk][/url]
http://www.mediafire.com/file/m1hnyimzlk0/HTCAlbum.apk][/url]
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/Camera.apk /system/app
cp /sdcard/HTCAlbum.apk /system/app
reboot (This will install them back)
hey Im trying to get my camera working again. I follwed the instructions here but after the second entry in the terminal to remove camera it says
"rm: cannot remove ' /system/app/Camera.apk ' : Read-only file system"
What can I do from there?
phatmanxxl said:
hey Im trying to get my camera working again. I follwed the instructions here but after the second entry in the terminal to remove camera it says
"rm: cannot remove ' /system/app/Camera.apk ' : Read-only file system"
What can I do from there?
Click to expand...
Click to collapse
type
su
mount -o rw,remount /dev/block/mtdblock3 /system
then the rest of the commands...
Ayee these two files are not up nomre to download mcfly015 displayed an i really need to kno how can i get my camera & my recorder back an working again plz any1 can reply to this statement as well
G1 camera and battry problem
I have the same issue with my camera, also battery is draining really fast and battery feels heated up. I am using cy 6.1 and it started since couple of days though b4 that everything was working perfectly normal, please HELP
Guys he is not rooted
Stop telling him to do "su"
It could also be a cable inside.
It's happened to me before
Obviously a radio difference, but what else prevents roms being easily ported to Milestone from Droid? Im not sure on the internals differences, but could we start porting.
NB do we even have root !?
we have root on both devices i think the exploit may be the same? forgive me if i am wrong.
(root guide for 2.1) the latest update at time of this post.
http://android.modaco.com/content/m...m/308422/milestone-2-1-update-and-root-guide/
the problem on the milestone as anyone will tell you, the LOCKED BOOT LOADER this isnt a problem for the Droid users, they got this for free. Hopefully with the power of the XDA super Dev team, we will have a solution for this, and start pumping out custom roms!
all of the accessories fit for each other, which maes it handy if you want some cheap bits from china, there isnt any carrier in the uk that has the milestone, what i am saying... carrier.. i mean mobile phone network!
i got my milestone from here. buymobilephones.net on a contract, but you can also get them from expansys, as far as i have researched, they are all unlocked. So you shouldnt even need to post about unlocking the sim.
there is another differnce i remember, if you are loading busybox on your device, this will not load if you use droid root helper from the market, you will need to manually do this via ADB and the loaction on the partition is different.
carphone warehouse sell the milestone on t-mobile and you can install busybox with droid root helper.
The kexec modules are nearly working. So there will be a 2nd bootloader in near future.
http://and-developers.com/motorola_milestone
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
iamdarren said:
I messed my first one up when I used droid root helper, but I have recently download titaium backup and that says it has installed busy box for me over the net. But terminal tells me no busy box found, the only way I have had it working was via the manual install.
Click to expand...
Click to collapse
Titanium installs busybox in its own data directory so that only it can access it.
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Main difference is the locked bootloader , there is a signature verification at boot time that prevents us from running custom Kernel .
Its unlikely that the bootloader signature will ever be cracked , other workaround like Kexec will most likely help achieve further mods to our device eventho it seem to be right around the corner there is still much work to be done
iamdarren said:
Cool that answers that. I want to put busybox back on to use cachemate again. But can't find any instructions. So haven't yet
Click to expand...
Click to collapse
Download Busybox and use this to install it:
Code:
ADB push busybox /sdcard/busybox
ADB shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
# cat /sdcard/busybox > /system/bin/busybox && chmod 700 /system/bin/busybox
# sync
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
Its better to push it to xbin and not to bin, as the most apps search there for the busybox
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
cmstlist said:
After Titanium had installed busybox, I opened Root Explorer and moved it from Titanium's data folder to /system/xbin (had to temporarily mount R/W to do so, using the button up top). Titanium is still happy as it still finds busybox. Do I need to do anything else for other programs that require it?
Click to expand...
Click to collapse
your good ..
Hey guys,
I rooted my N1, then (only days later) somehow my microusb port got damaged, and now won't charge or connect to the computer. My guess is that HTC would honor a replacement request regardless of root because it's solely a hardware issue, unless someone thinks otherwise, but I am curious as to whether it's possible to unroot without USB anyway.
Ideas?
You could try the 'Unroot' button in Universal Androot?
Hmm, that just tells me that I'm not rooted.
Hmmm, you could try downloaind a terminal emulator and using that to remove /system/bin/su and /system/app.Superuser.apk although you'd need to us SU to gain the rights to delete them, so not sure if it would like that. Worth a go though.
Edit: Just tested it, that works fine, go for it.
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd ..
cd bin
rm su
exit
why don't you copy a passimg.zip on your sdcard and flash it in hboot?
adbWireless
I Modified These APK files to enable the Webtop on any HDMI connection.
Removed the Device ID check from the Webtop Launcher in PortalApp.apk
And Made DockProvider/DockService Display the Webtop as an option whenever an HDMI cable is connected.
We got PROPS from Engadget: http://www.engadget.com/2011/03/05/motorola-atrix-docks-literally-and-figuratively-torn-apart-hack/
NOTE THESE FILES ARE FROM THE ATT BRANDED ATRIX v4.1.26
THEY WILL NOT WORK ON THE BELL ATRIX VARIANT
Added Support for:
Atrix 4.4.80.MB860 (South Africa) Users Go HERE: Updated Mod Files for Atrix 4.4.80.MB860 (South Africa)
Version 4.5.91 Users Go HERE: (This works now.) ATRIX 4.5.91 WEBTOP MOD FILES
ATT version 4.1.57 Users Go HERE: ATT ATRIX 4.1.57 WEBTOP MOD FILES
Bell Users Go HERE: BELL ATRIX WEBTOP MOD FILES
*new* CWM Install Method - CWM Required:
Get CWM here: http://forum.xda-developers.com/showthread.php?t=1019143
Then install the flashable zip here: CWM-ATT-4.1.26.zip
You no longer need to be rooted OR deodexed!!!!
Install Method 1 - No Root or Deodex Required:
Simpler install method:
Download The Mod Files here: HERE
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
RETURNING TO STOCK - Root Required:
This will restore the files that were backed up by the install script.
If you were Deodexed it will restore the modified files to the original Deodexed State, if you were not deodexed it will restore to stock and allow motorola updates to work again.
Note: If you were deodexed you can ignore the three lines about the odex files.
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/WebtopModBackup/DockProvider.odex.bak /system/app/DockProvider.odex
cp /mnt/sdcard/WebtopModBackup/DockService.odex.bak /system/app/DockService.odex
cp /mnt/sdcard/WebtopModBackup/PortalApp.odex.bak /system/app/PortalApp.odex
cp /mnt/sdcard/WebtopModBackup/DockProvider.apk.bak /system/app/DockProvider.apk
cp /mnt/sdcard/WebtopModBackup/DockService.apk.bak /system/app/DockService.apk
cp /mnt/sdcard/WebtopModBackup/PortalApp.apk.bak /system/app/PortalApp.apk
chmod 644 /system/app/*
Install Method 2 - Root Required:
Other than that, install with ADB
Code:
adb push DockProvider.apk /mnt/sdcard/
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mv /system/app/DockProvider.odex /system/app/DockProvider.odex.bak
mv /system/app/DockService.odex /system/app/DockService.odex.bak
mv /system/app/PortalApp.odex /system/app/PortalApp.odex.bak
cp /system/app/DockProvider.apk /system/app/DockProvider.apk.bak
cp /system/app/DockService.apk /system/app/DockService.apk.bak
cp /system/app/PortalApp.apk /system/app/PortalApp.apk.bak
cp /mnt/sdcard/DockProvider.apk /system/app
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
reboot
Or just use root explorer to copy the files to /system/app and rename the .odex files to .bak
Make sure you set the permissions on the files to rw-r--r-- or they will not work.
Then Enjoy your fully functional webtop.
Having problems? Read Below.
Try clearing your Dalvik Cache:
Code:
adb shell
su
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
acardinale said:
It was INDEED permission issues.
If using the root explorer method, you MUST fix permissions for all three files to rw-r--r--
Thanks Fenny!
Click to expand...
Click to collapse
Additionally, try unfreezing any frozen apps in Titanium Backup.
Thanks to DG for his ADEO installer script.
Appreciate my work? Buy Me a Beer:
Fenny said:
I Modified These APK files to enable the Webtop on any HDMI connection.
Removed the Device ID check from the Webtop Launcher in PortalApp.apk
And Made DockProvider/DockService Display the Webtop as an option whenever an HDMI cable is connected.
YOU WILL NEED TO BE ROOTED AND DEODEXED!!!!
@DesignGears, Mind if I modify your Installer script to load these? BTW You are in SLC? I am in Draper, We should totally meet up.
Other than that, install with ADB
Code:
adb push DockProvider.apk /mnt/sdcard/
adb push DockService.apk /mnt/sdcard/
adb push PortalApp.apk /mnt/sdcard/
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/DockProvider.apk /system/app
cp /mnt/sdcard/DockService.apk /system/app
cp /mnt/sdcard/PortalApp.apk /system/app
reboot
Or just use root explorer.
Then Enjoy your fully functional webtop.
Click to expand...
Click to collapse
HAHA you beat me to it i was up all night last night doing this ... good work ill test yours out
Hehe told you the answer was in PortalApp.apk.
Can you do the mirroring HDMI too in the same or similar way?
Anyway you're great!
mercuryzzz said:
Can you do the mirroring HDMI too in the same or similar way?
Anyway you're great!
Click to expand...
Click to collapse
I have been looking into it, I don't think the DockPicker Activity HAS a mirroring option, but I think it should be possible with third party software.
Fenny said:
@DesignGears, Mind if I modify your Installer script to load these? BTW You are in SLC? I am in Draper, We should totally meet up.
Click to expand...
Click to collapse
We totally need a xda meetup I am in Kearns
Fenny said:
Hehe told you the answer was in PortalApp.apk.
Click to expand...
Click to collapse
Yep, i did waste alot of time in the others as well, than i spent morning posting themes etc , any how congrats and glad to see either way we on same page... now we got to get some drivers and functionality over to this webtop, as my magic track pad is lacking any multi touch but im confident in getting that done , i mean after all if is Ubuntu !!
AWESOME work.
Are you sure we need to be deodexed? we are just replacing the APKs here.
clubtech said:
AWESOME work.
Are you sure we need to be deodexed? we are just replacing the APKs here.
Click to expand...
Click to collapse
Yes if you dont understand why you need to re read up on it, as .odex files contain parts of the program that were moved out side to be optimized
So, when I copied the last one using Root Explorer it kept crashing the process PortalApp so I ended up removing the battery and yet to test it.
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
ankitb4u said:
So, when I copied the last one using Root Explorer it kept crashing the process PortalApp so I ended up removing the battery and yet to test it.
Click to expand...
Click to collapse
Yeah, you need to reboot after replacing the files, can't hurt to clear the dalvik cache either. But the crashing is expected until you reboot.
clubtech said:
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
Click to expand...
Click to collapse
Yeah, the on screen Trackpad, AND Keyboard work great.
clubtech said:
So we basically need to install "Adeo" to get a deodexed system...
Before i do this, when connected only with HDMI and the webtop, does the on-screen trackpad works?
Click to expand...
Click to collapse
you dont need Adeo per-say but that might be the easiest way for you to get a deodexed system unless you know what you are doing... i do not have adeo but am deodexed
Works PERFECTLY.
Did have a continuous FC after loading PortalApp.apk, but it went away with a reboot.
Tested all the WebTop functions and from what I can tell, they all work without issue.
Nicely done!
Props to the OP + contributors for getting this much-needed functionality going so quickly.
I am super excited about this. Props to all that was involved. I will be trying this later. I really need to get more familiar with ADB. Thanks again.
clipse94
Webtop via HDMI cable is working great! Now to find a working ARM-based JRE...
Awesome
correct me if im wrong, but now a bluetooth keyboard and mouse are a neccessity for 'desktop computing' right
since the dock allowed us to use a USB one
?
If I recall correctly, the phone itself has an trackpad and onscreen keyboard that can be used for desktop computing. Otherwise, a bt mouse a keyboard would be in order.......and are ordered.
clipse94 said:
If I recall correctly, the phone itself has an trackpad and onscreen keyboard that can be used for desktop computing. Otherwise, a bt mouse a keyboard would be in order.......and are ordered.
Click to expand...
Click to collapse
Correct.
BT keyboard and mouse not required.
Built in track-pad mouse and keyboard work fine.
Takes getting used too though.
This comment was made via the webtop.
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Cowmonaut said:
Okay, so this is a doozy. I recently got a Droid3 to replace my original Droid. I've had it for less than 3 months. Its been rooted using Pete's One Click Root for this entire time without any issues.
Last week the following symptoms manifested:
1) Most applications, including system applications, force close constantly.
2) I'm usually unable to run any applications, including the Market.
3) What applications are having issues is not consistent.
4) The phone will reboot itself randomly, sometimes constantly.
5) Sometimes after a reboot it gives me no service and has the "Touch Android to begin" screen again. The phone is completely unusable when it does this, and the only fix is to pull the battery and then its back to its previous state.
5) Any changes made to the phone do not survive a reboot.
This last one is the real kicker. I can go through, uninstall every application I've ever downloaded but if you restart the phone or it restarts itself they will all return. This goes for everything on my Internal Storage. The SDCard seems unaffected...
I tried the SBF trick here from rootzwiki. (can't link since I'm new)
This did not work. How it failed might be important:
1) The primary method (psouza4's) acts like its successful but doesn't actually do anything.
2) RSDLite method will fail in step 3 (mbmloader.bin) every time, no matter what fastboot file I try to use.
3) After doing RSDLite I had the "flashboot flash failed" error and the phone was unusable. I then tried psouza4's method again and my phone has reverted to the same broken state it was in when I started.
So I'm not at all sure what I can do here. Since the bootloader isn't cracked yet I have no means to load another ROM. The only method I can find for Droid3 is through a Marketplace app that, on the rare instances I can install it, force closes immediately!
Any advice or ideas at all would be nice.
As for what started this, only two things happened out of the normal phone usage:
1) My girlfriend tried to text me a picture for the first time (of some chairs she wanted to buy for those curious/suggestive ) which never got to me initially but when it finally did after the 4th attempt I was never able to download the image.
2) I put a PDF file on the Internal Storage. Its one I've had for years and its just some manual I needed mobile and I don't have a laptop. Confirmed its malware free as far as any software can tell.
Working theory is I unplugged my phone from the USB too quickly after uploading the file but I don't know for sure. Nothing else was done unless Verizon had a OTA update that would break a rooted phone (guessing not since no one else seems to have this issue anywhere).
Again, any help someone can provide would be excellent. I'm going to have to load up my broken Droid in the mean time. Keyboard doesn't work and the touchscreen is failing but it can take calls more reliably than my Droid3 currently!
Click to expand...
Click to collapse
I can say a couple words to describe my reaction.. OH ****. Your phone seems to have too many problems to be software related. Try to flash back to stock 5.6.890 and get a new phone.
Sent from my DROID3 using XDA App
Hmm, I guess for the mean time I'll just have to keep trying to get the Marketplace ROM Manager to install and launch. Should be a way to install straight to the SDCard that doesn't have problems.
Thinking it over, my Internal Storage may just have a bad sector... Yeesh.
Have you tried formatting /system in mounts and storage in CWM? Then reinstalling a fresh rom on top?
Sent from my DROID3 using xda premium
Negative. I didn't have CWM installed (stock ROM just rooted for certain apps) and apps are usually crashing now.
I'll give that a shot though. Sometimes I can use an app so maybe if I'm persistent...
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Yea can't get any new apps to run. Interestingly, the camera app seems to crash the OS at the moment.
I think I'm going to have to try to RMA...
MrJudylicious said:
and to verify, you are using the verizon droid 3 xt862? Are you on 5.5.959 or 5.6.890 (or possibly 5.7.894)?
Click to expand...
Click to collapse
Its running 5.6.890. Unless I'm mistaken its the xt862. I've only had it since September.
well as long as root isnt showing and the /system hasnt been changed from stock rom, it should work. i do find it bad that rsd didnt work. i wonder if you were trying to flash the .959 sbf on your .890 system? I would def try again to sbf and wipe data/cache through stock recovery after that using volume buttons (android!)
Well, that's kind of the problem. Changes don't survive a reboot so i haven't been able to unroot the phone. I double checked and the file was the .890 flashboot. Wiping data/cache literally does nothing.
Is there a way to format this offline, from a PC? Going to try some more Google searches...
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
MrJudylicious said:
wiping data/cache should erase all of your saved data and force you to *228. Make sure USB debugging is on, set usb to Charge Only, try petes motorola tools to unroot but using RSD 5.5 fastboot .890 found http://forum.xda-developers.com/showthread.php?t=1255198
Click to expand...
Click to collapse
1) How do you unroot with Pete's motorola tools? Is it a different version than the one click root? Cause that's how I rooted my phone in the first place but it doesn't seem to have an option to unroot...
2) The link for the flashboot file gives a 404 error. The attached .RAR only has the .XML file.
Any place else I can get that version?
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Edit: srry didnt read the full post
jellydroid13 said:
just enter stock recovery by holding down the x key on the keyboard when you boot up and wipe data
Click to expand...
Click to collapse
If you read the original post, that doesn't work.
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
sh[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Cowmonaut said:
Okay so I had an outdated version of Pete's tools which is why I didn't see the unroot option. Mine is the older one that was a batch file, not a application.
Got that sorted out and it still doesn't work. Seems I may have some permissions issues:
Code:
> su
> /system/xbin/su
> mount -o remount,rw /dev/block/mtdblock3 /system
> if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
> exit
> exit
[email protected]_solana:/$ su
exit
exit
exit
Permission denied
[email protected]_solana:/$ /system/xbin/su
Permission denied
[email protected]_solana:/$ mount -o remount,rw /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]_solana:/$ if [ -e /data/local/12m.bak ];
> then
> rm /data/local/12m.bak
> fi
[email protected]_solana:/$ exit
(success)
That's part of the ADB log. There are a lot of other permission denied messages, which is a little comforting. The only thing I could think of that happened is permissions didn't get set right when Internal Storage was unmounted from my PC.
Since I can use ADB to access the shell, how can I format /system on the droid3? I can't seem to find the correct root name to use.
Click to expand...
Click to collapse
Have you tried to root manually? Here are the original instructions vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
[edit] I guess I miss read that you are trying to unroot.
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
MrJudylicious said:
try http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/ but you cant go from .890 back to .959! no idea about mounting, sorry.
Click to expand...
Click to collapse
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Cowmonaut said:
That's the reference to Rootzwiki I made in the original post, doesn't work sorry.
Using ADB I mounted /system as rw and tried to manually remove certain apps. Once I re-mounted they were there again. So something is preventing me from making real changes to the Internal Storage.
Click to expand...
Click to collapse
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
ChaoticWeaponry said:
You don't have superuser permissions.. In the ADB shell your command line should start with a # indicating superuser permissions.. you have a $
Click to expand...
Click to collapse
Where do you get that idea?
When I do this manually:
1) I'm running the command prompt as Administrator
2)I'm launching into adb using the command "adb shell".
3) First thing I do is type in "su"
4) second thing I do is approve "unknown" in the superuser app on account of it never remembering I already did that.
5) I use the command "mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system"
6) I use the "ls" command on /system/app and find an .apk to uninstall (not all my apps seem to be installed in this location either...)
7) I use the "pm list packages" command to find the rest of the files for that .apk
8) I use "rm <filename>.apk" followed by "pm uninstall <whatever that developer chose to name things>" command to fully uninstall.
I should note on my phone at this point it disappear from the application list.
9) I use the command "mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system"
10) I use the "ls" command on /system/app to confirm and voila, the apk file is back!
The app doesn't show up in my app manager until I reboot the phone. Changes to /system and /data are not persisting and I have no idea why.
I can't seem to unmount them either so I can't format via ADB...