Picked up a FRG83D updated Nexus One- easiest way to root on Mac? - Nexus One General

As the title suggest, I have a 2.21 based Nexus One. And I use a Mac. Is ther an easy way to root it?

ajaffarali said:
As the title suggest, I have a 2.21 based Nexus One. And I use a Mac. Is ther an easy way to root it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2

He's right. There is nothing really different about the mac rooting process since the SDK tools are generally the same.

efrant said:
http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
Click to expand...
Click to collapse
This guide was for the main 2.2.1 update. Since the last time that post was edited, there was a second 2.2.1 OTA pushed, which I believe was a small fix for adjusting partitions or something similar and gave a slightly different build number. You know if this still works for FRG83D?

Xel'Naga said:
This guide was for the main 2.2.1 update. Since the last time that post was edited, there was a second 2.2.1 OTA pushed, which I believe was a small fix for adjusting partitions or something similar and gave a slightly different build number. You know if this still works for FRG83D?
Click to expand...
Click to collapse
Rooting by the method quoted works on all Android builds to date.

Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.

ajaffarali said:
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
Click to expand...
Click to collapse
The guide is prob missing a step. Make sure you change the permissions on busybox to allow it to run before you try using it. Try chmod 755 busybox

ajaffarali said:
Ok- finally found some time for this but I'm getting a permission error at the step:
./busybox cp busybox /system/bin
Everything above that works well but when I reach this step, it messes up.
Click to expand...
Click to collapse
Make sure you actually did get root, I had to run the first step a few times until I got the root prompt on my friends phone.

efrant said:
The guide is prob missing a step. Make sure you change the permissions on busybox to allow it to run before you try using it. Try chmod 755 busybox
Click to expand...
Click to collapse
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with

ajaffarali said:
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
Click to expand...
Click to collapse
First thing to do after rooting is to make a backup. You would be surprised as to how many people forget to do this.

ajaffarali said:
Thanks! That did the trick. Nexus One is now rooted. Now to make the hard decision on which ROM to flash it with
Click to expand...
Click to collapse
First, flash any custom recovery if you already hadn't.
Then make a nandroid backup. It's a 'must' so you can go back if custom ROM flashing goes wrong. Also, backup your applications and their data is recommended.

Related

Programs missing from market with RUU 2.1

I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
jlem26 said:
I noticed earlier that m:zombie and m:vampire are not in the market. Any other programs that any of you have noticed are missing?
Click to expand...
Click to collapse
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
regaw_leinad said:
it's because the ruu is signed with test keys, not the release keys, so not everything is showing up.
Click to expand...
Click to collapse
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
jlem26 said:
That's what I figured but these are the only two apps I have seen missing so far. I was just wondering if anyone else came across more.
Click to expand...
Click to collapse
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
spatel9114 said:
Most of my purchased apps are gone, and they include Basketball, Toss It, Flight Control, and a few others..quite disappointed as I did the RUU install via the .exe file and so far, haven't found a way to undo it and go back to DamageControl 2.1...
Click to expand...
Click to collapse
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
lol very,very true!
RUU has test-key. thats means no protected apps. You should have flashed one of the many roms based on this RUU(damage,fresh or darchlegend even though its based on the Legend RUU). There already set to go.
Anyway I can do that now?
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
jlem26 said:
Lol, not to sound like a jerk but we knew this. I started the thread because I was wondering if anyone else knew which programs were affected. The whole idea behind loading the RUU was to test it out. It would be great if everyone didn't come in here and tell us how we should have loaded a custom ROM. Most of us probably came from a custom ROM to this, like myself.
Click to expand...
Click to collapse
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
regaw_leinad said:
Sorry, that was just your first post to the forum, and it had no implications that you knew how to do anything whatsoever. I was just going on what I read from your post. I was guessing you just joined and saw the RUU and flashed it. I am sorry.
Click to expand...
Click to collapse
Don't be sorry, I wasn't really aiming that at anyone in particular, I was just hoping to head off the thread turning into a point and laugh at the RUU users.
spatel9114 said:
Anyway I can do that now?
Click to expand...
Click to collapse
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Well I modified the build.prop last night and now all the apps are showing up in the market.
jlem26 said:
Well I modified the build.prop last night and now all the apps are showing up in the market.
Click to expand...
Click to collapse
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
MILH0U5E said:
Wow, is this easily done? I'm missing root manager, but otherwise am liking the leak (minus sprint crap).
Also.notice quick boot isn't working, but I'm sure its fixable, I just haven't looked or may not have the experience to get it going.
Click to expand...
Click to collapse
Yeah it is pretty easy, just need to get your build.prop, then in wordpad, if using windows use wordpad not notepad, just have to make a few changes. After that you clear the market cache. When I did this last night, none of the protected apps showed up, however this morning they all did. So for reason it may take a bit to work right but it did work. Just checked and root manager is showing in my market too.
I'll just post one I found online. If you adb push this to /system/ it should work.
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
@Kcarpenter, maybe dont post inflammatory stuff like this and instead be helpful and we wont have drama?
@Jlem
Good to see you got it going. You should share your build.prop (or link to instructions) so others that may have made the early (and quite risky) install of the RUU could get it going. That would be a nice thing to do
Personally I think you're crazy for trying that RUU!!! hahaha ! I'm glad someone did, and I hope it all works out for you.
edit:And you did! good work
Kcarpenter said:
Not to laugh about this, but maybe if that RUU had been kept hidden in the bowles of someones computer that wouldn't have happened. This is what drama does....
Click to expand...
Click to collapse
+1 Truth.
I have a feeling many people will do this.
danknee said:
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
spatel9114 said:
Alright, so when I go to do that, I get an error "Read-Only File System"..How can I make it read/write?
Click to expand...
Click to collapse
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
jlem26 said:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
or adb remount first.

