First, I do not have an Infuse. I am probably not an expert at ROMing but pretty close. Done it so many times on my DROID, Fascinate, NookColor, and now my Thunderbolt. But every phone/device seems to have their own unique thing going on.
I am trying to look into the ROMing world of the Infuse and it all looks standard. But I am having trouble figuring out the 3e Recovery. What is this about? I know with my Fascinate, I could not use the newest ROM Manager CW because of Voodoo and other reasons. Is that part of the reason why with the Infuse you have to go through these extra steps outside of flashing CW from ROM Manager?
He is not in a position to pay for Root Explorer as of yet. It seems you can install the Modded 3e through Terminal Emulator, correct? And THEN Flash ClockWork (i9000) through ROM Manager and boot into recovery like normal?
The ultimate goal is to install the Infused ROM. I got all the steps down except the first one--and since he can't use Root Explorer as of now, it may be more complicated. Any pointers here?
From what I understand, the stock recovery image on the Infuse (3e) will not allow you to install/flash unsigned .zip files. Modding the 3e recovery removes the requirement that zips be signed, letting you flash clockworkmod. I'm sure you've already seen this thread about installing modded 3e. If you aren't in a position to pay for root explorer, I'd suggest Super Manager instead. It worked fine for me when I modded my 3e. You don't need ADB or a terminal emulator either; there's an option in both root explorer and super manager to mount the system directory as read/write. Once you have the zip on your SD card, you shouldn't need your computer any more at all to finish installing modded 3e.
And yes, after that's done flash the i9000 CWM and it should be smooth sailing!
Thanks for helping out! That explains it perfectly.
Here is an issue I came across: We unzipped the recovery file and placed on SD card (I think it was like 307kb) and then I went and tried to copy it in /system/bin/ first with Terminal Emulator, then again with ADB. On the last step, I assume when I am pushing it to phone fromt he SD, it says it "cannot find" the recovery file.
Anyone come across something similar?
(I did download Super Manager and that seems like a nice option, I will see if that helps instead).
Eddog4DROID said:
Thanks for helping out! That explains it perfectly.
Here is an issue I came across: We unzipped the recovery file and placed on SD card (I think it was like 307kb) and then I went and tried to copy it in /system/bin/ first with Terminal Emulator, then again with ADB. On the last step, I assume when I am pushing it to phone fromt he SD, it says it "cannot find" the recovery file.
Anyone come across something similar?
(I did download Super Manager and that seems like a nice option, I will see if that helps instead).
Click to expand...
Click to collapse
Hm, that is odd. Dumb question, but are you sure you're pointing ADB/the terminal emulator to the right directory on the right SD card? Or is the recovery file properly named? Those are the only things I can think of.
Eddog4DROID said:
Thanks for helping out! That explains it perfectly.
Here is an issue I came across: We unzipped the recovery file and placed on SD card (I think it was like 307kb) and then I went and tried to copy it in /system/bin/ first with Terminal Emulator, then again with ADB. On the last step, I assume when I am pushing it to phone fromt he SD, it says it "cannot find" the recovery file.
Anyone come across something similar?
(I did download Super Manager and that seems like a nice option, I will see if that helps instead).
Click to expand...
Click to collapse
1) You must be root (e.g. rooted with SuperOneclick) to install the "modded 3e recovery"
2) Its permissions apparently must be EXACTLY the same as the original one for it to work - if it has MORE permissions than normal I've heard it may break!
3) I still haven't figured out why you need modded 3e recovery to flash CWM recovery - you should only need root to do so...
I forget my exact steps as I'm a bit of a Unix shell guru, but mine were something similar to:
1) SuperOneClick root
2) ADB shell into the phone
3) "su" within ADB (the superuser app will prompt on the touchscreen here)
4) in another terminal window on the PC (I'm a Linux guy... I can adb push while being adb shell'ed elsewhere), from wherever you have your modded recovery unzippped "adb push recovery /sdcard/recovery"
5) "cp /system/bin/recovery /system/bin/recovery.bak"
6) "busybox mount /system -o remount,rw" (for some reason, the default mount program is really crippled, gotta do busybox remount)
7) "cp /sdcard/recovery /system/bin/recovery"
8) "reboot"
Related
I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****
I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.
Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.
flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Thanks for this. worked out great.
willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3
mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..
that did it!! Thanks guys!!!
um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!
Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.
In the event something happens to your phone, -I'm- not responsible for the damages to it, you are. The end. I've personally tested this method and it works flawlessly.
This tutorial entails gaining full root access on your Evo. That means we -will- be unlocking NAND. But most importantly, we'll be doing it all without the use of a computer. Needless to say, this is going to take a while, especially if you don't have access to a wifi signal. The PC36IMG.zip files are rather hefty and are going to take at least 30 minutes to download. So I suggest you start downloading both of them now.
Prerequisites: Download Astro File Manager from the market. Open it up, hit the menu key on your phone, select more, select preferences, then scroll down and make sure Enable Browser Download is checked.
This is a template for you guys that'll explain to you how to move a file to the root of your SD card using Astro File Manager.
The files that you've downloaded from the links below are going to be located in the Downloads folder that is on the root of your SD card.
Unless you're using a browser like Xscope or Dolphin, then you'd have to navigate to the particular browser's folder that you're using, open it up and find the downloads folder in there.
When you first open the Astro File Manager app, you're going to be staring at what is the actual root of your SD card. Remember that.
Code:
When I tell you to move something to the root of your SD card, you're going to:
Locate and open the appropriate download folder that contains the file I am referring to.
Long press on the file.
Select Edit.
Select Move.
Press the Back key on your phone 'til you've reached the root of your SD card in Astro File Manager.
Click the Menu key on your phone.
Select Edit.
Select Paste.
When I tell you to rename a file you're going to:
Long press on the file.
Select Edit.
Select Rename.
Rename it accordingly and select done.
Step 1. Download this file http://link.geekfor.me/rootedromzip and move it to the root of your SD card.
Step 2. Power down your phone.
Step 3. Hold down the Volume Down and Power key simultaneously and keep holding it down until you've reached a white screen with 3 android dudes on skateboards.
Step 4. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 5. Once you've rebooted you will officially have root access. Just not full root access, we still need to unlock NAND.
Step 6. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. You can even delete it if you want.
Step 7. Download the mtd-eng.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802 And the flash_image.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
Step 8. Navigate to the root of your SD card and locate both of the .zip files you just downloaded. Open them, and long press on the files inside of them, then select Edit, then Copy, navigate back to the root of your SD card, press menu, select Edit, and then paste. Do the same thing for both files.
Step 9. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 10. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 11. Download the new PC36IMG.zip file here -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zipand move it to the root of your SD card, then rename it to "PC36IMG.zip" because the is named eng-PC36IMG.zip, which is wrong. Then power down your phone.
Step 12.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 13. Once your phone has rebooted, download the recovery.img file here - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img Then move it to the root of your SD card and rename it "recovery.img"
Step 14. Still know how to use terminal emulator? Open it up and type in these commands.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
You now have full root access as well as a legit recovery.
If you want to flash a ROM or the newest radio and you don't know how to do that, there's already guides for that. So I won't include that in my tutorial, just click here. http://forum.xda-developers.com/showthread.php?t=710513
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
PLEASE NOTE THE DONATION SUGGESTION IN MY SIGNATURE.
I must look like a douche what with the bold CAPS asking to note the donation link in my signature, which used to be a link to Dr. Cloverdale's paypal, not mine. Just thought I'd clear that up.
Reserved.
10 char
Great Work!!
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
adeyo said:
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
Click to expand...
Click to collapse
Legit, as in the most legit recovery on the scene, that being Amon_RA's.
Yup, got all three covered in that order.
Here's a link that shows you an in-depth guide on how to flash ROM's and what-have-you. http://forum.xda-developers.com/showthread.php?t=710513
No problem, man. Let me know how it goes for ya'.
Does this method still work with the latest OTA patch on 6/28/10?
Aren't you supposed to have Superuser Permissions after flashing the first ROM?
and you do get super permissions after you flash a CUSTOM rom....
what's your definition of 'CUSTOM'? This isn't my first time rooting, I unrooted lastnight and decided to try this method to see if it would work. I know for a fact that during the original rooting process the first PC36IMG you flash, you have Superuser permissions. And the second one that is flashed is the ROM to unlock NAND. However, doing this method, after flashing the first PC36IMG, I do not have Superuser permissions
However, it does seem that this method works. So I'm happy. It's good to know that I don't have to rely on a computer to root my phone now. Now the only thing I need to do, is figure out how to UNroot my phone without a computer.
Android believer, did you update to the ota update yesterday? Do you know if this works with the ota v1.47.651.1?
Sent from my Evo using XDA App
gordon1hd1 said:
Does this method still work with the latest OTA patch on 6/28/10?
Click to expand...
Click to collapse
I would assume it doesn't, as this is still toastcfh's method of rooting except it's done without a computer.
@ neckface
Hope you're not tired of hearing from me. First, thanks mass for this.
You say this is Toasts method without computer. I'm on the orig stock ROM, no 1.47 update. I WANT to do the update (for better battery mainly). I want to do whitslacks method. He says you need eng hboot 76.2000. He says use Toasts part 2 to get that.
Should I : use this to get eng hboot, then go to whitslacks for the 1.47 update? You seem to have a pretty good grip on this, so I thought I'd ask your opinion.
(if this is still Toastcfhs method, are these links to the same files he has posted? Meaning, will this get me eng-Hboot 76.2000? )
Thanks a lot.
anybody
Really interested in this. Anyone have success with this from 1.32 SW, and does it give you hboot 76.2000 ?
Thanks in advance.
Scott
OK i must be the dumb one
I have already used the "Unrevoked method" so I thought I could just skip to the Nand unlock. Now the phone(EVO) will not allow me access to my sdCard...and..will not read when I plug it up to my USB PC(windows) instead of it coming up as android like it use to it comes up as Qualcomm CDMA Technologies MSM(new found hardware wizard)....and the phone can only charge when the phone is powered off. Its like the usb is not responding and I can not have access to the SD card via teh device..i need advice
Thank you
Thank you,
I don't know if it was the wrong recovery.img or what, but I could not do a nand unlock. This worked great and did it all off the phone..... Awsome
I been trying to change my boot animation and I cant seem to get it right
I have downloaded "Boot Animation Changer LITE" and tried to change it. Now i have a different Droid boot animation that I do not want.
How can I change my boot animation with out these apps??
Also how to i revert to my old boot animation, I have a backup
ps. Im rooted on the Droid X 2.2
Bump. I would like to know this as well. I wonder if it is the same as the first Droid. Just replacing the bootanimation.zip file. Can anyone second?
bump bump
I think the easiest way to do so is to flash an update.zip...
Point me in the direction of your original boot anim and I might be able to fashion up an update.zip for you.
Unless I'm missing something, the Droid X doesn't have read/write access to /system while the phone is on in Android...Is that still the case?
Here is the really cool DroidX/Incredible bootanimation. I could not install it, though.
I got permission denied.
Please do fashion an update.zip!!
And try this, maybe it works for you. It's supposed to work, but it didn't for me.
Instructions
1. Download bootanimation.zip
2. Put it on the root directory of your SD card
3. Open the terminal app and enter:
su
cp /sdcard/bootanimation.zip /data/local/
reboot
Click to expand...
Click to collapse
Maltadev, here are the two boot animations you requested. They are in the same order as you posted.
Tell me if it works for ya.
Just to be safe, do a Nandroid backup before you flash these. You could probably use ROM Manager too, but IDK.
http://www.mediafire.com/file/gq8w5whz17gnkk0/bootanimation1-signed.zip
http://www.mediafire.com/file/9unu01nddwm5eoc/bootanimation2-signed.zip
Thanks, I managed to get it running, on eclair 2.2, and it looks HELL cool
I did this:
1. Paste bootanimation.zip to sd card.
2. Open a terminal and put in these commands
su
mount -o remount ,rw /system/
rm /system/media/bootanimation.zip -f
cp /sdcard/bootanimation.zip /system/media
Click to expand...
Click to collapse
and reboot. Worked for me
I will flush those updates for you though, just to see if they work =)
I tried renaming it to androidupdate.zip, but when I select "Install Update" in the menu it keeps looking for an "androidupdate.tar", and says "File not found".
Could you recompress it to .tar?
In rom manager or clockwork recovery?
Ahh sorry I misunderstood you - I didn't install any 3rd party programs, I just put the file in /andboot folder and when I rebooted I held the centerdpad and hit "Install Update"...
Do you know how to boot into recovery? That is what I'm talking about.
These bootanimations should be flashable via recovery. You need to manually select and update.zip like bootanimation1-signed.zip and confirm. It shouldn't throw any errors. If it works, reboot and watch your new animation.
Hello everyone. I have been working with android for a 6 months now and still cannot figure out what im doing wrong to get my permissions to work correctly. I have installed ADB and successfully rooted my MT3G Slide. I have been trying lately to figure out why i cannot manually configure A2SD. I have gone through both ADB Shell and Terminal under Su to try to mkdir /system/apps but it will give me a problem like my system is not allowing me to rewrite or its copy protected. I have tried to remount and it claims its successful. Another symptom i experience is not being able functionally use the rom manager or restart in clockwork recovery after i have flashed a rom. I always have to wipe the devices before i can loop hack back into clockwork mode. I have tried to fix permissions and restart in recovery through rom manager and it just brings up a question mark ontop of an image of a phone. I have been trying most recently to move a file through terminal to another name and replace the old with a new of the same name. It says the directory is not empty when i try to modify this file. So Anyone think they might know a solutions to these issues or hopefully all of them in one simple problem i cant seem to figure out.
download & install 'root explorer' for your phone from the android market (or your Pc, and put it on your phone) , grant it superuser permissions from superuser on your phone, open it up, and there's an option to make the phones memory R/W. (Its R/O as default which may be why your having permission issues)
Saying that Im yet to figure out adb's permissions fully..
Be careful with root explorer though, its a very intrusive programme which can screw up everything
Root explorer cost money... is there another program that allows me the same option. I have been using astro file manager, any way to do it on that one?
OK, so after fighting with my Nexus S 4G for three hours trying to get it rooted (it took 15 - 30 minutes for my Hero and Evo Shift) I finally established root and wanted to install ClockworkMod. Of course I've come to learn that it's just not that simple, and I have to rename the default recovery, which require r/w permissions, and just more hoops to jump through.
Long story short, I rooted, set r/w access and renamed install-recovery.sh and used ROM Manager to install ClockworkMod. Reboot to recovery, and all seems well. Except that the next time I reboot, I'm back to the default recovery, my renamed install-recovery.sh.old is no where to be found and low and behold, install-recovery.sh is back.
Considering how easy this was with HTC devices... I'm starting to get a little pissed off.
Anyone have any idea why I can't maintain ClockworkMod?
Why don't you just use fastboot and flash the recovery image? It will be permanent if you do that... It takes about ten seconds.
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
If you're sure you did the renaming properly and after that the file got restored back, I'd suggest you trying to trick the system by making a backup of the original install-recovery.sh and then instead of renaming it, just delete everything in that file so you still have the file named install-recovery.sh which will do noting to the recovery partition
radadev said:
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK... tried this. No go.
Reboot still shows the default and not clockwork.
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
jungbum said:
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
Click to expand...
Click to collapse
This is the first thing I tried. No dice.
Sophos1 said:
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
Click to expand...
Click to collapse
I don't see an "install-recovery.bak"
Stupid question, is your bootloader still unlocked?
wild1z said:
Stupid question, is your bootloader still unlocked?
Click to expand...
Click to collapse
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Shadodragon said:
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Click to expand...
Click to collapse
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
wild1z said:
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
Click to expand...
Click to collapse
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Shadodragon said:
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Click to expand...
Click to collapse
I can only tell you what I would do. I would try to get it back to stock and lock it up to start over.
Maybe JasonMahoney, AOSP and Lilduce will come on over and share this fun with us.