Related
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Raptor124 said:
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Click to expand...
Click to collapse
Can you upload a system dump?
Code:
adb pull /system/
gnufabio said:
Can you upload a system dump?
Code:
adb pull /system/
Click to expand...
Click to collapse
Sure - will take a while as i only have .5mb upload speed
Also worked for me, same exact way I did it.
Raptor124 said:
Sure - will take a while as i only have .5mb upload speed
Click to expand...
Click to collapse
Thanks
Raptor124 said:
Sure - will take a while as i only have .5mb upload speed
Click to expand...
Click to collapse
Instead of pulling, tar it up:
Code:
tar cvfj /sdcard/dump.tar.bz2 /system/
It will save all the permissions and files, and prepare special files (like, symlinks) in a readable format.
Also it will be way smaller!
Raptor124 said:
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Click to expand...
Click to collapse
What tablet version do you have? WW or US?
Turge said:
What tablet version do you have? WW or US?
Click to expand...
Click to collapse
I have The US Version
fonix232 said:
Instead of pulling, tar it up:
Code:
tar cvfj /sdcard/dump.tar.bz2 /system/
It will save all the permissions and files, and prepare special files (like, symlinks) in a readable format.
Also it will be way smaller!
Click to expand...
Click to collapse
where can i get tar - i am getting device not found when i use adb pull
Raptor124 said:
where can i get tar
Click to expand...
Click to collapse
Oh, you got me wrong. Issue that command in adb shell, on the phone itself!
Tar should be built-in within busybox, or if it isn't there, make an ext4 dump:
Code:
mount (this will list the mounted partitions, look for the one what's with /system!)
dd if=/dev/block/mmcblk0p[whatever partition was numbered as /system] of=/sdcard/system.img bs=4096
This one (ran in ADB shell too) will produce an Ext4 image of the system partition, like if you pulled it from nvFlash (or a full blob).
fonix232 said:
Oh, you got me wrong. Issue that command in adb shell, on the phone itself!
Tar should be built-in within busybox, or if it isn't there, make an ext4 dump:
Code:
mount (this will list the mounted partitions, look for the one what's with /system!)
dd if=/dev/block/mmcblk0p[whatever partition was numbered as /system] of=/sdcard/system.img bs=4096
This one (ran in ADB shell too) will produce an Ext4 image of the system partition, like if you pulled it from nvFlash (or a full blob).
Click to expand...
Click to collapse
in progress - using tar - had to install busybox
tried the mount method, could not get it to work either
Raptor124 said:
this is how i did it
1. did check for update
2. downloaded update
3, un-rooted with Voodoo OTA Root Keeper
4. installed update
5. when tablet had finished installing and had rebooted - ran Voodoo OTA Root Keeper and restored root
6. all data was kept - no need to reinstall apps or change any settings, desktop also had not changed had the same layout and wallpaper
now I am rooted and have Android 4.03
Click to expand...
Click to collapse
I followed the same methodology except for #3 where I clicked on Back Up Root in Voodoo OTA Root Keeper. Everything went really smooth including the Camera update. All of my data was intact and I didn't have to reinstall any apps or change any settings. Excited to be rooted and have ICS!
mwbarb said:
I followed the same methodology except for #3 where I clicked on Back Up Root in Voodoo OTA Root Keeper. Everything went really smooth including the Camera update. All of my data was intact and I didn't have to reinstall any apps or change any settings. Excited to be rooted and have ICS!
Click to expand...
Click to collapse
for no 3 i had already had backup up the root after i rooted when i was on .33
Raptor124 said:
in progress - using tar - had to install busybox
tried the mount method, could not get it to work either
Click to expand...
Click to collapse
uploading - will post link when upload is complete - have to go out for a while
Raptor124 said:
uploading - will post link when upload is complete - have to go out for a while
Click to expand...
Click to collapse
link for system dump
http://dl.dropbox.com/u/8589057/dump.tar
Raptor124 said:
link for system dump
http://dl.dropbox.com/u/8589057/dump.tar
Click to expand...
Click to collapse
Thanks!
One question: did you add any Samsung stuff to it? There appears to be some apps added from the Samsung Galaxy Tab builds!
fonix232 said:
Thanks!
One question: did you add any Samsung stuff to it? There appears to be some apps added from the Samsung Galaxy Tab builds!
Click to expand...
Click to collapse
sorry i ment to mention that - yes there is - ignore it, i was trrying to get them to work on the prime but they won't
had the dump done before i could delete them
I see. Could you please tell me what did you exactly add to the ROM? Every file what was going under /system, please! So we can have a clean system
fonix232 said:
I see. Could you please tell me what did you exactly add to the ROM? Every file what was going under /system, please! So we can have a clean system
Click to expand...
Click to collapse
dlna.apk
dlna.odex
divx.apk
divx.odex
fmradio.apk
fmradio.odex
jobmanager.apk
jobmanager.odex
com.sec.android.app.controlpanel.apk
memo.apk
memo.odex
minidiary.apk
minidiary.odex
SamsungApps.apk
SamsungAppsUNA3.apk
signin.apk
signin.odex
Swype.apk
Swype.odex
VoiceSearch.apk
VoiceSearch.odex
VoiceToGo.apk
VoiceToGo.odex
I wanted to extract some files from here, but when I expand the .tar file, I'm just left with a 474MB "dump" file with no extension, etc... how can I see the contents of that file?
And this dump was from the 9.4.2.7-20120106 US build, correct?
[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
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'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.