Ivan 0.8 with full market

Not my work, sed took ivan's rom and added the the sholes fingerprint.
Full Market should work fine in it now.
http://www.multiupload.com/X0LZ3W1RSL
Awesome. Thanks for uploading this.
jcase said:
Not my work, sed took ivan's rom and added the the sholes fingerprint.
Full Market should work fine in it now.
http://www.multiupload.com/X0LZ3W1RSL
Click to expand...
Click to collapse
Thanks sed .......
and jcase
are there a few specific files that were changed so i could manually push those instead? done my own customizing and, if possible, would like to avoid pushing all those edits again
but thanks for the work
gohamstergo said:
are there a few specific files that were changed so i could manually push those instead? done my own customizing and, if possible, would like to avoid pushing all those edits again
but thanks for the work
Click to expand...
Click to collapse
For existing roms, use my script.
jcase said:
For existing roms, use my script.
Click to expand...
Click to collapse
ah alrighty. ill search for it. since i dont see a link in the OP.
edit: got it. twas in the later pages of your market fix thread.
EDIT2: flashing over an existing Ivan .8 with a dalvik-only wipe works great. got all my previously purchased apps now and no apps wiped
gohamstergo said:
ah alrighty. ill search for it. since i dont see a link in the OP.
edit: got it. twas in the later pages of your market fix thread.
EDIT2: flashing over an existing Ivan .8 with a dalvik-only wipe works great. got all my previously purchased apps now and no apps wiped
Click to expand...
Click to collapse
Without it working, I'm 1" away from doing a wipe.
Some claim success without a wipe, some say they need it, and some say they wait a couple of days.
I'm playing the waiting game.
gohamstergo said:
ah alrighty. ill search for it. since i dont see a link in the OP.
edit: got it. twas in the later pages of your market fix thread.
EDIT2: flashing over an existing Ivan .8 with a dalvik-only wipe works great. got all my previously purchased apps now and no apps wiped
Click to expand...
Click to collapse
I tried a dalvik-wipe then flash but I still couldn't find tapatalk in the market. I had to do a full wipe.
pkopalek said:
I did this, exactly, only using dalvik, from my existing 0.8t2.
adb shell
su
cd system
cd app
rm -r VVMStub_v3.apk
.... says it's Read Only.
trying to chmod it, can't it's Read-Only (despite my superuser access)
All in system/app is Read-Only. I can't even chmod.
Can't remove VVMStub_v3.apk
teeter.apk
com.android.launcher2.apk
that's all I tried, then I quit and I flashed my nandroid restore point back to the original 0.8t2 from BEFORE market fix.
Now I can manipulate my apps again.
Click to expand...
Click to collapse
you forgot to mount
adb remount
adb shell
rm -r /system/app/VVMStub_v3.apk
that's it
Using the Market Fix Ivan's ROM. Having an issue with app updates now.
About 1/2 a dozen of apps had updates pop up for me today. The update would download then go into "install" then return an "insufficient memory" error. Strange thing is that if the update was 700kb or less, the update would install. Larger updates like Handcent (~1.7M) would error out.
An uninstall and redownload/install of the problematic apps would work so I wasn't stuck other than resetting up apps like Handcent.
jcase did try to help me on IRC but I'm a tard when it comes to trying to copy/paste from the cmd window.

