I have looked all over for the answer to this and I am at my wits end...
I have been trying out different roms and themes to find that sweet spot for me, and I think I have now. I know that alt+w on the bootloader only wipes factory data and such, and that if I reformat my sd card it'll wipe everything including my ext2 partition. But I don't want all of that to happen. I want to wipe the apps I have on my sd card but keep the music, movies, etc I have on there without having to uninstall each one thru a file mgr (I have 83 apps right now).
The problem I am having that is making me do this is that when I flash cyan3681 and start over at the adp screen where you tap the android, right after that it starts showing force closes for a number of apps, and it always opens open overclocker and kinda hangs there. On top of all that, at some point, it messed with some apps in my drawer and either won't allow me to access them anymore or it shows the stock apk icon with the little gear and the page behind it.
I just want a fresh start, without having to spend an hour(s?) doing it. Thanks for any help.
run this in terminal
su
rm -rf /system/sd/*
Bzerk1 said:
a question on this, can you use this command in the console of cyanogen recovery 1.4 (alt+X)? and do you stil have to input
su before rm -rf/system..... ?
Click to expand...
Click to collapse
in recovery console just type
mount /system/sd
rm -rf /system/sd/*
alritewhadeva said:
run this in terminal
su
rm -rf /system/sd/*
Click to expand...
Click to collapse
a question on this, can you use this command in the console of cyanogen recovery 1.4 (alt+X)? and do you stil have to input
su before rm -rf/system..... ?
Bzerk1 said:
a question on this, can you use this command in the console of cyanogen recovery 1.4 (alt+X)? and do you stil have to input
su before rm -rf/system..... ?
Click to expand...
Click to collapse
You would be running in recovery console so you would need to use alritewhadeva's method posted a couple posts up:
Do this before the above:
Code:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
Thank you, that worked perfectly.
I am M3 said:
Do this before the above:
Code:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
just "/# mount /system/sd" works fine
Adam17 said:
Thank you, that worked perfectly.
Click to expand...
Click to collapse
You're welcome. Please change the thread title to [SOLVED]
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
Title says it all. While trying to learn some theme tricks, I must have screwed something up in the framework, because I'm stuck in a boot-loop after rebooting.
Thanks to Aria's post, which describes an easy way to make an easy ADB shortcut, I'm all set to go with ADB... but how can I force my cell to mount my computer when it's turned off? I just need to push my backup onto my phone, because I copied my CWM backup onto my pc and deleted it from my cell to make more room for videos. Stupid, I know
Any ideas? Thanks!
Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.
how did you fix it i am stuck on lg logo when i boot i would really appreciate any help you could give
Komodo Rogue said:
Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.
Click to expand...
Click to collapse
You can mount the system like this. If it's in a bootloop and ADB is enabled, this'll work.
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
Sent from my LG Thrill 4G
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...
Ok, need a bit of help here. If ANYONE can help, please do. I don't mind suggestions.
So I'm rooted on 2.3.5 with CWM and CF-Root.
I smashed my screen the other day and I need to restore the device. Unfortunately, I disabled USB debugging mode so I've been having real issues. I've been able to get everything from the SD-Card, but now I need to wipe it.
If possible, is there a way of enabling USB debugging in Android from the CWM? I know it's active in CWM but I'm struggling to achieve anything. I have a Nandroid with USB Debugging Enabled but everytime I try to do something I hit a brick wall.
If I try to su in adb shell I get this:
~ $ su
su
/sbin/sh: su: not found
~ $
If I try to mount the internal sd card I get:
mount /sdcard
mount: permission denied (are you root?)
~ $
As expected...
I can't run Nandroid I get this:
E:unknown volume for path [/sdcard]
Can't mount /sdcard
~ $ su
but I can cd to the /sdcard and view my files.
Any help would be great, no matter how insane. I do have an SD card to hand so if anyone thinks I can somehow use that to run Nandroid that would be great. I have two or three Nandroids (all of which have USB Debugging ENABLED) on my computer so that COULD work...
The only trick I haven't done, is trying to restore nandroid blind by following a youtube video with the amount of clicks on the volume etc. that is the last roll of the dice.
Thanks,
Skezza
Nobody? Please, I really could do with some help here.
okay, ill do the last roll of the dice, can someone tell me how many presses down until I get to YES, out of the No No No, please this is really quite important.