Alot of people i see are still getting the update failed error...i was getting it and i found out i wasnt removing bootstrap completly..so heres the process i use
1. Go into titanium backup and find razr bootsrap
2. Click wipe data then uninstall
3.Go to root explorer or es file explorer
4. Navigate to system/ bin
5.In the bin folder you will find two files..."logwrapper" and "logwrapper.bin." Delete the file that is named just "logwrapper."Then go to the logwrapper.bin file and click rename. DELETE the". bin" so your just left with "logwrapper."
6.Reboot and except the ota
This will work only if you are stock rooted......
Sent for my maxxed out razr
Also if you didnt use voodo to backup root.....you can use motofail to root. 181.....i did with no issues
Sent for my maxxed out razr
Janker5050 said:
Alot of people i see are still getting the update failed error...i was getting it and i found out i wasnt removing bootstrap completly..so heres the process i use
1. Go into titanium backup and find razr bootsrap
2. Click wipe data then uninstall
3.Go to root explorer or es file explorer
4. Navigate to system/ bin
5.In the bin folder you will find two files..."logwrapper" and "logwrapper.bin." Delete the file that is named just "logwrapper."Then go to the logwrapper.bin file and click rename. DELETE the". bin" so your just left with "logwrapper."
6.Reboot and except the ota
This will work only if you are stock rooted......
Sent for my maxxed out razr
Click to expand...
Click to collapse
When I try to delete logwrapper ES file explorer says "logwrapper cannot be deleted". I even tried renaming it something else like logwrapper2 or logwrapperbak and it says "sorry, operation failed". Any ideas?
Im on stock rooted rom, ota 748 xt912 verizon.
Thanks
danh18 said:
When I try to delete logwrapper ES file explorer says "logwrapper cannot be deleted". I even tried renaming it something else like logwrapper2 or logwrapperbak and it says "sorry, operation failed". Any ideas?
Im on stock rooted rom, ota 748 xt912 verizon.
Thanks
Click to expand...
Click to collapse
Do you have root enabled on es? Our you could just use root explorer.
Sent from my DROID RAZR using xda premium
Yes I enabled root. Might just have to go buy root explorer, you think that's the solution?
Did not work. Really kinda frustrating. Buddy of my has same phone same basic setup yet his went through first time. Mine......not so much
Sent from my DROID RAZR using XDA
joeyboots13 said:
Did not work. Really kinda frustrating. Buddy of my has same phone same basic setup yet his went through first time. Mine......not so much
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
Did you remount the filesystem R/W? It's read-only (R/O) by default...
Ehm, I'm on cwm for GSM, and I've this problem: with ES file explorer, I can't find system folder! And I can't even find the logwrapper with search option!
How can I resolve?
draga277 said:
Ehm, I'm on cwm for GSM, and I've this problem: with ES file explorer, I can't find system folder! And I can't even find the logwrapper with search option!
How can I resolve?
Click to expand...
Click to collapse
Menu->Options->
Enable "Up to Root Folder"
that did it! Thanks, now to try the update...
I didn't remove bootstrap recovery and ota went without any problems, just had to reroot.
Phone so sharp, I sliced myself.
Giblet535 said:
Did you remount the filesystem R/W? It's read-only (R/O) by default...
Click to expand...
Click to collapse
How do you fix this? I'm thinking it may be my problem as well.
Giblet535 said:
Menu->Options->
Enable "Up to Root Folder"
Click to expand...
Click to collapse
Tnx!!!!
I finally figured out how to do this... now Im in a bootloop!! HELP!
blueice5249 said:
I finally figured out how to do this... now Im in a bootloop!! HELP!
Click to expand...
Click to collapse
You might want to RSD back to stock at this point.
That's what I'd do, just because the state of the device is unknowable.
Giblet535 said:
You might want to RSD back to stock at this point.
That's what I'd do, just because the state of the device is unknowable.
Click to expand...
Click to collapse
can you help me out with this? All the phone does is keep trying to reboot. itself. Im downloading RSD now.
blueice5249 said:
can you help me out with this? All the phone does is keep trying to reboot. itself. Im downloading RSD now.
Click to expand...
Click to collapse
Step by step instructions
Keep that handy! If you're doing this right - modding like you mean it - you'll have to do this another 20 times with this phone.
]I found this in my log...
" Verifying current system...
failed to stat "/system/app/VZWIM.apk": No such file or directory
file "/system/app/VZWIM.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/VZWIM.apk", "42c79537fd1c731d331368bee41923e8e6c20c71", "67b41ea216f98d59e6acba7ad92ad7108f667412")
assert failed: apply_patch_check("/system/app/VZWIM.apk", "42c79537fd1c731d331368bee41923e8e6c20c71", "67b41ea216f98d59e6acba7ad92ad7108f667412")
E:Error in /cache/Blur_Version.6.12.173.XT912.Verizon.en.US.zip
(Status 7)
Installation aborted."
Cache/recovery /last log
Can't figure out why its failed, the vzmim. Apk was renamed to (.bak) .
I navigate to the file and click as to instal and get the "parsing" error.
Edit : lmfao @ those weren't there
----posted maxx'ed out--
How I succeeded
I tried the OP and several other things that seemed to make sense at the time, and then I gave up:
TiBu all user apps, unchecking the red items
RSD to the .173 AP Fastboot image
OTA update to .181
MotoFail root
Installed TiBu, restored user apps + data
Safeboot Recovery
New nandroid backup
Ta da
Weird, I had bootstrap for a while, just deleted from the app drawer like any other app, and the 181 ota went just fine
Related
I attempted as many did to update the new OTA. You can find it on this forum. I constantly got an error 7 after the install failed as the install looked at my Preinstall files. After any number of attempts, I used a standard Preinstall directory. I deleted the current Preinstalled, using Root Explorer I did a copy paste. Bingo, Bango, Bongo. Install Complete!!
Here is a link to a dropbox copy of the preinstall.
http://dl.dropbox.com/u/8489906/preinstall.zip
posted a couple of different forums. Trying to help
Some were having trouble with the dropbox download. On another site a helpful member uploaded them to:
http://www.megaupload.com/?d=LKAU0HOO
Might just be me, but the link isn't working. Can you re-post it?
Sent from my DROID RAZR using XDA App
There you go. Try it now.
Could someone please provide detailed instructions on how to apply this?
Some help
My solution to the how and it goes without saying - you are on your own if you brick you phone.
1. Download the file. I am uploading to another online file site now and will update the link soon.
2. Unzip the downloaded file preinstall.zip on your computer. Connect USB to computer as a mass storage drive and copy preinstall directory to your SD-Ext.
3. Disconnect your computer and start Root Explorer. If you don't have it, it is available in the Market.
4. Go to the Main (root) directory of your Razr and scroll down to the Preinstall Directory. Using Root Explorer copy the current preinstall directory to your SD-ext in an out of the way directory.
5. Go back to the root directory. At the top of the screen is an small icon labeled RW. Select this option by touching the icon - it should now say RO. RW=Read Write RO-Read Only. The directory must be in the RW state to copy the preinstall directory.
6. Go back to the root directory and delete the old "preinstall" directory.
6. Go back to the SD-Ext where you stored the downloaded "Preinstall" directory. Select this file and copy. Root Explorer will now have the Paste option showing on the bottom left of the screen.
7. Navigate back to the Root (main) directory and press "paste". Root Explorer should now paste the downloaded copy of the preinstall into the root directory.
Note: Based on my limited experience if you simple copy and overwrite the preinstall directory, portion of the old preinstall will be left in the root directory. These files are the problem causing the Error 7 in the update - IMO.
Hope this helps.
benlane said:
My solution to the how and it goes without saying - you are on your own if you brick you phone.
1. Download the file. I am uploading to another online file site now and will update the link soon.
2. Unzip the downloaded file preinstall.zip on your computer. Connect USB to computer as a mass storage drive and copy preinstall directory to your SD-Ext.
3. Disconnect your computer and start Root Explorer. If you don't have it, it is available in the Market.
4. Go to the Main (root) directory of your Razr and scroll down to the Preinstall Directory. Using Root Explorer copy the current preinstall directory to your SD-ext in an out of the way directory.
5. Go back to the root directory. At the top of the screen is an small icon labeled RW. Select this option by touching the icon - it should now say RO. RW=Read Write RO-Read Only. The directory must be in the RW state to copy the preinstall directory.
6. Go back to the root directory and delete the old "preinstall" directory.
6. Go back to the SD-Ext where you stored the downloaded "Preinstall" directory. Select this file and copy. Root Explorer will now have the Paste option showing on the bottom left of the screen.
7. Navigate back to the Root (main) directory and press "paste". Root Explorer should now paste the downloaded copy of the preinstall into the root directory.
Note: Based on my limited experience if you simple copy and overwrite the preinstall directory, portion of the old preinstall will be left in the root directory. These files are the problem causing the Error 7 in the update - IMO.
Hope this helps.
Click to expand...
Click to collapse
I hope this works This has been driving me crazy! I'll post my results and spread the word to others I've spoken to about this frustrating issue. Great find, and thanks for sharing!
Edit: Strange, as soon as I delete the original preinstall folder, and hit paste, it asks if I want to merge folders instead of just paste. If I go into another folder, then back to the root folder, preinstall reappears... I'll try merging, but sounds like that isn't going to work.
Edit 1: Failed Maybe my issue has something to do with the preinstall folder being repopulated the instant I delete it, which doesn't allow me to simply replace it with the one hosted in the OP.
I believe I only have one option now... to learn how to dev, graduate, intern at Motorola, get a job at Motorola and work my way up the ladder until I can decide how FXZ files are protected, and release them to the public!
I still get this error
assert failed: getprop("ro.product.device") == "cdma_spyder" || getprop("ro.product.product") == "cdma_spyder"
E: Error in /sdcard/Blur_version.6.11.744.X912.Verizon.en.US.zip
(Status 7)
Strange issue with the preinstall
Not sure whats happening with the preinstall but I see that Nitro has a very straightforward install on another Razr forum.
Could you possibly direct me to that, via pm if necessary?
Sent from my Transformer TF101 using xda premium
benlane said:
Not sure whats happening with the preinstall but I see that Nitro has a very straightforward install on another Razr forum.
Click to expand...
Click to collapse
Please post or pm the link to the nitro install. Thanks!
Yes...Having trouble as well, if anyone has the nitro link...
Nitro's stuff
teegunn said:
Please post or pm the link to the nitro install. Thanks!
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/t...rooted-rom-744-system/page__p__1986#entry1986
benlane said:
http://www.droidrzr.com/index.php/t...rooted-rom-744-system/page__p__1986#entry1986
Click to expand...
Click to collapse
Yep, that did the trick.
So if I just froze some apps with tb can I just unfreeze them and install the ota without a problem?
Edit: never mind...I underuse my apps updated and rerooted :-D
Sent from my DROID RAZR using Tapatalk
networkdood said:
Yep, that did the trick.
Click to expand...
Click to collapse
Somehow that thread got killed....I was able to grab the rom, but not the update that was posted....Anyone have the update handy? Was there anything special about it or was it the normal one that already available?
EDIT: Nevermind, I dont need it...My issue, like most, was the preinstall directory.
Hi to all!
This is my first android device, and i am new to Unix-like systems.
I have tried to unlock, root & install custom rom on my phone. Used this instruction:
http://forum.xda-developers.com/showthread.php?t=1302423
Everything go perfect until step:
DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favorite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'
I always get "read only" trouble. As I understand, the problem in root access. I haven’t got it.
I have tried:
http://forum.xda-developers.com/showthread.php?t=740748
Then
http://forum.xda-developers.com/showthread.php?t=1046626
But in any case i get "read only" truing to delete 'install-recovery.sh'
Will be grateful for tips how to successfully root my device.
..
a guide is in the "stickys" in general forum made by swiftks
Sent from my MB860 using Tapatalk
Use root tools. And there's a little button to change it from read only to read/write. Then delete the file.
Sent from my MB860 using xda premium
kycats said:
Steps for rooting:
http://forum.xda-developers.com/showthread.php?t=1255548
It works like a champ.
Click to expand...
Click to collapse
Tnx very much, it worked.
But i still can't delete the
install-recovery.sh
Trying via all possible file explorers, and also tried
http://forum.xda-developers.com/showthread.php?t=740748
one more time. still get
rm failed for /system/etc/install-recovery.sh, Read-only file system
You need to go into the options of the file manager and enable root, and also mount system as writable. I use ES file explorer from market...its free. If it still fails my guess is you are not rooted.
I have root access, have checked with root checker basic. Have enabled root in es file explorer, still same problem.
I have made some photos, in attached files.
Did you also check the option 'mount system directory as writable' in es file explorer options
maulich said:
Did you also check the option 'mount system directory as writable' in es file explorer options
Click to expand...
Click to collapse
It helped. Thank you very much!
I've been getting FCs with apps like Tiny Tower and HeyTell on all stock-based roms that I've flashed.
However, this does not occur on sbf 198_7.
Any ideas?
Edit: I should mention that I'm using locked 4G-capable versions of these roms.
Yeah I get the same problem but I noticed that it happens on the deodexed version. The "update 1024 (data fixed)". I think any rom that uses that will get the fc problem. I know rocko rom has the same problem.
If you flash SBF 198_6 then install the 198_7 it fixes the problem.
andychan3e said:
If you flash SBF 198_6 then install the 198_7 it fixes the problem.
Click to expand...
Click to collapse
Flash SBF 198_6, then flash 198_7, or "install" 198_7? How do you install it :\ thanks
nevermind flashing 198_6 wont help.
i just figured out that some files are missing in the deodexed version.
when i copied it i lost battery percentage 1% increment.
once i find out which specific file it is, ill upload it
i figured it out.
copy "com.google.android.maps.jar"
to "/system/framework/"
you must have root
and a file explorer that uses root
ie. root explorer, es file manager, ...
es file manager: you need to go to "settings"
and enable "root explorer" and "mount file system"
andychan3e said:
i figured it out.
copy "com.google.android.maps.jar"
to "/system/framework/"
you must have root
and a file explorer that uses root
ie. root explorer, es file manager, ...
es file manager: you need to go to "settings"
and enable "root explorer" and "mount file system"
Click to expand...
Click to collapse
I dont know how that got deleted from my Rom but thanks
Sent from my MB855 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.
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.