Busybox update.zip for incredible?

Does an update.zip exist for the incredible to add busybox to a stock rooted Rom? Or is there anyone willing to make one? I found one for the hero where they stripped down a rom and just left busybox, apps2sd, and Su. It would be greatly appreciated by many noobs like myself.
Sent from my ADR6300 using XDA App
I believe Stericson has an app out that installs busy box for you with a single click. Just search "Busy box" in the market and it should come up. Not sure as to whether or not it works on the Incredible, as I've an Evo, but it should.
I tried that but it failed saying either I it couldn't remount or I wasn't rooted.
Sent from my ADR6300 using XDA App
bradatz said:
Does an update.zip exist for the incredible to add busybox to a stock rooted Rom? Or is there anyone willing to make one? I found one for the hero where they stripped down a rom and just left busybox, apps2sd, and Su. It would be greatly appreciated by many noobs like myself.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I think the unrevoked tool installs it for you.
I'll try that again, but I used 3.0 to root it. Maybe 3.1 will install it, I thought that was only windows fixes from 3.0
maybe
kind of a rookie here, but couldn't you just install titanium backup and then click the problems button. I think it downloads and install busybox??
Nice call!!! Worked like a charm. Thx.
NO
ejkeebler said:
kind of a rookie here, but couldn't you just install titanium backup and then click the problems button. I think it downloads and install busybox??
Click to expand...
Click to collapse
Wouldn't be permenant since NAND is still locked. Would lose it after reboot and have to do same thing over and over after every reboot.
http://www.unrevoked.com/incredible/payload-update.zip
Apply this payload-update.zip and it will install busybox. Just go to recovery and choose install zip from SD card and then choose this one
Then to test
go to cmd prompt
type adb shell
then when in shell type
busybox and you will see its now installed.
If you want the latest busybox, I've attached 1.16.2 freshly compiled.
One issue I ran into was that all the info on the forums has busybox being installed in /system/xbin. The PATH variable has /system/bin before /system/xbin, so that means the original symlinks to "toolbox" are getting picked up first - I don't know if I'm the only one who was annoyed by ls -al returning "-al: No such file or directory"
I guess "toolbox" didn't support this, so you can either install busybox to /system/bin, or leave it in /system/xbin and create a symlink called toolbox in /system/bin that points to busybox in /system/xbin.
As usual, backup your "toolbox" binary first before removing it from /system/bin.
Now ls -al returns a correct listing and I see no app breakage by the symlink method - Ti Backup runs just fine without needing to install its own busybox.
*edit - I guess this doesn't really answer the OP, but I figured I would share this anyway.
ok so I found a side effect - WiFi doesnt work after this. There seems to be a problem with dhcpcd and the new busybox, even though external dhcp support was compiled in...guess I've got some digging to do...
http://codehydra.com/Dinc/RootStock/roto-rooter.zip
that is a busybox install I ripped out of a N1 froyo root update.zip Cyanogen did, modded for the D-Inc.
Seems to work well for me.
the easy way is just to install titanium backup from the market and then click problems and it will install busybox for you in like 5 seconds
Not Really
... but it does NOT install the newest busybox; just one which is compatible with Titanium Backup.
Busybox.net shows v1.17 is the latest (unstable) release, and v1.16.2 is the latest stable. Titanium Backup pushes something in the v1.15 area.
http://www.busybox.net/
Also when I did it through titanium and went to busybox to install latest it said my system had none.
I have a busybox 1.16.2 version that I ripped from one of the posted ROMs that I can attach. It works on the Inc, and I think the whole DHCP / resolv.conf thing works too. At least it's the only version I tried where I can get wget working properly. You may need to create /system/etc/resolv.conf with some valid nameservers first though. Let me know if you want me to post it.
Hmm, nevermind. I tried with the busybox version I have, and WiFi does not get an IP address. Seems to be the same problem.
If you track it down, when you compile your version check if wget works properly also. There were some issues with that and DNS lookups. Don't forget you may need a valid resolv.conf.
Joe92T said:
the easy way is just to install titanium backup from the market and then click problems and it will install busybox for you in like 5 seconds
Click to expand...
Click to collapse
I second this , I used ones off the rooting forums and it never quite worked right until I let titanium backup install it for me. Also its much easier than pushing files to your device if you are unfamiliar with doing it, because you can download tb from market and it does the work for you
Sent from my ADR6300 using Tapatalk
Easiest way to stay current is to install the Stericson app. It can't install it for you due to the NAND lock, but
1) It's trivial to extract it and install manually from the .apk file.
2) It will give you an easy notification via the marketplace that a new version is available.

