Related
OK, for starters:
Tablet's current stats:
ROM: CWM-Rooted_Acer_A500_7.006.01_COM_GEN2
Recovery: Stock US 1.141.07_COM_GEN1
Root status: Rooted
Problem at hand: Cannot install OTA updates. I used Acer Recovery Installer to originally install CWM so I could flash ROMs (duh). So I used Acer Recovery Installer to have it install the stock recovery image so I could actually install the OTA updates. I know this likely means I would lose root, and that is OK.
When I installed the stock recovery back, I tried to let it install the update. It would reboot, show the package opening (little box that was open and a progress bar showed up). The bar got about 25% completed, then it changed into a triangle with a "!" inside it, and the little Android dude below it. After a few minutes, it would reboot by itself. Once booted up, I would get a message that simply said "Update Failed".
I brought this up in another thread, and someone suggested I unroot as well. I immediately tried to do that, but IconiaRoot gives me the following:
Removing superuser.apk
Removing /system/xbin/su
Sleeping in 5 seconds...
Something went wrong.. you are still root?!?!
I can confirm I am still rooted by going into terminal emulator and running su and I get a # sign. So I am at a loss now on what else to try. With the stock recovery, if I tell Acer Recovery Installer to reboot into recovery, when it reboots, all I get is the triangle with a "!" in it. I noticed the ROM has GEN2 and my stock recovery has GEN1, and the OTA update ends with GEN2, is that an issue?
EDIT: I also know now there are other rooted ROMs with these OTAs applied. I'd like to unroot and go back to stock, so please do not recommend this.
Ok did you make a backup via CWM ?
In the other thread the recovery i restored was the backup i made of my one via Acer recovery,
If i was you i would reinstall CWM and make sure that recovery is working then wait for someone to come in and tell you the correct stock recovery for your one is.
oh i get u now, u got the gen2rom installed and u want back to your own stock gen1 to get the OTA, correct?
u need a cwm backup of 3.2 gen1 stock, when u restore it, u should receive an OTA notification for the 3.2.1 GEN1 OTA. Before you download it, u need to be rooted, use the backdoor/OTA method of timmyDeans. It will create a backdoor so after you have installed the OTA you can get in to run the installtools command again to root and install cwm again. AND you will still recieve OTA's.
Iconia Root - only works on 3.1, it will not work for 3.2, so it will throw an error.
But i'm sure root wont prevent the install as the OTA overwrites system files and resets the permissions, it also checks all system apps are there, so if you;ve deleted any bloatware or changed build.props the update will fail.
I have spent the last week trying to get back to stock so i can OTA. I have read hundreds of posts and tried all the methods that had been posted. The easiest and quickest and most successful way of achieving this was the backdoor method. Yes you need adb installed but you dont actually use it, it is all done for you. there is a very good walkthrough here http://www.chdcomputers.gr/en/mnu-kb-en/mnu-kb-android-en/mnu-kb-android-devices-en/mnu-kb-android-a500-en/254-art-kb000005-en
Then install the backdoor v3 (link in sig) -have a look and see if that will get u to where u wanna be!
Decideed it was easieeer to just install one of the prerooted roms from the dev forum. Running 7.014.14.com gen 1 now. Thanks guys.
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
LORD MJ said:
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
Click to expand...
Click to collapse
nyepo said:
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
Click to expand...
Click to collapse
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
LORD MJ said:
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
Click to expand...
Click to collapse
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
I did a "flash stock+unroot" and relocked my device via the Wug app and it still errors
eksasol said:
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
Click to expand...
Click to collapse
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
LORD MJ said:
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
Click to expand...
Click to collapse
The OTA update can fail for many reasons, it could be due to any changes to the /system partition which is what root does, such as changes to gps.conf file, changes in build.prop, different kernel or radio.
If you're going to make a full backup, what you should do is flash a full factory image (link in my signature, and provided you already backup your data.) Then boot into a custom recovery to make a full backup, (not flash the recovery, but: fastboot boot twrp.img) When you do the backup make sure the boot (kernel) and recovery partition are selected. However, you can't backup the radio partition, but that should be fine unless you intend to use the LTE radio.
I have a similar problem. I have ROOTED device with TWRP recovery and stock 4.3 android (obtained OTA before rooting), and I just got notification that my OTA update to 4.4 is ready to be installed.
So I clicked Restart and Install button and the phone restarts(as it should) but after that it went in TWRP recovery and waited for some instruction I suppose. I didn't know what to click exactly, so I clicked Reboot from TWPR menu and it went in fastboot mode. From fastboot I chose Start and phone turns on. Updating didn't even start..
So, were there something that I could do when I was in TWRP recovery that could initiate updating process, or I never had a chance?
What exactly I should do to get that update on my phone? Sorry for my English and if was unclear.
Hi!
It is not the first time I root phones but this time seems I cannot manage it.
I have updated and re-rooted my nexus in every ROM update with no problems. Today I received the OTA 4.4 update and did a re-root of my phone BEFORE applying the update (don't ask me why I did it before... I'm just dumb).
I used the Nexus root toolkit as other times (I once uploaded cyanogen in a ZTE Skate through CWM but found the root kit more straight for my nexus). Now I'm stuck in the 'Pushing root files to your device' stage and the program is 'not working'. I still have it plugged and don't know what to do. Since it was rooted before I hope it has CWM still there. Should I unplug it and repeat the process or do I have a brick now?
Any advices would be appreciated. Thanks in advance.
(yes, I feel stupid)
Seems solved.
Since it was rooted and I didn't check the flash bootloader option only rebooting returned the phone to its previous state.
Next time...
Next time, flash temproraly (until next reboot) CWM or TWRP recovery And choose SuperSU-UPDATE zip. Its safe for OTA.
msihp said:
Next time, flash temproraly (until next reboot) CWM or TWRP recovery And choose SuperSU-UPDATE zip. Its safe for OTA.
Click to expand...
Click to collapse
I see... always the hard way seems beetter. My thought was that if I updated superSU before the OTA I wouldn't have to re-root again but I see those kits doesn't always work.
The CWM still scaries me although I used it before. I guess I will have to deal with it.
Thanks for your advice
I used Google's batch file on windows to flash the stock 5.0, having unlocked the bootloader and also installed the chainfire root. Just wondering whether I'll get any fixes, or whether i'll have to always repeat this process, wiping out everything on the device in the process.
You may get prompted to download and install new updates when they arrive, but they will fail upon installation unless you're 100% stock.
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Does the Google image download page (https://developers.google.com/android/nexus/images) get updated as Lollipop gets updated? Or am I going to have to do OTA updates?
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
igeigeige said:
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
Click to expand...
Click to collapse
Well, I'm a bit confused. I'm on stock, but i need root, so i installed cfar, which I think included super su. when a new version of super su came out (i was alerted via google play), i needed to install the twrp recovery (which I didn't have installed at that point) to update it. So I guess I'm not stock any more, even though I've not actually put a non-stock image on. So even if the OTA update message popped up, I doubt it's safe to install it that way, even if it let me. I'm just not sure whether I need to a factory reset/wipe etc before updating, or if I can do a dirty update (the OTA is effectively a dirty update, isn't it?). And, like i said, i'm not sure whether that page gets updated with new images, or whether you're supposed to just put the initial one down and then do OTA updates (and only then root, change the recovery etc).
You have a stock rom but with a CUSTOM recovery. Yes, ota will prompt you to update, but DON'T. You should convert to stock recovery first. Because if you do, the update will push through, but once it asks you to boot to make the update in effect, you will have a NO COMMAND error - bootloop, and only fastboot and recovery (sort of dysfunctional). Just like most of the people here, including me. So make backup of your files first before doing the update. Cheers :good:
Sent from my Nexus 10 using XDA Premium 4 mobile app
If having a custom recovery is an issue, why could I flash ota zips from custom recoveries ever since buying the tablet?
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Rizz67 said:
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Click to expand...
Click to collapse
Hi, what i did was flashing the official factory image from google via fastboot/bootloader... Make a nandroid backup first though.. Because you'll need to clean flash (system partition/cache and data) to avoid future problems.
please educate me
A few weeks ago I rooted my N4 with CFAR (& of course had to wipe out everything). My understanding was that now that my bootloader is unlocked, I can sideload new images, thus sparing me a rewipe -- & in my ignorance, was anticipating that ChainFire would make 5.0.1 images in due course.
So, If I want to root subsequent 5.x.x releases, how would this work in real life??
Can i just restore stock recovery and then install the 5.0.1 ota update without losing everything?
Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?