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.
Related
Someone who has done the whole DI01 update, please dump their system for me, or just the framework folder, apparently the one given to me had the stock android lockscreen patch applied to it lol.
Aside from that, the DI01 deodex works perfect, I opt_png'ed and zip_align'ed all the apk's, as well as the framework-res and twframework-res.
I will also need someone who knows how to sign updater-scripts to open the one attached, and just save it again properly and upload it for me. I am trying to get a flashable CW zip but the darn thing always gives me a status 6 error, which means the CW cannot read the updater script.
Sorry for the n00b question, but what benifit does deodexing provide? Also if there is another software update will I have to readd any .apk's to my /system folder?
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Is there anything involved in a dump besides just copying the files in /system?
namebrandon said:
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Click to expand...
Click to collapse
Because I am too lazy to go through all that.
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
s44 said:
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
Click to expand...
Click to collapse
That is all I need. The only things I deodex are the contents of system/app and system/framework.
frostman89 said:
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
Click to expand...
Click to collapse
Try a real editor, like bluefish or something.. Those scripts look like sh#! in notepad.
If no one has done it by tonight, just grab me on IRC and I'll do it under Linux for you.
Make sure you've got the file/directory structure right too.. You can't just throw a script in a zip file, but I'm sure you knew that. Myself and and a few others had the wrong directory structure at first, don't remember what error number that gave us though.. I think it just froze.
OK, how can I get it to you? I can't post links or (I think) files yet.
s44 said:
OK, how can I get it to you? I can't post links or (I think) files yet.
Click to expand...
Click to collapse
You can just zip it up and upload it to mediafire.com
Just splice up the link like WWW. Website. Com and I will just delete the spaces.
Mediafire upload just not working for some reason. Hm.
s44 said:
Mediafire upload just not working for some reason. Hm.
Click to expand...
Click to collapse
http://multiupload.com/
J1HDKEGYAR at multiupload
[GUIDE-IMPORTANT!] "rescue-backdoor" - regarding bootloop, do it before change in sys
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- do not use "File Manager HD" or other filemanager, which doesn't support root operations (thx kryddan),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
To enter RECOVERY-MODE - power off device,
hold vol-down + power button.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Remember, that after reflash in recovery, your build.prop will be updated back
to higher value, then to be safe you need to reapply modification!
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
great guide, thank you
I think an automated-script would be much appreciated
condi said:
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
Click to expand...
Click to collapse
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
It should be under '/cache/ota' ... nowhere else ..
Judah001 said:
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
Click to expand...
Click to collapse
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
condi said:
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
Click to expand...
Click to collapse
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Thank you condi... The instructions worked perfectly!!
Judah001 said:
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Click to expand...
Click to collapse
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
kryddan said:
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
Click to expand...
Click to collapse
That did the trick. I used the root browser in rom tool box and copied the zip to my sd card. Thank you for the help guys.
Good advice kyddan ... same on my tab with file manager HD.
I work normally with Root Explorer or File Expert.
Both show the folders and files in /cache .. File Manager HD do not.
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
EDIT: nevermind. I did so. Worked.
sebarkh said:
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
Click to expand...
Click to collapse
Yep, exacty. And then you will get newest ota zip of 111201038 pozdro
hahahahah I just had brick... I'm working on auto-install script for "rescue-backdoor", and accidentally I've pushed empty 0bytes build.prop - after reboot - sony logo, then black screen.... and guess what...
recovery reads incremental value (which doesnt exists..) as "0" zero
so i've got lower value, and reflash done.
after reboot my tab started correctly, but.. after reboot again brick - black screen.
fortunatelly - after few min with black screen i've got adb access.
but for first - i can't get root access.. 'su' not works.
but... '/system/xbin/su' works root lets check - build.prop still empty,
remounted system as rw, pushed correct build.prop - ahhh again working !!
that was good experience hahah.
-------------edit:
i've got auto-install tool ready... need to make one more full test with my device and will publish it.
full automatic !!!!!
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
ase3000 said:
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
Click to expand...
Click to collapse
Just wait for automatic-tool. Its ready, but need to make final tests.
condi said:
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Click to expand...
Click to collapse
In which way we can enter to recovery??
riccardo91 said:
In which way we can enter to recovery??
Click to expand...
Click to collapse
power off, hold vol-down + power.
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
riccardo91 said:
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
Click to expand...
Click to collapse
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
condi said:
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
Click to expand...
Click to collapse
I bricked my XTS playuing with build.prop. Shame I didn't see this post before. For future - how can I edit build.prop in a safe way? I changed file permission then I forgot to restore default. After restart brick. Do I need to change permission to edit build.prop then do i NEED to restore proper permission back? I'm still confused with it
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
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.
New update today from MT2-L03V100R001C00B126 to MT2-L03V100R001C00B148
Mine fails. Downloads the update, reboots, then fails to write patch. Where is this update stored? I want to try to save it to external SD and update that way. Anyone know?
My Bootloader is unlocked, and phone rooted. Would that prevent the update? Mt friend has same phone and he is rooted, bootloader unlocked, and his took the update just fine. Scratching my head.
Any help?
rekamyenom said:
New update today from MT2-L03V100R001C00B126 to MT2-L03V100R001C00B148
Mine fails. Downloads the update, reboots, then fails to write patch. Where is this update stored? I want to try to save it to external SD and update that way. Anyone know?
My Bootloader is unlocked, and phone rooted. Would that prevent the update? Mt friend has same phone and he is rooted, bootloader unlocked, and his took the update just fine. Scratching my head.
Any help?
Click to expand...
Click to collapse
This is the Error I am getting.....
Look in either /sdcard/HwOUC or /storage/sdcard1/HwOUC. Note that the update_sign.zip is deleted after a failed update. It's not deleted if you try to update from recovery manually and it fails.
foltz61 said:
Look in either /sdcard/HwOUC or /storage/sdcard1/HwOUC. Note that the update_sign.zip is deleted after a failed update. It's not deleted if you try to update from recovery manually and it fails.
Click to expand...
Click to collapse
I will Download the Update, then tell it to remind me later on the install, then try to locate the update where you said. I feel if I locate and save the update to the external SD, I can get it to take....
Found it under /storage/sdcard1/HwOUC
Tried installing from recovery (stock), "apply update from External Storage" Phone reboots, and same results (See pic). Dam!
The stock recovery can only see the external sdcard so that's fine.
foltz61 said:
The stock recovery can only see the external sdcard so that's fine.
Click to expand...
Click to collapse
I think I need to rename the .zip to something else to do a Local Update
No. You will be able to select it from recovery.
foltz61 said:
No. You will be able to select it from recovery.
Click to expand...
Click to collapse
I tried and selected the update_sign.zip but same result
Going to try this
1. Unzip the downloaded update file
2. Place the Update.app from the update_sign.zip inside a folder named “dload” on your SD card root directory
3. Power off and turn on your Ascend Mate by holding volume down + volume up + power button (or do a local update from system update)
Update: When I did this it said it was successful, but according to my build number, it did not.
There is no update. app in my zip. I just booted to stock recovery and chose install zip from internal sd. I selected update_sign.zip and let it do it's thing.
foltz61 said:
There is no update. app in my zip. I just booted to stock recovery and chose install zip from internal sd. I selected update_sign.zip and let it do it's thing.
Click to expand...
Click to collapse
Tried that and get the same fail....
foltz61 said:
There is no update. app in my zip. I just booted to stock recovery and chose install zip from internal sd. I selected update_sign.zip and let it do it's thing.
Click to expand...
Click to collapse
I will try from internal sd I was trying from external...
Same results "Assert Failed" after checking patch files...
Frustrating as hell...
Update took on 2 other identical phones but not this one.... Strange
I'm stumped... Guess I will sleep on this until I can figure it out.... Appreciate the input, if anyone has any ideas, chime in.
pls check the system update thread in general section, you have to restore all the to-be-upgrade files to stock. i have posted a system files zip there. (sorry, type in phone, hard to paste link)
--UPDATE
also, if you are missing facebook app, It is in the /cust/normal/us/app location, I just uploaded zip to the one google drive folder with the system zip:
http://tinyurl.com/qzxkm4x
Ill try that now thanks......
rekamyenom said:
This is the Error I am getting.....
Click to expand...
Click to collapse
The build.prop error might be because you may have changed it away from stock (for xposed to work for example). It has to be changed for the update to work. You can change it back afterwards.
See here for update procedure:
http://forum.xda-developers.com/asc...update-ota-t2897452/post55905077#post55905077
Sent from my MT2L03 using Tapatalk
arcadesdude said:
The build.prop error might be because you may have changed it away from stock (for xposed to work for example). It has to be changed for the update to work. You can change it back afterwards.
See here for update procedure:
http://forum.xda-developers.com/asc...update-ota-t2897452/post55905077#post55905077
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
I have stock recovery, never changed it, the only thing I ever did to the build.prop with root browser and an editor, was add to line items for a keyboard I am using. I may have deleted a few apps (Can't remember) with Chef's App freezer...
Here are the 2 lines I added to build prop
ime_extend_row_keyboard=true
ime_vibration_pattern=0:20
rekamyenom said:
I have stock recovery, never changed it, the only thing I ever did to the build.prop with root browser and an editor, was add to line items for a keyboard I am using. I may have deleted a few apps (Can't remember) with Chef's App freezer...
Here are the 2 lines I added to build prop
ime_extend_row_keyboard=true
ime_vibration_pattern=0:20
Click to expand...
Click to collapse
Remove those lines and try the update again. It probably does checks to ensure it is unedited before patching. You can add that back after updating.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
Remove those lines and try the update again. It probably does checks to ensure it is unedited before patching. You can add that back after updating.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
Tried removing the lines and no go. Did a back up then a factory reset, then tried update, still same error.... Going to try to go over the build.prop line by line now.
rekamyenom said:
Tried removing the lines and no go. Did a back up then a factory reset, then tried update, still same error.... Going to try to go over the build.prop line by line now.
Click to expand...
Click to collapse
Here's the stock build.prop file in a zip (attached). Unzip then copy build.prop to your sd card. Use ES File Explorer in root explorer mode. It goes in /system
For reference, the owner is root and the permissions are rw- r-- r-- (644).
Has this issue been resolved?
superbass311 said:
Has this issue been resolved?
Click to expand...
Click to collapse
Yes and you helped resolve it