I was following a guide to remove boot strap recovery, said to delete hijack in the system/bin folder and logwrapper, then rename logwrapper.bin to just logwrapper. Now I had hijack and logwrapper, but not logwrapper.bin, so to be safe i deleted hijack and renamed logwrapper to logwrapper.bak. Now my phone won't boot....
Anyway I can fix this without flashing a stock sbf on here?
rdbunch said:
I was following a guide to remove boot strap recovery, said to delete hijack in the system/bin folder and logwrapper, then rename logwrapper.bin to just logwrapper. Now I had hijack and logwrapper, but not logwrapper.bin, so to be safe i deleted hijack and renamed logwrapper to logwrapper.bak. Now my phone won't boot....
Anyway I can fix this without flashing a stock sbf on here?
Click to expand...
Click to collapse
You can try to use Early USB Enumeration and get into ADB. Most likely you will have to reflash.
Related
Hey guys so I haven't been following much lately due to exams. But I just found out Recovery was released for X10 and want to install it.
So I just wanted to know how I could safely remove 2.2 from my phone. I remember some guy deleting the folder off his sdcard and wrecking his phone. How do I avoid it?
mackdaddy187 said:
Hey guys so I haven't been following much lately due to exams. But I just found out Recovery was released for X10 and want to install it.
So I just wanted to know how I could safely remove 2.2 from my phone. I remember some guy deleting the folder off his sdcard and wrecking his phone. How do I avoid it?
Click to expand...
Click to collapse
Just do a clean install of whichever ROM you want using flash tool then install recovery mode onto that.
mackdaddy187 said:
Hey guys so I haven't been following much lately due to exams. But I just found out Recovery was released for X10 and want to install it.
So I just wanted to know how I could safely remove 2.2 from my phone. I remember some guy deleting the folder off his sdcard and wrecking his phone. How do I avoid it?
Click to expand...
Click to collapse
what u need to do mate is fairly simple. you need to delete a file and a folder.
boot into 2.1, open root explorer and make sure you are in R/W mode.
delete the chargemon file from /system/bin and delete the /sdcard/freeX10 folder
the freex10 folder contains all the data files for the 2.2 rom
the chargemon file contains the boot hijack that allows you to multi-boot. without this file (if you delete it all together like i am suggesting) the phone will simply boot into 2.1
once you have booted back into 2.1, you can setup the recovery menu
hope that helps mate, and thanks for not posting in the Dev thread!!!
mrtim123 said:
what u need to do mate is fairly simple. you need to delete a file and a folder.
boot into 2.1, open root explorer and make sure you are in R/W mode.
delete the chargemon file from /system/bin and delete the /sdcard/freeX10 folder
the freex10 folder contains all the data files for the 2.2 rom
the chargemon file contains the boot hijack that allows you to multi-boot. without this file (if you delete it all together like i am suggesting) the phone will simply boot into 2.1
once you have booted back into 2.1, you can setup the recovery menu
hope that helps mate, and thanks for not posting in the Dev thread!!!
Click to expand...
Click to collapse
Thank you so much, that worked like a charm.
Also LOL @ the dev thread comment. I am not really that retardo.
My O3D is constantly rebooting right after the boot img because I copied a wrong android.policy.jar in /system/framework/ . The original android.policy.jar is still there, renamed to android.policy.jar1. What is the easiest and simplest way to delete the faulty jar file and rename the original one?
P.S. ADB doesn't work in clockworkmod. Mount usb doesn't do anything.
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
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.
I had some problems with an in call echo. So I tried to fix this by some changes in mixer_paths.xml. I copied the original file to my sd-card so I thought I have a backup. But after I made some changes the phone get stuck and won't reboot. I didn't expect this to happen!
I restarted my phone in TWRP and tried to copy the original file from the sd-card. But I don't know how I can do this. Does anyone have an idea?? Is it possible in terminal? Or should I connect the phone to my computer and try with ADB?
Hopefully there will be a solution and I don't have to reinstall everything!
Edit: In terminal and file manager (in TWRP), I can't find the folder "etc" in "system". There is only the folder "usr". Or should I look at another folder?
NL_henk said:
I had some problems with an in call echo. So I tried to fix this by some changes in mixer_paths.xml. I copied the original file to my sd-card so I thought I have a backup. But after I made some changes the phone get stuck and won't reboot. I didn't expect this to happen!
I restarted my phone in TWRP and tried to copy the original file from the sd-card. But I don't know how I can do this. Does anyone have an idea?? Is it possible in terminal? Or should I connect the phone to my computer and try with ADB?
Hopefully there will be a solution and I don't have to reinstall everything!
Edit: In terminal and file manager (in TWRP), I can't find the folder "etc" in "system". There is only the folder "usr". Or should I look at another folder?
Click to expand...
Click to collapse
Could be just that you forgot to change permissions on mixer_path.xml....you could chmod it from twrp terminal.
chmod 644 /system/etc/mixer_path.xml
You could always restore your nandroid or dirty flash you rom.
Sent from my SM-G955F using Tapatalk