I'm expecting to see the OTA show up any time now and I want to be ready for it. I'm running stock .181 rooted with bootstrap recovery. I've seen lots of threads with instructions for sideloading the 211 ICS update, and all say to use Matt's utility to start with clean version of .181 with no bootstrap. I'm willing to wait a day or a week or whatever for the OTA and don't see a need to rush and sideload ICS, so do those instructions still apply? I"m sure it's cleaner if I wipe everything before applying the OTA update, but I'd rather not spend the hours it will take to restore and recover all my apps and data and such if I don't have to.
So, do I have to rsd back to clean 181 to get rid of bootstrap recovery? Can I just uninstall the Razr Bootstrapper app? Any recommendations or advice would be appreciated.
Thanks!
OK. Found a simpler option than RSDing to re-install 181. I followed instructions to remove CWM posted at http://theunlockr.com/2012/01/24/how-to-install-bootstrap-recovery-on-the-motorola-droid-razr/ . I also un-installed the RAZR Bootstrapper app just to be on the safe side. I plan to back up root with OTA rootkeeper before installing OTA which I am hoping is soon.
Astrobrewer said:
OK. Found a simpler option than RSDing to re-install 181. I followed instructions to remove CWM posted at http://theunlockr.com/2012/01/24/how-to-install-bootstrap-recovery-on-the-motorola-droid-razr/ . I also un-installed the RAZR Bootstrapper app just to be on the safe side. I plan to back up root with OTA rootkeeper before installing OTA which I am hoping is soon.
Click to expand...
Click to collapse
I can't delete the files, I keep getting "error deleting file". Also am attempting to get in to adb shell using the utility and keep getting "the system cannot find the path specified". I have debugging enabled. Really getting fed up with this. I tried to use the utility to revert to at least a clean install of 181 and the path specified is never available. Root is good. Constant error messages.
Try opening the su app, then hit menu, then update your su binaries, then do it again, then open rom manager, or what ever app you may have, or boot into cwm and run fix permissions, reboot and try again, though, even if you remove bootstrap, if you've frozen, removed any bloat, or you/an app you installed altered your build.prop at all any update from vzn/moto will fail. Also I don't think ota rootkeepr works for going to ics. When you have root, ti backup and a nandroid are amazing time saving tools to have.
Sent from my DROID RAZR using xda premium
To delete/rename files using ES file explorer I had to go to preferences and check the root explorer option and the mount /system read/write option. Then all was good.
Sent from my Kindle Fire running Glazed ICS ROM
Astrobrewer said:
OK. Found a simpler option than RSDing to re-install 181. I followed instructions to remove CWM posted at http://theunlockr.com/2012/01/24/how-to-install-bootstrap-recovery-on-the-motorola-droid-razr/ . I also un-installed the RAZR Bootstrapper app just to be on the safe side. I plan to back up root with OTA rootkeeper before installing OTA which I am hoping is soon.
Click to expand...
Click to collapse
Can anyone confirm this method works? I would like to avoid rsd if at all possible. Wanna keep all my files / settings intact for the update.
Sent from my DROID RAZR using Forum Runner
Computer doesn't see your phone for adb? And you have the motorola usb drivers installed on the pc?
UrbanDroid said:
Can anyone confirm this method works? I would like to avoid rsd if at all possible. Wanna keep all my files / settings intact for the update.
Sent from my DROID RAZR using Forum Runner
Click to expand...
Click to collapse
I can confirm you do need to remove bootstrap. However, that method did not work for me to remove it to install the soak test. I'm not sure the reasoning, but the following steps:
[Removing CWM on Boot]
1) Delete file /system/bin/mot_boot_mode
2) Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
My phone did not have a mot_boot_mode.bin. I found an alternate set of instructions that did work and allowed me to receive the OTA soak.
This thread has the instructions I followed (also pasted below):
droidforums.net/forum/droid-razr-hacks/188690-how-remove-razr-bootstrap-custom-recovery.html
"I found a thread on DroidXForums.com by Abe21599, which suggested the following for a Droid X:
1. Reroot (If not currently rooted)
2. Get root explorer in the market
3. Uninstall the bootstrap app
4. Go into root explorer to system/bin
5. In top right corner tap r/w
6. Delete the file called hijack
7. Delete logwrapper
8. Rename logwrapper.bin to just logwrapper
9. Reboot and it should be gone.
(thanks to Droidforums member Hostility6)"
You also need to unroot, which I did with the Razr Utility 1.6. After all of this, I was able to install the soak OTA without any further issues!
The theunlockr.com article with instructions that I used referred back to a 12/18/2011 post by J.Y Daddy on xda, http://forum.xda-developers.com/showpost.php?p=20447149&postcount=47 . The instructions are pretty much the same as what brgr had but also have you delete the /preinstall/recovery directory. That may be why it didn't work for brgr.
Here are the instructions given in the J.Y. Daddy post:
It's complicated to remove.
Because, it must also be removed CWM recovery.
Follow the below with very careful:
Please work with RootExplorer.
[Removing CWM on Boot]
1) Delete file /system/bin/mot_boot_mode
2) Rename file /system/bin/mot_boot_mode.bin to /system/bin/mot_boot_mode
[Removing CWM Recovery]
1) Delete file /system/bin/logwrapper
2) Delete file /system/bin/hijack
3) Rename file /system/bin/logwrapper.bin to /system/bin/logwrapper
4) Delete directory /preinstall/recovery
Click to expand...
Click to collapse
I'm optimistic that it will work, but until I get the OTA I won't know. If it doesn't work out then I'll start clean with the razr utility.
Astrobrewer said:
The theunlockr.com article with instructions that I used referred back to a 12/18/2011 post by J.Y Daddy on xda, http://forum.xda-developers.com/showpost.php?p=20447149&postcount=47 . The instructions are pretty much the same as what brgr had but also have you delete the /preinstall/recovery directory. That may be why it didn't work for brgr.
Here are the instructions given in the J.Y. Daddy post:
I'm optimistic that it will work, but until I get the OTA I won't know. If it doesn't work out then I'll start clean with the razr utility.
Click to expand...
Click to collapse
I don't have the mot_boot_mode.bin file. Only the one without the. bin extension.
Will that make a difference to remove Bootstrap / CWM?
Thanks
Florestan2 said:
I don't have the mot_boot_mode.bin file. Only the one without the. bin extension.
Will that make a difference to remove Bootstrap / CWM?
Click to expand...
Click to collapse
Sounds like you didn't set up CWM to automatically run at boot, so you just skip the two steps in that section. As I understand it the mot_boot_mode.bin file is just a back-up of the stock mot_boot_mode file that is replaced when you run the set up to have CWM always come up when you reboot. To get rid of CWM on boot is to delete/rename to get the original file back. The stock version boots to your normal system ROM, the other version for CWM at boot boots phone to CWM. If you don't have a mot_boot_mode.bin file then just leave the mot_boot_mode file as is -- you definitely don't want to delete it.
I didn't set up CWM to come up automatically at boot, so I didn't have the .bin file either. It shouldn't matter because the mot_boot_mode file is the stock version (wasn't replaced to make CWM run at boot). Still need to do the rest of the steps to remove CWM recovery.
Hope this helps.
Good to know, that's what I was hoping for. I boot normally, not going into recovery first, so it makes sense.
Thanks
Ill let you all know how the OTA goes if and when i receive it. Just a waiting game now.
Sent from my DROID RAZR using Forum Runner
Moved To Q&A
Please Post questions in the Q&A section
Finally got OTA. I temp un-rooted with Voodoo before installing. Went very smoothly with no issues. After update i restored root with Voodoo and I'm back in the game.
Removing CWM using the steps i followed and temp un-rooting allowed OTA to work and let me keep root. Done.
Thanks
Sent from my rooted DROID RAZR MAXX
running ICS using xda premium
Related
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!
Install the ICS leak without Cheesecake and retain root
NOTE: Attempt this at YOUR own RISK.
That said, I have just easily installed the ICS leak (it is sweet), and retained root.
We have also confirmed thru multiple staffers you can fastboot back to .173
NOTE: We have no way of knowing if this will throw you off the official upgrade path.
Assume it will, so be prepared to fastboot back to stock if you upgrade now
All credit for the install goes to Vicious over at droidrazr.com
1) Download this torrent (LInk blocked till i get 8 post in this thread)
2) Make sure you have ROM Manager, ES File Explorer (Make sure root access and system writable are enabled in the ES file explorer settings), and have root access to your system but are on an otherwise stock COMPLETELY UNMODIFIED installation of 173. In ROM Manager, DO NOT INSTALL CLOCKWORKMOD. Just have the ROM Manager app itself installed.
2a) If you plan to have root after the update, make sure you have voodoo OTA Rootkeeper protecting your root before proceeding. (Install it, free in the market, open it and select protect root.)
3) Copy the 2 files from that torrent into your /cache folder on the root of your system (see the picss below, just press the indicated buttons in es file)
4) When the copy operation is complete, tap the zip file and select ROM Manager when it asks you what to use to open the file.
5) ROM Manager will automatically open and prompt you that a reboot is necessary to complete the operation. Hit OK/Accept.
6) The system will reboot and install the ICS leak.
REMEMBER Voodo OTA Root Keeper!!!
I would post link to the download but i need *8 post first so please help yourselves
Look 14 posts down Same info with links
http://forum.xda-developers.com/showthread.php?t=1575065
Why are you calling it official when it's the leak?
Ectoplasmic said:
Why are you calling it official when it's the leak?
Click to expand...
Click to collapse
It's a official leak lol
Sent from my XT910 using Tapatalk 2
What is this shenanigans?!
You're about 11 days and a ICS wrapper late.
Sent from my DROID RAZR using xda premium
PLEASE
please post the link
---------- Post added at 03:48 AM ---------- Previous post was at 03:47 AM ----------
Heres post #8 ...were jonesing for ICS !!!!
Please Please.... give me some Ice Cream!!! =)
COLoREDbyCHAoS said:
Install the ICS leak without Cheesecake and retain root
NOTE: Attempt this at YOUR own RISK.
That said, I have just easily installed the ICS leak (it is sweet), and retained root.
We have also confirmed thru multiple staffers you can fastboot back to .173
NOTE: We have no way of knowing if this will throw you off the official upgrade path.
Assume it will, so be prepared to fastboot back to stock if you upgrade now
All credit for the install goes to Vicious over at droidrazr.com
1) Download this torrent (LInk blocked till i get 8 post in this thread)
2) Make sure you have ROM Manager, ES File Explorer (Make sure root access and system writable are enabled in the ES file explorer settings), and have root access to your system but are on an otherwise stock COMPLETELY UNMODIFIED installation of 173. In ROM Manager, DO NOT INSTALL CLOCKWORKMOD. Just have the ROM Manager app itself installed.
2a) If you plan to have root after the update, make sure you have voodoo OTA Rootkeeper protecting your root before proceeding. (Install it, free in the market, open it and select protect root.)
3) Copy the 2 files from that torrent into your /cache folder on the root of your system (see the picss below, just press the indicated buttons in es file)
4) When the copy operation is complete, tap the zip file and select ROM Manager when it asks you what to use to open the file.
5) ROM Manager will automatically open and prompt you that a reboot is necessary to complete the operation. Hit OK/Accept.
6) The system will reboot and install the ICS leak.
REMEMBER Voodo OTA Root Keeper!!!
I would post link to the download but i need *8 post first so please help yourselves
Click to expand...
Click to collapse
I posted the 8th post yesterday. Can you unlock the link now Please?
MischiefsMommy said:
I posted the 8th post yesterday. Can you unlock the link now Please?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/1562-ics-anyone-i-haz-it-4-yew/
I flashed an ics leak with cwm recovery. Now I want to flash the eclipse rom with safestrap. I have no idea where to even start. Can someone help me out
ClicquotRose said:
I flashed an ics leak with cwm recovery. Now I want to flash the eclipse rom with safestrap. I have no idea where to even start. Can someone help me out
Click to expand...
Click to collapse
Is your device from Verizon? Are your phone working now?
Cheers
yes it is from verizon and it is working. I dont like this ICS rom because it messed up my data connection. I just want to switch to safestrap to load the eclipse rom
ClicquotRose said:
yes it is from verizon and it is working. I dont like this ICS rom because it messed up my data connection. I just want to switch to safestrap to load the eclipse rom
Click to expand...
Click to collapse
Dont know about eclipse but you can try miui
http://forum.xda-developers.com/showthread.php?t=1539901
Enviado de meu XT910 usando o Tapatalk 2
even this rom says to install with bootstrap. my problem is removing cwm to flash with a different recovery. i cant find enough info on google about it
Found this elsewhere on the forums, not my own instructions. The first method assumes you have ADB and know how to use it. The other set utilizes apps and can be done on the actual phone.
Removing Bootstrap Recovery:
Removal from an Androidforums post:
UNINSTALL the Recovery APK (Droid X Bootstrapper) in Settings, Applications
Reboot
Run "adb shell"
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
or
1. Be rooted
2. Get root explorer in the market
3. Uninstall the Bootstrap app
4. Go into root explorer to system/bin
5. In top right corner tap r/w
6. Delete the file called hijack
7. Delete logwrapper
8. Rename logwrapper.bin to just logwrapper
9. Reboot and it should be gone.
(thanks to Droidforums member Hostility6)
Then you are now free to install Safestrap and use it. I personally like safestrap because it gives you a bit more freedom. Keep in mind safe strap has a safe and non safe place for Roms. You should have your phone back to completely stock and rooted. Go into the Nonsafe section and back up your stock system. Then you can toggle over to the safe side and flash away all the roms you want.
thats what i seen on google but those are instructions for bootstrap. i have cwm. im not too comfortable following instructions for a different one
Similiar issue
Hello, I have a rather similar issue.
I have a verizon razr maxx, with eclipse installed via bootstrap.
I now want to install safe strap, and use eclipse as the non safe side.
I am able to install safe strap, and when I boot, I do get to the safe strap screen, and I do have an option to enter recovery. However, if I enter recovery, I only get a logo in the background, and have no options available. I have tried uninstalling safestrap, and then uninstalling the safestrap apk, and then using the method described tucstwo, however, it has no effect.
I am using safestrap 2.00, my system version is .173, and I am on eclipse 1.3.
Help would be greatly appreciated.
tucstwo said:
Found this elsewhere on the forums, not my own instructions. The first method assumes you have ADB and know how to use it. The other set utilizes apps and can be done on the actual phone.
Removing Bootstrap Recovery:
Removal from an Androidforums post:
UNINSTALL the Recovery APK (Droid X Bootstrapper) in Settings, Applications
Reboot
Run "adb shell"
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
or
1. Be rooted
2. Get root explorer in the market
3. Uninstall the Bootstrap app
4. Go into root explorer to system/bin
5. In top right corner tap r/w
6. Delete the file called hijack
7. Delete logwrapper
8. Rename logwrapper.bin to just logwrapper
9. Reboot and it should be gone.
(thanks to Droidforums member Hostility6)
Then you are now free to install Safestrap and use it. I personally like safestrap because it gives you a bit more freedom. Keep in mind safe strap has a safe and non safe place for Roms. You should have your phone back to completely stock and rooted. Go into the Nonsafe section and back up your stock system. Then you can toggle over to the safe side and flash away all the roms you want.
Click to expand...
Click to collapse
Thanks that actually did work and everything was successful
This phone has actually turned out to be everything i could ask for. Except there is one more problem. Everytime my phone is sleep for a while i actually lose all data connection. I don't have any smart actions enabled and my wifi is set to sleep never. This is very important to me. Any help would be greatly appreciated
One thing that I found out with Safestrap and Eclipse is that if you use Safestrap to flash Eclipse, when you connect your phone to your computer, you won't be able to ADB SHELL into it. When you do ADB DEVICES, it will show the device as offline.
The only way to get this fixed, per Nitro, is to fxz back to GB 2.3.6, root, install bootstrap and then flash.
Too bad. Safestrap does provide a nice way to switch.
iBolski said:
One thing that I found out with Safestrap and Eclipse is that if you use Safestrap to flash Eclipse, when you connect your phone to your computer, you won't be able to ADB SHELL into it. When you do ADB DEVICES, it will show the device as offline.
The only way to get this fixed, per Nitro, is to fxz back to GB 2.3.6, root, install bootstrap and then flash.
Too bad. Safestrap does provide a nice way to switch.
Click to expand...
Click to collapse
You are referring to eclipse for gingerbread. This is no longer an issue for eclipse ICS.
There are a few posts regarding rooting Canadian ICS Note. It seems there is a script in the OTA ICS upgrade that re-installs stock recovery (3e) after flashing CWM using ODIN.
Note: The offending script only exists in the OTA ICS upgrade, and not in update from Kies or samfirmware ROM.
If you don't have the offending script, then after Step 7, just reboot into recovery, install superuser ZIP from CWM, reboot, and you're done.
I'm summarizing the steps needed to flash CWM and root Canadian ICS Note:
1) Download Odin, CWM tar, and superuser zip (http://forum.xda-developers.com/showthread.php?t=1763896 Post # 3)
2) Install Odin
3) Copy superuser zip file to Phone
4) Start Odin and browse for the CWM tar file in the PDA section
5) Put the phone into download mode (VOLUME DOWN + POWER, then VOLUME UP)
6) Connect Phone to PC
7) Flash CWM with Odin
8) As the phone is rebooting, take out the battery. This is done to avoid the script install-recovery.sh from reinstalling stock recovery
9) Put battery back and boot into recovery (VOLUME UP + VOLUME DOWN + POWER, Release POWER after first vibration)
10) Install superuser ZIP from CWM, you are now rooted
11) Reboot phone
12) Install root explorer or ES File explorer and enable root operations and /system mount on them.
13) Find /etc/install-recovery.sh and rename it to install-recovery.sh.bkp
14) Repeat steps 4 to 7
15) Reboot. You should now have CWM and Root.
Thanks to SKyRocKeting727 and aleks07.
This could not have come at a better time...I was just sitting down at my computer to try this...Wish me luck
Success won't come from luck but it will from reading every step twice at least before any clicks or taps.
Thanks so much! Worked like a charm! Just finished nandroid backup of stock Bell rom with SU.
Getting ready to Try Flapjaxx UCLF6 rom.:good:
This thread should be stickied...
worked! thanks a lot
With ES File Explorer, I get "Sorry, operation failed" attempting to rename install-recovery.sh. I installed Terminal Emulator, and tried a simple
Code:
su
mv /etc/install-recovery.sh /etc/install-recovery.sh.bkp
to which I get "Read only file system"
I checked back in SuperUser, and ES Explorer (and Terminal) have root allowed; es file explorer has Root Explorer enabled in settings.
Ideas?
Edit: I realise the OP lists "install_recovery.sh", but I have no such file, just "install-recovery.sh". The contents are exactly what you'd think, though, conditional test to restore the recovery image.
Second Edit: I am an idiot. I missed "Mount /, /system as writable". Carry on, nothing to see here
THANKS MAN!!!!! it worked!
I've been trying for days to figure this out.
It appears I didn't have to do steps 12 - 15? My phone appears to be rooted and CWM is installed.:good:
Wintersdark said:
With ES File Explorer, I get "Sorry, operation failed" attempting to rename install-recovery.sh. I installed Terminal Emulator, and tried a simple
Code:
su
mv /etc/install-recovery.sh /etc/install-recovery.sh.bkp
to which I get "Read only file system"
I checked back in SuperUser, and ES Explorer (and Terminal) have root allowed; es file explorer has Root Explorer enabled in settings.
Ideas?
Edit: I realise the OP lists "install_recovery.sh", but I have no such file, just "install-recovery.sh". The contents are exactly what you'd think, though, conditional test to restore the recovery image.
Second Edit: I am an idiot. I missed "Mount /, /system as writable". Carry on, nothing to see here
Click to expand...
Click to collapse
Lol I was just gonna tell you to mount the system as writable.
Good luck, I just had to rename the file since I was already rooted.
I wonder if we rename back to the original than well get stock recovery again?
Easy way of doing it I guess.
hmm...
i didn't have to go through steps 12-15 because i couldn't find
the install_recovery.sh file so i just rebooted to see if CWM works
and it did also my phone was rooted.
is there anyone whose situation the same as mine?
and yes i am on ICS
ygong said:
i didn't have to go through steps 12-15 because i couldn't find
the install_recovery.sh file so i just rebooted to see if CWM works
and it did also my phone was rooted.
is there anyone whose situation the same as mine?
and yes i am on ICS
Click to expand...
Click to collapse
You'll find, though, that after you reboot into Android, CWM will be gone. You'll still have root though. To find the file in ES File Explorer, you'll need to go into ES's settings and enable:
Up to root
Root Explorer
/, /system write able
Then you just click up until you get to /, then click Etc, and install-recovery.sh will be in there.
ygong said:
i didn't have to go through steps 12-15 because i couldn't find
the install_recovery.sh file so i just rebooted to see if CWM works
and it did also my phone was rooted.
is there anyone whose situation the same as mine?
and yes i am on ICS
Click to expand...
Click to collapse
Yup exact same here!
Wintersdark said:
You'll find, though, that after you reboot into Android, CWM will be gone. You'll still have root though. To find the file in ES File Explorer, you'll need to go into ES's settings and enable:
Up to root
Root Explorer
/, /system write able
Then you just click up until you get to /, then click Etc, and install-recovery.sh will be in there.
Click to expand...
Click to collapse
yeah CWM is still installed...
even though i rebooted my phone
Yup mine is still installed after reboot too!
Sent from my SGH-I717R using Tapatalk 2
kwhit said:
Yup mine is still installed after reboot too!
Sent from my SGH-I717R using Tapatalk 2
Click to expand...
Click to collapse
I think it might be helpful in this thread to list which Canadian Carrier you are with to determine which ones have to take the additional steps...
I am with Bell Mobility and can confirm that, for me, it was necessary,,,,,,
I am greatful to the OP and encourage and any of you that were helped to hit the Thank You button from his post..
crutzulee said:
I think it might be helpful in this thread to list which Canadian Carrier you are with to determine which ones have to take the additional steps...
I am with Bell Mobility and can confirm that, for me, it was necessary,,,,,,
I am greatful to the OP and encourage and any of you that were helped to hit the Thank You button from his post..
Click to expand...
Click to collapse
You are with Bell, I am with Rogers, and my friend is with Telus, and we all had to do the renaming of the script. I'm not really sure why some have to do it and some don't. Also, not sure why AT&T Notes don't have to do it.
zaptor99 said:
You are with Bell, I am with Rogers, and my friend is with Telus, and we all had to do the renaming of the script. I'm not really sure why some have to do it and some don't. Also, not sure why AT&T Notes don't have to do it.
Click to expand...
Click to collapse
Were you rooted on GB before?
Just looking for common denominators....
crutzulee said:
Were you rooted on GB before?
Just looking for common denominators....
Click to expand...
Click to collapse
Myself and my friend with Telus were not rooted before on GB.
I'm on Bell did root my phone when I was on GB
Rogers, and I was rooted, but had reflashed to pure stock before upgrading to ics.
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
chicguy said:
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
Click to expand...
Click to collapse
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
If you are rooted then all you need to do is find a nandroid backup of previous jb and flash it. Then you use the trick to force the OTA. If you are not rooted then the only thing I can say is download the kdz, flash it, and wait for the OTA.
there are a few things that manipulate the system: link2sd, overclocking, busybox, custom recovery. . .My thing was the busybox. I totally forgot that I downloaded it and my update didn't work at first. Good Luck
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
TheCoutures said:
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Make sure MD5 sum is correct. The other stuff doesn't matter. You are flashing a full backup not an OTA which requires all stock apps.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the thanks button.
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
Wait you tried to install it as a zip
You are supposed to extract it and put the nandroid in the CWM backup directory.
sent from my locked rooted P769 v20D
I'm on YouTube (BioDesigner48)
I'm having the same issue, I do not have CWM or QSlide Remove installed, I've uninstalled all Root related apps and still encountering the same issue....
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
chicguy said:
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
Click to expand...
Click to collapse
Get the full P769BKv20f kdz file download here. Please be advised that this is just stock and if you flash this ROM then you WILL LOSE ROOT! But you can download and create a bin file to do the Lelus root method.