How to confirm I have unrooted?

Okay unfortunately 5 mins after rooting my phone I noticed my replacement Vibrant has a bad screen. I used the one-click program to root, so I did the same thing to unroot. I downloaded ROM Manager after I unrooted to confirm the phone was unrooted and ROM Manager seems to think so (it told me to root my phone).
However, I am wondering if there is any way to *confirm* my phone has been unrooted (i.e. manually look for the root files and make sure they are not there)? I ask because I reset my phone to factory settings after unrooting, but updated.zip and chromemod folder were still present when I looked under files, which sort of scared me into thinking T-Mobile may be able to detect I had rooted.
Thanks for all the help and wish me luck for my *third* Vibrant.
DarkAgent said:
Okay unfortunately 5 mins after rooting my phone I noticed my replacement Vibrant has a bad screen. I used the one-click program to root, so I did the same thing to unroot. I downloaded ROM Manager after I unrooted to confirm the phone was unrooted and ROM Manager seems to think so (it told me to root my phone).
However, I am wondering if there is any way to *confirm* my phone has been unrooted (i.e. manually look for the root files and make sure they are not there)? I ask because I reset my phone to factory settings after unrooting, but updated.zip and chromemod folder were still present when I looked under files, which sort of scared me into thinking T-Mobile may be able to detect I had rooted.
Thanks for all the help and wish me luck for my *third* Vibrant.
Click to expand...
Click to collapse
You can test this to un-root.
https://www.dropbox.com/s/pyg5sypm9qto7rw/Galaxysroot.apk
I wrote it today. with help.
its posted on another thread.
Erm.. couldn't you just download Terminal Emulator (if it already isn't installed) and type in: "su" (without quotations)
zephiK said:
Erm.. couldn't you just download Terminal Emulator (if it already isn't installed) and type in: "su" (without quotations)
Click to expand...
Click to collapse
^^I second this, if you are not rooted, you will get a "su not found" type of error.
Also in this thread http://forum.xda-developers.com/showthread.php?t=728471 you will find
How to unroot
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
you could also do it from adb.
rhcp0112345 thanks for the app but I think the su way sounds easier.
Thanks zephiK and d_bot! I did the su thing and got a "su not found" error so I guess I am good.
Lakjin said:
rhcp0112345 thanks for the app but I think the su way sounds easier.
Thanks zephiK and d_bot! I did the su thing and got a "su not found" error so I guess I am good.
Click to expand...
Click to collapse
Yep, no su, no root
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
30Glock said:
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
Click to expand...
Click to collapse
Well, I know there will probably be a lot of people freaking out on me, but from how I use my phone the only use I've had so far is using cachemate to clear cache, and possibly modding the look of the os. I personally used to it to remove the annoying tmo boot and shutdown sounds/video.
30Glock said:
New to Andriod, sry for noob question, What are the benefits to Root, What changes on your phone??
Click to expand...
Click to collapse
Welcome to Android 30Glock
the main benefit of rooting is to be able to remove bloat-ware. Bloatware plagues the vibrant. Besides that there are other things you can do like custom roms(not many for the vibrant but they will come), with custom roms comes custom themes, also you can increase you cpu frequency. There are a few awesome apps out there that require root (Titanium Backup).
Basically think of it as you have just been given a new windows machine at work, and the admin gave you User permissions, so yeah you can do some cool stuff, but to really get in and have some fun you need admin permissions. To root/unroot this phone it is jaw dropping easy! Thank you samsung. Thank you DEVS!
Install Root Explorer and try to navigate to your system folder.
Moved to general section.

