**THE USUAL WARNINGS APPLY**
1/11/11: Updated CWR to 3.0.0.5. Now installs properly through ROM Manager. Nandroid backup works, don't know about restore. Not sure if partition wiping is working I would assume it is. Flashable zips from SD card are working, tested with Quickie OC kernel (HIGHLY RECOMMEND!!!). Attached the CWR 3.0.0.5 image to this post, it is not a flashable zip just the image file zipped. So we have some real progress. w00t!!!
1/2/11: Looks like CWR has been released for NC. I didn't see it up see here you go. Easiest way to get it installed is by downloading ROM Manager in the market and flashing it through the apk. Attached is the .zip, I believe you just rename it "update.zip" and put it on the root of your SD card. Then reboot into recovery. Again your best bet is to use ROM Manager. Link to website: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Awesome, will try this later today, thanks for bringing it to attention
Afraid i cant thank you from my nook, but rest assured i eil soon
install failed here, too.
Failed for me too....
Sent from my Nooted Rook XDA App
Not ready for prime time yet. You need to install uRecRam to use it. give it a day put so for out to be automated. At least that is where it was last night when I went to sleep.
Sent from my rooted droid x
As per the previous post. This is not ready yet and could result in a bricked NC.
http://nookdevs.com/NookColor:Building_Clockwork_Recovery
Unable to post url's
Also I don't think it is backing up all partitions.
Sent from my rooted droid x
Failed me too. Started the process and then failed. Looks like it is close though. Pretty exciting.
WOW, this is great news. Seems like real soon we will be able to make backups.
Awesome. Not too long now until ROMs start getting put together. Hope the teardown reveals working Bluetooth.
Here are the steps to actually making this work if you are the adventurous type. This may brick your device blah blah. I am not responsible, etc. You should only attempt this if you genuinely understand the commands you are performing.
Make sure neither /media or /sdcard are mounted in your OS!
Save this:
http://koush.tandtgaming.com/test/clockwork-b3-nook-uRecRam
adb push clockwork-b3-nook-uRecRam /media/
adb shell
su
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mkdir /system/boot/
mount -t vfat /dev/block/mmcblk0p1 /system/boot
cat /system/boot/uRecRam > /system/boot/uRecRam.bak
cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam
umount /system/boot
rmdir /system/boot
Now do the three fingered salute to get into CWM Recovery. VolUp/Down are up/down, respectively. The Nook/home button is Select and the power button is Back.
@Mistar Muffin
worked for me
starkruzr said:
Awesome. Not too long now until ROMs start getting put together. Hope the teardown reveals working Bluetooth.
Click to expand...
Click to collapse
That would be awesome!
Great job,
I tried to compile a scrip with the following but it doesn't work if i put it in a batch file but it works if I run it from DOS. Go figure...
Code:
adb push clockwork-b3-nook-uRecRam /media/
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell mkdir /system/boot/
adb shell mount -t vfat /dev/block/mmcblk0p1 /system/boot
adb shell "cat /system/boot/uRecRam > /system/boot/uRecRam.bak"
adb shell "cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam"
adb shell umount /system/boot
adb shell rmdir /system/boot
I will work on the batch for the community to run so it make it easy for noobs...no ETA
Would installing this hose the ability to factory reset (the 8 failed boots/bootcnt method)?
Flashed and it works.
Yes you will loose that ability in it's current state.
I do not recommend using this until it has the capability to backup all of your data. At this point an error can still leave you with no return path, you have been warned!
Edit: Scratch that. I see what I did.
Even if it might not be wise for most to use this yet, very happy to see this available. Looking forward to nandroid . . .
I saw that the nook color comes up in rom manager, does this mean we don't need to install that other file uRecRam.
Sent from my LogicPD Zoom2 using XDA App
Related
so my screen recently stopped displaying anything,and im probably gonna send it in to verizon ASAP. is there a way to unroot the device using somthing like adb?
theblorg said:
so my screen recently stopped displaying anything,and im probably gonna send it in to verizon ASAP. is there a way to unroot the device using somthing like adb?
Click to expand...
Click to collapse
RUU10chars
theblorg said:
so my screen recently stopped displaying anything,and im probably gonna send it in to verizon ASAP. is there a way to unroot the device using somthing like adb?
Click to expand...
Click to collapse
If you can't see the screen, then neither can Verizon. By the time your phone gets to a repair facility (which might not even happen at this point), nobody is going to care who the prior owner of the phone was. Something to consider.
But, since you asked, here's a couple of alternatives.
(1) Try using the "Official" 2.1 RUU -or-
(2) Manually install the Leak-V3 ROM via adb [SIZE=+1]with Amon_RA booted[/SIZE]:
(a) Unpack the Leak-V3 PB00IMG.ZIP file on your PC. (Note that Windows native "compressed folder" zip implementations may not work because of the way that HTC signs the PB00IMG.ZIP files; iirc 7-zip should work, and certainly Linux/cygwin versions of "unzip" will work)
(b) Push the following individual files (unpacked from the PB00IMG.ZIP) to your sdcard:
Code:
adb push recovery.img /sdcard/
adb push boot.img /sdcard/
adb push system.img /sdcard/
adb push userdata.img /sdcard/
(c) Start a shell on the phone with adb ("adb shell")
(d) In the adb shell on the phone, perform the following steps, exactly as shown here. ( Do not type them - cut and paste, one line at a time )
Code:
mount /system
mount /data
mount /sdcard
flash_image boot /sdcard/boot.img
cd /system
rm -rf /system/*
unyaffs /sdcard/system.img
cd /data
rm -rf /data/*
unyaffs /sdcard/userdata.img
flash_image recovery /sdcard/recovery.img
cd /
sync
umount /data
umount /system
umount /sdcard
cd /cache
rm -rf /cache/*
exit
That's it. (You might see an error during the " rm -rf /cache/* " command, or complaints about the "lost+found" directory with any of the rm commands, but that's OK)
The "unyaffs" command will take some time with the system.img file - it's a big file (~160 MB); just let it go until the unyaffs command prints a message that it is finished.
Note that "flash_image" is already part of Amon_RA - you don't need to transfer it to the (booted) Amon_RA.
bftb0
bftb0 said:
If you can't see the screen, then neither can Verizon. By the time your phone gets to a repair facility (which might not even happen at this point), nobody is going to care who the prior owner of the phone was. Something to consider.
Click to expand...
Click to collapse
great info to know. im still probably gonna unroot it, just in case. thanks for the great post.
bftb0's the man!
This method is a pain in the butt, http://forum.xda-developers.com/showthread.php?t=926749here is a better method!
PERFORM AT YOUR OWN RISK! (I will clean this up as I have more time)
Okay! I have seen several threads on here regarding getting Nookie Froyo working off EMMC. Here is my take on it, I have spent time psuedo bricking my Nook Color over and over, and bringing it back to a factory state. Also all credit for this work goes to the people who actually got all this to work... I am simply compiling the information needed to make this as simple as possible.
First things first… If you make your device not-bootable… it is not the end of the world! Thanks to samuelhalff you can simply just recover using CWR and his recovery image from http://forum.xda-developers.com/showthread.php?t=914690&highlight=emmc . (To make things easier you can get a CWR image that is bootable from your SD card to assist with this from here: http://forum.xda-developers.com/showthread.php?t=922870 .) Please be advised that after the recovery you MUST factory restore Data using the power + n method!
Prereqs:
1. Ubuntu 10.1 (this is what I am using and can verify that it works with no issues.)
2. ADB working over USB.
3. A micro SD card of at least 2gb (more than one helps speed things up!)
4. IOMonsters bootable SD CWR (http://forum.xda-developers.com/showthread.php?t=922870)
5. Nooter 0.2(Thanks Pokey9000, and MBM!) (http://www.mediafire.com/?cfddu9wt9d8dunl)
6. Modified boot files for Nookie Froyo (http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2 )
7. Nookie Froyo 0.5.9 (http://forum.xda-developers.com/showthread.php?t=883175)
8. The factory boot image (http://forum.xda-developers.com/showthread.php?t=919353)
How to:
1. If you are not already completely stock please do so now. (including wiping data.)
2. Boot from your SD card into Nookie Froyo 0.5.9
3. Configure your display to timeout at 30 minutes (so you have time to type this all in!)
4. Type the Following in your adb shell:
adb shell mount -o remount,rw /dev/block/mmcblk1 /
adb shell
mkdir tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
cd tmpfolder
rm -r *
cd ..
cp -r system/* tmpfolder
umount tmpfolder
mount /dev/block/mmcblk0p1 tmpfolder
exit
adb push [folder-containing-extracted-boot.zip] tmpfolder
adb shell
umount tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
exit
adb push [folder-containing-extracted-volds.zip] tmpfolder/etc/
adb shell
umount tmpfolder
rm -r tmpfolder
exit
5. Turn your NC off and take out the sd card and pop it into your computer and image Nooter 0.2 onto it.
6. Boot your NC up with Nooter 0.2
7. SSH into your NC from the console (sudo –s root console) with the following command “ssh [email protected]” (if you have to reconnect and you get an error about keys type: “ssh-keygen -R 192.168.2.2”)
8. Eject your sd card (unless you have 2) and put (copy the file, do not image boot.img to the sdcard!) the factory boot.img file onto the sd card (might need to use gpart to wipe out the card and format for fat32, pop it back into your NC.
9. In the ssh console type:
mkdir sdcard
mount /dev/mmcblk0p1 sdcard
cd sdcard
dd if=boot.img of=/dev/mmcblk1p1
10. Power off NC and remove sdcard.
11. Reboot NC and hold down power + n to factory restore data.
12. Boot from your nooter card again the same as before.
13. Once booted, eject your sdcard from the nc and load up the modified boot files from nookie froyo. (just place the files in the root of the sd card)
14. Put the sdcard back into your nc and type:
mkdir sdcard
mount /dev/mmcblk0p1 sdcard
15. Then mount your boot partition and backup the existing files:
mkdir boot
mount /dev/mmcblk1p1 boot
cd boot
mkdir bak
mv * bak
cd ..
cp /sd/* /boot/
16. Reboot your NC and enjoy Froyo on EMMC!
Until I read to part 7 I was thinking of trying this on windows. Have ubuntu also but don't have sdk on it. And not sure of how to get sdk on ubuntu. Can this be done on windows? What if I did 1 threw 5 on windows sdk,then finished it up with ubuntu?
Wondering the same...no Ubuntu here...just Windows 7 (32 & 64 bit). Hoping someone can verify Windows works.
I must say, I followed it up to step 9, and I get totally lost in the weeds from there..
I also suggest this lives in the NookDevs wiki, as it's easier for folks to tweak and make it easier to understand, add info etc to it there.
What if I di 1-5 on windows then the rest with the terminal emulator on the nook? That is if nooter preinstalls emulator.
At step 9 u need to open up an ssh tunnel via the console in ubuntu..if you go on nook devs under rooting they have an ssh connection tutorial... this could be done in windows if you had an ssh client and the dd package or something similar.... however the process at this point in time is fussy and works well on ubuntu 10.1 after i do some more tweaking i may just zip up the premade image...
Sent from my Nook Color (zoom2) using Tapatalk
ericman77 said:
What if I di 1-5 on windows then the rest with the terminal emulator on the nook? That is if nooter preinstalls emulator.
Click to expand...
Click to collapse
Not sure on that... nooter only provides a ramdisk and allows ssh and adb....
Sent from my Nook Color (zoom2) using Tapatalk
U go to the same place as to get it for windows... u could do ur adb stuff in windows and the ssh stuff in ubuntu
Sent from my Nook Color (zoom2) using Tapatalk
K thanks think I will try that then.
I somewhat successfully used this method. However, I had some issues with step 9 since I am on Mac OS X. I could not mount my sdcard at all. No matter how I formatted the card, the system type could not be identified. Nonetheless, I was able to boot into Froyo and just completed the rest of the guide within Froyo.
*Corrections Needed to Guide*
Step 9: Error on mount point. Should be "mmcblk1p1" and not "mmcblk0p1"
Step 14: Mounts are incorrect again, they need to be reversed (sdcard & boot)
Can someone give me a hand...in step 9 where is says 'mount /dev/mmcblk0p1 sdcard' it says file directory doesnt exist. When i list the files i see mmcblk0 so i use that one. when i go to do the "dd if=boot.img of=/dev/mmcblk1p1" i get boot.img does not exist. LS on that shows that the file isnt there. I wrote the boot.img to the sd card and the files that are part of the show but not the image i burned. Can someone get a little more direction on that part. Thanks...
something must be kooky with my NC as i literally copied and pasted this stuff into my console and got it to run... well as long as its working! (maybe people should double check the mounts prior to imaging....)
modembug said:
At step 9 u need to open up an ssh tunnel via the console in ubuntu..if you go on nook devs under rooting they have an ssh connection tutorial... this could be done in windows if you had an ssh client and the dd package or something similar.... however the process at this point in time is fussy and works well on ubuntu 10.1 after i do some more tweaking i may just zip up the premade image...
Click to expand...
Click to collapse
Well, not that I didn't understand the commands, just I can't quite figure out what 9 on is doing
so on step 9 prior to running those commands you need to Place the file onto the sdcard, do not image boot.img to the sdcard... you need the actual file so when you are in the shh console you can dd the image file to that partition... make sense?
I am working on a flashable zip file that should simplify this process greatly.... Stay tuned!
modembug said:
so on step 9 prior to running those commands you need to Place the file onto the sdcard, do not image boot.img to the sdcard... you need the actual file so when you are in the shh console you can dd the image file to that partition... make sense?
Click to expand...
Click to collapse
Yup makes sense ... had been at it for your 5... several went down for two hours. Then had issues with rndis driver but good now that was going to be my next step in the morning. Thanks... will continue where I left off.
Sent from my DROIDX using Tapatalk
I'm looking forward to the flashable version!
Sent from my LogicPD Zoom2 using XDA App
having some issues with the flashable zip... still working at it, just need to replicate these steps in the script... Hopefully later today ill have something
I need a way to manually delete the files in /boot and in /system instead of formatting those partitions in CWR... I think if that was done instead it would prevent the bootloop..
Windows
You should be able to do this in Windows.
Use:
Putty forSSH.
http://www.chiark.greenend.org.uk/~sgtatham/putty/
Win32 Disk Imager to write images to SD Card.
https://launchpad.net/win32-image-writer/+download
Ok...im am on the last two lines....this is what i am getting
when i type mv * bak...i get can't rename 'bak' invalid argument.
I checked and bak is there with files in it.
when i do cp /sd/* /boot/ i get can't stat '/sd/*' no such file or directyory
i have even tried changing sd to sdcard and still nothing. I see the steps should copy from the sdcard to the boot directory, but keep getting that error. thanks for any help you can provide. Everything up until that point works perfectly;
It seems that nobody is talking about deodexing the Droid X2. Just thought I would let everyone know that xUltimate 2.2.8 works on the Droid X2 with the newest drivers installed. I am currently manually deodexing my root GB Droid X 2.
Some Members Might Not Wanna Take The Risk. With All The ROMs Are Already Deodexed. Me Personally I've Had That Program Downloaded Since The First Time It Was Posted And Have Used It Numerous Times. Now That You Mentioned This, You Should Go Bump That Thread.
If anyone can instruct me on how to successfully create an update zip I would gladly do it for those that don't want to take the risk of deodexing manually. But I am really shocked that a deodexed GB is not in the TBH App and no one seems to be talking about it.
I'm Gonna PM You A Few Websites To Learn How To Do It.
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
dimitri407 said:
Am I doing something wrong? I am trying to use the adb commands to copy everything over from the done_app and the done_framework folders but it is saying: CP: /sdcard/done_app/* when I run cp /sdcard/done_app/* /system/app
These are the commands that I am trying:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
You Need To Manually Transfer Them Over USB First. Both App And Frame Place Them On Your SD Card.
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
dimitri407 said:
They are both on my sd card. Actually they are on the external sdcard and the internal sdcard. That is what seems so weird about the error. The files are there. Is the command wrong for the Droid X 2?
Click to expand...
Click to collapse
When You Did "su", Did You Grant The Superuser Request On The Phone?
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
dimitri407 said:
Yeah. You have to do that initially to be able to use the mount command. Is the mount command my issue by chance?
Click to expand...
Click to collapse
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
I can't figure it out either. I did this to my Droid X with no problems. But the Droid X 2 just wants to be a pain when I am trying it.
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
I am wondering, since it is not working in adb shell then could I do it in the terminal?
MikeJ92YJ said:
There's Nothing Wrong With Your Code As Long As The Two Folders Are On The Root Of The SD Card. I Have No Idea What Is Wrong When The Information You Provided Is What You're Actually Doing.
Click to expand...
Click to collapse
So I finally got everything to work but to do so I had to copy the done_app and the done_frame folders to /data/local/tmp then run the cp commands.
For some reason, I could not get to the SD Card or the External SDCard.
you both need to quit hijacking threads and grow up. If I was the mod I would ban both of you.
Sent from my DROID X2 using XDA App
mistawolfe said:
Lol. You beg for 'em. Signature...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Can we please stop hijacking my thread. This is suppose to be about Deodexing the Droid X 2.
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
dimitri407 said:
Well I am suprised to report that since deodexing my stock pre-rooted GB, my battery life has been much better. Will have to see what it is like at the end of the day.
Click to expand...
Click to collapse
Oh God Yes. It's Gonna Faster And Smoother. The Point Of Deodexing Is It Recompiles The Odex Inside The Apk For Easier Themeing And The System Is Able To Read The Apks Faster. Definitely Gonna Help Battery If The System Isn't Working As Hard.
when you connect USB, you MUST be in "charge only" mode w/ usb debugging enabled. ANY OTHER MODE will fail to allow complete access to /sdcard or /sdcard-ext...
or at least that was my experience.
I'll Challenge That I Used PC Mode To Run The Deodex App And Then To Transfer The Completed Files Without Switching Modes. Anytime I Run ADB Operations My Phone Is In PC Mode.
I will check both settings today. But by mounting the partition, it should become available either way. But we will see.
I'm trying to push files to /system via ADB. However I'm having problems (getting permission errors). I am running Eclipse 2.0.2, so yes, my phone is rooted, I have su and busybox.
Phone is connected to PC and is set as "USB Mass Storage".
USB Debugging is ON
Here is my CMD log:
Code:
C:\android-sdk\tools>adb remount
remount failed: Operation not permitted
I tried to remount and it failed
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to
'/system/myfile.apk': Read-only file system
I tried to push, and got a READ-ONLY FILE SYSTEM error (keep this in mind)
Code:
C:\android-sdk\tools>adb shell
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
I try to push inside of ADB shell. Nothing again...
Code:
$ su
su
# mount -o remount,rw /dev/block/mtdblock4 /system
mount -o remount,rw /dev/block/mtdblock4 /system
# exit
exit
I go into SU and attempt to remount the /system
Code:
$ adb push C:\myfile.apk /system
adb push C:\myfile.apk /system
adb: permission denied
$ exit
exit
I go back up to ADB shell and try to push again... same error as before
Code:
C:\android-sdk\tools>adb push C:\myfile.apk /system
failed to copy 'C:\myfile.apk' to '/system/myfile.apk': Permission denied
I go back to the main command line and try to push again. This time I get PERMISSION DENIED. This error is different than before.
Any help on the matter?
I've read about ro.secure needing to be set to 1, but I need to edit the boot.img in order to do this, correct? Does that require an unlocked bootloader? Is root ADB even possible on the DX2.
Thanks!
I am no expert (don't even know if i know enough to b called a newb) but maybe try a root explorer. I use es file explorer because it's free. In settings check root explorer and mount file system. I received similar errors and this solved my problem.
Sent from my DROID X2 using XDA App
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
wesf90 said:
I'm familiar with root explorer, it's easy. I'm wanting to be able to use ADB though. Your post made me try something new though. I plugged my phone into my PC, then went into root explorer and mounted everything as RW. But, still was unable to push via ADB. Thanks for the reply though
So, how can I get ADB working?
Click to expand...
Click to collapse
I was using adb also and had similar problems. After i changed those settings i was able to push a file. I had to have system mounted.
Sent from my DROID X2 using XDA App
No luck on my end :/
Sorry i couldn't be more help. I am new to adb and may have done more to get it working. I'm sure there's someone else around here that can help u out.
Sent from my DROID X2 using XDA App
Make sure there are no spaces in the file path to your android-sdk folder. Can't say if this is your issue but its worth a shot as it has always caused weird problems with android development since day one.
Sent from my DROID X2 using Tapatalk
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
CadenH said:
Ro.secure is in your local.prop on the root of your phone. As far as your issue you have to reset permissions in order to push to /system. I saw that you were trying to do that but with no success. I believe I know what will help but I will have to find it and repost.
http://forum.xda-developers.com/showthread.php?t=1133528
Ok look at the command lines at the bottom of the op. You are going to use adb shell. Follow that almost exactly but adjust according to your directories. Should go into adb shell, gain su permissions, mount /system rw, push your apk, then don't worry about remounting as ro, just reboot. Pay close attention to spaces.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
wesf90 said:
Took me a few days to be able to getting around to trying this, but it didn't work :/ I'm still getting all of the same errors. The /system just doesn't seem to want to mount as RW (even though it is possible when using root explorer).
As for ro.secure in my local.prop, I'm able to edit this but it resets on reboot because (from what I've read) this is a file generated by the kernel
Anyone else have ideas?
Wes
Click to expand...
Click to collapse
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
ashclepdia said:
Moon shadow has a post in development to mount system rw
It's some type of script u run before adb or something
I don't know anything bout adb
But I do know he created it for this reason
Check it out
It's prolly got the info you need
Click to expand...
Click to collapse
Thanks for that! It's not quite what I'm aiming to eventually do, but did give me more insight on how the whole adb/shell/su systems work. From inside of su, I was able to mount the /system as RW, however I'm only able to do this from inside of SU. I want to be able to do this from the initial CMD so that I can ADB PUSH from my computer to the phone.
Here's my latest log:
Code:
C:\android-sdk>adb shell
[[TRYING TO MOUNT FROM ADB SHELL]]
$ mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: Operation not permitted
[[TRYING TO MOUNT FROM ADB SHELL USING BUSYBOX]]
$ busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount: permission denied (are you root?)
[[GO TO SU]]
$ su
su
[[MOUNTING AS RW SUCCESSFUL]]
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
[[COPYING A FILE INSIDE /SYSTEM SUCCESSFUL]]
# cp framework/framework-res.apk framework/framework-res-test.apk
cp framework/framework-res.apk framework/framework-res-test.apk
[[REMOUNTING /SYSTEM AS RO]]
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
[[ATTEMPTING TO COPY AGAIN, FAILED]]
# cp framework/framework-res.apk framework/framework-res-test2.apk
cp framework/framework-res.apk framework/framework-res-test2.apk
cp: can't create 'framework/framework-res-test2.apk': Read-only file system
#
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Maybe its because im tired but im confused as to why it wont let you push your files if you have remounted as rw. At that point it should be cake. You gained access to system by remounting it as rw successfully already.
Sent from my DROID X2 using xda premium
wesf90 said:
So now the question is, how do I mount as R/W so I can use ADB push?
Wes
Click to expand...
Click to collapse
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
I'm no expert in ADB, but I had run into the same issue as you and for me the fix was to go into ADB SHELL , then type SU to get SU access, then type exit twice to get out of shell completely. Then I tried pushing the APK and it worked fine with no read only errors.
This worked for me on my SGS2, could work for you ! Goodluck !
Come to IRC and I can help you with this. http://webchat.freenode.net Come to the #cm7dx2 channel. I'm usually there... Look for the nick(s) Moon|Work|(something), Moon|Home|(something), or MoonShadow-NM. If the (something) says Busy, I might not answer right away. If it says Away, I'm away from the keyboard and you won't receive a response until I return.
Ciao!
Any update
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
I've got a better idea to fix your issue brotha!
From my nexus tappin the talk
<edit post successful>
hellhunter said:
did you ever get this figured out? I'm having the same frustrations on mine. Mine won't install the 2.3.5 update due to it not recognizing the Quickoffice.apk and I'm trying to push the files manually, but I'm having no luck getting past the same you've posted here.
Click to expand...
Click to collapse
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
From my nexus tappin the talk
<edit post successful>
jamesh0317 said:
Try:
Code:
adb devices
adb remount
adb push [filename] [destination]
adb reboot
the "adb remount" remounts the fs RW instead of the default RO.
Click to expand...
Click to collapse
This won't work with Eclipse since it's not using 2nd init. I asked this question in the Eclipse forums and Nitro responded with the following:
Not without using 2nd init. All of that works due to being able to load its own init.rc which starts services and passes parameters, etc.. during boot time. It is possible to make a stock rom use 2nd init. CM9 will not even have root enabled by default. The only other way to push stuff is to enable root shell prior to pushing.
Click to expand...
Click to collapse
I know that CM7 allows using the adb remount, but that's because it's using 2nd init. I had also asked the question about why CM7 defaults to root shell when you adb shell into it and that's why he mentions how CM9 won't have root enabled by default.
The way I push to Eclipse is to run root explorer on my phone and mount the directory r/w. Then, I can use "adb push" to the phone.
ashclepdia said:
Do this
Sbf to 2.3.4
(or 2.3.3& take one ota To get to 2.3.4...however you want to do it..just be bone stock 2.3.4 )
Root your device.
BUT DO NOT USE ZERGRUSH TO ROOT
Use petes Motorola one click root method.
Then continue the process as normal from there on out.
Trust me in this. Zergrush root method is not playing nice with your /system partition, (if you notice during the root process it might say something like "making room in system,"= or "moving/deleting app to make room" something similar)
And when it does that, it's messing up how the update checks for untouched stock apps.
Let me know how it goes.
This solution has worked for COUNTLESS others so far, zergrush has always been the culprit when it comes to failing to find certain apk or system file that needs to be there for the update to install.
Click to expand...
Click to collapse
I think I may have tried that in one of my iterations. Originally I had it rooted with One-Click and then I was having issues with the 2.3.5 OTA update (quickoffice.apk) and at this point I've SBF'ed and rooted it probably 5 times this week so far. Rooted with both One-click and zergRush at various times. Actually I think every time except this last time has been with one-click. So I don't think that has seemed to make a difference for me so far. I can try it again, but if there's any other advice to throw out in the mean time, I'll take it.
Alternatively, I may take the new phone (the first replacement they sent had 2.3.5 on it, but a bad menu key causing the phone to flip out), load Titanium Backup on it, backup all the system apps and restore them to my original phone. Worst case is I have to SBF it again. But that seems like a logical process since I will have two phones available.
I was running Bricked Kang but installed the new build of cherry but now the old bricked rom's kernal is still a boot option, how can i remove this kernal from my touchpad and delete the entry in moboot?
I had the Bricked installed myself, and decided to go back to the stock CM9 kernel (since I was having FC issues with certain apps).
Here's what I did:
Open up Terminal Emulator
Type the following:
Code:
su <enter>
mount -t remount,rw /boot <enter>
cd /boot <enter>
rm uImage.CM <tab> <enter> (press Tab until the CM-Bricked is filled in)
echo "CyanogenMod" > moboot.default <enter> (this will set you back to defaulting CyanogenMod. If you want another, use the name of the uImage.<whatever> for Cherry (just put everything after the uImage. part)
reboot <enter>
That'll remove the Bricked Kernel from your boot options, and set your default to Cherry (or in my example, CyanogenMod). Make sure you have the proper Wifi modules installed from your Cherry install, and you should be good to go.
Hope that helps, mate.
I'm having the same problem and that proposed solution did not work...I got a Read only file error...thanks, though...
You have to make sure you mount the /boot partition before you try and do the changed. If it isn't mounted, you get that error.
Sent from my cm_tenderloin using xda premium
ve6ay said:
You have to make sure you mount the /boot partition before you try and do the changed. If it isn't mounted, you get that error.
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Could you elaborate on how to do that please? The CM_Bricked thing has been bothering me as well.
Thanks in advance!
I had the exact problem and instead of playing around with the instructions I just went to a backup I had before the install.
It worked like a charm for me. If you have a recent backup on CWM don't hesitate to use it .