Related
So, I've had this rooted G1 for a long time. It was running Flan, and quite well, today, i kept getting errors, so I rebooted, after reboot, it would not go past the first bootscreen, I can still access recovery mode, but I have no idea what is going on, I tried to reflash Flan, and I kept getting error in sector E, or something like that, anyone know what's up?
I think I had a similar problem. It just died on me randomly and immediately started to reboot. It got stuck on the bootscreen (mine was the second I believe; the one after Tmobile G1). I did an alt+w wipe and rebooted. It took a long time, but just be patient and see if it will boot.
Didn't boot, I unrooted, and it booted, but now I'm stuck at the activation screen, Win 7, will not get the damn driver right, and Mint doesn't know what ADB is, even thought I installed correctly, or so I think, It's been so long since I've used ADB.
Since Mint is just ubuntu in a nice frock, follow this to get adb talking to your phone:
wddglr said:
You will now set up your bashrc file and UDEV to recognize your HTC Device.
!!START -------------------------------------- ADB + FASTBOOT --------------------------------------
The Android Debug Bridge (adb) is one of the tools that will help you the most when you run into flashing problems or running shell commands directly from your machine. UDEV will not recognize your G1 out of the box, but we will configure it with some rules so it can connect.
We will work with /AndroidSDK as the location of your sdk. If this is not your setup, I think you're smart enough to figure it out.
Editing .bashrc file to use tools from /AndroidSDK/tools/ directory -
Go to your home folder.Example: /home/wddglr/
Press Control + H to view hidden files.
Look for your .bashrc file and double click to open it with gedit.
Add the following lines to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/AndroidSDK/tools
IMPORTANT NOTE
Setting up UDEV to recognize HTC Device -
Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click save and close.
To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
Setting up fastboot -
Download this fastboot binary from http://android-dls.com.130.4 KB [http://android-dls.com/files/linux/fastboot]
Once downloaded to your desktop, right click and select Properties.
Navigate to the Permissions tab and configure the following option:Execute: [√] Allow executing file as program
Click Close.
Move the fastboot bianary to your /AndroidSDK/tools/ directory.
Reboot.
-------------------------------------- ADB + FASTBOOT -------------------------------------- END!!
Click to expand...
Click to collapse
I got it working, I forgot to do the root exploit thing, anyways, I installed the Danger SPL, newest radio, Cyan works, all of the 2.1+ builds don't, they just stay at the first boot screen, I even left one going over night, never got past the first boot screen, I'm annoyed as hell with this. Could it be something to do with the newest radio? The one after 26I?
Just womdering?
did yyou have your sdcard patitioned? If so you may want to wipe your ext partition and also repair your ext partition and then reflash a flan rom?
That's what I thought, because I had a second SD card, just Fat32, and it booted after a reroot, so I formatted the whole SD, but now I'm scared of using anything but Cyan.
Ok, new issue, I tried putting SuperEclair V8 on the G1, and I get this error:
E:Can't symlink /system/xbin/bb/
[
E:Failure at line 61:
symlink /system/xbin/busybox SYS
TEM:xbin/bb/[
Installation Aborted
So what's the issue with this, gives me that error after a complete reroot, and multiple wipes.
Godfrd824 said:
Ok, new issue, I tried putting SuperEclair V8 on the G1, and I get this error:
E:Can't symlink /system/xbin/bb/
[
E:Failure at line 61:
symlink /system/xbin/busybox SYS
TEM:xbin/bb/[
Installation Aborted
So what's the issue with this, gives me that error after a complete reroot, and multiple wipes.
Click to expand...
Click to collapse
I am having the same exact issue with the same exact rom, if anyone can help it would be much appreciated
thanks
nate
Hey guys, I didn't make this guide, nor did I contribute to it at all. This is in no way an attempt to toot my own horn.
I am linking this guide because I have followed it with my HTC Incredible at it worked flawlessly and figure some of you might be interested in running Ubuntu on your phones too.
Here is the guide, it was written for the Nexus One but works great for the Incredible too.
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
Some things to note, I am running Cyanogen 6.0 RC3. You must run an android with a modified kernel that supports loopback devices. Cyanogen 6.0 RC3 has loopback devices enabled. Also it goes without saying, but I will say it any way, you need to have a rooted phone. A quick down and dirty of what you need to do to get started is as follows.
**** MAKE SURE YOU HAVE YOUR PHONE PLUGGED IN FOR ALL OF THIS!!! YOU DON'T WANT YOUR PHONE DYING AT ANY POINT IN THIS QUICKY GUIDE****
Go here: http://unrevoked.com/#inc
Download both Unrevoked3 and Unrevoked Forever. Connect your phone to your computer and run unrevoked3. This will root your phone.
Once rebooted go to the market and find and install "Rom Manager" by ClockworkMod. When you open this up it will ask for root permissions, give it. then use the "Flash ClockworkMod Recovery"
Now place unrevoked forever zip on your sdcard.
Open up Rom Manager again and select Reboot into Recovery.
Once in recover select "Install zip from sdcard" locate the unrevoked forever zip file and install it.
Now reboot your phone. Your phone is now completely rooted and nand unlocked. Congrats!! (Oh by the way, now that you have finished you might want to know you just voided your phones warranty. Should you ever need to return your phone make sure you revert all of these changes and go back to an unrooted phone before sending it in. There are guides for that, just look for them.)
Now we need to update your radio but first lets do a nandroid backup! These backups are great as they can save you countless hours of trying to return your phone to operable status after you screw it up (trust me, I found out about nandroid backup WAY WAY WAY after I should have, you should start with it earlier than I did)
Go back into Rom manager and find the "Backup current Rom" selection, select it. Now change the name of the backup to something like "stock rooted rom" that way you know what it is, the date and time stamped names never help me. Now click ok and let it do it's backup. This will take a minute. Once it is finished take a deep breath and relax, you likely just saved your future self many hours of frustration. Now reboot the phone it's time to update the radio.
Attention!!! DO NOT SCREW THIS SECTION UP!!! IF YOU DO, YOU WILL BRICK YOUR PHONE!!!!
(by the way, I am not responsible for any bricking that may occur due to not following this guide to the "T" Also I am not responsible for any bricking that may occur due to following this guide to the "T" You assume ALL of the risk for attempting any of this stuff)
Download the following radio update: http://adrynalyne.stfuthxbye.net/radio/2.15.00.07.28/PB31IMG.zip
Place it on your sdcard in the bottom directory.
Now shutdown your phone. Once your phone is powered off hold down the volume down button and the power on button. A white screen should appear and say something about HBOOT.
It will locate the PB31IMG.zip file on your sdcard and ask you if you wish to update with it, answer yes. (If it does not find the file then you need to shut your phone off, take the sdcard out and put it in your computer and save the contents off of the sdcard into a folder on your computer and format the card to fat32 then replace the contents back onto the sdcard, put it back in your phone and boot back into HBOOT and let it find the update and get to the point we are at now)
DO NOT, DO NOT, I REPEAT, DO NOT RUN THIS UPDATE MORE THAN ONCE!! IF YOU SCREW THIS UP AND RUN THE UPDATE TWICE, YOU WILL BRICK YOUR PHONE.
Once it is finished press the power button, this should change the list of options, you should now see a reboot option, reboot your phone. Congrats you now have an updated radio (and hopefully a phone that isn't bricked)
No go back into Rom Manager and select "Download Rom" Find the Cyanogen rom and download it. Make sure if it asks, you select to download google apps too, don't wana be stuck without those! Also when it asks, you need to do a wipe too, a backup isn't needed but if you are scared, you can do another backup anyway.
Once it is done downloading it should ask to finish or reboot, once you send it on it's way, it will do it's thing and reboot your phone and flash it with the Cyanogen rom. Reboot the phone and you now have Android Froyo 2.2, rooted, with loopback support, overclocked kernel with tons of optimization. Cyanogen's roms are VERY excellent, so enjoy.
Once all of that is done, you are ready to follow the guide at nexusonehacks.net to get ubuntu linux running on your phone.
Also if you have any SIMPLE questions, I may be able to help you with them, however if they are in any way complex, please be sure to scan the comments posted in his guide to find a solution and post your own comment in his guide should you be unable to find a solution already there. I am in no way able to provide complex support to help you get this working on your system.
Don't get me wrong, I do think it's cool but what will it do for me? I can't imagine navigating the gui on the incredible's small screen. Maybe the netbook remix. I've done quite a bit of terminal work and ssh on my Incredible and it sucks. I just don't see the advantage of it. I still need a device that is very user friendly and I can efficiently use as a phone.
I'll keep an eye on it and see how it develops but for now it's a no go for me. I would rather just carry my netbook around, even an ipad would be a better option. Ubuntu on an Ipad would be very cool to play with. I wish the ipad competition would hurry up and get here.
Thanks for an intriguing post and link.
gedster314 said:
Don't get me wrong, I do think it's cool but what will it do for me? I can't imagine navigating the gui on the incredible's small screen. Maybe the netbook remix. I've done quite a bit of terminal work and ssh on my Incredible and it sucks. I just don't see the advantage of it. I still need a device that is very user friendly and I can efficiently use as a phone.
I'll keep an eye on it and see how it develops but for now it's a no go for me. I would rather just carry my netbook around, even an ipad would be a better option. Ubuntu on an Ipad would be very cool to play with. I wish the ipad competition would hurry up and get here.
Thanks for an intriguing post and link.
Click to expand...
Click to collapse
Cuz ubuntu is the ****
sent from jdfroyo v2.0 EVO-lution
Well there are tons of Ubuntu programs that you could then run on your phone. For devs and such this could be invaluable, granted devs would already know how to install ubuntu on their phones and not need this guide, but meh. Personally for the rest of us, I am not sure what I am going to use my ubuntu for yet, but I like having the option there.
It is also a cool parlor trick to pull on iphone users. "Can your iphone run a full fledged desktop operating system? Hmmm... that's too bad, my android phone can."
It's especially helpful against those people you told to get an android phone over an iphone because of all of the advantages of the android phone and they got an iphone anyway because they are more concerned about making a status statement than actually getting the best. Just another log on the fire.
But really really, why do I run Ubuntu on my mobile phone? BECAUSE I CAN!!! Seriously, just because I can. Isn't that why a lot of us do these kinds of things?
Does it work or is camera worked?
sent from jdfroyo v2.0 EVO-lution
I am running the same ROM as you and when I tried to install it I get the following.
sh ./ubuntu.sh
modprobe: chdir(2.6.32.15-g936f68f): No such file or directory
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Junknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) mu
lti-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
Make sure you have the latest busybox installed. Also make sure you do an su command before you do the sh ./ubuntu.sh.
One other thing, you have done the unrevoked forever right?
To update your busybox install the busybox app from the market and run it.
Sent from my Incredible.
Yes I have the newest busy box and yes I did type the SU before. Here is everything that I typed.
C:\android\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: chdir(2.6.32.15-g936f68f): No such file or directory
←[H←[J←[H←[Jrm: can't remove '/system/bin/fsrw': No such file or directory
rm: can't remove '/system/bin/bootubuntu': No such file or directory
rm: can't remove '/system/bin/unionfs': No such file or directory
unknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-ca
ll binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
Make sure when you install busybox to your phone with the app that you install it to /system/xbin.
Sent from my Incredible.
Yes busybox has been installed to /system/xbin. I just looked into that directory and I see alot of busybox files.
Ignore the error messages. Now make sure you are still in root and type bootubuntu.
Sent from my Incredible.
If you look at the screenshot in his guide, the one of the command prompt you will notice he gets the same exact errors, apparently they don't matter.
Sent from my Incredible.
This is what I get when I type that.
# bootubuntu
bootubuntu
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/mnt/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/mnt/dev/pts: No such file or directory
umount: can't umount /data/local/mnt/proc: No such file or directory
umount: can't umount /data/local/mnt/sys: No such file or directory
umount: can't umount /data/local/mnt: Invalid argument
dadicus said:
If you look at the screenshot in his guide, the one of the command prompt you will notice he gets the same exact errors, apparently they don't matter.
Sent from my Incredible.
Click to expand...
Click to collapse
My errors are not exactly like his. He does not have these in his screen shot.
BusyBox v1.16.1 (2010-03-29 11:50:09 CDT) multi-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Please tell me your kernel version. Almost looks like your kernel doesn't support loopback devices in that first part. The rest almost looks like a permissions problem. Also just a quick confirmation here, you did do a full nand unlock right, with unrevoked forever? I doubt this would make much of a difference but what baseband are you running? Please answer each question.
Sent from my Incredible.
Well I do see one problem, you are running an older version of busybox than I am. Please download that busybox app from the market and update your busybox with it. Don't forget to make sure it installs it in /system/xbin it will give you a choice. Once done your busybox should be 1.18.0
Sent from my Incredible.
I gotta go finish my workout. I will be back in 15 minutes, please get that info for me, thanks.
Sent from my Incredible.
I am running 2.6.32.15-g936g68g the one that comes with CyanogemMOd 6 RC3
I just installed the new busybox into the location that you said and I got the same error. Yes I did the unrevoked forever so I do have S-off
Attempt to do the following again now that you have the new busybox.
su
sh ./ubuntu.sh
Sent from my Incredible.
This is what I get same thing. It is like it does not like the rm -f that is in the .sh file.
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: chdir(/lib/modules): No such file or directory
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Jrm: invalid option -- /
BusyBox v1.18.0.git (2010-08-11 01:17:17 CDT) multi-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Value too large for defined data type
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
I am no noob when it comes to rooting- I've had my D1 and Incredible both rooted manually.
However, I'm having some serious problems rooting the DroidX...
I have all the drivers and ADB software installed. This is the 3rd computer i've tried this on and i've been receiving the same errors.
Droid X
Froyo 2.2
1) when i try to adb push exploid to /sqlite_stmt_journals/exploid - i received an error message that says that there is no such file or directory.
instead i adb pushed exploid to /data/local/tmp - and went on from there.
2) I'm able to run ./exploid and even get to the rootshell- but then when i try to cp /sdcard/Superuser.apk /system/app/Superuser.apk - an error occurs that says /sdcard/Superuser.apk is a directory (not copied)
3) I also tried running the 1-click root for the DX - and it fails every time.
I'm completely stuck. Any ideas?
The Answer
To problems one: Where are you getting your information on how to root the X?
To problem two: Did you remember to mount the system to read-write (rw)? And to problem three: Try using this instead, if your on the official OTA of 2.2 FroYo, GO HERE!!!
The link above is what you need and it is the first post on the page.
Good Luck
-Cameron
*edit*
Apparently I'm not allowed to post links...
rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
*end*
got it
yeah i forgot to mount the system- started getting "read-only" errors- the rooting instructions that i was reading seemed to have left that out... :-/
Okay this little package has been the bane of my resoning with g++ and build essentials I found the fix for it as I was playing with 2.3.6 webtop and trying to fix synaptic getting stuck at preparing packages, still looking into it but this needs to get out there.
Okay problem:
libc6-dev cant install due to needing to overwrite package in rootfs
simple fix when you run into this download this and this
and from the terminal run:
sudo dpkg -i --root=/osh --force-all libc6-dev_2.9-4ubuntu6_armel.deb linux-libc-dev_2.6.28-19.66_armel.deb
and resume your stuck install:
sudo apt-get -f install
update: noted a linux-libc complaint from dpkg on my latest webtop setup, updated instructions accordingly.
This seems interesting. Does force install the package break dependencies?
Hi, i try but the error not gone... can you help me?
when i run sudo apt-get -f install the result is:
18 upgraded, 100 newly installed, 21 to remove and 107 not upgraded.
2 not fully installed or removed.
Need to get 0B/43.7MB of archives.
After this operation, 80.0MB of additional disk space will be used.
Do you want to continue [Y/n]? y
E: Internal Error, Could not perform immediate configuration (1) on libc6
The same error is present in every instalation and i cant install nothing
tks
I tried today to upgrade from 4.1.2 to 4.2.2 but it failed about 30% of the way through the upgrade and ended with the Droid on his back with a red x.
Its rooted but got stock recovery.
I did the same upgrade for my Nexus 4 to 4.2.2 from 4.2.1 and that upgraded fine.
What's causing the upgrade to fail?
Any help would be much appreciated.
Thanks
Jon
Sent from my Nexus 7 using XDA Premium HD app
look for the error message in /cache/recovery/recovery.log
If you comb thru the bigger threads on the 4.2.2 update....every imaginable problem and solutions are in there.
Sent from my cell phone telephone....
This is part of the log that shows the failure.
Any help would be much appreciated.
Thanks
Verifying current system...
failed to stat "/system/xbin/bttest": No such file or directory
file "/system/xbin/bttest" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
assert failed: apply_patch_check("/system/xbin/bttest", "07168ec97de36a7cca8b6867ad66937c6c6c1f4d", "2bb363a3f434d165d1167d915c2ba44967e22071")
E:Error in /cache/da55f917feee.signed-nakasi-JDQ39-from-JZO54K.da55f917.zip
Sent from my Nexus 7 using XDA Premium HD app
OK jonchill I will try to help out.
But only because you inadvertently disclosed a new OTA download (JZO54K->JDQ39) for nakasi.
Here's the deal:
The OTA process performs checksums on hundreds of individual files (and even partitions e.g. boot partition) before it begins any work. 100% of checksums must pass before anything gets changed by the OTA.
It's a safety feature meant to protect people from applying the wrong files to their tablets/phones. More importantly, the reason that it is done is because the OTA does not contain "replacement" files - it only has small binary "patch" files which can be used only in conjunction with the original file to create the intended replacement file. This is how OTAs can be so much smaller than a full ROM - the files already present are "patched" to create their replacements.
But the bottom line is that if *you* removed or altered any single file which is a target of the OTA patching process, these pre-installation checks will fail. (Even worse, it stops immediately - it is possible that you have more than one file involved in this. Because of this stop-on-first-fail behavior, you don't know yet whether or not there are more to come.)
When I say *you* I mean you personally plus any root-using apps which you installed and ran on your tablet. Could have been an app.
OK, now for the good news. I downloaded the OTA - thanks for providing the file name - and looked at the installer script; that installer script for JZO54K-> JDQ39 is shown here on pastebin. The file which your OTA is complaining about is "bttest" - and as it turns out, this check occurs on line 1040 - it is the third from last file checked. The only thing which comes after that is a check of
/system/xbin/dexdump
and
the boot partition ( EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX )
Now I don't have any idea what might have caused "bttest" to disappear from your ROM. On the off-chance that "dexdump" got deleted too, attached is a zip of those two files from the JZO54K distro.
This is not a flashable zip - it's just the two files. It's your responsibility to get them into /system/xbin/
Note their ownership info:
Code:
-rwxr-xr-x 1 root 2000 5448 Oct 2 14:49 /system/xbin/bttest
-rwxr-xr-x 1 root 2000 59828 Oct 2 14:49 /system/xbin/dexdump
If you restore them to /system/xbin/ make sure you
Code:
chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
chmod 755 /system/xbin/bttest /system/xbin/dexdump
I verified their SHA1 checksums (note these are the 2nd string of digits in the failing assert_check).
2bb363a3f434d165d1167d915c2ba44967e22071 bttest
e5e4d35038ed3e32a15194275806d90e64e003c6 dexdump
good luck.
I've downloaded the files and tried transferring them across to XBIN but it fails saying the folder isn't writable, I've tried changing the permissions on the folder but it errors saying can't set permissions.
What am I doing wrong?
Thanks
The /system partition is typically mounted "ro" - Read Only.
Root-aware file browsers typically have a toggle in their (root-related) menu to remount /system in rw mode, but you can easily do it yourself from the command line. (using a terminal emulator or adb). You just need to be root to do this. (Or you can just do everything in the custom recovery, in which case the /system mount point will be in "rw" mode by default)
C:\foo> adb shell
$ su
# mount -o remount,rw /system
(copy files into place, do chmods , etc)
# mount -o remount,ro /system
Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks
jonchill said:
Just tried a you suggested and it doesn't seem to want to put the system into RW. I've also tried changing the permissions through the file manager I've got installed and get the same result.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Read-only file system
255|[email protected]:/ #
Thanks
Click to expand...
Click to collapse
Well, that's odd. I'm not really sure why that is happening. You could fool around with the mount command a little bit or just avoid all this nonsense and do what you need via adb in the custom recovery.
If your bootloader is unlocked, but you don't want to *flash* a custom recovery (I see you said you have stock recovery), you can nevertheless temporarily *boot* one, and just that temporarily booted custom recovery as in:
- put device in bootloader mode
C:\fubar> fastboot boot name-of-custom-recovery-image.img
(wait until it is booted)
C:\fubar> adb shell
# mount /system
# cp /sdcard/wherever/bttest /system/xbin/bttest
# cp /sdcard/wherever/dexdump /system/xbin/bttest
# chown 0.2000 /system/xbin/bttest /system/xbin/dexdump
# chmod 755 /system/xbin/bttest /system/xbin/dexdump
# sync
# umount /system
reboot
I don't know how you originally rooted, but generally the adb connection from either custom recovery (TWRP/CWM) needs an additional USB driver (yes, even though you "already have ADB working with the normal OS"). I suppose most lazy folks use either a toolkit or the XDA Universal Naked driver for this. (No support will be given by me on driver installs - I need to draw the line someplace.)
good luck
Tried booting to a temp custom recovery (TWRP) and followed your instructions but still getting the Read-Only file system. At this stage would it be better to take a backup and re-flash a full image?
C:\NRT\data>adb shell
~ # ←[6n
~ # ←[6nmount /system
mount /system
~ # ←[6ncp /sdcard/bttest /system/xbin/bttest
cp /sdcard/bttest /system/xbin/bttest
cp: can't create '/system/xbin/bttest': I/O error
~ # ←[6ncp /sdcard/dexdump /system/xbin/dexdump
cp /sdcard/dexdump /system/xbin/dexdump
cp: can't create '/system/xbin/dexdump': Read-only file system
Thanks
Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?
bftb0 said:
Well that is bizarre.
Some boot kernel/ramdisk configurations use a "errors=remount-ro" mount option with ext4 filesystem that automatically prevents a "rw" mount if corruption was detected in the ext4 filesystem meta-data.
Although when the mount of /system succeeds in 4.2.2 stock I don't see that - this is what you get:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
I also don't see that option in use with TWRP 2.4.1.0 either:
Code:
adb shell cat /proc/mounts | grep system
/dev/block/mmcblk0p3 /system ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
It's just a hypothesis - but perhaps somehow your /system partition got damaged?
I am reluctant to continue giving advice since your device is behaving non-nominally. (I never used JZO54K, so I can't say for sure.)
It is possible that doing a dirty overflash of factory 4.2.2 (of only the boot partition & system partition) via fastboot would succeed, but I would feel a lot more comfortable about doing that in the sequence JOP40C->JOP40D->JDQ39 where you are converting a 4.2.x ROM to a later version. In your case though, coming from a 4.1.x ROM (JZO54K), that seems like there could be downstream problems.
The conservative route would be to take as many backups as you feel are appropriate, e.g. Nandroid + TiBu or Carbon, reinstall the full factory 4.2.2 stock (including bootloader!), re-root, and then restore your market apps & data (TiBu or Carbon). Note that because we have no idea what the changes/bug fixes were in the 4.18 bootloader update, you probably want to make sure you install the 4.18 bootloader first (and make sure to reboot to it!) before doing any of the subsequent steps (partition erasures & formatting, in particular).
I wouldn't do anything at all, though until I had succeeded making a full Nandroid backup and making sure I had a copy of it off of the tablet. Do your Nandroid backups succeed?
Click to expand...
Click to collapse
Thanks for all your help, as this is going to be quite a bit more complex than first thought I'm going to leave the above until I come back from holiday.
Thanks again.
You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.
GedBlake said:
You can always tell when there's a technical guru around... they use wonderful phrases like "...since your device is behaving non-nominally...".
bftb0, your posts, as ever, continue to be hugely informative and a delight to read...
----------
Hi, jonchill... (when you return from your holiday)...
Here's what I would try...
When I'm poking around in /system (usually for something more prosaic, like changing the BOOTANIMATION.ZIP), I use X-Plore File Manager (http://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en).
It's a ROOT capable DUAL pane file manager... so you should be able to copy the files directly into /SYSTEM/XBIN (setting one pane as your SOURCE, the other as your DESTINATION TARGET).
Once copied there, LONG PRESS on the respective files just copied, select PERMISSIONs from the context menu that appears, and set accordingly.
But first, you will have to go into CONFIGURATION>ROOT ACCESS and set X-Plore File Manager to SUPERUSER+MOUNT WRITABLE...
I have both these files (bttest and dexdump) in my xbin folder... and permissions for both are 755.
See my screenshots appended to this post.
Hope this helps...
Rgrds,
Ged.
-----------
PS. where did you get the OTA updater ZIP nakasi-JDQ39-from-JZO54K.da55f917.zip from? I've Googled around for it, but can't find it anywhere. Would be nice to have it in my collection.
Click to expand...
Click to collapse
Ged
The OTA was what I received automatically.
I've already got XPlore and have tried what you suggested but get Can't write to file /system/xbin/bttest can't move temp file to /system/xbin/bttest.
Thanks