[Q] .sh script help

Hey guys, need some help with this one from some of you with more android/linux experience than me.
In my continuing quest to make Blackhole as customizable as possible I've been working on a way for users to easily install paid apps (legally downloaded of course), and stuff that I don't have available in rom manager in one easy step at the same time the rom is installed. In pursuit of this goal I've found that it's possible for the update-script file inside a clockworkmod zip to call a script in the zip as well. I've gotten it to say it's run the script, but it doesn't do what it's supposed to. here's what i've got:
#! /bin/
busybox cp /sdcard/app/* /system/app/
When I type the command into a terminal on the phone it works. When I open an adb shell and type "bash install.sh" it works. But when I get the update.zip to run the script, or run it in root explorer it just says it's run it, but doesn't do anything.
Is there something I'm missing about how to call the script? Do I need to somehow add the bash program to the zip file so it can run the script right? Has anyone ever done something like this who can point me in the right direction?
do you have an output you can show us?
Sent from my SCH-I500 using XDA App
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
wizang said:
This is a shot in the dark but does writing to /system/app require root permissions? It could be that you've given your terminal app root, so it runs under su. But when the script is being executed it does not have root and fails, but perhaps the output is being held back a bit and you're not seeing the permission denied.
Click to expand...
Click to collapse
Could very well be, it's not showing me any output when i run it the two ways it doesn't work, just says it's been run.
vegittoss15 said:
Steve_ ?!
whoa, didn't expect it to be you of all people
Anyhoo, this is a bit off topic, but I've got a small request, can you somehow make BlackHole 2.4 an option on Rom manager? I don't have DL09 so I can't use 3.0, but I really like the ability to select everything to customize, instead of me going and installing one thing at a time....
Click to expand...
Click to collapse
Haha, caught me. I was trying to remain incognito Yeah, i'll get 2.4 loaded back up on rom manager for you today. But if you flash 3.0 it will upgrade you to DL09 and the DJ05 kernels and modem are compatible, or at least no one i know of has had issues.
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
sdcard is mounted when you go to recovery, because it's got to access the update.zip file on it to install anything. I'll try your code, do you know what to put after SYSTEM: to make it go to the /app directory? thanks for the idea, it's a different way to go, i didn't think about the fact the update-script could access the device if you don't use the "package" tag.
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
dcow90 said:
Don't you need to add "sh" to the bin directory and define the script as so:
#! /bin/sh
if you want it to execute properly..
Click to expand...
Click to collapse
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
imnuts said:
Why not just add the following to the end of the update-script:
Code:
copy_dir /sdcard/app SYSTEM:
Also, is the SDCard mounted by default when the phone boots to recovery? If it isn't, or it isn't mounted while the update is processing, that will also cause the problem.
Click to expand...
Click to collapse
Well I gave that a shot, and i think it could work, but the recovery wouldnt do it. it says "non-package source path not yet supported" good idea tho.
yutsoku said:
I made a script to do this forever ago on my G1 when it first came out... Let me see if I can find it.
Click to expand...
Click to collapse
If you can that would be great.
n0yd said:
This has been done lots of times before. If you look around on xda there are some backup scripts which do the same thing.
Sent from my SCH-I500
Click to expand...
Click to collapse
I spent a good bit of time searching and most of the scripts I found were much more complex than what i need, or were written to run on a computer, which i've already done.
sonofskywalker3 said:
normally yes, but there doesn't seem to be a /bin/sh directory on my fascinate, only /bin and that's where the cp and mv and cat, etc. are.
Click to expand...
Click to collapse
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
jt1134 said:
Thats not the point. You need to set a shell interpreter, not a path. Cwm uses busybox sh, which is in /bin in recovery mode. Google search shebang
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
sonofskywalker3 said:
Going to go ahead and parade my stupidity in front of everyone here:
so does that mean i'm right using #! /bin/ or that it should be #! /bin/sh/ or something else entirely? I'm so confused.
Click to expand...
Click to collapse
#!/bin/sh for scripts in recovery. #!/system/bin/sh for scripts in android.
Sent from my SCH-I500 using XDA App

Categories

Resources