Related
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!
Hey guys
So I am currently running 2.3.3 on my N1. I manually flashed the update from Here. I used the "Modified GRI40".
So after update, I noticed that my adfree wasn't working. Running the app, it tells me my host file is up to date. However, no ads are being blocked. Same after uninstalling and re-installing the app. So then I decided to try to copy the host file over manually using adb.
I run adb and get root prompt. Then I mount /system as rw using
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
It appears to work. So then I try copying the host file to /system/etc using
Code:
cp hosts /system/etc
Then I get the following error.
"write error: No space left on device"
But i do, over 30mb of free space.
So I don't know what the issue is. Im thinking that maybe /system isn't being mounted as RW so it is giving the error??
Any help would be much appreciated.
Thanks!
Did you check the /system free space, or /data?
Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.
codesplice said:
Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.
Click to expand...
Click to collapse
Well looks like somehow I don't have any space left. I went to go download a terminal application from the market but it errored saying no space left.
So now I can't even install new apps.
However, under settings->storage it says I have 28MB of free space left.
Any ideas?
Sent from my Nexus One using XDA App
Reboot, wipe Dalvik cache.
Go to Manage Applications, clear browser cache.
If it restores you some space - great, proceed with what codesplice suggested above.
If it doesn't - backup, wipe and reflash.
If no backup installed - you're out of luck.
Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
codesplice said:
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
Well that's thing, that is why I started this thread because I was trying to use ADB to push a new hosts file but got the no space error. So I already tried that.
Sent from my Nexus One using XDA App
I was asking if you had specifically tried removing the old one and replacing it rather than just overwriting.
Oh I see what you mean. But no I have not, let me give it a shot.
**Nope didn't work. I still got the same error, no space left on device.
Have you had the opportunity to do adb shell df -h yet?
codesplice said:
Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?
Brownbay said:
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?
Click to expand...
Click to collapse
yes, without root access to the filesystem, adb remount will fail.
So when I try adb shell df -h, I get:
"-h: No such filesystem or directory"
You don't have busybox. Try running "adb shell df", maybe it'll still give some info.
Ok when I ran adb shell df I got a listing of filesystems. /system says size 145M and used 145M. So apparently it is full.
How could that be though?
It could be that you have some bad blocks on your /system partition (you can generally only check by doing a wipe operation in recovery and then viewing the log). These bad blocks could take up space that would otherwise store your system data, and could push you over capacity.
Or you could just have some extra bloat related to that ROM. You could drive to remove some of the applications on /system that you don't have use for (the Amazon MP3 thing, for instance). I'd suggest using Titanium Backup to do this, but you can also do it by manually using the adb shell.
Alternatively, a full wipe and clean reinstall may help make sure you don't have anything left over taking up space.
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
I've been really impressed with the Kang-o-rama ROMs. Basically prettied-up versions of Cyanogen. The latest release is a beta based on CM7, so still has a few issues. The prior release (KOR 1.1Final) is still quite solid.
And yes, a nandroid backup creates a copy of your current disk image, which can then be restored at any time to revert back to a previously-working configuration (great for when you break stuff!).
decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
Exactly Remember to wipe before restoring
Oh and that brings up another thought.
So if before I flash a new ROM, I do a Titanium Backup and then flash the ROM...
Would I then be able to restore that Titanium Backup made on the previous stock ROM to restore all my apps and user data?
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...
Hello,
I've had my phone rooted for a long time and things were working out quite fine (yes, I have a recent xRecovery backup ) but a couple of days ago I wanted to try out something new, and wanted to prepare my system for the installation of a custom kernel.
Long story short: I used the busybox installer from the market, but it couldn't verify the installation process because of some previously installed busybox version (guess it came with my ROM...) So I used the uninstall option within the app and this is were things started to go down the drain:
Now when I reboot the phone, it's no longer possible to enter xRecovery as it was possible before (pressing back button repeatedly, during SonyEricson Logo) instead the it just reboots straight into Android. And in Android all that works is the log screen - all other applications / services crash. (I really can't do anything, as soon as I try to unlock the screen I'm bombarded with Error Messages, and sometimes the phone reboots because so many services fail)
I still can get into the reboot options menu when I press the power button > 1sec, but selecting "reboot into xRecovery" or "reboot into CWM" doesn't work -> it will just reboot normally again.
It also seems impossible to get the phone into flash mode. (Turn Phone off, Unplug USB, hold Back Button, Turn Phone on, Connect USB - and every possible variation I could find just leads to the phone booting into Android)
What I tried to do:
I still have root access when I connect to the phone with adb, so I reinstalled the busybox binary from the "SuperOneClick" package into the /system/xbin/ folder manually -> no change
I checked the debug log (from adb logcat) for errors indicate a problem, but there's no obvious message
I checked the dmesg output for errors / problems, but here everything seems to be fine
I reinstalled xRecovery manually (files from SuperOneClick) via adb by putting the files (xrecovery.tar+chargemon), into /system/bin -> no change
I tried to get into recovery / bootloader mode by using "adb reboot bootloader" and "adb reboot recovery" -> normal reboot
I checked the permissions of the binary files (su, busybox, chargemon) and they're all set to 06755
I checked if all symlinks of system programs that require busybox / su are pointing to existing binaries, and they all seem to be correct
Before I proceed and start trying some things that are not so easily reversible I've got a couple of questions:
What happens if I delete all files in the "/system/" folder? (the xRecovery files are in that folder and I guess xRecovery itself needs a couple of files to work properly)
Do you have any tips / ideas what I could try? I really don't mind resetting the phone as I have backups, it's just that I can't get into the mode where I can reset the phone
Thank you very much!
In your case, i suggest you never ever, ever fiddle up with busybox again... leave that up to chefs.
Also, i think you should try removing the battery for a couple minutes, then put it back and press back, then (while holding it) insert usb cable. That's a surefire way to get into flash mode (At least for me, sometimes it happens to boot normally even if i press back if i don't remove the battery). Also, just to be sure, before connecting your phone in flash mode, press Windows + R [In your keyboard, obviously] and type "devmgmt.msc" [Without the quotes] and see if you get a new device under USB devices. If it has a yellow triangle, right click it and choose update drivers, then point it to the flashtool folder for drivers, it should be able to find them. Good luck.
Use PCC
PCC Brought my phone to its original state when I had soft bricked my phone. It worked as a charm , and it was back to the state like nothing ever happened. Also my phone got unrooted. Everything stock like I had bought it from the store.
Use PCC , thereafter get your phone rooted again , as you had initially done.
Dude are you kidding me???You are doing it wrong man...
to get into flashmood
1. turn your phone off
2.press and hold the back button
3.without leaving the back button insert ur phones cable ..
you don't. need to turn on your phone after doing this....
use pcc or seus to repair it it's a soft brick......
@all that replied: Thank you for your help, I managed to fix the problem, will explain it in next post in case somebody runs into a similar problem
@Drknzz
about the fiddeling: that's how you learn stuff - in the last 36 hours I was forced to dig deep into android, and it was fun - and now I've got a pretty good picture of the system
Your your tip about removing the battery for a cpl of minutes didn't work for me.
I also tried XperiaRebootOptions, but this app also fails putting the phone into FASTBOOT mode - so I'll have to keep searching for an explanation
@Mayank77
I can't use PCC, because I'm running Linux as my O/S of choice and try to keep my VirtualBox locked (when I was very desperate this morning I tried it in a VirtualMachine, but PCC wouldn't connect properly to my phone)
@noobismyname
thanks, but doesn't work in my case
a little description of how you can solve problems (using Linux) with incompatible versions of su and busybox that can occur when Market Apps like BusyBoxInstaller are used in combination with ROMs that require specific Versions of the above tools.
In special cases this might lead to the problem, that you can no longer enter xRecovery or put your phone into fastboot mode (depending on your ROM) but you still have debug access to your phone.
Requirements
Nandroid / xRecovery Backup on your local machine
Android SDK -> adb
Image extraction tool unyaffs
root access to phone
Steps
Extract the backup image
The backup files created by xRecovery use an uncommon format because of the filesystem used in android. Use the tool unyaffs (code dot google dot com/p/unyaffs) to extract the image to a directory of your choice.
log into you phone with adb
open up a terminal, and use $adb shell to connect to your phone. Change to root user $su root
If required: make the partition writeable
$mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
compare files
open a second terminal window and navigate to the folder where you extracted the backup image. Start comparing the content of the directories with each other. Important files are: /system/build.prop, /system/bin/su ->symlink to system/xbin/su, /system/xbin/busybox, ...... (depending on what you messed up)
the command $busybox ls -l /system/targetdir | grep sought_file [/] comes in handy, because it will output the files alphabetically sorted and not in arbitrary order like the default adb ls proproamm
[*]use adb to push files to your device
if you find a missing / missmatching file use $adb push /file/on/your/pc /data/local/tmp to copy the backup file to your mobile
[*]copy files to target directory
use (as root) $ cp /data/local/tmp/file /system/..... to copy your backup into the correct place
[*]check permissions
check the permission of every file you copied and in case you're unsure: they should belong to root, group root, access permission 755 (or 06755 in case of busybox and su)
$ls -l /target/dir | grep filename to check
$chown root /target/file
$chgrp root /target/file
$chmod 755 /target/file
[*]make sure changes are written to disk
flush all pending filesystem changes $sync
[*]reboot
exit the adb session with ctrl+c
and use adb reboot to restart & enjoy your phone
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
kmacho714 said:
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
Click to expand...
Click to collapse
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
twrp sideload
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
kmacho714 said:
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
Click to expand...
Click to collapse
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
adb
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
do i need android sdk? and htc sync? i have the drivers i think? on my device managers it doesnt say adb . just device and on the info it says htc device
thank you
tdhite said:
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
Click to expand...
Click to collapse
thanks a lot! those commands work ! just needed to install the drivers . thanks! again